Process Metrics

Introduction
Introduction Software
Production Process
Visual Requirements Definition & Validation ::: Strictly Proprietary & Confidential :::
Agenda
1. S. Passova & D. Shier. Sofea an industry leader in Requirements
Lifecycle Acceleration
2. Russian Team. Introduction to Sofea-Russia Software Production
Process
Standard Software Engineering Process based CMMI
Software Configuration Management

Project Management
Reviews
Quality Assurance
Defect Prevention
Organization Process Maintenance
Tailored process for Sofea-Russia team

Project Profesy 6.3 status
Hiring plan for Release 6.3
Customer support and maintenance
New location
Subjects for discussion
Why Dealing With Process?
Basic Underlying Principle

The quality of a system is governed by the quality of the
process used to develop it
CMMI are formal models for process improvement
People
Process
Technology
Overview of SPP
Software Production Process

Essential part of software engineering activities
Working instructions in various areas of software
engineering and management
Mechanism for continuous improvement
Overview of SPP (contd)
ORGANIZATION PROCESS
Policies
organizations expectations
Processes
working instructions
Assets
Templates
supporting elements
L
E
V
E
L5
o
p
tim
izin
g
Guidelines
L
E
V
E
L4
m
an
age
d
Metrics
Standards
Checklists
L
E
V
E
L3
d
e
fin
e
d
L
E
V
E
L2
re
p
e
atab
le
Tools
L
E
V
E
L1
in
itial
Process in SW Development Cycle

Project Planning, Management Reviews, Quantitative Project and Process Management
Configuration Management
Product Development
Req
Analysis
Kick-off
Develop
ment
Coding&UT
Req Gathering
& Planning
Integration
Testing
Test Planning
Estimates
Planning
Phase Kick-Off
Reviews
System
Release Maintenance
Testing
Automated
Test Generation
Organization Metrics Repository

Organization Knowledge Database
Organization Process Assets
Organization Configuration Management Repository
Postmortem
Audits
Metrics Analysis
Causal Analysis
Software Engineering Handbook
Definition of standard processes/procedures

Standard Development
Generic lifecycle and associated work products
Project Scheduling & Estimation Process

Program Management Process
Configuration Management Process
Product Integration Process
Review Process
Software Engineering Handbook (contd)
Definition of standard processes/procedures

(contd):
Quality Process
Testing Process
Organizational Innovation
Training Process
Documentation Process
Maintenance Process
Supplier Agreement Process
Standard Development Process

Generic Lifecycle Phases:
Pre-planning (SOW)
Requirement Gathering and Planning
Implementation
Requirements Analysis,
Design
Coding & Unit Testing
Test Planning&Development
Testing
Release
Maintenance
Pre-planning
Project Ticket
Official Project Start
Notification of project stakeholders
Planning of Pre-planning activities
Project Kick-off Meeting

Introduction of Project Scope
Communications between project stakeholders
Identification and resolution of issues and dependencies with
stakeholders
SOW (Statement of Work)

Preliminary agreement with Customer
Scope, resources, schedule
10
Requirement Gathering and Planning
Typical Outputs
Requirements Book
Planning Docs
Software Project Management Plan
Risk Management Forms
Software Quality Assurance Plan
Software Configuration Management Plan
11
Requirement Gathering and Planning (contd)
Requirement Book (REQB)

Project requirements
Business
Architectural
Concepts and scenarios
Features/Functions
Target/Host Platform
Interfaces
Installation
Legal
Performance
Test
Documentation
Agreed with Customer
12
Requirement Gathering and Planning (contd)
Project Plans
Software Project Management Plan (SPMP)
Software Configuration Management Plan (SCMP)
Configuration items
Baselines
Change Control Board
Integration Sequence
Software Quality Assurance Plan (SQAP)

Quality Goals
Product oriented
Process Performance
Metrics
Project Audit Plan
13
Requirements Analysis
Functional Specification (Use Case Diagram)

Detailed description of product requirements
Product will be tested against FS
Must be traced to corresponding tests (functional test coverage)
Must be traced to project requirements in Req.Book and vice versa
14
Design
Architecture Meetings
Alternative Technical Solutions identified

