L6-b - S o m e p r i n c i p l e s to c o n s i d e r b e...

Info iconThis preview shows pages 1–5. Sign up to view the full content.

View Full Document Right Arrow Icon
www.infotech.monash.edu.au 1 Some principles to consider before starting ‘Get the Owners and Users Involved’ • ‘Use a Problem-Solving Approach’ • ‘Establish Phases and Activities’ • ‘Establish Standards for Consistent Development and Documentation’ • ‘Justify Systems as Capital Investments’ • ‘Don’t Be Afraid to Cancel or Revise Scope’ • ‘Divide and Conquer’ • ‘Design Systems for Growth and Change’ J. Whitten & L. Bentley (1998) . Fourth Edition. Boston: Irwin/McGraw-Hill, pp.73-77.
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
www.infotech.monash.edu.au 2 ‘Get the Owners and Users Involved’ ‘Although analysts and programmers work hard to create technologically impressive solutions, those solutions often backfire because they don’t address the real organization problems or they introduce new organization or technical problems’ (ibid, p.73)
Background image of page 2
www.infotech.monash.edu.au 3 ‘Use a Problem-Solving Approach’ If not, there is a risk of 1. ‘solving the wrong problem’ 2. ‘incorrectly solving the problem’ 3. ‘picking the wrong solution’ (ibid, p.74)
Background image of page 3

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
www.infotech.monash.edu.au
Background image of page 4
Image of page 5
This is the end of the preview. Sign up to access the rest of the document.

This note was uploaded on 08/15/2010 for the course FIT 1003 taught by Professor Yeap during the Three '10 term at Monash.

Page1 / 11

L6-b - S o m e p r i n c i p l e s to c o n s i d e r b e...

This preview shows document pages 1 - 5. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online