|
|
Jointly presented by Osellus and Number Six Software
Like a software system, a software development process cannot be hobbled together from a pile of disparate components. A mature process requires a mature process definition practice that specifies by what criteria certain process components are selected. And it requires a pluggable process architecture that ensures that the components fit together with key responsibilities and matching interfaces to create a robust, full-featured, integrated process.
This presentation will analyze the organization of process elements in the Software Process Engineering Metamodel (SPEM) and propose a way to organize these into a pluggable process architecture that involves a lifecycle, a set of predefined discipline categories, and a set of work products. In building up from a set of reusable work products, a process can be defined that marries together otherwise disparate disciplines under a selected lifecycle. In predefining a pluggable architecture, completeness is ensured (for example, there must always be a requirements discipline of some variety). Exemplar processes built within this architecture will be described such as a PMI-based lifecycle applying the RUP requirements discipline, agile implementation discipline, and an MSF project management discipline.
Required Background Knowledge
Basic knowledge of process and project management issues
Suggested Audience
Process or SEPG leads, Project managers, Development Managers
|
