Design patterns: elements of reusable object-oriented software
Design patterns: elements of reusable object-oriented software
Software architecture: perspectives on an emerging discipline
Software architecture: perspectives on an emerging discipline
Pattern-oriented software architecture: a system of patterns
Pattern-oriented software architecture: a system of patterns
Object-oriented software construction (2nd ed.)
Object-oriented software construction (2nd ed.)
Designing Concurrent, Distributed, and Real-Time Applications with Uml
Designing Concurrent, Distributed, and Real-Time Applications with Uml
Pattern-Oriented Software Architecture: Patterns for Concurrent and Networked Objects
Pattern-Oriented Software Architecture: Patterns for Concurrent and Networked Objects
Software Architecture in Practice
Software Architecture in Practice
Modeling behavioral design patterns of concurrent objects
Proceedings of the 28th international conference on Software engineering
Software Architecture: Foundations, Theory, and Practice
Software Architecture: Foundations, Theory, and Practice
A modular scheme for deadlock prevention in an object-oriented programming model
ICFEM'10 Proceedings of the 12th international conference on Formal engineering methods and software engineering
Software Modeling and Design: UML, Use Cases, Patterns, and Software Architectures
Software Modeling and Design: UML, Use Cases, Patterns, and Software Architectures
Design of an Empirical Study for Comparing the Usability of Concurrent Programming Languages
ESEM '11 Proceedings of the 2011 International Symposium on Empirical Software Engineering and Measurement
| Hi-index | 0.00 |
Architectural modeling using the Unified Modeling Language (UML) can support the development of concurrent applications, but the problem of mapping the model to a concurrent implementation remains. This paper defines 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. Given the strong execution guarantees of the SCOOP model, which is free of data races by construction, this development method eliminates a source of intricate concurrent programming errors.