Open-system environment reference model: Difference between revisions

Revision as of 16:53, 23 October 2016

Latest revision as of 17:10, 25 June 2025

(8 intermediate revisions by 6 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: Application Portability Profile and Open System Environment Users Forum 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 23 ⟶ 24:

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"/>

* Operating system services (OS)

* Human/computer interface services (HCI)

Line 61 ⟶ 62:

* 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"/>

== Applications ==

Line 70 ⟶ 71:

* 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"/>