The Magic of Integration Points
SCA Engineering
Service Component Architecture provides definitions and diagrams that define
the integration points and components for complex application composites.
The SCA model can be used to build new composites and also used to
document existing applications built without a service orientation.
Every application should have a boundary where all of its components are
within the boundary and all of those that it is integrated with are outside the
boundary. The SCA composite provides this boundary. The integration points
provide the link between composites and become the magic for capturing
enterprise architecture metadata.
The service and reference elements of the standard XML schema for SCA
have been extended to require four additional attributes. These attributes are
required for the promoted services and references within a composite. The
additional attributes are subjectarea, processdomain, archlayer and archstyle.
Including these four values provide the ability to validate an application
composite against the other EA models.
More detail on SCA can be found at the Open Service Oriented Architecture
Site.
Link to the Architecture Layers
The architecture layer is also defined on each promoted service or reference.
This identifies the layer in the architecture that is the source or target of the
integration point.
Link to the Process Model
The combined business domain and sub-domain names from the process
model are included on each promoted service and reference as well. This
source and the target from the information flow can be validated against the
process model.
Link to the Data Model
The data subject area from the enterprise model is included on each
promoted service and reference. This becomes the qualifier for the service
and the reference and can be used as the namespace on the interface.
Maintaining Enterprise Architecture Metadata
from a Holistic, Enterprise Perspective
Link to the Architecture Style
The architecture styles included in the XML schema are SOA
(Service-Oriented Architecture), EDA (Event-Driven Architecture), and batch
(Scheduled batch processing). The style defined for a service or reference
determines the direction of the flow of information.