Using Business Rules in Extreme Requirements

  • Maria Carmen Leonardi
  • Julio Cesar Sampaio do Prado Leite
Conference paper
Part of the Lecture Notes in Computer Science book series (LNCS, volume 2348)


Extreme Requirements (XR) is a proposal that tries to improve the quality of Extreme Programming (XP). XP is a well known agile method for software production. XP key elements are: little documentation, simplicity, analysis as constant activity, evolutionary design, integration and daily test. XR defines a requirements strategy that can be coupled with XP. In this article, we present an XR business rules based process. Our process is oriented to the customer, based on natural language, facilitating construction and validation. One of the strongest aspects of our proposed process is communication with customers, making them active participants in the software production process.


Requirement Engineer Requirement Model Business Rule Agile Method Integration Scenario 
These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.


  1. 1.
    Beck, K., Extreme Programming Explained Embrace Change, Addison Wesley Longman, Inc., (2000)Google Scholar
  2. 2.
    Fowler Martin “New Methodology”,
  3. 3.
    Leite, J.C.S.P., Scenario Evolution. Dagstuhl-Seminar-Report; 199, Schloss Dagstuhl, Internationales Begegnungs-und Forschungszentrum Fur Informatik, Bui, Carrol and Jarke (editors), Alemanha, (1998) 13–14Google Scholar
  4. 4.
    Leite J.C.S.P “Extreme Requirements (XR)”, Jornadas de Ingeniería de Requisites Aplicada. Sevilla, 11 y 12 de Junio (2001)Google Scholar
  5. 5.
    Beck K., Cunningham W, “A Laboratory For Teaching Object-Oriented Thinking:” From the OOPSLA’89 Conference Proceedings October 1–6 (1989) 1–6Google Scholar
  6. 6.
    Leite, J.C.S.P, Rossi, G., Maiorana, V., Balaguer, F., Kaplan, G., Hadad, G., Oliversos, A. Enhancing a Requirements Baseline with Scenarios, Proceedings of the Third International Symposium on Requirements Engineering, IEEE Computer Society Press (1997) 44–53Google Scholar
  7. 7.
    Leite, J.C.S.P., Anchoring the Requirements Process on Vocabulary, Requirements Capture, Documentation and Validation, Dagstuhl Seminar Report-241 (1999).
  8. 8.
    Leite J.C.S.P, Leonardi Ma. Carmen, “Business rules as organizational Policies”, IEEE IWSSD9: Ninth International Workshop on Software Specification and Design, IEEE Computer Society Press (1998) 68–76Google Scholar
  9. 9.
    Gottesdiener “Business RULES Show, Power, Promise”, Application Development Trends, Vol 4, nro. 3 (1997)
  10. 10.
    Leite J.C.S.P, Oliveira A. Pádua Albuquerque. “A Customer Oriented Requirements Baseline”, Proceedings of the Second IEEE International Symposium on Requirements Engineering, IEEE Computer Society Press (1995)108–115Google Scholar
  11. 11.
    R. Wirfs-Brock, B. Wilkerson, and L. Wiener Designing Object-Oriented Software, Prentice Hall International, Englewood Cliffs, NJ, (1990)Google Scholar
  12. 12.
    Coleman et al., Object-Oriented Development The Fusion Method, Prentice Hall, Englewood Cliffs, NJ, (1994Google Scholar
  13. 13.
    Leite J, Hadad G, Doom J, Kaplan G., “A Scenario Construction Process” Requirements Engineering Journal, Springer-Verlag. Vol. 5 N1 (2000) 38–61CrossRefGoogle Scholar
  14. 14.
    Leonardi Carmen, Leite J.C.S.P, Rossi G., “Estrategias para la identificación de Reglas de Negocio”, Proceeding de Sbes98 “Simposio Brasilero de Engenharia de Software” Sociedad Brasilera de Computacao, Brasil, 14–16 de Octubre (1998) 53–67Google Scholar
  15. 15.
    Schmauch, Ch., ISO 9000 for software Developers, revised Edition, ASQC, Quality Press (1995)Google Scholar
  16. 16.
    Fiorini, S., Leite, J.C.S.P., Macedo-Soares, T., “Integrando Processos de Negocio a Elicitacao de Requisites” Revista de Informática Teorica e Aplicada, Institute de Informática da Universidade Federal do Rio Grande do Sul, Vol. IV, N. I. 7–48Google Scholar
  17. 17.
    Yu E., Modelling Strategic Relationships for Process Reingeneering, PhD Thesis, University of Toronto (1995)Google Scholar
  18. 18.
    Diaz, O., Iturrioz, J., Piattine, M., “Promoting business policies in object-oriented methods” Sesión Trabajos ya publicados: publicado en The Journal of Systems and Software, 1998. Actas de II Jomadas de Ingenieria de Software, JIS97, Dpto. de Informática, Universidad del país Vasco, San Sebastián, España (1997) 384–400Google Scholar
  19. 19.
    Leonardi Carmen, Una Estrategia de Modelado Conceptual de Objetos basada en Modelos de Requisites en Lenguaje Natural. Tesis de Magister en Ingeniería de Software, Dpto. de Informática de la Universidad Nacional de La Plata (2001)Google Scholar
  20. 20.
    Guide Business Rules Project, “Defining Business Rules-What are they are really”, (1996)
  21. 21.
    Gottesdiener Ellen “Business Rules as Requirements” Software Development. Volume 7, No. 12. December (1999)
  22. 22.
    Leite, J.C.S.P, Freeman, P. A. “Requirements Validation Through Viewpoint Resolution” IEEE Transactions on Software Engineering: Vol. 17, N. 1 (1991) 1253–1269CrossRefGoogle Scholar
  23. 23.
    Cockburn Alistair “Responsibility-based Modeling”, Technical Memo HaT TR-99.02. http://members/
  24. 24.
    Kotonya G, Sommerville I., Requirements Engineering, J. Wiley and Sons, (1998)Google Scholar
  25. 25.
    Sommerville I, Sawyer P “Requirements Engineering: A good practice guide” J. Wiley and Sons (1997)Google Scholar
  26. 26.
    Highsmith Jim and Cockburn Alistair “ Agile Software Development: The Business of Innovation”. IEEE Computer, V. 24, N. 8. 120–122Google Scholar
  27. 27.
    Brokat Advisor TM “Ruling a Self-Service World”

Copyright information

© Springer-Verlag Berlin Heidelberg 2002

Authors and Affiliations

  • Maria Carmen Leonardi
    • 1
  • Julio Cesar Sampaio do Prado Leite
    • 2
  1. 1.INTIA-UNCPBA - TandilBuenos AiresRepublica Argentina
  2. 2.Pontificia Universidade Católica do Rio de Janeiro—PUC-RioGávea-RJ Rio de JaneiroBrasil

Personalised recommendations