Scribd Logo
Upload

Welcome to Scribd!

  • 331 views

    Configuration Status Accounting-Introduction

    Uploaded by

    Shai
    Status accounting is the function that documents and reports the information related to Cis to everyone involved in the project. The status accounting function should also be able to answer ad hoc queries. In a large project, creating and distributing reports, even the routine reports, as hard copy is expensive – not to mention that it is an administrative nightmare. So in this kind of a project it is better to publish and post these reports on the corporate intranet and inform staff about the fact that the reports are available via e-mail or nay other messaging system that the project is using. For ad hoc querying, it is better to assign role – such as developer, tester, and manager - and give selective access to the people who fit these roles. For example, a developer could be given access to query the table that contains information about the Cis of his module, whereas a manager could be given the access query any table in the database. This kind of electronic distribution of the status accounting information is necessary for a large project, because the other option having hardcopies is a big burden on the SCM budget.

    Copyright:

    © All Rights Reserved
    Download as PPTX, PDF, TXT or read online from Scribd

    Configuration Status Accounting-Introduction

    Uploaded by

    Shai
    331 views26 pages
    Status accounting is the function that documents and reports the information related to Cis to everyone involved in the project. The status accounting function should also be able to answer ad hoc queries. In a large project, creating and distributing reports, even the routine reports, as hard copy is expensive – not to mention that it is an administrative nightmare. So in this kind of a project it is better to publish and post these reports on the corporate intranet and inform staff about the fact that the reports are available via e-mail or nay other messaging system that the project is using. For ad hoc querying, it is better to assign role – such as developer, tester, and manager - and give selective access to the people who fit these roles. For example, a developer could be given access to query the table that contains information about the Cis of his module, whereas a manager could be given the access query any table in the database. This kind of electronic distribution of the status accounting information is necessary for a large project, because the other option having hardcopies is a big burden on the SCM budget.

    Copyright

    © © All Rights Reserved

    Available Formats

    PPTX, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    Status accounting is the function that documents and reports the information related to Cis to everyone involved in the project. The status accounting function should also be able to answer ad hoc queries. In a large project, creating and distributing reports, even the routine reports, as hard copy is expensive – not to mention that it is an administrative nightmare. So in this kind of a project it is better to publish and post these reports on the corporate intranet and inform staff about the fact that the reports are available via e-mail or nay other messaging system that the project is using. For ad hoc querying, it is better to assign role – such as developer, tester, and manager - and give selective access to the people who fit these roles. For example, a developer could be given access to query the table that contains information about the Cis of his module, whereas a manager could be given the access query any table in the database. This kind of electronic distribution of the status accounting information is necessary for a large project, because the other option having hardcopies is a big burden on the SCM budget.

    Copyright:

    © All Rights Reserved
    Download as PPTX, PDF, TXT or read online from Scribd
    Download as pptx, pdf, or txt
    331 views26 pages

    Configuration Status Accounting-Introduction

    Uploaded by

    Shai
    Status accounting is the function that documents and reports the information related to Cis to everyone involved in the project. The status accounting function should also be able to answer ad hoc queries. In a large project, creating and distributing reports, even the routine reports, as hard copy is expensive – not to mention that it is an administrative nightmare. So in this kind of a project it is better to publish and post these reports on the corporate intranet and inform staff about the fact that the reports are available via e-mail or nay other messaging system that the project is using. For ad hoc querying, it is better to assign role – such as developer, tester, and manager - and give selective access to the people who fit these roles. For example, a developer could be given access to query the table that contains information about the Cis of his module, whereas a manager could be given the access query any table in the database. This kind of electronic distribution of the status accounting information is necessary for a large project, because the other option having hardcopies is a big burden on the SCM budget.

    Copyright:

    © All Rights Reserved
    Download as PPTX, PDF, TXT or read online from Scribd
    Download as pptx, pdf, or txt
    You are on page 1of 26

    CONFIGURATION STATUS

    ACCOUNTING
    Mohd Sayuti Bin Md Sauf
    Mohamad Ridzuan Bin Abdullah
    Nik Mulaikah Naimah Binti Nik Adnan
    Noorsuziyante Binti Mat Napi
    Shahidah Binti Avelino

    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 facilitating CM, the purpose of CSA is
    to provide a highly reliable source of confguration
    information to support all program or project
    activities including

    program management
    systems engineering
    manufacturing
    software development and maintenance
    logistic support
    modification
    maintenance.

    Activity Configuration Status Accounting

    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 configuration
    item
    The history of baseline changes including rationales for
    change
    A list of open change requests by configuration item
    Deficiencies identified by configuration audits
    The status of works associated with approved change
    requests by CI.

    Four Principle

    Change Requests

    A Change Request (CR) is a general term for a request to


    change an artifact or process. The general process associated
    with CRs is described in Concepts: Change Request
    Management.
    Categories

    Aging (Time Based Reports)-How long have Change Requests of the


    various kinds been open? What is the lag time of when in the lifecycle
    defects are found, versus when are they being fixed?
    Distribution (Count Based Reports)-How many Change Requests are
    there in the various categories by owner, priority or state of fix?
    Trend (Time and Count Related Reports)-What is the cumulative number
    of defects being found and fixed over time? What is the rate of defect
    discovery and fix?

    Build Reports
    Build Reports list all the files, their location, and
    incorporated changes that make up a build for a specific
    version of the software.
    Build Reports can be maintained both at the system and
    subsystem level.

    Version Descriptions
    Similar to Release Notes, Version Descriptions describe
    the details of a software release.

    Audits
    There two kinds of audits that are covered in the
    context of Configuration Management
    1:Physical Configuration Audits
    2:Functional Configuration Audits.

    TYPICAL CSA INFORMATION OVER THE


    ACQUISITION PROGRAM LIFE CYCLE

    New and innovative methods of capturing the


    confguration of installed and spare items and
    software versions are becoming commonplace.
    These methods include bar coding and the
    interrogation of embedded identifcation via onequipment data buses and on-board support
    equipment.
    The technology for this process is now
    commonplace in the commercial personal
    computer industry and the automotive industry.

    The information that is loaded into CSA is


    considered "metadata," that is, information about
    the data. It provides status and cross-references
    actual Technical Data Package (TDP) information
    that is stored digitally in data repositories.

    Each design activity establishes a document


    repository for the CIs developed, produced, or
    maintained by an Office of Project Responsibility
    (OPR) under their authority. The data repositories
    are normally maintained by the inventory control
    point responsible for the provisioning/supply
    support of the CI.

    CSA records should be maintained in such range and


    depth as to be responsive to the requirements of the
    various support activities for access to confguration
    information.
    The data repository is the central point for the
    collection, storage, processing, and promulgation of this
    data.
    Confguration information should be available on a
    request basis, either by hard copy or online computer
    access.
    The CSA records are used as "best source" input data
    for purchasing data packages, design studies, and
    management analyses requested by the
    supporting/design activities. In particular, the CSA
    metadata records must accurately reflect the status of
    the confguration documents (specifcations, drawings,
    lists, test reports, etc.) maintained in the document
    repositories.


    Concept and Technology Development

    Typical information sources include:


    Mission need statements
    Baseline performance, cost, and schedule
    goals
    System requirements documents for
    alternative confgurations
    Preliminary system performance
    Specifcations for selected confguration
    Engineering change proposals or contract
    change proposals, as applicable

    Typical outputs include:


    Current revision of each document
    Current Document Change Authority (CDCA)
    and approval status for each document

    System Development and


    Demonstration
    Typical information sources include:

    System performance specifcation


    CI performance specifcations
    CI detailed specifcations
    Engineering drawings and associated lists
    CAD fles
    Test plans and procedures, and results
    Audit plan

    Audit report
    Audit certifcation
    Engineering change proposals
    Notice of Revision (NORS)
    Engineering orders, change notices,
    Installation and as-built verifcation
    Removal and reinstallation

    Typical output
    include:
    CDCA release and approval status of each document
    Functional, allocated, and product baselines
    As-designed confguration, current and as of any prior
    date
    As-built confguration, current up to time of delivery,
    and any prior date
    As-delivered confguration

    Cont
    Status of ECPs and RFDs in process

    Effectivity ad incorporation status of approved

    ECPs and RFDs, including retroft effectivity


    Test and certifcation requirements to be completed prior to
    milestones, such as reviews, demonstrations, tests, trials and
    delivery
    Verifcation and audit status and action items

    Production and
    Deployment
    Typical
    Typicalinformation
    informationsources
    sources
    include:
    include:

    All development phase items


    System CI location by serial number
    Support equipment and software
    Spares
    Trainers
    Training materialOperatig and
    maintenance manuals

    Cont..
    Cont..
    CI delivery dates and warranty data
    Shelf life or operating limits on
    components with limited life or limited
    activation
    Operational history (e.g: for aircrafttakeoffs and landing
    Verifcation/validation of retroft
    instruction, retroft kits
    Incorporation of retroft kits
    Installation of spares, replacements by
    maintenance action

    Typical
    Typicaloutput
    outputinclude:
    include:
    All development phase items
    All development phase items
    Current confguration of all systems/CIs in
    Current confguration of all systems/CIs in
    all
    locations
    (as-modifed/
    as-maintained)
    all locations (as-modifed/ as-maintained)
    Required and on-board confguration of all
    Required and on-board confguration of all
    support
    supportequipment,
    equipment,spares,
    spares,traines,
    traines,
    training,
    training,manuals,
    manuals,software,
    software,facilities
    facilities
    needed
    neededto
    tooperate
    operateand
    andmaintain
    maintainall
    all
    systems/Cis
    systems/Cisat
    atall
    allsites
    sites
    Status of all requested, in-process, and
    Status of all requested, in-process, and
    approved
    changes
    and
    deviation
    requests
    approved changes and deviation requests

    Cont..
    Authorization and ordering actions
    required to implement approved changes,
    including recurring retroft
    Warranty status of all Cis
    Predicted replacement date for critical
    component
    Retroft actions necessary to bring any
    serial-numbered CI to the current or any
    prior confguration

    Operational Support
    Typical information sources include:

    All production and deployment phase items

    Typical outputs include:

    All production and deployment phase items

    CONFIGURATION STATUS ACCOUNTING


    PROCESS EVALUATION CHECKLIST
    Typical information sources include:

    Documented process
    CSA information
    CSA system
    Metrics

    Documented process

    Is there a documented confguration


    status accounting (CSA) process?
    Is the documented process followed?
    Are personnel from all disciplines
    involved in the process informed and
    knowledgeable about the procedures
    they are supposed to follow?

    CSA information

    Has an accurate, timely information base


    concerning the product and its associated
    product information, appropriate to the
    applicable phase(s) of the cycle, been
    establish?
    Is confguration information appropriate
    to the product systematically recorded
    and disseminated?
    Is applicable CSA information captured as
    CM tasks are performed and is it
    available for display or retrieval in a
    timely fashion?

    CSA system

    Is the data collection and information


    processing system based on and
    consistent with the confguration status
    accounting information needs of the
    organization?
    Are the data relationships in the system
    based on a sound set of business rules?

    Metrics

    Does the status accounting data being


    collected and the information system
    enable meaningful metrics to be
    developed and used to maintain and
    improve the CM process

    You might also like