1. PowerPoint Presentation for Dennis, Wixom, & Roth Systems Analysis and Design, 3rd Edition Copyright 2006 © John Wiley & Sons, Inc. All rights reserved. 4 - 1 Systems Analysis and Design 3rd Edition Alan Dennis, Barbara Haley Wixom, and Roberta Roth John Wiley & Sons, Inc. Slides by Candace S. Garrod Red Rocks Community College Modified by Yusuf Altunel To be presented in CSE 440 Systems Analysis and Design İKU Department of Computer Engineering

2. PowerPoint Presentation for Dennis, Wixom, & Roth Systems Analysis and Design, 3rd Edition Copyright 2006 © John Wiley & Sons, Inc. All rights reserved. 4 - 2 Requirements Determination Chapter 4 The system’s functional and non functional characteristics should be controllable Requirements determination Analysis of requirements Modeling functional and non-functional characteristics

3. PowerPoint Presentation for Dennis, Wixom, & Roth Systems Analysis and Design, 3rd Edition Copyright 2006 © John Wiley & Sons, Inc. All rights reserved.. 4 - 3 Chapter Outline Requirements Determination What is a Requirement? Requirements Definition Determining Requirements Documenting Requirements Requirements Analysis Techniques Business Process Automation Business Process Improvement Business Process Reengineering Comparing Analysis Techniques Requirements Gathering Techniques Interviews Joint Application Development (JAD) Questionnaires Document Analysis Observation Selecting the Appropriate Requirements-Gathering Techniques

4. PowerPoint Presentation for Dennis, Wixom, & Roth Systems Analysis and Design, 3rd Edition Copyright 2006 © John Wiley & Sons, Inc. All rights reserved.. 4 - 4 Key Definitions The As-Is system is the current system and may or may not be computerized The To-Be system is the new system based on updated requirements The System Proposal is the key deliverable from the Analysis Phase

5. PowerPoint Presentation for Dennis, Wixom, & Roth Systems Analysis and Design, 3rd Edition Copyright 2006 © John Wiley & Sons, Inc. All rights reserved.. 4 - 5 Key Ideas The goal of the analysis phase is to truly understand the requirements and develop a new system or decide a new system isn’t needed. The System Proposal is presented to the approval committee via a system walk-through. Systems analysis incorporates initial systems design. Requirements determination is the single most critical step of the entire SDLC.

6. PowerPoint Presentation for Dennis, Wixom, & Roth Systems Analysis and Design, 3rd Edition Copyright 2006 © John Wiley & Sons, Inc. All rights reserved. 4 - 6 REQUIREMENTS DETERMINATION

7. PowerPoint Presentation for Dennis, Wixom, & Roth Systems Analysis and Design, 3rd Edition Copyright 2006 © John Wiley & Sons, Inc. All rights reserved.. 4 - 7 A statement of what the system must do characteristics the system must have Focus is on business user needs Requirements will change over time as project moves from analysis to design to implementation What is a Requirement?

8. 05.10.2015 8 Importance of Requirements Discovering what the stakeholders want the system to do. Failure here will cause project failure Lack of user involvement is a major cause of project failure Requirement should drive the rest of system development

9. 05.10.2015 9 Requirements: The Crossroad Requirements study is the crossroad All other project practices are directed by the requirements

10. 05.10.2015 10 Defining Requirements Specification of “what” should be implemented not “how” Functional and Non-functional requirements Functional requirements: What behavior system should offer Non-functional requirements : A specific property of the system A constraint on the system It is easier to include some “how”, but it must be mostly “what” Produce SRS Document the System Requirements Specification

11. 05.10.2015 11 Well-formed Requirements UML does not have a specific tool Book suggests the format the shall do Separate Functional from non-functional requirements Functional what the system should do Non-functional constraints on the system

