DEPARTMENT OF CSIT

COURSE NAME – ADAPTIVE SOFTWARE

ENGINEERING

COURSE CODE – 22CI2001

TOPIC:
PERSONAL AND TEAM PROCESS MODELS
 AIM OF THE SESSION

To familiarize students with the basic concept of Personal and Team Process Models

INSTRUCTIONAL OBJECTIVES LEARNING OUTCOMES

This Session is designed to: At the end of this session, you should be able to:
1. Demonstrate Personal and Team Process models 1. Define Process Models
2. Describe Personal Software Process (PSP) defines 2. Describe Personal and Team Process models
5 framework activities 3. Summarize Difference between Product and Process
3. List out the Product and Process
4. Describe the Difference between Product and
Process

2
 AGENDA
 Personal and Team Process models​
 Personal Software Process (PSP) defines 5 framework activities
 Team Software Process (TSP)
 Product and Process
 Difference between Product and Process:-

3
 PERSONAL & TEAM PROCESS MODELS

•The software process is effective only if it is amenable to significant adaption to

meet the needs of the project team.
•Personal process model: Individual create a process that best fits your needs, and at
the same time, meets the broader needs of the team and the organization.
•Team process model: The Team itself create its own process, and at the same time
meet the narrower needs of individuals and the broader needs of the organisation.

“Watts Humphrey” argues that both models are achievable but require hard work, training and coordination.

4
 Personal Software Process (PSP)
Watts Humphrey suggests that to change an ineffective personal process, an
individual must move through four phases, each requiring training and careful
instrumentation.
The PSP
• emphasizes personal measurement of the work product that is produced.
• emphasizes the resultant quality of the work product.
• Makes practitioner responsible for project planning (e.g; estimating and
scheduling)
• Empowers the practitioner to control the quality of all software work
products that are developed.

5
 PERSONAL SOFTWARE PROCESS (PSP)
DEFINES 5 FRAMEWORK ACTIVITIES
• Planning. This activity isolates requirements and develops both size and resource
estimates. In addition, a defect estimate (the number of defects projected for the work)
is made. All metrics are recorded on worksheets or templates. Finally, development
tasks are identified, and a project schedule is created.

• High-level design. An external specification is created for each component and a

component design is created. Prototypes are built when uncertainty exists. All issues
are recorded and tracked.

6
 PERSONAL SOFTWARE PROCESS (PSP)

• High-level design review. Formal verification methods are applied to uncover errors
in the design. Metrics are maintained for all important tasks and work results.

• Development. The component level design is refined and reviewed. Code is

generated, reviewed, compiled, and tested. Metrics are maintained for all important
tasks and work results.

• Postmortem. Using measures and metrics collected the effectiveness of the process
is determined. (If this is a large amount of data it should be analyzed statistically.)
Measures and metrics should provide guidance for modifying the process to improve
its effectiveness.

7
 PERSONAL SOFTWARE PROCESS (PSP)

•PSP Stresses the need for each software engineer to identify errors early and as important, to
understand the types of errors through a rigorous assessment activity performed on all work products
you produce.
However, PSP has not been widely adopted throughout the industry.
•PSP is intellectually challenging and demands a level of commitment (by practitioners and managers)
that is not always possible to obtain.
•Training is relatively lengthy and training costs are high.
•The required level of measurement is culturally difficult for many software people.

8
 TEAM SOFTWARE PROCESS (TSP)
The goal of TSP is to build a “self-directed” project team that organizes itself to produce
high-quality software. Humphrey defines the following objectives for TSP.

• Build self-directed teams that plan and track their work, establish goals, and own their processes
and plans. These can be pure software teams or integrated product teams (IPT) of three to about
20 engineers.
• Show managers how to coach and motivate their teams and how to help them sustain peak
performance.
• Accelerate software process improvement by making CMM Level 5 behavior normal and
expected.
– The Capability Maturity Model (CMM), a measure of the effectiveness of a software process.
• Provide improvement guidance to high-maturity organizations.
• Facilitate university teaching of industrial-grade team skills.

