Repeatable quality assurance techniques for requirements negotiations

Many software projects fail because early life-cycle defects such as ill-defined requirements are not identified and removed. Therefore, quality assurance (QA) techniques for defect detection and prevention play an important role. The effectiveness and efficiency of QA approaches has been empirically evaluated. In this paper we discuss QA techniques optimized for requirements negotiations. In particular, we focus on negotiations using the EasyWinWin approach. We present (1) repeatable techniques for checking quality throughout negotiations as well as (2) role-oriented inspection techniques helping a project team to reduce unnecessary complexity and to mitigate risks stemming from defects in requirements negotiation results. We present the results of a thorough feasibility study we conducted to test our approach.

[1]  Stefan Biffl,et al.  Using reading techniques to focus inspection performance , 2001, Proceedings 27th EUROMICRO Conference. 2001: A Net Odyssey.

[2]  Stefan Biffl,et al.  Integrating Collaborative Processes and Quality Assurance Techniques: Experiences from Requirements Negotiation , 2004, J. Manag. Inf. Syst..

[3]  Thomas Gilb,et al.  Software Inspection , 1994 .

[4]  Robert O. Briggs,et al.  Surfacing tacit knowledge in requirements negotiation: experiences using EasyWinWin , 2001, Proceedings of the 34th Annual Hawaii International Conference on System Sciences.

[5]  Barry W. Boehm,et al.  Developing Groupware for Requirements Negotiation: Lessons Learned , 2001, IEEE Softw..

[6]  Douglas R. Vogel,et al.  Using Group Support Systems for Software Inspections , 2001, IEEE Softw..

[7]  Barry W. Boehm,et al.  Software Requirements Negotiation and Renegotiation Aids: A Theory-W Based Spiral Approach , 1995, 1995 17th International Conference on Software Engineering.

[8]  Colin Potts,et al.  Recording the reasons for design decisions , 1988, Proceedings. [1989] 11th International Conference on Software Engineering.

[9]  S. Biffl,et al.  Groupware Support for Software Requirements Inspection , 2001 .

[10]  Galal H. Galal-Edeen,et al.  Stakeholder identification in the requirements engineering process , 1999, Proceedings. Tenth International Workshop on Database and Expert Systems Applications. DEXA 99.

[11]  Henk Sol,et al.  Proceedings of the 54th Hawaii International Conference on System Sciences , 1997, HICSS 2015.

[12]  Michael E. Fagan.  Design and Code Inspections to Reduce Errors in Program Development , 1976, IBM Syst. J..

[13]  Robert O. Briggs,et al.  EasyWinWin: managing complexity in requirements negotiation with GSS , 2002, Proceedings of the 35th Annual Hawaii International Conference on System Sciences.

[14]  Stefan Biffl,et al.  A groupware-supported inspection process for active inspection management , 2002, Proceedings. 28th Euromicro Conference.

[15]  Kuntz Werner,et al.  Issues as Elements of Information Systems , 1970 .

[16]  Stefan Biffl,et al.  Tailoring a COTS group support system for software requirements inspection , 2001, Proceedings 16th Annual International Conference on Automated Software Engineering (ASE 2001).

[17]  Oliver Laitenberger,et al.  An encompassing life cycle centric survey of software inspection , 2000, J. Syst. Softw..

[18]  Jay F. Nunamaker,et al.  ThinkLets: achieving predictable, repeatable patterns of group interaction with group support systems (GSS) , 2001, Proceedings of the 34th Annual Hawaii International Conference on System Sciences.

[19]  Oliver Laitenberger,et al.  Cost-effective Detection of Software Defects through Perspective-based Inspections , 2001, Empirical Software Engineering.

[20]  Stefan Biffl,et al.  Software Product Improvement with Inspection , 2000, EUROMICRO.

[21]  S. Toulmin.  The uses of argument , 1960 .

[22]  William N. Robinson,et al.  Supporting the negotiation life cycle , 1998, CACM.

[23]  Olly Gotel,et al.  An analysis of the requirements traceability problem , 1994, Proceedings of IEEE International Conference on Requirements Engineering.

[24]  Forrest Shull,et al.  The empirical investigation of Perspective-Based Reading , 1995, Empirical Software Engineering.

[25]  Thomas P. Moran,et al.  Design rationale: the argument behind the artifact , 1989, CHI '89.