Acquisition of a Project-Specific Process

  • Olga Jaufman
  • Jürgen Münch
Part of the Lecture Notes in Computer Science book series (LNCS, volume 3547)


Currently, proposed development processes are often considered too generic for operational use. This often leads to a misunderstanding of the project-specific processes and its refuse. One reason for non-appropriate project-specific processes is insufficient support for the tailoring of generic processes to project characteristics and context constraints. To tackle this problem, we propose a method for the acquisition of a project-specific process. This method uses a domain-specific process line for top-down process tailoring and supports bottom-up refinement of the defined generic process based on tracking process activities. The expected advantage of the method is tailoring efficiency gained by usage of a process line and higher process adherence gained by bottom-up adaptation of the process. The work described was conducted in the automotive domain. This article presents an overview of the so-called Emergent Process Acquisition method (EPAc) and sketches an initial validation study.


Project Team Abstraction Level Process Attribute Meta Model Process Line 
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.
    Dustdar, S., Hoffmann, T., van der Aalst, W.: Mining of ad-hoc business with TeamLog, Distributed Systems Group. Technical University of Vienna (2004)Google Scholar
  2. 2.
    Becker-Kornstaedt, U., Hamann, D., Kempkens, R., Rösch, P., Verlage, M., Webby, R., Zettel, J.: The SPEARMINT Approach to Software Process Definition and Process Guidance. In: Workshop on Software Engineering over the Internet at ICSE 1998, Kyoto, Japan (April 1998)Google Scholar
  3. 3.
    Graydon, A.: ISO/IEC DTR 15504-2 Part 2: A Reference Model for Processes and Process Capability (1998) Google Scholar
  4. 4.
  5. 5.
    Humphrey, W.S.: Introduction in the TSP. Addison-Wesley, Reading (2000)Google Scholar
  6. 6.
    Jaufman, O., Dold, A., Haeberlein, T., Schlumpberger, C., Stupperich, M.: Requirements for Flexible Software Development Processes within Large and Long Taking Projects, QUATIC, Porto (2004)Google Scholar
  7. 7.
    Jaufman, O., Potznewick, S.: Suitability of the State of the Art Methods for Interdisciplinary System Development in Automotive Industry, Interdisciplinary Software Engineering (2004)Google Scholar
  8. 8.
    Jaufman, O.: Process Line Framework for the Domain of Automotive System Development. In: SPICE 2005 Conference (2005)Google Scholar
  9. 9.
    Kleiner, N.: Verbesserungsstrategien für den Workflow-Designprozess, Dissertation, University of Ulm (2004) Google Scholar
  10. 10.
    Droschel, W., Wiemers, H.: Das V-Modell 1997, Der Standard für die Entwicklung von IT-Systemen mit Anleitung für den Praxiseinsatz, Oldenbourg (German) (2000) Google Scholar
  11. 11.
    Miers, D.: The Workware Evaluation Framework, ENIX Ltd. (1996)Google Scholar
  12. 12.
    Münch, J., Schmitz, M., Verlage, M.: Tailoring großer Prozessmodelle auf der Basis von MVP-L*, 4. Workshop der Fachgruppe 5.1.1 (GI): Vorgehensmodelle – Einführung, betrieblicher Einsatz, Werkzeug-Unterstützung und Migration“, Berlin (1997)Google Scholar
  13. 13.
    Reichert, M.: Dynamic Changes in Process Management Systems. Ph.D. Thesis, University of Ulm, Faculty of Computer Science (July 2000) (in German) Google Scholar
  14. 14.
    Rombach, R.: Practical benefits of goal-oriented measurement. In: Fenton, N., Littlewood, B. (eds.) Software Reliability and Metrics. Elsevier Applied Science, London (1991)Google Scholar
  15. 15.
    Riddle, W., Schneider, H.: Coping with Process Agility. In: Tutorial at 2002 Software Engineering Process Group Conference (SEPG 2002), Phoenix, Arizona (2002)Google Scholar
  16. 16.
    Wohlin, C., Runeson, P., Höst, M., Ohlsson, M., Regnell, B., Wesslen, A.: Experimentation in Software Engineering: An Introduction. Kluwer Academic Publishers, Boston (2000)zbMATHGoogle Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 2005

Authors and Affiliations

  • Olga Jaufman
    • 1
  • Jürgen Münch
    • 2
  1. 1.DaimlerChrysler AGUlmGermany
  2. 2.Fraunhofer Institute for Experimental Software Engineering (IESE)KaiserslauternGermany

Personalised recommendations