Jeff Schneider, CEO of MomentumSI, who has been a contributor to SOA since the early days, has focused on enabling the "Service Oriented Enterprise".
Yesterday, MomentumSI released the Harmony™ SOA Framework. The base framework is provided for free. Other frameworks have been published before with different scope and focus, such as the UN/CEFACT Modeling Methodology which focuses on B2B, the CBDI Service Architecture & Engineering Metamodel which focuses on some of the information captured during service construction, or the Praxeme Enterprise Methode (in English) which focuses on service identification and construction as part of business processes. The purpose of these frameworks is to define precisely the metamodel of a service oriented system -including a logical data model-, specify the organization, the processes, activities and deliverables that help create services and assemblies of services, as well as the technical foundation of service oriented systems from an Enterprise Architecture perspective. Overall they help structuring the decision process around service and service oriented infrastructure construction.
For instance, even capturing the metadata associated to a service to help design it, implement it, find it, manage it and operate it remains challenging.
MomentumSI's framework is based on 5 perspectives:
- SOA Lifecycle & Work Patterns
- SOA Technical Reference Architecture
- SOA Governance & Organizational Model
- SOA Maturity Model
- SOA Business & Information Architecture (to be published)
MomentumSI's SOA lifecycle is composed of 9 phases, ranging from investigation, realization to operation, evolution and consumption. The Eclipse Process Framework can be used to managed SOA lifecycles and align it with existing Project and Software methodologies such as RUP, OpenUP...
The Technical Reference Architecture defines for instance, the SOA Infrastructure, the different class of services, security and Management & Operations.
The Governance model specifies the Governance Organization and the relationships with the Service lifecycles.
The Maturity Model describe in details the target levels of maturity for the enterprise architecture, the technology infrastructure, the methodology, and the operations.