next up previous
Next: A Cyclical Software Engineering Up: Software Engineering Methodologies Previous: A Sequential Software Engineering

The Boehm-Waterfall Software Engineering Methodology

See tables 7.1 and 7.24 starting on page [*].


 
Table 7.23: Survey: Boehm-Waterfall : Part 1
Question Response
Analysis? none..poor..fair..good.. great
Design? none..poor..fair..good.. great
Implementation? none..poor..fair..good.. great
Testing? none..poor..fair..good.. great
Cycles of ADIT? one.. few..several..frequent
Priority? no..yes
Versions? no..yes
Change Order Control? no..yes
Internal Prototype? no..yes
External Prototype? no..yes
Alpha Release? no..yes
Beta Release? no..yes
Duration? short
Effort? little
 


 
Table 7.24: Survey: Boehm-Waterfall: Part 2
Question Response
Did a new introduced requirement ever negatively affect accomplished work? never..seldom..often..frequent
Did an architectural change ever negatively affect accomplished work? never..seldom..often..frequent
Are new features introduced up to product release? never..seldom..often..frequent
Is there a dedicated period of quality assurance before the product is released? no.. yes
 


next up previous
Next: A Cyclical Software Engineering Up: Software Engineering Methodologies Previous: A Sequential Software Engineering
Ronald LeRoi Burback
1998-12-14