TEAM SOFTWARE
PROCESS
Introduction
The Team Software Process (TSP) is a software development
methodology that helps teams improve their quality and productivity. It
is a discipline-based process that is based on the Personal Software
Process (PSP), which is a process for individual software developers.
• TSP is designed to help teams develop software-intensive products in
a more efficient and effective way. It provides a framework for teams
to plan, estimate, track, and improve their software development
process.
Benefits of Using TSP
There are many benefits to using TSP, including:
Improved software quality
• One of the main benefits of using TSP is that it can help teams
improve the quality of their software. This is because TSP
emphasises the importance of testing and quality assurance
activities. TSP teams also use metrics to track their progress and
identify areas where they can improve the quality of their code.
Increased productivity
• TSP can also help teams increase their productivity. It provides a
framework for teams to plan, estimate, track, and improve their
software development process, which helps teams to avoid wasting
time on rework and to focus on the most important tasks.
• Reduced costs
• TSP helps teams reduce costs and to avoid costly mistakes and to
deliver software on time and within budget. TSP teams are also
more likely to be able to reuse code, which can further reduce
costs.
Reduced risk of project failure
• TSP can also help to reduce the risk of project failure. This is
because TSP provides a framework for teams to identify and
mitigate risks throughout the software development process. TSP
teams are also more likely to have a realistic understanding of the
scope of the project and the resources required to complete it.
Key Principles of TSP
• Team-Oriented Approach
• Discipline of Process Definition and Adherence
• Continuous Process Improvement
• Quality Focus
• Measurement and Analysis
TSP TRAMEWORK AND ACTIVITIES
• LAUNCH
It reviews course objectives and describes the TSPi structure
and content. It assigns teams and roles to students and
describes the customer needs statement. It also establishes
team and individual goals.
• STRATEGY
It creates a conceptual design for the product and establishes
the development strategy and decide what will be produced in
each cycle. Strategy makes initial size and effort estimates
and establish a configuration management plan, reuse plan
and risk management.
• PLAN
It estimates the size of each artifact to be developed. Planning also
identifies tasks to be performed, estimates time to complete each
task;, assign tasks to team members, make a weekly schedule for
task completion and make a quality plan.
• REQUIREMENTS
Requirements analyze need statements and interview the customers,
specify and inspect the requirements and develop a system test plan.
• DESIGN
It creates a high-level design, specify the design, inspect the design,
develop an integration test plan.
• IMPLEMENT
Implementation uses the PSP to implement modules/units, creates
detailed design of modules/units, reviews the design, translates the
design to code, review the code,
compile and test the modules/units and analyze the quality of the
modules/units.
• TEST
Testing builds and integrate the system. It conducts a system test and
produce user documentation.
• POSTMORTEM
It conducts a postmortem analysis, writes a cycle report and produce
peer and team evaluations.
