Gestion de la configuration

1
Développement dun simulateur pour former un
technicien radar

• Gestion de la configuration
• Exercice

2
Contenu

• Introduction
• Exigences du simulateur dun radar
• Système proposé
• Quincaillerie et logiciel
• Exercices
• Sélection des éléments de configuration (CI)
• Identification des CI
• Contrôle des configurations
• Statuts de configuration
• Audits de configuration
• Plan de gestion configuration

Source Cours de gestion de configuration,
Ministère de la défense, Canada, 1989
3
Introduction

• 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.

4
Exigences du simulateur dun radar

• 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.

5
Système proposé
CD/DVD
CD/DVD
6
Quincaillerie

• a cabinet,
• two chassis,
• two power supplies and cables,
• two USB and controller card(s),
• two CD/DVD disk readers and controller card(s) ,
• two hard disks and controller card(s),
• two memory boards,
• two chassis to chassis interface boards,
• two monitors and interface board(s) ,
• two keyboards,
• a backup device and two interface board(s) ,
• a data recorder and one interface board,
• two chairs,
• one chassis to chassis interface cable, and
• one audio recorder.

7
Composants logiciels

• Operating System
• Provides all background functions including
  interfaces with monitor, keyboard, floppies and
  hard disk
• Command utility (menu selection for system
  access, selection environment, backup, system
  crash recovery, etc.),
• Radar searching modules (land, sea, air)
• Radar tracking modules (land, sea, air)
• Radar targeting modules (land, sea, air)
• Message handlers,
• Backup software,
• Data recorder software, and
• Data files (example situations)

8
Composants logiciels

• The instructor's station will have the following
  added software
• Map Maker for creation of backgrounds,
• Instructor Interface Module for the sending and
  receiving of information to/from the student's
  station,
• Instructor Interrupt Module which allows the
  instructor to temporarily/permanently end the
  training session.

9
Composants logiciels

• In addition, the following support software is
  installed on the instructor's station
• Compiler,
• Linker,
• Loader,
• Assembler,
• Editor,
• Programming Aids Package,
• Software Library Package,
• Software EPROM Programming Utility,
• Test Data Files,
• Hardware Diagnostics, and
• Software Diagnostics.

10
Exercice 1 Sélection des CI

• Create two Configuration Item (CI) Breakdown
  Charts for the RTS
• From the governments 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.

11
CI du fournisseur
USB
12
CI du client
USB
13
Exercice 2 Identification des CI

• 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

14
Exercice 2 Identification des CI

• 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)
• 3.1.0 Version/Revision/Patch

15
Exercice 2 Identification des CI

• Task 2 - Determine the baselines to be
  established
• Functional Baseline Documentation describing a
  systems or items functional, interoperability
  and interface characteristics and the
  verification used to demonstrate their
  achievement
• Allocated Baseline Documentation describing an
  items 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.

16
Task 2 - State the documentation, software items
which compose each baseline

• 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)

• CI System DesignSystem/Segment Design Document
  (SSDD)Interface Design Document (IDD)Database
  Design Description (DBDD)
• Program/Project PlanningComputer 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)

17
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
Coding, CSU testing
SSR
PDR
CSC Integration Testing
CSCI Testing
CDR
Functional Baseline
TRR
Allocated Baseline
Design Baseline
Product Baseline
Adapted from DoD Standard 2167A
18
Exercice 3 Contrôle des configurations

• Task The contractor shall, using the IEEE
  Standard
• Identify the membership of the CCB
• Describe, using a flowchart, the operation of
  the CCB.

19
Exercice 3 Contrôle des configurations

• Task 1 - Identify the membership of the CCB
• Project management
• Development
• Testing
• Quality Assurance
• Customer representatives
• User documentation developers
• Technical support
• Configuration management

20
Exercice 3 - Tâche 2
Originator submits a change request

• Task 2 - Describe, using a flowchart, the
  operation of the CCB.

Submitted
Evaluator performs impact analysis
dont make the change
Rejected
Archived
Evaluated
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
Closed
21
Exercice 4 - Statuts de configuration

• Task The contractor shall
• Establish a Configuration Status Accounting (CSA)
  system
• According to the IEEE Standard

22
Exercice 4 - Statuts de configuration

• 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

23
Exercice 4 - Statuts de configuration

• Example
• Data Elements for a Software Trouble Report
  (STR)
• Date (date format, e.g. DD,MM,YYYY)
• Category -Software, Design, Engineering, Logic,
  Other (1-character field)
• Priority -1 to 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-numeric character field, 40
  characters max)
• Telephone/Ext. (alpha-numeric field, 20
  characters max)
• Status (table field)

24
Exercice 4 - Statuts de configuration
Sample Report Record of Approved Configuration
Documentation and ID Numbers
File Drwr 3

MK50
-
SQAP
-
U
-
R0
-
C0

Widget MK50 Software
12/13/94

Open

Quality Assurance Plan




25
 Exercice 5  - Audits

• Task The contractor shall
• For the Functional Configuration Audit (FCA),
  determine
• Audit participants
• Information required to perform the audit
• Audit check-list
• Facilities to perform the audit
• For the Physical Configuration Audit (PCA)
• Same as task 1

26
 Exercice 5 - 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 items product baseline.

27
Exercice 6  - 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

28
Exercice 6  - 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
29
Sommaire

• Introduction
• Exigences du système de formation dun radar
• Système proposé
• Quincaillerie et logiciel
• Exercices
• Sélection des CI
• Identification des CI
• Contrôle des configurations
• Statuts de configuration
• Audits de configuration
• Plan de gestion configuration