LE FastCounter
The major milestones for the implementation of configuration management are the establishment of CCBs, each of the configuration identifications (baselines), interface control agreements with associate (partner) companies, configuration index and status accounting procedures.
The acquirer may have his own internal configuration procedures and/or terms of reference. Identify them here and reference them in Section 2.
The acquirers agent (if applicable) will consider all proposed changes from the suppliers and will submit them to the acquirer for a decision. They will co-ordinate resolution of any disagreement and will refer if disagreement persists to the next higher level of approval.
The Interface coordination meeting is comprised of
Configuration Control personnel, and is convened to discuss problem
areas where two parties of an interface need to keep full interface
records of submitted changes.
Interface Control procedures in the system program will consist
of establishing and maintaining technical agreements among the
different organizations responsible for interfacing systems and
system elements. These shall be documented in the System Interface
Control Documentation (ICD).
An interface change dictates that the source and destination are
affected. An interface will be 'defined' when the functional and
physical characteristics are appropriately specified (or referenced)
in the System/subsystem specification(s).
Interface Control will be accomplished by the Interface Control
Working Group (ICWG) and serves as the official communications
link between the project participants to resolve interface problems,
document interface agreements, and co-ordinate CPs.
Configuration control of the interface will be performed using
the control process identified in this CMP when the ICWG approves
a change which amends the ICD and recommends changes to the IRS.
On occasions it may be necessary to hold meetings outside of the
meeting schedule (ad hoc) due to the urgency of the change. If
this does become necessary, all affected developers/suppliers
shall be informed of the information exchange by the official
report of the meeting.
Note: ICD will be prepared in accordance with ICD model text.
All configuration items and their specifications
and design documents will be identified and all changes tracked
from their initial issue.
These shall include:
The structure of these meetings shall be determined by the lead company. Project CCBs will discuss the proposed changes (recommended from System Design) as they arise in a formal meeting and approved changes circulated to other affected companies and technical authorities.
Discussions between interested parties will be encouraged, and ad-hoc meetings may be necessary to discuss the impact of interface changes.
Local configuration control boards will control the
documentation prepared during development which will be needed
for evidence of compliance with the contractually identified standards.
For software (CSCIs) during development the software unit coding
and its integration into a CSCI shall be controlled by methods
identified in the SDP or SDP (overall) usually defined in a separate
SCMP.
After initial release of a specification containing
any of the Functional, Allocated or Product (CSCI or HWCI) baselines
or program plans, changes will be controlled using the processes
identified in this Configuration Management plan.
Subsequent changes to each specification will be formally approved
using the change reports (CR/CP) defined in this CMP and will
be documented in accordance with these reports and made a part
of the specification.
TBC
Under construction.
Back to Home page
Back to CMP page
Back to Top of this page
For Home page MANAGING STANDARDS
kenr@wysywig.airtime.co.uk
Originated on the 17th of July 1995
Please send any beneficial comments or identification of errors
using the following form to: kenr@wysywig.airtime.co.uk