Page 65 -

50

Alavi (1984); Boehm, Gray, and Seewaldt (1984); Deephouse et al. (1995); Mahmood (1987); Naumann and Jenkins (1982); Necco, Alavi (1984); Boehm, Gray, and Seewaldt (1984); Gordon and Bieman (1993, 1995); Mahmood (1987); Naumann and Jenkins (1982); Necco, Gordon, and Tsai (1987) Baskerville and Pries-Heje (2004); Boehm, Gray, and Seewaldt (1984); Gordon and Bieman (1995); Naumann and Jenkins (1982); Necco, G

Source Gordon, and Tsai (1987) (2004)

Learn about requirements; support communication and problem Greater user involvement; better user satisfaction; ease of use; Shorten lead times for projects and/or less effort; designer Positively related to higher system performance; more maintainable Less functional systems, with potentially less coherent designs; “negotiable” quality requirements Prototyping must be combined with other factors, such

Conclusion solving greater system use satisfaction code

Alavi (1984); Basili and Turner (1975); Beck (2002); Boehm (1981); Brooks (1995); Cockburn (2002); Davis (1982); Floyd (1984); Keen and Scott Morton (1978); Larman and Basili (2003); McCracken and Jackson (1982) Hardgrave, Wilson, and Eastman (1999); Larman and Basili (2003) Basili and Turner (1975); Beck (2002); Boehm (1988); Brooks (1987); Cockburn (2002); Larman (2004); Larman and Basili (2003); Lyytine

Testing the Promise of “Iterative Development”

Supported? Yes Supported? Yes Supported? Yes Stage (1995) Supported? Mixed Eastman (1999) Not supported Supported? Yes

Source Supported (2002)

Promise of iterative development 1. Supports mutual learning between users and developers Learning about the problem and solution; addresses requirements uncertainty; more realistic validation of requirements; demonstrates 2. Improves user-related Increase participation; more successful system use 3. Improves design process Software developed more quickly; designers more productive; projects cost less; 4. Imp

Table 4.4 technical feasibility outcomes reduce risk innovativeness practices formal structure