Building Software Process Line Architectures from Bottom Up

  • Hironori Washizaki
Part of the Lecture Notes in Computer Science book series (LNCS, volume 4034)


In this paper, we propose a technique for establishing process lines, which are sets of common processes in particular problem domains, and process line architectures that incorporate commonality and variability. Process line architectures are used as a basis for deriving process lines from the perspective of overall optimization. The proposed technique includes some extensions to the Software Process Engineering Metamodel for clearly expressing the commonality and variability in the process workflows described as UML activity diagrams. As a result of applying the proposed technique to hardware/software co-design processes in an embedded system domain, it is found that the proposed technique is useful for defining consistent and project-specific processes efficiently.


Optional Element Variation Point Core Process Process Line Project Characteristic 
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.
    Jaufman, O., Munch, J.: Acquisition of a Project-Specific Process. In: Bomarius, F., Komi-Sirviö, S. (eds.) PROFES 2005. LNCS, vol. 3547, pp. 328–342. Springer, Heidelberg (2005)CrossRefGoogle Scholar
  2. 2.
    Rombach, D.: Integrated Software Process and Product Lines. In: Li, M., Boehm, B., Osterweil, L.J. (eds.) SPW 2005. LNCS, vol. 3840, pp. 83–90. Springer, Heidelberg (2006)CrossRefGoogle Scholar
  3. 3.
    Mi, P., et al.: A Knowledge-based Software Process Library for Process-Driven Software Development. In: 7th Knowledge-Based Software Engineering Conference (1992)Google Scholar
  4. 4.
    Matsumoto, Y.: Japanese Software Factory. In: Marciniak, J.J. (ed.) Encyclopedia of Software Engineering. John Wiley & Sons, Chichester (1994)Google Scholar
  5. 5.
    OMG: Software Process Engineering Metamodel Specification, Version 1.1 (2005)Google Scholar
  6. 6.
    Ocampo, A., Bella, R., Munch, J.: Software Process Commonality Analysis. Software Process Improvement and Practice 10(3) (2005)Google Scholar
  7. 7.
    Trigaux, J.C., Heymans, P.: Modelling variability requirements in Software Product Lines, Technical report PLENTY project (2003)Google Scholar
  8. 8.
    Wolf, W.H.: Computer as Components: Principles of Embedded Computing System Design. Morgan Kaufmann, San Francisco (2001)Google Scholar
  9. 9.
    Axelsson, J.: Hardware/Software Partitioning of Real-Time Systems. IEE Colloquium on Partitioning in Hardware-Software Codesigns (1995)Google Scholar
  10. 10.
    Kassner, K.C., Ricks, K.G.: Hardware/Software Co-Design of Embedded Real-Time Systems from an Undergraduate Perspective. In: Workshop on Computer Architecture Education (2005)Google Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 2006

Authors and Affiliations

  • Hironori Washizaki
    • 1
  1. 1.National Institute of InformaticsTokyoJapan

Personalised recommendations