1. Systems Analysis and Design in a Changing World, 6th Edition 1 Chapter 2 CHAPTER 2 SATZINGER | JACKSON | BURD INTRODUCTION TO SYSTEMS ANALYSIS AND DESIGN: AN AGILE, ITERATIVE APPROACH

2. Investigating System Requirements Introduction to Systems Analysis and Design: An Agile, Iteractive Approach 6 th Ed Satzinger, Jackson & Burd Chapter 2 © 2012 Cengage Learning. All Rights Reserved. This edition is intended for use outside of the U.S. only, with content that may be different from the U.S. Edition. May not be scanned, copied, duplicated, or posted to a publicly accessible website, in whole or in part.

3. 3 Chapter 2 Outline The RMO Consolidated Sales and Marketing System Project Systems Analysis Activities What Are Requirements? Models and Modeling Stakeholders Information-Gathering Techniques Documenting Workflows with Activity Diagrams Introduction to Systems Analysis and Design, 6th Edition © 2012 Cengage Learning. All Rights Reserved. This edition is intended for use outside of the U.S. only, with content that may be different from the U.S. Edition. May not be scanned, copied, duplicated, or posted to a publicly accessible website, in whole or in part.

4. Introduction to Systems Analysis and Design, 6th Edition 4 Learning Objectives Describe the activities of systems analysis Explain the difference between functional and nonfunctional requirements Describe the role of models in systems analysis Identify and understand different kinds of stakeholders and their contributions to requirements definition Describe information-gathering techniques and determine when each is best applied Develop activity diagrams to model workflows © 2012 Cengage Learning. All Rights Reserved. This edition is intended for use outside of the U.S. only, with content that may be different from the U.S. Edition. May not be scanned, copied, duplicated, or posted to a publicly accessible website, in whole or in part.

5. 5 Overview Chapter 1 introduced the system development lifecycle (SDLC) and demonstrated its use for a small project This chapter expands the SDLC processes to cover a wider range of concepts, tools and techniques Core process 3: Discover and understand the details of the problem or need—is the main focus of systems analysis Systems analysis activities are detailed in this chapter A larger Ridgeline Mountain Outfitters (RMO) project is introduced that will be used throughout the text to illustrate analysis and design Introduction to Systems Analysis and Design, 6th Edition © 2012 Cengage Learning. All Rights Reserved. This edition is intended for use outside of the U.S. only, with content that may be different from the U.S. Edition. May not be scanned, copied, duplicated, or posted to a publicly accessible website, in whole or in part.

6. 6 Ridgeline Mountain Outfitters (RMO) RMO has an elaborate set of information systems that support operations and management Customer expectations, modern technological capabilities, and competitive pressures led RMO to believe it is time to upgrade support for sales and marketing A new Consolidated Sales and Marketing System was proposed This is a major project that grew out of the RMO strategic planning process Introduction to Systems Analysis and Design, 6th Edition © 2012 Cengage Learning. All Rights Reserved. This edition is intended for use outside of the U.S. only, with content that may be different from the U.S. Edition. May not be scanned, copied, duplicated, or posted to a publicly accessible website, in whole or in part.

7. 7 Ridgeline Mountain Outfitters (RMO) Strategic planning and competitive advantage for organizations involves leveraging information systems The information systems strategic plan is based on the overall strategic needs of the organization The information systems strategic plan includes definition of the technology architecture and the application architecture needed by the organization Introduction to Systems Analysis and Design, 6th Edition © 2012 Cengage Learning. All Rights Reserved. This edition is intended for use outside of the U.S. only, with content that may be different from the U.S. Edition. May not be scanned, copied, duplicated, or posted to a publicly accessible website, in whole or in part.

8. 8 Information Systems Strategic Plan Technology architecture— the set of computing hardware, network hardware and topology, and system software employed by the organization Application architecture—the organization and construction of software resources to implement an organization’s information systems Introduction to Systems Analysis and Design, 6th Edition © 2012 Cengage Learning. All Rights Reserved. This edition is intended for use outside of the U.S. only, with content that may be different from the U.S. Edition. May not be scanned, copied, duplicated, or posted to a publicly accessible website, in whole or in part.

9. 9 RMO Existing Application Architecture Supply Chain Management (SCM) 5 years old; Java/Oracle Tradeshow system will interface with SCM Phone/Mail Order System 12 years old; Visual Studio/MS SQL Reached capacity; minimal integration Retail Store System Older package solution; minimal integration Customer Support System (CSS) Web based system; evolved over the years, minimal integration Introduction to Systems Analysis and Design, 6th Edition © 2012 Cengage Learning. All Rights Reserved. This edition is intended for use outside of the U.S. only, with content that may be different from the U.S. Edition. May not be scanned, copied, duplicated, or posted to a publicly accessible website, in whole or in part.

