Computer
An overview of Manifold and its implementation
Concurrency: Practice and Experience
Gamma and the chemical reaction model: ten years after
Coordination programming
The unified software development process
The unified software development process
Requirements engineering: a roadmap
Proceedings of the Conference on The Future of Software Engineering
Requirements engineering in the year 00: a research perspective
Proceedings of the 22nd international conference on Software engineering
2nd international workshop on living with inconsistency
ICSE '01 Proceedings of the 23rd International Conference on Software Engineering
From software requirements to architectures
ICSE '01 Proceedings of the 23rd International Conference on Software Engineering
Software Architectures and Coordination Models
The Journal of Supercomputing
Coordination of massively concurrent activities
Coordination of massively concurrent activities
Automated Check of Architectural Models Consistency Using SPIN
Proceedings of the 16th IEEE international conference on Automated software engineering
| Hi-index | 0.00 |
Software coordination models and languages describe how agents, resources and processes work together to implement a software system. One of their limitations is that they are used late in the software development and they are not integrated in a typical software development process.What we claim, with our research, is that if coordination becomes explicit and formalized as soon as possible in the life cycle, then it is possible to create coordinated-aware software systems. Moreover, it is possible to verify the adequacy of a Software Architecture model (or of the code itself) with respect to these dynamic constraints as well as refine or disambiguate coordination requirements themselves.In previous work, we presented a UML-based development process to elicit, describe, analyze and validate system coordination properties that might be then specified with a suitable coordination language. In this general picture, the aim of this paper is to implement the first step, i.e., to elicit and formalize coordination policies. We propose a five steps approach that incrementally identifies the elements to be coordinated (i.e., static coordination) and how these entities may be coordinated (i.e., dynamic coordination).