2018
DOI: 10.1007/s10270-018-0682-5
|View full text |Cite
|
Sign up to set email alerts
|

Model-integrating development of software systems: a flexible component-based approach

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1

Citation Types

0
4
0

Year Published

2019
2019
2023
2023

Publication Types

Select...
3
2
1

Relationship

1
5

Authors

Journals

citations
Cited by 7 publications
(4 citation statements)
references
References 20 publications
0
4
0
Order By: Relevance
“…We modeled this information using the pso:StatusInTime class included in the Publishing Status Ontology (PSO) 9 , which allows to describe the state (e.g. to be slow) that a system component (e.g.…”
Section: Examples From the Case Studymentioning
confidence: 99%
See 2 more Smart Citations
“…We modeled this information using the pso:StatusInTime class included in the Publishing Status Ontology (PSO) 9 , which allows to describe the state (e.g. to be slow) that a system component (e.g.…”
Section: Examples From the Case Studymentioning
confidence: 99%
“…A reference architecture for these adaptive systems has been proposed in [6], and a general and reusable infrastructure based on the classical control loop in control theory has been described in [7].More recently, the emerging field of Model Driven Engineering (MDE) [8] called Models@Run.time [4] extended this approach, investigating the use of different models to represent the knowledge required for managing the operations of software systems. The main benefit of Models@Run.time is a unified high-level perspective of the observed systems, together with precise representations of the knowledge needed to drive their adaptation.Model-based adaptation raises new research challenges that have to be tackled [9]. In this work we mainly focus on two problems.…”
mentioning
confidence: 99%
See 1 more Smart Citation
“…Over the last decades, modeling activities have been applied across the whole life-cycle of complex softwareintensive systems to support all stakeholders involved in software development, mostly thanks to the use of abstractions -provided by general-purpose and domainspecific modeling languages -and separation of concerns. Modeling is continually requiring larger efforts and it is often indispensable in tackling the constantly increasing intrinsic complexity of such systems [13,15]. Owing to (i) the ever-increasing complexity of the problems that modelers are trying to solve, (ii) the growing number of stakeholders whose needs have to be addressed, and (iii) the increase in domain-specific modeling abstractions used by these stakeholders, modelers face higher and higher cognitive load.…”
Section: Introductionmentioning
confidence: 99%