Advertisement

Requirements Engineering

, Volume 2, Issue 4, pp 184–198 | Cite as

Enhancing a requirements baseline with scenarios

  • Julio Cesar Sampaio do Prado LeiteEmail author
  • Gustavo Rossi
  • Federico Balaguer
  • Vanesa Maiorana
  • Gladys Kaplan
  • Graciela Hadad
  • Alejandro Oliveros
Article

Abstract

Scenarios are well recognised as an important strategy towards understanding the interface between the environment and the system as well as a means of eliciting and specifying software behaviour. We adopt a broader view of scenarios. For us, a scenario is an evolving description of situations in the environment. Our proposal is framed by Leite’s work on a client-oriented requirements baseline, which aims to model the external requirements of a software system and its evolution. Scenarios start by describing the environment situations, according to the main actions performed outside the software system. Scenarios also help to clarify the interrelation between functional and non-functional requirements. We have validated our strategy and the related representations based on case studies.

Keywords

Requirements baseline Requirements modelling Scenarios Traceability 

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

References

  1. 1.
    Lehman MM. Process Improvement—The Way Forward, Anais do X Simpósio Brasileiro de Engenharia de Software, Sociedade Brasileira de Computação, Out. 1996, pp. 23–33.Google Scholar
  2. 2.
    Chatzoglou PD, Macaulay LA. Requirements Capture and Analysis: A Survey of Current Practice Requirements Engineering Journal, Springer Verlag, London, 1996, Vol:1, N.2, 75–87Google Scholar
  3. 3.
    Leite JCSP and Oliveira APA. A Client Oriented Requirements Baseline, In Proceedings of the Scnd IEEE International Symposium on Requirements Engineering, IEEE Computer Society Press, 1995 pp. 108–115Google Scholar
  4. 4.
    Jackson MA. Software Requirements & Specifications, Addison-Wesley, ACM Press, 1995Google Scholar
  5. 5.
    Carrol J (ed). Scenario-Based Design: Envisoning Work and Technology in System Development, Wiley, New York, 1995Google Scholar
  6. 6.
    Zorman L. Requirements Envisaging by Utilizing Scenarios (Rebus), Ph.D. Dissertation, University of Southern California, 1995Google Scholar
  7. 7.
    Rubin KS, Goldberg J. Object Behavior Analysis, Communications of the ACM, Vol. 35, No. 9, Sep. 1992, 48–62CrossRefGoogle Scholar
  8. 8.
    Jacobson I, Christerson M, Jonsson P, Overgaard G. Object-Oriented Software Engineering—A Use Case Driven. Approach, Reading, MA: Addison-Wesley; New York: Acm Press, 1992zbMATHGoogle Scholar
  9. 9.
    Potts C, Takahashi K, Antón AI. Inquiry-Based Requirements Analysis. IEEE software, Mar. 1994, Vol. 11, n. 2, pp. 21–32CrossRefGoogle Scholar
  10. 10.
    Leite JCSP and Franco APM. A Strategy for Conceptual Model Acquisition In Proceedings of the First IEEE International Symposium on Requirements Engineering, San Diego, Ca, IEEE Computer Society Press, 1994 pp. 243–246Google Scholar
  11. 11.
    Gotel OCZ and Finkelstein ACW. An Analysis of the Requirements Traceability Problem, In Proceedings of the First International Conference on Requirements Engineering, Colorado Springs, IEEE Computer Society Press, 1994, pp. 94–101CrossRefGoogle Scholar
  12. 12.
    Pohl K. PRO-ART: Enabling Requirements Pre-Traceability, In Proceedings of the Scnd International Conference on Requirements Engineering, IEEE Computer Society Press, 1996 pp. 76–84Google Scholar
  13. 13.
    Parnas DL, Clements PC. A Rational Design Process: How and Why to Fake it. IEEE Transactions on Software Engineering, Feb. 1996, Vol. SE-12, No. 2, 251–257Google Scholar
  14. 14.
    Kaplan G, Hadad G, Oliveros A. Uso de Lexico Extendido del Lenguaje (LEL) y de Escenarios para la Elicitacion de Requerimientos. Aplicacion a un Caso Real, Informe d Investigación Departamento de Inverstigación, Universidad de Belgrano, Buenos Aires, 1996Google Scholar
  15. 15.
    Oliveira AP, Leite JCSP. SERBAC: Uma Estratégia para a Definição de Requisitos, In Proceedings of the VIII Simpósio Brasileiro de Engenharia de Software, Sociedade Brasileira de Computação, Out. 1994, pp. 109–123Google Scholar
  16. 16.
    Elmasri and Navathe S. Fundamentals of Data Base Systems, Benjamin/Cummings Publishing Comp. Inc, 1989Google Scholar
  17. 17.
    Schwabe D, Rossi G. The Object-Oriented Hypermedia Design Model. Communications of the ACM, Aug. 1995, Vol. 38 (8), 45–46CrossRefGoogle Scholar
  18. 18.
    Schwabe D, Rossi G, Barbosa S. Systematic Hypermedia Design with OOHDM, Proceedings of the Seventh ACM International Conference on Hypertext, Hypertext ’96, pp. 116–128Google Scholar
  19. 19.
    Hadad G, Kaplan G, Léxico extendido del lenguaje y escenarios del Agenda de Reuniones, Documento de Trabajo, Dep. de Investigación, Universidad de Belgrano, 1997Google Scholar
  20. 20.
    van Lamsweerde A, Darimont R, Massonet Ph. The Meeting Scheduler System—Preliminary Definition, Internal Report, University of Louvain, 1993Google Scholar
  21. 21.
    Oliveros A, Leite JCSP, Rossi G. Uso de Escenarios en el Desarrollo de Software. Proyecto de Investigacion, Departamento de Inverstigación, Universidad de Belgrano, Buenos Aires, 1995Google Scholar
  22. 22.
    Jackson MA. Systems Development, Prentice-Hall, 1983Google Scholar
  23. 23.
    Maiorana V, Balaguer F, La Relacion Entre el Modelo Baseline y Escenarios, Informe de Investigación Departamento de Inverstigación, Universidad de Belgrano, Buenos Aires, 1996Google Scholar
  24. 24.
    Rolland C. Modelling the Evolution of Artifacts. In Proceedings of the First International Conference on Requirements Engineering. IEEE Computer Society Press, 1994, pp. 216–219Google Scholar
  25. 25.
    Pott, C. “Using Schematic Scenarios to Understand User Needs” Proceedings of the Symposium on Designing Interactive Systems. ACM Press, Ann Arbor, 1995, pp. 247–256Google Scholar
  26. 26.
    Dardenne A, van Lamsweerde A, Fickas S. Goal Directed Requirements Acquisition, Science of Computer Programming, Apr. 1993, Vol. 20 (1), 3–50zbMATHCrossRefGoogle Scholar
  27. 27.
    Antón AL. Goal-Based Requirements Analysis, Proceedings of the IEEE Second International Conference on Requirements Engineering, Colorado Springs, IEEE Computer Society Press, 1996, pp. 136–144Google Scholar
  28. 28.
    Mylopoulos J, Chung L, Nixon B. Representing and Using Non-Functional Requirements: A Process Oriented Approach, IEEE Transactions on Software Engineering, Jun. 1992, Vol. 18, No. 6, 483–497CrossRefGoogle Scholar
  29. 29.
    Sutcliffe A. A Technique Combination Approach to Requirements Engineering, In Proceedings of the Third International Symposium on Requirements Engineering, IEEE Computer Society Press, 1997, pp. 65–74Google Scholar
  30. 30.
    Dano B, Briand H, Barbier F. An Approach Based on the Concept of Use Case to Product Dynamic Object-Oriented Specifications, In Proceedings of the Third International Symposium on Requirements Engineering, IEEE Computer Society Press, 1997, pp. 54–64Google Scholar
  31. 31.
    Gough P, Fodemski FT, Higgins SA, Ray SJ. Scenarios—An Industrial Case Study and Hypermedia Enhancements, In Proceedings of the Scnd IEEE International Symposium on Requirements Engineering, IEEE Computer Society Press, 1995, pp. 10–17Google Scholar

Copyright information

© Springer-Verlag 1997

Authors and Affiliations

  • Julio Cesar Sampaio do Prado Leite
    • 1
    Email author
  • Gustavo Rossi
    • 1
  • Federico Balaguer
    • 2
  • Vanesa Maiorana
    • 2
  • Gladys Kaplan
    • 2
  • Graciela Hadad
    • 2
  • Alejandro Oliveros
    • 2
  1. 1.Departamento de InformáticaPUC-RioRio de JaneiroBrazil
  2. 2.Dep. de InvestigaciónUniversidad de BelgranoBuenos AiresArgentina

Personalised recommendations