COSMOD-RE: Supporting the Co-Design of Requirements and Architectural Artifacts

Pohl, Klaus; Sikora, Ernst

doi:10.1109/re.2007.25

Cited by 21 publications

(9 citation statements)

References 8 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…However, the model does not distinguish between the modes of specification for the requirements and their contents. The Scenario and Goal based System Development Method (COSMOD-RE) offers a goal-and scenario-based method to support the hardware/ software co-design in the development of embedded systems [16]. The method is based on a definition of requirements and design artifacts, describing six levels of abstraction that increasingly concretize the requirements and assign them to the functional groups and afterward to the precise software components.…”

Section: Related Workmentioning

confidence: 99%

“…The RDMod separates requirements into artifacts and is a scheme for the concretization of requirements that defines how the requirements incrementally become more detailed with respect to the levels of abstraction across the development phases and how they receive technical features and characteristics [7,[14][15][16][17]. The artifacts are structured in the RDMod and get modified by the RE activities [5].…”

Section: Structure Of the Requirements Data Modelmentioning

confidence: 99%

“…In the iterative-incremental development [16], the artifacts, including requirements and development information and that being created in the iteration i, have a significant impact on the artifacts of the next iterations (i ? 1), up to the final iteration n. In each step, the artifacts comprising the requirements, as well as the artifacts comprising the development information, which both have been created in former iterations, are supplemented, detailed, or revised.…”

Section: Structure Of the Requirements Data Modelmentioning

confidence: 99%

“…Clearly, not every stakeholder's needs and wishes could be considered. The aim of the requirements negotiation is the identification of conflicts, analysis of possible causes, closure of conflicts with suitable strategies and the documentation of the closure if conflicts arise, including the reasons for them [16,27].…”

Section: Conflict Detection and Resolutionmentioning

confidence: 99%

See 3 more Smart Citations

A requirements data model for product service systems

et al. 2012

View full text Add to dashboard Cite

Product service systems (PSS) are bundles of physical technological elements and service elements that are integrated to solve customer problems. In practice, most components of PSS are developed independently from each other, which leads to problems with coordination of development activities and integration of PSS components. Therefore, an integrated requirements engineering for PSS is needed that deals with the involvement of developers from product engineering, software engineering, and service engineering, as well as the inherent complexity of the PSS and the development process. In a case study with the development department of a PSS provider, we analyzed requirements documents and conducted expert interviews. We identified problems in the development, for example, that requirements on different levels of abstraction are intermingled, rationales for requirements are missing, and the concretization of requirements is unclear.To solve these problems, we propose a requirements data model (RDMod) for requirements to PSS. An RDMod describes different types of requirements and the relations between them. Thus, it is a scheme for the concretization of the requirements, which especially addresses the problems of structuring the requirements, enabling traceability, and finding conflicts. We then used an analytical evaluation, a feature-based evaluation and a retrospective application with requirements analysts of the industry partner. In a joint workshop, we specified requirements for a PSS with the RDMod. In structured interviews, we analyzed the perceived advantages of the RDMod. The experts confirmed that the RDMod is applicable in their development and it provides a clear structure for the requirements and therefore helps overcoming the identified problems.

show abstract

Section: Related Workmentioning

confidence: 99%

Section: Structure Of the Requirements Data Modelmentioning

confidence: 99%

Section: Structure Of the Requirements Data Modelmentioning

confidence: 99%

Section: Conflict Detection and Resolutionmentioning

confidence: 99%

See 2 more Smart Citations

A requirements data model for product service systems

et al. 2012

View full text Add to dashboard Cite

show abstract

“…NFR Definition is performed in parallel with Functionality, Topology and Network Infrastructure Definition. Developing requirements and architectural artifacts in parallel has already been addressed in the literature [13]. After an EIS architecture has been defined, it should be evaluated, most commonly using simulation.…”

Section: Eis Architecture Design Tasksmentioning

confidence: 99%

Evaluating software architecture in a model-based approach for enterprise information system design

Tsadimas

Νικολαϊδου

Anagnostopoulos

2010

Proceedings of the 2010 ICSE Workshop on Sharing and Reusing Architectural Knowledge

View full text Add to dashboard Cite

Enterprise information system architecture design is the process of defining and optimizing its structure (both software and hardware) to effectively support provided functionality. System architects are combining software and hardware vital components, usually defined by other stakeholders, and are dealing with both functional and non functional requirements. Alternative architecture solution evaluation is usually a part of the design process, aiming to determine if the defined requirements are satisfied. A model-based approach, constituted of discrete views, each of which facilitates a discrete design task, has been proposed, while Systems Modeling Language (SysML) has been adopted for the model representation. In this paper, emphasis is given on the Evaluation View, aiming at the exploration of alternative software and hardware combination scenarios proposed in other views. The view facilitates the management of simulation experiments and results and the verification of predefined requirements. A case study, where the proposed model-based design approach has been applied is also discussed.

show abstract