Problem structuring and analysis method based on soft system methodology for teaching requirements engineering/ Rafia Naz Memon

The discipline of Requirements Engineering (RE) is hard for students to understand and challenging for lecturers to teach due to its complex nature. In the literature, researchers have presented a number of Requirements Engineering Education (REE) problems in universities, as well as RE problems in the industry, which can be addressed by providing proper REE at universities. However, no effort has been made to systematically compile, and analyse these problems so that it is possible to have a bird’s-eye view of REE problems. This analysis and presentation of the problems is referred to as “an integrated view of the REE problems”. Some problems have been reported and investigated by researchers while some remain only as reported problems. Therefore, this research aims to come up with an integrated view of REE problems, followed by selecting one problem area to be the research focus and addressing the selected problem by formulating a method. In the first phase of the study, an integrated view of REE problems was produced. A survey was then performed among students and lecturers who have studied and taught RE course to verify the REE problems presented in the integrated view and to identify a selected research focus. This leads to the identification of the research focus which is teaching problem structuring and analysis. The literature survey on problem structuring and analysis showed that it has not been explicitly emphasised in the RE course but thought to be covered using requirements analysis methods. For students with no industrial experience, it is difficult to learn problem structuring and analysis using these methods. Therefore, in the second phase of the research, a light-weight method was proposed to be taught to undergraduate software engineering students in the RE course to enable them to understand and perform the problem structuring and analysis. The method is referred to as L-Soft to portray that it has transformed the idea of Soft system methodology into a light-weight iii (simple structure and easy to apply procedure) RE method. In order to facilitate the understanding and application of the L-Soft method, students were provided with a step-by-step guide on performing the problem structuring and analysis, a glossary of terms used in the method and a sample of solved case studies. A web-based tool for LSoft was developed to provide learning support to the students. In the final phase of the study, the appropriateness of the method for performing the problem structuring and analysis was validated using feature analysis performed by lecturers and software engineers. The perceived adoption in practice was validated using method acceptance testing performed by the lecturers and software engineers and the results showed that the L-Soft method has a high likelihood of being adopted in practice. Finally, an experimental study was performed among undergraduate software engineering students to validate the method’s successfulness. The results showed that LSoft was more efficient and effective than an existing analysis method and have a higher likelihood of being adopted into practice rather than the existing analysis method.

[1]  Donald Firesmith,et al.  Prioritizing Requirements , 2004, J. Object Technol..

[2]  Michele Biasutti,et al.  The student experience of a collaborative e-learning university module , 2011, Comput. Educ..

[3]  Douglas T. Ross,et al.  Structured Analysis (SA): A Language for Communicating Ideas , 1977, IEEE Transactions on Software Engineering.

[4]  Ban Al-Ani,et al.  Role-playing, group work and other ambitious teaching methods in a large requirements engineering course , 2004, Proceedings. 11th IEEE International Conference and Workshop on the Engineering of Computer-Based Systems, 2004..

[5]  A. J. Downs The Hole in the Curriculum. , 1971 .

[6]  Anselm L. Strauss,et al.  Basics of qualitative research : techniques and procedures for developing grounded theory , 1998 .

[7]  H. Rittel,et al.  Dilemmas in a general theory of planning , 1973 .

[8]  Ian Sommerville,et al.  Requirements process improvement through the phased introduction of good practice , 1997 .

[9]  Tony Gorschek,et al.  Multi Perspective Requirements Engineering Education with Focus on Industry Relevance , 2005 .

[10]  Daniel L. Moody,et al.  The method evaluation model: a theoretical model for validating information systems design methods , 2003, ECIS.

[11]  Peter Checkland,et al.  Soft Systems Methodology in Action , 1990 .

[12]  James Robertson,et al.  Mastering the Requirements Process: Getting Requirements Right , 2012 .

[13]  Donald C. Gause,et al.  Teaching the Unknown and the Unknowable in Requirements Engineering Education , 2008, 2008 Requirements Engineering Education and Training.

[14]  Daniela Rosca An active/collaborative approach in teaching requirements engineering , 2000, 30th Annual Frontiers in Education Conference. Building on A Century of Progress in Engineering Education. Conference Proceedings (IEEE Cat. No.00CH37135).

[15]  Richard Stevens,et al.  Writing Better Requirements , 2002 .

