05.08.2014 Views

here - Stefan-Marr.de

here - Stefan-Marr.de

here - Stefan-Marr.de

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

6.2. Case Studies<br />

concepts has practical relevance. Consequently, the concepts supported by the<br />

OMOP are relevant.<br />

Absence of wi<strong>de</strong> Support in Today’s VMs In or<strong>de</strong>r to evaluate the novelty<br />

of the OMOP, i. e., to assess whether these concepts are not yet wi<strong>de</strong>ly<br />

supported in VMs, Sec. 6.5.1 relies on the VM survey in Sec. 3.1. For each concept,<br />

this analysis assesses whether the concept is supported. Furthermore,<br />

the analysis consi<strong>de</strong>rs the whole set of concepts and its support by a single<br />

VM to validate the initial premise that today’s VMs support is insufficient. By<br />

showing based on the VM survey that this is the case, it supports the claim<br />

that the OMOP can add relevant support to today’s VMs.<br />

Significance In or<strong>de</strong>r to evaluate the significance of the support the OMOP<br />

provi<strong>de</strong>s, Sec. 6.5.1 argues that the OMOP facilitates the implementation of<br />

all concepts that were i<strong>de</strong>ntified as benefiting from VM support for semantic<br />

enforcement. Since the OMOP covers all concepts, t<strong>here</strong> is an indication that<br />

the supported set is sufficiently large to warrant interest.<br />

Unifying Substrate Finally, Sec. 6.5.1 discusses the unifying properties of<br />

the OMOP. The goal is to argue that the OMOP makes an abstraction of concrete<br />

programming concepts. The section shows this by relating the concepts<br />

to the mechanisms the OMOP exposes and by <strong>de</strong>monstrating that it is not a<br />

one-to-one relationship between mechanisms and concepts. Furthermore, it<br />

argues that the OMOP provi<strong>de</strong>s a minimal set of elements to fulfill the requirements.<br />

It <strong>de</strong>monstrates that the proposed <strong>de</strong>sign in its current form is<br />

minimal by arguing that none of the parts can be removed without reducing<br />

the number of concurrent programming concepts that can benefit from it, and<br />

that removing any part would also result in unsatisfied requirements.<br />

6.2. Case Studies<br />

This section discusses the case studies covering Clojure agents, software transactional<br />

memory, and event-loop actors.<br />

In or<strong>de</strong>r to show that the OMOP simplifies the implementation of these<br />

concurrent programming concepts, it <strong>de</strong>monstrates how the OMOP is used<br />

to solve common implementation challenges. Tab. 6.1 recapitulates these challenges,<br />

which Sec. 3.3 discussed in more <strong>de</strong>pth.<br />

141

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!