Selection Criteria established
Alternatives are evaluated against the Criteria
The best fit selected
Decision documented in Architecture Meeting Minutes
HLD (High Level Design)

Product Architecture (modules, interfaces, dependencies)
Formal notations (e.g. UML, SDL) can be used
Must be traced to Requirements Book
Detailed Design (DD)

Low level decomposition of product modules/interfaces
Must be traces to HLD
15
Coding & UT
Source Code
Must be compliant with Coding Standards
Must pass walkthrough review
Must be traced to HLD/DD
Build Report
Documented Handover to Test Team
Build Procedure
Verification of Integration Readiness
Features implemented
Defects fixed
Results of Unit Testing
HLD/DD -> Code traceability
16
Test Planning & Development
Test Plan
Test Strategy and Approach
Features to be Tested
Test Procedures
Description about how to run the Test Suites
Test Suites
A set of tests to run
17
Testing
Conduct Test Cycles in accordance with Test Plan

and Test Procedures
Analyze Test Logs
Submit the defects, verify defect resolution
Prepare/Update Test Report
18
Maintenance
Customer support after product release

Defect resolution
Implementation of enhancements
Maintenance Plan
Similar to SPMP content
Maintenance Report
Releases with bug fixes/enhancements
19
Software Configuration Management
All about changes!

Documents, Code, Tests = Configuration Items
Revisions are under CM control

Revision Mgmt System (RMS) definition (ClearCase/SVN)
Check-In/Check-Out
Baselines
snapshot of project configuration items
Versions of docs passed reviews (approved)
Builds (Build Report)
Releases
Special Labels/Tags assigned to revisions of Configuration Items
20
Software Configuration Management (cont.)
Defect Tracking System

Tools definition (Test Director/ClearQuest)
Defect Severity
Level 4 (Urgent) - most critical, fatal discrepancy

Level 3 (High) critical, discrepancy
Level 2 (Medium) major discrepancy
Level 1 (Low) cosmetic
Defect Lifecycle
Submitted
Assigned
Open
Resolved
Verified
21
Reviews
Agreement of affected people on content of the doc
Focus on problem identification not problem resolution
Artifact (document) passed review is baselined
Review Procedure in Brief
Notify in advance
Send material in advance
Prepare Review Notes
Assign Moderator, Recorder, Time Keeper
Go thru doc
Record the problems (Review Notes)
Gather metrics (Review Notes)
Agree upon Review Results (Review Notes Sign-off)
Review Follow-Up
22
Project Management
SPMP development
Prepare Work Breakdown Structure

Perform Resource Allocation
Generate Estimates on Effort, Size, Defects
Identify Major Milestones
Prepare Schedule
Identify, Assess project risks
Document in SPMP
Conduct review of SPMP and get approvals of affected people (e.g.
Customer, Mgmt, Test, Quality, Project Team)
SCMP&SQAP
Planning of Configuration Management and Quality Management
Activities
23
Project Management (cont.)
Risk Management
Identify potential problem
E.g. Staffing Re-allocation, External HW/SW Delivery
Assess the Risk
Abatement/Mitigation Plan
Risk Trigger
What to do if triggers
Document in Risk Status Log and

Risk Management Form
Track Risks periodically
---------- I m
pact --------->
- - - - - - - - -Pr obabi l i t y - - - - - - - >
Probability + Impact = Exposure

Affected Tasks
Risk Mgmt Forms for
HIGH Exposure risks
LOW
MEDIUM
HIGH
HIGH(7-9)
(medium)
(high)
(unacceptable)
MEDIUM(4-6)
(low)
(high)
(unacceptable)
(medium)
(high)
LOW (1-3)
(low)
24
Project Management (cont.)
Project Metrics
Project Quality Tracking Tool (PQTT)
Tracked Parameters
Defect Rate, Code Progress, Test Progress, Staffing, Slippage
Other Quality Attributes
Requirements Volatility, Phase Containment Effectiveness, Schedule
Estimation Accuracy
Update by SQA
Analyzed by PLs
Update and Analysis typically weekly
25
Defect Prevention
Purpose
To avoid the recurrence of problems
To prevent potential problems
Project Level DP Activities

