(FACEâ„¢) Library Requirements -

Future Airborne Capability Environment (FACE™)

Library Requirements

Version 2.0 September 2013

Prepared by the FACE Consortium Business Working Group Library Subcommittee

NAVAIR Public Release 2013-393

Distribution Statement A – “Approved for public release; distribution is unlimited”

Future Airborne Capability Environment (FACE™): Library Requirements 2.0 2

ArchiMate®, DirecNet®, Jericho Forum®, Making Standards Work®, OpenPegasus®, The Open Group®, TOGAF®, UNIX®, and the “X”® device are registered trademarks and Boundaryless Information Flow™, Dependability Through Assuredness™, FACE™, Platform 3.0™, and The Open Group Certification Mark™ are trademarks of The Open Group.

Object Management Group®, OMG®, and XMI® are registered trademarks and MOF™ is a trademark of Object Management Group, Inc. in the United States and/or other countries.

All other brands, company, and product names are used for identification purposes only and may be trademarks that are the sole property of their respective owners.

Future Airborne Capability Environment (FACE™): Library Requirements 2.0

Authored by The Open Group FACE Consortium, September 2013.

Comments relating to the material contained in this document may be submitted to:

The Open Group, 8 New England Executive Park, Burlington, MA 01803, United States

or by electronic mail to:

[email protected]


Contents 1. Introduction ........................................................................................................................................................ 4

1.1 Scope..................................................................................................................................................... 4 1.2 Assumptions.......................................................................................................................................... 4 1.3 Related Documents ............................................................................................................................... 5

2. Library Overview ............................................................................................................................................... 6 2.1 FACE Landing Page ............................................................................................................................. 6 2.2 FACE Library Portal............................................................................................................................. 7 2.3 FACE Registry...................................................................................................................................... 7 2.4 FACE Library Repositories .................................................................................................................. 8

2.4.1 FACE Product Repositories....................................................................................................... 8 2.4.2 FACE Reference Repositories................................................................................................... 8 2.4.3 FACE Certification Retention Repository................................................................................. 8 2.4.4 FACE Verification Retention Repositories ............................................................................... 9 2.4.5 FACE Shared Data Model Reference Repository ..................................................................... 9

3. Requirements.................................................................................................................................................... 10 3.1 FACE Landing Page Requirements .................................................................................................... 10 3.2 FACE Library Portal Requirements.................................................................................................... 10 3.3 FACE Registry Requirements............................................................................................................. 12 3.4 FACE Repository Requirements......................................................................................................... 13

3.4.1 Common FACE Repository Requirements ............................................................................. 13 3.4.2 FACE Reference Repository Requirements ............................................................................ 13 3.4.3 FACE Product Repository Requirements................................................................................ 13 3.4.4 FACE Certification Retention Repository Requirements........................................................ 14 3.4.5 FACE Verification Retention Repository Requirements ........................................................ 14 3.4.6 FACE Shared Data Model Reference Repository Requirements ............................................ 15

A FACE Registry Metadata ................................................................................................................................. 18 B FACE Product Repository Metadata................................................................................................................ 20 C FACE Reference Repository Metadata ............................................................................................................ 23


1. Introduction

The purpose of the Future Airborne Capability Environment (FACE™) Library is to provide the infrastructure to enable the discovery and acquisition of FACE Certified Products. The FACE Library enables the distribution of FACE Certified Products through a centrally located and managed gateway.

This document outlines the architecture and functionality for the FACE Library and defines the FACE Library’s requirements. This document is written for developers responsible for the design, implementation, and maintenance of the FACE Library as well as anyone interested about the operation of the FACE Library.

The primary goal of this document is to define the operational and functional requirements for identification, storage, management, and distribution of FACE Certified Products. This document also communicates the organization and functionality of the FACE Library to stakeholders in government, industry, and academia.

1.1 Scope

The basic FACE Library overview, concept, and functionality are summarized in this document. This document updates those requirements and addresses requirements for the FACE Landing Page, the FACE Certification and Verification Retention Repositories, and the FACE Shared Data Model Reference Repository.

This version of the document is intended to address US stakeholders only; future versions of this document will address international requirements.

