Software Project Management Brochure Template Page 22

ADVERTISEMENT

22
Handbook on Software Engineering & Knowledge Engineering
Control
Status
Release
Auditing
Management
Accounting
Processing
Management
and Planning
Development
team
Configuration identification
Figure 6 – Software configuration management activities (after [26])
Configuration identification activities provide the basis for other SCM
activities. These activities enumerate the configuration items to be controlled
(such as plans, specifications, source and executable code, code libraries, data
and data dictionaries, testing materials, software tools, and documentation for
installation, maintenance, operations and software use), establish identification
schemes for the items and their versions, and establish the tools and techniques
to be used in acquiring and managing controlled items.
SCM control activities involve both managers and developers. Managers
make decisions on whether some changes in configuration should be made or
not, and authorize the changes. Developers perform change activities (code
management) in a coordinated manner. Status reports are generated that account
for each change in the configuration, and can be of use to various parties in the
project, including managers, developers, testers, SQA team members, and
maintenance engineers. The information obtained by status accounting can also
serve as a basis for various measurements, such as the number of change
requests per software configuration item and the average time needed to
implement a change request. Release processing activities support customers and
the maintenance team. They are related to identification, packaging and delivery
of the elements of a product (such as the software, its documentation, release
notes, and configuration data), as well as product version management (versions
for different platforms or versions with varying capabilities). The software
configuration auditing activity determines the extent to which an item satisfies
the required functional and physical characteristics. Its ultimate goal is to
evaluate the conformance of software products and processes to applicable
regulations, standards, guidelines, plans, and procedures [26].
Standards
There are two major aspects of the term ``standards" in software development.
One of them is that of using widely accepted standards under the assumption that
they embody ``the common body of knowledge and accepted state of industry

ADVERTISEMENT

00 votes

Related Articles

Related forms

Related Categories

Parent category: Business