Docsity
Docsity
Prepare for your exams
Prepare for your exams

Study with the several resources on Docsity

Earn points to download
Earn points to download

Earn points by helping other students or get them with a premium plan

Guidelines and tips
Guidelines and tips
Sell on Docsity
Sell on Docsity
Docsity AI
Docsity AI
Log inSign up

Prepare for your exams

Study with the several resources on Docsity

Find documents

Prepare for your exams with the study notes shared by other students like you on Docsity

Search for your university

Find the specific documents for your university's exams

Docsity AINEW

Summarize your documents, ask them questions, convert them into quizzes and concept maps

Explore questions

Clear up your doubts by reading the answers to questions asked by your fellow students

Earn points to download

Earn points by helping other students or get them with a premium plan

Share documents
download point icon20 Points

For each uploaded document

Answer questions
download point icon5 Points

For each given answer (max 1 per day)

All the ways to get free points
Get points immediately

Choose a premium plan with all the points you need

Study Opportunities

Choose your next study program

Get in touch with the best universities in the world. Search through thousands of universities and official partners

Community

Ask the community

Ask the community for help and clear up your study doubts

Free resources

Our save-the-student-ebooks!

Download our free guides on studying techniques, anxiety management strategies, and thesis advice from Docsity tutors

PSP2 Development Script, Codes and Instructions-Software Quality-Handout, Exercises of Software Development Methodologies

Biju Patnaik University of TechnologySoftware Development Methodologies

This handout is part of Software Quality course. It was provided by Dr. Raja Sahay at Biju Patnaik University of Technology, Rourkela. It includes: Development, Script, Entry, Criteria, Requirements, Defect, Type, Design, Code, Review, Compile

Typology: Exercises

2011/2012

Uploaded on 07/09/2012

chandu
chandu 🇮🇳

4

(4)

44 documents

1 / 10

Toggle sidebar

This page cannot be seen from the preview

Don't miss anything!

bg1
PSP2 Development Script
Purpose To guide the development of small programs
Entry Criteria - Requirements statement
- Project Plan Summary form with estimated program size and
development time
- For projects lasting several days or more, completed Task Planning and
Schedule Planning templates
- Time and Defect Recording logs
- Defect Type standard and Coding standard
Step Activities Description
1 Design - Review the requirements and produce a design to meet them.
- Record in the Defect Recording log any requirements defects found.
- Record time in the Time Recording log.
2 Design
Review - Follow the Design Review script and checklist to review the design.
- Fix all defects found.
- Record defects in the Defect Recording log.
- Record time in the Time Recording log.
3 Code - Implement the design following the Coding standard.
- Record in the Defect Recording log any requirements or design defects
found.
- Record time in the Time Recording log.
4 Code
Review - Follow the Code Review script and checklist to review the code.
- Fix all defects found.
- Record defects in the Defect Recording log.
- Record time in the Time Recording log.
5 Compile - Compile the program until there are no compile errors.
- Fix all defects found.
- Record defects in the Defect Recording log.
- Record time in the Time Recording log.
6 Test - Test until all tests run without error.
- Fix all defects found.
- Record defects in the Defect Recording log.
- Record time in the Time Recording log.
- Complete a Test Report template on the tests conducted and the results
obtained.
Exit Criteria - A thoroughly tested program that conforms to the Coding standard
- Completed Design Review and Code Review checklists
- Completed Test Report template
- Completed Time and Defect Recording logs
docsity.com
pf3
pf4
pf5
pf8
pf9
pfa

Partial preview of the text

Download PSP2 Development Script, Codes and Instructions-Software Quality-Handout and more Exercises Software Development Methodologies in PDF only on Docsity!

PSP2 Development Script

Purpose To guide the development of small programs Entry Criteria - Requirements statement

  • Project Plan Summary form with estimated program size and development time
  • For projects lasting several days or more, completed Task Planning and Schedule Planning templates
  • Time and Defect Recording logs
  • Defect Type standard and Coding standard

Step Activities Description 1 Design - Review the requirements and produce a design to meet them.

  • Record in the Defect Recording log any requirements defects found.
  • Record time in the Time Recording log. 2 Design Review
  • Follow the Design Review script and checklist to review the design.
  • Fix all defects found.
  • Record defects in the Defect Recording log.
  • Record time in the Time Recording log. 3 Code - Implement the design following the Coding standard.
  • Record in the Defect Recording log any requirements or design defects found.
  • Record time in the Time Recording log. 4 Code Review
  • Follow the Code Review script and checklist to review the code.
  • Fix all defects found.
  • Record defects in the Defect Recording log.
  • Record time in the Time Recording log. 5 Compile - Compile the program until there are no compile errors.
  • Fix all defects found.
  • Record defects in the Defect Recording log.
  • Record time in the Time Recording log. 6 Test - Test until all tests run without error.
  • Fix all defects found.
  • Record defects in the Defect Recording log.
  • Record time in the Time Recording log.
  • Complete a Test Report template on the tests conducted and the results obtained.

Exit Criteria - A thoroughly tested program that conforms to the Coding standard

  • Completed Design Review and Code Review checklists
  • Completed Test Report template
  • Completed Time and Defect Recording logs

PSP2 Design Review Script

Purpose To guide you in reviewing detailed designs Entry Criteria - Completed program design

  • Design Review checklist
  • Design standard
  • Defect Type standard
  • Time and Defect Recording logs General Where the design was previously verified, check that the analyses
  • covered all of the design
  • were updated for all design changes
  • are correct
  • are clear and complete

