Effects of Architecture and Technical Development Process on Micro-process

Current software development methodologies (such as agile and RUP) are largely management-centred, macro-process life-cycle models. While they may include some fine-grained micro-process development practices, they usually provide little concrete guidance on appropriate microprocess level day-to-day development activities. The major factors that affect such micro-process activities are not well understood. We propose that software architecture and technical development processes are two major factors. We describe how these two factors affect micro-process activities. We validate our claim by mining micro-processes from two commercial projects and investigating relationships with software architecture and technical development processes.

[1]  Jürgen Münch.  Transformation-based Creation of Custom-tailored Software Process Models , 2004, ICSE 2004.

[2]  H. Dieter Rombach.  Integrated Software Process and Product Lines , 2005, ISPW.

[3]  Rick Kazman,et al.  From requirements negotiation to software architecture decisions , 2005, Inf. Softw. Technol..

[4]  D. Ross Jeffery.  Exploring the Business Process-Software Process Relationship , 2006, SPW/ProSim.

[5]  Leon J. Osterweil,et al.  Unifying Microprocess and Macroprocess Research , 2005, ISPW.

[6]  Tu Tak Tran.  An Interim Report of XML Process Models , 2006 .

[7]  D. Ross Jeffery,et al.  A Systematic Approach to Process Enactment Analysis as Input to Software Process Improvement or Tailoring , 2006, 2006 13th Asia Pacific Software Engineering Conference (APSEC'06).

[8]  Martin Höst,et al.  A Qualitative Methodology for Tailoring SPE Activities in Embedded Platform Development , 2005, PROFES.

[9]  Li,et al.  Unifying the Software Process Spectrum , 2006 .

[10]  Maurizio Morisio,et al.  COTS-based software development: Processes and open issues , 2002, J. Syst. Softw..

[11]  Dietmar Pfahl,et al.  Special issue on ProSim 2004, The 5th International Workshop on Software Process Simulation and Modeling, Edinburgh, Scotland, May 2004 , 2005, Softw. Process. Improv. Pract..

[12]  Jürgen Münch,et al.  Software process commonality analysis , 2005, Softw. Process. Improv. Pract..

[13]  L. Osterweil,et al.  Programming Rework in Software Processes , 2002 .

[14]  Dietmar Pfahl,et al.  Software Process Change, International Software Process Workshop and International Workshop on Software Process Simulation and Modeling, SPW/ProSim 2006, Shanghai, China, May 20-21, 2006, Proceedings , 2006, SPW/ProSim.

[15]  Liming Zhu,et al.  Tool support for just-in-time architecture reconstruction and evaluation: an experience report , 2005, Proceedings. 27th International Conference on Software Engineering, 2005. ICSE 2005..

[16]  Jürgen Münch,et al.  Acquisition of a Project-Specific Process , 2005, PROFES.

[17]  Hironori Washizaki.  Building Software Process Line Architectures from Bottom Up , 2006, PROFES.

[18]  Geir Kjetil Hanssen,et al.  Tailoring RUP to a Defined Project Type: A Case Study , 2005, PROFES.

[19]  D. Ross Jeffery.  Achieving Software Development Performance Improvement Through Process Change , 2005, ISPW.

[20]  Barry W. Boehm,et al.  Process Elements: Components of Software Process Architectures , 2005, ISPW.

[21]  D. Ross Jeffery,et al.  An exploratory study of process enactment as input to software process improvement , 2006, WoSQ '06.

[22]  Stuart Anderson,et al.  Requirements Evolution from Process to Product Oriented Management , 2001, PROFES.