IAD 2263: System Analysis and Design Chapter 2: Approaches to System Development.
IAD 2263: System Analysis and Design Chapter 3: Investigating System Requirements.
-
Upload
brenda-brooks -
Category
Documents
-
view
219 -
download
1
Transcript of IAD 2263: System Analysis and Design Chapter 3: Investigating System Requirements.
![Page 1: IAD 2263: System Analysis and Design Chapter 3: Investigating System Requirements.](https://reader036.fdocuments.net/reader036/viewer/2022062407/56649f515503460f94c75408/html5/thumbnails/1.jpg)
IAD 2263: System Analysis and Design
Chapter 3: Investigating System Requirements
![Page 2: IAD 2263: System Analysis and Design Chapter 3: Investigating System Requirements.](https://reader036.fdocuments.net/reader036/viewer/2022062407/56649f515503460f94c75408/html5/thumbnails/2.jpg)
Content
• Analysis activities in more detail• System requirements• Models and modeling• Stakeholders – The source of system
requirements • Techniques for Information Gathering • Validating the requirement
![Page 3: IAD 2263: System Analysis and Design Chapter 3: Investigating System Requirements.](https://reader036.fdocuments.net/reader036/viewer/2022062407/56649f515503460f94c75408/html5/thumbnails/3.jpg)
The Analysis Phase in More Detail
• Gather information
• Define system requirements
– Functional and nonfunctional
• Prioritize requirements
• Prototype for feasibility and discovery
• Generate and evaluate alternatives
• Review recommendations with management
3
![Page 4: IAD 2263: System Analysis and Design Chapter 3: Investigating System Requirements.](https://reader036.fdocuments.net/reader036/viewer/2022062407/56649f515503460f94c75408/html5/thumbnails/4.jpg)
The Activities of the Analysis Phase
4
![Page 5: IAD 2263: System Analysis and Design Chapter 3: Investigating System Requirements.](https://reader036.fdocuments.net/reader036/viewer/2022062407/56649f515503460f94c75408/html5/thumbnails/5.jpg)
Activities of the Analysis Phase and Their Key Questions
5
![Page 6: IAD 2263: System Analysis and Design Chapter 3: Investigating System Requirements.](https://reader036.fdocuments.net/reader036/viewer/2022062407/56649f515503460f94c75408/html5/thumbnails/6.jpg)
System Requirements• System requirements – specifications
that define the new system • Functional requirements
– Activities system must perform (use cases)
– Based on procedures and business functions
– Documented in analysis models
6
![Page 7: IAD 2263: System Analysis and Design Chapter 3: Investigating System Requirements.](https://reader036.fdocuments.net/reader036/viewer/2022062407/56649f515503460f94c75408/html5/thumbnails/7.jpg)
System Requirements (cont)
• Nonfunctional requirements– Technical requirement – hardware and
software– Performance requirement – workload
measures– Usability requirement – user interface,
workflow– Reliability requirement – outages, error
detection– Security requirement – access &
protection
7
![Page 8: IAD 2263: System Analysis and Design Chapter 3: Investigating System Requirements.](https://reader036.fdocuments.net/reader036/viewer/2022062407/56649f515503460f94c75408/html5/thumbnails/8.jpg)
Models and Modeling• Analyst describes information system
requirements using a collection of models
• Complex systems require more than one type of model
• Models represent some aspect of the system being built
• Process of creating models helps analyst clarify and refine design
• Models assist communication with system users
8
![Page 9: IAD 2263: System Analysis and Design Chapter 3: Investigating System Requirements.](https://reader036.fdocuments.net/reader036/viewer/2022062407/56649f515503460f94c75408/html5/thumbnails/9.jpg)
Stakeholders—The Source of
System Requirements• People with interest in successful system implementation
• Three primary groups of stakeholders
– Users (use system)
– Clients (pay for and own system)
– Technical staff (ensure system operation)
• Every type of stakeholder is identified by analyst
9
![Page 10: IAD 2263: System Analysis and Design Chapter 3: Investigating System Requirements.](https://reader036.fdocuments.net/reader036/viewer/2022062407/56649f515503460f94c75408/html5/thumbnails/10.jpg)
Stakeholders Interested in New System Development
10
![Page 11: IAD 2263: System Analysis and Design Chapter 3: Investigating System Requirements.](https://reader036.fdocuments.net/reader036/viewer/2022062407/56649f515503460f94c75408/html5/thumbnails/11.jpg)
Techniques for Information Gathering• Analysis phase done to understand business functions and develop system
requirements• Original structured approach
– Create model of existing system – Derive requirements from existing system
model
• Current approach – Identify logical requirements for new system – Balance the review of current business
functions with new system requirements11
![Page 12: IAD 2263: System Analysis and Design Chapter 3: Investigating System Requirements.](https://reader036.fdocuments.net/reader036/viewer/2022062407/56649f515503460f94c75408/html5/thumbnails/12.jpg)
Relationship Between Information Gathering and Model Building
12
![Page 13: IAD 2263: System Analysis and Design Chapter 3: Investigating System Requirements.](https://reader036.fdocuments.net/reader036/viewer/2022062407/56649f515503460f94c75408/html5/thumbnails/13.jpg)
Validating the Requirements
• Make sure gathered information is correct• Structured walkthrough
– Effective means of implementing quality control early in project
– Verify and validate system requirements– Review of findings from investigation and of
models based on findings• Project manager responsible for system
quality – Systems analyst, project manager are
partners
13
![Page 14: IAD 2263: System Analysis and Design Chapter 3: Investigating System Requirements.](https://reader036.fdocuments.net/reader036/viewer/2022062407/56649f515503460f94c75408/html5/thumbnails/14.jpg)
Structured
Walkthrough Form
14
![Page 15: IAD 2263: System Analysis and Design Chapter 3: Investigating System Requirements.](https://reader036.fdocuments.net/reader036/viewer/2022062407/56649f515503460f94c75408/html5/thumbnails/15.jpg)
Activity Diagrams• Workflow – sequence of steps to
process a business transaction• Activity Diagram – workflow diagram
to describe sequence of steps• Synchronization bar – symbol to
control splitting or merging of a path on an activity diagram
• Swimlane – bounded area that contains activities of a single agent
15
![Page 16: IAD 2263: System Analysis and Design Chapter 3: Investigating System Requirements.](https://reader036.fdocuments.net/reader036/viewer/2022062407/56649f515503460f94c75408/html5/thumbnails/16.jpg)
Activity Diagram Symbols
16
![Page 17: IAD 2263: System Analysis and Design Chapter 3: Investigating System Requirements.](https://reader036.fdocuments.net/reader036/viewer/2022062407/56649f515503460f94c75408/html5/thumbnails/17.jpg)
Activity Diagram
that Models a Workflow
17
![Page 18: IAD 2263: System Analysis and Design Chapter 3: Investigating System Requirements.](https://reader036.fdocuments.net/reader036/viewer/2022062407/56649f515503460f94c75408/html5/thumbnails/18.jpg)
Activity Diagram with Concurrent Paths
18
![Page 19: IAD 2263: System Analysis and Design Chapter 3: Investigating System Requirements.](https://reader036.fdocuments.net/reader036/viewer/2022062407/56649f515503460f94c75408/html5/thumbnails/19.jpg)
Build Prototypes• Prototype - Preliminary working model
of a larger, more complex system component
– Discovery, design, evolving prototypes• Prototype should be
– Operative • Working model to provide “look and feel”
– Focused to accomplish single objective– Quick
• Built and modified rapidly with CASE tools
19
![Page 20: IAD 2263: System Analysis and Design Chapter 3: Investigating System Requirements.](https://reader036.fdocuments.net/reader036/viewer/2022062407/56649f515503460f94c75408/html5/thumbnails/20.jpg)
Distribute and Collect Questionnaires
• Limited and specific information from a large number of stakeholders
• Preliminary insight into business
• Not well suited for gathering detailed information
• Closed-ended questions direct person answering question
• Open-ended questions encourage discussion and elaboration
20
![Page 21: IAD 2263: System Analysis and Design Chapter 3: Investigating System Requirements.](https://reader036.fdocuments.net/reader036/viewer/2022062407/56649f515503460f94c75408/html5/thumbnails/21.jpg)
Class Activity- Case Study on activity
diagram• Develop an activity diagram based on the following narrative.
– The purchasing department handles purchase requests from other departments in the company. People in the company who initiate the original purchase request are the "customers" of the purchasing department. A case worker within the purchasing department receives that request and monitors it until it is ordered and received.
– Case workers process requests for the purchase of products under $1,500, write a purchase order, and then send it to the approved vendor. Purchase requests over $1,500 must first be sent out for bid from the vendor that supplies the product. When the bids return, the case worker selects one bid. Then, he or she writes a purchase order and sends it to the vendor.
![Page 22: IAD 2263: System Analysis and Design Chapter 3: Investigating System Requirements.](https://reader036.fdocuments.net/reader036/viewer/2022062407/56649f515503460f94c75408/html5/thumbnails/22.jpg)
Case Study
Answer
![Page 23: IAD 2263: System Analysis and Design Chapter 3: Investigating System Requirements.](https://reader036.fdocuments.net/reader036/viewer/2022062407/56649f515503460f94c75408/html5/thumbnails/23.jpg)
THANKS
You are never too old to set another goal or to dream a new dream.
~C. S. Lewis~