Statistical Service Definition


Template


Name

 

GSBPM

 

Business Function

 

Outcomes

 

Restrictions

 

GSIM Inputs

 

GSIM Outputs

 

Service dependencies

 


Statistical Service Specification


Template

Statistical Service Specification: Name of Statistical Service Protocol for Invoking the Service
This service can be invoked in different ways, depending on the chosen architectural pattern.
Describe the architectural pattern(s) that this service is expected to operate in (see Chapter V - Architectural pattern).
The protocol used to invoke this function should be in compliance with the guidance provided for developing Statistical Services by CSPA. Input Messages
The inputs of the service are related to the following CSPA logical model objects:....
Describe specific inputs in terms of CSPA logical Information Model
Output Message
The outputs of the service are related to the following CSPA logical model objects:....
Describe specific outputs in terms of CSPA logical Information Model
Applicable Methodologies
Describe the statistical methods that may be implemented in this Statistical Service

Statistical Service Implementation Description


Template


Name : A name that identifies the Statistical Service implementation. It must be unique in the Service catalogue.
Version: Version number
Builder Organization: The owner of the Statistical Service, i.e. the Service Builder's organization.
Statistical Service Definition: The link to the Statistical Service Definition document.
Statistical Service Specification: The link to the Statistical Service Specification document.
Invocation protocols: Depending on the chosen architectural pattern, specify how the service has to be invoked in the deployed infrastructure.
If the service is capable to work in many architectural patterns with different implementations, then it would require different Service Implementation documents, one per supporter pattern.
Service Interface
Protocol-dependent specification of the information required to invoke the service.

  • Definition of Service Interface (if service is Web service) or
  • Environment settings (if service is local)

Examples:

  • WSDL interface for SOAP Web Service protocol
  • List of HTTP request parameters for REST Web Service protocol
  • Command line specification for Command Line protocol
  • Add other examples for other supported protocols

Data-by-Reference protocols: For each input passed as reference, specify supported protocol(s). Accepted protocols are listed in this document.
Technical dependencies: Which methodologies listed in the Statistical Service Specification are supported by this Service Implementation
Technical dependencies: List of technical requirements of the service in terms of:

  • Operating system(s) (specify version)
  • Runtime platforms – any additional software that has to be installed on the machine the service is installed on (e.g. SAS, R, Java virtual machine, .net runtime, J2EE container, etc. – Specify version)
  • Database(s)
  • Other dependencies (libraries, packages etc.)

Installation documentation Installation guide for the Assembler
Additional information Any additional information for a Assembler which is deemed relevant by the Service Builder

Annex 2: Glossary

Term

Definition

Application Architecture

Application Architecture (AA) classifies and hosts the individual applications describing their deployment, interactions, and relationships with the business processes of the organization (e.g. estimation, editing and seasonal adjustment tools, etc.).  AA facilitates discoverability and accessibility, leading to greater reuse and sharing. Source: Statistical Network BA definition

Architectural Pattern

The description of a recurring particular design problem which comes from different design contexts. The solution schema is specified by describing its components, its responsibilities its relations and the ways they collaborate. Source: CSPA

Business Architecture

Business Architecture (BA) covers all the activities undertaken by a statistical organization, including those undertaken to conceptualize, design, build and maintain information and application assets used in the production of statistical outputs. BA drives the Information, Application and Technology architectures for a statistical organization. Source: Statistical Network BA definition

Business Line

A business line within a statistical organization usually delivers a particular business outcome. Business lines allow the Business Architecture to be split into homogeneous areas of related activities. Business lines are defined in order to guarantee independence from reorganization of the current organizational structure. Source: Statistical Network BA definition

Business Function

Something an enterprise does, or needs to do, in order to achieve its objectives. Source: GSIM

Business Process

A set of process steps to perform one or more Business Functions to deliver a Statistical Program. Source: GSIM

Business Service

A defined interface for accessing business capabilities (an ability that an organization possesses, typically expressed in general and high level terms and requiring a combination of organization, people, processes and technology to achieve). Source: GSIM

Capability

Capabilities provide the Statistical Organisation with the ability to undertake a specific activity. A capability is only achieved through the integration of all relevant capability elements (e.g. methods, processes, standards and frameworks, IT systems and people skills). Source: Statistical Network BA definition

Common Statistical Production Architecture

A set of principles for increased interoperability within and between statistical organizations through the sharing of processes and components, to facilitate real collaboration opportunities, international decisions and investments and sharing of designs, knowledge and practices. Source: CSPA

