Concurrent object-oriented development with behavioral design patterns
Benjamin Morandi, Scott West, Sebastian Nanz, Hassan Gomaa

TL;DR
This paper presents a systematic approach to map UML-based concurrent designs annotated with behavioral patterns to concurrent object-oriented code using SCOOP, simplifying development and reducing errors.
Contribution
It introduces a method to translate UML models with behavioral patterns into SCOOP-based implementations, enhancing correctness and easing concurrent application development.
Findings
Successful implementation of an ATM system using the proposed method
Elimination of data races due to SCOOP's guarantees
Systematic mapping improves development efficiency
Abstract
The development of concurrent applications is challenging because of the complexity of concurrent designs and the hazards of concurrent programming. Architectural modeling using the Unified Modeling Language (UML) can support the development process, but the problem of mapping the model to a concurrent implementation remains. This paper addresses this problem by defining a scheme to map concurrent UML designs to a concurrent object-oriented program. Using the COMET method for the architectural design of concurrent object-oriented systems, each component and connector is annotated with a stereotype indicating its behavioral design pattern. For each of these patterns, a reference implementation is provided using SCOOP, a concurrent object-oriented programming model. We evaluate this development process using a case study of an ATM system, obtaining a fully functional implementation based…
Peer Reviews
No public reviews on file for this paper yet. If you reviewed it on a platform where reviews are public (OpenReview, ICLR, NeurIPS, ICML), you can paste yours below so the community can read it here.
Videos
No videos yet. Explain this paper in a talk, walkthrough, or lecture? Add one.
