8. CDD 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, or meet any
interoperability requirements. Each architecture view has a purpose that can
be traced back to an operational concept.
a. Step 1. Develop the mandatory architecture
views. Ideally, the CDD architecture views should be very much the same as
the ICD except with more detail.
(1) The format and description for all of the architectural
views will be IAW with the most current version of reference n. All 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 usually found in an
appendix of 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
(TV-1). This profile is required prior to submitting the CDD.
d. Step 4. Complete the initial LISI profile
(Interface Requirement Profile) using the INSPECQTOR tool. This profile is
required prior to submitting the CDD. 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.
The NR-KPP statement alone does not ensure interoperability requirements; a
system must also be designed against the appropriate architectures, most
current version of the DOD DISR and IA standards.