BaSyRE : A Lightweight Combination of Proven RE Techniques

Many small companies do requirements engineering (RE) superficially or neglect it totally. However, according to software project risk studies a cursorily done RE is one of the biggest risks for software projects. So far RE research has focused on large and complex projects that cannot be managed without proper RE practices. At the same time smaller projects have suffered from basic RE problems. To alleviate this situation we have developed a basic systematic RE method – BaSyRE – that is targeted for small projects developing administrative and business information systems. The key design rationale for BaSyRE are (1) a systematic approach to RE, (2) a ready-to-hand solution, (3) simplicity, and (4) domain specificity. The method itself consists of a requirements document template with techniques and processes for both requirements development and management. All these elements have been adapted to the specific application domain to form a simple but systematic method to be taken in use even without adaptation.

[1]  Steve McConnell,et al.  Software Project Survival Guide , 1997 .

[2]  Peter Checkland,et al.  Systems Thinking, Systems Practice , 1981 .

[3]  Heikki Kälviäinen,et al.  Management View on Current Requirements Engineering Practices in Small and Medium Enterprises , 2000 .

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

[5]  Karan Harbison,et al.  User-Centered Requirements: The Scenario-Based Engineering Process , 1997 .

[6]  Brian Fitzgerald,et al.  An empirical investigation into the adoption of systems development methodologies , 1998, Inf. Manag..

[7]  Kalle Lyytinen,et al.  A framework for identifying software project risks , 1998, CACM.

[8]  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.

[9]  I R Graham.  Requirements engineering and rapid development: an object-oriented approach , 1998 .

[10]  Leszek A. Maciaszek.  Requirements analysis and system design: developing information systems with UML , 2001 .

[11]  Joe Saur.  Effective requirements practices , 2002, SOEN.

[12]  John Daniels,et al.  UML Components: A Simple Process for Specifying Component-Based Software , 2000 .

[13]  Ivar Jacobson,et al.  The Unified Software Development Process , 1999 .

[14]  Lawrence D. Pohlmann,et al.  Customer‐Centered Products – Creating Successful Products through Smart Requirements Management , 2001 .

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

[16]  Bill Curtis,et al.  Applying Discount Usability Engineering , 1995, IEEE Softw..

[17]  Watts S. Humphrey,et al.  A discipline for software engineering , 2012, Series in software engineering.

[18]  Hermann Kaindl.  Why is it so difficult to introduce requirements engineering research results into mainstream requirements engineering practice? , 2000, Proceedings Fourth International Conference on Requirements Engineering. ICRE 2000. (Cat. No.98TB100219).

[19]  Suzanne Robertson,et al.  Mastering the Requirements Process , 1999 .

[20]  Benjamin L. Kovitz,et al.  Practical Software Requirements: A Manual of Content and Style , 1998 .

[21]  Steve Miller.  How Can Requirements Engineering Research Become Requirements Engineering Practice? , 1997, RE.

[22]  Sol J. Greenspan.  Extreme RE: What If There Is No Time for Requirements Engineering? , 2001, RE.

[23]  Gerald Kotonya,et al.  Software Requirements Engineering , 1999 .

[24]  Kent L. Beck,et al.  Extreme programming explained - embrace change , 1990 .

[25]  Sjaak Brinkkemper,et al.  Method engineering: engineering of information systems development methods and tools , 1996, Inf. Softw. Technol..

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

[27]  Lucas D. Introna,et al.  Against method-ism: Exploring the limits of method , 1997, Inf. Technol. People.

[28]  S. Lauesen.  Software Requirements Styles and Techniques , 2001 .

[29]  J. Barrie Thompson,et al.  The use, limitations and customization of structured systems development methods in the United Kingdom , 1995, Inf. Softw. Technol..