Application Portability Profile

The Application Portability Profile (APP) is a 1990s framework for Open-System Environment designed by the NIST for use by the U.S. Government. It contains a selected suite of specifications that defines the interfaces, services, protocols, and data formats for a particular class or domain of applications.

Application Portability Profile (APP) Service Areas and the Open-system environment reference model (OSE-RM).

The Application Portability Profile offers structure to "integrate US federal, national and international, and other specifications to provide the functionality necessary to accommodate the broad range of US federal information technology requirements." [1]

Overview

In the second half of the 20th century information systems initially developed from isolated islands of computing. Through progressive changes, these individual systems became connected by common users and common information needs. Late 20th century these systems were well on the way to migrating toward computing environments that consist of distributed, heterogeneous, networked applications, databases, and hardware. The concept emerged of a federal computing environment, that is built on an infrastructure defined by open, consensus-based standards which serve as de facto means of organizing these systems. The NIST developed such an infrastructure, and named it Open System Environment (OSE).[2]

An Open System Environment (OSE) encompasses the functionality needed to provide interoperability, portability, and scalability of computerized applications across networks of heterogeneous, multi-vendor hardware/software/communications platforms. The Open System Environment forms 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.[2]

Complementary to the Open System Environment is the Application Portability Profile standard. This standard can covers a broad range of application software domains of interest to many US 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.

APP topics

APP and the NIST Enterprise Architecture Model
The APP addresses the lowest architecture in the NIST Enterprise Architecture Model, i.e., the Delivery System Architecture.

The "Application Portability Profile (APP) - The U.S. Government’s Open System Environment Profile Version 3.0" provides recommendations on a set of industry, Federal, national, international and other specifications that define interfaces, services, protocols, and data formats to support an Open System Environment (OSE).

The APP addresses the lowest architecture in the NIST Enterprise Architecture Model, i.e., the Delivery System Architecture. On this level the hardware of the computer architecture, the software and the communications are being specified. Based on these specification recommendations, various services and agencies have defined detailed technical reference models.

APP service areas

The services defined in the Application Portability Profile fall into the following broad spectrum of service areas:[3]

  • Operating system services (OS)
  • Human/computer interface services (HCI)
  • Data management services (DM)
  • Data interchange services (DI)
  • Software engineering services (SWE)
  • Graphics services (GS)
  • Network services (NS)

Each of the Application Portability Profile 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.[3]

Applications

In the 1990s the NIST's Application Portability Profile has been applicated in several Enterprise Information Architecture frameworks, such as:[4]

  • Information Architecture framework for the U.S. Patent and Trademark Office (PTO) of the Department of Commerce (DoC), and
  • Department of Defense (DoD) in its Technical Architecture Framework for Information Management (TAFIM)
  • C4I Technical Architecture, COE Architecture, 1995
  • Detailed DoD Technical Reference Model, 1996

Further reading
  • Department of Defense (1996). Technical Architecture Framework for Information Management. Vol. 2, Technical Reference Model.
  • Gary Fisher (1993). Application Portability Profile (APP) : The U.S. Government’s Open System Environment Profile OSE/1 Version 2.0. NIST Special Publication 500-210, June 1993.
  • Joseph Hungate (1995) "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
  • IEEE P1003.22 Draft Guide for POSIX Open Systems Environment—A Security Framework
gollark: Well, with crates.io, it shouldn't.
gollark: No, it's automated, which is good and useful™.
gollark: no.
gollark: Mutable state leads to fiddly control flow and stuff.
gollark: JS has surprisingly good FP utilities and there are libraries for more.

References

 This article incorporates public domain material from the National Institute of Standards and Technology website https://www.nist.gov.

  1. The Open Group (2007) TOGAF 2007 Edition: (incorporating 8.1.1). p. 507
  2. Naval Information Systems Management Center (1994) Ada Implementation Guide : Software Engineering With Ada Volume I. Department of the Navy, April 1994
  3. Joseph Hungate (1995) "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
  4. Federal Aviation Administration (1998) Federal Information Architecture Initiatives. Federal Aviation Administration, Architecture and Systems Engineering Division, ASD-100, and NAS Information Architecture Team. February 1998
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.