Kick-off Meetings
overview of the coming activities
Post-mortems
overview of passed activities
Causal Analysis
Critical investigation of root causes of the most critical defects
26
Defect Prevention
DP Planning and Tracking

DP activities planned in SPMP
Action Items generated are recorded in DTS and tracked till closure
Use of Checklist
A list of typical problems and memory records
Most of project documents have an associated checklist
Accumulated experience of previous projects
Domain Problem Lists
27
Quality Assurance
To independently evaluate the process adherence

SQA Team exists
Participation in reviews
Typically, management docs
Auditing
Use of Audit Checklists
Reporting the non-compliance

Escalating non-resolved issues to Mgmt
Direct reporting to Managing Director
Other SQA functions include

Support of Measurement Program
Project and organization level
Process Consulting
Tailoring/non-compliance issues
28
Tailored process
for Sofea-Russia team
29
Process Tailoring (customizing org process to specific

Profesy needs)
Lifecycle Selection
Metrics selection
Project Documents Definition
Update Standard Software Development Process
Selection Needed Tools
Dependencies
30
The Software Configuration Management Plan (SCMP) defines project-specific

implementation of standard SCM activities specified in SCM Process. It
describes additional information of SCM organization as needed for specific
needs of the project. SCMP shall identify the project configuration items (CI),
directories hierarchy, naming conventions, project baselines, SCM
responsibilities and SCM tools.
Revision Management System (RMS):
Subversion 1.4 - is a tool that used to store all
versions of the software in <PROJECT>
repository and to track changes for the
project
31
Configuration Item (CI) - information created as part of the software
process (documents, source code, reports, etc.)
Configuration identification activities shall identify, name, and describe the
documented physical and functional characteristics of the code, specifications,
design, and data elements to be controlled for the project.
Baseline is a set of consistent CIs. Typically baselines are identified in RMS
by some rules, e.g. as snapshot in time of the current state of every item
related to the project.
Tag/label is used to identify CI baseline.
32
<PROCESS> repository in SVN
proposed for storage of the process artifacts
process
<VAULT> - special share, proposed for storage of the following

invariable items:
Project tools
Project tools documentation
Project technology documentation
Audits
Guidelines
Handbook
Procedures
Standards
Templates
Training
<PROJECT> repository proposed for storage of the following items:

Project documentation
Project Source Code, UnitTests and project tests
Project releases
<PROJECT >
docs
fs
versions
manual mgmt models planspresentationsreports staff
testing
defects models plans reportsscenarios
emf
main
server
branches tags trunk
branches tags trunk
branches tags trunk
UAT
Bundle
33
Goals of Software Product Improvement

Goals
Goal 1: Improve project planning.
Goal 2: Evaluate satisfaction customer level
Goal 3: Improve software quality.
Goal 4: Decrease software defect density.
Goal 5: Increase Defect Containment.
Goal 6: Improve Customer Service.
Goal 7: Increase software reliability
Measurement Areas
Delivered defects and delivered defects per size
Total effectiveness throughout the process
Adherence to schedule
Accuracy of estimates
Number of open customer problems
Time that problems remain open
Metrics in Software Quality Management
Metrics
Customer
Satisfaction
Software
Development
Testing
In-process
35
Software and Process Metrics
Customer
Satisfaction
NSI - Net
Satisfaction Index
Software
Development
Response for a class
(RFC)
Code Convention
Defect Rate (CDR
Number defects per
package)
Code Progress (CP)
Testing
Defects Density
(DD)
Defected rate (DR)
Software
Development
Effectiveness
(SDE):
Defect Removal
Effectiveness (DRE)
Mean Age of Open
Defects(AOD)
NRC number of
regression cycles
TCD Testing
Completeness
Degree
In-process
Schedule
Estimation
Accuracy (SEA)
36
Periodicity of Metrics
Development
Phase
Module Testing
Regression
Testing
Process
CP weekly
SDE cycle
SDE cycle
SEA weekly
Code Progress
Software Development
Effectiveness
Software
Development
Effectiveness
Schedule Estimation
Accuracy
CCD monthly
Code Convention Defect
Rate
RFC- monthly
Response for a class
AOD- cycle
Mean Age of Open
Defects
AOD- cycle
Mean Age of Open
Defects
DD - cycle
AOD - after
release
Mean Age of Open Defects
NSI-after release
Defect Density
Net Satisfaction Index
TCD - cycle
DRE after
release
Testing Completeness
Degree
Defect Removal
Effectiveness
NRC after
release
Number of regression
cycles
DR after release
defect rate
37
Weekly Report Template