1.2 Assumptions

The following assumptions have been identified as relevant to this document:

1. Only products that have achieved FACE Conformance Certification are listed in the FACE Library.

2. The FACE Library is the single reference listing for FACE Certified Products.

3. FACE Certified Product discovery is publicly accessible:

a. All FACE Library metadata is approved for public release.

b. FACE Library metadata is accessible by all stakeholders (including industry competitors).

c. The FACE Consortium is not responsible for ensuring information is approved for public release.

4. The FACE Library supports multiple, independent FACE Repositories to enable stakeholders to protect intellectual property and data.

5. Acquisition of FACE Certified Products is a business transaction between two independent entities. The FACE Library is not responsible for implementing methods to conduct these business transactions.


6. The FACE Library supports multiple FACE Verification Retention Repositories and a single FACE Certification Retention Repository.

1.3 Related Documents

The following is a list of references used in developing this document:

1. Future Airborne Capability Environment (FACE) Technical Standard

2. FACE Business Guide

3. FACE Conformance Policy

4. FACE Contract Guide


2. Library Overview

The FACE Library consists of the following components (see Figure 1):

1. FACE Landing Page

2. FACE Library Portal

3. FACE Registry

4. FACE Product Repositories

5. FACE Reference Repository

6. FACE Certification Retention Repository

7. FACE Verification Retention Repositories

8. FACE Shared Data Model Reference Repository

Figure 1: FACE Library Overview

2.1 FACE Landing Page

The FACE Landing Page is the public-facing web site for the FACE Consortium. The entry point for all components of the FACE Library is via the FACE Landing Page. This page serves to direct users to relevant FACE content. Content on the FACE Landing Page includes:

1. General information about the FACE Consortium and its products

FACE Library

Main FACE Landing Page

Registry

Reference Repository

Product Repositorie

s

• FACE Certified Product listings • Searchable Metadata

• FACE Certified Products and associated artifacts

• Development

/ Testing Tools • FACE Business

Guide • FACE Technical Guide • FACE Contracting Guide

Shared Data

Model Referenc

e Repository

• FACE data model and extensions

Verification Retention Repositorie

s

• Software Verification Package • Digital Signature • Verification Results

Certification Retention Repository

• Verification Results • Digital Signature • Legal Agreements • Certification Results

FACE Library Porta

l

• Role

- based user access and interaction

with FACE Library Repositories

• General FACE information • Consortium POCs • Upcoming Events


2. Upcoming FACE events

3. Recent FACE procurements

4. Links to specific FACE content

2.2 FACE Library Portal

Access to FACE Repositories is controlled through the FACE Library Portal. This portal is accessed via the FACE Landing Page. The FACE Library Portal facilitates moving data through FACE Consortium defined processes. The FACE Library Portal facilitates populating the FACE Reference Repository, enabling discovery by users needing specific FACE-related documents and tools. The FACE Library Portal also controls the flow of information into the FACE Conformance Program to ensure data is transferred from the correct source and provided to the correct authority. The FACE Library Portal authenticates each transaction by enforcing a set of privileges retrieved through login information.

The FACE Library Portal enables FACE-defined processes such as:

1. System Integrators use the FACE Library Portal to find FACE Certified Products that Software Suppliers have developed and that have completed FACE Conformance Certification and registration process.

2. To facilitate the FACE Conformance processes, the FACE Library Portal enables submission of verification data and ensures that a product remains synced with its metadata and other artifacts.

3. Software Suppliers request an account and login to initiate a FACE Registry submittal following successful completion of the FACE Conformance process. The privileges associated with an authenticated Software Supplier allow the Software Supplier to provide metadata associated with their product, the Digital Signature for reference, and other information to be included in the FACE Registry for FACE Certified Products.

4. Once a product’s metadata is stored in the FACE Registry, the FACE Library Portal enables a user to initiate a search to find FACE Certified Products. Users view the product’s metadata to discover information necessary to acquire the product.

5. Users access the FACE Library Portal to collect metrics about a product or group of products.

2.3 FACE Registry

