Software Requirements Analysis And Design PDF

Document Details

DextrousMendelevium

Uploaded by DextrousMendelevium

The University of Winnipeg

2022

THE UNIVERSITY OF WINNIPEG

David Tenjo

Tags

software requirements software analysis software design information systems

Summary

This document is a study resource for the Software Requirements Analysis and Design class, potentially a past paper from The University of Winnipeg, in the Fall 2022 session. It covers various techniques for gathering requirements information for software projects, including interviewing users, analyzing documents, and exploring industry solutions.

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” It is important to be as specific...

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” 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 How to identify Requirements In order to gather “good” information about the system, there are specific methods (techniques) that can be followed. A good 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 INTERVIEWING USERS DISTRIBUTING AND REVIEWING INPUTS, Information AND OTHER STAKEHOLDERS COLLECTING QUESTIONNAIRES OUTPUTS, AND DOCUMENTATION Gathering Techniques OBSERVING AND RESEARCHING VENDOR COLLECTING ACTIVE DOCUMENTING SOLUTIONS USER COMMENTS AND BUSINESS PROCEDURES SUGGESTIONS SYSTEMS ANALYSIS AND DESIGN IN A CHANGING WORLD, 7TH EDITION - CHAPTER 2 ©2016. CENGAGE LEARNING. ALL RIGHTS RESERVED. 3 ❖Prepare detailed questions ❖Meet with individuals or groups of users 1. Interviewing ❖Obtain and discuss answers to the questions Users and Other Stakeholders ❖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 LEARNING. ALL RIGHTS RESERVED. 7 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 5. Research Vendor Solutions ◦ See what others have done for similar situations Techniques ◦ 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 The most common way to To define requirements, should be defined to define requirements is there are several different properly document what through the creation of ways to document them. the system should models accomplish THE UNIVERSITY OF WINNIPEG - ACS 2913 - FALL 2016 12 Model– a representation of some aspect of the system being built Types of Models ◦ Textual model– something written down, described Models and ◦ Graphical models– diagram, schematic ◦ Mathematical models– formulas, statistics, algorithms Modeling 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 ❖Communicating with other development team members Modeling ❖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 Activity Diagram– describes user (or system) activities, Workflows with the person who does each activity, and the sequential flow of these activities Activity ◦ Useful for showing a graphical model of a workflow Diagrams ◦ 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 The UML Activity Diagram is used to document (model) Summary 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

Use Quizgecko on...
Browser
Browser