D. Pandey, A. K. Ramani and U. Suman

 D. Pandey  assistant professor at the Department of Information Technology of the BBA University in India.  A. K. Ramani  professor at the School for CSIT of DAVV  U. Suman  reader and chair examination at the School for CSIT of DAVV

Requirements engineering consists of activities that deal with the gathering, analysis, validation, documentation and maintenance of the set of requirements for a system and implements them into the software development process (Pandey, Suman, & Ramani, 2010; Siddiqi, 1996). Requirements are the properties, i.e. features or qualities, that must be possessed by the system or system component that is to be delivered, in order to satisfy customer needs (Jalote, 1997).

1.Requirement elicitation and development 2.Documentation of requirements 3.Validation and verification of requirements 4.Requirement management and planning The process model aids in the effective implementation of the requirement engineering process in order to obtain quality requirements (i.e. they must be clear, consistent, modifiable, and traceable). Phases

 Dorfman, M. (1990). System and Software Requirements Engineering.  Jalote, P. (1997). An integrated approach to software engineering. Springer.  Pandey, D., & Ramani, A. K. (2009). Social- Organizational Participation difficulties in Requirement Engineering Process-A Study.  Sommerville, I., & Kotonya, G. (1998). Requirements Engineering: Processes and Techniques.  Chatzoglou, P. D., & Macaulay, L. A. (1996). Requirements capture and analysis: A survey of current practice

 After the publication of the requirements engineering process model, the three authors cooperated on:  A Framework for Modelling Software Requirements  An Approach to Information Requirement Engineering  Security Requirement Engineering Issues in Risk Management  The proposed RE process is general  In some situations a more specialized and detailed approach is required.  There are no publications available that describe the application of the RE process.

 Suitability for a specific software development context is not described by Pandey et al.  Is the RE process appropriate for Market Driven Requirements Engineering (MDRE)?  Analysis of relevant papers show that only parts of the process are usefull in MDRE context:  Karlsson, L., Dahlstedt, A., och Dag, J. N., Regnell, B., & Persson, A. (2003). Challenges in market-driven requirements engineering-an industrial interview study  Regnell, B., & Brinkkemper, S. (2005). Market-driven requirements engineering for software products  Van de Weerd, I., Brinkkemper, S., Nieuwenhuis, R., Versendaal, J., & Bijlsma, L. (2006). On the creation of a reference framework for software product management: Validation and tool support.

A use case is a series of actions that share an objective (OMG, 2011)

D. Pandey, A. K. Ramani and U. Suman