LOGO

Software Project Managerment

K15T02 – Team02

Contents:

Introduce TSP

TSP Process

1

2

4

33

TSP & CMMI

Software Development Process

Software Development Process

The software development process is the set of coordinated activities performed by : Engineers Managers Technical writers

Software development process aims to create software products

There are four operation are the foundation of most software process is:

oSoftware specificationoThe software developmentoEvaluation softwareoThe evolution of software

Software Development Process

Software Development Process

Activities and steps

o Indentify the system developmento Establish project scope and timeo Develop project plano Identify and requirements analysis :

Clarify requirements Review requirements documentation requirements.

1. Requirement

o Develop technical design architecture workso Identify the system output, input and user

interface.o Select the system componentso Determine how to integrate the components

2. Architect

3. Implement

o Translating the design into code o Find and check the identification code to

prevent syntax errors

4. Test

o Check your code o Check the performance of the system in

hardware.o Testing the system in the business

environment.

5. Maintain

o Continued monitoring and supporto Provide support (debugging, repair, improve)

Software Development Process

Software development model

1. The Waterfall Model Sequential development model Only move to the next phase when the preceding

phase is completed. Use for a large software system with stable

requirements

2. The Spiral Model Combines elements of both design and

prototyping concepts Combines prototyping model and the waterfall

model Estimates (i.e. budget, schedule, etc.) Issues are discover earlier and cope with the

changes better .

3. AUP (Agile Unified Process)

AUP is a simplified version of the Rational Unified Process (RUP) and using agile techniques

AUP applies agile techniques include : Test driven development (TDD) Agile Model Driven Development (AMDD) Agile change management Database refactoring to improve your

productivity.Use for medium and small projects, requiring

fast development.

3. AUP (Agile Unified Process)

4. Scrum Scrum use the AGILE methodology Include: establish , monitoring, and managing

the job is not done, the current work, the risks, problems and changes.

SCRUM particularly suitable for the requested project or quickly change.

5. Extreme Programming

XP is operating iteration model The advantage of this model is that the project

team to quickly get feedback from customers.The necessary changes will be applied

immediately in the next iteration.

Contents:

Software Development Process

Introduce TSP

TSP Process

1

2

4

33

TSP & CMMI

Team Software Process (TSP)

Definition o TSP is a process that is specifically designed for software teams

o It guides engineering teams that are developing software-intensive products

o Using TSP helps organizations establish a mature and disciplined engineering practice that produces secure, reliable software in less time and at lower costs

Purpose Build high-performance teams and help them:o Plan their work o Negotiate their commitments with management o Manage and track projects to a successful conclusion o Produce quality products in less time o Achieve their best performance without the “death march”

ending

Introduce TSP:

Contents:

Software Development Process

Introduce TSP

TSP Process

1

2

4

33

TSP & CMMI

Implementation Strategy:

The TSP has three general parts:

1. The first part is team formation, during which you recruit potential team members and provide them and their mangers with any needed training or orientation

2. Second comes the team launch, in which management tells the team what they want done and the team builts its plan to do the necessary work.

3. The third part is ongoing team operation, where the team follows its plan to do the job.

TSP Process:

Implementation StrategyPersonal Software Process (PSP) • The first step in a TSP

initiative is to train all team members who can write programs in PSP

• The result of the PSP: learn about good processes improve their own

processes measure the effects of those

process changes quantify the benefits they

have experienced, and set goals for further improvements

1. In PSP0, they lay a simple foundation for the learning to come:

• Following simple process scripts.• Collecting three basic measures of their

work (time spent, size of products produced, and defects corrected).

• Performing a simple post-project analysis.

2. In PSP1, they begin to build the capability to plan and manage their own work:

• Following a defined project planning process.

• Using their own prior data to make increasingly more accurate estimates for each programming assignment.

• Planning their work at a level of detail that allows them to track and manage their progress.

3. In PSP2, they focus on achieving significant quality improvements:

• Using their prior data to plan for incremental improvements in the quality of their programs.

• Removing defects early using personal review techniques guided by their own prior defect performance.

• Identifying and capitalizing on defect prevention opportunities in their program design and implementation methods.

Those who complete the PSP boot camp emerge with the knowledge and skills to make accurate plans, work to those plans, and produce superior quality products.

The TSP Launch Process

Meeting Content1 Understand the Project

Objectives

2 Assign Roles and Define Team Goals

3 Define the Work and the Approach

4 Build the Overall Plan

5 Build the Quality Plan

6 Build Individual Work Plans

7 Risk Management

8 Management Review

9 Making a Commitment

Software Development Process

Introduce TSP

TSP Process

1

2

4

33

TSP & CMMI

Contents:

TSP & CMMI:

CMMI and TSP form a powerful set of technologies that businesses can use to improve performance and meet their business goals, sometimes even quicker than using one by itself.

The TSP has the same roots as the CMMI, being based on the Software Engineering Institute’s (SEISM) early research that produced the CMM for Software (SW-CMM). As such, it aligns well with the CMMI and partly or fully satisfies the CMMI’s goals.

So, adding the TSP to a CMMI initiative does not mean adding more work to an already overworked group. Rather, it can be an effective way to accelerate that initiative by laying a solid foundation of process discipline, engaging the engineers from the very beginning, and providing processes that already address a significant number of CMMI practices. The costs of incorporating the TSP into your CMMI initiative should be more than returned as you achieve your CMMI goals more quickly and with less organizational pain.

THE END