Scribd
Upload
77 views41 pages

TMP3413 Software Engineering Lab: The Development Plan

The document discusses the development plan process using the Team Software Process (TSP). It explains that the plan allows engineers to work more efficiently by knowing what tasks need to be done and when. The planning process involves estimating task sizes, creating task and schedule forms for each engineer, balancing the workload, and generating final team plans and forms to track progress. Key forms include TASK, SCHEDULE, SUMP, SUMS, and logs to track time worked and defects found.

Uploaded by

Nurfauza Jali
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
77 views41 pages

TMP3413 Software Engineering Lab: The Development Plan

The document discusses the development plan process using the Team Software Process (TSP). It explains that the plan allows engineers to work more efficiently by knowing what tasks need to be done and when. The planning process involves estimating task sizes, creating task and schedule forms for each engineer, balancing the workload, and generating final team plans and forms to track progress. Key forms include TASK, SCHEDULE, SUMP, SUMS, and logs to track time worked and defects found.

Uploaded by

Nurfauza Jali
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
You are on page 1/ 41

TMP3413

Software
Engineering Lab

Lecture 04:
The Development
Plan
Why Make Plans?

Can work more efficiently, know what to do and


when to do the tasks

More likely to meet the commitments and


perform better work

Can increase or reduce the amount of work we


plan to do
Balanced Plans
 A plan is balanced when all the engineers
complete their planned tasks in the proper
order and at roughly the same time.

 With a balanced plan, no one needs to wait


for anyone else and everyone is fully utilized.
Tracking Progress Against the Plan
 A detailed plan helps us to track and manage our
work.

 With TSP, the principal project-tracking measures are


planned value (PV) and earned value (EV). These
measures provide a way to determine the schedule
contribution of each task.
Tracking Progress Against the Plan
(cont)…
Tracking Progress Against the Plan
(cont)…
 Table 5.1 shows the planned-value calculations
for cycle 1 of a project to develop the
change counter software tool (to count
program size).

 By tracking earned value against planned


value, we can see where we are on a
project. This knowledge helps us to manage
our work precisely and also helps us to meet
the schedule.
Estimating Level
 With the TSP, engineers estimate programs by
first identifying the objects of functions they
contain and then estimating the sizes of these
objects and functions.

 For the programs developed for this course,


there are typically only three levels:
 the system,
 the modules or system components, and
 the module’s objects or functions.
The TSP Planning Process (cont…)
The TSP Planning Process (cont…)
1. In the strategy phase, as described in Lecture 4,
we produced the conceptual design. We will use
this conceptual design throughout the planning
process.
2. During the strategy phase, we estimated the
sizes of the various parts of the conceptual
design, decided which parts to develop in each
cycle and entered the information on the STRAT
form.
The TSP Planning Process (cont…)
3. Now, during the planning phase, we enter on the
SUMS form the names and estimated sizes of the
components we will develop in cycle 1. We also
identify any other products we will need to develop
for cycle 1, such as test plans or requirements
specifications and enter these items and their
estimated sizes on the SUMS form.

4. List the tasks required to build the products identified


in step 3, estimate how long each task will take and
enter this information on the TASK form.
The TSP Planning Process (cont…)
5. Make the quality plan, SUMQ. Again, we use the
TSP support tool to do this.

6. Make copies of the team TASK and SCHEDULE


forms for each engineer and have each engineer
produce personal TASK and SCHEDULE forms.

7. Use the TSP tool to generate individual TASK and


SCHEDULE forms that show the PV and
completion times for each of our
personal tasks. Every team member
should do this.
The TSP Planning Process
8. With the TASK and SCHEDULE forms for every
engineer, we have the data to balance the
team workload. Do this by identifying those
engineers who will complete tasks later than
desired and reassigning some of their work to
other team members.

9. Use the TSP tool to roll up the individual


engineer plans to produce the final team
plan. Also generate final copies of the team
and engineer TASK and SCHEDULE form as well
as copies of the SUMP and
SUMQ formsfor the total project.
The Development Plan Scripts (cont…)
The Development Plan Scripts (cont…)
The Development Plan Scripts (cont…)
The Development Plan Scripts (cont…)
The Development Plan Scripts (cont…)
The Development Plan Scripts (cont…)
The Development Plan Scripts (cont…)
The Development Plan Scripts (cont…)
The Development Plan Scripts
Purpose:
To calculate the planned value and
how to determine the dates when you
will complete each task.

Two forms to complete:


1. TASK form
2. SCHEDULE form
Purpose:
 To summarize the teams’ and each
engineers’ work.
 Provide overall view of each teams’ results
and are the best reference for assessing a
team’s or engineer’s data.

One form to complete:


 SUMP form
Purpose:
 To summarize the data for product size.

One form to complete:


 SUMS form
Tracking the Work (cont…)
 Todetermine the status and quality of the
work.

 In order to track the work, the students


need the following:
 A defined process or plan to follow.
 A time tracking log or tool for recording the
time.
 Some way to tell time.
 Work to do while tracking their time.
Tracking the Work (cont…)
Tracking the Work (cont…)
Purpose:
For engineers to track all the time they
work on the project and that they properly
report this time against the process phases
and the product component.

One form to complete :


 LOGT form
Purpose:
To record defects in the system in order
to track the quality of the product.

One form to complete:


 LOGD form

You might also like