2016
DOI: 10.1002/spe.2463
|View full text |Cite
|
Sign up to set email alerts
|

Modelling a family of systems for crisis management with concern‐oriented reuse

Abstract: Summary Concern‐oriented reuse (CORE) proposes the concern as a new unit of model‐based reuse encapsulating software artefacts pertaining to a domain of interest that span multiple development phases and levels of abstraction. With CORE, a concern encapsulates multiple reusable features, while allowing its generic models to be customized to problem‐specific contexts. We report on our experience of designing a family of crisis management systems (CMS) with the help of reusable concern libraries. The collected m… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
4
0

Year Published

2018
2018
2022
2022

Publication Types

Select...
2
2

Relationship

0
4

Authors

Journals

citations
Cited by 4 publications
(4 citation statements)
references
References 35 publications
0
4
0
Order By: Relevance
“…This section presents a notable multi-language modelling paradigm in the software engineering community, Concern-Orientated Reuse (CORE) [44,45]. A Multi-Language…”
Section: Multi-language Modelling Environment (Core)mentioning
confidence: 99%
See 1 more Smart Citation
“…This section presents a notable multi-language modelling paradigm in the software engineering community, Concern-Orientated Reuse (CORE) [44,45]. A Multi-Language…”
Section: Multi-language Modelling Environment (Core)mentioning
confidence: 99%
“…The usage interface defines how a customized concern may eventually be used [45]. It specifies the design structure (structural language), behaviour (behavioural language), and intentions (intentional language) that the concern provides to the reusing application.…”
Section: Usage Interfacementioning
confidence: 99%
“…WeaFQAs was chosen because it follows the classical framework for SPL and incorporates additional requirements that can be found in current complex projects. Results of this work encompass from simpler SPLs [4,52] to complex SPL processes like WeaFQAs or the Concern-Oriented Reuse (CORE) approach [1].…”
Section: Spl Tools Roadmapmentioning
confidence: 99%
“…Alternatively, some approaches to AOM rely on generating code targeting an aspect-oriented language (like AspectJ), and then rely on weaver provided by the target language to deal with crosscutting aspects [76]. Some approaches to AOM are related to a systematic identification of early aspects -already in the requirements and design phases -which then need to be expressed in notations for requirements, architecture and design [77,78]. In our case, advices are expressed either programmatically or using model management languages.…”
Section: Aspect-oriented Modellingmentioning
confidence: 99%