In this trail we will provide an overview of design issues when
constructing services to be executed on Openwings. It is assumed
you have a basic notion of some key concepts:
- A
component is a basic unit of deployment
- An interface declares the nature of a service without specifying
implementation
- Policies
decouples components from component execution
- Connectors
provide the means for connecting components
- A
service is a contractually defined behavior that can be
implemented and provided by a component for use by any component,
solely based on the contract
When perusing this trail keep in mind the objectives of the Openwings
Architecture. An introduction to these notions were provided in
the Openwings
Architecture Introduction.
We begin this section with a description of an effective modeling tool
that represents service-oriented problems. Openwings endorses the use of
modeling tools such as
UML (Unified Modeling Language) and ADL (Architecture Description Language).
Next: Architecture Description
Language
