Configuration Status Accounting-Introduction

7/24/2019 Configuration Status Accounting-Introduction

1/26

CONFIGURATION STATUS

ACCOUNTING

Mohd Sayuti Bin Md SaufMohamad Ridzuan Bin Abdullah

Nik Mulaikah Naimah Binti Nik Adnan

Noorsuziyante Binti Mat NapiShahidah Binti Avelino


2/26

PURPOSE

Configuration status accounting (CSA) is the process of creating

and organizing the knowledge base necessary for the

performance of configuration management

In addition to acilitating M! the purpose o SA is

to provide a highly reliable source o confgurationinormation to support all program or pro"ectactivities including program management

systems engineering

manufacturing

software development and maintenance

logistic support

modification

maintenance.


3/26

Activity Configuration Status Accounting


4/26

Configuration Status Report Include

A list of the configuration items that comprise a baseline

The date when each version of each configuration item was

baselined

A list of the specifications that describe each configurationitem

The history of baseline changes including rationales for

change

A list of open change reuests by configuration item !eficiencies identified by configuration audits

The status of works associated with approved change

reuests by C".


5/26

Four Principle

hange Re#uests A Change #euest (C#) is a general term for a reuest to

change an artifact or process. The general process associated

with C#s is described in Concepts$ Change #euest

%anagement. Categories Aging (Time &ased #eports)'ow long have Change #euests of the

various kinds been open *hat is the +lag time,, of when in the lifecycle

defects are found- versus when are they being fied

!istribution (Count &ased #eports)'ow many Change #euests are

there in the various categories by owner- priority or state of fi

Trend (Time and Count #elated #eports)'*hat is the cumulative number

of defects being found and fied over time *hat is the rate of defect

discovery and fi


6/26

Build Reports &uild #eports list all the files- their location- and

incorporated changes that make up a build for a specific

version of the software. &uild #eports can be maintained both at the system and

subsystem level$

%ersion &escriptions Similar to #elease /otes- 0ersion !escriptions describe

the details of a software release.

Audits There two kinds of audits that are covered in the

contet of Configuration %anagement

1$2hysical Configuration Audits

3$4unctional Configuration Audits.


7/26

TYPICAL CSA INFORMATION OVER THE

ACQUISITION PROGRAM LIFE CYCLE

Ne' and innovative methods o capturing theconfguration o installed and spare items and

sot'are versions are becoming commonplace$ (hese methods include bar coding and the

interrogation o embedded identifcation via on)e#uipment data buses and on)board support

e#uipment$ (he technology or this process is no'

commonplace in the commercial personalcomputer industry and the automotive industry$


8/26

(he inormation that is loaded into SA is

considered *metadata!* that is! inormation aboutthe data$ It provides status and cross)reerencesactual (echnical &ata +ackage ,(&+- inormationthat is stored digitally in data repositories$

.ach design activity establishes a documentrepository or the Is developed! produced! ormaintained by an /0ce o +ro"ect Responsibility

,/+R- under their authority$ (he data repositoriesare normally maintained by the inventory controlpoint responsible or the provisioning1supplysupport o the I$


9/26

SA records should be maintained in such range anddepth as to be responsive to the re#uirements o the

various support activities or access to confgurationinormation$

(he data repository is the central point or thecollection! storage! processing! and promulgation o thisdata$

onfguration inormation should be available on are#uest basis! either by hard copy or online computeraccess$

(he SA records are used as *best source* input dataor purchasing data packages! design studies! andmanagement analyses re#uested by thesupporting1design activities$ In particular! the SAmetadata records must accurately re2ect the status othe confguration documents ,specifcations! dra'ings!lists! test reports! etc$- maintained in the documentrepositories$


10/26

Concept n! Tec"nolo#$ %e&elop'ent

(ypical inormation sources include3 Mission need statements

Baseline perormance! cost! and schedule

goals System re#uirements documents or

alternative confgurations

+reliminary system perormance

Specifcations or selected confguration .ngineering change proposals or contract

change proposals! as applicable


11/26

(ypical outputs include3 urrent revision o each document

urrent &ocument hange Authority ,&A-

and approval status or each document


12/26

S$(te' %e&elop'ent n!%e'on(trtion

System perormance specifcation

I perormance specifcations

I detailed specifcations

.ngineering dra'ings and associated lists

A& fles

(est plans and procedures! and results

Audit plan

(ypical inormation sources include3


13/26

Audit report

Audit certifcation

.ngineering change proposals

Notice o Revision ,N/RS-

.ngineering orders! change notices!

Installation and as)built verifcation

Removal and reinstallation


14/26

(ypical outputinclude3

&A release and approval status o each document

4unctional! allocated! and product baselines

As)designed confguration! current and as o any priordate

As)built confguration! current up to time o delivery!and any prior date

As)delivered confguration


15/26

ont5Status o .+s and R4&s in process

.6ectivity ad incorporation status o approved

.+s and R4&s! including retroft e6ectivity

(est and certifcation re#uirements to be completed prior to

milestones! such as revie's! demonstrations! tests! trials anddelivery

%erifcation and audit status and action items


16/26

Pro!uction n!%eplo$'ent

(ypical inormation sourcesinclude3 All development phase items System I location by serial number Support e#uipment and sot'are Spares

(rainers (raining material/peratig and

maintenance manuals


17/26

ont$$

I delivery dates and 'arranty data Shel lie or operating limits on

components 'ith limited lie or limitedactivation

/perational history ,e$g3 or aircrat)takeo6s and landing

%erifcation1validation o retroft

instruction! retroft kits Incorporation o retroft kits Installation o spares! replacements by

maintenance action


18/26

(ypical output include3

All development phase items urrent confguration o all systems1Is in

all locations ,as)modifed1 as)maintained-

Re#uired and on)board confguration o allsupport e#uipment! spares! traines!training! manuals! sot'are! acilitiesneeded to operate and maintain all

systems1is at all sites Status o all re#uested! in)process! and

approved changes and deviation re#uests


19/26

ont$$

Authorization and ordering actionsre#uired to implement approved changes!including recurring retroft

7arranty status o all is

+redicted replacement date or criticalcomponent

Retroft actions necessary to bring anyserial)numbered I to the current or any

prior confguration


20/26

Opertionl Support

(ypical inormation sources include3 All production and deployment phase items

(ypical outputs include3 All production and deployment phase items


21/26

CONFIGURATION STATUS ACCOUNTINGPROCESS EVALUATION CHEC)LIST

&ocumented process

SA inormation

SA system

Metrics

(ypical inormation sources include3


22/26

%ocu'ente! proce((

Is there a documented confgurationstatus accounting ,SA- process8

Is the documented process ollo'ed8

Are personnel rom all disciplinesinvolved in the process inormed andkno'ledgeable about the proceduresthey are supposed to ollo'8


23/26

CSA in*or'tion

9as an accurate! timely inormation baseconcerning the product and its associatedproduct inormation! appropriate to the

applicable phase,s- o the cycle! beenestablish8

Is confguration inormation appropriateto the product systematically recorded

and disseminated8 Is applicable SA inormation captured as

M tasks are perormed and is it

available or display or retrieval in atimel ashion8


24/26

CSA ($(te'

Is the data collection and inormationprocessing system based on and

consistent 'ith the confguration statusaccounting inormation needs o theorganization8

Are the data relationships in the systembased on a sound set o business rules8


25/26

Metric(

&oes the status accounting data beingcollected and the inormation system

enable meaningul metrics to bedeveloped and used to maintain andimprove the M process


26/26

Configuration Status Accounting-Introduction

Documents

Transcript of Configuration Status Accounting-Introduction