The FACE Registry is the single source for listing all FACE Certified Products. The FACE Registry is the gateway to finding FACE Certified Products that are stored in a FACE Repository. The FACE Registry provides a central point for users to access a searchable listing of all products and information available in the FACE Repositories. The FACE Registry requires a user to register and be authenticated prior to being directed to a FACE Repository.

The FACE Registry allows full public access, presenting only information that is approved for public release. Only products that are FACE Certified Products are listed in the FACE Registry.


2.4 FACE Library Repositories

FACE Certified Products are stored in a FACE Library Repository that meets the minimum requirements described in this document. FACE Library Repositories may be owned and managed by for-profit companies, government agencies, or other organizations. Information about each FACE Certified Product or application stored in any of these FACE Library Repositories is linked to the FACE Registry.

All FACE Library Repositories employ Configuration Management (CM) to address the CM elements of CM planning, configuration identification, configuration control, configuration status accounting, and configuration verification and audits. Policies for implementing sufficient CM will be documented in a follow-on document: FACE Library Governance.

2.4.1 FACE Product Repositories

A FACE Product Repository may be controlled and managed by the FACE Consortium, a for-profit company, a government organization, or an academic institution. FACE Product Repository owners determine specific access controls.

Software Suppliers are responsible for ensuring the integrity of FACE Certified Products stored in a FACE Product Repository under their control/management in accordance with the FACE Conformance Policy. The minimal requirements for a FACE Product Repository are described in this document.

2.4.2 FACE Reference Repositories

A FACE Reference Repository maintains products that are used for reference purposes to understand the FACE process, contracting efforts, and to maintain available tools available for download. Examples of documents and tools that are stored in a FACE Reference Repository include:

1. FACE Conformance Test Tools

2. FACE Technical Standard

3. FACE Business Guide

4. FACE Conformance Policy

A FACE Reference Repository may be controlled and managed by the FACE Consortium, a for-profit company, a government organization, or academia.

2.4.3 FACE Certification Retention Repository

The Certification Authority retains a copy of the files generated during certification for each software product that completes FACE Conformance Certification. A FACE Certification Retention Repository is used to store these files. Access to this Repository is restricted to the Certification Authority and a designated Auditor.

The set of files for FACE Conformance Certification includes the following:

1. Verification Statement

2. Digital Signature

3. Conformance Statement


4. Conformance Certificate

5. Legal Agreements

2.4.4 FACE Verification Retention Repositories

The Verification Authority retains a copy of the Verification Package, Digital Signature, and the Verification Results Package for each software product that completes FACE Conformance Verification. A FACE Verification Retention Repository is used to store these files. Access to the Repository is restricted to the associated Verification Authority and a designated Auditor. Each Verification Authority maintains its own FACE Verification Retention Repository.

2.4.5 FACE Shared Data Model Reference Repository

The FACE Shared Data Model Reference Repository is the information technology asset that contains and provides access to the Shared Data Model.

The Shared Data Model is a common data model that is used as the basis for development of specific Unit of Portability (UoP) and System Data Models. The Shared Data Model is populated from information contained in conformant UoP data models and changes input by the Data Model Configuration Control Board (CCB).


3. Requirements

3.1 FACE Landing Page Requirements

1. The FACE Landing Page shall be hosted on a publicly available, secure web server.

2. The FACE Landing Page shall have content pages and navigation links that are updatable as directed by the FACE Consortium.

3. The FACE Landing Page shall be capable of archiving the previous three versions.

4. The FACE Landing Page shall be discoverable by public Internet search engines.

5. The FACE Registry shall be able to export metrics to external analysis tools.

6. The FACE Landing Page shall provide access to the FACE Library Portal.

7. The FACE Landing Page will ensure sufficient Configuration Management (CM), as described in Section 2.4.

3.2 FACE Library Portal Requirements

8. The FACE Library Portal shall provide a list of Verification Authorities and their contact information.

9. The FACE Library Portal shall update the list of Verification Authorities as directed by the FACE Consortium.

10. The FACE Library Portal shall provide a metrics report with the following information:

a. Number of page visits

b. Number of unique visitors

c. Internet Protocol (IP) address of page visitors

11. The FACE Library Portal shall host a FACE Library Portal user’s guide.