12. 05.10.2015 ATM SW Requirements Functional requirements 1.The ATM system shall check the validity of the inserted ATM card 2.The ATM system shall validate the PIN number entered by the customer. 3.The ATM system shall dispense no more than $250 against any ATM card in 24-hour period. Non-functional requirements 1.The ATM system shall be written in C++. 2.The ATM system shall communicate with the bank using 256-bit encryption. 3.The ATM system shall validate and ATM card in three seconds or less. 4.The ATM system shall validate a PIN number in three seconds or less 12

13. PowerPoint Presentation for Dennis, Wixom, & Roth Systems Analysis and Design, 3rd Edition Copyright 2006 © John Wiley & Sons, Inc. All rights reserved.. 4 - 13 Functional Requirements A process the system has to perform Information the system must contain Nonfunctional Requirements Behavioral properties the system must have Operational Performance Security Cultural and political Requirement Types

14. PowerPoint Presentation for Dennis, Wixom, & Roth Systems Analysis and Design, 3rd Edition Copyright 2006 © John Wiley & Sons, Inc. All rights reserved.. 4 - 14 Functional Requirements Functional Requirement DescriptionExamples

15. PowerPoint Presentation for Dennis, Wixom, & Roth Systems Analysis and Design, 3rd Edition Copyright 2006 © John Wiley & Sons, Inc. All rights reserved.. 4 - 15 Nonfunctional Requirements Nonfunctional Requirement DescriptionExamples

16. PowerPoint Presentation for Dennis, Wixom, & Roth Systems Analysis and Design, 3rd Edition Copyright 2006 © John Wiley & Sons, Inc. All rights reserved.. 4 - 16 Requirements Definition A report also called as “Requirements Definition Report” Text report Lists all requirements funcional and nonfunctional in outline format Structure Requirments are grouped Functional and nonfunctional Further grouped into Type of requirement or function Prioritization High Medium Low

17. PowerPoint Presentation for Dennis, Wixom, & Roth Systems Analysis and Design, 3rd Edition Copyright 2006 © John Wiley & Sons, Inc. All rights reserved.. 4 - 17 Sample Requirements Definition

18. PowerPoint Presentation for Dennis, Wixom, & Roth Systems Analysis and Design, 3rd Edition Copyright 2006 © John Wiley & Sons, Inc. All rights reserved.. 4 - 18 The obvious purpose to provide information needed in analysis phase Usecases Process models Data models to support activities in design phase Key purpose is to define the project scope: what is to be included and what is not. Documenting Requirements

19. PowerPoint Presentation for Dennis, Wixom, & Roth Systems Analysis and Design, 3rd Edition Copyright 2006 © John Wiley & Sons, Inc. All rights reserved. 4 - 19 REQUIREMENTS ANALYSIS TECHNIQUES

20. PowerPoint Presentation for Dennis, Wixom, & Roth Systems Analysis and Design, 3rd Edition Copyright 2006 © John Wiley & Sons, Inc. All rights reserved.. 4 - 20 Basic Process of Analysis (Determining Requirements) Understand the “As-Is” system Identify improvement opportunities Develop the “To-Be” system concept Techniques vary in amount of change BPA: Business Process Automation small change BPI : Business Process Improvement moderate change BPR : Business Process Reengineering significant change Additional information gathering techniques are needed as well

21. PowerPoint Presentation for Dennis, Wixom, & Roth Systems Analysis and Design, 3rd Edition Copyright 2006 © John Wiley & Sons, Inc. All rights reserved.. 4 - 21 Business Process Automation Goal: Efficiency for users

22. PowerPoint Presentation for Dennis, Wixom, & Roth Systems Analysis and Design, 3rd Edition Copyright 2006 © John Wiley & Sons, Inc. All rights reserved.. 4 - 22 Identifying Improvements in As-Is Systems Problem Analysis Ask users to identify problems and solutions Improvements tend to be small and incremental Rarely finds improvements with significant business value Root Cause Analysis Challenge assumptions about why problem exists Trace symptoms to their causes to discover the “real” problem

23. PowerPoint Presentation for Dennis, Wixom, & Roth Systems Analysis and Design, 3rd Edition Copyright 2006 © John Wiley & Sons, Inc. All rights reserved.. 4 - 23 Root Cause Analysis Example

