Object-oriented software engineering
Object-oriented software engineering
Writing Effective Use Cases
DREP: A Requirements Engineering Process for Dependable Reactive Systems
Methods, Models and Tools for Fault Tolerance
Checking the correspondence between UML models and implementation
RV'10 Proceedings of the First international conference on Runtime verification
Requirements modeling with the aspect-oriented user requirements notation (AoURN): a case study
Transactions on aspect-oriented software development VII
Transactions on aspect-oriented software development VII
Aspect-oriented development using protocol modeling
Transactions on aspect-oriented software development VII
Using VCL as an aspect-oriented approach to requirements modelling
Transactions on aspect-oriented software development VII
Modeling the car crash crisis management system using HiLA
Transactions on aspect-oriented software development VII
Aspect-oriented design with reusable aspect models
Transactions on aspect-oriented software development VII
Discovery of stable abstractions for aspect-oriented composition in the car crash management domain
Transactions on aspect-oriented software development VII
Requirements modeling with the aspect-oriented user requirements notation (AoURN): a case study
Transactions on aspect-oriented software development VII
Transactions on aspect-oriented software development VII
Aspect-oriented development using protocol modeling
Transactions on aspect-oriented software development VII
Using VCL as an aspect-oriented approach to requirements modelling
Transactions on aspect-oriented software development VII
Modeling the car crash crisis management system using HiLA
Transactions on aspect-oriented software development VII
Aspect-oriented design with reusable aspect models
Transactions on aspect-oriented software development VII
Discovery of stable abstractions for aspect-oriented composition in the car crash management domain
Transactions on aspect-oriented software development VII
Aspect-oriented model development at different levels of abstraction
ECMFA'11 Proceedings of the 7th European conference on Modelling foundations and applications
Guiding architects in selecting architectural evolution alternatives
ECSA'11 Proceedings of the 5th European conference on Software architecture
Service-oriented architecture modeling: bridging the gap between structure and behavior
Proceedings of the 14th international conference on Model driven engineering languages and systems
Clustering with proximity knowledge and relational knowledge
Pattern Recognition
Comparing six modeling approaches
MODELS'11 Proceedings of the 2011th international conference on Models in Software Engineering
A commutative model composition operator to support software adaptation
ECMFA'12 Proceedings of the 8th European conference on Modelling Foundations and Applications
Aspect-oriented model-driven code generation: A systematic mapping study
Information and Software Technology
EA-Analyzer: automating conflict detection in a large set of textual aspect-oriented requirements
Automated Software Engineering
Assessing composition in modeling approaches
Proceedings of the CMA 2012 Workshop
A causal model to predict the effect of business process evolution on quality of service
Proceedings of the 9th international ACM Sigsoft conference on Quality of software architectures
Incremental software design modelling
CASCON '13 Proceedings of the 2013 Conference of the Center for Advanced Studies on Collaborative Research
Hi-index | 0.00 |
The intent of this document is to define a common case study for the aspect-oriented modeling research community. The domain of the case study is crisis management systems, i.e., systems that help in identifying, assessing, and handling a crisis situation by orchestrating the communication between all parties involved in handling the crisis, by allocating and managing resources, and by providing access to relevant crisis-related information to authorized users. This document contains informal requirements of crisis management systems (CMSs) in general, a feature model for a CMS product line, use case models for a car crash CMS (CCCMS), a domain model for the CCCMS, an informal physical architecture description of the CCCMS, as well as some design models of a possible object-oriented implementation of parts of the CCCMS backend. AOM researchers who want to demonstrate the power of their AOM approach or technique can hence apply the approach at the most appropriate level of abstraction.