9.6. DESIGN TIME

The design-time phase includes the business service definition and the technical design of the service. During this phase, architects and software developers are in need of software design artifacts and guides to ensure that the resulting Services not only satisfy the business needs, but adhere to the enterprise architecture and SOA policies. The use of registries, repositories, and policy managers can be used to facilitate and enforce the enterprise design-time policies. Design-time governance requirements should include:

  • Application of SOA policies to services development processes

  • Process policies such as reuse, design reviews, code reviews, release procedures

  • Technical policies such as schema usage, WS-I conformance, security policies, compliance policies

  • Automation through service validation process

  • Access to operational and run-time metadata

The following sections will discuss in more detail how the use of tools can support both the designer and developer of services while ensuring that enterprise policies are followed.

9.6.1. Design-Time Policies at the Enterprise Level

At the enterprise level, the need for the definition and enforcement of policies that are to be followed at design time is critical to the success of the enterprise SOA. Design-time enterprise policies need to be defined and placed into the appropriate repositories, registries, and policy engines to ensure that they are followed as the services are being designed and created.

9.6.2. Repositories ...

Get Service-Oriented Architecture Governance for the Services Driven Enterprise now with the O’Reilly learning platform.

O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.