A Survey of the Use and Documentation of Architecture Design Rationale
暂无分享,去创建一个
Muhammad Ali Babar | Ian Gorton | Antony Tang | Jun Han | Jun Han | M. Babar | A. Tang | I. Gorton
[1] Matthias Jarke,et al. Toward Reference Models of Requirements Traceability , 2001, IEEE Trans. Software Eng..
[2] Colin Potts,et al. ScenIC: a strategy for inquiry-driven requirements determination , 1999, Proceedings IEEE International Symposium on Requirements Engineering (Cat. No.PR00188).
[3] Thomas P. Moran,et al. Questions, Options, and Criteria: Elements of Design Space Analysis , 1991, Hum. Comput. Interact..
[4] R. Henry,et al. Principles of survey research. , 2018, Family practice research journal.
[5] David Lorge Parnas,et al. A rational design process: How and why to fake it , 1986, IEEE Transactions on Software Engineering.
[6] Robert L. Nord,et al. Proceedings of the Working IEEE/IFIP Conference on Software Architecture , 2006 .
[7] Paul Clements,et al. Software architecture in practice , 1999, SEI series in software engineering.
[8] Jintae Lee,et al. What's in Design Rationale? , 1991, Hum. Comput. Interact..
[9] Kenji Takahashi,et al. Inquiry-based requirements analysis , 1994, IEEE Software.
[10] Barbara Paech,et al. Rationale-Based Use Case Specification , 2002, Requirements Engineering.
[11] Bill Curtis,et al. A field study of the software design process for large systems , 1988, CACM.
[12] Jintae Lee,et al. Extending the Potts and Bruns model for recording design rationale , 1991, [1991 Proceedings] 13th International Conference on Software Engineering.
[13] Mark Keil,et al. 'Why didn't somebody tell me?': climate, information asymmetry, and bad news about troubled projects , 2004, DATB.
[14] Jan Bosch,et al. Experiences with ALMA: Architecture-Level Modifiability Analysis , 2002, J. Syst. Softw..
[15] Alexander L. Wolf,et al. Acm Sigsoft Software Engineering Notes Vol 17 No 4 Foundations for the Study of Software Architecture , 2022 .
[16] Michael L. Begeman,et al. gIBIS: a hypertext tool for exploratory policy discussion , 1988, CSCW '88.
[17] David Garlan,et al. Documenting software architectures: views and beyond , 2002, 25th International Conference on Software Engineering, 2003. Proceedings..
[18] Thomas R. Gruber,et al. Design Knowledge and Design Rationale: A Framework for Representation, Capture, and Use , 1991 .
[19] Jan Bosch,et al. Software Architecture: The Next Step , 2004, EWSA.
[20] Raymond McCall,et al. Rationale Management in Software Engineering , 2006 .
[21] Jeff Tyree,et al. Architecture decisions: demystifying architecture , 2005, IEEE Software.
[22] Jintae Lee,et al. Design Rationale Systems: Understanding the Issues , 1997, IEEE Expert.
[23] Kuntz Werner,et al. Issues as Elements of Information Systems , 1970 .
[24] Colin Potts,et al. Recording the reasons for design decisions , 1988, Proceedings. [1989] 11th International Conference on Software Engineering.
[25] Antony Tang,et al. Architecture rationalization: a methodology for architecture verifiability, traceability and completeness , 2005, 12th IEEE International Conference and Workshops on the Engineering of Computer-Based Systems (ECBS'05).
[26] Muhammad Ali Babar,et al. A survey of architecture design rationale , 2006, J. Syst. Softw..
[27] Vasant Dhar,et al. Supporting Systems Development by Capturing Deliberations During Requirements Engineering , 1992, IEEE Trans. Software Eng..
[28] IEEE-SA Standards Board , 2000 .