Advertisement

Software Process and Reuse: A Required Unification

  • Miguel A. Laguna
  • Bruno González-Baixauli
  • Oscar López
  • Francisco J. García
Conference paper
  • 307 Downloads
Part of the Lecture Notes in Computer Science book series (LNCS, volume 2817)

Abstract

Conventional software processes such as the Unified Process do not include reuse techniques among their disciplines. In this article, we present an extension of the Unified Process that introduces software reuse with minimal disturbance by means of the definition of a new process for product line engineering and the adaptation of standard disciplines for specific product construction. This proposal reduces the money and time costs related to the progressive introduction of software reuse in an organization. Some tools that provide support to the process, including a requirement reuse tool and a repository of reusable elements, have been developed.

Keywords

Product Line Asset Management Software Reuse Reference Architecture Product Line Engineering 
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.

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

References

  1. 1.
    Bass, L., Clements, P., Donohoe, P., McGregor, J., Northrop, L.: Fourth Product Line Practice Workshop Report. Technical Report CMU/SEI-2000-TR-002 (ESC-TR-2000- 002), Software Engineering Institute. Carnegie Mellon University, Pittsburgh, Pennsylvania, USA (2000)Google Scholar
  2. 2.
    Beck, K.: Extreme Programming Explained. Addison-Wesley, Reading (2000)Google Scholar
  3. 3.
    Bosch, J.: Design & Use of Software Architectures. Adopting and Evolving a Product-Line Approach. Addison-Wesley, Reading (2000)Google Scholar
  4. 4.
    Chastek, G., Donohoe, P., Kang, K.C., Thiel, S.: Product Line Analysis: A Practical Introduction. Technical Report CMU/SEI-2001-TR-001 ESC-TR-2001-001, Software Engineering Institute (Carnegie Mellon), Pittsburgh, PA 15213 (2001)Google Scholar
  5. 5.
    Curto, B., García, F.J., Moreno, V., González, J., Moreno, Á.: Ma: An Experience of a CORBA Based Architecture for Computer Integrated Manufacturing. In: proceedings of 8th IEEE International Conference on Emerging Technologies and Factory Automation – ETFA 2001, Antibes – Juan les Pins, France, October 15-18, pp. 765–769. IEEE Press, Los Alamitos (2001)CrossRefGoogle Scholar
  6. 6.
    García Peñalvo, F.J.: Modelo de Reutilización Soportado por Estructuras Complejas de Reutilización Denominadas Mecanos. Ph. D. Dissertation, in Spanish. Universidad de Salamanca (2000)Google Scholar
  7. 7.
    García, F.J., Barras, J.A., Laguna, M.A., Marqués, J.M.: Product Line Variability Support by FORM and Mecano Model Integration. ACM Software Engineering Notes 27(1), 35–38 (2002)Google Scholar
  8. 8.
    González-Baixauli, B., Laguna, M.A.: Software Process Specification for Product Line Approach. Technical Report DI-2003-0001, Computer Science Department, University of Valladolid, Spain (2003)Google Scholar
  9. 9.
    International Organization for Standardization: Information technology – Software life cycle processes – Amendment 1. ISO/IEC 12207/Amd1 (2002)Google Scholar
  10. 10.
    Jacobson, I., Griss, M., Jonsson, P.: Software Reuse. In: Architecture, Process and Organization for Business Success, ACM Press. Addison Wesley Longman (1997)Google Scholar
  11. 11.
    Jacobson, I., Booch, G., Rumbaugh, J.: The Unified Software Development Process. Object Technology Series. Addison-Wesley, Reading (1999)Google Scholar
  12. 12.
    Kang, K.C., Kim, S., Lee, J., Kim, K.: FORM: A Feature-Oriented Reuse Method with Domain-Specific Reference Architectures. Annals of Software Engineering 5, 143–168 (1998)CrossRefGoogle Scholar
  13. 13.
    Karlsson, E.-A. (ed.) Software Reuse. A Holistic Approach. Wiley Series in Software Based Systems, John Wiley and Sons Ltd., Chichester (1995)Google Scholar
  14. 14.
    Knauber, P., Succi, G.: Perspectives on Software Product Lines. ACM Software Engineering Notes 26(2), 29–33 (2001)CrossRefGoogle Scholar
  15. 15.
    Kuusela, J., Savolainen, J.: Requirements Engineering for Product Families. In: Proceedings of 22nd International Conference on Software Engineering – ICSE 2000, pp. 60–68. ACM Press, New York (2000)Google Scholar
  16. 16.
    Lee, K., Kang, K.C., Chae, W., Choi, B.W.: Feature-Based Approach to Object- Oriented Engineering of Applications for Reuse. Software: Practice and Experience 30(9), 1025–1046 (2000)CrossRefGoogle Scholar
  17. 17.
    Object Management Group: Software Process Engineering Metamodel Specification. Final Adopted Specification. Object Management Group Inc. (2001) Google Scholar
  18. 18.
    Paulk, M.C., Curtis, B., Chrissis, M.B., Weber, C.V.: Capability Maturity Model, Version 1.1. IEEE Software 10(4), 18–27 (1993)CrossRefGoogle Scholar
  19. 19.
    Reifer, D.J.: Practical Software Reuse. Wiley, Chichester (1997)zbMATHGoogle Scholar
  20. 20.
    Simos, M., Creps, D., Klingler, C., Levine, L., Allemang, D.: Organization Domain Modeling (ODM) Guidebook – Version 2.0. Technical Report STARS-VC-A025/001/00, Lockheed Martin Tactical Defense Systems, 9255 Wellington Road Manassas, VA 22110- 4121 (1996)Google Scholar
  21. 21.
    Smith, J.: A Comparison of RUP® and XP. Rational Software White Paper. Technical Paper TP –167 (2001)Google Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 2003

Authors and Affiliations

  • Miguel A. Laguna
    • 1
  • Bruno González-Baixauli
    • 1
  • Oscar López
    • 2
  • Francisco J. García
    • 3
  1. 1.Department of Computer ScienceUniversity of ValladolidValladolidSpain
  2. 2.Technological Institute of Costa RicaSan Carlos Regional CampusCosta Rica
  3. 3.Department of Computer ScienceUniversity of SalamancaSpain

Personalised recommendations