9
 DIFFERENCES BETWEEN PSP AND TSP
PSP
PSP is a project management process that defines how to manage a project in a
face-to-face environment.
PSP is more formal and structured than TSP.
PSP is more suited for large projects.
PSP is a high-level language, and it is easy to learn and use.
PSP is a structured language, and it is easy to read and write.
PSP programs are written in English, and they are easy to understand.
PSP is a portable language, and it can be run on any platform.
PSP is an interpreted language, and it does not need to be compiled.
PSP is a free language, and it can be downloaded from the internet.
PSP is a linear process model that is completed in a sequential manner.
10
TSP
TSP is a project management process that defines how to manage a project in a
virtual environment.
TSP is less formal and structured than PSP.
TSP is more suited for small projects.
TSP is a low-level language, and it is difficult to learn and use.
TSP is an unstructured language, and it is difficult to read and write.
TSP programs are written in assembly language, and they are difficult to
understand.
TSP is a platform-dependent language, and it can be run only on specific platforms.
TSP is a compiled language, and it needs to be compiled before it can be run.
TSP is a commercial language, and it is not available for free.
TSP, on the other hand, is an iterative and incremental process model that allows
for feedback and changes at each stage of the process.
HOW PSP USED FOR QUALITY IMPROVEMENT

• The PSP helps the engineer to control, manage, and improve his or her work
and it is taught through a course.
• The students (many times software engineers) perform several programming
exercises in which techniques and phases of the PSP are added as the exercises
advance.
• For each exercise, process data are collected

11
HOW TSP USED FOR QUALITY IMPROVEMENT

• The primary objective of TSP is creating a team environment

that supports disciplined work while still building and
maintaining a self-directed team.
• TSP guides a team in addressing essential business needs of
schedule management, cycle-time reduction, effective quality
management, and better cost management.

12
 PRODUCT AND PROCESS
• Product:
• Product includes any software development based on the customer’s request. This can be a problem-solving
software or computer-based system. It can also be said that this is the result of a project.

• Process
• Process is a set of sequence steps that must be followed to create a project. The main purpose of a process is to
improve the quality of the project. The process serves as a template that can be used through the creation of its
examples and is used to direct the project.

13
 DIFFERENCE BETWEEN PRODUCT AND
PROCESS:-
S.NO Product Process

While process is a set of sequence steps that must

1. Product is the final production of the project.
be followed to create a project.

Whereas the process is focused on completing

2. A product focuses on the result.
each step being developed.

In case of product, the firm guidelines are In contrast, the process consistently follows
3.
followed. guidelines.

4. A product is tended to be short term. Whereas the process is tended to be long term.

The main goal of the product is to complete While The purpose of the process is to make
5.
the work successfully. better the quality of the project.

14
SELF-ASSESSMENT QUESTIONS

1. What is PSP.
2. What is TSP.
3. Differences between PSP and TSP.
4. How PSP used for Quality improvement.
5. How TSP used for Quality improvement.
6. Differences between product and process

15
 REFERENCES FOR FURTHER LEARNING OF THE
SESSION
TEXTBOOKS:

1. Roger S.Pressman, “Software Engineering – A Practitioner’s Approach” 7th Edition, Mc Graw Hill,(2014).
2. Ian Sommerville, “Software Engineering”, Tenth Edition, Pearson Education, (2015).
3. Agile Software Development Ecosystems, Jim Highsmith, Addison Wesley; ISBN: 0201760436; 1 st edition

Reference Book
Agile Modelling: Effective Practices for Extreme Programming and the Unified Process Scott Amber John Wiley &
Sons; ISBN: 0471202827; 1st edition.

WEB REFERNCES/MOOCS:
https://www.digite.com/kanban/what-is-kanban/
http://www.scaledagileframework.com
https://www.guru99.com/test-driven-development.html
https://junit.org/junit5/

16
 THANK YOU

Team – ADAPTIVE SOFTWARE ENGINEERING

17