Traceability and Communication of Requirements in Digital I & C Systems Development Project Report 2003

In 2004, the work has focused on providing a unified exposition on the issues studied and thereby facilitating a common approach to requirements handling, from their origins and through the different development phases. Emphasis has been put on the development of the TACO Traceability Model. The model supports understandability, communication and traceability by providing a common basis, in the form of a requirements change history, for different kinds of analysis and presentation of different requirements perspectives. Traceability is facilitated through the representation of requirements changes in terms of a change history tree built up by composition of instances of a number of change types, and by providing analysis on the basis of this representation. Much of the strength of the TACO Traceability Model is that it aims at forming the logic needed for formalising the activities related to change management and hence their further automation. The work was presented at the second TACO Industrial Seminar, which took place in Helsinki on the 8 of December 2004.

[1]  W. Royce Managing the development of large software systems: concepts and techniques , 2021, ICSE '87.

[2]  Edward H. Bersoff,et al.  Elements of Software Configuration Management , 1984, IEEE Transactions on Software Engineering.

[3]  Barry W. Boehm,et al.  A spiral model of software development and enhancement , 1986, Computer.

[4]  A. Berztiss,et al.  Requirements Engineering , 2002, J. Object Technol..

[5]  Alexander L. Wolf,et al.  Acm Sigsoft Software Engineering Notes Vol 17 No 4 Foundations for the Study of Software Architecture , 2022 .

[6]  Fletcher J. Buckley Configuration management : hardware, software, and firmware , 1993 .

[7]  Rogério de Lemos,et al.  On the safety analysis of requirements specifications for safety-critical software , 1995 .

[8]  Mary Shaw,et al.  Abstractions for Software Architecture and Tools to Support Them , 1995, IEEE Trans. Software Eng..

[9]  Terje Sivertsen A Case Study on the Formal Development of a Reactor Safety System , 1996, FME.

[10]  Kendall Scott,et al.  UML distilled - applying the standard object modeling language , 1997 .

[11]  Reidar Conradi,et al.  Version models for software configuration management , 1998, CSUR.

[12]  Ian Sommerville,et al.  Requirements Engineering: Processes and Techniques , 1998 .

[13]  Peter A. Lindsay,et al.  Supporting Fine-Grained Traceability in Software Development Environments , 1998, SCM.

[14]  Ivar Jacobson,et al.  The Unified Modeling Language User Guide , 1998, J. Database Manag..

[15]  Hossein Saiedian,et al.  Requirements engineering: making the connection between the software developer and customer , 2000, Inf. Softw. Technol..

[16]  Reidar Conradi,et al.  Software Architecture and Software Configuration Management , 2003, SCM.

[17]  Bente Anda,et al.  Towards an inspection technique for use case models , 2002, SEKE '02.

[18]  A.P.-J. Thunem Modelling of knowledge intensive computerised systems based on capability-oriented agent theory (COAT) , 2003, IEMC '03 Proceedings. Managing Technologically Driven Organizations: The Human Side of Innovation and Change (IEEE Cat. No.03CH37502).

[19]  Terje Sivertsen,et al.  Undefinedness vs. Underspecification in HALDEN ASL , 2004, Nord. J. Comput..