24. PowerPoint Presentation for Dennis, Wixom, & Roth Systems Analysis and Design, 3rd Edition Copyright 2006 © John Wiley & Sons, Inc. All rights reserved.. 4 - 24 Business Process Improvement Goal: Efficiency and effectiveness for users

25. PowerPoint Presentation for Dennis, Wixom, & Roth Systems Analysis and Design, 3rd Edition Copyright 2006 © John Wiley & Sons, Inc. All rights reserved.. 4 - 25 Duration Analysis Calculate time needed for each process step Calculate time needed for overall process Compare the two – a large difference indicates a badly fragmented process Potential solutions: Process integration – change the process to use fewer people, each with broader responsibilities Parallelization – change the process so that individual steps are performed simultaneously

26. PowerPoint Presentation for Dennis, Wixom, & Roth Systems Analysis and Design, 3rd Edition Copyright 2006 © John Wiley & Sons, Inc. All rights reserved.. 4 - 26 Activity-Based Costing Calculate cost of each process step Consider both direct and indirect costs Identify most costly steps and focus improvement efforts on them

27. PowerPoint Presentation for Dennis, Wixom, & Roth Systems Analysis and Design, 3rd Edition Copyright 2006 © John Wiley & Sons, Inc. All rights reserved.. 4 - 27 Benchmarking Studying how other organizations perform the same business process Informal benchmarking Common for customer- facing processes Interact with other business’ processes as if you are a customer

28. PowerPoint Presentation for Dennis, Wixom, & Roth Systems Analysis and Design, 3rd Edition Copyright 2006 © John Wiley & Sons, Inc. All rights reserved.. 4 - 28 Business Process Reengineering (BRP) Goal: Radical redesign of business processes

29. PowerPoint Presentation for Dennis, Wixom, & Roth Systems Analysis and Design, 3rd Edition Copyright 2006 © John Wiley & Sons, Inc. All rights reserved.. 4 - 29 Outcome Analysis Consider desirable outcomes from customers’ perspective Consider what the organization could enable the customer to do

30. PowerPoint Presentation for Dennis, Wixom, & Roth Systems Analysis and Design, 3rd Edition Copyright 2006 © John Wiley & Sons, Inc. All rights reserved.. 4 - 30 Technology Analysis Analysts list important and interesting technologies Managers list important and interesting technologies The group identifies how each technology might be applied to the business how the business might benefit

31. PowerPoint Presentation for Dennis, Wixom, & Roth Systems Analysis and Design, 3rd Edition Copyright 2006 © John Wiley & Sons, Inc. All rights reserved.. 4 - 31 Activity Elimination Identify what would happen if each organizational activity were eliminated Use “force-fit” to test all possibilities

32. PowerPoint Presentation for Dennis, Wixom, & Roth Systems Analysis and Design, 3rd Edition Copyright 2006 © John Wiley & Sons, Inc. All rights reserved.. 4 - 32 Comparing Analysis Techniques Potential business value Project cost Breadth of analysis Risk

33. PowerPoint Presentation for Dennis, Wixom, & Roth Systems Analysis and Design, 3rd Edition Copyright 2006 © John Wiley & Sons, Inc. All rights reserved.. 4 - 33 Project Characteristics

34. PowerPoint Presentation for Dennis, Wixom, & Roth Systems Analysis and Design, 3rd Edition Copyright 2006 © John Wiley & Sons, Inc. All rights reserved. 4 - 34 REQUIREMENTS-GATHERING TECHNIQUES

35. PowerPoint Presentation for Dennis, Wixom, & Roth Systems Analysis and Design, 3rd Edition Copyright 2006 © John Wiley & Sons, Inc. All rights reserved.. 4 - 35 Interviews Most commonly used technique Basic steps: Selecting Interviewees Designing Interview Questions Preparing for the Interview Conducting the Interview Post-Interview Follow-up

36. PowerPoint Presentation for Dennis, Wixom, & Roth Systems Analysis and Design, 3rd Edition Copyright 2006 © John Wiley & Sons, Inc. All rights reserved.. 4 - 36 Selecting Interviewees Based on information needs Best to get different perspectives Managers Users Ideally, all key stakeholders Keep organizational politics in mind

