TRAM: a tool for requirements and architecture management

Management of system requirements and system architectures is part of any software engineering project. But it is usually very tedious and error prone. In particular, managing the traceability between system requirements and system architectures is critical but difficult. The article introduces a tool, TRAM, for managing system requirements, system architectures and more importantly the traceability between them. Its primary design objective is "being practical" and ready for practitioners to use without much overhead. The issues discussed in the paper include an information model that underlies the capture of requirements, architectures and their traceability, a set of document templates implementing the information model, and the support tool.

[1]  Wolfgang Emmerich,et al.  Managing Standards Compliance , 1999, IEEE Trans. Software Eng..

[2]  Jun Han Experience with designing a requirements and architecture management tool , 2000, Proceedings International Conference on Software Methods and Tools. SMT 2000.

[3]  Jun Han A comprehensive interface definition framework for software components , 1998, Proceedings 1998 Asia Pacific Software Engineering Conference (Cat. No.98EX240).

[4]  Mary Shaw,et al.  Software architecture - perspectives on an emerging discipline , 1996 .

[5]  Stephen Fickas,et al.  Goal-Directed Requirements Acquisition , 1993, Sci. Comput. Program..

[6]  Naranker Dulay,et al.  Specifying Distributed Software Architectures , 1995, ESEC.

[7]  Paul Clements,et al.  Software Architecture in Practice: Addison-Wesley , 1998 .

[8]  Paul Clements,et al.  Software architecture in practice , 1999, SEI series in software engineering.

[9]  Michael Jackson,et al.  The World and the Machine , 1995, 1995 17th International Conference on Software Engineering.