A rationale-based architecture model for design traceability and reasoning

Journal of Systems and Software

Volumn 80, Issue 6, 2007, Pages 918-934

  Tang, Antony ^a   Jin, Yan ^a   Han, Jun ^a  

^a SWINBURNE UNIVERSITY OF TECHNOLOGY   (Australia)

Author keywords

Architecture design; Design rationale; Traceability

Indexed keywords

ARCHITECTURAL DESIGN; COMPUTER AIDED SOFTWARE ENGINEERING; LARGE SCALE SYSTEMS; LOGIC PROGRAMMING; SOFTWARE DESIGN; UNIFIED MODELING LANGUAGE;

DESIGN RATIONALE; ELECTRONIC PAYMENT SYSTEM; TRACEABILITY;

SOFTWARE ARCHITECTURE;

EID: 33947402169     PISSN: 01641212     EISSN: None     Source Type: Journal    
DOI: 10.1016/j.jss.2006.08.040     Document Type: Article

References (49)

1. Ali-Babar M., Gorton I., and Kitchenham B. A framework for supporting architecture knowledge and rationale management. Rationale Management in Software Engineering (2006), Springer 237-254
2. Bosch, J., 2004. Software architecture: the next step. In: Proceedings 1st European Workshop on Software Architecture (EWSA). St Andrews, UK. pp. 194-199.
3. Clements P., Bachmann F., Bass L., Garlan D., Ivers J., Little R., Nord R., and Stafford J. Documenting Software Architectures: Views and Beyond. first ed. (2002), Addison Wesley
4. Conklin, J., Begeman, M., 1988. gIBIS: a hypertext tool for exploratory policy discussion. In: Proceedings ACM Conference on Computer-Supported Cooperative Work. pp. 140-152.
5. Egyed, A., 2001. A scenario-driven approach to traceability. In: Proceedings 23rd International Conference on Software Engineering (ICSE). pp. 123-132.
6. Garlan, D., Allen, R., Ockerbloom, J., 1995. Architectural mismatch or why it's hard to build systems out of existing parts. In: Proceedings 17th International Conference on Software Engineering (ICSE). pp. 179-185.
7. Gotel, O.C.Z., Finkelstein, A.C.W., 1994. An analysis of the requirements traceability problem. In: Proceedings International Conference on Requirements Engineering (RE). pp. 94-101.
8. Gruber T., and Russell D. Generative design rationale: beyond the record and replay paradigm. In: Moran T., and Carroll J. (Eds). Design Rationale: Concepts, Techniques and Use (1996), Lawrence Erlbaum Associates 323-350 (Chapter 11)
9. Han J. Designing for increased software maintainability. Proceedings International Conference on Software Maintenance (1997), IEEE Computer Society Press 278-286
10. Han J. TRAM: a tool for requirements and architecture management. Proceedings 24th Australasian Computer Science Conference (2001), IEEE Computer Society Press, Gold Coast, Australia 60-68
11. Haumer, P., Pohl, K., Weidenhaupt, K., Jarke, M., 1999. Improving reviews by extended traceability. In: Proceedings 32nd Hawaii International Conference on System Sciences.
12. Herbsleb J.D., and Kuwana E. Preserving knowledge in design projects: what designers need to know?. Proceedings of the Conference on Human Factors in Computing Systems, April 24-29 (1993), ACM Press, New York 7-14
13. Hilliard, R., 2001. Viewpoint modeling. In: Proceedings of 1st ICSE Workshop on Describing Software Architecture with UML.
14. Hughes, T., Martin, C., 1998. Design traceability of complex systems. In: Proceedings 4th Annual Symposium on Human Interaction with Complex Systems. pp. 37-41.
15. IEEE, 1996. IEEE/EIA standard-industry implementation of ISO/IEC 12207:1995. Information Technology - Software Life Cycle Processes (IEEE/EIA Std 12207.0-1996).
16. IEEE, 1997. IEEE/EIA guide - industry implementation of ISO/IEC 12207:1995. Standard for Information Technology - Software Life Cycle Processes - Life Cycle Data (IEEE/EIA Std 12207.1-1997).
17. IEEE, 2000. IEEE Recommended Practice for Architecture Description of Software-Intensive System (IEEE Std 1471-2000).
18. Koning H., and van Vliet H. A method for defining IEEE Std 1471 viewpoints. The Journal of Systems and Software 79 (2005) 120-131
19. Kruchten, P., Lago, P., Vliet, H. v., Wolf, T., 2005. Building up and exploiting architectural knowledge. In: Proceedings 5th IEEE/IFIP Working Conference on Software Architecture.
20. Kunz W., and Rittel H. Issues as elements of information systems. Center for Planning and Development Research (1970), University of California, Berkeley
21. Lassing N., Rijsenbrij D., and Vliet H.V. Viewpoints on modifiability. International Journal of Software Engineering and Knowledge Engineering 11 4 (2001) 453-478
22. Lee, J., 1991. Extending the Potts and Bruns model for recording design rationale. In: 13th International Conference on Software Engineering. pp. 114-125.
23. Lee J. Design rationale systems: understanding the issues. IEEE Expert 12 3 (1997) 78-85
24. Lee J., and Lai K. What's in design rationale?. In: Moran T., and Carroll J. (Eds). Design Rationale: Concepts Techniques and Use (1996), Lawrence Erlbaum Associates 21-52 (Chapter 2)
25. Maclean A., Young R., Bellotti V., and Moran T. Questions, options and criteria: elements of design space analysis. In: Moran T., and Carroll J. (Eds). Design Rationale: Concepts Techniques and Use (1996), Lawrence Erlbaum Associates 53-106 (Chapter 3)
26. McCall R. PHI: a conceptual foundation for design hypermedia. Design Studies 12 1 (1991) 30-41
27. Nuseibeh, B., 2004. Crosscutting requirements. In: Proceedings 3rd International Conference on aspect-oriented software development. pp. 3-4.
28. Parnas D., and Clements P. A rational design process: how and why to fake it?. IEEE Transactions on Software Engineering 12 (1985) 251-257
29. Perry D.E., and Wolf A.L. Foundations for the study of software. ACM SIGSOFT 17 4 (1992) 40-52
30. Pinheiro, F.A.C., 2000. Formal and informal aspects of requirements tracing. In: Workshop em Engenharia de Requisitos. Brazil. pp. 1-21.
31. Pinheiro F.A.C., and Goguen J.A. An object-oriented tool for tracing requirements. IEEE Software 13 2 (1996) 52-64
32. Potts C. Supporting software design: integrating design methods and design rationale. In: Moran T., and Carroll J. (Eds). Design Rationale: Concepts, Techniques and Use (1996), Lawrence Erlbaum Associates 295-322 (Chapter 10)
33. Ramesh B., and Jarke M. Towards reference models for requirements traceability. IEEE Transactions on Software Engineering 27 1 (2001) 58-93
34. Roeller R., Lago P., and van Vliet H. Recovering architectural assumptions. The Journal of Systems and Software 79 (2005) 552-573
35. Savolainen, J., Kuusela, J., 2002. Framework for goal driven system design. In: Proceedings of the 26th Annual International Computer Software and Applications Conference (COMPSAC'02).
36. Shipman III F., and McCall R. Integrating different perspectives on design rationale: supporting the emergence of design rationale from design communication. Artificial Intelligence in Engineering Design, Analysis, and Manufacturing 11 2 (1997)
37. Simon H. The Sciences of the Artificial (1981), MIT Press
38. Smith, W., 1998. Best Practices: Application of DOORS to System Integration. QSS Quality Systems and Software, 1999 So. Bascom Av., Suite 700, Cambell, CA 950008, USA.
39. Spanoudakis G., Zisman A., Pérez-Miñana E., and Krause P. Rule-based generation of requirements traceability relations. The Journal of Systems and Software 72 2 (2004) 105-127
40. Sparx Systems, 2005. Enterprise Architect V5.00.767. .
41. Tang, A., 2005. An UML Profile Extension to Support Architecture Decision Traceability using Enterprise Architect. .
42. Tang, A., 2006. An AREL Tool for Traceability and Validation. .
43. Tang, A., Han, J., 2005. Architecture rationalization: a methodology for architecture verifiability, traceability and completeness. In: Proceedings 12th Annual IEEE International Conference and Workshop on the Engineering of Computer Based Systems (ECBS'05). IEEE, USA, pp. 135-144.
44. Tang A., Babar M., Gorton I., and Han J. A survey of architecture design rationale. The Journal of Systems and Software (2006) 10.1016/j.jss.2006.04.029
45. Tang A., Nicholson A., Jin Y., and Han J. Using Bayesian belief networks for change impact analysis in architecture design. The Journal of Systems and Software (2006) 10.1016/j.jss.2006.04.004
46. The Open Group, 2003. The Open Group Architecture Framework (v8.1 enterprise edition). .
47. Toulmin S. The Uses of Argument (1958), Cambridge University Press
48. Tyree J., and Akerman A. Architecture decisions: demystifying architecture. IEEE Software 22 2 (2005) 19-27
49. Watkins R., and Neal M. Why and how of requirements tracing. IEEE Software 11 4 (1994) 104-106