|
Object:
Software Engineering III, Quality Assurance, Maintenance and Evolution,
is an intensive investigation into software quality issues, defect detection
and prevention, reliability engineering, examination of maintenance
issues and configuration management. Software evolution issues, including
planning for evolution, round out the course.
Contact Hours:
3 lecture hours
Topics:
1. SQAS1 Elements of Software Quality Management
- Introduction
- Software quality; what it is and is not
- Examples of good quality
- Examples of bad quality
- The true cost of quality
- The quality lift cycle
- The seven old and new improvement tools
- Implementing the PDCA cycle
- Establishing quality improvement teams
- Instituting quality improvement
- Quality standards
- Case Study
- The future of quality
2. SQAS2 Software Quality Standards
- Why standardize anyway?
- A short history of standards
- The old DoD 2167, 2168 standards
- The SEI capability maturity model (CMM)
- ISO 9126 software quality standard
- ISO 10006 project quality standard
- ISO 12207 software process standard
- ISO 9000 standards suite
- The SPICE project
- Other initiatives
- Case studies
3. SQAS3 Developing a Software Quality Management Plan
- Introduction
- The IEEE SQAP
- Implementing the SQAP
- Selling the SQAP to your organization
- Auditing the SQAP
- Case Study
4. SQAS4 Software Quality Metrics
- Review of Software Quality Issues
- Definition and characteristics of metrics; Measurement Theory 101
- Software quality metrics
- Reviews, Inspections and Walkthroughs
- Testing methodologies
- Product quality metrics
- In-process quality metrics
- Maintenance metrics
- Quality audits
- Case studies of metric programs (Motorola, IBM Rochester)
- Enhancing the metrics program at London Life
- The future
5. SQAS5 Defect Reduction
- Introduction to Reliability Theory
- Classification of defects
- Strategies for removing defects
- Estimation of remaining defects
- Cost effectiveness of defect removal
- Phase-driven defect removal
- Seeding techniques
- Measuring customer satisfaction
- Case studies
6. Reviews, Inspections and Walkthroughs
7. Evolution of Software
- Architecture
- Planning for Evolution
8. Maintenance Issues
- why is it hard?
- maintenance metrics
- motivating maintenance teams
- administrative issues
Textbooks:
- Kan, S., "Software Quality Engineering", PH
Evaluation:
In order to pass the laboratory, a student must obtain a passing grade
in each component. A student who fails any component shall receive a
final grade not greater than 48%. The approximate weights for each component
in shown below. Note that these are maximums; if less than the stated
number is given, the rest of the marks will be pro-rated.
- 20% written assignments (4)
- 30% programming assignments (4)
- 50% final examination
|
