Open-system environment reference model: Difference between revisions

Revision as of 13:46, 14 July 2013

Latest revision as of 17:10, 25 June 2025

(11 intermediate revisions by 9 users not shown)

Line 1:

{{Short description|Reference model for enterprise architecture}}

[[File:Open System Environment Reference Model.jpg|thumb|320px|Open System Environment Reference Model, 1995.<ref name="Hun95"> Joseph I. Hungate et al. (1995) "[http://nvl.nist.gov/pub/nistpubs/jres/100/6/j16ce-hun.pdf Conference Report: APPLICATIONApplication PORTABILITYPortability PROFILEProfile ANDand OPENOpen SYSTEMSystem ENVIRONMENTEnvironment USER’SUsers FORUMForum Gaithersburg, MD May 9–10, 1995]" in: ''Journal of Research of the National Institute of Standards and Technology''. Volume 100, Number 6, November–December 1995</ref>]]

'''Open-system environment (OSE) reference model (RM)''' or ''OSE reference model'' (OSE/RM) is a 1990 [[reference model]]s for [[enterprise architecture]]. It provides a [[software framework|framework]] for describing [[Open system (computing)|open system]] concepts and defining a lexicon of terms, that can be agreed upon generally by all interested parties. <ref name="Hun95"/>

This reference model is meant as an environment model, complementary to the [[POSIX]] architecture for open systems. It offers an extensible framework that allows services, interfaces, protocols, and supporting data formats to be defined in terms of nonproprietary specifications that evolve through open (public), consensus-based forums.<ref>''ACM Sigsoft (1993) 15th International Conference on Software Engineering, May 17-21, 1993''. p.349</ref> This reference model served in the 1990s as a basic building block of several technical reference models and technical architecturearchitectures.

