Scribd
Upload
78 views14 pages

IT 440 Software Implementation-6

The document discusses software implementation and configuration management. It explains that software implementation provides assurance that software builds function as expected and enables verification and validation activities. It also discusses configuration management practices that are applied throughout the software lifecycle to control, manage and maintain software work products. Specific tools like IBM Rational ClearCase and ClearQuest are also summarized that help enable configuration management and change control.

Uploaded by

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

IT 440 Software Implementation-6

The document discusses software implementation and configuration management. It explains that software implementation provides assurance that software builds function as expected and enables verification and validation activities. It also discusses configuration management practices that are applied throughout the software lifecycle to control, manage and maintain software work products. Specific tools like IBM Rational ClearCase and ClearQuest are also summarized that help enable configuration management and change control.

Uploaded by

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

Software

Implementation
IT 440: SYSTEM INTEGRATION
Upon completion of this
week’s activities, you will be
able to:
Explain how the software implementation method provides assurance that
software engineering builds function as expected in target software and systems
environments.
Identify how disciplined software implementation principles, planning, and
resources for systems buildup provide effective testing to be conducted in a
development facility for a software/system integration environment.
Discuss how the software released under configuration management control is
described in a defined documented configuration management plan.
SOFTWARE
IMPLEMENTATION METHOD
Purpose: provides assurance that software engineering builds
function as expected and enables smooth execution for verification
and validation activities.
• The necessary requirements for software implementation is
released under configuration management control as
described in a defined documented configuration management
plan (CMP).
CONFIGURATION
MANAGEMENT
Purpose: ensures configuration management practices are applied consistently
throughout the software life cycle for programs/products.
Team Focus: identifies and manages changes and maintains software
configuration and documentation visibility.
Processes: controls storage, access, changes, archive, and release of the software
work products.
Procedures: describes implementation of processes required to meet
requirements and direction provided under plan association and documentation.
BUILD REQUESTS
Purpose: provides checklists to assemble, compile, link source code,
build archive copies, and provide listings for use in software
design/development, test, and work product customer delivery.
Processes: include the capability to package builds and
documentation together.
• Requires coordinated communication between internal
and external teams to be efficient and available for
scheduled tests or configuration checkouts.
BUILD ENGINEER ROLE
Creates build folders to store documentation of
software building
Provides source code changes and control of the
source code
Maintains and controls records during program and
project development
CONFIGURATION
MANAGEMENT TOOLS

Purpose: provides the capabilities for adding new files to a software


design/development environment in addition to providing version
control to directories and files.

Essential Elements: File sharing, parallel software


design/development, multiple team support, and software reuse to
ensure integration test activities demanded by the schedule.
IBM RATIONAL CLEARCASE
Definition: An object-oriented database utility provided to
establish software product archiving, automation,
identification, version/change control, engineering building,
product releases, status accounting, and auditing activities.
Purpose: provides an open architecture to implement
configuration management and control solutions.
CLEARCASE ROLES
• Architect
• Configuration manager
• Lead
• Software design engineer
• Build engineer
IBM RATIONAL
CLEARQUEST
Purpose: provides support for change request management
processes and is a ClearCase complementary tool.
Use: recording, tracking, and reporting and provides
internal access control mechanisms for permitting the
restriction of work product updates throughout the various
stages of software design/development, integration and
test, and production processes.
SOFTWARE MEDIA AND
DATA
Physical software media identification and labeling must be in accordance with
program and project documented media requirements.
Media Label Documentation Items:
• Date: Day/month/year format
• Title: Document the title of the software being produced
• Derived from: Program and project
• Special handling: Distribution requirements
• Contract number: Document contract number
• Part number: Document software identifier
• Software version: Media version
FUTURE TRENDS
Improvements in software technology will address and
resolve issues and improvements required for:
• Software design/development
• Software process definition and enhancements
• Reuse of software program and project artifacts
• Ongoing support of past tool artifacts
• Training for software design engineers
• Software tool disciplines
TOOL SUPPORT
Key: selecting the right vendor products to match
engineering needs.
Questions: necessary for meeting organizational
needs.
PRIMARY STEPS
1. Become effective for designing and developing work
products
2. Establish the resources for use of software tools
3. Conduct software implementation with no problems
4. Conduct training

You might also like