Requirements Interdependencies: State of the Art and Future Challenges

Dahlstedt, Åsa G.; Persson, Anne

doi:10.1007/3-540-28244-0_5

Cited by 84 publications

(118 citation statements)

References 21 publications

Supporting

Mentioning

107

Contrasting

Unclassified

Order By: Relevance

“…Inconsistency candidates include groups of requirements that are either indicated as being conflicting or similar [12], or that include inconsistencies in requirements specifications such as:…”

Section: Interaction Analysismentioning

confidence: 99%

Requirements engineering within a large-scale security-oriented research project: lessons learned

Gürses

Seguran²,

Zannone

2011

Requirements Eng

View full text Add to dashboard Cite

Requirements engineering has been recognized as a fundamental phase of the software engineering process. Nevertheless, the elicitation and analysis of requirements are often left aside in favor of architecture-driven software development. This tendency, however, can lead to issues that may affect the success of a project. This paper presents our experience gained in the elicitation and analysis of requirements in a large-scale security-oriented European research project, which was originally conceived as an architecture-driven project. In particular, we illustrate the challenges that can be faced in large-scale research projects and consider the applicability of existing best practices and off-the-shelf methodologies with respect to the needs of such projects. We then discuss how those practices and methods can be integrated into the requirements engineering process and possibly improved to address the identified challenges. Finally, we summarize the lessons learned from our experience and the benefits that a proper requirements analysis can bring to a project.

show abstract

Section: Interaction Analysismentioning

confidence: 99%

Requirements engineering within a large-scale security-oriented research project: lessons learned

Gürses

Seguran²,

Zannone

2011

Requirements Eng

View full text Add to dashboard Cite

show abstract

“…Dahlstedt and Persson [21] address requirements relations (they call a relation an ''interdependency'') from a traceability perspective. They give an overview of requirements relations research and present a model of fundamental relation types.…”

Section: Requirements Relationsmentioning

confidence: 99%

“…Zhang et al [96] conducted a case study to evaluate the usefullness and applicability of existing dependency types given in Dahlstedt's dependency model (D-model) [21] and Pohl's dependency model (P-model) [75] in change propagation with a real-world industry project. The findings in the conducted case study are (1) the definitions of some dependency types are confusing; (2) some dependency types from literature are not common and seldom found in real projects; and (3) in existing dependency models, five dependency types propagate changes, but their definitions need to be clarified [96].…”

Section: Requirements Relationsmentioning

confidence: 99%

Change impact analysis for requirements: A metamodeling approach

Göknil

Kurtev²,

Berg

et al. 2014

Information and Software Technology

View full text Add to dashboard Cite

a b s t r a c tContext: Following the evolution of the business needs, the requirements of software systems change continuously and new requirements emerge frequently. Requirements documents are often textual artifacts with structure not explicitly given. When a change in a requirements document is introduced, the requirements engineer may have to manually analyze all the requirements for a single change. This may result in neglecting the actual impact of a change. Consequently, the cost of implementing a change may become several times higher than expected. Objective: In this paper, we aim at improving change impact analysis in requirements by using formal semantics of requirements relations and requirements change types. Method: In our previous work we present a requirements metamodel with commonly used requirements relation types and their semantics formalized in first-order logic. In this paper the classification of requirements changes based on structure of a textual requirement is provided with formal semantics. The formalization of requirements relations and changes is used for propagating proposed changes and consistency checking of proposed changes in requirements models. The tool support for change impact analysis in requirements models is an extension of our Tool for Requirements Inferencing and Consistency Checking (TRIC). Results: The described approach for change impact analysis helps in the elimination of some false positive impacts in change propagation, and enables consistency checking of changes. Conclusion: We illustrate our approach in an example which shows that the formal semantics of requirements relations and change classification enables change alternatives to be proposed semi-automatically, the reduction of some false positive impacts and contradicting changes in requirements to be determined.

show abstract

“…Requirements relations influence a number of development activities and decisions made during software development, for example release planning, requirements validation, change impact analysis, testing, and requirements reuse [8]. In this respect, these activities may produce deficient results.…”

Section: Deficiencies Of Current Approachesmentioning

confidence: 99%

“…Dahlstedt and Persson [8] address requirements relations (they call a relation an "interdependency") from a traceability perspective. They give an overview of requirements relations research and present a model of fundamental relation types.…”

Section: Requirements Relationsmentioning

confidence: 99%

Semantics of trace relations in requirements models for consistency checking and inferencing

et al. 2009

View full text Add to dashboard Cite

Requirements traceability is the ability to relate requirements back to stakeholders and forward to corresponding design artifacts, code, and test cases. Although considerable research has been devoted to relating requirements in both forward and backward directions, less attention has been paid to relating requirements with other requirements. Relations between requirements influence a number of activities during software development such as consistency checking and change management. In most approaches and tools, there is a lack of precise definition of requirements relations. In this respect, deficient results may be produced. In this paper, we aim at formal definitions of the relation types in order to enable reasoning about requirements relations. We give a requirements metamodel with commonly used relation types. The semantics of the relations is provided with a formalization in first-order logic. We use the formalization for consistency checking of relations and for inferring new relations. A tool has been built to support both reasoning activities. We illustrate our approach in an example which shows that the formal semantics of relation types enables new relations to be inferred and contradicting relations in requirements documents to be determined.

show abstract

Requirements Interdependencies: State of the Art and Future Challenges

Cited by 84 publications

References 21 publications

Requirements engineering within a large-scale security-oriented research project: lessons learned

Requirements engineering within a large-scale security-oriented research project: lessons learned

Change impact analysis for requirements: A metamodeling approach

Semantics of trace relations in requirements models for consistency checking and inferencing

Contact Info

Product

Resources

About