10. 10 Proposed Application Architecture: Integrate SCM and New CSMS Introduction to Systems Analysis and Design, 6th Edition © 2012 Cengage Learning. All Rights Reserved. This edition is intended for use outside of the U.S. only, with content that may be different from the U.S. Edition. May not be scanned, copied, duplicated, or posted to a publicly accessible website, in whole or in part.

11. 11 New Consolidated Sales and Marketing System (CSMS) Sales Subsystem Integrates online, phone, and retail stores Order Fulfillment Subsystem Track shipments, rate products and services Customer Account Subsystem Shopping history, linkups, “mountain bucks” rewards Marketing Subsystem Promotional packages, partner relationships, more complete merchandise information and reporting Introduction to Systems Analysis and Design, 6th Edition © 2012 Cengage Learning. All Rights Reserved. This edition is intended for use outside of the U.S. only, with content that may be different from the U.S. Edition. May not be scanned, copied, duplicated, or posted to a publicly accessible website, in whole or in part.

12. 12 Systems Analysis Activities The New Consolidated Sales and Marketing System (CSMS) will require discovering and understanding extensive and complex business processes and business rules The SDLC indicates the project starts with identifying the problem, obtaining approval, and planning the project (as seen in Chapter 1) To get to the heart of systems analysis, this text skips right to analysis activities generally and the specifically for the RMO CSMS project Project planning and project management are covered in detail later in the text Introduction to Systems Analysis and Design, 6th Edition © 2012 Cengage Learning. All Rights Reserved. This edition is intended for use outside of the U.S. only, with content that may be different from the U.S. Edition. May not be scanned, copied, duplicated, or posted to a publicly accessible website, in whole or in part.

13. 13 Systems Analysis Activities Involve discovery and understanding Introduction to Systems Analysis and Design, 6th Edition © 2012 Cengage Learning. All Rights Reserved. This edition is intended for use outside of the U.S. only, with content that may be different from the U.S. Edition. May not be scanned, copied, duplicated, or posted to a publicly accessible website, in whole or in part.

14. 14 Systems Analysis Activities Gather Detailed Information Interviews, questionnaires, documents, observing business processes, researching vendors, comments and suggestions The analyst must become an expert in the business area the system will support Define Requirements Modeling functional requirements and non-functional requirements Prioritize Requirements Essential, important, vs. nice to have Why prioritize the requirements? 2 reasons Develop User-Interface Dialogs Flow of interaction between user and system Analyst can develop user interfaces via models or prototype Evaluate Requirements with Users User involvement, feedback, adapt to changes When do you need to develop prototypes?

15. 15 What Are Requirements? System Requirements = Functional requirements Non-functional requirements Functional Requirements– the activities the system must perform Business uses, functions the users carry out Use cases in Chapter 1 Non-Functional Requirements– other system characteristics Constraints and performance goals Introduction to Systems Analysis and Design, 6th Edition © 2012 Cengage Learning. All Rights Reserved. This edition is intended for use outside of the U.S. only, with content that may be different from the U.S. Edition. May not be scanned, copied, duplicated, or posted to a publicly accessible website, in whole or in part.

16. 16

17. 17 FURPS+ Requirements Acronym F unctional requirements U sability requirements R eliability requirements P erformance requirements S ecurity requirements + even more categories… Introduction to Systems Analysis and Design, 6th Edition © 2012 Cengage Learning. All Rights Reserved. This edition is intended for use outside of the U.S. only, with content that may be different from the U.S. Edition. May not be scanned, copied, duplicated, or posted to a publicly accessible website, in whole or in part.

18. 18 FURPS+ Requirements Acronym Introduction to Systems Analysis and Design, 6th Edition © 2012 Cengage Learning. All Rights Reserved. This edition is intended for use outside of the U.S. only, with content that may be different from the U.S. Edition. May not be scanned, copied, duplicated, or posted to a publicly accessible website, in whole or in part.

19. 19 Models and Modeling How do we define requirements? After collecting information, create models Model– a representation of some aspect of the system being built Types of Models Textual model: text-based models such as memos, reports, narratives, and lists Graphical models: system models that use pictures and other graphical elements. like diagrams Mathematical models: system models that describe requirements numerically or as mathematical expressions. Like formulas, statistics, algorithms Unified Modeling Language (UML) Standard set of model constructs and notations defined by the Object Management Group

