Small Computer Based Configuration Management
Sobczak competed to support the USAF at Wright Patterson AFB by providing non-personal services. The areas where we helped were Configuration and Logistics Management for seven (7) System Program Offices (SPOs).
ADVANCED AUTOMATED CONFIGURATION TRACKING INFORMATION ON-LINE
NETWORK STATEMENT OF WORK
BACKGROUND:
Modern software development requires the use of a Knowledge Base Configuration
information system that provide control of Advanced Change Study Notices (ACSNs),
Engineering Change Proposals (ECPs), and other Configuration Change Management
documents. The Automated Configuration Tracking On-line Network (ACTION) is a
composite of the optimum requirements of the primier systems in use across the spectrum
of the Federal Government and theoretically defined by the NDU Program Managers
Program. This Statement of Work (SOW) addresses the deployment of an advanced
version (AACTION) for major system access, including software maintenance and training.
Sobczak shall complete the following tasks associated with this SOW in the non-
traditional manner described herein. The services described shall be accomplished
according to the phases outlined below. The sponsor technical contract monitor is
responsible for the tasking, technical liaison review, approval, and final acceptance of all
services and products delivered under this SOW.
PHASE I: REMOTE ACCESS SETUP AND DEPLOYMENT OF AACTION FOR USE
1.0 Set up user accounts as required.
1.1 Install data line, terminal, printer and communications equipment to allow interface
at a 56000 baud rate.
1.2 Setup/Configure existing micro computers to allow interface at a 2400 baud rate
and above and assure that the stand alone microcomputer version is operational.
1.3 Coordinate initial training for use of integrated AACTION.
1.4 Determine the required modifications to the F-16 SPO system's input screens to
support local user level of comfort. Nature of modifications shall be limited to field
names/terminology.
1.5 Modify input screens, records structures, and reports accordingly.
PHASE II: SOFTWARE REQUIREMENTS ANALYSIS FOR AUTOMATED PROGRAM
CONTROL BUDGET EXECUTION.
Sobczak shall define and analyze a complete set of functional performance, interface
and qualification requirements in accordance with overall system requirements listed in
Phase II to include:
2.1 Review Directorates and collect documentation concerning existing
configuration/change management data bases resident on micro-computers and/or
mini-computers wherever located.
2.2 Review existing computer hardware and develop the distribution network/LAN
philosophy which best utilize available resources optimized per this IRD.
2.3 Build a relational matrix to plot the level of automation activity for the purpose
of optimizing the integration of data bases, showing functional and interface requirements.
2.4 Build data use matrixes for the identified data bases chosen for integration and
generate a baseline glossary and an index of use.
2.5 Generate cross index of comparable definitions presently identified by
non-common terminology, i.e., ACSN = Pre-ECP = Draft ECP = etc.
2.6 Analyze the reports defined, as appropriate, from the overview analysis and
determine optimal strategies to integrate data delivery.
2.7 Develop a Part I specification detailing functional interfaces and necessary design
constraints for the integration of data bases to include the modular program concept to
optimize software reliability and maintainability.
2.8 Develop new or tailor existing SIID type architectures to reflect the unique
requirements of the budget and cost reporting system.
PHASE III: PRELIMINARY SYSTEM DESIGN FOR DATA BASES AND OUTPUT
SYSTEMS.
3.1 Sobczak shall produce preliminary versions of top level software, interface and
data base design of a knowledge base of the six major management segments listed
below. The design shall encompass the decomposition of each top-level computer
software component (TLCSC) into a complete work breakdown structure of lower-level
computer software component prior to the detail design phase. The System Design shall
address the below listed disciplines:
Configuration Management:
Configuration Control Board Directive (CCBD)
Configuration Identification (CI)
Configuration Audits:
Functional Configuration Audit (FCA)
Physical Configuration Audit (PCA)
Status Accounting and Change Control:
Engineering Change Proposal (ECP)
Facility Engineering Change Proposal (FECP)
Contract Change Proposal (CCP)/Task Change
Proposal (TCP)
Advanced Change Study Notice (ACSN)
Request for Deviation/Waiver (D/W)
Specification Change Notice (SCN)
Interface Change Notice (ICN)
Document Change Notice (DCN)
Request for Contract Change Proposal (RFCCP)
Data Management (DM):
Contract Data Requirements List (CDRL)
Data Identification Description (DID)
Contract Documentation:
Change Orders (CO)
Supplemental Agreements (SA)
Procurement Contracting Officer (PCO) Letters
Suspense Tracking:
Document Flow
Review Item Discrepancy (RID) Status
Problem Reporting
Quality Assurance
Trend Analysis
CM Review Action Items
DM Review Action Items
Design Reviews and Configuration Audits
Program Control:
Cost/Schedule Performance Measurement
Value Profile and Analysis
Traceability of Associated Documentation with Cost
PHASE IV: DETAIL DESIGN
4.1 Sobczak shall establish complete modular, lower level design by refining the Top
Level Computer Software Component (TLCSC) into Lower Level Computer Software
Components (LLCSC) and Units. Each Unit shall perform a single function.
4.2 Sobczak shall identify:
a. All required details for implementing external interfaces, including item
summary and item format for each interface.
b. Global data definitions within each TLCSC.
c. Inputs, local data definitions, process control requirements,
processing, utilization of other elements, limitations, and outputs of all LLCSCs.
d. Inputs, local data definitions, process control requirements,
processing, special control features, protection, error handling, utilization of other elements,
limitations, and outputs for all Units.
e. Detailed data base design including data base management system
overview, data base structure, data base file design, and data base references.
4.3 Sobczak shall refine all TLCSCs using a top-down design approach, unless
specific alternate methodologies have been proposed and have received contracting
agency approval.
4.3.1 Sobczak may depart from a top-down approach to:
a. Address critical lower-level elements, or
b. Incorporate commercially available, reusable, and Government
furnished software. The contractor shall describe the criteria for determining critical
lower-level elements in either the SSPM or SDP.
4.4 In the development of the detailed design for each TLCSC the contractor shall
employ a program design language.
4.5 Sobczak shall monitor size and time estimates for the Computer Software
Configuration Item (CSCI) and adjust the estimates if necessary. All modifications to
controlled or baselined documentation shall be made in accordance with the configuration
management requirements contained in DoD-STD-2167.
4.6 Sobczak shall establish Software Development Files (SDFs) for all Units. Each
SDF may serve a single Unit or logically related group of Units. Unit requirements, design
considerations and constraints, schedule, status information, and test documentation shall
be incorporated into the corresponding SDF. To reduce duplication, SDFs should not
contain information provided in other documents. SDFs may be generated, maintained,
and controlled by automated means.
4.7 Sobczak shall document additional engineering information generated in the
design process for each CSCI. The engineering information shall include rationale, results
of analyses and trade-off studies, and any other information which aids in understanding
the detailed design.
4.8 Sobczak shall identify the test requirements responsibilities, and schedule for the
informal testing to be conducted for each Unit, and shall record them in the corresponding
SDF.
4.9 Sobczak shall produce updated versions of the SDF as necessary.
4.10 Sobczak shall produce records and summary reports of the internal reviews
conducted.
4.11 Sobczak shall establish and maintain SDFs for all Units.
4.12 Sobczak shall produce a Software Programmer's Manual (SPM) and a Firmware
Support Manual (FSM).
4.13 Formal Reviews - Detailed Design. The contractor shall present the Software
Detail Design Document (SDDD) and the Software Test Document (STD) for each CSCI
at a Critical Design Review (CDR). Specific details regarding the CDR process are
contained in MIL-STD-1521.
4.14 Developmental Configuration - Detailed Design. Upon successful completion of
the CDR, the contractor shall enter the SDDD, for each CSCI into the Developmental
Configuration for the CSCI.
PHASE V: CODING AND UNIT TESTING. THE CONTRACTOR SHALL CODE
AND TEST EACH UNIT MAKING UP THE DETAILED DESIGN.
5.1 The contractor shall code and test Units in top-down sequence, unless alternate
methodologies have been proposed and have received contracting agency approval.
5.1.1 The contractor shall follow design and coding standards outlined in
DoD-STD-2167, Appendix C.
5.2 The contractor may depart from a top-down approach to:
a. Code and test critical Units, or
b. Incorporate commercially available, reusable, or Government furnished
software.
5.3 The contractor shall code all Units in accordance with coding standards.
5.4 The contractor shall produce deliverable code that can be regenerated and
maintained using only Government-owned, contractually deliverable, or commercially
available support software and hardware.
5.5 Prior to the testing of each Unit, the contractor shall prepare and record in the
SDF test procedures for conducting each informal Unit test.
5.6 The contractor shall perform informal Unit tests according to the Unit test
procedures contained in the SDF.
5.7 The contractor shall record in the SDF the test results of all informal Unit testing.
5.8 The contractor shall make necessary revisions to the design documentation and
code, and shall update the SDFs of all Units that undergo design or coding changes based
on Unit tests.
5.9 The contractor shall enter into the Developmental Configuration and release for
integration each coded Unit that has been successfully tested and reviewed.
PHASE VI: INTEGRATION AND TESTING
6.1 The contractor shall integrate Units of code entered in the Developmental
Configuration and perform informal tests on aggregates of integrated Units.
6.2 The contractor shall monitor the development effort for consistency with the
Software Development Plan (SDP).
6.3 The contractor shall integrate and test aggregates of Units in a top-down
sequence, unless alternate methodologies have been proposed in either the Software
Standards and Procedures Manual (SSPM) or SDP and have received contracting agency
approval.
6.3.1 The contractor may depart from a top-down approach to:
a. Integrate or test critical Units, or
b. Incorporate commercially available, reusable, and
Government furnished software. The contractor
shall describe the criteria for determining critical
Units in either the SSPM or SDP.
6.4 As Units are successively integrated with one another, the contractor shall
compare memory and processing time values with allocations established during
Preliminary and Detailed Design. The contractor shall also compare any system resources
affected by the integrated Units with specified requirements (e.g., secondary storage,
communication channel utilization, etc.). Sobczak shall modify, as necessary, all controlled
or base lined documentation based on the memory, processing time, and system
resources comparisons. All modifications to controlled or base lined documentation shall
be made in accordance with the configuration management requirements contained in
DoD-STD-1521.
6.5 The contractor shall document the results of all integration testing in the standard
format described in the SDP.
6.6 The contractor shall make necessary revisions to the design documentation and
code, perform all necessary retesting, and update the SDFs of all Units that undergo
design or coding changes based on integration tests.
6.7 The contractor shall complete preparation of detailed procedures for conducting
each formal CSCI test and for analyzing formal test results.
6.8 The contractor shall update with additional known details all information and
instructions pertaining to computer system operation, software operation by users,
computer system diagnostics, programming or reprogramming software for the target
computer, and modifying or replacing firmware.
6.9 Sobczak shall conduct internal in-process reviews during this phase and shall
make all necessary changes based on the results of the internal reviews, prior to
presenting the informal test results, completed formal CSCI test procedures, and
subsequently update operation and support documentation to the contracting agency.
PHASE VII: PRODUCTION AND DEPLOYMENT
7.1 Sobczak shall deploy the operational system on a DEC VAX 11/7XX OR 8XXX.
7.2 Sobczak shall provide lease time of the mini-computer system for real-time data
entry and retrieval during core hours (0700 - 1800) should a need exist for a non
government owned/operated computer. Lease charges shall include hourly use of
hardware, expendable supplies, communication lines and all other equipment to allow for
independent use of the system.
7.3 Sobczak shall provide software maintenance as necessary to remove latent
errors, enhance operations, further system evolution or incorporate knowledge gained from
operational use.
7.4 Sobczak shall provide all on-site user's training as required.
DATA REQUIREMENTS
The contractor shall produce the documents listed below in support of the system
described herein.
Data Requirements Title Applicable DID No.
Software Development Plan DI-MCCR-80030
Software Configuration Mgmt Plan DI-MCCR-80009
Software Requirements Specification DI-MCCR-80025
Software Top Level Design Document DI-MCCR-80012
Software Detailed Design Document DI-NCCR-80031
Interface Design Document DI-MCCR-80027
Data Base Design Document DI-MCCR-80028
Software Product Specification DI-MCCR-80029
Software Test Plan DI-MCCR-80014
Software User's Manual DI-MCCR-80019
Engineering Change Proposal DI-E-3128
Specification Change Notice DI-E-3134
AFFIRMATION
Sobczak has functioning a VAX version of AACTION. We have programmed and
operating a Microcomputer version. We will develop the design structure for automated
logical relations from the microcomputer to either a second microcomputer or a VAX. The
result to be a functioning software demonstration. A Phase 2 will extend the software into
a generic tool to assist those who choose to use it as a means of establishing logical
relations within and among projects/programs using exiting Federal and/or commercial
software configuration control packages.
CONTRACT: F33657-84-C-0090