Asgkit prog2
Download as DOC, PDF1 like692 views
Program 2 requires students to write a program that counts the size of Program 1 in lines of code (LOC) or an alternative measure. The summary must provide: 1) A single count for the entire program size of Program 1. 2) Size and item counts for each part (e.g. class, function) of Program 1 along with the part name. 3) Test the counting program by using it to count Programs 1 and 2. The document provides instructions, templates, and evaluation criteria for students to plan, develop, test, and review their Program 2 counting application according to the Personal Software Process.
Asgkit prog2
- 1. Assignment Kit for Program 2 __________________________________________________________________________________ __________________________________________________________________________________ __________________________________________________________________________________ __________________________________________________________________________________ __________________________________________________________________________________ PSP Fundamentals The Software Engineering Institute (SEI) is a federally funded research and development center sponsored by the U.S. Department of Defense and operated by Carnegie Mellon University. This material is approved for public release. Distribution limited by the Software Engineering Institute to attendees. Program 2 September 2007 1 © 2007 by Carnegie Mellon University
- 2. PSP Fundamentals Assignment Kit for Program 2 Overview Overview This assignment kit covers the following topics. Section See Page Prerequisites 2 Program 2 requirements 3 Program 2 hints 4 Assignment instructions 5 Guidelines and evaluation criteria 9 PSP1 Grading Checklist 11 Prerequisites Reading • Chapters 3 and 4 Assignments • size counting standard • coding standard Program 2 September 2007 2 © 2007 by Carnegie Mellon University
- 3. Program 2 requirements Program 2 requirements Using PSP1, write a program to count (in LOC) the • total program size • total size of each of the program’s parts (classes, functions, or procedures) • the number of items (or methods) in each part Produce and print • a single count for the entire program • size and item counts for each part together with the part name If LOC is not a suitable size measure for the language you use, see chapter 3 and the following “Hints” section for alternative ways to measure size. Then write program 2 to use those measures. Use the size counting standard and the coding standard defined in your report assignments. Thoroughly test the program. At a minimum, test the program by counting the total program and part sizes in programs 1 and 2. Example output is illustrated in Table 1. In Table 1, consider the word part to be whatever applies for your language: class, function, procedure, and so forth. Program Number Part Name Number of Items Part Size Total Size 1 ABC 3 86 DEF 2 8 GHI 4 92 212 2 … Table 1 Program 2 September 2007 3 © 2007 by Carnegie Mellon University
- 4. Program 2 hints Hints Do not try to write a sophisticated counting program. For LOC counting, follow the counting strategy suggested in Chapter 3, page 48, Size Counters. If the classes, functions, embedded code, or anything else in your programming language is hard to identify and count, consider including special comments to identify such things for your counting program. Remember to modify your R1 counting standard and R2 coding standard to include these comments. You will also have to include such comments in every program, including program 1. For database application or other languages where the LOC measure may not be appropriate, identify the items that you think could provide useful counts. Be as complete as you can while keeping the counting approach simple. A simple sum of the basic countable elements will likely provide as useful a size measure as more sophisticated measures. Program 2 September 2007 4 © 2007 by Carnegie Mellon University
- 5. Assignment instructions Assignment instructions Before starting program 2, review the top-level PSP1 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. PSP1 Process Script Purpose To guide the development of module-level programs Entry Criteria - Problem description - PSP0.1 Project Plan Summary form - Time and Defect Recording logs - Defect Type, Coding, and Size Counting standards - Stopwatch (optional) Step Activities Description 1 Planning - Produce or obtain a requirements statement. - Estimate the added and modified size of this program. - Estimate the required development time. - Enter the plan data in the Project Plan Summary form. - Complete the Time Recording log. 2 Development - Design the program. - Implement the design. - 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 PIP forms - Completed Time and Defect Recording logs Continued on next page Program 2 September 2007 5 © 2007 by Carnegie Mellon University
- 6. Assignment instructions, Continued Planning phase Plan program 2 following the PSP1 planning phase script. PSP1 Planning Script Purpose To guide the PSP planning process Entry Criteria - Problem description - PSP0.1 Project Plan Summary form - Time Recording log Step Activities Description 1 Program Requirements - Produce or obtain a requirements statement for the program. - Ensure that the requirements statement is clear and unambiguous. - Resolve any questions. 2 Size Estimate - Make your best estimate of the added and modified size of this program. - Enter the plan size data in the Project Plan Summary form. 3 Resource Estimate - Make your best estimate of the time required to develop this program. - Enter the plan time data in the Project Plan Summary form. - Using the To Date % from the most recently developed program as a guide, distribute the development time over the planned project phases. (Note: This step is completed by the SEI student workbook.) Exit Criteria - Documented requirements statement - Completed Project Plan Summary form with estimated program size and development time data - Completed Time Recording log Verify that you have met all of the exit criteria for the planning phase, then have an instructor review your plan. After your plan has been reviewed, proceed to the development phase. Continued on next page Program 2 September 2007 6 © 2007 by Carnegie Mellon University
- 7. Assignment instructions, Continued Development phase Develop the program following the PSP1 development phase script. PSP1 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 - 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 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. 3 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. 4 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. Exit Criteria - A thoroughly tested program that conforms to the Coding standard - Completed Time and Defect Recording logs Verify that you have met all of the exit criteria for the development phase, then proceed to the postmortem phase. Continued on next page Program 2 September 2007 7 © 2007 by Carnegie Mellon University
- 8. Assignment instructions, Continued Postmortem phase Conduct the postmortem following the PSP1 postmortem script. PSP1 Postmortem Script Purpose To guide the PSP postmortem process Entry Criteria - Problem description and requirements statement - Project Plan Summary form with program size and development time data - Completed Time and Defect Recording logs - A tested and running program that conforms to the coding and size counting 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. - 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, deleted, modified, reused, total, and new reusable code. (Note: The size of added and modified code is calculated by the SEI student workbook.) - 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 counting standards - 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 PSP1 postmortem phase, then review your assignment. Continued on next page Program 2 September 2007 8 © 2007 by Carnegie Mellon University
- 9. Guidelines and evaluation criteria for program 2 Reviewing your assignment Use the attached grading checklist to check your assignment. Ensure that your assignment is correct before you submit it. Your process report must be • complete • legible • in the specified order Your process data must be • accurate • precise • self-consistent Submitting your assignment When you’ve completed your review, submit your assignment. • .mdb export file from your student workbook • source program listing for programs 1 and 2 • test results • coding standard Suggestions Remember, you should complete this assignment today. Keep your programs simple. You will learn as much from developing small programs as from large ones. If you are not sure about something, ask your instructor for clarification. Software is not a solo business, so you do not have to work alone. - You must, however, produce your own estimates, designs, code, and completed forms and reports. - You may have others review your work, and you may change it as a result. - You should note any help you receive from others in your process report. Log the review time that you and your associates spend, and log the defects found or any changes made. Program 2 September 2007 9 © 2007 by Carnegie Mellon University
- 10. Grading Checklist - PSP 1 Student Program Instructor Grading Data Entry Date Legend Start √ - O.K. End X - resubmit Interrupt Total Assignment Package Comments PSP1 Project Planning Summary Test Report PIP Form Size Estimating Template PROBE Worksheet Time Recording Log Defect Recording Log Source Program Listing Test Results Program and Test Results Comments The program appears to be workable. All required tests have been run. The actual output is correct for each test. Source is compatible with coding standard. Test Report Template Comments Planned and actual results are included for all tests. All information to repeat the tests is provided. Time Log Comments Time data are entered for all process steps. Process steps are sequenced appropriately. Time data are entered against the appropriate process step. Interrupt time is tracked appropriately. Time data are complete and reasonable. Times were recorded as the work was done. Defect Log Comments Every defect has all required data. Defects were injected before removed. Every defect has a fix time. Defects injected in compile and test have fix numbers. Defects are adequately described. Defect types are consistent with description. Defect types are consistent with phase injected. Defect types are assigned consistently. PSP1 GC January 2006 11 © 2006 by Carnegie Mellon University
- 11. Grading Checklist - PSP 1 Size Estimating Template & PROBE Worksheet Comments Plan and actual size data are complete and reasonable. The reuse and base measures are used correctly. A suitable number of new parts are identified. The item sizes are balanced around medium. The relative size data values are correct and based on historical data The appropriate PROBE method has been selected. PIP Form Comments The PIP form is completed. The entries show insight and thought. Planning Summary Comments Planned total time has been entered correctly. Planned and actual size data are entered correctly. Planned and actual size/hour data are reasonable. Consistency Checks Comments Defects removed are consistent with compile and test phase time and program size. Total compile defect fix times are less than compile time. Total test defect fix times are less than test time. Defect dates & phases are consistent with the time log. Planning summary is consistent with the time log. Planning summary is consistent with the defect log. Planning Summary values are consistent with the size estimating template values. Actual Added on planning summary close to and no less than actual BA+PA on size estimating template. General Comments Followed the defined process. Complete, consistent and accurate process data collected. The student did his or her own work. Historical data are used in planning the work. PSP1 GC January 2006 12 © 2006 by Carnegie Mellon University