The Community for Technology Leaders
RSS Icon
Issue No.02 - March-April (2013 vol.30)
pp: 38-45
Lianping Chen , University of Limerick and Paddy Power PLC
Muhammad Ali Babar , Lancaster University and IT University of Copenhagen
Bashar Nuseibeh , University of Limerick and The Open University
This article presents a framework for characterizing architecturally significant requirements (ASRs) on the basis of an empirical study using grounded theory. The study involved interviews with 90 practitioners with an accumulated 1,448 years of software development experiences in more than 500 organizations of various sizes and domains. These findings could provide researchers with a framework for discussing and conducting further research on ASRs and can inform researchers' development of technologies for dealing with ASRs. The findings also enrich understanding of requirements and architecture interactions, allowing the twin peaks to move from aspiration to reality.
Software, Computer architecture, Software architecture, Organizations, Interviews, Electronic mail, ASR, requirements, specifications, software engineering, software architectures, architecturally significant requirements, nonfunctional requirements, quality attributes, grounded theory, empirical study
Lianping Chen, Muhammad Ali Babar, Bashar Nuseibeh, "Characterizing Architecturally Significant Requirements", IEEE Software, vol.30, no. 2, pp. 38-45, March-April 2013, doi:10.1109/MS.2012.174
1. B. Nuseibeh, “, Weaving Together Requirements and Architectures,” Computer, vol. 34, no. 3, 2001, pp. 115–117.
2. R.N. Taylor, N. Medvidovic, and E.M. Dashofy, Software Architecture: Foundations, Theory, and Practice, Wiley, 2009.
3. C. Hofmeister et al., “A General Model of Software Architecture Design Derived from Five Industrial Approaches,” J. Systems and Software, vol. 80, no. 1, 2007, pp. 106–126.
4. P. Clements and L. Bass, Relating Business Goals to Architecturally Significant Requirements for Software Systems, tech. note CMU/SEI-2010-TN-018, Software Eng. Inst., Carnegie Mellon Univ., 2010.
5. B. Glaser and A. Strauss, The Discovery of Grounded Theory: Strategies for Qualitative Research, Aldine Transaction, 1967.
6. S. Adolph, W. Hall, and P. Kruchten, “Using Grounded Theory to Study the Experience of Software Development,” Empirical Software Eng., vol. 16, no. 4, 2011, pp. 487–513.
7. J. Corbin and A. Strauss, Basics of Qualitative Research: Techniques and Procedures for Developing Grounded Theory, 3rd ed., Sage, 2007.
8. M.A. Babar, L. Chen, and F. Shull, “Managing Variability in Software Product Lines,” IEEE Software, vol. 27, no. 3, 2010, pp. 89–91, 94.
9. M. Jorgensen and M. Shepperd, “A Systematic Review of Software Development Cost Estimation Studies,” IEEE Trans. Software Eng., vol. 33, no. 1, 2007, pp. 33–53.
10. L. Rapanotti et al., “Architecture-Driven Problem Decomposition,” Proc. 12th IEEE Int'l Requirements Eng. Conf., IEEE, 2003; doi: 10.1109/ICRE.2004.133 5666.
18 ms
(Ver 2.0)

Marketing Automation Platform Marketing Automation Tool