Scribd
Upload
483 views7 pages

SPM Unit 4

Uploaded by

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

SPM Unit 4

Uploaded by

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

UNIT – IV

Process Automation: Automation Building blocks, The Project Environment.


Project Organizations and Responsibilities: Line-of-Business Organizations, Project
Organizations, evolution of Organizations
.

The Process Automation:


Introductory Remarks:
The environment must be the first-class artifact of the process.
Process automation& change management is critical to an iterative process. If the change is
expensive then the development organization will resist it.
Round-trip engineering& integrated environments promote change freedom & effective
evolution of technical artifacts.
Metric automation is crucial to effective project control.
External stakeholders need access to environment resources to improve interaction with the
development team & add value to the process.
The three levels of process which requires a certain degree of process automation for the
corresponding process to be carried out efficiently.
Metaprocess (Line of business): The automation support for this level is called an
infrastructure.
Macroproces (project):The automation support for a project’s process is called an
environment.
Microprocess (iteration):The automation support for generating artifacts is generally called
a tool.

Tools: Automation Building blocks:


Many tools are available to automate the software development process. Most of the
core software development tools map closely to one of the process workflows
Workflows Environment Tools & process Automation
Management Workflow automation, Metrics automation
Environment Change Management, Document Automation
Requirements Requirement Management
Design Visual Modeling
Implementation -Editors, Compilers, Debugger, Linker, Runtime
Assessment -Test automation, defect Tracking
Deployment defect Tracking
The Project Environment:
The project environment artifacts evolve through three discrete states.
(1)Prototyping Environment.(2)Development Environment.(3)Maintenance Environment.
The Prototype Environment includes an architecture test bed for prototyping project
architecture to evaluate trade-offs during inception & elaboration phase of the life cycle.
The Development environment should include a full suite of development tools needed to
support various
Process workflows & round-trip engineering to the maximum extent possible.
The Maintenance Environment should typically coincide with the mature version of the
development.
There are four important environment disciplines that are critical to management context &
the success of a modern iterative development process.
Round-Trip engineering
Change Management
Software Change Orders (SCO)
Configuration baseline Configuration Control Board
Infrastructure
Organization Policy
Organization Environment
Stakeholder Environment.

Round Trip Environment


Tools must be integrated to maintain consistency & traceability.
Round-Trip engineering is the term used to describe this key requirement for environment
that support iterative development.
As the software industry moves into maintaining different information sets for the
engineering artifacts, more automation support is needed to ensure efficient & error free
transition of data from one artifacts to another.
Round-trip engineering is the environment support necessary to maintainConsistency among
the engineering artifacts.

Change Management
Change management must be automated & enforced to manage multiple iterations & to
enable change freedom.
Change is the fundamental primitive of iterative Development.
I. Software Change Orders
The atomic unit of software work that is authorized to create,modify or obsolesce
components within a configuration baseline is called a software change orders ( SCO )
The basic fields of the SCO are Title, description, metrics, resolution, assessment &
disposition
Change management
II.Configuration Baseline
A configuration baseline is a named collection of software components &Supporting
documentation that is subjected to change management & is upgraded, maintained,
tested, statuses & obsolesced a unit
There are generally two classes of baselines
External Product Release
Internal testing Release
Three levels of baseline releases are required for most Systems
1. Major release (N)
2. Minor Release (M)
3. Interim (temporary) Release (X)
Major release represents a new generation of the product or project
A minor release represents the same basic product but with enhanced features,
performance or quality.
Major & Minor releases are intended to be external product releases that are
persistent & supported for a period of time.
An interim release corresponds to a developmental configuration that is intended to
be transient.
Once software is placed in a controlled baseline all changes are tracked such that a
distinction must be made for the cause of the change. Change categories are
Type 0: Critical Failures (must be fixed before release)
Type 1: A bug or defect either does not impair (Harm) the usefulness of the system or
can be worked around
Type 2: A change that is an enhancement rather than a response to a defect
Type 3: A change that is necessitated by the update to the environment
Type 4: Changes that are not accommodated by the othercategories.
Change Management
III Configuration Control Board (CCB)
A CCB is a team of people that functions as the decision
Authority on the content of configuration baselines
A CCB includes:
1. Software managers
2. Software Architecture managers
3. Software Development managers
4. Software Assessment managers
5. Other Stakeholderswho are integral to the maintenance of the controlled
software delivery system?
Infrastructure
The organization infrastructure provides the organization’s capitalassets including two
key artifacts - Policy & Environment
I Organization Policy:
A Policy captures the standards for project software developmentprocesses
The organization policy is usually packaged as a handbook that defines the life cycles
& the process primitives such as
 Major milestones
 Intermediate Artifacts
 Engineering repositories
 Metrics
 Roles & Responsibilities
Infrastructure
II Organization Environment
The Environment that captures an inventory of tools which are building blocks from
which project environments can be configuredefficiently & economically

Stakeholder Environment
Many large scale projects include people in external organizationsthat represent other
stakeholders participating in the development processthey might include
 Procurement agency contract monitors
 End-user engineering support personnel
 Third party maintenance contractors
 Independent verification & validation contractors
 Representatives of regulatory agencies & others.
These stakeholder representatives also need to access to development resources so that
they can contribute value to overall effort. These stakeholders will be access through
on-line
An on-line environment accessible by the external stakeholdersallow them to
participate in the process a follows
Accept & use executable increments for the hands-on evaluation.
Use the same on-line tools, data & reports that the development organization uses to
manage & monitor the project
Avoid excessive travel, paper interchange delays, format translations, paper *
shipping costs & other overhead cost
Unit – Important Questions

1. Define Model-Based software architecture?


2. Explain various process workflows?
3. Define typical sequence of life cycle checkpoints?
4. Explain general status of plans, requirements and product across the major milestones.
5. Explain conventional and Evolutionary work break down structures?
6. Explain briefly planning balance throughout the life cycle?

You might also like