ISO IEC 18384-1 pdf download

ISO IEC 18384-1 pdf download.Information technology — Reference Architecture for Service Oriented Architecture (SOA RA)
2 Terms and definitions
For the purposes of this document, the following terms and definitions apply. 2.1 actor person or system component that interacts with the system as a whole and that provides stimulus which invokes actions [SOURCE: ISO/IEC 16500-8:1999, 3.1] 2.2 architecture fundamental concepts or properties of a system in its environment embodied in its elements, relationships, and in the principles of its design and evolution [SOURCE: ISO/IEC/IEEE 42010:2011, 3.2] 2.3 choreography type of composition (2.5) whose elements (2.8) interact in a non-directed fashion with each autonomous part knowing and following an observable predefined pattern of behaviour for the entire (global) composition Note 1 to entry: Choreography does not require complete or perfect knowledge of the pattern of behaviour. Note 2 to entry: See ISO/IEC 18384-3:2016, 8.3. 2.4 collaboration type of composition (2.5) whose elements (2.8) interact in a non-directed fashion, each according to their own plans and purposes without a predefined pattern of behaviour Note 1 to entry: See ISO/IEC 18384-3:2016, 8.3. 2.5 composition result of assembling a collection of elements (2.8) for a particular purpose Note 1 to entry: See ISO/IEC 18384-3:2016, 8.2.2.6 endpoint location at which information is received to invoke and configure interaction 2.7 effect outcome of an interaction with a service (2.20) Note 1 to entry: The effect is how a service delivers results to its consumer, through the element (2.8) that performs it. Note 2 to entry: See ISO/IEC 18384-3:2016, 7.10. 2.8 element unit at a given level of abstraction and with a clearly defined boundary Note 1 to entry: An element can be any type of entity (2.9). Note 2 to entry: See ISO/IEC 18384-3:2016, 5.1. 2.9 entity individual element (2.8) in a system with an identity which can act as a service provider (2.50) or service consumer (2.29) Note 1 to entry: Examples of entities are organizations, enterprises and individuals, software, and hardware. 2.10 event something that occurs to which an element (2.8) may choose to respond Note 1 to entry: Any element can generate (emit) or respond to an event. Note 2 to entry: See ISO/IEC 18384-3:2016, Clause 10. 2.11 execution context set of technical and business elements (2.8) needed by those with needs and capabilities to permit service providers (2.50) and service consumers (2.29) instantiation and communication Note 1 to entry: The execution context of a service interaction (2.37) is the set of infrastructure elements, process entities, policy assertions, and agreements that are identified as part of an instantiated service interaction, and thus forms a path between those with needs and those with capabilities. Note 2 to entry: See Reference [8]. 2.12 human actor actor (2.1) restricted to a person or an organizational entity (2.9) Note 1 to entry: This classification is not exhaustive. Note 2 to entry: See ISO/IEC 18384-3:2016, 6.2. 2.13 human task task (2.60) which is done by a human actor (2.12)2.14 interface shared boundary between two functional units, defined by various characteristics pertaining to the functions, physical interconnections, signal exchanges, and other characteristics, as appropriate [SOURCE: ISO/IEC 2382:2015, 2121308] 2.15 loose coupling principle where dependencies between elements (2.8) of a SOA solution (2.56) are intentionally reduced 2.16 orchestration type of composition (2.5) where one particular element (2.8) is used by the composition to oversee and direct the other elements Note 1 to entry: The element that directs an orchestration is not part of the orchestration (Composition instance) itself. Note 2 to entry: See ISO/IEC 18384-3:2016, 8.3. 2.17 policy statement that an entity (2.9) intends to follow or intends that another entity should follow Note 1 to entry: See ISO/IEC 18384-3:2016, Clause 9). 2.18 process type of composition (2.5) whose elements (2.8) are composed into a sequence or flow of activities and interactions with the objective of carrying out certain work Note 1 to entry: A process may also be a collaboration (2.4), choreography (2.3), or orchestration (2.16). Note 2 to entry: See ISO/IEC 18384-3:2016, 8.6. 2.19 real-world effect change relevant to and experienced by specific stakeholders Note 1 to entry: See Reference [8]. 2.20 service logical representation of a set of activities that has specified outcomes, is self-contained, may be composed of other services, and is a “black box” to consumers of the service Note 1 to entry: The word “activity” in the “service” definition is used in the general English language sense of the word, not in the process-specific sense of that same word [i.e. activities are not necessarily process (2.18) activities]. Note 2 to entry: See ISO/IEC 18384-3:2016, 7.2. 2.21 service broker element (2.8) that enables the communication with services (2.20), either at a business level or at the implementation level, i.e. with intermediaries