1. 1 Chapter Objectives  Describe systems analysis phase activities and the end product of the systems analysis phase  Explain joint application development (JAD) and rapid application development (RAD)  Understand how systems analysts use a functional decomposition diagram (FDD)  Describe the Unified Modeling Language (UML) and explain use case diagrams and sequence diagrams

2. 2 Chapter Objectives  List and describe system requirements, including outputs, inputs, processes, performance, and controls  Explain the importance of scalability in system design  Use fact-finding techniques, including interviews, documentation review, observation, questionnaires, sampling, and research

3. 3 Chapter Objectives  Define total cost of ownership (TCO) and explain the concept  Conduct a successful interview  Develop effective documentation methods to use during systems development

4. 4 Systems Analysis Phase Overview  The overall objective is to understand the proposed project, ensure that it will support business requirements, and build a solid foundation for system development  You use a models and other documentation tools to visualize and describe the proposed system

5. 5 Systems Analysis Phase Overview  Systems Analysis Activities – Requirements modeling Requirements modeling Outputs Inputs Processes Performance Security Figure 3-2

6. 6 Systems Analysis Phase Overview  Systems Analysis Activities – Data and process modeling – Development Strategies System requirements document

7. 7 Systems Analysis Phase Overview  Systems Analysis Skills – Analytical skills Analytical skills – Interpersonal skills Interpersonal skills  Team-Oriented Methods and Techniques – Joint application development (JAD) Joint application development (JAD) – Rapid application development (RAD) Rapid application development (RAD) For more information about Interpersonal Skills visit scsite.com/sad7e/morescsite.com/sad7e/more, locate Chapter 3 and then the Interpersonal Skills link.

8. 8 Joint Application Development  User Involvement – Users have a vital stake in an information system and they should participate fully – Successful systems must be user-oriented and users need to be involved – One popular strategy for user involvement is a JAD team approach For more information about JAD visit scsite.com/sad7e/more, scsite.com/sad7e/more locate Chapter 3 and then the JAD link.

9. 9 Joint Application Development  JAD Participants and Roles – JAD participants should be insulated from the distraction of day-to-day operations – Objective is to analyze the existing system, obtain user input and expectations, and document user requirements for the new system Figure 3-3 Figure 3-4 Figure 3-5

10. 10 Joint Application Development  JAD Advantages and Disadvantages – Advantages Allows key users to participate effectively When properly used, JAD can result in a more accurate statement of system requirements, a better understanding of common goals, and a stronger commitment to the success of the new system – Disadvantages More expensive and can be cumbersome if the group is too large relative to the size of the project

11. 11 Rapid Application Development  Is a team-based technique that speeds up information systems development and produces a functioning information system  Relies heavily on prototyping and user involvement  Process continues until the system is completely developed and users are satisfied Figure 3-6 For more information about RAD visit scsite.com/sad7e/more,scsite.com/sad7e/more locate Chapter 3 and then the RAD link.

12. 12 Rapid Application Development  RAD Phases and Activities – Requirements planning phase Requirements planning phase – User design phase User design phase – Construction phase Construction phase – Cutover phase Cutover phase Figure 3-7

13. 13 Rapid Application Development  RAD Objectives – To cut development time and expense by involving the users in every phase of systems development – Successful RAD team must have IT resources, skills, and management support – Helps a development team design a system that requires a highly interactive or complex user interface

14. 14 Rapid Application Development  RAD Advantages and Disadvantages – Advantages Systems can be developed more quickly with significant cost savings – Disadvantages RAD stresses the mechanics of the system itself and does not emphasize the company’s strategic business needs Might allow less time to develop quality, consistency, and design standards

15. 15 Modeling Tools and Techniques  CASE Tools – Offer powerful modeling features – Systems analysts use modeling and fact- finding interactively  Functional Decomposition Diagrams – Functional decomposition diagram (FDD) Functional decomposition diagram (FDD) – Also called structure chartsstructure charts Figure 3-8 Figure 3-9

16. 16 Modeling Tools and Techniques  Data Flow Diagrams – Data flow diagram (DFD) Data flow diagram (DFD) – Working from a functional decomposition diagram, analysts can create data flow diagrams (DFDs) to show how the system stores, processes, and transforms data Figure 3-10

17. 17 Modeling Tools and Techniques  Unified Modeling Language Unified Modeling Language – Widely used method of visualizing and documenting software systems design – Use case diagrams Use case diagrams Actor – Sequence diagrams Sequence diagrams Figure 3-11 Figure 3-12 Figure 3-13 Figure 3-14 For more information about Unified Modeling Language visit scsite.com/sad7e/more,scsite.com/sad7e/more locate Chapter 3 and then the Unified Modeling Language link.

18. 18 System Requirements Checklist  System requirement System requirement  Five general categories – Outputs – Inputs – Processes – Performance – Controls

19. 19 System Requirements Checklist  Outputs – The Web site must report online volume statistics every four hours, and hourly during peak periods – The inventory system must produce a daily report showing the part number, description, quantity on hand, quantity allocated, quantity available, and unit cost of all sorted by part number

20. 20 System Requirements Checklist  Inputs – Manufacturing employees must swipe their ID cards into online data collection terminals that record labor costs and calculate production efficiency – The department head must enter overtime hours on a separate screen

21. 21 System Requirements Checklist  Processes – The student records system must calculate the GPA at the end of each semester – As the final step in year-end processing, the payroll system must update employee salaries, bonuses, and benefits and produce tax data required by the IRS