Name:
Project: Profesy
Project leader:
Week: DD MM YYYY - DD MM YYYY
PRACTICE TASK OVERVIEW:
NEW ISSUES / ISSUE MANAGEMENT:
NEW RISKS / RISK MANAGEMENT:
SUMMARY OF PROGRESS:
MODULE SIZE/ EFFORT ESTIMATE:
Module
Size (LOCs)
Effort (Hours)
Note: Assembler: 1 line loc, C 2,5 LOC, C++ - 6 LOC, Visual C 9 LOC, Java 6
TEST EFFORT:
Activity
Effort (Hours)
KEY MILESTONE STATUS: (include main milestones only)

Tasks name
Plan
Actual
Delay
SCHEDULE STATUS:
CORRECTIVE ACTION TAKEN FOR SLIPPAGE:
38
Customer Satisfaction Metric

Goal: Evaluate satisfaction customer level
Net Satisfaction Index (NSI)

Completely satisfied = 100%
Satisfied = 75%
Neutral = 50%
Dissatisfied = 25%
Completely dissatisfied = 0%
39
Testing process metrics

Goal: Decrease Software Defect Density.
Defect Density (DD):
DD
NM
NT
NM
100%
NT
- Total defects opened for module
- Total open defects
Goal: Decrease Software Defect Density.

Defect Rate (DR):
NM
DR
1000
N LOC
NM
N LOC
- Total defects opened for module

- Total lines of code number
40

Goal: Increase Defect Containment
Software Development Effectiveness (SDE):
N DC
SDE
100 %
N DO
N DO - Defects opened during testing phase.
N DC - Defects removed during testing phase.
Goal: Increase Defect Containment

Defect Removal Effectiveness (DRE):
DRE
N DC
100 %
N DL
N DC - Defects removed during testing phase

N DL - Defects latent in product (Defects removed during the phase +
defects found later )
41

Goal: Improve Customer Service
Mean Age of Open Defects (AOD):
TDO
AOD
100 %
N DO
TDO
- Total
time N
for
open problems.
DO
- Total number of open problems.
42

Goal: Increase software reliability
Testing Completeness Degree (TCD):
TCD
Np
Nt
100%
N p - Test Scenarios Number Passed.

- Total N
Test
Scenarios Number.
t
43
In-process metrics
Goal: Improve Project Planning
Schedule Estimation Accuracy (SEA):
SEA
Actual Project Duration

Estimated Project Duration
Goal: Improve Project Planning

Code Progress (CP) :
CP N LOCi N LOCi 1
LOCi
- NNumber
of Lines of Code created on phase i.
-N
Number
of Lines of Code created on phase (i-1).
LOCi-1
44
Software Development Metrics

Goal: Improve source code quality
Lorenz metrics (OOP metrics)
Response for a class (RFC)

Code Convention Defect Rate (CDR Number defects per
package) : structure, syntax and miscellaneous defects.
45
Quality Assurance Tasks

Tasks recommended by SEI
Statistics on software design errors
Statistics on software code and test errors
Realize
+
In-process
Projection of test errors and comparison between projected and actual numbers
Measurement of design review coverage
Measurement of test coverage
Tracking of design review actions to closure
Tracking of testing defects to closure
Database for process metrics data across all projects
Analysis of review data gathered during design reviews
Analysis of data already gathered to determine the likely distribution and

characteristics of the errors in the remainder of the project
Analysis of errors to determine their process-related causes
Analysis of review efficiency for each subproject
46
Defect Rate Density by Profesy 6.0/6.1/6.2 Versions
No Release
Defect Rate
6.0
0.41
Level 1
0.75
6.1
0.42*
Level 2
0.44
6.2
0.15
Level 3
0.27
6.3
In-process
Level 4
0.14
Level 5
0.05
Defect Rate (DR):

