||CJCSI 6212.01C: Interoperability and Supportability of Information Technology and Nation
7. NR-KPP Development
7. NR-KPP Development. Development of the NR-KPP begins with
designing the architecture for the proposed system. Without an architecture
the systems will not meet its goals nor meet any interoperability
requirements. Each architecture view has a purpose and can be traced back to
the operational concept.
a. Step 1. Develop the mandatory architecture views.
(1) The format and description for all of the architectural views will
be IAW with the most current version of the DOD Architecture Framework (reference n). All of the fields/columns
for each architecture view from reference n are mandatory.
(2) A short description of the view, its intended use and a discussion
of the top-top leveltop level exchanges will accompany each view. The
narrative for each view should be as concise as possible while still
giving the necessary explanation of the view. A length of ½ page or less
is ideal; some views may require a longer narrative.
b. Step 2. Complete the CRD Crosswalk.
The format for the crosswalk for a particular CRD is found in an appendix in
the applicable CRD. However, if the applicable CRD does not have a
crosswalk, use the format shown in Table
c. Step 3. Build a DISR online standards
profile. This profile is required prior to submitting the ISP. See Enclosure L.
d. Step 4. Complete a LISI interoperability
requirements profile. This profile is required prior to submitting the ISP.
See Enclosure K.
e. Step 5. Include the NR-KPP statement. The
NR-KPP definition statement will document that all requirements will be
satisfied to the standards specified in the threshold and objective values.
See Table I-1 below.
|All activity interfaces, services,
policy-enforcement controls, and data-sharing of the NCOW-RM and GIG-KIPs
will be satisfied to the requirements of the specific Joint integrated
architecture products (including data correctness, data availability and
data processing*), and information assurance accreditation specified in
the threshold (T) and objective (O) values.
||100 percent of interfaces, services,
policy-enforcement controls, data correctness, availability and
processing* requirements designated as enterprise-level or critical in the
|100 percent of interfaces services,
policy-enforcement controls, data correctness, availability|
processing* requirements in the Joint integrated
Table I-1. ISP NR-KPP Statement
* Data processing is defined as: The input, output,
verification, organization, storage, retrieval, transformation, and
extraction of information from data.
f. Step 6. Include the Key Interface Profile
(KIP) Implementation Statement. The statement expands on the declaration
given in the CDD to include an explanation of how well the design complies
with the KIPs. It includes the required KIP specification values and
the corresponding system design values. The KIP statement alone does
not ensure interoperability; a system must also be designed against the
appropriate architectures, most current version of the DISR and IA
g. Step 7. Complete an IA compliance