Scribd
Upload
9 views20 pages

Week 16 - SCM and Release Management

The document outlines the Software Configuration Management (SCM) process, which includes tasks such as identification, version control, change control, configuration auditing, and reporting. It also details the Release Management process, which consists of planning, building, user acceptance testing, preparing, and deploying software releases. The aim is to ensure efficient management of software configurations and successful delivery of software products to consumers.

Uploaded by

izhanizi20
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
9 views20 pages

Week 16 - SCM and Release Management

The document outlines the Software Configuration Management (SCM) process, which includes tasks such as identification, version control, change control, configuration auditing, and reporting. It also details the Release Management process, which consists of planning, building, user acceptance testing, preparing, and deploying software releases. The aim is to ensure efficient management of software configurations and successful delivery of software products to consumers.

Uploaded by

izhanizi20
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 20

Software Configuration Management Process

and Release Management


SCM Process
The software configuration management process defines a series
of tasks that have four primary objectives:
The following questions lead to the definition of five SCM tasks—
identification, version control, change control, configuration auditing,
and reporting, as shown in previous fig.
• How does a software team identify the discrete elements of a
software configuration?
• How does an organization manage the many existing versions of a
program (and its documentation) in a manner that will enable change
to be accommodated efficiently?
• How does an organization control changes before and after software
is released to a customer?
• How does an organization assess the impact of change and manage
the impact effectively?
• Who has responsibility for approving and ranking requested changes?
• How can we ensure that changes have been made properly?
• What mechanism is used to apprise others of changes that are made?
Identification of Objects
Types of objects:
Basic objects:
-Unit of information that is created during analysis,
design, code or test.
-For ex: Part of design model, source code for a
component, suite of test cases etc.

Aggregate objects:
-Collection of basic objects.
-For ex: Design specification.
Version Control
Change Control
Fig: The change control
process.
Configuration Audit
Status Reporting
SCM Standards
Release Management.
What is a Software Release?
A release is the distribution of software to the
consumer. From floppy disks to CDs, one-off
downloads to continuous delivery, software
distribution speed has accelerated
exponentially.
Release Management Process
1. Plan release
• The planning stage may be the most time
intensive as this is where your entire release is
structured from start to finish. A robust release
plan will help your team stay on track and ensure
standards and requirements are properly met.
• There are several ways to approach a release
plan. One of the most popular release
management methods is the systems
development life cycle (SDLC).
Plan release
• There are multiple ways to map out your plan
and clarify the process. One option is a release
management checklist. The checklist should
outline the process functions and
responsibilities in roughly chronological order.
• When your team looks at the checklist, they
should be able to quickly establish what step
they are on and what their role or
responsibility is.
Plan release
• Another option is to create a release workflow.
Create an intuitive flowchart of your release
process using color coding, shapes etc. to
designate timelines, roles, and tasks.
• Once your plan is sketched out, present it to all
relevant stakeholders (your team, product
manager, and high-level leaders) for review. Get
their feedback on any gaps or problems they see
in the requirements or scope.
• Once the plan is approved and finalized, you can
put it into action.
2. Build release
• With the release plan finalized, you can start
designing and building the product for release.
This is the actual “development” of the
product based on the requirements outlined
in the release plan.
• Once all the issues that may have come up are
addressed, it’s time to subject the build to
real-world scenario testing.
3. User acceptance testing
• User acceptance testing, also known as UAT, is
when the end users the product was built for get
to actually use it and give feedback. This is often
done as a free beta trial online or shared with a
larger group of employees within the company.
• User acceptance testing is the most crucial step
to release management because of the amount
of data collected and fixes required in order to
get the build to where it needs to be for the
official launch.
4. Prepare release
• This step is to put the finishing touches on the
product, taking into account everything that
was learned in UAT. Release preparation also
includes a final quality review by the QA team.
• During the review, the QA team will conduct
final checks to ensure the build meets the
minimum acceptable standards and business
requirements outlined in the release plan.
5. Deploy release
• The big day has finally arrived and here is
where all your team’s hard work pays off. It’s
time to release your product into the wilds of
the live production environment.
• Besides simply sending the build out into
production, the deployment stage also
includes messaging and education on the
product to both the end user and your
company at large.

You might also like