In CBDI-SAE we use Disciplines as a way of separating out the different capabilities required by an organization. For example the capabilities required to deliver the Service Architecture – such as skills or tools - will be different to that required to deliver Service Implementations. Disciplines are also responsible for one or more key deliverables in Application Modernization and SOA. Application Modernization Planning produces the Application Modernization Plan; Service Oriented Architecture & Design produces the Service Portfolio Plan, and so on.
The process decomposition of Disciplines, Process Units and Tasks forms the basic ‘building blocks’ from which various types of project plans can be assembled to meet different needs. Think of Disciplines as the ‘service providers’ to an IT process.
Most projects will be focused on delivering a solution to a business requirement. The project will be tasked with understanding the requirement, mapping out the architecture, provisioning and implementing the various components and services, and finally assembling and deploying the solution. Consequently it will be using the ‘services’ provided by a number of Disciplines.
However, not all Application Modernization projects are exactly the same.
Mapping the process decomposition to appropriate project phases and into work packages enables us to explore these different options and to construct various types of project plans.
In this report we use a generic project lifecycle. We recognize that readers may follow frameworks such as RUP or various agile approaches that provide their own lifecycle phases. Mapping to these should be straightforward.
In context with Application Modernization, the phases cover:
continued in PDF