NM
N LOC
DR
SEI CMMI
Level
Defect Rate
NM
1000
N LOC
- Total open defects.

- Total number of Lines of code.
* The large amount of new functions
were added to Release 6.1 in short
period of time.
47
Testing Process
Usability
Manual
Module
Manual
Code Convention
Manual
*Automated
Code Structure
Manual
zed
* Automated
Functional
Code Structure
Testing
Regression
Manual
*Automated
Stress
Installation
- Russian
Configuration
-Toronto Team
*
Team
-Planned to realize
48
Comparison Manual and Automated testing for

Release 6.0
Parameter
Manual
(actually)
Automated
(estimated)
340
340
Average time of passing test,

h
0.7
0.25
Day
119
42.5
Persons
Months
2.9
1.06
Total number of test scenarios

Cycle regression testing
To cover all test scenarios and to provide good quality of software product its
necessary to automate phase of testing. It should reduce period of testing.
49
Sofea-Russia Team
Sofea-Russia Team Staff and Experience in Profesy project
Education
44%
PHD 19%
PHD in progress -15%
Master 11%
Bachelor 11%
Students 44%
19%
11%
15%
Students
11%
Bachelor
Master
PHD in progress
PHD
Participation
51%
15%
5 years and over- 15%

3-4 years - 19%
1-3 years - 15%
Less than 1 years 51%
19%
15%
less than 1 year
1 -3 years
3-4 years
5 years and over
50
Project management Legend
PM manages sub-project with small number of

people.
SPM manages multiple sub-projects with small
number of people. Usually sub-projects form a
bigger line of development
SSPM manages multiple sub-projects that have
SPM or a PM as a lead. Usually sub-projects form a
bigger line of development
51
Basic processes
Release 6.3 Development
Customer
Request
Req Analysis
Requirements Definition
General Planning
Software Architecture Design
Development
Phase 0
Phase 1
SubProject 1
SubProject 2
SubSubProject 3 Project 4
Phase 2
Integration
Overall system and regression testing
Release
52
Project Documents Definition

Project Planning, Management Reviews, Quantitative Project
and Process Management
Product Development
Use Case
Specification
Schedule,
QA doc
Test Report
from Test
Director
Test Report from Test
Director
Req
Analysis
Kick-off
Profesy
API (Javadoc)
Develop
Coding&UT
ment
Req Gathering
& Planning
Integration
Testing
Test
Planning
Profesy
API
(Javadoc)
System
Testing
Release Maintenance
Automated
Test Generation
QA doc
Test Plan
for Russian
team
Profesy 6.2 Test

Scenarios
53
Project management practices (sub-projects and

prototyping)
Release Developing divided on 4 Sub-Projects:

1.
2.
3.
4.
EMF integration, General Usability

Use Case Graphic Editor and Use Case Diagram
HTML Report Publishing
Prototyping:
1. Sub-Project 1: EMF Integration
2. Sub-Project 2: SVN client prototype, Diff-Merge prototype
3. Sub-Project 4: Velocity HTML engine prototype
54
Assistance processes
Sub-Project Development
Prototyping
Refinement of requirements
for SubProject
Exploring and analysis

existing technologies
Sub-Project Planning/Preplanning
Quick design
Sub-Project Design
Prototyping
Refining
Design
and Prototype
Sub-Project Coding
Sub-Project Testing
Building
Prototype
Customer evolution
of Prototype
Sub-Project Module
Phase 0,1
Phase 2
Customer satisfied
Prototype and report
Sub-Project Finish
55
Release 6.3 Planning

Release Developing divided on three phases:
Nov 10
2006
Phase 0
(Simple)
Phase 1 (Full
version)
Phase 2 (Final
Version)
Dec 01
2006
Jan 01
2007
Feb 01
2007
March 01
2007
April 01
2007
May 01
2007
June 01
2007
July 31
2007
Feb 16
2007
Apr 02
2007
May 16
2007
Testing
milestone
0
milestone
1
milestone 2
56
Sub-Project 1 (EMF, General Usability)

