Scribd
Upload
20 views33 pages

Lecture 9 - Process Maturity Plan - SCM SQA Standards

The document discusses process maturity and improvement areas like commitments, planning, SCM, and SQA. It covers topics like basic SCM, change management, measurements, quality assurance, establishing an SQA function, software standards, and a standards development program.

Uploaded by

sadia amjad
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
20 views33 pages

Lecture 9 - Process Maturity Plan - SCM SQA Standards

The document discusses process maturity and improvement areas like commitments, planning, SCM, and SQA. It covers topics like basic SCM, change management, measurements, quality assurance, establishing an SQA function, software standards, and a standards development program.

Uploaded by

sadia amjad
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/ 33

Process Maturity Plan

Focus on highest priority areas for organizational improvement: commitments,


planning, SCM, SQA
Software Configuration
Management
At basic level to start with
Needed?
• Multi person construction of multi-version
software
– What is my current software configuration?
– How do I control changes to my configuration?
– How do I inform everyone else of my changes?
– What changes have been made to my software?
– Do anyone else’s changes affect my code?
Software Systems Development
• Development
• Integration
Basic SCM
• Baseline: official repository that contains the
most current version
• Ensure the following:
– One official copy of code
– Track of revisions (numbering)
– Ability to determine what has changed
– Ability to handle multiple copies of same code
Change Management System
• Change Control Board
– Problems?
Measurements and Metrics
• Open changes
• Oldest outstanding changes
• Number of changes to a particular component
• MTCC
• Change backlog
SQA
Monitoring? Verifying?? Tracking???
Quality
• Need of quality?
– Schedule?
– Bug?
• Tracking?
Software Quality
Parties interested in Quality
• Client/Customer?
• Developer?
Software Quality Assurance

i s
s s
ce d?
ro te
p en
d
e em
h
is pl
l
b im
s a
t g
e
y be i n
l l
a ly
c i
ffi ual
O ct
a
Is SQA Useful?
• 3 to 5 times improvement in software quality
over 8 years. SQA was enforcing standards
• Project success rate increased from 60% to
76%. Enforcing standards
• “Increased product quality and
cost-effectiveness through explicit SQA activity
• -SQA “significantly increased ability… to
predictably engineer reliable software”
QC vs QA
• Withholding a product that does not qualify
• Minimize the cost of guaranteeing quality
Assurance of?

Motivate people to
monitor each other??
Goals of SQA
• Monitor software, monitor development
process, improve quality
• Ensure compliance with standards and
procedures
• Generate alerts in case of deviations s.t.
inadequacies may be fixed
Objectives of SQA Activities
• Assure that the software conforms to
functional technical requirements
• Assure that the software conforms to
managerial scheduling and budgetary
requirements
• Initiating and managing activities that improve
e l l
prospects of conforming to functional and a s w
e nt ….
managerial requirements, with reduced
l o p m ncosts
ce
eve tena
D a in
as m
Potential Pitfalls
• It is a mistake to assume that the SQA people
themselves can do anything about quality
• The existence of an SQA function does not
ensure that the standards and procedures are
followed
• Management needs to show support by
following SQA recommendations, in order to
make SQA effective
SQA Responsibilities
• Review all development and quality plans for
completeness
• Participate in design and code inspection
• Review all test plans for adherence to standards
• Review a significant sample of all test results to
determine adherence to plans
• Periodically audit SCM performance to determine
adherence to standards
• Participate in all quarterly and phase reviews to
register nonconcurrence
Example Items for Review
Establishing SQA Function -
Organizational framework
• Definition of QA practices
• Software project planning evaluation
• Requirements evaluation (conformance)
• Evaluation of design process
• Evaluation of coding practices
• Evaluation of software integration and test
process
• Evaluation of management and project control
process
• Tailoring of QA procedures
SQA Reporting
• Project Manager?
Metrics and Measurements
• ???
• Number of non-concurrences?
– Number of deviations from process?
• Time spent on SQA activities?
• Effort?
Some Maturity? Repeatable?
• Organization’s capabiities in the following
mastered
– Project Management
– Basic SCM
– SQA
• Stable performance of projects
• Better foundation for orderly process
improvement
More Maturity? The Defined Process?
• Why?
– Need of a uniform and consistent process, across
organization
– Coherent framework for organized learning
• How?
– Software Standards
– Inspections
– Testing
– Advanced SCM
– Process Models and Architecture
– SEPG
Software Standards

Help perform tasks in consistent


manner
Examples
• Programming Standards
• Documentation Standards
• Naming and Numbering
• Configuration Management
• Software Development Plan
• SQA Plans
• SQA Reviews
• Problem Reporting
Why Standards?
• Many people perform similar/same task
• Many products being worked on at the same time by many
people

• Disagreements during quality debates when schedule is


tight
• Knowing and understanding common way of doing the
same task

• Move professionals between projects, with no or limited


training
• Uniform method of review
Standards Development Program
• Priority needs?
– Management and planning (status report, SQA,
estimation)
– Development process (RS, coding, reviews,
inspections)
– Tool and process (code editing tools, product naming,
size measure) Adopt others’ standard without careful
examination
• Available standards?
• Projects’ status?
• Staff skills?
• Enforcement mechanism?
Standards Development Program
• Maintaining standards
– SEPG
• Stay aware of standard implementation problems
• Provide advice (when needed) on using standards
• Maintain the standards baseline and control changes
• Ensure effectiveness and pertinence of standards (periodic
review)
• Enforcing standards
– SQA
• Automated tools (coding conventions, naming conventions etc)
• Exhaustive reviews (product plans, delivery commitments etc.)
• Statistical reviews (code inspection)
When to and When not to use
Standards?
• When things need to be done uniformly
• When we have a clear best alternative/practice

• When technical judgement is required?


– Maximum module size?
– Maximum complexity?

• Use guidelines when standards are not


appropriate option
Quiz 4
5x6 = 30 Marks. 20 Minutes.
Task Planned effort Actual effort
1 6 5
2 4 6
3 5 4
4 14 15
5 16 17
6 6 –
7 8 –

30 tasks in the whole project were estimated to require 390 person days.
At time t the above data is available.
A ‘–’ is replaced with a value when the task gets completed
To do: Compute the values for SPI, Schedule Variance, percent scheduled for
completion, percent complete, CPI, cost variance.
References
• SE book by Pfleeger
• SE book by Pressman
• SQA by Daniel Galin
• Managing the Software Process by Humphrey

33

You might also like