5.3. Service Orientation Name: Service Orientation Statement: The architecture is based on a design of services which mirror real-world business activities comprising the enterprise (or inter-enterprise) business processes. Rationale: • Service orientation supports enterprise agility and boundaryless information flow Implications: • Need to think in terms of APIs, application services, and service-based integration that fulfills a business need • Service representation utilizes business description to provide context (i.e. business process, goal, rule, policy service interface and service component) and implements services using service orchestration • Service orientation places unique requirements on the infrastructure; implementations should use open standards to realise interoperability and location transparency. • Implementations are environment specific; they are constrained by context and must be described within that context. • Service orientation requires strong governance of service representation and implementation. • ESDC needs to transform its acquisition of IT solutions from siloed systems to modern, modular service-based contracts exploiting common services. References: • TOGAF 9.2 Principle 6