TMP3413 Software Engineering Lab Lab 01: TSPi Tool Support

Lecture Overview  Objectives  Project Planning and TSPi Planning Overview  TSPi Planning and Tool Support  project and team information  estimating sizes  producing TASK and SCHEDULE plans  producing a quality plan  producing a summary plan  tracking the plan  Software Configuration Management

Objectives  After completing this tutorial, you will be able to  install the TSP tool  use the TSP tool to enter project information  use the TSP tool to produce team plans  use the TSP tool to record and track project progress

Project Planning  Effective planning is a critical element in the success of a software project.  The more complex the project, the more important good plans are to the project’s success.  Planning activities consist of  project estimation  establishing project task and schedule plans  project plan tracking  Plans are also needed to support  risk management  configuration management

TSPi Planning Overview  TSPi introduces students to a simple planning system that is appropriate for a project the size and duration of a semester- long software engineering course.  Most of the planning activities are incorporated in an early phase of the process.  TSPi planning is supported by  a defined process  forms and instructions  a planning and tracking tool  Before we discuss TSPi planning, we will first take a more detailed look at the structure, content, and schedule of the TSPi.

TSPi Planning Steps/Forms Produce Conceptual Design Develop the Strategy Make Size Estimates Produce Team Plan Produce Quality Plan Produce Final Team Plan Balance Team Workload Make Team Member Plans Make Personal Plans STRAT SUMS SCHEDULE SUMQ TASK SCHEDULE TASK TASK SCHEDULE TASK SCHEDULE SUMQ SUMS SUMP

TSPi Planning  The Planning Manager leads the team through a series of steps that produce the following:  a team task and schedule plan  a team quality plan  a plan for each individual team member  a team summary plan  Throughout the project the Planning Manager is responsible for tracking and recording plan progress.  An Excel spreadsheet tool provides templates of all the required planning forms.

TSPi Planning Forms

Tool Setup  Load the tool “tspi workbook xls” from the CD  Open the tool using Microsoft Excel.  Select the “TSPi Instructions” tab.

Support Tool Instructions

Project and Team Information  Enter project information on PROJECT sheet.  project name, start date, instructor, cycle number  select “use Time log” and “use Defect log”  Enter team member information on TEAM sheet.  team member names, initials, phone numbers, addresses, and team member filenames  Enter team role information on ROLES sheet.

Project Entries 1

Project Entries 2 The project’s start date should be a Monday. Each of these should be checked

Team Entries

Role Entries

Size Estimates  Estimate part sizes using the SUMS sheet.  List product parts to be developed in Cycle 1.  Enter the owner and size measure for each part.  Estimate part sizes and enter them.  for Cycle 1, enter size estimates under “added” column  each part should be designated as part of a SYSTEM

Size Entries 1

Size Entries 2

Task and Schedule Planning Overview  With the TASK sheet  use the “Generate Task List” button to generate a default task list  modify the default list as appropriate and estimate sizes and times for each task  assign portions of tasks to individual engineers  determine total time required for the project cycle  With the SCHEDULE sheet  Plan sufficient hours to accomplish all tasks  With the TASK sheet  schedule each engineers tasks for each week of the project  balance engineer task loads

Task Planning  Estimate engineer tasks using the TASK sheet.  Produce the list of Cycle 1 tasks that must be completed.  your task list should cover any and all time spent on the project  include all major activities and enough detail so that weekly work can be allocated  Estimate time to complete each task.  allocate task time to individual team members  enter task time into the appropriate role columns

Task Entries (pass 1)

Schedule Planning (pass 1)  Develop the project schedule using SCHEDULE sheet.  The start date for each week of the schedule will be generated automatically.  Estimate and enter the Planned Hours available for the team to work on the project each week. (This should be adjusted to the overall schedule for the course and the due dates/milestones for project deliverables.)  Use the Update Task Plan command to compute the Planned Values and the completion date for each task.

Schedule Entries

Task Planning  After completing the schedule (SCHEDULE sheet)  Use the Update Task Plan command to compute:  the Planned Value for each task  planned hours for a task X 100  total planned hours  the Planned Week and Date for completion of the task  Review the TASK plan to ensure the following:  the task list covers all Cycle 1 work  the task list is not too general or too detailed  the effort required of each engineer is reasonably balanced on a weekly basis

Task Entries (pass 2)

