1. 5-1 © Prentice Hall, 2004 Chapter 5: Determining Object-Oriented Systems Requirements Object-Oriented Systems Analysis and Design Joey F. George, Dinesh Batra, Joseph S. Valacich, Jeffrey A. Hoffer

2. Chapter 5 5-2 © Prentice Hall, 2004 Chapter Objectives Af ter studying this chapter you should be able to: – Describe options for designing and conducting interviews. – Design, distribute and analyze questionnaires.

3. Chapter 5 5-3 © Prentice Hall, 2004 Chapter Objectives (Continued) Af ter studying this chapter you should be able to: – Compare direct observation and business document analysis – Participate in and help plan Joint Application Design (JAD) sessions.

4. Chapter 5 5-4 © Prentice Hall, 2004 Chapter Objectives (Continued) Af ter studying this chapter you should be able to: – Use prototyping during requirements determination. – Select the appropriate methods to determine requirements. – Understand requirements determination for Internet applications.

5. Chapter 5 5-5 © Prentice Hall, 2004

6. Chapter 5 5-6 © Prentice Hall, 2004 Characteristics for Successful Requirements Determination Impertinence Impartiality Relaxing of constraints Attention to details Reframing

7. Chapter 5 5-7 © Prentice Hall, 2004

8. Chapter 5 5-8 © Prentice Hall, 2004 How to Determine Requirements

9. Chapter 5 5-9 © Prentice Hall, 2004 What Is Interviewing? Dialogue with user or manager to obtain their requirements Two forms: – Open-ended – conversational, questions with no specific answers in mind – Closed-ended – structured, questions with limited range of possible answers

10. Chapter 5 5-10 © Prentice Hall, 2004 How to Conduct Interviews

11. Chapter 5 5-11 © Prentice Hall, 2004 Interview Guide is a document for developing, planning, and conducting an interview.

12. Chapter 5 5-12 © Prentice Hall, 2004 Each question in an interview guide can include both verbal and non-verbal information.

13. Chapter 5 5-13 © Prentice Hall, 2004 What Are Questionnaires? A written set of questions, sometimes with answers to select from, that is distributed to a cross-section of stakeholders in order to obtain system requirements

14. Chapter 5 5-14 © Prentice Hall, 2004 Choosing Questionnaire Respondents Goal: obtain a representative sample of stakeholders Methods: – Convenience – Random – Purposeful – Stratified

15. Chapter 5 5-15 © Prentice Hall, 2004 Designing Questions Avoid ambiguity, especially in closed- ended questions Pretest questions before use Closed-ended questions: true/false, multiple choice, rating, ranking Open-ended questions: for discovering potential probing questions

16. Chapter 5 5-16 © Prentice Hall, 2004 Interviews vs. Questionnaires

17. Chapter 5 5-17 © Prentice Hall, 2004 Other Approaches What is Observation? – Watching users do their jobs – Can provide more accurate information than self-reporting (like questionnaires and interviews) What is Document Analysis? – Review of existing business documents – Can give a historical and “formal” view of system requirements

18. Chapter 5 5-18 © Prentice Hall, 2004 Observations vs. Document Analysis

19. Chapter 5 5-19 © Prentice Hall, 2004 Written work procedure is a business document that formally describes work processes. Provides useful information regarding system functionality and logic.

20. Chapter 5 5-20 © Prentice Hall, 2004 Business form is a document that contains useful information regarding data organizations and possible screen layouts.

21. Chapter 5 5-21 © Prentice Hall, 2004 Other Business Documents Report – Often contains pertinent summary information, and possibly screen layout ideas Existing system documentation – Gives descriptions of use and inner workings of current information system

22. Chapter 5 5-22 © Prentice Hall, 2004 Joint Application Design (JAD) Intensive group-oriented requirements determination technique Team members meet in isolation for an extended period of time Highly focused Resource intensive Started by IBM in 1970s

23. Chapter 5 5-23 © Prentice Hall, 2004 JAD Team Members Session leadercoordinator Usersinformation source Managersinformation source Sponsorchampion Systems analystslisteners Scriberecorder IS stafflisteners

24. Chapter 5 5-24 © Prentice Hall, 2004

25. Chapter 5 5-25 © Prentice Hall, 2004 What Is Prototyping? A repetitive process in which analysts and users build a rudimentary version of an information system based on user feedback Repeated cycle: build, use, evaluate

26. Chapter 5 5-26 © Prentice Hall, 2004

27. Chapter 5 5-27 © Prentice Hall, 2004 When to Use Prototyping Prototyping is good when: – Users are unclear about their requirements. – The system affects a relatively small number of users. – Designs are complex. – Communication between users and analysts needs to be strengthened. – Rapid application development tools are available.

28. Chapter 5 5-28 © Prentice Hall, 2004 Recap After studying this chapter we learned to: – Design and conduct interviews – Design and use questionnaires – Use direct observation and business document analysis – Work in JAD sessions – Use prototyping for requirements determination – Apply requirements determination to a Web application