Functional requirements categorization Grounded Theory approach

The ever-increasing complexity of information system is making the requirements analysis an intricate and challenging task. The challenge is further intensified in the absence of well-defined body of knowledge as to which requirements must be looked for. Though the requirements are broadly classified as functional and non-functional requirements; however, a special concern is required for functional requirements as the information system, envisioned for an organization, is expected to meet the functional behaviour of that organization. We have used Grounded Theory approach to explore the granular level of functional requirements analyzed during requirements analysis. Based on this qualitative study, we propose a classification scheme for functional requirements in this paper.

[1]  Barry Boehm,et al.  A view of 20th and 21st century software engineering , 2006, ICSE.

[2]  Julio Cesar Sampaio do Prado Leite,et al.  On Non-Functional Requirements in Software Engineering , 2009, Conceptual Modeling: Foundations and Applications.

[3]  John Mylopoulos,et al.  Security and privacy requirements analysis within a social setting , 2003, Proceedings. 11th IEEE International Requirements Engineering Conference, 2003..

[4]  Mayumi Itakura Kamata,et al.  Figure Out the Current Software Requirements Engineering - What Practitioners Expect to Requirements Engineering? - , 2007, 14th Asia-Pacific Software Engineering Conference (APSEC'07).

[5]  W. W. Royce,et al.  Managing the development of large software systems , 1970 .

[6]  Mordechai Ben-Menachem,et al.  Writing effective use cases , 2001, SOEN.

[7]  James Noble,et al.  Developing a grounded theory to explain the practices of self-organizing Agile teams , 2012, Empirical Software Engineering.

[8]  André Kushniruk,et al.  Reusable knowledge for satisficing usability requirements , 2005, 13th IEEE International Conference on Requirements Engineering (RE'05).

[9]  Gerald W. Both,et al.  Object-oriented analysis and design with applications , 1994 .

[10]  Pamela Jordan.  Basics of qualitative research: Grounded theory procedures and techniques , 1994 .

[11]  Brian Randell,et al.  Software engineering : report on a conference sponsored by the NATO Science Committee, Garmisch, Germany, 7th to 11th October 1968 , 1969 .

[12]  Richard H. Thayer,et al.  System and Software Requirements Engineering , 1994 .

[13]  A. Strauss,et al.  The discovery of grounded theory: strategies for qualitative research aldine de gruyter , 1968 .

[14]  Rory V. O'Connor,et al.  Using grounded theory to understand software process improvement: A study of Irish software product companies , 2007, Inf. Softw. Technol..

[15]  B. Glaser.  Theoretical Sensitivity: Advances in the Methodology of Grounded Theory , 1978 .

[16]  Arbi Ghazarian,et al.  Characterization of functional software requirements space: The law of requirements taxonomic growth , 2012, 2012 20th IEEE International Requirements Engineering Conference (RE).

[17]  Tony Gorschek,et al.  A taxonomy for requirements engineering and software test alignment , 2014, ACM Trans. Softw. Eng. Methodol..

[18]  Anthony F. Norcio,et al.  Exploring language in software process elicitation: A grounded theory approach , 2009, 2009 3rd International Symposium on Empirical Software Engineering and Measurement.

[19]  Laurie Williams,et al.  Automated extraction of non-functional requirements in available documentation , 2013, 2013 1st International Workshop on Natural Language Analysis in Software Engineering (NaturaLiSE).

[20]  Grady Booch,et al.  Object-oriented analysis and design with applications (2nd ed.) , 1993 .

[21]  J. N. Buxton,et al.  Software engineering techniques , 1970 .

[22]  Annie I. Antón,et al.  Analyzing Regulatory Rules for Privacy and Security Requirements , 2008, IEEE Transactions on Software Engineering.