Development Methodology

The development methodology consists of multiple sequential phases in a project lifecycle, with some phases being optional, and the order of phases being dependent on the project being undertaken.

Development Methodology Considerations
When starting a development project involving the IPS models, there are variations to the methodology that a project team may use, from a top-down full life-cycle methodology using many related process and services models, to the use of a single model for a short-term quick-win model design phase.
Structured and model-driven development
Before discussing the details of each phase of IBM Process and Service Model customization, this topic explains the project lifecycle, artifacts and skills required at each stage in this cycle.
Service Design Quickstart
An alternative to performing a top-down development cycle is to take another model-driven development approach, which is described in this topic as quickstart service development, whereby projects may start with existing implemented services and/or data definitions, and Project Teams want to use those services as they are, but hook them into the IPS modelset. Alternatively, Project Teams may be interested in only ever using design level Service Models.
Example Methodology Variants
The Insurance Process and Service Models development method consists of multiple sequential phases in a project lifecycle, with some phases being optional according to the project being undertaken. Some example variants on the full end-to-end project lifecycle are presented in this section.