12. The FACE Library Portal shall provide role-based user authentication and access privileges as defined in the table below:

Privilege

FACE Library Portal

FACE Reference Repository

FACE Certification

Retention Repository

FACE Registry

FACE Shared Data Model Reference Repository

Verification Authority Write Read — Read Read

Software Supplier Write Read — Read/Write Read

Certification Authority Read/Write Read Read/Write Read Read


Privilege

FACE Library Portal

FACE Reference Repository

FACE Certification

Retention Repository

FACE Registry

FACE Shared Data Model Reference Repository

Reference Repository — Write — Read Read

Data Model — Read —- Read Read/Write

13. The FACE Library Portal shall provide user access to the FACE Shared Data Model Reference Repository.

14. The FACE Library Portal shall provide user access to FACE Consortium work products and tools in the FACE Reference Repository.

15. The FACE Library Portal shall provide a mechanism to collect and manage feedback from users on FACE Consortium work products and tools.

16. The FACE Library Portal shall enable discovery of information about FACE business practices (i.e., business model, contracting guide, etc.).

17. The FACE Library Portal shall provide user access to the FACE Registry.

18. The FACE Library Portal shall allow a user to submit search queries on product metadata in the FACE Registry and return results.

19. The FACE Library Portal shall allow the user to browse listings of FACE Certified Products in the FACE Registry.

20. The FACE Library Portal shall provide guidance to a Software Supplier on how to submit a product for verification, certification, and registration.

21. The FACE Library Portal shall assign a single unique identifier to associate a single product with its associated verification, certification, and registration data.

22. The FACE Library Portal shall allow a Software Supplier to securely submit a verified product and its associated artifacts and metadata for FACE Conformance Certification as defined in the FACE Conformance Policy.

23. The FACE Library Portal shall restrict a Software Supplier to read-only access to the artifacts submitted to the FACE Certification Retention Repository after submission.

24. The FACE Library Portal shall allow a Verification Authority to securely submit a Verification Results Package and Digital Signature.

25. The FACE Library Portal shall provide notification to the Software Supplier upon successful completion of the FACE Conformance Certification process.

26. The FACE Library Portal shall allow a Software Supplier to submit a FACE Certified Product and its associated artifacts and metadata for registration.

27. The FACE Library Portal shall provide notification to the Software Supplier upon successful completion of the registration process.

28. The FACE Library Portal shall allow the Certification Authority to securely submit a Certification Results Package and Digital Signature.


29. The FACE Library Portal shall allow a Software Supplier to modify and update metadata information on registered FACE Certified Products.

30. The FACE Library Portal shall allow a Software Supplier to remove a FACE Certified Product from the FACE Registry.

31. The FACE Library Portal shall allow public access to the FACE Registry.

32. The FACE Library Portal shall link to the FACE Landing Page.

33. The FACE Library Portal shall require positive affirmation of public availability of submitted metadata.

34. The FACE Library Portal shall display a privacy statement upon initial login.

35. The FACE Library Portal shall protect the FACE Library from unauthorized modification.

36. The FACE Library Portal shall enable verification of data integrity.

37. The FACE Library Portal shall have intrusion detection capability.

38. The FACE Library Portal shall have tamper detection capability.

3.3 FACE Registry Requirements

39. The FACE Library shall provide a single FACE Registry.

40. The FACE Registry shall be hosted on a publicly available, secure web server.

41. The FACE Registry shall be backed up daily.

42. The FACE Registry shall allow the offline backup of all content of the web site itself and the stored product information.

43. The FACE Registry shall capture metrics (raw data) about the FACE Library:

a. The FACE Registry shall capture the number of page visits.

b. The FACE Registry shall capture the number of unique visitors.

c. The FACE Registry shall capture the Internet Protocol (IP) address of page visitors.

d. The FACE Registry shall capture search terms.

44. The FACE Registry shall enable distribution of search analytics.

45. The FACE Registry shall restrict access to metrics data based on a user’s role.

46. The FACE Registry shall store product metadata as defined in Appendix A.

47. The FACE Registry shall provide the capability to compare selected products based on filtered metadata.

48. The FACE Registry shall enable search by the metadata.

