Requirements Specifications and Recovered Architectures as Grounded Theories
Main Article Content
Abstract
This paper describes the classic grounded theory (GT) process as a method to discover GTs to be subjected to later empirical validation. The paper shows that a well conducted instance of requirements engineering or of architecture recovery resembles an instance of the GT process for the purpose of discovering the requirements specification or recovered architecture artifact that the requirements engineering or architecture recovery produces. Therefore, this artifact resembles a GT.
Downloads
Article Details
The Grounded Theory Review is an open-access journal, which means that all content is freely available without charge to the user or his/her institution. Users are allowed to read, download, copy, distribute, print, search, or link to the full texts of the articles in this journal without asking prior permission from the publisher or the author. This is in accordance with the international Budapest Open Access Initiative (BOAI) definition of open access.
References
Adolph, S., Hall, W., & Kruchten, Ph. (2011). Using grounded theory to study the experience of software development. Empirical Software Engineering 16, 487–513
Bachmann, F., Bass, L., Carriere, J., Clements, P., Garlan, D., Ivers, J., Nord, R., & Little, R. (2000). Software Architecture Documentation in Practice: Documenting Architectural Layers. CMU/SEI-2000-SR-004. Software Engineering Institute, Carnegie Mellon University, Pittsburgh, PA, USA, http://www.sei.cmu.edu/reports/00sr004.pdf
Berry, D.M., Daudjee, K., Dong, J., Fainchtein, I., Nelson, M.A., Nelson, T., & Ou, L. (2004). User's Manual as a Requirements Specification: Case Studies. Requirements Engineering Journal 9, 67–82
Booch, G., Jacobson, I., & Rumbaugh, J. (1998). The Unified Modeling Language User Guide. Addison-Wesley Longman, Reading, MA, USA
Bowen, J. (1996). Formal Specification and Documentation using Z: A Case Study Approach. International Thomson Computer Press, New York, NY, USA, also at http://www.zuser.org/zbook
Breaux, T.D., & Antón, A.I. (2008). Analyzing regulatory rules for privacy and security requirements. IEEE Transactions on Software Engineering 34, 5–20
Briand, L.C. (2006). The experimental paradigm in reverse engineering: Role, challenges, and limitations. In: Thirteenth Working Conference on Reverse Engineering (WCRE), 3–8
Brower, R.S., & Jeong, H.S. (2008). Grounded analysis: Beyond description to derive theory from qualitative data. In Yang, K., Miller, G.J., eds.: Handbook of Research Methods in Public Administration. Boca Raton, FL, USA, Auerbach, Taylor & Francis, 823 – 839
Calloway, L.J., & Knapp, C.A. (1995). Using grounded theory to interpret interviews. Technical report, School of Computer Science and Information Systems, Pace University, New York, NY, USA, http://csis.pace.edu/~knapp/AIS95.htm
Carver, J. (2007). The use of grounded theory in empirical software engineering. In: Empirical Software Engineering Issues. Critical Assessment and Future Directions. LNCS 4336, Berlin/Heidelberg, Germany, Springer, 42–42.
Chikofsky, E.J., & Cross, J.H. (1990). Reverse engineering and design recovery: A taxonomy. IEEE Software 7, 13–17
Cockburn, A. (2000). Selecting a project’s methodology. IEEE Software 17, 64–71
Coleman, G., & O’Connor, R. (2006). Software process in practice: A grounded theory of the irish software industry. In: Software Process Improvement. LNCS 4257, Berlin/Heidelberg, Germany, Springer, 28–39
Coleman, G., & O’Connor, R. (2007). Using grounded theory to understand software process improvement: A study of Irish software product companies. Information and Software Technology 49, 654–667
Dick, B. (2005). Grounded theory: a thumbnail sketch. Technical report, Graduate College of Management, Southern Cross University, Lismore, NSW, Australia, http://www.scu.edu.au/schools/gcm/ar/arp/grounded.htmlGalal, G.H. (2001). From contexts to constructs: the use of grounded theory in operationalising contingent process models. European Journal of Information Systems 10, 2–14
Galal, G.H., & Paul, R.J. (1999). A qualitative scenario approach to managing evolving requirements. Requirements Engineering Journal 4, 92–102
Gause, D., & Weinberg, G. (1990). Are Your Lights On? How to Figure Out What the Problem REALLY Is. Dorset House, New York, NY, USA
Glaser, B.G. (1992). Basics of Grounded Theory Analysis: Emergence vs. Forcing. Sociology Press, Mill Valley, CA, USA
Glaser, B.G., & Strauss, A.L. (1967). The Discovery of Grounded Theory: Strategies for Qualitative Research. Aldine, Chicago, IL, USA
Gold, N.E., & Bennett, K.H. (2002). Hypothesis-based concept assignment in software maintenance. IEE Proceedings — Software 149, 103–110
Hoda, R., Noble, J., & Marshall, S. (2010). Using grounded theory to study the human aspects of software engineering. In: Human Aspects of Software Engineering, Reno, NV, USA, 5:1–2
Holt, R. (2002). Software architecture as a shared mental model. In: Proceedings of the Tenth International Workshop on Program Comprehension (IWPC). Paris, France
IEEE (1998). IEEE Recommended Practice for Software Requirements Specifications. ANSI/IEEE Standard 830-1998. IEEE Computer Society, Los Alamitos, CA, USA
Jeong, H.S. (2006). A Grounded Analysis of the Sensemaking Process of Korean Street-Level Fire Service Officials. PhD thesis, Public Administration, Florida State University, Tallahassee, FL, USA
Johansson, M., & Timpka, T. (1996). Quality functions for requirements engineering in system development methods. Informatics for Health and Social Care 21, 133–145.
Kapser, C.J., & Godfrey, M.W. (2006). “Cloning considered harmful” considered harmful. In: Thirteenth Working Conference on Reverse Engineering (WCRE), 19–28
Lang, M., & Fitzgerald, B. (2007). Web-based systems design: a study of contemporary practices and an explanatory framework based on “method-in-action”. Requirements Engineering Journal 12, 203–220
Pershin, G. (2006). Adoption of Policies that Permit Community Colleges to Grant Bachelor Degrees in Florida. PhD thesis, Public Administration, Florida State University, Tallahassee, FL, USA
Power, N. (2002). A Grounded Theory of Requirements Documentation in the Practice of Software Development. PhD thesis, Dublin City University, Dublin, Ireland
Ramos, I.M. (2000). Aplicações das Tecnologias de Informação que Suportam as Dimensões Estrutural, Social, Política e Simbólica do Trabalho. PhD thesis, Departamento de Informática, Universidade do Minho, Guimarães, Portugal
Rittel, H., & Webber, M. (1973). Dilemmas in a General Theory of Planning. Policy Sciences 4, 155–169
Robertson, S., Robertson, J. (2006). Mastering the Requirements Process. Second Edition. Addison-Wesley, Harlow, UK
Sillito, J., Volder, K.D., Fisher, B., & Murphy, G. (2005). Managing software change tasks: An exploratory study. In: Proceedings of the International Symposium on Empirical Software Engineering (ISESE), 23–32
Sillito, J., & Wynn, E. (2007). The social context of software maintenance. In: Proceedings of the Twenty-Third IEEE International Conference on Software Maintenance (ICSM), 325–334
Sommerville, I. (2007). Software Engineering. Pearson Education, Harlow, UK
Teixeira, L., Ferreira, C., & Santos, B.S. (2010). User-centered requirements engineering in health information systems: A study in the hemophilia field. Computer Methods and Programs in Biomedicine 106, 160–174
Walsham, G. (1995). Interpretive case studies in IS research: Nature and method. European Journal of Information Systems 4, 74–83
Weber, J.L. (2010). Privacy and security attitudes, beliefs and behaviours: Informing future tool design. Master’s thesis, University of Waterloo, Waterloo, ON, Canada, http://se.uwaterloo.ca/~dberry/FTP_SITE/students.theses/janna.weber/thesis.pdf