Nov 10 2006
Dec 01 2006
Jan 01 2007
Feb 01 2007
March 01 2007
April 01 2007
EMF, General Usability
New data model

integration
Requirements
Specification
Multi-model
support
Requirements Specification
Project Explorer
Requirements
Specification
New Detail Pane
Preferences and
Settings
Design / Development
Clickable
Message Pane
Import from 3-rd

party tools
May 01 2007
June 01 2007
Testing
Design / Development standalone component
Testing
Multi-model
Integration
Design/
Development
Multi-model
Integration
System
Testing
Release
Preparation
Setup
testing
Post Setup
Testing
Integration
Testing
Testing
Feb 16 2007
milestone 0
Apr 02 2007
milestone 1
May 16 2007
milestone 2
PM for this sub-project is Anton Trinkunas

There are 4 developers now and sub-project needs 4 additional SE. Requirements phase
is delayed 0.5-1 month, and design/development task in time except task Import from 3rd party tools. Delay two weeks.
57
Sub-Project 2 (Configuration Management)

Nov 10 2006
Dec 01 2006
Requirements
Specification
(Non EMF)
Compare / Diff /
Merge
Formal
Workspace
Jan 01 2007
Requirements
Specification
Configuration
Management
Version Control
User Interface
Feb 01 2007
Development
/ Design
(Non EMF)
March 01 2007
May 01 2007
June 01 2007
Design/Development (EMF)
Requirements
(EMF)
EMF
Integration
Design/Development
Design
/Development CM/SVN Library
standalone
Design /Development
MKS
April 01 2007
Testing
Design /Development
Synch/Merge/Diff.
Testing
Development
Synch/Merge/Diff
Research and Requirements

Specification
Integration
Testing
Testing
Design
/Development
prototype
System
Testing
Release
Preparation
Setup
testing
Post Setup
Testing
Testing
Feb 16 2007
milestone 0
Apr 02 2007
milestone 1
May 16 2007
milestone 2
PM for this sub-project is Dmitry Agapitov

There are 4 developers now
Design/development tasks in time except task Formal workspace. EMF Integration.
Delay two weeks.
58
Sub-Project 3 (Use Case Graphic Editor and

Use Case Diagram)
Nov 10 2006
Use Case Diagram & Use

Case Graphical Editor
Layout
improvements
UCG Editor GUI
Dec 01 2006
Jan 01 2007
Feb 01 2007
March 01 2007
Export to MS Visio
Design/Devel
EMF
providers
Devel of GUI
elements
May 01 2007
Design/Development
Layout algorithms improvements
UC Diagram
integration
April 01 2007
EMF
Integration
EMF
Integration
Design /Devel
Interaction engine
Design /Development
Export to MS Visio
Modular and
integration testing
June 01 2007
System
Testing
Release
Preparation
Setup
testing
Post Setup
Testing
Testing
Feb 16 2007
milestone 0
Apr 02 2007
milestone 1
May 16 2007
milestone 2
PM for this sub-project is Michael Trevgoda

There are 3 developers now, 2 more is necessary.
Design/development tasks delayed for two weeks.
59
Sub-Project 4 (HTML Report Publishing)

Nov 10 2006
HTML Report Publishing
Profesy Reporting
Format (EMF)
Dec 01 2006
Requirements
HTML Site Design

Templates Engine
Profesy
Integration
Jan 01 2007
Feb 01 2007
PRF
Design
March 01 2007
Testing
April 01 2007
PRF
Generator
HTML Site Design
Engines Analysis
Testing
Testing
Publishing via
Templates
Prototyping
Requirements
Integration
Testing
May 01 2007
GUI
Wizard
Traceability
Preferences
Traceab.
June 01 2007
System
Testing
Release
Preparation
Setup
testing
Post Setup
Testing
Testing
Feb 16 2007
milestone 0
Apr 02 2007
milestone 1
May 16 2007
milestone 2
PM for this sub-project is Alexander Groman

There are 2 developers now, 1 more is necessary.
Development tasks was delayed for 2 weeks, but design was implemented detailed.
60
Release 6.3 milestones and Hiring Plans