49. The FACE Registry shall support downloading of metadata content.


50. The FACE Registry shall provide the capability to download search comparison results.

51. The FACE Registry shall interface with the FACE Library Portal.

52. The FACE Registry shall export metrics to external analysis tools.

53. The FACE Registry shall have a Configuration Management (CM) plan that addresses the CM elements defined in Section 2.4.

3.4 FACE Repository Requirements

3.4.1 Common FACE Repository Requirements

54. FACE Repositories shall be secure.

55. FACE Repositories shall enable authenticated access control.

56. FACE Repositories shall have a Configuration Management (CM) plan that addresses the CM elements defined in Section 2.4.

57. FACE Repositories shall permit removal of products.

3.4.2 FACE Reference Repository Requirements

58. The FACE Library shall provide a single FACE Reference Repository.

59. The FACE Reference Repository shall only accept products that have been approved by the FACE Consortium for publication.

60. Only FACE Reference Repository administrators shall be able to upload a reference product.

61. The FACE Reference Repository shall maintain all previous versions of stored work products and tools.

62. The FACE Reference Repository shall store metadata for work products and tools as defined in Appendix C.

63. The FACE Reference Repository shall link to the FACE Library Portal.

64. The FACE Reference Repository shall allow for downloading of FACE work products and tools.

3.4.3 FACE Product Repository Requirements

65. The FACE Product Repository shall interface with the FACE Library Portal.

66. The FACE Library shall allow multiple, independent FACE Product Repositories.

67. A FACE Product Repository shall store only FACE Certified Products and associated artifacts and metadata as defined in Appendix B.

68. The FACE Product Repository shall limit access to approved users.

69. The FACE Product Repository shall allow for auditing of a product using its Digital Signature by a FACE Administrator/Auditor.


70. The FACE Product Repository shall enable retrieval of a FACE Certified Product and its associated artifacts.

71. The FACE Product Repository shall retain a FACE Certified Product for the duration the product is listed in the FACE Registry.

3.4.4 FACE Certification Retention Repository Requirements

72. The FACE Certification Retention Repository shall interface with the FACE Library Portal.

73. The FACE Library shall provide a single FACE Certification Retention Repository.

74. The FACE Certification Retention Repository shall contain a working sub-section.

75. The working sub-section of the FACE Certification Retention Repository shall be restricted to Software Suppliers and the Certification Authority.

76. The FACE Certification Retention Repository shall contain a retention sub-section.

77. The retention sub-section of the FACE Certification Retention Repository shall only be accessible by the Certification Authority and designated Auditor.

78. The FACE Certification Retention Repository shall enable selective deletion of contents within all subsections when selected by the Certification Authority.

79. The FACE Certification Retention Repository shall enable selective moving of contents within all subsections when selected by the Certification Authority.

80. The FACE Certification Retention Repository shall contain a directed output sub-section.

81. The directed output sub-section of the FACE Certification Retention Repository shall be accessible by the Certification Authority for Software Supplier output.

3.4.5 FACE Verification Retention Repository Requirements

82. The FACE Library shall allow multiple, independent FACE Verification Retention Repositories.

83. A FACE Verification Retention Repository shall interface with the FACE Library Portal.

84. A FACE Verification Retention Repository shall contain a working sub-section.

85. The working sub-section of a FACE Verification Retention Repository shall be accessible by only the Software Supplier and the Verification Authority.

86. A FACE Verification Retention Repository shall contain a retention sub-section.

87. The retention sub-section of a FACE Verification Retention Repository shall be accessible by only the Verification Authority and designated Auditor.

88. The FACE Verification Retention Repository shall enable selective deletion of contents within all subsections when selected by the Verification Authority.

89. The FACE Verification Retention Repository shall enable selective moving of contents within all subsections when selected by the Verification Authority.


90. A FACE Verification Retention Repository shall contain a directed output sub-section.

91. The direct output sub-section of a FACE Verification Retention Repository shall be accessible by only Software Supplier output and the Verification Authority.

3.4.6 FACE Shared Data Model Reference Repository Requirements

92. The FACE Shared Data Model Reference Repository shall interface with the FACE Library Portal.