Enterprise Architecture

Enterprise Architecture is about understanding all of the different elements that go to make up the enterprise and how those elements interrelate. It is an approach to enabling the vision and strategy of an organization, by providing a clear, cohesive, and achievable picture of what's required to get there.  Source: Statistical Network BA definition

Global Artefact Catalogue

A list and descriptions of standardized artefacts, and, where relevant, information on how to obtain and use them. Source: CSPA

Industry Architecture

A set of agreed common principles and standards designed to promote greater interoperability within and between the different players that make up an "industry", where an industry is defined as a set of organizations with similar inputs, processes, outputs and goals. Source: CSPA

Information Architecture

Information Architecture (IA) classifies the information and knowledge assets gathered, produced and used within the Business Architecture. It also describes the information standards and frameworks that underpin the statistical information. IA facilitates discoverability and accessibility, leading to greater reuse and sharing. Source: Statistical Network BA definition

Interface

A type of contract by which subsystems or component communicate. Source: CSPA

Non Functional Requirements

Non Functional Requirements are the overall factors that affect runtime behaviour, system design, and user experience. They represent areas of concern that have the potential for application wide impact. Source: CSPA

Principles

Principles are general rules and guidelines, intended to be enduring and seldom amended, that inform and support the way in which an organization sets about fulfilling its mission and business objectives. Source: Statistical Network BA definition

Protocol

Formats and rules for exchanging messages in or between computing systems. Source: CSPA

Reuse

Reuse is the concept of using a common asset (implemented component, a component definition, a pattern...) repetitively in different (or similar) contexts (for example in different business processes), and/or by different participants, and/or overtime. Source: CSPA

Service

A service is a logical representation of a repeatable business activity that has a specified outcome and is self-contained, fulfils a business need for a customer (internal or external to the organization) and may be composed of other services. Source: Statistical Network BA definition (adapted from TOGAF G113)

Service Contract

A service contract is comprised of one or more published documents (called service description documents) that express meta information about a service. The fundamental part of a service contract consists of the service description documents that express its technical interface. These form the technical service contract which essentially establishes an API into the functionality offered by the service. A service contract can be further comprised of human-readable documents, such as a Service Level Agreement (SLA) that describes additional quality-of-service features, behaviours, and limitations. Source: http://serviceorientation.com/soaglossary/service_contract

Service Interface

A service interface is the abstract boundary that a service exposes. It defines the types of messages and the message exchange patterns that are involved in interacting with the service, together with any conditions implied by those messages. Source: http://www.w3.org/TR/ws-arch/#service_interface

Service Oriented Architecture

Service-Oriented Architecture (SOA) is an architectural style that supports a way of thinking (Service Orientation) in terms of services and service-based development and the outcomes of services.  The SOA architectural style has the following distinctive features: It is based on the design of the services – which mirror real-world business activities – comprising the enterprise (or inter-enterprise) business processes. Service representation utilizes business descriptions to provide context (i.e., business process, goal, rule, policy, service interface, and service component) and implements services using service orchestration. It places unique requirements on the infrastructure – it is recommended that implementations use open standards to realize interoperability and location transparency. Implementations are environment-specific – they are constrained or enabled by context and must be described within that context. It requires strong governance of service representation and implementation. It requires a "Litmus Test", which determines a "good service".  Source: The Open Group http://www.opengroup.org/soa/source-book/soa/soa.htm

Share

Share is an ownership concept where an asset is made available to other participants for use. There are levels of sharing. A limited form of sharing would be to provide another participant with the means to replicate (make a copy) the asset (for example give the source code) (i.e. they share an aspect of the asset only). A more involved form of sharing would entail that asset is actually been made entirely common (in this case the asset is also reused).  Source: CSPA

Statistical Service

A Statistical Service is a specialization of Service for the statistical industry. A Statistical Service represents a defined interface for accessing business capabilities (an ability that an organization possesses, typically expressed in general and high level terms and requiring a combination of organization, people, processes and technology to achieve). It is logical representation of a repeatable business activity that has a specified outcome and is self-contained, fulfils a business need for a customer (internal or external to the organization) and may be composed of other services Source: GSIM and Statistical Network BA definition (Service)

Technology Architecture

Technology Architecture (TA) describes the IT infrastructure required to support the deployment of applications and IT services, including hardware, middleware, networks, platforms, etc. Source: Statistical Network BA definition


  • No labels