| Title: |
A Meta Model for Service Architecture and Engineering |
| Author: |
John Dodd |
| Publication Date: |
3 November 2006 |
| Report Type: |
Journal |
| Report Class: |
Best Practice |
| Abstract: |
This month, Everware-CBDI has launched its Service Architecture and Engineering (CBDI-SAETM) methodology. Formalizing our best practice guidance has required us to be more precise about the SOA concepts applied in CBDI-SAETM, no more so than in our work with vendors who are building tools that support CBDI-SAETM. Core to this is the definition of a meta model for CBDI-SAETM.. |
| Backgrounder: |
What do we mean by Meta Model? A meta model defines the rules for building a model of a business or software -- or anything else for that matter.
For example, the software architect might want to describe an Address Service and a Bookkeeping Service in their model. So the meta model needs to define a concept called “service”, state which data items are to be collected about each service, define how services may be related to other concepts, and specify any further constraints on the data to be collected.
|
| Report Size: |
6 Pages |
| Report Access Type: |
 | Silver/Gold (Premium) |
|
| Available for separate purchase |
Single copies of recent CBDI Journals may be purchased |
| Login |
|
Home