TY - CHAP
T1 - Requirements tracing to support change in dynamically adaptive systems
AU - Welsh, Kristopher
AU - Sawyer, Peter
PY - 2009
Y1 - 2009
N2 - [Context and motivation] All systems are susceptible to the need for change, with the desire to operate in changeable environments driving the need for software adaptation. A Dynamically Adaptive System (DAS) adjusts its behaviour autonomously at runtime in order to accommodate changes in its operating environment, which are anticipated in the system?s requirements specification. [Question/Problem] In this paper, we argue that Dynamic Adaptive Systems? requirements specifications are more susceptible to change than those of traditional static systems. We propose an extension to i* strategic rationale models to aid in changing a DAS. [Principal Ideas/Results] By selecting some of the types of tracing proposed for the most complex systems and supporting them for DAS modelling, it becomes possible to handle change to a DAS? requirements efficiently, whilst still allowing artefacts to be stored in a Requirements Management tool to mitigate additional complexity. [Contribution] The paper identifies different classes of change that a DAS? requirements may be subjected to, and illustrates with a case study how additional tracing information can support the making of each class of change.
AB - [Context and motivation] All systems are susceptible to the need for change, with the desire to operate in changeable environments driving the need for software adaptation. A Dynamically Adaptive System (DAS) adjusts its behaviour autonomously at runtime in order to accommodate changes in its operating environment, which are anticipated in the system?s requirements specification. [Question/Problem] In this paper, we argue that Dynamic Adaptive Systems? requirements specifications are more susceptible to change than those of traditional static systems. We propose an extension to i* strategic rationale models to aid in changing a DAS. [Principal Ideas/Results] By selecting some of the types of tracing proposed for the most complex systems and supporting them for DAS modelling, it becomes possible to handle change to a DAS? requirements efficiently, whilst still allowing artefacts to be stored in a Requirements Management tool to mitigate additional complexity. [Contribution] The paper identifies different classes of change that a DAS? requirements may be subjected to, and illustrates with a case study how additional tracing information can support the making of each class of change.
UR - https://link.springer.com/chapter/10.1007%2F978-3-642-02050-6_6
U2 - 10.1007/978-3-642-02050-6_6
DO - 10.1007/978-3-642-02050-6_6
M3 - Chapter
SN - 9783642020490
T3 - Lecture Notes in Computer Science
SP - 59
EP - 73
BT - Requirements Engineering: Foundation for Software Quality
PB - Springer
ER -