Assignment 4 - Personal Software Process - Fall 2005 | CS 350, Assignments of Software Engineering

Download Assignment 4 - Personal Software Process - Fall 2005 | CS 350 and more Assignments Software Engineering in PDF only on Docsity!

CS 350: Assignment Kit for

Program 4

Fall 2005

Version 1 (subject to change

Personal Software Process

Assignment Kit for Program 4

Overview

Overview This assignment kit covers the following topics.

Section See Page

Prerequisites 2

Program 4 requirements 3

Search algorithm 4

Assignment instructions 5

Guidelines and evaluation criteria 14

Prerequisites Reading

• Chapters 10 and 11

Search algorithm

Finding the

value of x

Find the value of x for which integrating the t function from 0 to x gives a result

of p.

• Start with a trial value for upper limit of 1 and calculate the value of the

integration.

• Compare it to the desired value.
  • if the result of the integration is too low, pick a larger trial upper limit
  • if the result of the integration is too high, pick a smaller trial upper limit

Make successive trial integrations until the value of the integration is within an

acceptable error, say 0.00001.

One way to make this calculation is as follows.

Step Action

1 Start with a trial value of x (for example, 1.0).

2. Make an initial integral and test to see if it gives a proper value; if

not, continue.

3. If it is too low, add d = 0.5 to trial x.

4. If it is too high, subtract d = 0.5 from trial x.

5. Integrate again and test if the result is within an acceptable error; if

not, continue.

6. If too low, adjust d ; add d to trial x.

7. If too high, adjust d ; subtract d from trial x.

8. Recycle at 5.

The rules for adjusting d are these.

1. As long as the tests for the error of the result give the same sign of the error,

leave d unchanged.

2. Whenever the sign of the error changes, divide d by 2.

Note that this method of adjusting d could result in a trial value of x = 0.

To guard against a problem with Simpson’s method, ensure that the program will

handle a 0 value of the function being integrated.

Assignment instructions

Assignment

instructions

Before starting program 4, review the top-level PSP2.1 process script below to

ensure that you understand the “big picture” before you begin. Also, ensure that

you have all of the required inputs before you begin the planning phase.

PSP2.1 Process Script Purpose To guide the development of module-level programs Entry Criteria - Problem description

• PSP2.1 Project Plan Summary form
• Size Estimating template
• Historical size and time data (estimated and actual)
• Time and Defect Recording logs
• Defect Type, Coding, and Size Measurement standards
• Stopwatch (optional) Step Activities Description 1 Planning - Produce or obtain a requirements statement.
• Use the PROBE method to estimate the added and modified size.
• Omit computing the size prediction interval for now.
• Complete the Size Estimating template.
• Use the PROBE method to estimate the required development time.
• Omit computing the time prediction interval for now.
• Complete a Task Planning template.
• Complete a Schedule Planning template.
• Enter the plan data in the Project Plan Summary form.
• Complete the Time Recording log. 2 Development - Design the program. - Omit the use of design templates but provide a design in a format of your choice. Pseudo-code is acceptable
• Review the design, and fix and log all defects found.
• Implement the design.
• Review the code, and fix and log all defects found.
• Compile the program, and fix and log all defects found.
• Test the program, and fix and log all defects found.
• Complete the Time Recording log. 3 Postmortem Complete the Project Plan Summary form with actual time, defect, and size data. Exit Criteria - A thoroughly tested program
• Completed Project Plan Summary form with estimated and actual data
• Completed Size Estimating and Task and Schedule Planning templates
• Completed Design
• Completed Test Report template
• Completed PIP forms
• Completed Time and Defect Recording logs Continued on next page

Assignment instructions, Continued

Use the PROBE method to create size and resource estimates.

Purpose To guide the size and time estimating process using the PROBE method Entry Criteria - Requirements statement

• Size Estimating template and instructions
• Size per item data for part types
• Time Recording log
• Historical size and time data General - This script assumes that you are using added and modified size data as the size-accounting types for making size and time estimates.
• If you choose some other size-accounting types, replace every “added and modified” in this script with the size-accounting types of your choice. Step Activities Description 1 Conceptual Design Review the requirements and produce a conceptual design. 2 Parts Additions Follow the Size Estimating Template instructions to estimate the parts additions and the new reusable parts sizes. 3 Base Parts and Reused Parts
• For the base program, estimate the size of the base, deleted, modified, and added code.
• Measure and/or estimate the side of the parts to be reused. 4 Size Estimating Procedure
• If you have sufficient estimated proxy size and actual added and modified size data (three or more points that correlate), use procedure 4A.
• If you do not have sufficient estimated data but have sufficient plan added and modified and actual added and modified size data (three or more points that correlate), use procedure 4B.
• If you have insufficient data or they do not correlate, use procedure 4C.
• If you have no historical data, use procedure 4D. 4A Size Estimating Procedure 4A
• Using the linear-regression method, calculate the! 0 and! 1 parameters from the estimated proxy size and actual added and modified size data.
• If the absolute value of! 0 is not near 0 (less than about 25% of the

expected size of the new program), or! 1 is not near 1.0 (between about

0.5 and 2.0), use procedure 4B. 4B Size Estimating Procedure 4B

• Using the linear-regression method, calculate the! 0 and! 1 parameters from the plan added and modified size and actual added and modified size data.
• If the absolute value of! 0 is not near 0 (less than about 25% of the

expected size of the new program), or! 1 is not near 1.0 (between about

0.5 and 2.0), use procedure 4C. 4C Size Estimating Procedure 4C If you have any data on plan added and modified size and actual added and

modified size, set! 0 = 0 and! 1 = (actual total added and modified size to

date/plan total added and modified size to date). 4D Size Estimating Procedure 4D If you have no historical data, use your judgment to estimate added and modified size.

(continued)

Continued on next page

Assignment instructions, Continued

PROBE Estimating Script (Continued) Step Activities Description 5 Time Estimating Procedure

• If you have sufficient estimated proxy size and actual development time data (three or more points that correlate), use procedure 5A.
• If you do not have sufficient estimated size data but have sufficient plan added and modified size and actual development time data (three or more points that correlate), use procedure 5B.
• If you have insufficient data or they do not correlate, use procedure 5C.
• If you have no historical data, use procedure 5D. 5A Time Estimating Procedure 5A
• Using the linear-regression method, calculate the! 0 and! 1 parameters from the estimated proxy size and actual total development time data.
• If! 0 is not near 0 (substantially smaller than the expected development

time for the new program), or! 1 is not within 50% of 1/(historical

productivity), use procedure 5B. 5B Time Estimating Procedure 5B

• Using the linear-regression method, calculate the! 0 and! 1 regression parameters from the plan added and modified size and actual total development time data.
• If! 0 is not near 0 (substantially smaller than the expected development

time for the new program), or! 1 is not within 50% of 1/(historical

productivity), use procedure 5C. 5C Time Estimating Procedure 5C

• If you have data on estimated – added and modified size and actual

development time, set! 0 = 0 and! 1 = (actual total development time to

date/estimated – total added and modified size to date).

• If you have data on plan – added and modified size and actual

development time, set! 0 = 0 and! 1 = (actual total development time to

date/plan total added and modified size to date).

• If you only have actual time and size data, set! 0 = 0 and! 1 = (actual total development time to date/actual total added and modified size to date). 5D Time Estimating Procedure 5D If you have no historical data, use your judgment to estimate the development time from the estimated added and modified size. 6 Time and Size Prediction Intervals
• If you used regression method A or B, calculate the 70% prediction intervals for the time and size estimates.
• If you did not use the regression method or do not know how to calculate the prediction interval, calculate the minimum and maximum development time estimate limits from your historical maximum and minimum productivity for the programs written to date. Exit Criteria - Completed estimated and actual entries for all pertinent size categories
• Completed PROBE Calculation Worksheet with size and time entries
• Plan and actual values entered on the Project Plan Summary Continued on next page

Assignment instructions, Continued

Assignment instructions, Continued

Postmortem

phase

Conduct the postmortem following the PSP2.1 postmortem script.

PSP2.1 Postmortem Script Purpose To guide the PSP postmortem process Entry Criteria - Problem description and requirements statement

• Project Plan Summary form with program size, development time, and defect data
• For projects lasting several days or more, completed Task Planning and Schedule Planning templates
• Completed Test Report template
• Completed Design templates
• Completed Design Review and Code Review checklists
• Completed Time and Defect Recording logs
• A tested and running program that conforms to the coding and size measurement standards Step Activities Description 1 Defect Recording - Review the Project Plan Summary to verify that all of the defects found in each phase were recorded.
• Using your best recollection, record any omitted defects. 2 Defect Data Consistency
• Check that the data on every defect in the Defect Recording log are accurate and complete.
• Verify that the numbers of defects injected and removed per phase are reasonable and correct.
• Determine the process yield and verify that the value is reasonable and correct.
• Using your best recollection, correct any missing or incorrect defect data. 3 Size - Count the size of the completed program.
• Determine the size of the base, reused, deleted, modified, added, total, added and modified, and new reusable code.
• Enter these data in the Project Plan Summary form. 4 Time - Review the completed Time Recording log for errors or omissions.
• Using your best recollection, correct any missing or incomplete time data. Exit Criteria - A thoroughly tested program that conforms to the coding and size measurement standards
• Completed Design templates
• Completed Design Review and Code Review checklists
• Completed Test Report template
• Completed Project Plan Summary form
• Completed PIP forms describing process problems, improvement suggestions, and lessons learned
• Completed Time and Defect Recording logs

Verify that you have met all of the exit criteria for the PSP2.1 postmortem phase, then

submit your assignment.

Continued on next page

Assignment instructions, Continued

Submitting your

assignment

When you’ve completed the postmortem phase, submit your assignment

package, source code, and test results to the instructor.

The order for the assignment package is

• PSP2.1 Project Plan Summary form
• Test Report template
• PIP form
• Size Estimating template
• PROBE Calculation worksheet
• Time Recording log
• Defect Recording log
• source program listing