In 1996 this reference model was standardized in the [[List_of_International_Organization_for_Standardization_standards#ISO_10000.E2.80.93ISO_14999|ISO/IEC TR 14252]] titled "Information technology -- Guide to the POSIX Open System Environment (OSE)".<ref>Wolfgang Kresse, Kian Fadaie (2004) ''ISO Standards for Geographic Information''. p.72</ref>

== History ==

The development of the open-system environment reference model started early 1990s by the [[NIST]] as refinement of the [[POSIX]] (Portable Operating System Interface) standard. POSIX is a standard for maintaining compatibility between operating systems, and addresses interoperation for communications, computing, and entertainment infrastructure. It'sIts developeddevelopment started late 1980s by the POSIX Working Group 1003.0 of the [[Institute of Electrical and Electronics Engineers]] (IEEE).<ref name="Hun95"/>

The NIST hosted workshops and conducts other support activities to assist users in addressing open systems requirements, preparing for the use of new technology, and identifying the international, national, industry and other open specifications that are available for building open systems frameworks, such as the government's applications portability profile for the open-system environment.

Line 19 ⟶ 20:

Two types of elements are used in the model: entities consisting of the application software, application platform, and platform external environment; and interfaces including the application program interface and external environment interface.

=== OSEAPP referenceservice model entitiesareas ===

[[File:APP Service Areas and the OSE-RM.jpg|thumb|240px|left320px|APP Service Areas and the OSE-RM]]

The three classes of OSE reference model entities are described as follows:<ref name="Hun95"/>

The [[Application Portability Profile]] (APP) is an OSE profile designed for use by the U.S. Government. It covers a broad range of application software domains of interest to many Federal agencies, but it does not include every ___domain within the U.S. Government’s application inventory. The individual standards and specifications in the APP define data formats, interfaces, protocols, or a mix of these elements.

The services defined in the APP tend to fall into broad service areas . These service areas are:<ref name="Hun95"/>

* ''Application software'' : Within the context of the OSE Reference Model, the application software includes data, documentation, and training, as well as programs.

* Operating system services (OS)

* ''Application platform'' : The application platform is composed of the collection of hardware and software components that provide the generic application and system services.

* Human/computer interface services (HCI)

* ''Platform external environment'' : The platform external environment consists of those system elements that are external to the application software and the application platform (e.g., services provided by other platforms or peripheral devices).

* Data management services (DM)

* GraphicsData interchange services (GSDI)

* Software engineering services (SWE)

* NetworkGraphics services (NSGS)

* Network services (NS)

Each service area is defined in the following sections. The figure illustrates where each of these services areas relates to the OSE/RM. Assume that [[software engineering]] services are applicable in all areas. Each of the APP service areas addresses specific components around which interface, data format, or protocol specifications have been or will be defined. Security and management services are common to all of the

service areas and pervade these areas in one or more forms.<ref name="Hun95"/>

=== Classes of interfaces ===

Line 35 ⟶ 44:

** Internal system services

* ''External environment interface (EEI)'' : The EEI is the interface that supports information transfer between the application platform and the external environment, and between applications executing on the same platform. Consisting chiefly of protocols and supporting data formats, the EEI supports interoperability to a large extent. An EEI is categorized in accordance with the type of information transfer services provided.

=== Types of information transfer services ===

There are three types of information transfer services. These are transfer services to and from:<ref name="Hun95"/>

* Human users

* External [[data stores]]

* Other application platforms

In its simplest form, the OSE/RM illustrates a straightforward user-supplier relationship: the application software is the user of services and the application platform/ external environment entities are the suppliers. The API and EEI define the services that are provided.<ref name="Hun95"/>

=== OSE profile ===

Line 48 ⟶ 50:

An OSE profile is composed of a selected list of open (public), consensus-based standards and specifications that define services in the OSE/RM. Restricting a profile to a specific ___domain or group of domains that are of interest to an individual organization results in the definition of an organizational profile.<ref name="Hun95"/>

=== APPOSE servicereference areasmodel entities ===

The three classes of OSE reference model entities are described as follows:<ref name="Hun95"/>

[[File:APP Service Areas and the OSE-RM.jpg|thumb|240px|left|APP Service Areas and the OSE-RM]]

The Application Portability Profile (APP) is an OSE profile designed for use by the U.S. Government. It covers a broad range of application software domains of interest to many Federal agencies, but it does not include every ___domain within the U.S. Government’s application inventory. The individual standards and specifications in the APP define data formats, interfaces, protocols, or a mix of these elements.

* ''Application software'' : Within the context of the OSE Reference Model, the application software includes data, documentation, and training, as well as programs.

The services defined in the APP tend to fall into broad service areas . These service areas are:<ref name="Hun95"/>

* ''Application platform'' : The application platform is composed of the collection of hardware and software components that provide the generic application and system services.

* Operating system services (OS)

* ''Platform external environment'' : The platform external environment consists of those system elements that are external to the application software and the application platform (e.g., services provided by other platforms or peripheral devices).

* Human/computer interface services (HCI)

* Data management services (DM)

*=== DataTypes interchangeof information transfer services (DI)===

There are three types of information transfer services. These are transfer services to and from:<ref name="Hun95"/>

* Software engineering services (SWE)

* Human users

* Graphics services (GS)

* External [[data stores]]

* Network services (NS)

* Other application platforms

[[File:Detailed DoD Technical Reference Model.jpg|thumb|240px|Detailed DoD technical reference model of the [[TAFIM]], is based on the Open System Environment model.<ref name = "DoD96V2"> Department of Defense (1996). ''Technical Architecture Framework for Information Management. Vol. 2''. April 1996</ref>]]

In its simplest form, the OSE/RM illustrates a straightforward user-supplier relationship: the application software is the user of services and the application platform/ external environment entities are the suppliers. The API and EEI define the services that are provided.<ref name="Hun95"/>

Each service area is defined in the following sections. The figure illustrates where each of these services areas relates to the OSE/RM. Assume that [[software engineering]] services are applicable in all areas. Each of the APP service areas addresses specific components around which interface, data format, or protocol specifications have been or will be defined. Security and management services are common to all of the

service areas and pervade these areas in one or more forms.<ref name="Hun95"/>

== Applications ==

[[File:Detailed DoD Technical Reference Model.jpg|thumb|240px|Detailed DoD technical reference model of the [[TAFIM]], is based on the Open System Environment model.<ref name = "DoD96V2"> Department of Defense (1996). ''Technical Architecture Framework for Information Management. Vol. 2''. April 1996</ref>]]

Basically, the open-system environment model is a basic building block of several technical reference models and technical architecture. A [[technical architecture]] identifies and describes the types of applications, platforms, and external entities; their interfaces; and their services; as well as the context within which the entities interoperate. A technical architecture is based on a technical reference model (TRM) and the selected standards that further describe the TRM elements (the profile). The technical architecture is the basis for selecting and implementing the infrastructure to establish the target architecture.<ref name="ACF">[http://www.acf.hhs.gov/nhsitrc/it_planning/pdf/consolidated_definitions.pdf Consolidated Definitions and References] at acf.hhs.gov. Accessed 12 Dec 2008.</ref>

A technical architecture is based on:

* a Technical Reference Model (TRM); and

* the selected standards that further describe the TRM elements (the profile).

The technical architecture is the basis for selecting and implementing the infrastructure to establish the target architecture.<ref name="ACF">[https://web.archive.org/web/20060928000010/http://www.acf.hhs.gov/nhsitrc/it_planning/pdf/consolidated_definitions.pdf Consolidated Definitions and References] at acf.hhs.gov. Accessed 12 Dec 2008.</ref>

A [[technical reference model]] can be defined as a taxonomy of services arranged according to a conceptual model, such as the Open System Environment model. The enumerated services are specific to those needed to support the technology computing style (e.g., distributed object computing) and the industry/business application needs (e.g., Human Services, financial). <ref name="ACF"/>