ISO IEC 18384-2-2016 PDF

Full title and description

ISO/IEC 18384-2:2016 — Information technology — Reference Architecture for Service Oriented Architecture (SOA RA) — Part 2: Reference Architecture for SOA Solutions. This part defines a domain-independent reference architecture and guidance for designing, developing, deploying and managing SOA solutions, covering functional and non-functional requirements, capability descriptions, a metamodel and conformance guidance.

Abstract

ISO/IEC 18384-2:2016 describes a Reference Architecture for Service-Oriented Architecture (SOA) Solutions that applies to functional design, performance, development, deployment and management of SOA solutions. It provides a layered architecture, cross-cutting aspects (integration, management & security, information, governance, development), common service categories, a metamodel and conformance rules, and best-practice guidance to address both functional and non-functional requirements of service-oriented systems.

General information

• Status: Published / Confirmed
• Publication date: 2016 (Edition 1, published June–July 2016)
• Publisher: ISO and IEC (joint publication; JTC 1/SC 38)
• ICS / categories: 35.210 (Information technology — Cloud computing and distributed platforms / SOA-related ICS grouping)
• Edition / version: Edition 1 — 2016
• Number of pages: 191 pages (approx.)

Scope

The standard defines a reference architecture for SOA solutions that is domain‑independent. It addresses the structure and responsibilities of layered components and service categories, identifies cross‑cutting aspects that must be managed (integration, management & security, information, governance, development), and provides a metamodel and conformance guidance so implementations can be consistently described, evaluated and reused. The scope covers the service lifecycle (definition, realization, publication/exposure, binding, invocation, deployment and runtime enablement) and both functional and non‑functional requirements (e.g., performance, scalability, reliability, security, manageability).

Key topics and requirements

• Layered reference architecture (examples: Operational & IT Systems Layer, Service Component Layer, Service Layer, Process Layer, Consumer Layer) and responsibilities for each layer.
• Cross‑cutting aspects: Integration; Management and Security (MaS); Information; Governance; Development.
• Service lifecycle model and guidance for service definition, realization, publication, binding, invocation, deployment and runtime management.
• Metamodel, terminology and conformance rules to enable consistent description, interoperability and assessment of SOA solutions.
• Common service categories (infrastructure, application, orchestration, management, access, etc.) and recommended interactions.
• Non‑functional requirements and associated capabilities (performance, scalability, availability, auditing/logging, policy enforcement, monitoring, virtualization and deployment considerations).
• Best practices and capability descriptions for design, development, deployment and operational management of SOA solutions.

Typical use and users

Used by enterprise architects, solution architects, system integrators, platform vendors, senior developers, operations and security teams, procurement and standards groups. Typical uses include creating SOA solution blueprints, internal architecture standards, vendor evaluations, interoperability assessments, and aligning development and operational practices with a common SOA vocabulary and metamodel.

Related standards

ISO/IEC 18384-1:2016 (Part 1 — Terminology and concepts for SOA), ISO/IEC 18384-3:2016 (Part 3 — Service-Oriented Architecture Ontology). Related architecture and systems standards often used alongside this standard include ISO/IEC 42010 (architecture description), and other SOA reference models and industry frameworks (e.g., TOGAF, OASIS SOA Reference Model) for complementary guidance.

Keywords

SOA, service-oriented architecture, reference architecture, metamodel, conformance, service lifecycle, governance, integration, security, management, interoperability, non-functional requirements, service categories, architecture pattern.

FAQ

Q: What is this standard?

A: ISO/IEC 18384-2:2016 is Part 2 of the SOA Reference Architecture series; it defines a reference architecture and practical guidance for implementing service-oriented solutions.

Q: What does it cover?

A: It covers layered architecture for SOA solutions, cross‑cutting aspects (integration, management & security, information, governance, development), a metamodel and conformance guidance, service lifecycle stages, common service categories, and guidance on meeting non‑functional requirements.

Q: Who typically uses it?

A: Enterprise and solution architects, system integrators, vendors and development/operations teams use it to design, evaluate and manage SOA-based systems and to align teams on terminology and architecture practices.

Q: Is it current or superseded?

A: The 2016 edition is the first edition (2016). The standard was reviewed and confirmed by ISO during its periodic review process (confirmed in a 5‑year review cycle); users should check the relevant national or ISO catalogues for the most recent confirmation or revision status before relying on it for regulatory or procurement decisions.

Q: Is it part of a series?

A: Yes — it is Part 2 of the ISO/IEC 18384 series (SOA Reference Architecture). Part 1 covers terminology and concepts and Part 3 defines an ontology; the parts are intended to be used together.

Q: What are the key keywords?

A: Key keywords include SOA, reference architecture, metamodel, service lifecycle, governance, integration, interoperability, conformance, security, management.