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.1. Evaluation Criteria<br />

Concurrent Programming Concepts benefit from the OMOP To <strong>de</strong>monstrate<br />

the benefits of the OMOP, this chapter argues that it simplifies the<br />

implementation of supported concurrent programming concepts by solving<br />

the problems implementers face when they use common ad hoc approaches.<br />

This discussion relies on the problems i<strong>de</strong>ntified in Sec. 3.3. For each of the<br />

problems, it illustrates how it is solved using the OMOP and shows the improvements<br />

over existing ad hoc solutions. This comparison shows the benefits<br />

of the OMOP by showing that it solved the implementation challenges<br />

language implementers are facing when they target today’s VMs.<br />

The evaluation discusses how the OMOP addresses these problems as part<br />

of three case studies in Sec. 6.2. These case studies are the implementation<br />

of Clojure agents, an STM system, and event-loop actors. They are chosen<br />

to cover all of the i<strong>de</strong>ntified problems and all mechanisms provi<strong>de</strong>d by the<br />

OMOP. Furthermore, the characteristics of the three implemented concurrent<br />

programming concepts are sufficiently different from each other to discuss<br />

the OMOP and the problems it addresses from different angles. T<strong>here</strong>fore,<br />

the case studies provi<strong>de</strong> the necessary foundation to fully evaluate the OMOP<br />

and its benefits.<br />

Fulfillment of Requirements Sec. 3.4 i<strong>de</strong>ntified concrete requirements as a<br />

foundation for the <strong>de</strong>sign of the OMOP. This evaluation discusses these requirements<br />

as part of the three case studies in Sec. 6.2. For each case study<br />

the section evaluates which mechanisms the case study requires and how it<br />

maps onto the OMOP. Furthermore, to <strong>de</strong>monstrate the fulfillment of the requirements<br />

the discussion inclu<strong>de</strong>s the evaluation criteria Sec. 3.4 stated for<br />

each of the requirements.<br />

To complete the discussion of how the OMOP fulfills its requirements,<br />

Sec. 6.3 discusses the concepts from which the requirements were initially<br />

<strong>de</strong>rived. For each of these concepts, it evaluates the <strong>de</strong>gree to which it is supported<br />

by the OMOP. The evaluation differentiates between concepts w<strong>here</strong><br />

the main aspects are covered and concepts w<strong>here</strong> only some aspects are supported<br />

by the OMOP to assess the extent to which the concepts benefit. Even if<br />

only some of the concept’s aspects are supported, the benefits are substantial,<br />

since the OMOP addresses common implementation challenges.<br />

Applicability Sec. 6.4 assesses the applicability of the OMOP by showing<br />

that its use does not increase the implementation size for the supported concurrent<br />

programming concepts.<br />

139

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

Saved successfully!

Ooh no, something went wrong!