20. 20 Some Analysis and Design Models Introduction to Systems Analysis and Design, 6th Edition © 2012 Cengage Learning. All Rights Reserved. This edition is intended for use outside of the U.S. only, with content that may be different from the U.S. Edition. May not be scanned, copied, duplicated, or posted to a publicly accessible website, in whole or in part.

21. 21 Reasons for Modeling Learning from the modeling process Reducing complexity by abstraction Remembering all the details Communicating with other development team members Communicating with a variety of users and stakeholders Documenting what was done for future maintenance/enhancement Introduction to Systems Analysis and Design, 6th Edition © 2012 Cengage Learning. All Rights Reserved. This edition is intended for use outside of the U.S. only, with content that may be different from the U.S. Edition. May not be scanned, copied, duplicated, or posted to a publicly accessible website, in whole or in part.

22. 22 Stakeholders Who do you involve and talk to? Stakeholders– persons who have an interest in the successful implementation of the system Internal Stakeholders– persons within the organization External stakeholders – persons outside the organization Operational stakeholders – persons who regularly interact with the system Executive stakeholders– persons who don’t directly interact, but use the information or have financial interest Client – person or group that provides the funding for a system development project Organization's technical & support staff

23. 23 Stakeholders of a comprehensive accounting system for public company Introduction to Systems Analysis and Design, 6th Edition © 2012 Cengage Learning. All Rights Reserved. This edition is intended for use outside of the U.S. only, with content that may be different from the U.S. Edition. May not be scanned, copied, duplicated, or posted to a publicly accessible website, in whole or in part.

24. 24 Stakeholders For RMO CSMS Project Phone/mail sales order clerks Warehouse and shipping personnel Marketing personnel who maintain online catalog information Marketing, sales, accounting, and financial managers Senior executives Customers External shippers (e.g., UPS and FedEx) Introduction to Systems Analysis and Design, 6th Edition © 2012 Cengage Learning. All Rights Reserved. This edition is intended for use outside of the U.S. only, with content that may be different from the U.S. Edition. May not be scanned, copied, duplicated, or posted to a publicly accessible website, in whole or in part.

25. 25 RMO Internal Stakeholders Introduction to Systems Analysis and Design, 6th Edition © 2012 Cengage Learning. All Rights Reserved. This edition is intended for use outside of the U.S. only, with content that may be different from the U.S. Edition. May not be scanned, copied, duplicated, or posted to a publicly accessible website, in whole or in part.

26. 26 Information Gathering Techniques Interviewing users and other stakeholders Distributing and collecting questionnaires Reviewing inputs, outputs, and documentation Observing and documenting business procedures Researching vendor solutions Collecting active user comments and suggestions Introduction to Systems Analysis and Design, 6th Edition © 2012 Cengage Learning. All Rights Reserved. This edition is intended for use outside of the U.S. only, with content that may be different from the U.S. Edition. May not be scanned, copied, duplicated, or posted to a publicly accessible website, in whole or in part.

27. 27 Interviewing Users and Other Stakeholders Prepare detailed questions Meet with individuals or groups of users Obtain and discuss answers to the questions Document the answers Follow up as needed in future meetings or interviews Introduction to Systems Analysis and Design, 6th Edition © 2012 Cengage Learning. All Rights Reserved. This edition is intended for use outside of the U.S. only, with content that may be different from the U.S. Edition. May not be scanned, copied, duplicated, or posted to a publicly accessible website, in whole or in part.

28. 28 Themes for Information Gathering Questions Question types Open-ended questions: that encourage discussion or explanation Closed-ended questions: that elicit specific facts Focus of Questions – current system or new?

29. 29 Interview Preparation, Conduct, and Follow-up Introduction to Systems Analysis and Design, 6th Edition © 2012 Cengage Learning. All Rights Reserved. This edition is intended for use outside of the U.S. only, with content that may be different from the U.S. Edition. May not be scanned, copied, duplicated, or posted to a publicly accessible website, in whole or in part.

30. 30 Interview Session Agenda Introduction to Systems Analysis and Design, 6th Edition © 2012 Cengage Learning. All Rights Reserved. This edition is intended for use outside of the U.S. only, with content that may be different from the U.S. Edition. May not be scanned, copied, duplicated, or posted to a publicly accessible website, in whole or in part.

31. 31 Keeping an Open Items List Introduction to Systems Analysis and Design, 6th Edition © 2012 Cengage Learning. All Rights Reserved. This edition is intended for use outside of the U.S. only, with content that may be different from the U.S. Edition. May not be scanned, copied, duplicated, or posted to a publicly accessible website, in whole or in part.

32. Distribute and Collect Questionnaires To collect information from a large number of stakeholders If the stakeholders are widely distributed geographically To obtain preliminary insight into stakeholders information needs, which helps to determine areas that need further research by using other methods Can contain a very limited number of open-ended questions Systems Analysis and Design in a Changing World, 6th Edition 32

