Personal Software Process (PSP) for Engineers: Part I
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 EngineeringInstitute to attendees.
Personal Software Process for Engineers: Part I
Assignment Kit for Program 2
Overview This assignment kit covers the following topics.
Section See Page
Program 2 requirements 3
Program 2 hints 4
Assignment instructions 5
Guidelines and evaluation criteria 10
• Chapters 3 and 4
• size countingstandard
• coding standard
Program 2 requirements
Program 2 requirements Using PSP0.1, 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 thepart 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 andpart 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
Program 2 hints
Hints Do not try to write a sophisticated countingprogram.
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 includethese 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 usefula size measure as more sophisticated measures.
Assignment instructions Before starting program 2, review the top-level PSP0.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.
PSP0.1 Process Script
Purpose To guide the development ofmodule-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....