Step Activities Description 1 Preparation Examine the program and checklist and decide on a review strategy. 2 Review - Follow the Design Review checklist.

  • Review the entire program for each checklist category; do not try to review for more than one category at a time!
  • Check off each item as you complete it.
  • Complete a separate checklist for each product or product segment reviewed. 3 Fix Check - Check each defect fix for correctness.
  • Re-review all changes.
  • Record any fix defects as new defects and, where you know the defective defect number, enter it in the fix defect space.

Exit Criteria - A fully reviewed detailed design

  • One or more Design Review checklists for every design reviewed
  • All identified defects fixed and all fixes checked
  • Completed Time and Defect Recording logs

PSP2 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 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 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

PSP2 Project Plan Summary

Student Date Program Program # Instructor Language

Summary Plan Actual To Date Size/Hour Planned Time Actual Time CPI (Cost-Performance Index) (Planned/Actual) % Reuse % New Reusable Test Defects/KLOC or equivalent Total Defects/KLOC or equivalent Yield %

Program Size Plan Actual To Date Base (B) (Measured) (Measured) Deleted (D) (Estimated) (Counted) Modified (M) (Estimated) (Counted) Added (A) (A+M − M) (T − B + D − R) Reused (R) (Estimated) (Counted) Added and Modified (A+M) (Projected) (A + M) Total Size (T) (A+M + B − M − D + R) (Measured) Total New Reusable

Estimated Proxy Size (E)

Time in Phase (min.) Plan Actual To Date To Date % Planning Design Design Review Code Code Review Compile Test Postmortem Total

(continued)

PSP2 Plan Summary Instructions

Purpose To hold the plan and actual data for programs or program parts General - Use the most appropriate size measure, either LOC or element count.

  • “To Date” is the total actual to-date values for all products developed.
  • A part could be a module, component, product, or system.

Header -^ Enter your name and the date.

  • Enter the program name and number.
  • Enter the instructor’s name and the programming language you are using. Summary -^ Enter the added and modified size per hour planned, actual, and to-date.
  • Enter the planned and actual times for this program and prior programs.
  • For planned time to date, use the sum of the current planned time and the to-date planned time for the most recent prior program.
  • CPI = (To Date Planned Time)/(To Date Actual Time).
  • Reused % is reused size as a percentage of total program size.
  • New Reusable % is new reusable size as a percentage of added and modified size.
  • Enter the test and total defects/KLOC or other appropriate measure.
  • Enter the planned, actual, and to-date yield before compile. Program Size - Enter plan base, deleted, modified, reused, new reusable, and total size from the Size Estimating template.
  • Enter the plan added and modified size value (A+M) from projected added and modified size (P) on the Size Estimating template.
  • Calculate plan added size as A+M – M.
  • Enter estimated proxy size (E) from the Size Estimating template.
  • Enter actual base, deleted, modified, reused, total, and new reusable size from the Size Estimating template.
  • Calculate actual added size as T-B+D-R and actual added and modified size as A+M.
  • Enter to-date reused, added and modified, total, and new reusable size. Time in Phase - Enter plan total time in phase from the estimated total development time on the Size Estimating template.
  • Distribute the estimated total time across the development phases according to the To Date % for the most recently developed program.
  • Enter the actual time by phase and the total time.
  • To Date: Enter the sum of the actual times for this program plus the to- date times from the most recently developed program.
  • To Date %: Enter the percentage of to-date time in each phase. (continued)

PSP2 Plan Summary Instructions (continued)

Defects Injected - Enter the total estimated defects injected.

  • Distribute the estimated total defects across the development phases according to the To Date % for the most recently developed program.
  • Enter the actual defects by phase and the total actual defects.
  • To Date: Enter the sum of the actual defects injected by phase and the to- date values for the most recent previously developed program.
  • To Date %: Enter the percentage of the to-date defects injected by phase. Defects Removed - Enter the estimated total defects removed.
  • Distribute the estimated total defects across the development phases according to the To Date % for the most recently developed program.
  • To Date: Enter the actual defects removed by phase plus the to-date values for the most recent previously developed program.
  • To Date %: Enter the percentage of the to-date defects removed by phase.
  • After development, record any defects subsequently found during program testing, use, reuse, or modification. Defect-Removal Efficiency
  • Calculate and enter the defects removed per hour in design review, code review, compile, and test.
  • For DRL, take the ratio of the review and compile rates with test.
  • Where there were no test defects, use the to-date test defect/hour value.

Code Review Checklist

Student Date Program Program # Instructor Language C++

Purpose To guide you in conducting an effective code review General - Review the entire program for each checklist category; do not attempt to review for more than one category at a time!

  • As you complete each review step, check off that item in the box at the right.
  • Complete the checklist for one program or program unit before reviewing the next.

Complete Verify that the code covers all of the design. Includes Verify that the includes are complete. Initialization Check variable and parameter initialization.

  • at program initiation
  • at start of every loop
  • at class/function/procedure entry Calls Check function call formats.
  • pointers
  • parameters
  • use of ‘&’ Names Check name spelling and use.
  • Is it consistent?
  • Is it within the declared scope?
  • Do all structures and classes use ‘.’ reference? Strings Check that all strings are
  • identified by pointers
  • terminated by NULL Pointers Check that all
  • pointers are initialized NULL
  • pointers are deleted only after new
  • new pointers are always deleted after use Output Format Check the output format.
  • Line stepping is proper.
  • Spacing is proper. () Pairs Ensure that () are proper and matched. Logic Operators - Verify the proper use of ==, =, ||, and so on.
  • Check every logic function for (). Line-by-line check Check every line of code for
  • instruction syntax
  • proper punctuation Standards Ensure that the code conforms to the coding standards. File Open and Close Verify that all files are
  • properly declared
  • opened
  • closed