Complementary use of ad hoc and post hoc design rationale for creating and organising process knowledge

Documenting the requirements engineering (RE) process using the ad hoc notation IBIS (Issue Based Information Systems) and analysing the complexity of the requirement model revealed that the process was not smoothly evolutionary, but involved occasional "crisis" points at which the model was reconceptualised, simplified and restructured. The IBIS base provided essential input for the reconceptualisation, simplification and major restructuring of the model. However, the locality of arguments and the lack of context in the IBIS notation led to difficulty in searching and retrieving desirable information from the large IBIS based. In this paper we investigate the supplementary use of the post hoc notation QOC (Question-Option-Criteria).

[1]  Nick Hammond,et al.  Argumentation-based design rationale: what use at what cost? , 1994, Int. J. Hum. Comput. Stud..

[2]  P. Checkland.  From framework through experience to learning: The essential nature of action research , 1991 .

[3]  Graeme G. Shanks,et al.  Using Design Explanation within the Formal Object-Oriented Method , 1999, Requirements Engineering.

[4]  Raymond McCall,et al.  Making argumentation serve design , 1991 .

[5]  Galal H. Galal-Edeen,et al.  Requirements engineering: A good practice , 2000, Eur. J. Inf. Syst..

[6]  Klaus Pohl,et al.  The three dimensions of requirements engineering: a framework and its applications , 1994, Inf. Syst..

[7]  Paul A. Swatman,et al.  Managing the RE Process : Lessons from Commercial Practice , 1999 .

[8]  Matthias Jarke,et al.  Requirements tracing , 1998, CACM.

[9]  S Buckingham Shum,et al.  Developing the Design Space with Design Space Analysis , 1993 .

[10]  E. Jeffrey Conklin,et al.  A process-oriented approach to design rationale , 1991 .

[11]  Nick Hammond,et al.  Graphical Argumentation and Design Cognition , 1997, Hum. Comput. Interact..

[12]  J. Nunamaker,et al.  Proceedings of the 32nd Hawaii International Conference on System Sciences , 1999 .

[13]  Roger Duke,et al.  Formal Object Oriented Specification Using Object-Z , 2000 .

[14]  Galal H Galal,et al.  Requirements engineering: A good practice , 2000 .

[15]  LeMai Nguyen,et al.  Essential and incidental complexity in requirements models , 2000, Proceedings Fourth International Conference on Requirements Engineering. ICRE 2000. (Cat. No.98TB100219).

[16]  Klaus Pohl,et al.  Adapting traceability environments to project-specific needs , 1998, CACM.

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

[18]  Simon Buckingham Shum,et al.  QOC Design Rationale Retrieval: A Cognitive Task Analysis and Design Implications , 1993 .

[19]  Allan MacLean,et al.  Generating Good Design Questions , 1997 .

[20]  Balasubramaniam Ramesh,et al.  Factors influencing requirements traceability practice , 1998, CACM.

[21]  Thomas P. Moran,et al.  Questions, Options, and Criteria: Elements of Design Space Analysis , 1991, Hum. Comput. Interact..

[22]  Vasant Dhar,et al.  Supporting Systems Development by Capturing Deliberations During Requirements Engineering , 1992, IEEE Trans. Software Eng..

[23]  Paul A. Swatman.  Formal Object-Oriented Method — Foom , 1996 .

[24]  Lemai Nguyen,et al.  Formal Object-Oriented Method (FOOM) , 2000 .

[25]  Raymond McCall,et al.  Making Argumentation Serve Design , 1996, Hum. Comput. Interact..