[16]  Khaled El Emam,et al.  A field study of requirements engineering practices in information systems development , 1995, Proceedings of 1995 IEEE International Symposium on Requirements Engineering (RE'95).

[17]  Jocelyn Armarego,et al.  Studio learning of requirements: towards aligning teaching to practitioner needs , 2005 .

[18]  J. Paul Gibson Formal requirements engineering: learning from the students , 2000, Proceedings 2000 Australian Software Engineering Conference.

[19]  Jonathan Rosenhead,et al.  What's the Problem? An Introduction to Problem Structuring Methods , 1996 .

[20]  Gene P. Agre The Concept of Problem , 1982 .

[21]  P. Hsia,et al.  Scenario driven requirements analysis method , 1992, Proceedings of the Second International Conference on Systems Integration.

[22]  Rafia Naz Memon,et al.  Analysis and Classification of Problems Associated with Requirements Engineering Education: Towards an Integrated View , 2014 .

[23]  Anne Hoffmann Teaching Soft Facts in Requirements Engineering Using Improvisation Theatre Techniques , 2008, 2008 Third International Workshop on Multimedia and Enjoyable Requirements Engineering - Beyond Mere Descriptions and with More Fun and Games.

[24]  Nazim H. Madhavji,et al.  A controlled experiment to assess the impact of system architectures on new system requirements , 2010, Requirements Engineering.

[25]  Lene Tolstrup Sørensen,et al.  Evaluating six soft approaches , 2008 .

[26]  Orlena Gotel,et al.  RE-O-POLY : A Game to Introduce Lightweight Requirements Engineering Good Practices , 2007 .

[27]  Norman Bresky Root Cause Analysis: Simplified Tools and Techniques (2nd ed.), by Bjorn Andersen and Tom Fagerhaug , 2007 .

[28]  Behrouz Homayoun Far,et al.  Combining requirements engineering techniques - theory and case study , 2005, 12th IEEE International Conference and Workshops on the Engineering of Computer-Based Systems (ECBS'05).

[29]  H. D. Rombach,et al.  The Goal Question Metric Approach , 1994 .

[30]  R. N. Memon,et al.  Identifying research gaps in requirements engineering education: An analysis of a conceptual model and survey results , 2012, 2012 IEEE Conference on Open Systems.

[31]  Tony Gorschek,et al.  Requirements Abstraction Model , 2005, Requirements Engineering.

[32]  Michael Pidd,et al.  Problem Structuring — A Literature Review , 1981 .

[33]  Shari Lawrence Pfleeger,et al.  Experimental design and analysis in software engineering , 1995, Ann. Softw. Eng..

[34]  Frederick P. Brooks,et al.  No Silver Bullet: Essence and Accidents of Software Engineering , 1987 .

[35]  Daniel L. Moody,et al.  Evaluating the quality of information models: empirical testing of a conceptual model quality framework , 2003, 25th International Conference on Software Engineering, 2003. Proceedings..

[36]  Zhi Li,et al.  Progressing problems from requirements to specifications in problem frames , 2008, IWAAPF '08.

[37]  Ian Sommerville,et al.  Requirements Engineering: Processes and Techniques , 1998 .

[38]  R. Vidal Dealing with problematic situations , 2005 .

[39]  Roel Wieringa,et al.  Guest Editors' Introduction: RE'03-Practical Requirements Engineering Solutions , 2004, IEEE Softw..

[40]  Claes Wohlin,et al.  Achieving industrial relevance in software engineering education , 1999, Proceedings 12th Conference on Software Engineering Education and Training (Cat. No.PR00131).

[41]  P. Kline Handbook of Psychological Testing , 2013 .

[42]  Pamela Zave Classification of research efforts in requirements engineering , 1997, ACM Comput. Surv..

[43]  Daniel L. Moody,et al.  Complexity effects on end user understanding of data models : An experimental comparison of large data model representation methods , 2002, ECIS.

[44]  Xavier Franch The i∗ framework: The way ahead , 2012, 2012 Sixth International Conference on Research Challenges in Information Science (RCIS).

[45]  Marta Arquero Badal Strategic management - Problem structuring methods , 2006 .

[46]  Olly Gotel,et al.  Gameplay to introduce and reinforce requirements engineering good practices , 2009 .

[47]  W. Richards Adroin Developing and deploying software engineering courseware in an adaptable curriculum framework , 2000, ICSE '00.

[48]  Angela Carbone,et al.  Ill-structured Problem Solving in Engineering Education , 2007 .

[49]  James R. Evans Creative Thinking in the Decision and Management Sciences , 1991 .

[50]  Jonathan Rosenhead,et al.  Problem structuring methods in action , 2004, Eur. J. Oper. Res..

[51]  Philippe Massonet,et al.  GRAIL/KAOS: An Environment for Goal-Driven Requirements Engineering , 1997, Proceedings of the (19th) International Conference on Software Engineering.

[52]  R. Ackoff The Future of Operational Research is Past , 1979 .

[53]  Didar Zowghi Teaching Requirements Engineering to the Baháí Students in Iran who are Denied of Higher Education , 2009, 2009 Fourth International Workshop on Requirements Engineering Education and Training.

[54]  John H. McColl,et al.  Statistics Glossary v1.1 , 1997 .

[55]  Charles Wallace,et al.  Instruction in Problem Structuring and Analysis Through Problem Frames , 2006, 19th Conference on Software Engineering Education & Training (CSEET'06).

[56]  James D. Arthur,et al.  Problem Identification and Decomposition within the Requirements Generation Process , 2002 .

[57]  Armin Eberlein,et al.  Requirements engineering for time-to-market projects , 2002, Proceedings Ninth Annual IEEE International Conference and Workshop on the Engineering of Computer-Based Systems.

[58]  Ivar Jacobson,et al.  Object-oriented software engineering - a use case driven approach , 1993, TOOLS.

[59]  Klaas Sikkel,et al.  Mission 2 Solution: Requirements Engineering Education as a Central Theme in the BIT Programme , 2005 .

[60]  David Callele,et al.  Teaching requirements engineering to an unsuspecting audience , 2006, SIGCSE.

[61]  Julio Cesar Sampaio do Prado Leite,et al.  Viewpoint analysis: a case study , 1989, IWSSD '89.

[62]  Gordana Dodig Crnkovic,et al.  Constructive Research and Info-computational Knowledge Generation , 2010 .

[63]  M. Jackson,et al.  Problem Analysis and Structure , 2000 .

[64]  Gerald W. Evans,et al.  The impact of training on the formulation of ill-structured problems , 2007 .

[65]  Donald A. Schön Educating the Reflective Practitioner: Toward a New Design for Teaching and Learning in the Professions , 1987 .

[66]  Jocelyn Armarego,et al.  Requirements Engineering: a close look at industry needs and a model curricula , 2005, Australas. J. Inf. Syst..

[67]  R. B. Johnson,et al.  Educational Research: Quantitative, Qualitative, and Mixed Approaches , 2007 .

[68]  Christopher M. Lott,et al.  Technology Package for the Goal Question Metric Paradigm , 1996 .

[69]  Roger J. Volkema Creativity in MS/OR: Managing the Process of Formulating the Problem , 1995 .

[70]  Krassie Petrova,et al.  Bridging the Research-Practice Gap in Requirements Engineering through Effective Teaching and Peer Learning , 2009, 2009 Sixth International Conference on Information Technology: New Generations.

[71]  Nelly Condori-Fernández,et al.  An empirical comparative evaluation of requirements engineering methods , 2010, Journal of the Brazilian Computer Society.

[72]  Annie I. Antón,et al.  Goal-based requirements analysis , 1996, Proceedings of the Second International Conference on Requirements Engineering.

[73]  Charles R. Schwenk,et al.  Formulating the mess: The role of decision aids in problem formulation , 1983 .

[74]  Daryl Kulak,et al.  Use cases: requirements in context , 2000, SOEN.

[75]  Michele Biasutti,et al.  'Evaluating a music e-learning resource: The participants' perspective' , 2009, Comput. Educ..

[76]  Mahmood Khan Niazi,et al.  Improving the Requirements Engineering Process through the Application of a Key Process Areas Approach , 2002 .

[77]  Douglas T. Ross,et al.  Structured Analysis for Requirements Definition , 1977, IEEE Transactions on Software Engineering.

[78]  Francisca Losavio,et al.  Feature analysis for architectural evaluation methods , 2006, J. Syst. Softw..

[79]  Didar Zowghi,et al.  The Role of Conducting Stakeholder Meetings in Requirements Engineering Training , 2012 .

[80]  Li Jiang,et al.  A framework for the requirements engineering process development , 2005 .

[81]  Romi Satria Wahono ANALYZING REQUIREMENTS ENGINEERING PROBLEMS , 2003 .

[82]  Lemai Nguyen,et al.  Understanding requirements engineering: a challenge for practice and education , 2002 .

[83]  Bashar Nuseibeh,et al.  Problem Frames: A Case for Coordination , 2004, COORDINATION.

[84]  Dean Leffingwell,et al.  Managing software requirements: a unified approach , 1999 .

[85]  B. Kitchenham,et al.  DESMET : A method for evaluating Software Engineering methods and tools , 2000 .

[86]  Michael Jackson Problem frames and software engineering , 2008, Expert Syst. J. Knowl. Eng..

[87]  Ian K. Bray,et al.  An Introduction to Requirements Engineering , 2002 .

[88]  P. Zave,et al.  Specifying software requirements , 1980, Proceedings of the IEEE.

[89]  David E. Avison,et al.  Towards an SSM toolkit: rich picture diagramming , 1992 .

[90]  Gerald M. Weinberg,et al.  Are Your Lights On?: How to Figure Out What the Problem Really is , 1982 .

[91]  Alain Wegmann,et al.  Experiential learning approach for requirements engineering education , 2009, Requirements Engineering.

[92]  Colin Eden,et al.  Analyzing cognitive maps to help structure issues or problems , 2004, Eur. J. Oper. Res..

[93]  Colette Rolland,et al.  Guiding Goal Modeling Using Scenarios , 1998, IEEE Trans. Software Eng..

[94]  Sidney C. Bailin,et al.  Software requirements engineering , 2011 .

[95]  Alan M. Davis,et al.  Moving Beyond the Classroom : Integrating Requirements Engineering Research & Education to Improve Practice , 2005 .

[96]  Michael Pidd From Problem-Structuring to Implementation , 1988 .