37. PowerPoint Presentation for Dennis, Wixom, & Roth Systems Analysis and Design, 3rd Edition Copyright 2006 © John Wiley & Sons, Inc. All rights reserved.. 4 - 37 Three Types of Questions

38. PowerPoint Presentation for Dennis, Wixom, & Roth Systems Analysis and Design, 3rd Edition Copyright 2006 © John Wiley & Sons, Inc. All rights reserved.. 4 - 38 Designing Interview Questions Unstructured interview is useful in early information gathering: Goal is broad Information is roughly defined Structured interview is useful later Goal is very specific Information is defined correctly

39. PowerPoint Presentation for Dennis, Wixom, & Roth Systems Analysis and Design, 3rd Edition Copyright 2006 © John Wiley & Sons, Inc. All rights reserved.. 4 - 39 Top-Down and Bottom-up Questioning Strategies

40. PowerPoint Presentation for Dennis, Wixom, & Roth Systems Analysis and Design, 3rd Edition Copyright 2006 © John Wiley & Sons, Inc. All rights reserved.. 4 - 40 Preparing for the Interview Prepare general interview plan List of question Anticipated answers and follow-ups Confirm areas of knowledge Set priorities in case of time shortage Prepare the interviewee Schedule Inform of reason for interview Inform of areas of discussion

41. PowerPoint Presentation for Dennis, Wixom, & Roth Systems Analysis and Design, 3rd Edition Copyright 2006 © John Wiley & Sons, Inc. All rights reserved.. 4 - 41 Conducting the Interview Appear professional and unbiased Record all information Check on organizational policy regarding tape recording Be sure you understand all issues and terms Separate facts from opinions Give interviewee time to ask questions Be sure to thank the interviewee End on time

42. PowerPoint Presentation for Dennis, Wixom, & Roth Systems Analysis and Design, 3rd Edition Copyright 2006 © John Wiley & Sons, Inc. All rights reserved.. 4 - 42 Post-Interview Follow-Up Prepare interview notes Prepare interview report Have interviewee review and confirm interview report Look for gaps and new questions

43. PowerPoint Presentation for Dennis, Wixom, & Roth Systems Analysis and Design, 3rd Edition Copyright 2006 © John Wiley & Sons, Inc. All rights reserved.. 4 - 43 Joint Application Development (JAD) A structured group process focused on determining requirements Involves project team, users, and management working together May reduce scope creep by 50% Very useful technique

44. PowerPoint Presentation for Dennis, Wixom, & Roth Systems Analysis and Design, 3rd Edition Copyright 2006 © John Wiley & Sons, Inc. All rights reserved.. 4 - 44 JAD Participants Facilitator Trained in JAD techniques Sets agenda and guides group processes Scribe(s) Record content of JAD sessions Users and managers from business area with broad and detailed knowledge

45. PowerPoint Presentation for Dennis, Wixom, & Roth Systems Analysis and Design, 3rd Edition Copyright 2006 © John Wiley & Sons, Inc. All rights reserved.. 4 - 45 Preparing for the JAD Sessions Time commitment – ½ day to several weeks Strong management support is needed to release key participants from their usual responsibilities Careful planning is essential e-JAD can help alleviate some problems inherent with groups

46. PowerPoint Presentation for Dennis, Wixom, & Roth Systems Analysis and Design, 3rd Edition Copyright 2006 © John Wiley & Sons, Inc. All rights reserved.. 4 - 46 JAD Meeting Room

47. PowerPoint Presentation for Dennis, Wixom, & Roth Systems Analysis and Design, 3rd Edition Copyright 2006 © John Wiley & Sons, Inc. All rights reserved.. 4 - 47 Conducting the JAD Session Formal agenda and ground rules Top-down structure most successful Facilitator activities Keep session on track Help with technical terms and jargon Record group input Stay neutral, but help resolve issues Post-session follow-up report

