Software Project Process Models: From Generic to Specific

  • Hao Wang
  • Xuke Du
  • Hefei Zhang
Part of the Lecture Notes in Electrical Engineering book series (LNEE, volume 125)


Organization Standard Software Process models are based on the assumption of similarity between projects - either cross or within a given business section. The research describes a validated reference metamodel, based on an empirical study on the commonality of different projects from various business areas. Based on the metamodel, we suggest a tailoring approach and tools for design and generation of the specific project process model.


Domain Model Process Element Software Process Software Project Role Element 
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.
    Arbaoui, S., Oquendo, F.: Reuse sensitive process models: Are process elements software assets too? In: The 10th International Software Process Workshop (1996)Google Scholar
  2. 2.
    CMMI for Development,Version 1.2. Carnegie Mellon University, Software Engineering Institute (August 2006)Google Scholar
  3. 3.
    Demirors, O., et al.: Tailoring ISO/IEC 12207 for instructional software development. In: The 26th Euromicro Conference (2000)Google Scholar
  4. 4.
    Pereira, E.B., Bastos, R.M., Oliveira, T.C.: A Systematic Approach to Process Tailoring. In: Proceedings of the 2007 International Conference on Systems Engineering and Modeling (2007)Google Scholar
  5. 5.
    Ginsberg, M.P., Quinn, L.H.: Process Tailoring and the Software Capability Maturity Model. Technical Report,SEI (November 1995)Google Scholar
  6. 6.
    Greenwood, R.M., et al.: An Asset View on the Software Process. In: The 10th International Software Process Workshop (1996)Google Scholar
  7. 7.
    Jacobson, I., Booch, G., Rumbaugh, J.: The Unified Software Development Process. Addison-Wesley Longman, Inc. (1999)Google Scholar
  8. 8.
    Rittinghouse, J.W.: Managing Software Deliverables:A Software Development Management Methodology. Digital Press (2004)Google Scholar
  9. 9.
    Motorola: Software Production Process. In: Acmc_Process_Spp_1.1.0, SPP, p. 3. Motorola Software Center, Motorola China (1998)Google Scholar
  10. 10.
    Pedreira, O., Piattini, M., Luaces, M.R., Brisaboa, N.R.: A Systematic Review of Software Process Tailoring. ACM SIGSOFT Software Engineering Notes 32(3) (May 2007)Google Scholar
  11. 11.
    Xu, P., Ramesh, B.: Using Process Tailoring to Manage Software Development Challenges. IEEE Computer Society, (July/August 2008)Google Scholar
  12. 12.
    Polo, M., et al.: MANTEMA: a Software Maintenance Methodology Based on the ISO/IEC 12207 Standard. In: The Fourth IEEE International Symposium and Forum on Software Engineering Standards (1999)Google Scholar
  13. 13.
    Polo, M., et al.: MANTEMA:a Complete Rigorous Methodology for Supporting Maintenance based on The ISO/IEC 12207 Standard. In: The Third IEEE European Conference on Software Maintenance and Reengineering (1999)Google Scholar
  14. 14.
    Pressman, R.S.: Software Engineering: A Practitioner’ s Approach. McGraw-Hill Companies, Inc., New York (2001)Google Scholar

Copyright information

© Springer-Verlag GmbH Berlin Heidelberg 2012

Authors and Affiliations

  1. 1.Beijing University of Posts and TelecommunicationsBeijingChina
  2. 2.BCI Technology Inc.BeijingChina

Personalised recommendations