Situational Requirement Method System: Knowledge Management in Business Support

Software developers have been successfully tailoring software development methods according the project situation and more so in small scale software development organizations. There is a need to propagate this knowledge to other developers who may be facing the same project situation so that they can benefit from other people experiences. In this paper, use of situational method engineering in requirement elicitation phase is explored. A new, user friendly and progressive web-based tool, Situational Requirement Method System (SRMS), for requirement elicitation phase is developed that can assist in creation, storage and extraction of methods related with this phase. These methods are categorized according to some criteria. This categorization also helps in searching a method which will be most appropriate in a given situation. This approach and tool can also be used for other software development activities.

[1]  Naveen Prakash,et al.  Engineering Methods from Method Requirements Specifications , 2001, Requirements Engineering.

[2]  Kalle Lyytinen,et al.  MetaEdit+: A Fully Configurable Multi-User and Multi-Tool CASE and CAME Environment , 1996, CAiSE.

[3]  E. Domínguez,et al.  Noesis: Towards a situational method engineering technique , 2007, Inf. Syst..

[4]  Kyo Chul Kang,et al.  Issues in Requirements Elicitation , 1992 .

[5]  Isabelle Mirbel,et al.  Situational method engineering: combining assembly-based and roadmap-driven approaches , 2005, Requirements Engineering.

[6]  A. F. Harmsen,et al.  Situational Method Engineering , 1997 .

[7]  J. J. Odell,et al.  A primer to method engineering , 1996 .

[8]  Colette Rolland,et al.  Constructing the Lyee method with a method engineering approach , 2004, Knowl. Based Syst..

[9]  Carine Souveyet,et al.  Patterns for Extending an OO Model with Temporal Features , 1998 .

[10]  Alan M. Davis,et al.  Requirements Elicitation Techniques: Analyzing the Gap between Technology Availability and Technology Use , 2003 .

[11]  M. Heym,et al.  A semantic data model for methodology engineering , 1992, [1992] Proceedings of the Fifth International Workshop on Computer-Aided Software Engineering.

[12]  Colette Rolland,et al.  Towards a Generic Model for Situational Method Engineering , 2003, CAiSE.

[13]  Raees Ahmad Khan,et al.  Software Engineering: A Practitioners Approach , 2014 .

[14]  B. Neeraja,et al.  Knowledge management: an overview & its impact on software industry , 2007 .

[15]  Sjaak Brinkkemper,et al.  Situational method engineering for informational system project approaches , 1994, Methods and Associated Tools for the Information Systems Life Cycle.

[16]  Colette Rolland,et al.  MENTOR: A Computer Aided Requirements Engineering Environment , 1996, CAiSE.

[17]  Colette Rolland,et al.  An Assembly Process Model for Method Engineering , 2001, CAiSE.

[18]  Colette Rolland,et al.  A Multi-Model View of Process Modelling , 1999, Requirements Engineering.

[19]  Neil A. M. Maiden,et al.  ACRE: selecting methods for requirements acquisition , 1996, Softw. Eng. J..

[20]  Roger S. Pressman,et al.  Software Engineering: A Practitioner's Approach , 1982 .

[21]  Raman Ramsin,et al.  Computer-Aided Method Engineering: An Analysis of Existing Environments , 2008, CAiSE.

[22]  Brian Henderson-Sellers,et al.  Comparison of Method Chunks and Method Fragments for Situational Method Engineering , 2008 .