48. PowerPoint Presentation for Dennis, Wixom, & Roth Systems Analysis and Design, 3rd Edition Copyright 2006 © John Wiley & Sons, Inc. All rights reserved.. 4 - 48 Post JAD Follow-up Postsession report is prepared and circulated among session attendees The report should be completed approximately a week to two after the JAD session

49. PowerPoint Presentation for Dennis, Wixom, & Roth Systems Analysis and Design, 3rd Edition Copyright 2006 © John Wiley & Sons, Inc. All rights reserved.. 4 - 49 Questionnaires A set of written questions, often sent to a large number of people May be paper-based or electronic Select participants using samples of the population Design the questions for clarity and ease of analysis Administer the questionnaire and take steps to get a good response rate Questionnaire follow-up report

50. PowerPoint Presentation for Dennis, Wixom, & Roth Systems Analysis and Design, 3rd Edition Copyright 2006 © John Wiley & Sons, Inc. All rights reserved.. 4 - 50 Good Questionnaire Design

51. PowerPoint Presentation for Dennis, Wixom, & Roth Systems Analysis and Design, 3rd Edition Copyright 2006 © John Wiley & Sons, Inc. All rights reserved.. 4 - 51 Document Analysis Study of existing material describing the current system Forms, reports, policy manuals, organization charts describe the formal system Look for the informal system in user additions to forms/report and unused form/report elements User changes to existing forms/reports or non-use of existing forms/reports suggest the system needs modification

52. PowerPoint Presentation for Dennis, Wixom, & Roth Systems Analysis and Design, 3rd Edition Copyright 2006 © John Wiley & Sons, Inc. All rights reserved.. 4 - 52 Observation Watch processes being performed Users/managers often don’t accurately recall everything they do Checks validity of information gathered other ways Be aware that behaviors change when people are watched Be unobtrusive Identify peak and lull periods

53. PowerPoint Presentation for Dennis, Wixom, & Roth Systems Analysis and Design, 3rd Edition Copyright 2006 © John Wiley & Sons, Inc. All rights reserved.. 4 - 53 Selecting the Appropriate Requirements-Gathering Techniques Type of information Depth of information Breadth of information Integration of information User involvement Cost Combining techniques

54. PowerPoint Presentation for Dennis, Wixom, & Roth Systems Analysis and Design, 3rd Edition Copyright 2006 © John Wiley & Sons, Inc. All rights reserved.. 4 - 54 Comparison of Requirements- Gathering Techniques

55. PowerPoint Presentation for Dennis, Wixom, & Roth Systems Analysis and Design, 3rd Edition Copyright 2006 © John Wiley & Sons, Inc. All rights reserved.. 4 - 55 Summary The analysis process focuses on capturing the business requirements for the system Functional and non-functional business requirements tell what the system must do Three main requirements analysis techniques are BPA, BPI, and BPR These techniques vary in potential business value, but also in potential cost and risk

56. PowerPoint Presentation for Dennis, Wixom, & Roth Systems Analysis and Design, 3rd Edition Copyright 2006 © John Wiley & Sons, Inc. All rights reserved.. 4 - 56 Summary, continued There are five major requirements- gathering techniques that all systems analysts must be able to use: Interviews, JAD, Questionnaires, Document Analysis, and Observation. Systems analysts must also know how and when to use each as well as how to combine methods.

57. PowerPoint Presentation for Dennis, Wixom, & Roth Systems Analysis and Design, 3rd Edition Copyright 2006 © John Wiley & Sons, Inc. All rights reserved.. 4 - 57 Copyright © 2006 John Wiley & Sons, Inc. All rights reserved. Reproduction or translation of this work beyond that permitted in Section 117 of the 1976 United States Copyright Act without the express written permission of the copyright owner is unlawful. Request for further information should be addressed to the Permissions Department, John Wiley & Sons, Inc. The purchaser may make back-up copies for his/her own use only and not for redistribution or resale. The Publisher assumes no responsibility for errors, omissions, or damages, caused by the use of these programs or from the use of the information contained herein.