Requirements and Systems Architecture Interaction in a Prototypical Project: Emerging Results

Ferrari, Remo; Sudmann, Oliver; Henke, Christian; Geisler, Jens; Schäfer, Wilhelm; Madhavji, Nazim H.

doi:10.1007/978-3-642-14192-8_4

Cited by 5 publications

(4 citation statements)

References 4 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…The influence of existing architecture and reusable elements on requirements has been confirmed in several studies, such as in Ferrari et al [17], or Boer et al [4]. However, besides observing this influence, they do not provide an approach to utilize architecture or its elements for requirements engineering.…”

Section: Related Workmentioning

confidence: 98%

How the understanding of the effects of design decisions informs requirements engineering

Durdik

Koziolek

Reussner

2013

2013 2nd International Workshop on the Twin Peaks of Requirements and Architecture (TwinPeaks)

View full text Add to dashboard Cite

Requirements are usually one of the main drivers for software architecture. Although current research acknowledges the opposite effects of design decisions on requirements engineering, it does not go beyond the general idea of their existence. The contribution of this paper lies in the explicit discussion of the effects of design decisions on requirements engineering. We define two types of design decisions and discuss their effect on requirements, and in particular on elicitation and prioritisation. Furthermore, we propose and demonstrate on an example two channels from architectural design to requirements that can be used to drive requirement elicitation and prioritization. This is the base for a new approach where also the results of the quantitative analysis of the effects of requirements on architecture are fed back into the requirements process.

show abstract

Section: Related Workmentioning

confidence: 98%

How the understanding of the effects of design decisions informs requirements engineering

Durdik

Koziolek

Reussner

2013

2013 2nd International Workshop on the Twin Peaks of Requirements and Architecture (TwinPeaks)

View full text Add to dashboard Cite

show abstract

“…Studies in [14,13,6] confirmed influence of existing software architecture on the requirements engineering, however they do not consider using this influence for the requirement elicitation. The idea to use architecture as a basis for further requirement discovery and determination of the alternative design solutions is presented in [16].…”

Section: Related Workmentioning

confidence: 99%

An architecture-centric approach for goal-driven requirements elicitation

Durdik

2011

Proceedings of the 19th ACM SIGSOFT Symposium and the 13th European Conference on Foundations of Software Engineering

View full text Add to dashboard Cite

Software system development typically starts from a requirement specification followed by stepwise refinement of available requirements while transferring them into the system architecture. However, the granularity and the amount of requirements to be elicited for a successful architectural design are not well understood. This paper proposes a process concept to support system development with the help of an architecture-centric approach for goal-driven requirements elicitation. The process focuses on multiple quality dimensions, such as performance, reliability and scalability, and at the same time shall reduce costs and risks through early decision evaluation. The main contribution of this paper is a novel process where not only requirements can drive architectural design, but also architectural design can selectively drive requirement elicitation with the help of hypotheses connected to the selected architectural solutions. The paper concludes with a discussion on its possible empirical validation.

show abstract

“…According to Ferrari et al [6], tighter integration of software architecture to requirements engineering is necessary across different subsystems due to the strong influence that architecture has on requirements engineering decisions. The lower two levels of our proposed model support such a tight integration by illustrating the relations already in the RE content model.…”

Section: Requirements Engineering Content Modelmentioning

confidence: 99%

A Requirements Engineering content model for Cyber-Physical Systems

Penzenstadler

Eckhardt

2012

2012 Second IEEE International Workshop on Requirements Engineering for Systems, Services, and Systems-of-Systems (RESS)

View full text Add to dashboard Cite

The development of highly distributed Systems of Systems (SoS) poses a big challenge on the whole development process of such systems. Especially in Requirements Engineering, one has to cope with the resulting variety of stakeholders and their multitude of different and possibly contradictory goals. This is challenging for requirements elicitation, documentation, and management, especially with regard to communication and consistency.One promising means to this challenge is to use an artefactoriented requirements engineering approach that puts emphasis on artefacts and dependencies rather than dictating processes and methods for creating the artefacts.In this paper, we present a content model that facilitates collaboration between stakeholders from 30 companies in the research project ARAMiS and is used on a SoS; more specifically, on a so-called Cyber-Physical System that spans a variety of application domains. The content model was elaborated iteratively on the basis of models from preliminary work and in discussion with partner representatives. It is now under evaluation by the 30 project partners, so we present a preview of the evaluation.

show abstract

Requirements and Systems Architecture Interaction in a Prototypical Project: Emerging Results

Cited by 5 publications

References 4 publications

How the understanding of the effects of design decisions informs requirements engineering

How the understanding of the effects of design decisions informs requirements engineering

An architecture-centric approach for goal-driven requirements elicitation

A Requirements Engineering content model for Cyber-Physical Systems

Contact Info

Product

Resources

About