A survey of the use and documentation of architecture design rationale

Proceedings - 5th Working IEEE/IFIP Conference on Software Architecture, WICSA 2005

Volumn 2005, Issue , 2005, Pages 89-98

  Tang, Antony ^a   Babar, Muhammad Ali ^b   Gorton, Ian ^b   Han, Jun ^a  

^a SWINBURNE UNIVERSITY OF TECHNOLOGY   (Australia)

^b UNIVERSITY OF NEW SOUTH WALES   (Australia)

Author keywords

[No Author keywords available]

Indexed keywords

INFORMATION USE; PROBLEM SOLVING; PROGRAM DOCUMENTATION; SOFTWARE DESIGN;

DESIGN RATIONALE; SYSTEMATIC USE;

SOFTWARE ARCHITECTURE;

EID: 33746466265     PISSN: None     EISSN: None     Source Type: Conference Proceeding    
DOI: 10.1109/WICSA.2005.7     Document Type: Conference Paper

References (32)

1. IEEE Recommended Practice for Architectural Description of Software-Intensive Systems: IEEE Standard No. 1471-2000, Available at http://shop.ieec.org/store/.
2. L. Bass, P. Clements, and R. Kazman, Software Architecture in Practice. Boston: Addison Wesley, 2003.
3. J. Bosch, "Software Architecture: The Next Step," European Workshop on Software Architecture, pp, 2004.
4. P. Clements, F. Bachmann, L. Bass, D. Garlan, J. Ivers, R. Little, R. Nord, and J. Stafford, Documenting Software Architectures : Views and Beyond, Boston ed: Addison Wesley, 2002.
5. P. Clements, F. Bachmann, L. Bass, D. Garlan, j. Ivers, R. Little, R. Nord, and J. Stafford, Documenting Software Architectures: Views and Beyond: Addison-Wesley, 2002.
6. J. Conklin and M. L. Begeman, "gIBIS: A Hypertext Tool for Exploratory Policy Discussion," ACM Transactions on Office Information Systems, vol. 6, pp. 303-331, 1988.
7. B. Curtis, H. Krasner, and N. Iscoe, "A Field Study of the Software Design Process for Large Systems," Communications of the ACM, vol. 31, 1988.
8. A. Dutoit and B. Peach, "Rationale Management in Software Engineering," in Handbook of Software Engineering and Knowledge Engineering, 2000.
9. Dutoit A.H. and Peach B., "Rationale-Based Use Case Specification," Requirements Engineering, vol. 3, pp. 3-19, 2002.
10. T. R. Gruber and D. M. Russell, "Design Knowledge and Design Rationale: A Framework for Representing, Capture, and Use," Knowledge Systems Laboratory, Standford University, California, USA, California KSL 90-45, 1991.
11. M. Keil, H. J. Smith, S. Pawlowski, and L. Jin, '"Why didn't somebody tell me?': climate, information asymmetry, and bad news about troubled projects," SIGMIS Database, vol. 35, pp. 65-84, 2004.
12. B. Kitchenham and S. L. Pfleeger, "Principles of Survey Research, Parts 1 to 6," Software Engineering Notes, 2001-2002.
13. W. Kunz and H. W. J. Rittet, "Issues As Elements of Information Systems." Institute of Urban & Regional Development, University of California, Berkeley, 1970.
14. N. Lassing, P. Bengtsson, J. Bosch, and H. V. Vliet, "Experience with ALMA: Architecture-Level Modifiability Analysis," Journal of Systems and Software, vol. 61, pp. 47-57, 2002.
15. J. Lee, "Extending the Potts and Bruns Model for Recording Design Rationale," 13th International Conference on Software Engineering, pp 114-125, 1991.
16. J. Lee, "Design Rationale Systems: Understanding the Issues," IEEE Expert, vol. 12, pp. 78-85, 1997.
17. J. Lee and K.-Y. Lai, "What's in Design Rationale?," Human-Computer Interaction, 1991.
18. A. MacLean, R. M. Young, V. M. E. Bellotti, and T. P. Moran, "Questions, Options, and Criteria: Elements of Design Space Analysis," Human-Computer Interaction, vol. 6, pp. 201-250, 1991.
19. R. McCall, "PHIBIS: Procedural Hierarchical Issue-Based Information Systems," Proc. Int'l. Congress on Planning and Design Theory, pp, 1987.
20. ObjectPlanet Inc., "Surveyor: Web-based Survey Application," 2002, http://www.sharewareconnection.com/surveyor.htm.
21. D. Parnas and P. Clements, "A rationale design process: How and why to fake it," IEEE Transactions on Software Engineering, vol. SE-12, pp. 251-257, 1985.
22. D. Parnas and P. Clements, "A Rationale Design Process: How and Why to Fake It," IEEE Transactions of Software Engineering, vol. 12, pp. 251-257, 1986.
23. D. E. Perry and A. L. Wolf, "Foundations for the Study of Software Architecture," ACM SIGSOFT, Software Engineering Notes, vol. 17, October 1992.
24. C. Potts, "ScenIC: A Strategy for Inquiry-Driven Requirements Determination," Proc. Int'l. Symposium on requirements engineering, pp 58-65, 1999.
25. C. Potts, K. Takahashi, and A. I. Anton, "Inquiry-Based Requirements Analysis," IEEE Software, vol. 11, pp. 21-32, 1994.
26. Potts C. and Burns G., "Recording the Reasons for Design Decisions," 10th International Conference on Software Engineering, pp 418-427, 1988.
27. B. Ramesh and B. Dhar, "Supporting Systems Development by Capturing Deliberations During Requirements Engineering," IEEE Transactions on Software Engineering, vol. 18, pp. 498-510, 1992.
28. B. Ramesh and M. Jarke, "Towards Reference Models for Requirements Traceability," IEEE Transactions on Software Engineering, vol. 27, pp. 58-93, 2001.
29. A. Tang and J. Han, "Architecture Rationalization: a Methodology for Architecture Verifiability, Traceability and Completeness," 12th Annual IEEE International Conference and Workshop on the Engineering of Computer Based Systems ECBS 2005, U.S.A., pp 135-144, 2005.
30. A. Tang, M.A. Barbar, I. Gorton, and J. Han, "A Survey of Architecture Design Rationale," Swinburne University of Technology SUTICT-TR2005.02, 2005.
31. J. Tyree and A. Akerman, "Architecture Decisions: Demystifying Architecture," IEEE SOFTWARE, vol. 22, pp. 19-27, 2005.
32. R. K. Yin, Case Study Research: Design and Methods, vol. 5, 3rd ed: Sage Publications, 2002.