Design decisions and design rationale in software architecture

Journal of Systems and Software

Volumn 82, Issue 8, 2009, Pages 1195-1197

  Babar, Muhammad Ali ^a   Lago, Patricia ^b  

^a UNIVERSITY OF LIMERICK   (Ireland)

^b VU UNIVERSITY AMSTERDAM   (Netherlands)

Author keywords

[No Author keywords available]

Indexed keywords

EID: 67949098848     PISSN: 01641212     EISSN: None     Source Type: Journal    
DOI: 10.1016/j.jss.2009.05.053     Document Type: Editorial

References (20)

1. Ali-Babar M., Gorton I., and Kitchenham B. A framework for supporting architecture knowledge and rationale management. In: Dutoit A.H., McCall R., Mistrik I., and Paech B. (Eds). Rationale Management in Software Engineering (2006), Springer 237-254
2. Bass L., Clements P., Nord R.L., and Stafford J. Capturing and using rationale for a software architecture. In: Dutoit A.H., McCall R., Mistrik I., and Paech B. (Eds). Rationale Management in Software Engineering (2006), Springer 275-292
3. Bosch, J., 2004, Software architecture: the next step. In: Proceedings of the First European Workshop on Software Architecture (EWSA), pp. 194-199.
4. Clements P., Bachmann F., Bass L., Garlan D., Ivers j., Little R., Nord R., and Stafford J. Documenting Software Architectures: Views and Beyond (2002), Addison-Wesley, USA
5. Dutoit A.H., and Paech B. Rationale-based use case specification. Requirements Engineering Journal 3 1 (2002) 3-19
6. IEEE, 2000. Recommended practices for architecture description of software-intensive systems. In: IEEE Std. 1471-2000.
7. Jansen, A., Bosch, J., 2005. Software architecture as a set of architectural design decisions. In: Proceedings of the Fifth Working IEEE/IFIP Conference on Software Architecture, pp. 109-120.
8. Kunz, W., Rittle, H. 1970. Issues as Elements of Information Systems. Institute of Urban and Regional Development, University of California, Berkeley, Calif., Working paper No. 131.
9. Kruchten, P., Lago, P., Vliet, H.V., 2006. Building up and Reasoning about Architecture Knowledge. In: Proceedings of the Second International Conference on Quality of Software Architectures, pp. 43-58.
10. Lee, J., 1991. Extending the Potts and Bruns model for recording design rationale. In: Proceedings of the 13th International Conference on Software Engineering, pp. 114-125.
11. Lee J., and Lai K.-Y. What's in design rationale?. Human-Computer Interaction 6 3-4 (1991) 251-280
12. MacLean A., Young R.M., Bellotti V.M.E., and Moran T.P. Questions, options, and criteria: elements of design space analysis. Human-Computer Interaction 6 3-4 (1991) 201-250
13. McCall, R., 1987. PHIBIS: Procedural hierarchical issue-based information systems. In: Proceedings of the 13th International Congress on Planning and Design Theory, pp. 17-22.
14. Parnas D., and Clements P. A rationale design process: how and why to fake it. IEEE Transactions of Software Engineering 12 2 (1986) 251-257
15. Perry D.E., and Wolf A.L. Foundations for the study of software architecture, ACM SIGSOFT. Software Engineering Notes 17 4 (1992) 40-52
16. Potts, C., 1999. ScenIC: A strategy for inquiry-driven requirements determination. In: Proceedings of the Symposium on Requirements Engineering, pp. 58-65.
17. Potts, C., Burns, G., 1988. Recording the reasons for design decisions. In: Proceedings of the 10th International Conference on Software Engineering, pp. 418-427.
18. Potts C., Takahashi K., and Anton A.I. Inquiry-based requirements analysis. IEEE Software 11 2 (1994) 21-32
19. Ramesh B., and Dhar B. Supporting systems development by capturing deliberations during requirements engineering. IEEE Transaction on Software Engineering 18 6 (1992) 498-510
20. Tyree J., and Akerman A. Architecture decisions: demystifying architecture. IEEE Software 22 2 (2005) 19-27