Software Requirements Analysis and Design (ACS2913) PDF
Document Details
Uploaded by WinningZircon
The University of Winnipeg
2022
David Tenjo
Tags
Summary
This document is lecture notes/slides for a software requirements analysis and design course (ACS2913) offered at the University of Winnipeg during Fall 2022. It covers various techniques for gathering requirements, including interviewing, questionnaires, and observing business processes.
Full Transcript
ACS2913 Software Requirements Analysis and Design Instructor: David Tenjo GATHERING AND DOCUMENTING REQUIREMENTS THE UNIVERSITY OF WINNIPEG - ACS 2913 - FALL 2022 1 We call it “information Gathering” How to identify Requirements It is important to be as specific and clear as possible as the en...
ACS2913 Software Requirements Analysis and Design Instructor: David Tenjo GATHERING AND DOCUMENTING REQUIREMENTS THE UNIVERSITY OF WINNIPEG - ACS 2913 - FALL 2022 1 We call it “information Gathering” How to identify Requirements It is important to be as specific and clear as possible as the entire system will be based on the information that is gathered at this stage In order to gather “good” information about the system, there are specific methods (techniques) that can be followed. A good Business Analyst is one who can gather specific, detailed, relevant requirements about a system, and is able to document those properly for Systems Designers / Developers THE UNIVERSITY OF WINNIPEG - ACS 2913 - FALL 2016 2 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 SYSTEMS ANALYSIS AND DESIGN IN A CHANGING WORLD, 7TH EDITION - CHAPTER 2 ©2016. CENGAGE LEARNING. ALL RIGHTS RESERVED. 3 ❖Prepare detailed questions 1. Interviewing Users and Other Stakeholders ❖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 SYSTEMS ANALYSIS AND DESIGN IN A CHANGING WORLD, 7TH EDITION - CHAPTER 2 ©2016. CENGAGE LEARNING. ALL RIGHTS RESERVED. 4 Themes Theme: What is the information that you would like to get? For Each Theme, identify questions that will get you the information you need SYSTEMS ANALYSIS AND DESIGN IN A CHANGING WORLD, 7TH EDITION - CHAPTER 2 ©2016. CENGAGE LEARNING. ALL RIGHTS RESERVED. 5 Preparing for the Interview SYSTEMS ANALYSIS AND DESIGN IN A CHANGING WORLD, 7TH EDITION - CHAPTER 2 ©2016. CENGAGE LEARNING. ALL RIGHTS RESERVED. 6 Interview Session Agenda SYSTEMS ANALYSIS AND DESIGN IN A CHANGING WORLD, 7TH EDITION - CHAPTER 2 7 LEARNING. ALL RIGHTS RESERVED. Keeping an Open Items List SYSTEMS ANALYSIS AND DESIGN IN A CHANGING WORLD, 7TH EDITION - CHAPTER 2 ©2016. CENGAGE LEARNING. ALL RIGHTS RESERVED. 8 2. Distribute and Collect Questionnaires SYSTEMS ANALYSIS AND DESIGN IN A CHANGING WORLD, 7TH EDITION - CHAPTER 2 ©2016. CENGAGE LEARNING. ALL RIGHTS RESERVED. 9 3. Review Inputs, Outputs, and Procedures SYSTEMS ANALYSIS AND DESIGN IN A CHANGING WORLD, 7TH EDITION - CHAPTER 2 ©2016. CENGAGE LEARNING. ALL RIGHTS RESERVED. 10 4. Observe and Document Business Processes ◦ Watch and learn ◦ Document with Activity diagram (next section) Additional Techniques 5. Research Vendor Solutions ◦ See what others have done for similar situations ◦ White papers, vendor literature, competitors 6. Collect Active User Comments and Suggestions ◦ Feedback on models and tests ◦ Users know it when the see it SYSTEMS ANALYSIS AND DESIGN IN A CHANGING WORLD, 7TH EDITION - CHAPTER 2 ©2016. CENGAGE LEARNING. ALL RIGHTS RESERVED. 11 Defining Requirements Once information is gathered, requirements should be defined to properly document what the system should accomplish To define requirements, there are several different ways to document them. THE UNIVERSITY OF WINNIPEG - ACS 2913 - FALL 2016 The most common way to define requirements is through the creation of models 12 Model– a representation of some aspect of the system being built Types of Models Models and Modeling ◦ Textual model– something written down, described ◦ Graphical models– diagram, schematic ◦ Mathematical models– formulas, statistics, algorithms Unified Modeling Language (UML) ◦ Standard graphical modeling symbols/terminology used for information systems SYSTEMS ANALYSIS AND DESIGN IN A CHANGING WORLD, 7TH EDITION - CHAPTER 2 ©2016. CENGAGE LEARNING. ALL RIGHTS RESERVED. 13 ❖Learning from the modeling process ❖Reducing complexity by abstraction ❖Remembering all the details Reasons for Modeling ❖Communicating with other development team members ❖Communicating with a variety of users and stakeholders ❖Documenting what was done for future maintenance/enhancement SYSTEMS ANALYSIS AND DESIGN IN A CHANGING WORLD, 7TH EDITION - CHAPTER 2 ©2016. CENGAGE LEARNING. ALL RIGHTS RESERVED. 14 Analysis and Design model samples SYSTEMS ANALYSIS AND DESIGN IN A CHANGING WORLD, 7TH EDITION - CHAPTER 2 ©2016. CENGAGE LEARNING. ALL RIGHTS RESERVED. 15 Workflow– sequence of processing steps that completely handles one business transaction or customer request Documenting Workflows with Activity Diagrams 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 SYSTEMS ANALYSIS AND DESIGN IN A CHANGING WORLD, 7TH EDITION - CHAPTER 2 ©2016. CENGAGE LEARNING. ALL RIGHTS RESERVED. 16 Activity Diagram Symbols SYSTEMS ANALYSIS AND DESIGN IN A CHANGING WORLD, 7TH EDITION - CHAPTER 2 ©2016. CENGAGE LEARNING. ALL RIGHTS RESERVED. 17 Activity Diagram for RMO Order Fulfillment SYSTEMS ANALYSIS AND DESIGN IN A CHANGING WORLD, 7TH EDITION - CHAPTER 2 LEARNING. ALL RIGHTS RESERVED. 18 Activity Diagram with Concurrent Paths SYSTEMS ANALYSIS AND DESIGN IN A CHANGING WORLD, 7TH EDITION - CHAPTER 2 ©2016. CENGAGE LEARNING. ALL RIGHTS RESERVED. 19 Information gathering techniques are used to collect information about the project ◦ Interviews, questionnaires, reviewing documents, observing business processes, researching vendors, comments and suggestions Summary The UML Activity Diagram is used to document (model) workflows after collecting information Models and modeling are used to explore and document requirements Unified Modeling Language (UML) is the standard set of notations and terminology for information systems models SYSTEMS ANALYSIS AND DESIGN IN A CHANGING WORLD, 7TH EDITION - CHAPTER 2 ©2016. CENGAGE LEARNING. ALL RIGHTS RESERVED. 20