Service Models
Service Models provide the predefined analysis and design-level structures to enable more consistency and reuse in the creation of services.
Service Model components comprise:
- Business Object Model (BOM) comprises technology-independent
class models that enable traceability between:
- Automated business process requirements
- Downstream services-oriented architecture (SOA) IT analysis representation
- Web Service Design Model (WSDM) provides
a design for an enterprise-wide and business-services-based architecture
though the development of:
- Participants
- Service interfaces
- Messages
- Interface Design Model (IDM) provides a
design for an enterprise-wide and business-services-based architecture
through the development of:
- Components
- Types
- Interfaces
- Data transfer objects
- Transfer Objects Model (TOM) defines transfer
objects, which are simple Unified Modeling Language (UML) data types
derived from the IDM class model. Transfer objects are used to explicitly
define, at modeling time, the structure of data that will be used
in:
- Deployed services
- Data objects in executable Process Models
- WSDM
- Java Service Design Model (JSDM)
- Message Service Design Model (MSDM)
- Governance over multiple versions of transfer objects
- Governance over multiple transfer object hierarchies intended for different target systems
- Control over who can modify transfer objects
Note: it is also possible to have multiple TOMs within a project. - Java Service Design Model (JSDM) is a platform-specific
model that contains definitions to enable the generation of Java services.
Service operations in JSDM are derived from capability operations
in BOM. Like the other platform-specific design models, service operations
in JSDM do not directly reference IDM classes or interfaces. JSDM
service option parameters can only be of type:
- Transfer object
- IDM enumeration
- Design Models Datatypes (DMD) primitive type
- Message Service Design Model (MSDM) Message
Service Design Model (MSDM) is a platform-specific model that contains
definitions to enable the generation of XSD messages and commands.
Messages in MSDM are derived from capability operations in BOM. Message-based
XSDs and command-based XSDs generated from the MSDM can be used in
a messaging environment. Request messages can be routed to a messaging
engine, which can, in turn, invoke lower-level services created from
BPS for Standard Tooling models. When required, a response message
can be routed back to the sender. Like the other platform-specific
design models, messages in MSDM do not directly reference IDM classes
or interfaces. MSDM request/response message attributes can only be
of type:
- Transfer object
- IDM enumeration
- DMD primitive type
- RESTful Application Design Model (RADM) The RESTful Application Design Model (RADM) is a UML Service model which contains definitions for REST (Representational State Transfer) Applications, REST Resources and associated REST Data Objects (JSON/XML structures). RADM elements are derived from and mapped to IDM Class model elements.