Reuse, Standardization, and Transformation of Requirements

  • Miguel A. Laguna
  • Oscar López
  • Yania Crespo
Part of the Lecture Notes in Computer Science book series (LNCS, volume 3107)


Correct requirements determination is a critical factor in software development. Having stored reusable requirements elements, both qualified and classified, in a repository might contribute to reducing the error probability in requirements specifications but the diversity of requirements formats is a constraint for their reuse. To solve this problem, a common requirements model allowing the standardization and transformation of some types of requirements in others is presented. The transformations use an intermediate representation based on Petri nets, which provides rigor to the models and allows its consistency to be checked. Transformation algorithms are defined and implemented as part of a requirements management and reuse tool.


Activity Diagram Requirement Engineer Business Rule Requirement Elicitation Software Reuse 
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.


Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.


  1. 1.
    van der Aalst, W.M.P.: Three Good reasons for Using a Petri-net-basedWorkflowManagement System. In: Proceedings of the InternationalWorking Conference on Information and Process Integration in Enterprises (IPIC 1996), pp. 179–201 (1996)Google Scholar
  2. 2.
    Bass, L., Clements, P., Donohoe, P., McGregor, Linda,J., Northrop.: Fourth product line practice workshop report. Technical Report 2000-TR-002, CMU/SEI, CMU/SEI-2000-TR-002 (2000)Google Scholar
  3. 3.
    Booch, G., Rumbaugh, J., Jacobson, I.: The Unified Modeling Language User Guide. Addison–Wesley, London (1999)Google Scholar
  4. 4.
    Dardenne, A., van Lamsweerde, A., Fickas, S.: Goal directed requirements acquisition. Science of Computer Programming 20, 3–50 (1993)zbMATHCrossRefGoogle Scholar
  5. 5.
    Durn, A., Bernrdez, B., Ruiz, A., Toro, M.: A Requirements Elicitation Approach Based in Templates and Patterns. In: WER 1999 Proceedings, Buenos Aires (1999)Google Scholar
  6. 6.
    Ecube, E., Lpez, O., Laguna, M.A.: Transformaci n de requisitos. Technical Report DI-2004-1, Dep. of Computer Science, University of Valladolid, avalaible (2004), at
  7. 7.
    Frakes, W., Isoda, S.: Success factors of systematic reuse. IEEE Software 11(5), 15–18 (1994)CrossRefGoogle Scholar
  8. 8.
    Francisco, J.,Garca.: Modelo de Reutilizaci n Soportado por Estructuras Complejas de Reutilizaci n Denominadas Mecanos. PhD thesis, Universidad de Salamanca (2000)Google Scholar
  9. 9.
    Griss, M.L., Favaro, J., D’Alessandro, M.: Integrating feature modeling with RSEB. In: Proceedings of the Fifth International Conference on Software Reuse (ICSR-5), Victoria, B. C., Canada, pp. 76–85. IEEE Computer Society, IEEE Press (1998)Google Scholar
  10. 10.
    Jacobson, I., Christerson, M., Jonsson, P., vergaard, G.: Object–Oriented Software Engineering: A Use Case Driven Approach, 4th edn. Addison–Wesley, London (1993)Google Scholar
  11. 11.
    Kang, K.C., Cohen, S.G., Hess, J.A., Novak, W.E., Peterson, A.S.: Feature-Oriented Domain Analysis (FODA). Feasibility study. Technical Report CMU/SEI-90-TR21 (ESD- 90-TR-222), Software Engineering Institute, Carnegie-Mellon University, Pittsburgh, Pennsylvania 15213 (November 1990)Google Scholar
  12. 12.
    Laguna, M.A., Marqus, J.M., Garca, F.J.: A user requirements elicitation tool. ACM SIGSOFT Software Engineering Notes 26(2), 35–37 (2001)CrossRefGoogle Scholar
  13. 13.
    Lee, K., Kang, K., Chae, W., Choi, B.: Feature-based approach to object-oriented engineering of applications for reuse. Software-Practice and Experience 30(9), 1025–1046 (2000)CrossRefGoogle Scholar
  14. 14.
    Lee, W.J., Cha, S.D., Kwon, Y.R.: Integration and Analysis of Use Cases Using Modular Petri Nets in Requirement Engineering. IEEETransactions on Software Engineering 24(12), 1115–1130 (1998)CrossRefGoogle Scholar
  15. 15.
    López, O.: Reutilizaci n de Requisitos para Incremento de la Calidad y Productividad en el Desarrollo de Especificaciones. PhD thesis, Universidad de Valladolid, Spain (2003)Google Scholar
  16. 16.
    López, O., Laguna, M.A., Garca, F.J.: Automatic generation of use cases from workflows: A petri net based approach. In: Kutsche, R.-D., Weber, H. (eds.) FASE 2002. LNCS, vol. 2306, pp. 279–293. Springer, Heidelberg (2002)CrossRefGoogle Scholar
  17. 17.
    Lowry, M., Duran, R.: Knowledge-Based Software Engineering. In: The Handbook of Artificial Intelligence, pp. 241–322. Addison-Wesley, Reading (1989)Google Scholar
  18. 18.
    Moriarty, T.: Business rule analysis. Database Programming & Design 6(4), 66–69 (1993)Google Scholar
  19. 19.
    Mylopoulos, J., Chung, L., Yu, E.: From object-oriented to goal-oriented requirements analysis. Communications of the ACM 42(1), 31–37 (1999)CrossRefGoogle Scholar
  20. 20.
    Pohl, K.: Requirements engineering: An overview. Technical Report TR 96/2, CREWS (1996)Google Scholar
  21. 21.
    Poulin, J.S.: Integrated support for software reuse in computer-aided software engineering (CASE). ACM SIGSOFT Software Engineering Notes 18(4), 75–82 (1993)CrossRefGoogle Scholar
  22. 22.
    Sawyer, P., Kontoya, G.: Software Requirements, in Guide to the Software Engineering Body of Knowledge, Version 0.95. Technical report (May 2001),
  23. 23.
    WfMC.Workflowmanagement coalition terminology and glossary. Technical ReportWFMCTC- 1011,Workflow Management Coalition, Brussels, 1996

Copyright information

© Springer-Verlag Berlin Heidelberg 2004

Authors and Affiliations

  • Miguel A. Laguna
    • 1
  • Oscar López
    • 2
  • Yania Crespo
    • 1
  1. 1.University of ValladolidValladolidSpain
  2. 2.Technological Institute of Costa RicaCartagoCosta Rica

Personalised recommendations