Fundamentals of Software Engineering
- 1. Personal and Team Process models • The software process is effective only if it is amenable to significant adaption to meet the needs of the project team. • Personal process model: Individual create a process that best fits your needs, and at the same time, meets the broader needs of the team and the organization. • Team process model: The Team itself create its own process, and at the same time meet the narrower needs of individuals and the broader needs of the organisation. “Watts Humphrey” argues that both models are achievable but require hardwork, training and coordination.
- 2. Personal Software Process (PSP) Watts Humphrey suggests that in order to change an ineffective personal process, an individual must move through four phases, each requiring training and careful instrumentation. The PSP • emphasizes personal measurement of the work product that is produced . • emphasizes the resultant quality of the work product. • Makes practitioner responsible for project planning (e.g; estimating and scheduling) • Empowers the practitioner to control the quality of all software work products that are developed.
- 3. Personal Software Process (PSP) defines 5 framework activities • Planning. This activity isolates requirements and develops both size and resource estimates. In addition, a defect estimate (the number of defects projected for the work) is made. All metrics are recorded on worksheets or templates. Finally, development tasks are identified and a project schedule is created. • High-level design. An external specification is created for each component and a component design is created. Prototypes are built when uncertainty exists. All issues are recorded and tracked. 3
- 4. Personal Software Process (PSP) • High-level design review. Formal verification methods (Chapter 21) are applied to uncover errors in the design. Metrics are maintained for all important tasks and work results. • Development. The component level design is refined and reviewed. Code is generated, reviewed, compiled, and tested. Metrics are maintained for all important tasks and work results. • Postmortem. Using measures and metrics collected the effectiveness of the process is determined. (If this is a large amount of data it should be analyzed statistically.) Measures and metrics should provide guidance for modifying the process to improve its effectiveness. 4
- 5. • PSP Stresses the need for each software engineer to identify errors early and as important, to understand the types of errors through a rigorous assessment activity performed on all work products you produce. Personal Software Process (PSP) • However, PSP has not been widely adopted throughout the industry. • PSP is intellectually challenging and demands a level of commitment (by practitioners and managers) that is not always possible to obtain. • Training is relatively lengthy and training costs are high. • The required level of measurement is culturally difficult for many software people.
- 6. Team Software Process (TSP) • Build self-directed teams that plan and track their work, establish goals, and own their processes and plans. These can be pure software teams or integrated product teams (IPT) of three to about 20 engineers. • Show managers how to coach and motivate their teams and how to help them sustain peak performance. • Accelerate software process improvement by making CMM Level 5 behavior normal and expected. – The Capability Maturity Model (CMM), a measure of the effectiveness of a software process, is discussed in Chapter 30. • Provide improvement guidance to high-maturity organizations. • Facilitate university teaching of industrial-grade team skills. 6 The goal of TSP is to build a “self-directed” project team that organizes itself to produce high quality software. Humphrey defines the following objectives for TSP.