Lonchamp, J., "CPCE: A Kernel for Building Flexible Collaborative Process-Centred Environments," in Procs of the 7th Conference on Software Engineering Environments, Netherlands, April 1995, IEEE CS Press, pp. 95-105.  Home/Search   Document Details and Download   Summary   Related Articles   Check

.... to partially keep design and code consistent [33, 30] Federated approaches use a database, such as PCTE, spread over several locations [4] Tools supporting collaboration between multiple users include ConversationBuilder [19] and GroupKit [29] Process centred environments include CPCE [20] and Marvel [3] None of these has satisfactorily solved all of the above problems. We describe a heterogeneous approach to ISDE production. Tools supporting related aspects of software development are integrated via hierarchical repositories which support flexible, bi directional consistency ....

Lonchamp, J., "CPCE: A Kernel for Building Flexible Collaborative Process-Centred Environments," in Procs of the 7th Conference on Software Engineering Environments, Netherlands, April 1995, IEEE CS Press, pp. 95-105.

.... of concept structures behind PMLs (process ontologies) can be defined in MetaEdit (Koskinen and Marttiin, 1997) and OVAL (Malone et al. 1995) Some concept adaptation can also be achieved through specialising generic process classes or types into application specific ones, e.g. in CPCE (Lonchamp, 1995), EPOS (Jaccheri and Conradi, 1993) and SPADE (Bandinelli et al. 1993) Process modelling (with process instantiation) is divided into process template customisation, enactable model customisation (i.e. various project specific models for the same template) and enacting model customisation ....

Lonchamp, J. 1995. CPCE: A Kernel for Building Flexible Collaborative Process-Centered Environments. In: Procs. of the Software Engineering Environments, IEEE Computer Society Press, 28-41.

....but these usually only inform collaborators about the work artefacts of immediate interest, not their overall work contexts. Process centred software engineering environments utilise information about software processes to enforce or guide software development. Examples include Marvel [1] CPCE [10], and ConversationBuilder [8] These environments usually provide low level text based descriptions of work rationale, and often do not effectively handle restructuring of software processes while in use [14] Workflow based systems attempt to coordinate work by describing the flow of documents ....

Lonchamp, J. CPCE: A Kernel for Building Flexible Collaborative Process-Centred Environments. In Procs of the 7th Conference on Software Engineering Environments, IEEE CS Press, 1995, pp. 95-105.

....data and control integration. Unfortunately these approaches alone do not provide adequate process integration on large scale projects. Tools supporting collaboration between multiple users include ConversationBuilder [24] wOrlds [25] and GroupKit [35] Process centred environments include CPCE [26], Oz [20] SPADE [1] and ProcessWEAVER [6] The process centred environments tend to support process integration well, as they support the coordinated use of multiple tools. But they often do not adequately support other aspects of tool integration, as it can be very difficult to tightly integrate ....

Lonchamp, J., "CPCE: A Kernel for Building Flexible Collaborative Process-Centred Environments," In Proceedings of the 7th Conference on Software Engineering Environments, IEEE CS Press, Netherlands, April 1995, pp. 95-105.

....actions to carry out based on a range of possible events. Our visual event handling language provides a much wider range of capabilities, but remains accessible to both novice and expert end users. Many Process Centred Environments (PCEs) such as SPADE [1] Merlin [29] Marvel [2] Oz [4] CPCE [25], and EPOS [22] use complex, textual descriptions of processes and tool configurations which are often very difficult for end users to understand and modify, often can not be modified while in use, and have poor exception handling. The event handling of most graphical process modelling languages ....

Lonchamp, J., "CPCE: A Kernel for Building Flexible Collaborative Process-Centred Environments," in Proceedings of the 7th Conference on Software Engineering Environments, IEEE CS Press, 1995, pp. 95-105.

....only inform collaborators about the work artefacts collaborators are immediately interested in and do not provide the context of others work. Process centred environments utilise information about software processes to enforce or guide development. Examples include Marvel (Barghouti 1992) CPCE (Lonchamp et al. 1995), and ConversationBuilder (Kaplan et al. 1992) Computer Aided Method Engineering (CAME) tools, such as Decamerone (Harmsen and Brinkkemper 1995) and Method Base (Saeki et al. 1993) provide support for configuring development processes and tools to a particular application. These approaches ....

Lonchamp, J. (1995). "CPCE: A Kernel for Building Flexible Collaborative ProcessCentred Environments," In Proceedings of the 7th Conference on Software Engineering Environments (Noordwijkerhout, Netherlands, April 5-7), IEEE CS Press, pp. 95-105.

....of graphical expression for users, and is generally more flexible, able to be driven by all kinds of process model, tool or artefact update events. Process Centred Environments (PCEs) define the processes used to construct software systems. Examples include Merlin [26] Marvel [2] Oz [3] CPCE [21], and EPOS [17] Computer Aided Method Engineering (CAME) tools support evolution of the methodologies and notations used for software development. Examples include Decamerone [15] and MethodBase [28] Many of these environments use complex, textual descriptions of processes and tool ....

Lonchamp, J., "CPCE: A Kernel for Building Flexible Collaborative Process-Centred Environments," in Procs. of the 7th Conference on Software Engineering Environments, IEEE CS Press, 1995, pp. 95-105.

....changes to NIAM or OOA D relationship changes. Thus changes which can not be automatically translated to another notation are not supported. Process centred environments utilise information about software processes to enforce or guide development. Examples include Marvel (Barghouti, 1992) CPCE (Lonchamp, 1995), and ConversationBuilder (Kaplan, 1992) These environments usually provide low level text based descriptions of work rationale, and often do not effectively handle restructuring of development processes while in use (Swenson, 1993) ProcessMaker (Mark, 1995b) supports the definition and use of ....

Lonchamp, J. (1995) CPCE: A Kernel for Building Flexible Collaborative Process-Centred Environments, in Proceedings of the 7th Conference on Software Engineering Environments, IEEE CS Press, Netherlands, April 5-7 1995, pp. 95-105.

....of the process model, make the system play an active role, by taking constructive or corrective initiatives, guide the participants, by informing them about what to do next, by reporting on the current process state, by explaining system initiatives, etc. We have prototyped a PCE kernel [3], named CPCE ( Collaborative Process Centered Environment ) to support asynchronous collaborative work. The first two dedicated environments, built on top of this kernel, support a collaborative brainstorming process [4] and a collaborative review inspection process [5] 2. The PCE must support ....

....or to the process model itself, in the context of the model driven meta process. Within both contexts, CPCE kernel currently provides simple model based control, guidance, and partial automation. Implementation details and comparisons with related approaches and systems can be found elsewhere [3, 5, 6]. Our current work aims at: integrating negotiations and negotiated contracts support within the generic kernel, enriching the meta model, by creating explicit decision and assumption classes and by allowing the hierarchical decomposition of phases and issues, enriching control, ....

J. Lonchamp, `CPCE: A Kernel for Building Flexible Collaborative Process-Centered Environments', Proc. SEE'96, Nordwijkerhout, IEEE Press, pp 95-105, 1995.

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