Managing change in an OTS-aware requirements engineering approach

Cooper, Kendra M. L.; Chung, Lawrence

doi:10.1145/1082948.1082955

Cited by 5 publications

(3 citation statements)

References 7 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Architectural-level dependence has also been studied [70] using the architecture description languages (ADL) Rapide [44]. The softgoal interdependency graph (SIG) has been used to model non-functional requirements (NFR) [14] and algorithms have been explored to compare different meta-models (graphs) for reviewing the evolution of general models [2][21] [37] and/or UML diagrams [61].…”

Section: Therementioning

confidence: 99%

Formalizing the transition from requirements’ change to design change using an evolutionary traceability model

Wen

Tuffley

Dromey

2014

Innovations Syst Softw Eng

View full text Add to dashboard Cite

The ideal outcome when responding to changes in the functional requirements of a system is that we can quickly determine (1) where to make the change, (2) how the change affects the architecture of the existing system, (3) which components of the system are affected by the change, and (4) what behavioral changes will need to be made to the components (and their interfaces) that are affected by the change of requirements. If these facts are known, the impact of the change is entirely understood and therefore manageable. Moreover, a system is likely to undergo multiple changes over the course of its service life, so there is also a need to make a comprehensive record of these changes thus preserving the integrity of the system and potentially extending its service life. To this worthy end, a traceability model using behavior trees as a formal notation to represent functional requirements is proposed. This will address the issues cited above, revealing change impacts on different types of design constructs (documents) caused by the changes to the requirements. The proposed model introduces the concept of evolutionary design documents that record the change history of the designs. From these documents, any version of a design document as well as the difference between any two versions can be reviewed, thus affording the desirable condition of full traceability. An important advantage of this model is that the major part of the procedure to generate these evolutionary design documents can be supported by automated tools making the method accessible for use in large-scale software and systems development projects.

show abstract

Section: Therementioning

confidence: 99%

Formalizing the transition from requirements’ change to design change using an evolutionary traceability model

Wen

Tuffley

Dromey

2014

Innovations Syst Softw Eng

View full text Add to dashboard Cite

show abstract

“…Softgoal Interdependency Graphs (SIGs) were introduced by , and have been used to represent quality attributes Yu, 2001, 2002;Cleland-Huang and Schmelzer, 2003;Cysneiros and do Prado Leite, 2004;Cleland-Huang et al, 2005) and architectural decisions (Chung et al, 1995Subramanian and Chung, 2003;Cooper and Chung, 2005;Ma et al, 2006). However, SIGs (and other similar models) can become quite difficult to read, and their complexity hampers their broader use by practicing architects.…”

Section: Introductionmentioning

confidence: 99%

Visualization and comparison of architecture rationale with semantic web technologies

López

Inostroza

Cysneiros

et al. 2009

Journal of Systems and Software

View full text Add to dashboard Cite

“…The BT approach also provides a systematic way to transform the natural language described user requirements into component-based designs, in contrast to approaches based on UML use case diagrams, PLUSS [42], or interdependency graphs (SIG) [43]. The transformation process follows three steps [1].…”

Section: The Behavior Tree Design Approachmentioning

confidence: 99%

“Integrare”, a Collaborative Environment for Behavior-Oriented Design

Wen

Colvin

Lin

et al.

Lecture Notes in Computer Science

View full text Add to dashboard Cite

In this paper, we introduce a new cooperative design and visualization environment, called "Integrare", which supports designers and developers in building dependable, component-based systems using a new behavior-oriented design method. This method has advantages in terms of its abilities to manage complexity, find defects and make checks of dependability. The environment integrates and unifies several tools that support multiple phases of the design process, allowing them to interact and exchange information, as well as providing efficient editing capabilities. It can help formalize individual natural language functional requirements as Behavior Trees. These trees can be composed to create an integrated tree-like view of all the formalized requirements. The environment manages complexity by allowing multiple users to work independently on requirements translation and tree editing in a collaborative mode. Once a design is constructed from the requirements, it can be visually simulated with respect to an underlying operational semantics, and formally verified by way of a model checker.

show abstract

Managing change in an OTS-aware requirements engineering approach

Cited by 5 publications

References 7 publications

Formalizing the transition from requirements’ change to design change using an evolutionary traceability model

Formalizing the transition from requirements’ change to design change using an evolutionary traceability model

Visualization and comparison of architecture rationale with semantic web technologies

“Integrare”, a Collaborative Environment for Behavior-Oriented Design

Contact Info

Product

Resources

About