93. The FACE Library will develop and maintain a single FACE Shared Data Model Reference Repository.

94. The FACE Shared Data Model Reference Repository shall enable storage of the FACE Shared Data Model and its attributes.

95. The FACE Shared Data Model Reference Repository shall support versioning of the data model in accordance with the data model governance process.

96. The FACE Shared Data Model Reference Repository shall enable storage of FACE UoP Platform Data Models and its attributes.

97. Bulk updates shall be submitted to the FACE Shared Data Model Reference Repository in the format of Object Management Group (OMG) eXtensible Markup Language (XML) Metadata Interchange (XMI) data defined by the FACE OMG Meta Object Facility (MOF)-based metamodel.

98. Subsets of the data stored in the FACE Shared Data Model Reference Repository shall be available for retrieval as (XMI) data.

99. The FACE Shared Data Model Reference Repository shall store all data elements.

100. The FACE Shared Data Model Reference Repository shall retrieve all data elements.

101. The FACE Shared Data Model Reference Repository shall store data model views defined in accordance with the FACE Technical Standard.

102. The FACE Shared Data Model Reference Repository shall retrieve data model views defined in accordance with the FACE Technical Standard.

103. The FACE Shared Data Model Reference Repository shall enable searching based on filtered characteristics of XMI data.

104. The FACE Shared Data Model Reference Repository shall enable filtering capabilities.

105. The FACE Shared Data Model Reference Repository shall enable sub-setting capabilities.

106. The FACE Shared Data Model Reference Repository shall support automated updating with versioning of the data model and metadata.

107. The FACE Shared Data Model Reference Repository shall enable data model search, retrieval, and storage without installation of a local tool.

108. The FACE Shared Data Model Reference Repository shall provide the ability to load new data into a “staging” area for review prior to approval.


109. The FACE Shared Data Model Reference Repository shall support comparison of two data models to identify differences.

110. The FACE Shared Data Model Reference Repository shall support identification of all changes to the data model.

111. The FACE Shared Data Model Reference Repository shall store information related to each change to the data model.

112. The FACE Shared Data Model Reference Repository shall support migration of data between versions of the metamodel.

113. The FACE Shared Data Model Reference Repository shall support validation of the data model to the metamodel.

114. The FACE Shared Data Model Reference Repository shall support validation of the data model against constraints defined using the OMG Object Constraint Language (OCL).

115. The FACE Shared Data Model Reference Repository shall support generation of unique Meta Object Facility (MOF) identifiers.

116. The FACE Shared Data Model Reference Repository shall support identification of the data upon which a data element depends.

117. The FACE Shared Data Model Reference Repository shall support the ability to dynamically add new meta information about a data element without invalidating the data model.

118. The FACE Shared Data Model Reference Repository shall support storage of at least 10 million Meta Object Facility (MOF) data elements.

119. The FACE Shared Data Model Reference Repository shall support at least 100 simultaneous read accesses.

120. The FACE Shared Data Model Reference Repository shall support draft storage of private user data models prior to conformance.

121. The FACE Shared Data Model Reference Repository shall support publishing private user data models without requiring conformance.

122. The FACE Shared Data Model Reference Repository shall support end-user access via a wide area network (Internet).

123. The FACE Shared Data Model Reference Repository shall support batch loading of very large data sets (hundreds of thousands of data elements).

124. The FACE Shared Data Model Reference Repository shall enforce validation upon modification of the data model.

125. The FACE Shared Data Model Reference Repository shall support both internal and external validation methods.

126. The FACE Shared Data Model Reference Repository shall support rollback to previous save points.

127. The FACE Shared Data Model Reference Repository shall provide a list of errors when data fails validation.


128. The FACE Shared Data Model Reference Repository shall support modification of data down to the granularity of the metamodel.


A FACE Registry Metadata

Metadata Metadata Description

Name of product The formal name of the product.

Acronym The abbreviated name for the product.

FACE Conformance Certificate The FACE Conformance Certificate from the Certification Authority.

FACE Base Line (B/L) Version number of the FACE Technical Standard that the product was certified against.

Product Version The specific product version number certified as conformant to the FACE Technical Standard.