22. 22 System Requirements Checklist  Performance – The system must support 25 users online simultaneously – Response time must not exceed four seconds

23. 23 System Requirements Checklist  Controls – The system must provide log-on security at the operating system level and at the application level – An employee record must be added, changed, or deleted only by a member of the human resources department

24. 24 Future Growth, Costs, and Benefits  Scalability Scalability – A scalable system offers a better return on the initial investment – To evaluate, you need information about projected future volume for all outputs, inputs, and processes

25. 25 Future Growth, Costs, and Benefits  Total Cost of Ownership – Total cost of ownership (TCO) is especially important if the development team is evaluating several alternatives Total cost of ownership (TCO) – One problem is that cost estimates tend to understate indirect costs – Rapid Economic Justification (REJ) Rapid Economic Justification (REJ) Figure 3-15 For more information about REJ visit scsite.com/sad7e/more,scsite.com/sad7e/more locate Chapter 3 and then the REJ link.

26. 26 Fact-Finding  Fact-Finding Overview – The first step is to identify the information you need – Develop a fact-finding plan  Who, What, Where, When, How, and Why? – Difference between asking what is being done and what could or should be done Figure 3-16

27. 27 Fact-Finding  The Zachman Framework – Zachman Framework for Enterprise Architecture Zachman Framework for Enterprise Architecture – Helps managers and users understand the model and assures that overall business goals translate into successful IT projects Figure 3-17 For more information about Zachman Framework visit scsite.com/sad7e/more, scsite.com/sad7e/more locate Chapter 3 and then the Zachman Framework link.

28. 28 Interviews  Systems analysts spend a great deal of time talking with people  Much of that time is spent conducting interviews interviews

29. 29 Interview  Step 1: Determine the People to Interview – Informal structures Informal structures  Step 2: Establish Objectives for the Interview – Determine the general areas to be discussed – List the facts you want to gather Figure 3-18

30. 30 Interviews  Step 3: Develop Interview Questions – Creating a standard list of interview questions helps to keep you on track and avoid unnecessary tangents – Avoid leading questionsleading questions – Open-ended questions Open-ended questions – Closed-ended questions Closed-ended questions – Range-of-response questions Range-of-response questions

31. 31 Interviews  Step 4: Prepare for the Interview – Careful preparation is essential because interview is an important meeting and not just a casual chat – Limit the interview to no more than one hour – Send a list of topics – Ask the interviewee to have samples available Figure 3-19Figure 3-20

32. 32 Interviews  Step 5: Conduct the Interview – Develop a specific plan for the meeting – Begin by introducing yourself, describing the project, and explaining interview objectives – Use engaged listeningengaged listening – Allow the person enough time to think about the question – After interview, summarize the session and seek a confirmation

33. 33 Interviews  Step 6: Document the Interview – Note taking should be kept to a minimum – After the interview, record the information quickly – After the interview, send memo expressing appreciation, including the main points discussed so the interviewee has a written summary and can offer additions or corrections

34. 34 Interviews  Step 7: Evaluate the Interview – In addition to recording the facts obtained in an interview, try to identify any possible biases  Unsuccessful Interviews – No matter how well you prepare for interviews, some are not successful

35. 35 Other Fact-Finding Techniques  Document Review Document Review  Observation Observation – Seeing the system in action gives you additional perspective and a better understanding of the system procedures – Plan your observations in advance – Hawthorne Effect Hawthorne Effect Figure 3-21

36. 36 Other Fact-Finding Techniques  Questionnaires and Surveys QuestionnairesSurveys – When designing a questionnaire, the most important rule of all is to make sure that your questions collect the right data in a form that you can use to further your fact-finding – Fill-in form Fill-in form Figure 3-22 Figure 3-23

37. 37 Other Fact-Finding Techniques  Sampling Sampling – Systematic sample Systematic sample – Stratified sample Stratified sample – Random sample Random sample – Main objective of a sample is to ensure that it represents the overall population accurately For more information about Sampling visit scsite.com/sad7e/more, scsite.com/sad7e/more locate Chapter 3 and then the Sampling link.

38. 38 Other Fact-Finding Techniques  Research Research – Can include the Internet, IT magazines, and books to obtain background information, technical material, and news about industry trends and developments – Site visit Site visit Figure 3-24

39. 39 Other Fact-Finding Techniques  Interviews versus Questionnaires – Interview is more familiar and personal – Questionnaire gives many people the opportunity to provide input and suggestions – Brainstorming Brainstorming – Structured brainstorming Structured brainstorming – Unstructured brainstorming Unstructured brainstorming

40. 40 Documentation  The Need for Recording the Facts – Record information as soon as you obtain it – Use the simplest recording method – Record your findings in such a way that they can be understood by someone else – Organize your documentation so related material is located easily

41. 41 Documentation  Software Tools – CASE Tools – Productivity Software Productivity Software Word processing, spreadsheets, database management, presentation graphics programs Histogram Figure 3-25

42. 42 Documentation  Software Tools – Graphics modeling software – Personal information managers Personal information manager (PIM) Handheld computers Personal digital assistants (PDAs) – Wireless communication devices Figure 3-26 Figure 3-27 Figure 3-28 Figure 3-29

43. 43 Preview of Data and Process Modeling  At the conclusion of requirements modeling, systems developers should have clear understanding of business processes and system requirements  The next step is to model the logical design of the system