33. 33

34. 34 Review Inputs, Outputs, and Procedures Two sources: 1.Industry-wide professional organizations and other companies 2.Existing business documents and procedure descriptions To get a preliminary understanding of the process Serve as visual aids for interview and as the working documents for discussions Help in identifying business rules that may not come up in the interviews Help in revealing discrepancies and redundancies in the business process

35. 35 Additional Techniques Observe and Document Business Processes Observing help you understand the business functions Ranging from Quick-walk through to doing the work yourself It is not necessary to observe all process at the same level of detail Observation often makes the users nervous Research Vendor Solutions See what others have done for similar situations Help users generate new ideas for how to better perform their business functions Some of these solutions are excellent and state of the art It is often cheaper and less risky to buy a solution rather than to build it Collect Active User Comments and Suggestions Feedback on models and tests Users know it when they see it

36. 36 Documenting Workflows with Activity Diagrams Workflow– sequence of processing steps that completely handles one business transaction or customer request Activity Diagram– describes user (or system) activities, the person who does each activity, and the sequential flow of these activities Useful for showing a graphical model of a workflow A UML diagram Synchronization bar :activity diagram component that either splits a control path into multiple concurrent paths or recombines concurrent paths Swimlane: activity diagram component containing all activities for a single agent or organizational unit

37. 37 Activity Diagrams Symbols Introduction to Systems Analysis and Design, 6th Edition © 2012 Cengage Learning. All Rights Reserved. This edition is intended for use outside of the U.S. only, with content that may be different from the U.S. Edition. May not be scanned, copied, duplicated, or posted to a publicly accessible website, in whole or in part.

38. 38 Activity Diagram for RMO Order Fulfillment Introduction to Systems Analysis and Design, 6th Edition © 2012 Cengage Learning. All Rights Reserved. This edition is intended for use outside of the U.S. only, with content that may be different from the U.S. Edition. May not be scanned, copied, duplicated, or posted to a publicly accessible website, in whole or in part.

39. 39 Activity Diagram with Concurrent Paths Introduction to Systems Analysis and Design, 6th Edition © 2012 Cengage Learning. All Rights Reserved. This edition is intended for use outside of the U.S. only, with content that may be different from the U.S. Edition. May not be scanned, copied, duplicated, or posted to a publicly accessible website, in whole or in part.

40. 40 Summary Systems analysis activates correspond to the core SDLC process Discover and understand details System projects originate from the information system strategic plan, which contains an technology architecture plan and an application architecture plan The RMO CSMS Project will be used throughout the text as an example of analysis and design Introduction to Systems Analysis and Design, 6th Edition © 2012 Cengage Learning. All Rights Reserved. This edition is intended for use outside of the U.S. only, with content that may be different from the U.S. Edition. May not be scanned, copied, duplicated, or posted to a publicly accessible website, in whole or in part.

41. 41 Summary Systems analysis involves defining system requirements– functional and non-functional Analysis activities include Gather detailed information Define requirements Prioritize requirements Develop user-interface dialogs Evaluate requirements with users FURPS+ is the acronym for functional, usability, reliability, performance, and security requirements Introduction to Systems Analysis and Design, 6th Edition © 2012 Cengage Learning. All Rights Reserved. This edition is intended for use outside of the U.S. only, with content that may be different from the U.S. Edition. May not be scanned, copied, duplicated, or posted to a publicly accessible website, in whole or in part.

42. 42 Summary Models and modeling are used to explore and document requirements A model represents some aspect of a system, and can include textual, graphical, and mathematical models Unified Modeling Language (UML) is the standard set of notations and terminology for information systems models Introduction to Systems Analysis and Design, 6th Edition © 2012 Cengage Learning. All Rights Reserved. This edition is intended for use outside of the U.S. only, with content that may be different from the U.S. Edition. May not be scanned, copied, duplicated, or posted to a publicly accessible website, in whole or in part.

43. 43 Summary Stakeholders are the people who have an interest in the success of the project There are internal vs. external stakeholders and operational vs. executive stakeholders Information gathering techniques are used to collect information about the project Interviews, questionnaires, reviewing documents, observing business processes, researching vendors, comments and suggestions The UML Activity Diagram is used to document (model) workflows after collecting information Introduction to Systems Analysis and Design, 6th Edition © 2012 Cengage Learning. All Rights Reserved. This edition is intended for use outside of the U.S. only, with content that may be different from the U.S. Edition. May not be scanned, copied, duplicated, or posted to a publicly accessible website, in whole or in part.