Explicitar Requisitos del Software usando Escenarios

Los escenarios describen situaciones del proceso del negocio, tanto del proceso observable actual como del proceso proyectado o futuro. En este ultimo caso los escenarios resultan ser contenedores de la mayoria de los requisitos del sistema de software, pero no son los requisitos propiamente dichos. Muchas de las buenas practicas o practicas recomendadas en el proceso de desarrollo de software se basan en la existencia de un documento de requisitos en el que estos se individualizan en forma precisa. En el presente articulo se presenta una estrategia para confeccionar un documento de requisitos a partir de escenarios ya construidos. La particularidad que presenta la misma es que los requisitos individualizados tienden a ser libres de conflictos y de ambiguedad a consecuencia del propio proceso de produccion.

[1]  Bashar Nuseibeh,et al.  Managing inconsistent specifications: reasoning, analysis, and action , 1998, TSEM.

[2]  Richard Stevens,et al.  Requirements Traceability , 1997, RE.

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

[4]  Karl E. Wiegers,et al.  Software Requirements , 1999 .

[5]  Gregory D. Schumacher,et al.  IEEE Guide for Developing System Requirements Specifications , 1999 .

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

[7]  Graciela D. S. Hadad,et al.  Comprendiendo el Universo de Discurso Futuro con Escenarios , 2002, WER.

[8]  Graciela D. S. Hadad,et al.  Facilitando la Asignación de Prioridades a los Requisitos , 2009, WER.

[9]  Barbara Paech,et al.  Elicitation and Documentation of Non-Functional Requirements for Sociotechnical Systems , 2005 .

[10]  Steve Easterbrook,et al.  Handling conflict between domain descriptions with computer-supported negotiation , 1991 .

[11]  A Straw,et al.  Guide to the Software Engineering Body of Knowledge , 1998 .

[12]  Ralph Young,et al.  The requirements engineering handbook , 2003 .

[13]  Ian Sommerville,et al.  Ingeniería de software , 1988 .

[14]  Desmond Greer.  Requirements Prioritisation for Incremental and Iterative Development , 2004 .

[15]  Barry W. Boehm,et al.  Identifying Quality-Requirement Conflicts , 1996, IEEE Softw..

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

[17]  Julio Cesar Sampaio do Prado Leite,et al.  On Non-Functional Requirements in Software Engineering , 2009, Conceptual Modeling: Foundations and Applications.

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

[19]  William N. Robinson,et al.  Surfacing Requirements Interactions , 2004 .

[20]  Eric Yu,et al.  Non-Functional Requirements Elicitation , 2019, International Journal of Recent Technology and Engineering.

[21]  Jeffrey L. Whitten,et al.  Systems Analysis and Design Methods , 1986 .

[22]  Julio Cesar Sampaio do Prado Leite,et al.  A strategy for conceptual model acquisition , 1993, [1993] Proceedings of the IEEE International Symposium on Requirements Engineering.

[23]  Mark T True,et al.  Software Requirements , 2005 .

[24]  Didar Zowghi,et al.  Reasoning about inconsistencies in natural language requirements , 2005, TSEM.

[25]  M. Bohanec,et al.  The Analytic Hierarchy Process , 2004 .

[26]  Identifying Requirements – , 2022 .

[27]  Claes Wohlin,et al.  An evaluation of methods for prioritizing software requirements , 1998, Inf. Softw. Technol..

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

[29]  A. Berztiss,et al.  Requirements Engineering , 2002, J. Object Technol..

[30]  Alan M. Davis,et al.  The Art of Requirements Triage , 2003, Computer.

[31]  John Yen,et al.  A systematic tradeoff analysis for conflicting imprecise requirements , 1997, Proceedings of ISRE '97: 3rd IEEE International Symposium on Requirements Engineering.

[32]  Julio Cesar Sampaio do Prado Leite,et al.  Scenario inspections , 2003, Requirements Engineering.

[33]  Julio Cesar Sampaio do Prado Leite,et al.  A Scenario Construction Process , 2000, Requirements Engineering.

[34]  Bashar Nuseibeh,et al.  Expressing the relationships between multiple views in requirements specification , 1993, ICSE '93.

[35]  John Mylopoulos,et al.  Representing and Using Nonfunctional Requirements: A Process-Oriented Approach , 1992, IEEE Trans. Software Eng..

[36]  Richard E. Fairley,et al.  The concept of operations: The bridge from operational requirements to technical specifications , 1994, Proceedings of IEEE International Conference on Requirements Engineering.

[37]  Alexander Egyed,et al.  Identifying requirements conflicts and cooperation: how quality attributes and automated traceability can help , 2004, IEEE Software.