09.02.2015 Views

ISO/IEC 21827

ISO/IEC 21827

ISO/IEC 21827

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

<strong>ISO</strong>/<strong>IEC</strong> <strong>21827</strong>:2002(E)<br />

B.3.9.2<br />

Example Work Products<br />

• ongoing database or repository containing identified needs, process improvements, and product improvements;<br />

• clearly described processes, methods, and avenues for getting identified needs into a database or repository;<br />

• identified needs for process improvement;<br />

• identified needs for product improvement;<br />

• trouble reports.<br />

B.3.9.3<br />

Notes<br />

This base practice is critical to the effective use of systems engineering in the production, operations, and maintenance<br />

life-cycle phases.<br />

Needs for corrective action are detected in this base practice. Corrective actions are directed in the Monitor and Control<br />

Technical Effort process area (PA11).<br />

Trouble reports also flow into this base practice from the Verify and Validate System process area (PA11).<br />

B.4 PA13 - Manage Configurations<br />

B.4.1<br />

B.4.1.1<br />

Process Area<br />

Security Considerations<br />

In BP.13.02 the determination of the level of configuration units identified for a system/project should consider the level<br />

of detail required by the assurance objectives in PA06 Build Assurance Argument.<br />

Manage Configurations provides evidence to PA06 Build Assurance Argument. Also, the configuration management<br />

system selected should itself be managed according to PA08 Administer Security Controls.<br />

B.4.1.2<br />

Summary Description<br />

The purpose of Manage Configurations is to maintain data on and status of identified configuration units, and to analyse<br />

and control changes to the system and its configuration units. Managing the system configuration involves providing<br />

accurate and current configuration data and status to developers and customers.<br />

This process area is applicable to all work products that are placed under configuration management. An example set of<br />

work products that may be placed under configuration management could include hardware and software configuration<br />

items, design rationale, requirements, product data files, or trade studies.<br />

B.4.1.3<br />

Goals<br />

• Control over work product configurations is maintained.<br />

B.4.1.4<br />

Base Practice List<br />

The following list contains the base practices that are essential elements of good systems engineering:<br />

BP.13.01<br />

BP.13.02<br />

BP.13.03<br />

BP.13.04<br />

BP.13.05<br />

Decide on appropriate method for configuration management..<br />

Identify the indivisible units for configuration management.<br />

Maintain a repository of work product baselines.<br />

Control changes to established configuration units.<br />

Communicate status of configuration data, proposed changes, and access information to affected<br />

groups.<br />

78 © <strong>ISO</strong>/<strong>IEC</strong> 2002 – All rights reserved

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!