Date of Approval The date the product was certified as conformant to the FACE Technical Standard.

Software Supplier’s Name The name of the organization or company providing the product.

Software Supplier’s Address The address of the organization or company providing the product.

Software Supplier Point of Contact (POC)

The title, name, and contact information of the primary person to be contacted.

Licensing Categories Licensing category that describes who owns the licensing rights to the product.

FACE Repository Links Individual or multiple web-based links from the FACE Registry to any appropriate FACE Repository and/or back to any vendor's web site. Links shall also take the form of email links.

Key Words Identification of key words that describe the product for searching purposes.

Product Background Identifies whether the product has been used before and provides some high-level descriptions or where or how without mentioning the aviation platforms. Also describers the organization(s) supported.

Description Free text description of the FACE Certified Product.

Safety Certifications Applicable product safety certifications and certifying authority.

Security Certifications Applicable product security certifications and certifying authority.

Information Assurance (IA) Certifications

Applicable product IA certifications and certifying authority.


Metadata Metadata Description

Applicable Domain(s) Refers to the applicable domains; i.e., the kinds of purposes for which users use the FACE intellectual property, software, or software system/product. Domain may include: application, administrative, CLR, data, domain driven design, domain model, domain-specific language, domain-specific modeling, etc. For the purposes of FACE, “application domains” are most applicable.

Applicable Segment(s) The segment or layer within the FACE Technical Standard such as application, transport, platform-specific, operating, etc. (Segment selection will be mutually exclusive.)

Dependencies Applicable hardware or software dependencies.

Digital Signature Digital Signature provided by the Certification Authority.

Previous Versions FACE Registry links to previous versions of the product.

Logo Company/product logo.

FACE Profile Identifies which FACE Profiles are supported by the product.

OS API Type Identifies FACE operating system requirements for the product.

Flash Memory Size Minimum static memory requirements (OFP footprint).

RAM Memory Size Minimum dynamic memory requirements.

Application Interfaces Listing of exposed product application interfaces.

Available Artifacts Listing of artifacts available in the linked FACE Repository entry.


B FACE Product Repository Metadata

Metadata

Development/Testing Tools Models

Source Code

Airworthiness Qualification Plan

PSAC/AQS

Software Development Plan

Configuration Management Plan

Software Quality Assurance Plan

Test & Evaluation Master Plan

Open Systems Management Plan

Software Architecture Evaluation Plan

System Engineering Plan

Software Transition Plan

Risk Management Plan

Software Test Plan

Lifecycle Cost Management Plan

Integrated Master Schedule

Plans

Data Accession List

System/Subsystem Design Document

System/Software Requirements Specification

API Specification (tool-generated document that is a combination of SRS and ICD)

Requirements Trace and Verification Matrix

Software Design Document

Software Version Description

Design and Specification

SCM Records


Metadata

SQA Records

Prime Item Development Specifications

Interface Requirement Specification

System Architecture Description

Software Architecture Description

System Safety Program Plan

Preliminary Hazard Assessment

Failure Mode Effects and Criticality Analysis

Functional Hazard Assessment

System (Software) Safety Assessment

Safety Analysis

Safety Assessment Report (Software)

Architecture Peer Review Results

PDR/CDR/TRR/FRR Milestone Review Exit Criteria Achieved

Source Code Peer Reviews

SIL Configuration Audit

Software Test Procedures Peer Review Results

Software Architecture Assessment Report

Software Re-use Management Report

Physical Configuration Audit Report

Reviews

Functional Configuration Audit Report

Unit Test Results (developer document)

Software Test Plan

Software Verification Cases and Procedures (SVCP)

Software Test Results

Software Robustness Test Results

Performance Test Results

Statement Coverage Analysis Report

Test Artifacts

Static Code Analysis Report


Metadata

Integration Test Plan

Integration Test Results

Software Problems Reports

Software Change Requests

CCB Minutes

Action Items

Software Accomplishment Summary

Version Description Document

User Manual Training Documentation

Installation Guide


C FACE Reference Repository Metadata

Metadata

Common Name

Status

Service Category

Service

Type

Reference #

US ISBN

Subject