Inspección de escenarios

Abstract.The closeness of the scenarios with concrete situations helps clients/users and requirements engineers to develop a shared understanding of the necessities. This phenomenon is significantly increased when scenarios are built using natural language. The flexibility offered by the natural language improves the interaction of the participants in the process of requirements capture, however it adds one important difficulty when the time to validate them arrives, since the discrepancies, omissions and errors are hard to detect. On the other hand to rely on requirements as much consistent and complete as possible is a growing necessity in the current software engineering. In the present article a set of heuristics to ease the detection of errors in scenarios is proposed. These heuristics basically consist on a set of cross checks between the scenarios and the Language Extended Lexicon, and between the scenarios themselves.

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

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

[3]  Alan M. Davis,et al.  Software Requirements: Objects, Functions and States , 1993 .

[4]  Richard C. Waters,et al.  The Requirements Apprentice: Automated Assistance for Requirements Acquisition , 1991, IEEE Trans. Software Eng..

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

[6]  Matthias Jarke,et al.  Scenarios in System Development: Current Practice , 1998, IEEE Softw..

[7]  W. T. Farris,et al.  Software requirements specifications , 1993 .

[8]  Kenji Takahashi,et al.  Inquiry-based requirements analysis , 1994, IEEE Software.

[9]  T.M. Duffy,et al.  Scenario-Based Design: Envisioning Work and Technology in System Development [Book Review] , 1996, IEEE Transactions on Professional Communication.

[10]  J. A. Bubenko,et al.  Objectives driven capture of business rules and of information systems requirements , 1993, Proceedings of IEEE Systems Man and Cybernetics Conference - SMC.

[11]  Linda A. Macaulay Requirements capture as a cooperative activity , 1993, [1993] Proceedings of the IEEE International Symposium on Requirements Engineering.

[12]  Michael Jackson,et al.  Four dark corners of requirements engineering , 1997, TSEM.

[13]  Arthur L. Price,et al.  Managing code inspection information , 1994, IEEE Software.

[14]  Grady Booch,et al.  Object-Oriented Design with Applications , 1990 .

[15]  Lorna A. Zorman Requirements Envisaging by Utilizing Scenarios (REBUS). , 1995 .

[16]  Thomas E. Bell,et al.  Software requirements: Are they really a problem? , 1976, ICSE '76.

[17]  Pericles Loucopoulos,et al.  System Requirements Engineering , 1995, System Requirements Engineering.

[18]  Julio Cesar Sampaio do Prado Leite,et al.  A client oriented requirements baseline , 1995, Proceedings of 1995 IEEE International Symposium on Requirements Engineering (RE'95).