Tool support for generation and validation of traces between requirements and architecture

Göknil, Arda; Kurtev, Ivan; Berg, Klaas van den

doi:10.1145/1814392.1814398

Cited by 19 publications

(13 citation statements)

References 21 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…By providing change alternatives with impact prediction we determine some of the false positive impacts that usually occur in the industrial tools. Once the requirements engineer analyzes the impact of a change in the requirements model with our approach, by using traces between requirements and architecture [35,37] the requirements engineer/the software architect can identify the impact of this change in the software architecture.…”

Section: Resultsmentioning

confidence: 99%

Change impact analysis for requirements: A metamodeling approach

Göknil

Kurtev²,

Berg

et al. 2014

Information and Software Technology

Self Cite

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

Section: Resultsmentioning

confidence: 99%

Change impact analysis for requirements: A metamodeling approach

Göknil

Kurtev²,

Berg

et al. 2014

Information and Software Technology

Self Cite

View full text Add to dashboard Cite

show abstract

“…Little support for evolution is provided. Preliminary work on the semantics of traces between requirements and architecture has been proposed by Goknil et al [2]. Our work is similar to Könemann's [4] with respect to explicitly considering design decisions as first-class entities, but Könemann gives no hint on how to exploit this information.…”

Section: Related Work Outlookmentioning

confidence: 97%

Leveraging Design Decisions in Evolving Systems

Küster

Klatt

2012

Softwaretechnik-Trends

View full text Add to dashboard Cite

“…In our previous work [7] [10], we already give a detailed description of the verification of functional requirements since we also use the verification output (i.e., execution trace and counter example) to generate traces between requirements and architecture. In this section, we revisit the verification employing the Maude model checker (Figure 4).…”

Section: Verification Of Functional Requirementsmentioning

confidence: 99%

“…We employ behavioral semantics for a part of AADL [19] expressed in rewriting logic supported by the Maude language and tools [3]. Having the formal semantics makes the AADL models executable and enables the formal verification of functional requirements on the architecture, which is also employed in our previous work [7] [10] to generate traces between requirements and architecture. The verification uses the discrete event simulation, which introduces the notion of events, states, and state space.…”

Section: Introductionmentioning

confidence: 99%

A rule-based approach for evolution of AADL models based on changes in functional requirements

Göknil

Kurtev

Berg

2016

Proccedings of the 10th European Conference on Software Architecture Workshops

Self Cite

View full text Add to dashboard Cite

The increasing complexity of software systems makes change management costly and time consuming. To ensure the costeffective system longevity and endurance, it is crucial to apply change management in the early stages of software development. In this paper, we introduce a rule-based approach to make software architecture evolving based on counter examples provided by a model checker for violated, changing functional requirements. The approach works on software architecture in AADL and is based on verifying functional requirements using Maude model checker. Our goal is to provide guidelines to the architect about potential changes. Using an industrial example, we show how our approach helps in determining changes to produce a new version of the architecture.

show abstract

Tool support for generation and validation of traces between requirements and architecture

Cited by 19 publications

References 21 publications

Change impact analysis for requirements: A metamodeling approach

Change impact analysis for requirements: A metamodeling approach

Leveraging Design Decisions in Evolving Systems

A rule-based approach for evolution of AADL models based on changes in functional requirements

Contact Info

Product

Resources

About