The Open Group Service Integration Maturity Model (OSIMM) Version 2 – Method Dimension: Base Model
This chapter defines the base model for the OSIMM Method dimension base model. The base model defines a set of generic maturity indicators and attributes that can be used to assess an organization’s SOA maturity level against the OSIMM maturity matrix. Additional maturity indicators, assessment questions, and attribute mappings can be added by vendors or user organizations to extend the base OSIMM model.
The following assessment questions help elicit the level of formality to which an organization has implemented a formal SOA development and deployment methodology, which ranges from structured design and analysis to business grammar-oriented modeling.
OSIMM Method Dimension
Method Dimension: Base Model Maturity Indicator
The base OSIMM model provides one of many possible maturity indicators per dimension. Organizations, vendors, and consultants can provide additional maturity indicators, assessment questions, and attribute mappings to provide additional guidance necessary for the maturation of an organization’s SOA.
The following Method dimension maturity indicator is provided as part of the base OSIMM specification:
- An SOA maturity assessment of the OSIMM Method dimension can be conducted by identifying the formal use of an SOA architectural design, construction, and deployment methodology for the implementation of SOA services.
Method Dimension: Assessment Questions
By gathering information using these assessment questions, an assessor can map a maturity indicator to the associated maturity attributes, thereby determining the Method dimension maturity level.
- What are the current application or systems requirements elicitations and requirements management practices?
- What design methodologies and best practices are you currently adopting?
- Do you practice any SOA design techniques?
- What design tools are in practice today?
- What is the current practice for service development and management?
- What is your current project management framework?
- How is IT project management organized?
- What are your organization’s current QA processes?
- Do you have an active community that works to evolve your SOA methods and practices?
- Has your organization developed a repository for best practices and asset re-use?
Method Dimension: Maturity Indicator-to-Attribute Mapping
The following are the base set of maturity indicators for the OSIMM Method dimension. Each maturity indicator is associated with a set of maturity attributes. Maturity attributes are those observed characteristics of a maturity indicator for each maturity level. The assessment questions are used to survey an organization’s Method dimension. Survey data obtained through the Method dimension assessment questions is used to determine the maturity level by assessing the data and matching to the maturity attributes that best fit the information obtained. The maturity weighting is used to determine an average maturity score across multiple maturity indicators. The model can be extended by adding additional maturity indicators and assigning weighting to the indicator by maturity level according to the value placed on the maturity indicator by the assessing organization.
Maturity Indicators for the Method Dimension
Maturity Level |
Maturity Indicator |
Maturity Attributes |
Maturity Weighting |
Assessment Question Mapping |
Silo Structured Analysis and Design |
Formal use of an SOA architectural design, construction, and deployment methodology for the implementation of services. |
Low or nonexistent No formal use of SOA design and implementation methodology. IT and business employees have little understanding or appreciation for implementing business processes as services. |
10 |
2, 3 5, 6 |
Integrated Object-oriented Modeling |
Formal use of an SOA architectural design, construction, and deployment methodology for the implementation of services. |
Limited SOA methods and practices are limited to the IT development teams and have not been formalized across teams. |
20 |
1, 2, 3 |
Componentized Component-based Development |
Formal use of an SOA architectural design, construction, and deployment methodology for the implementation of services. |
Cross-organizational SOA method and practices have been enhanced to address the creation, implementation, and deployment of services. Methodology is largely focused on implementing IT infrastructure and integration services. |
30 |
1, 2, 3, 4, 5, 6, 7 |
Services Service-oriented Modeling |
Formal use of an SOA architectural design, construction, and deployment methodology for the implementation of services. |
Enterprise-wide SOA methods and practices have been implemented across the enterprise. Not all organizations follow a unified approach. |
40 |
1, 2, 3, 4, 5, 6, 7 |
Composite Services Service-oriented Modeling |
Formal use of an SOA architectural design, construction, and deployment methodology for the implementation of services. |
Integrated Enterprise-wide A formal and recognized methodology for the creation, development, deployment, and management is in practice. A recognized community is empowered to manage, train, and update the enterprise SOA methods and practices. |
50 |
1, 2, 3, 5 7, 9 |
Virtualized Services Service-oriented Modeling for Infrastructure |
Formal use of an SOA architectural design, construction, and deployment methodology for the implementation of services. |
Integrated across the enterprise and externally between business partners. Formal methods are used to create and manage both internal and external (partner)-based services. Best practice guidance has been developed to facilitate consistent adoption of SOA and virtualization technologies; for example, ESB and registry. Virtualization is a key element of the IT service operations methods and is used to facilitate service performance. |
60 |
1, 2, 3 4, 9, 10 2, 8 |
Dynamically Re-Configurable Services Business Process Modeling |
Formal use of an SOA architectural design, construction, and deployment methodology for the implementation of services. |
Adaptive Enterprise Formal methods leverage architectural constructs and assets for supporting virtualization and dynamic services and business process modeling. |
70 |
1, 2, 3, 4, 5, 9, 10 |