Schedule Planning (pass 2)  Review the project schedule to ensure the following:  it conforms to the class schedule and any established milestones  a reasonable amount of time is planned for completion of each task  tasks are scheduled in the proper sequence  the schedule plan allows sufficient hours to complete all of the project tasks

Quality Planning 1  Determine and enter quality planning information on the SUMQ sheet.  Use the “Transfer Phase Yield Guidelines to Plan” and “Transfer Defect Injection Rate Guidelines to Plan” buttons to enter default quality criteria into the SUMQ form  the Percent Defect Free components in each of the defect detection phases  the defect removal yields in various phases (Phase Yields)  the rate at which defects are injected in various phases (Defect Injection Rates)

SUMQ Entries

Quality Planning 2  Review the Summary Plan and adjust parameters on other sheets as necessary. For example:  Are the defects/KLOC within range of ?  Is the ratio of HLD inspection time to HLD time > 0.5?

Quality Plan Entries 1

Quality Plan Entries 2

Individual Plans  Each team member completes personal Task and Schedule Plans.  the tasks, effort, and planned completion dates should conform to the team task and schedule plans  some assigned tasks may be subdivided into two or more subtasks  The workload should be reasonably balanced.  Individual and team plans should be adjusted as necessary.  Use the “Update Task and Schedule” button to update individual spreadsheets before they are recombined for the team.

Individual Plan Entries

Individual Schedule Entries

Tracking Team and Individual Plans  Team status is recorded in the team’s Task Plan.  enables team to track performance against its plan  requires accurate data for each team member  Team member status is recorded in each team member’s Task Plan.  enables an individual to track performance against his plan  requires that each team member record carefully  time  size  defects

Recording Data 1  LOGT for recording time  LOGD for recording defects  Planning Manager may determine whether team members use the tool. If not, then each team member must provide a paper copy of LOGT and LOGD to the Planning Manager on a weekly basis.

LOGT Entries

LOGD Entries

Recording Data 2  Measure and Record Sizes (SUMS)  Record Task Completion (TASK)  When a task is completed, record the date on TASK form.  The Earned Value (EV) of the task is automatically recorded  Forms such as SUMQ, and SUMP are updated when the “Update” button on the PROJECT form is pressed.  The TSPi tool provides various graphs that give tracking information and support planning analysis and adjustment.

Task Entries

SUMS Entries Recorded by the owner of the assembly

WEEK Summary

Tracking Planned vs. Actual Time

Tracking Earned Value

Configuration Management  Change is an inevitable part of software development.  Confusion, and even chaos, can arise if change is not managed in a disciplined and coordinated manner.  Software Configuration Management (SCM) is the activity concerned with identifying, organizing, and controlling change to software (and its associated documents) during development.

Reason for Change  Software is developed in an evolutionary/incremental manner.  Defects are found in software reviews.  Changes occur in customer requirements.  Changes occur in project resources (such as budgetary or schedule constraints, team organization).

SCM Objectives  The purpose of SCM is to identify the configuration of the system at discrete points of time so that changes to the configuration can be made in a systematic, controlled, and documented manner.  SCM has the goal of maintaining the integrity and traceability of the software system throughout its life-cycle.

SCM Identification  The first step in identification is the labeling of the software configuration items.  A software configuration item (SCI) is an elementary software development entity that is part of a configuration. It includes:  Project Plan  Requirements Specification  Design Specification  Source Code Listing  Test Specification  User Manual  Standards and Processes

SCM Control  Change control is the process used for managing changes to software. This process includes:  change requests (developers/users/customers)  analysis of requests  CCR (Configuration Change Request)  Configuration Control Board  evaluate CCR  approve/disapprove CCR  forward for disposition  making changes (or archive CCR)  document changes  Version control uses procedures and tools to manage different versions of SCIs that are created during development.

SCM Plan  In the strategy phase each team develops and documents a configuration management plan that includes the following:  a list of the items that will be part of the configuration/change control system (e.g, strategy, plan, SRS, etc.)  a description of how configuration items will be identified and maintained  the change control procedure for processing changes to configuration items (change approval procedure, required documentation)  Appendix B of the text book contains a discussion of SCM.

Risk Management Risk: a likely event that would have negative consequences if it occurred Risk Management activities risk assessment risk identification risk analysis risk control risk management plan Teams should assess project risks and think about how they might be addressed or mitigated.

Summary  The planning phase has a well-defined sequence of activities and deliverables.  It can be supported by a tool that is based on spreadsheet software.  The SCM plan helps manage change in an efficient and effective manner.