Minh Ngoc Nguyen and Reidar Conradi. Classification of Meta-processes and Their Models. In [22], 1994. 167--175.  Home/Search   Document Details and Download   Summary   Related Articles   Check

....description of a software process allows its understanding, verification and enaction. A SEE which supports the definition and enaction of software process models is called a process centered SEE and must support software development without restricting human creativity and work organization [NGU 94] 3. The PROSOFT Software Engineering Environment PROSOFT is a software development environment built to support the formal development of software, providing the data, control and presentation integration between the tools developed under its paradigm. Thus, PROSOFT is a framework for software ....

NGUYEN, M.; CONRADI, R. Classification of Meta-processes and their models. In: INTERNATIONAL CONFERENCE ON SOFTWARE PROCESS. 3., 1994, Washington. Proceedings... Washington: IEEE Computer Society Press, 1994.

....above the PROGRES level in order to generate routine parts of a PROGRES specification [21] In this paper, we have focused on feedback handling at the instance level, i.e. within software production processes. We have considered neither the meta process of developing process models (see e.g. [26, 27]) nor the interactions between meta process and production process. Several authors apply the term feedback to the control loop between meta process and production process (see e.g. feedback modifications in MELMAC [13] In particular, implementation of the control loop requires some means to ....

M. N. Nguyen and R. Conradi. Classification of Meta Processes and their Models. In Proceedings of the 3rd International Conference on the Software Process, pages 167--175, Washington, 1994. IEEE Computer Society Press.

....as a process model [Curtis92, Armenise92] that is analyzed [Gruhn92] in order to determine their correctness. Then, a process model is instantiated creating a process instance which is enactable by the PSEE. During runtime a process is monitored [Huff93] and evolved if changes are required [Nguyen94, Bandinelli94]. This means a PSEE provides the above described effective way for problem solving. This is especially important in software engineering due to the complexity of large software projects. 3.2 A PSEE may provide cooperation and coordination support during software development Clarence Ellis et al. ....

Nguyen, M. N., Conradi, R., "Classification of Meta-processes and their Models", Proc. Third Int. Conference on the Software Process (ICSP-3), 1994, IEEE CS Press.

....evolution aspects [10] Within this context the meta process is seen as a life cycle aiming at define, describe, enact and improve PM. For example, Process Cycle [11] or Prism [12] give a detailed description of the PM life cycle. Recent works on conceptual frameworks for process evolution like [13] or [14] identify general requirements and methods to support the meta process. In [13] the authors establish a taxonomy to characterize the meta process and assess five european PSEEs against this taxonomy. In [14] the authors make a first step towards reconciliation of process and process model ....

....aiming at define, describe, enact and improve PM. For example, Process Cycle [11] or Prism [12] give a detailed description of the PM life cycle. Recent works on conceptual frameworks for process evolution like [13] or [14] identify general requirements and methods to support the meta process. In [13] the authors establish a taxonomy to characterize the meta process and assess five european PSEEs against this taxonomy. In [14] the authors make a first step towards reconciliation of process and process model evolution at the meta process level. Requirements for inconsistency management between ....

M. Nguyen and R. Conradi. "Classification of Meta-processes and their Models." In Proceedings of the 3rd International Conference on the Software Process. IEEE Computer Society Press, October 1994.

....evolution entities: Software Releases, Software Systems Under Development, Application Domains, Development Process, and the Process Model. The paper also describes the evolutionary characteristics of each of these entities. However, the discussion is in a very abstract manner. On the other hand, [18] proposes a functional framework (neither too abstract, nor in operational details) to classify process evolution and link evolution patterns to different project profiles. The evolution characteristics are: where (origin) why (cause) what (process element) when (phase) how (kind of change) ....

Minh Ngoc Nguyen and Reidar Conradi. Classification of Meta-processes and Their Models. In [22], 1994. 167--175.

....missing features, and generally poor quality. That is, we need to improve both ability to predict plan changes based upon previous experiences and adequate support for managing unexpected changes when they first arrive. Our earlier work on categorizing the evolutionary aspects of software process [NC94a] has been elaborated putting emphasis in classifying changes and their impact on project outcome into recognizable evolution patterns. Such patterns together with typical project context characteristic will effectively contribute to improving planning process. By doing so, the number of ....

....technology availability, and unanticipated delay distortion, also influence and drive process evolution. 3. 2 Categorization framework for process evolution In this section we briefly describe our categorization framework for process evolution which is an elaboration of our previous work in [NC94a] Our framework depends on where, why, what, when, how and by whom process changes are introduced. Those six dimensions are then hierarchically decomposed to such extent that leaves space for flexibility and future extensions. Where: identifies the sources of process change requests. From section ....

Minh N. Nguyen and Reidar Conradi. Classification of Meta-processes and their Models. In Proc. from the third International Conferenceon Software Process, Washington, USA, 10-11 October, pages167--175, 1994.

....evolution entities: Software Releases, Software Systems Under Development, Application Domains, Development Process, and the Process Model. The paper also describes the evolutionary characteristics of each of these entities. However, the discussion is in a very abstract manner. On the other hand, [19] proposes a functional framework (neither too abstract, nor in operational details) to classify process evolution and link evolution patterns to different project profiles. The evolution characteristics are: where (origin) why (cause) what (process element) when (phase) how (kind of change) ....

Minh Ngoc Nguyen and Reidar Conradi. Classification of Meta-processes and Their Models. In [23], 1994. 167--175.

....claimed to be a characteristic feature of successful companies. We need to improve our ability to predict, plan and manage changes based upon previous experiences. Adequate enactment support for process changes, embedded in a PSEE, is also considered necessary and desirable. Our previous work [NC94] has been revised to contain a classification of process change and their impact on the enacting process (project) in the form of recognizable evolution patterns. Such patterns associated with typical project and product profiles will contribute to building an empirical base. By utilizing this ....

Minh N. Nguyen and Reidar Conradi. Classification of Meta-processes and their Models. In Proc. from the third International Conference on Software Process, Washington, USA, 10-11 October, pages 167-- 175, 1994.

Online articles have much greater impact   More about CiteSeer.IST   Add search form to your site   Submit documents   Feedback  

CiteSeer.IST - Copyright Penn State and NEC