Download presentation
Presentation is loading. Please wait.
1
Configuration Management Case Study
Radar Training System Configuration Management Case Study Source: Cours de gestion de configuration, Ministère de la défense, Canada, 1989
2
Content Background Radar Training System (RTS) Requirements
Proposed system Hardware and software components Exercises CI selection CI identification Configuration Control Configuration status accounting Configuration audits CM Plan 12/28/2018
3
Background Present method for training radar technicians is based on textbooks and classroom lectures. The main focus is on the theory rather than the practice in the actual operation of radars. As a result, radar technicians are entering the field with little or no hands-on experience. This forces the student to learn "on the job". This situation places the organization at risk during training cycles and leads to inconsistency in the knowledge acquired by various radar technicians. 12/28/2018
4
Radar Training System Requirements
Shall simulate present radar systems (air, land and sea) Shall have an instructor's system and a student's system side-by-side that interact in the following manner: the instructor will be able to feed situations to the student's system, the instructor will be able to monitor the student's responses; Shall record the student's session (audio and video) for replay at a later date. 12/28/2018
5
Proposed Radar Training System
12/28/2018 12/28/2018
6
Hardware Components Each RTS is composed of the following:
(1) a cabinet, (2) two chassis, (3) two power supplies and cables, (4) two 5 1/4 inch floppy disks and controller card(s), (5) two 3 1/2 inch floppy disk and controller card(s) , (6) two hard disks and controller card(s), (7) two memory boards, (8) two chassis to chassis interface boards, (9) two monitors and interface board(s) , (10) two keyboards, (11) a tape backup device and two interface board(s) , (12) a data recorder and one interface board and tapes, (13) two chairs, (14) one chassis to chassis interface cable, and (15) one audio recorder and tapes. 12/28/2018
7
Software Components (1) UNIX Based Operating System
Provides all background functions including interfaces with monitor, keyboard, floppies and hard disk; (2) Command utility (menu selection for system access, selection environment, tape backup,system crash recovery, etc.), (3) Radar searching modules (land, sea, air) (4) Radar tracking modules (land, sea, air) (5) Radar targeting modules (land, sea, air) (6) Message handlers, (7) Tape backup software, (8) Data recorder software, and (9) Data files (example situations) 12/28/2018
8
Software Components The instructor's station will have the following added software: (1) Map Maker for creation of backgrounds, (2) Instructor Interface Module for the sending and receiving of information to/from the student's station, (3) Instructor Interrupt Module which allows the instructor to temporarily/permanently end the training session. 12/28/2018
9
Software Components In addition, the following support software is installed on the instructor's station: (I) Compiler, (2) Linker, (3) Loader, (4) Assembler, (5) Editor, (6) Programming Aids Package, (7) Software Library Package, (8) Software EPROM Programming Utility, (9) Test Data Files, (10) Hardware Diagnostics, and (11) Software Diagnostics. 12/28/2018
10
Exercise 1 Configuration Item Selection
Create two Configuration Item (CI) Breakdown Charts for the RTS From the government’s point of view and from the contractor's point of view. In other words, if you are the CM manager for the government what Configuration Items would you select and if you are the CM Manager for the contractor what Configuration Items would you select. Justify each selection by referring to the Configuration Item criteria discussed in class. 12/28/2018
11
Contractor CIs 12/28/2018
12
Government CIs 12/28/2018
13
Exercise 2 Configuration Item Identification
Task: The contractor shall: Develop numbering schemes for the CI Software Drawings Specifications 2. Determine the baselines to be established. Place them on a chart showing the life cycle phases State the documentation, software items which compose each baseline 12/28/2018
14
Exercise 2 Configuration Item Identification
Task 1 - Develop numbering schemes for the CI Method: SCM identifies each CI and all project-developed support software required for development and maintenance with unique names, numbers, and version identifiers. Example: “COMPASS-SW-SOM-3.1.0” COMPASS = CI Designator SW = Software (SW) or Firmware (FW) SOM = Software module Identifier (Scenario Operation Monitor) = Version/Revision/Patch 12/28/2018
15
Exercise 2 Configuration Item Identification
Task 2 - Determine the baselines to be established Functional Baseline: Documentation describing a system’s or items functional, interoperability and interface characteristics and the verification used to demonstrate their achievement Allocated Baseline: Documentation describing an item’s functional, interoperability and interface characteristics, allocated from a higher-level configuration item Product Baseline: Documentation describing all of the necessary functional and physical characteristics of the CI and the selected Functional and Physical characteristics designated for product acceptance testing and support Other Baseline: A/PDR, CDR, TRR, PRR. 12/28/2018
16
Task 2 - State the documentation, software items which compose each baseline
CI System Design System/Segment Design Document (SSDD) Interface Design Document (IDD) Database Design Description (DBDD) Program/Project Planning Computer Resources Life Cycle Management Plan (CRLCMP) Software Development Plan (SDP) Software Test Plan (STP) Software Installation Plan (SIP) Software Configuration Management Plan (SCMP) Software Quality Assurance Plan (SQAP) Software Requirements Specification (SRS) Interface Requirements Specification (IRS) Software Design Description (SDD) Interface Design Document (IDD) Data Base Design Document (DBDD) Software Test Description (STD) Software Test Report (STR) Software Version Description (SVD) Software User Manual (SUM) Software Input/Output Manual (SIOM) Software Center Operator Manual (SCOM) Computer Operator Manual (COM) Software Product Specification (SPS) 12/28/2018
17
Adapted from DoD Standard 2167A
Task 2 - State the documentation, software items which compose each baseline Hardware System Design Software Reviews Software Reqts Analysis SRR SDR Prelim Design Detail Design Functional Baseline SSR Coding, CSU testing PDR CSC Integration Testing Allocated Baseline CDR CSCI Tes ting TRR Design Baseline Product Baseline Adapted from DoD Standard 2167A 12/28/2018
18
Exercise 3 Configuration Control
Task: The contractor shall, using the IEEE Standard: Identify the membership of the CCB Describe, using a flowchart, the operation of the CCB. 12/28/2018
19
Exercise 3 Configuration Control
Task 1 - Identify the membership of the CCB Project management Development Testing Quality Assurance Customer representatives User documentation developers Technical support Configuration management 12/28/2018
20
Exercise 3 - Task 2 Originator submits a change request Task 2 - Describe, using a flowchart, the operation of the CCB. Submitted Evaluator performs impact analysis don’t make the change Evaluated Rejected Archived CCB CCB decided to make the change Approved change has been made; formal verification requested verification (e.g. regression test) failed Change Made no formal verification is requested; changed product is installed change has been verified Verified modified product is installed Formal verification: e.g. inspection Wiegers K., Software Requirements, Microsoft Press, 2003 12/28/2018 Closed
21
Exercise 4 Configuration Status Accounting
Task: The contractor shall: Establish a Configuration Status Accounting (CSA) system According to the IEEE Standard 12/28/2018
22
Exercise 4 Configuration Status Accounting
Task 1 - Establish a Configuration Status Accounting (CSA) system Establish/Maintain CSA system Definition Data Base to identify the elements that will comprise the CSA (e.g. Configuration Identifier, Description, Change Status, Location(s), Current/Archived Baseline Version(s), etc.). Receive CI and technical data for entry into the CSA system Generate CSA reports Report any deficiencies against this activity 12/28/2018
23
Exercise 4 Configuration Status Accounting
Example Required Data Elements for a Software Trouble Report (STR): Date (date format) Category -Software, Design, Engineering, Logic, Other (1-character field) Priority -1 thru 5 (1-digit numeric field) STR # (numeric field, Auto generation, starting with 1) STR title (alpha-numeric field, 55 characters max) Originator (20-character field) Activity/Code (alpha-numberic character field, 40 characters max) Telephone/Ext. (alpha-numeric field, 20 characters max) Status (table field) 12/28/2018
24
Exercise 4 Configuration Status Accounting
Sample Report Record of Approved Configuration Documentation and ID Numbers Doc identifier Document Title Doc date Status Lib Location MK50 - SRS S R0 C0 Widget MK50 Software Requirements Specification 4/6/95 Approved CCB Safe 12345 SDD RA Widget MK50 Software Design Specification 9/1/95 9/15/95 Sa fe 12345 SDP U Development Plan 12/5/94 1/5/96 File Drwr 3 MK50 - SQAP - U - R0 - C0 Widget MK50 Software 12/13/94 Open Quality Assurance Plan 12/28/2018
25
Exercise 5 Configuration Audits
Task: The contractor shall: For the Functional Configuration Audit (FCA), determine: Audit participants Information required to perform the audit Audit checklist Facilities to perform the audit For the Physical Configuration Audit (PCA) Same as task 1 12/28/2018
26
Exercise 5 Configuration Audits
Functional Configuration Audit (FCA) Formal examination of functional characteristics of a configuration item, prior to acceptance. To verify that the item has achieved the requirements specified in its functional and allocated configuration documentation. Functional Characteristics are quantitative performance parameters and design constraints, including operational and logistic parameters and their respective tolerances. Functional characteristics include all performance parameters, such as range, lethality, reliability, maintainability, and safety. Physical Configuration Audit (PCA) The formal examination of the “as built” configuration of a configuration item against its technical documentation to establish or verify the configuration item’s product baseline. 12/28/2018
27
Exercise 6 Configuration Management Plan
Task: The contractor shall: Develop a Configuration Management Plan According to the IEEE Standard Obtain approval of the CM plan Distribute the plan Put the plan under CM 12/28/2018
28
Exercise 6 Software Configuration Management Plan (SCMP)
Section 1. Introduction Section 2. Reference Documents Section 3. Organization Section 4. Configuration Management Phasing and Milestones Section 5. Data Management Section 6. Configuration Identification Section 7. Interface Management Section 8. Configuration Control Section 9. Configuration Status Accounting Section 10. Configuration Audits Section 11. Subcontractor/Vendor Control SCMP 12/28/2018
29
Summary of Case Study Radar Training System (RTS) Requirements
Proposed system Hardware and software components Exercises CI selection CI identification Configuration Control Configuration audits Configuration status accounting CM Plan 12/28/2018
Similar presentations
© 2025 SlidePlayer.com Inc.
All rights reserved.