DSEEP process authoring made easy Tom van den Berg Brad Dillman TNO, The Netherlands DRDC, Canada

Outline Authoring issues Eclipse Process Framework Composer Possible implementations Use cases Discussion Conclusion

Authoring issues Different representations make integration difficult Difficulty in keeping descriptions up to date Lack of easy navigation No support for tailoring process descriptions Lack of sharing of practices

A possible solution SPEM (Systems Process Engineering Metamodel) as a model to capture content EPF (Eclipse Process Framework) Composer as a tool for authoring, tailoring and deploying development processes and practices Examples of available content: OpenUP, XP SCRUM, RUP TOGAF RUP-SE/DODAF

Eclipse Process Framework Composer EPF Composer: http://www.eclipse.org/epf Functions for authoring, configuring, viewing, tailoring … Key concepts: Method content and process content Method library, plug-in, content/process package

EPF: Method Content Work product Role Task and step Guidance, Category Library Method Content

EPF: Process Content Phase, Iteration, Milestone Activity Delivery Process Capability Pattern Method Library Process Content

EPF: Method Library Method library Method plug-in Method content package Method process package Method Library Plugins Method Content Process Content

Library view Element Content Method Process Configuration view Tabs Perspective Library view Element Content Method Process Rich text editor Configuration view Tabs

Library view Preview Element Content Preview Tab

Library view Element Content Method Process Configuration view Tabs Perspective Library view Element Content Method Process Configuration view Tabs

Possible implementations DSEEP concepts: steps, activities, inputs, outcomes, overlays SPEM concepts: phase, activity, task, task step, work product, role, guidance, … Several ways to map DSEEP to SPEM, e.g. DSEEP process model plug-in DSEEP practice library plug-in

DSEEP process model plug-in A plug-in that serves as a model for and is extended with content from other plug-ins Process content: Method content: DSEEP model = SPEM capability pattern DSEEP step = SPEM phase DSEEP activity = SPEM activity DSEEP task = SPEM task DSEEP role = SPEM role DSEEP work product = SPEM work product

Process model plug-in: example

DSEEP practice library plug-in A process-agnostic practice plug-in, that provides practices and will contribute to other plug-ins Method content: DSEEP activity = SPEM task DSEEP task = SPEM task step DSEEP role = SPEM role DSEEP work product = SPEM work product

Practice library plug-in: example

Some use cases – website generation Many options, e.g.: Title and links Banner image Glossary and index Diagram options Layout options Static HTML or war

Some use cases – MS Project export Exported: WBS Dependencies Roles Phases Iterations Activities Tasks

Some use cases – Extending OpenUp Open Unified Process applies iterative and incremental approaches within a structured lifecycle EPF Variability options to adapt content: Contributes, Extends, Replaces, Extends and Replaces

DSEEP Identify needs contributes to OpenUP task Define vision in Inception Phase Using the practice library plug-in Result: EPF:

Discussion Implementation Process and method content A process model plug-in, a process-agnostic practice plug-in or a combination of both? Process and method content More content needed! More info on DSEEP roles, work products, tasks Potential DSEEP improvements IEEE copyright issue

Conclusion DSEEP process content can be mapped to SPEM in multiple ways EPFC is a useful tool for process/method content management Using SPEM provides advantages for content reuse However, more process/method content needed! DSEEP improvements, such as: more extensive role definitions, work product descriptions and guidance DSEEP Copyright restrictions may pose restrictions