Nov 10 2006
Dec 01 2006
Jan 01 2007
Feb 01 2007
March 01 2007
April 01 2007
May 01 2007
June 01 2007
Feb 16 2007
R6.3 Phase 0
Apr 02 2007
R6.3 Phase 1
May 16 2007
R6.3 Phase 2
Hiring Plan
Testing
Core team: 13
Students: 3
Hirig:
1 student,
3 engineers
Hiring:
2 students
Dismissed:
1 SE,
1 IT mgr
Hiring:
4 students
Hiring 3
students
Requirements to Internship candidates:

Java programming language knowledge
Base knowledge of Object Oriented Programming
Initial verbal and written English communication skills
Test Task for each student must be done
61
Trainings
Training is an integral part of any organization and has special significance to organizations
dealing with knowledge-based products and services. All managers have to ensure that the
engineers assigned to the project receive sufficient training to improve their skills every year.
Trainings
Core Team
Internship Team
Code convention
Version control
New technologies
New libraries/tools
SW process improvement
Code Convention_
Version Control_
Defect Tracking_
Schedule and Time Tracking
Defect tracking system

SW development process
Schedule and Time Tracking
Training exercises have been conducted:
Expectations:
Advanced trainings courses
English language trainings for Sofea-Russia
Java 1.5 (Sun Microsystems Conference)

SVN training for Sofea-Russia - October 2006
Test Director December 2006
Profesy 6.2 technologies - periodic training for new
Team members
62
Support and Maintenance
Customer
Request
Request
analysis
Supported Release 5.5,

6.0/1/2: defects and
improvements.
Estimation
Coding
Testing
Build
63
Subjects for discussion
Descriptions/Deliverables
Milestones and Outlook
Issues and Resolution
Plan
Risks and Mitigation
Strategies
Dependencies and Outlook
Budget and Actual/Outlook (estimated)
Metrics progress, quality
64

Process Metrics

Transféré par

Informations du document

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

Process Metrics

Transféré par

Droits d'auteur :

Formats disponibles

Introduction

Software Configuration Management

Tailored process for Sofea-Russia team

Why Dealing With Process?

Basic Underlying Principle

Software Production Process

Overview of SPP (contd)

Process in SW Development Cycle

Organization Metrics Repository

Software Engineering Handbook

Definition of standard processes/procedures

Project Scheduling & Estimation Process

Software Engineering Handbook (contd)

Definition of standard processes/procedures

Standard Development Process

Project Kick-off Meeting

SOW (Statement of Work)

Requirement Gathering and Planning

Requirement Gathering and Planning (contd)

Requirement Book (REQB)

Agreed with Customer

Requirement Gathering and Planning (contd)

Software Quality Assurance Plan (SQAP)

Functional Specification (Use Case Diagram)

Alternative Technical Solutions identified

HLD (High Level Design)

Detailed Design (DD)

Test Planning & Development

Conduct Test Cycles in accordance with Test Plan

Customer support after product release

Software Configuration Management

All about changes!

Revisions are under CM control

Software Configuration Management (cont.)

Defect Tracking System

Level 4 (Urgent) - most critical, fatal discrepancy

Prepare Work Breakdown Structure

Project Management (cont.)

Assess the Risk

Document in Risk Status Log and

- - - - - - - - -Pr obabi l i t y - - - - - - - >

Probability + Impact = Exposure

Project Management (cont.)

Update and Analysis typically weekly

Project Level DP Activities

DP Planning and Tracking

Domain Problem Lists

To independently evaluate the process adherence

Reporting the non-compliance

Direct reporting to Managing Director

Other SQA functions include

Tailored process for Sofea-Russia team

Tailored process for Sofea-Russia team

Process Tailoring (customizing org process to specific

The Software Configuration Management Plan (SCMP) defines project-specific

<VAULT> - special share, proposed for storage of the following

<PROJECT> repository proposed for storage of the following items:

manual mgmt models planspresentationsreports staff

branches tags trunk

branches tags trunk

branches tags trunk

Goals of Software Product Improvement

Metrics in Software Quality Management

Software and Process Metrics