G. Joeris, "Change Management Needs Integrated Process and Configuration Management", LNCS, Vol. 3101, pp. 125-141,1997.  Home/Search   Document Details and Download   Summary   Related Articles   Check

....[25, 5] and workflow history management [14] Our approach to traces is property based, i.e. they are in essence versioned and materialized views on the properties and the review procedure. For a detailed discussion of the relationship between document, version, and process models see [12]. For added organizational value, traces are stored in a database [22] maintained by the docket framework. It allows queries on the trace extent which provide a basis for data warehousing over content oriented value chains. Eachdocket performer may get a specific variant of the trace and may use ....

Joeris, G.: Change Management Needs Integrated Process and Configuration Management. ESEC/SIGSOFT FSE (1997) 125-141

.... the next section on the integration of the versioning concept rather than on details of the modeling constructs (details can be found in [30] We disregard also the integration of document, version, and workspace management capabilities in our approach which support collaborative workflows (see [27, 28] for details) Furthermore, all elements of the organizational sub model are omitted in this paper. 3.1 Task and Process definition 3.1.1 Task Definition and Task Interface A task definition (or task type) is separated into the definition of the task interface which specifies what is to do , ....

....correctness criteria. In particular, human actors can react very flexibly on changes of the context of a task. The integration of version and workspace control capabilities substantially supports adequate reactions to workflow changes in the case of manual and cooperative tasks. We refer to [27, 28, 31] for an overview on this aspects. 16 5.2 Performing Complex Workflow Changes 5.2.1 (Re)Engineering of Workflow Schemata Whereas the structural and behavioral consistency of a workflow change can be ensured by an (atomic) change operation, the semantical correctness cannot be guaranteed ....

Joeris, G.: Change Management Needs Integrated Process and Configuration Management. In Jazayeri, M; Schauer, H (eds.), Software Engineering - ESEC/FSE'97, Proceedings, LNCS 1301, Springer Verlag, pp. 125-141 (1997).

....and their versions, and organizational aspects in order to capture the different aspects of processes. We concentrate in the following on the modeling and enacting of tasks and workflows and disregard the integration of document, version, and workspace management capabilities in our approach (see [15, 16] for details) Furthermore, all elements of the organizational sub model are omitted in this paper. We introduce our object model step by step starting with the definition of task types: 3.1 Task Definition and Task Interface First of all, a task definition (or task type) is separated into the ....

Joeris, G.: "Change Management Needs Integrated Process and Configuration Management ", in Jazayeri, M; Schauer, H (eds.), Software Engineering - ESEC/FSE'97, Proceedings, LNCS 1301, Springer, 1997; pp. 125-141.

....instance elements are modeled as first level objects and their relationships are explicitly maintained. Following the principle of separation of concerns, we divide the overall model into sub models for tasks and workflow, documents and their versions, resources, and organizational units (see [14] for a detailed overview) In the following, we focus only on the modeling of tasks and their flow structure (as illustrated in Fig. 2) and concentrate in the next section on the integration of the versioning concept rather than on details of the modeling constructs. 3.1 Task and Workflow ....

Joeris, G.: "Change Management Needs Integrated Process and Configuration Management", in Jazayeri, M; Schauer, H (eds.), Software Engineering - ESEC/FSE'97, Proceedings, LNCS 1301, Springer, 1997; pp. 125-141.

....the functional and behavioral perspective. Furthermore, these separation supports a clear definition of the interrelationships between these spaces leading to a well defined and tightly integrated overall process model (for details of interrelationships between repository and process space see [16]) Artifact Process Task SubProcess Resource Passive Active Tool Human Role Class Organisational Space Resource Space Process Space Repository Space Figure 1: Modeling Spaces and Abstract Process Meta Model Object oriented concepts are well suited to enliven these spaces since they rely on a ....

Joeris, G.: Change Management Needs Integrated Process and Configuration Management. To appear in the proc. of the European Software Engineering Conference (ESEC'97), 1997.

....of abstraction (cf. JaBu96] 3. Object Oriented Modeling of Processes We start introducing our approach with some remarks on the terminology employed: A process encompasses all aspects of performing a task, at least the informational, organizational, functional, and behavioral aspects (cf. [CKO92, JaBu96, Joe97b]) Further, we summarize the functional view (what a task provides) and the behavioral view (how it is done) under the notion workflow aspect and use task and workflow in a similar and informal way. Thus, we use a process in a broader and workflow in a narrow sense. A process is defined within a ....

....processes, such an approach is not applicable for functional (object transformation) processes. Further, a general process modeling methodology should take into account the dual perspective of workflow and data models on a process and hence cannot be based on a pure object oriented method [Joe97b, EDA97]. On the other hand, object oriented modeling techniques are well suited to provide uniform and powerful representation capabilities for the different aspects of a process since they rely on a natural way of identifying and encapsulating existing entities. Furthermore, OO techniques like ....

[Article contains additional citation context not shown here]

Joeris, G.: "Change Management Needs Integrated Process and Configuration Management ", in Jazayeri, M; Schauer, H (eds.), Software Engineering - ESEC/FSE'97, Proceedings, LNCS 1301, Springer, 1997; pp. 125-141.

.... ( 8] Conceptual Framework To define a terminological basis for our consideration, we adopt and integrate the basic notions from software process and configuration management, respectively (cf. 6] 15] This leads to a conceptual framework for integrated model based approach, as proposed in [12]: First, we adopt the notions repository, product, version, and work space (cf. Figure 2) The repository space is defined by a product or document model. It defines the structure, i.e. the composition of documents and their dependencies, and the properties of a document (denoted as the product ....

....well as controlled interoperability by means of process and product management services which control the task and work spaces of a work environment. 4. Classification of Integration Approaches Integrated process and product management approaches are best to be found in software engineering (see [12] for a detailed overview) We classify these approaches on a conceptual level with respect to the integration of their modeling languages for processes and products, respectively. We distinguish between five classes which are further categorized into activity and productcentered integration ....

Joeris, G.: "Change Management Needs Integrated Process and Configuration Management", to appear in Proc. of the 6 th European Software Engineering Conference (ESEC'97), 1997

No context found.

G. Joeris, "Change Management Needs Integrated Process and Configuration Management", LNCS, Vol. 3101, pp. 125-141,1997.

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