Unifying Microprocess and Macroprocess Research

Abstract

This paper proposes the unification of two complementary approaches to software process research. The two approaches can be characterized as macroprocess research, focused on phenomenological observations of external behaviors of processes, and microprocess research, focused on the study of the internal details and workings of processes. The paper suggests that it is time to bring these approaches together with the goal of using microprocess methods to provide definitive explanations of observed macroprocess behaviors. The paper suggests that this unification could lead to improved understandings leading to improvements in software development practice. The paper observes that such positive outcomes have resulted when the macro-and micro-approaches have been synthesized in domains such as Economics, Physics, and the Life Sciences.

Effects of Architecture and Technical Development Process on Micro-process

“…This has hindered the wide adoption of rigorous development processes by developers because they do not usually find macro-processes useful for their immediate needs at a micro-level. This gap between macro-processes and micro-processes has been recognized previously [15], [13]. In this paper, we suggest that software architecture and technical development are two major factors that affect fine-grained micro-processes: 1) Software architecture is important for decomposing a system into functional modules.…”

“…In process engineering, a macro-process describes the high-level behaviours of process while micro-process describes the fine-grained internal workings of processes [15]. Current software development methodologies (such as Agile and RUP) are largely project management-centred, macro-process life cycle models.…”

Formalisms to Support the Definition of Processes

“…These "black box" approaches attempt to obtain improvements to process outputs and results without direct examination of explicit process features and details. In a previous paper this has been referred to as a "macro-process" approach [16] . This current paper will emphasize the complementary advantages obtained through "white box", or "micro-process" approaches, in which processes are observed, analyzed, and modified directly [16] .…”

Automated Recognition of Low-Level Process: A Pilot Validation Study of Zorro for Test-Driven Development

“…Osterweil has developed a view of software process research that recognizes two complementary levels: macroprocess and microprocess [6]. Macroprocess research is focused on the outward manifestations of process-the time taken, costs incurred, defects generated, and so forth.…”