1 SYS366 Week 3 Lecture 1 Introduction to Requirements Gathering: Part 1.
-
Upload
domenic-white -
Category
Documents
-
view
225 -
download
8
Transcript of 1 SYS366 Week 3 Lecture 1 Introduction to Requirements Gathering: Part 1.
![Page 1: 1 SYS366 Week 3 Lecture 1 Introduction to Requirements Gathering: Part 1.](https://reader033.fdocuments.in/reader033/viewer/2022051315/56649e405503460f94b3155f/html5/thumbnails/1.jpg)
1
SYS366
Week 3 Lecture 1Introduction to
Requirements Gathering: Part 1
![Page 2: 1 SYS366 Week 3 Lecture 1 Introduction to Requirements Gathering: Part 1.](https://reader033.fdocuments.in/reader033/viewer/2022051315/56649e405503460f94b3155f/html5/thumbnails/2.jpg)
2
Today Business Systems Projects Why do Projects Fail? The importance of Stakeholders
![Page 3: 1 SYS366 Week 3 Lecture 1 Introduction to Requirements Gathering: Part 1.](https://reader033.fdocuments.in/reader033/viewer/2022051315/56649e405503460f94b3155f/html5/thumbnails/3.jpg)
3
What is a system? A combination of hardware and
software that meets the needs of a business.
A collection of inter-related components that collect, process, store and provide as output the information needed to complete business tasks and to make business decisions.
![Page 4: 1 SYS366 Week 3 Lecture 1 Introduction to Requirements Gathering: Part 1.](https://reader033.fdocuments.in/reader033/viewer/2022051315/56649e405503460f94b3155f/html5/thumbnails/4.jpg)
4
Types of systems? Office Systems
Productivity tools available to employees on a desk top.
Electronic Mail, Word Processing, Database Management, Spreadsheets, Desktop Publishing, Presentation Graphics and so on.
![Page 5: 1 SYS366 Week 3 Lecture 1 Introduction to Requirements Gathering: Part 1.](https://reader033.fdocuments.in/reader033/viewer/2022051315/56649e405503460f94b3155f/html5/thumbnails/5.jpg)
5
Types of systems? Operational (Transaction
Processing) Systems Take care of the day-to-day
processing of the business Information about the transactions
that affect the organization are captured and recorded
![Page 6: 1 SYS366 Week 3 Lecture 1 Introduction to Requirements Gathering: Part 1.](https://reader033.fdocuments.in/reader033/viewer/2022051315/56649e405503460f94b3155f/html5/thumbnails/6.jpg)
6
Types of systems? Management Information Systems
Uses operational systems’ information to give management the information needed to make management decisions
![Page 7: 1 SYS366 Week 3 Lecture 1 Introduction to Requirements Gathering: Part 1.](https://reader033.fdocuments.in/reader033/viewer/2022051315/56649e405503460f94b3155f/html5/thumbnails/7.jpg)
7
Types of systems? Executive Information Systems
Provide information to executives on how their company is doing relative to the industry
![Page 8: 1 SYS366 Week 3 Lecture 1 Introduction to Requirements Gathering: Part 1.](https://reader033.fdocuments.in/reader033/viewer/2022051315/56649e405503460f94b3155f/html5/thumbnails/8.jpg)
8
Types of systems? Decision Support Systems
Systems that allow a user to explore the impact of available options or decisions
‘What if’ analysis
![Page 9: 1 SYS366 Week 3 Lecture 1 Introduction to Requirements Gathering: Part 1.](https://reader033.fdocuments.in/reader033/viewer/2022051315/56649e405503460f94b3155f/html5/thumbnails/9.jpg)
9
Types of systems? Expert Systems
Simulate human reasoning and decision-making.
Artificial Intelligence.
![Page 10: 1 SYS366 Week 3 Lecture 1 Introduction to Requirements Gathering: Part 1.](https://reader033.fdocuments.in/reader033/viewer/2022051315/56649e405503460f94b3155f/html5/thumbnails/10.jpg)
10
Types of Systems
Information systems Collection of interrelated
components that collect, process, store, and provide as output the information needed to complete business processes
![Page 11: 1 SYS366 Week 3 Lecture 1 Introduction to Requirements Gathering: Part 1.](https://reader033.fdocuments.in/reader033/viewer/2022051315/56649e405503460f94b3155f/html5/thumbnails/11.jpg)
11
Flow of Information Horizontally - information flows
across departments Vertically - information needs of
clerical staff, middle management, and senior executives
![Page 12: 1 SYS366 Week 3 Lecture 1 Introduction to Requirements Gathering: Part 1.](https://reader033.fdocuments.in/reader033/viewer/2022051315/56649e405503460f94b3155f/html5/thumbnails/12.jpg)
12
Information Systems
IS PlanningLevel
Type of planning Typical IS applications
Organizational Unit
Responsible for Developing
Strategic Strategies in support of organizational long-term objectives
Market and sales analysis, Product planning, Performance evaluation
Senior Management/ Executives
Tactical Policies in support of short-term goals and resource allocation
Budget analysis, Salary forecasting, Inventory scheduling, Customer service
Middle Management
Operational Day-to-day staff activities and production support
Payroll, Invoicing, Purchasing, Accounting
Lower Management; Operational
![Page 13: 1 SYS366 Week 3 Lecture 1 Introduction to Requirements Gathering: Part 1.](https://reader033.fdocuments.in/reader033/viewer/2022051315/56649e405503460f94b3155f/html5/thumbnails/13.jpg)
13
Today Business Systems Projects Why do Projects Fail? The importance of Stakeholders
![Page 14: 1 SYS366 Week 3 Lecture 1 Introduction to Requirements Gathering: Part 1.](https://reader033.fdocuments.in/reader033/viewer/2022051315/56649e405503460f94b3155f/html5/thumbnails/14.jpg)
14
What is a Project? Sequence of unique, complex,
connected activities having one goal and that must be completed by a specific time, within a specific budget and according to spec
![Page 15: 1 SYS366 Week 3 Lecture 1 Introduction to Requirements Gathering: Part 1.](https://reader033.fdocuments.in/reader033/viewer/2022051315/56649e405503460f94b3155f/html5/thumbnails/15.jpg)
15
Project Initiation: How are Projects Chosen?
Long-term information systems strategic plan (top-down)
Department managers or process managers (bottom-up)
Response to outside forces Legislative changes Market forces Competition
![Page 16: 1 SYS366 Week 3 Lecture 1 Introduction to Requirements Gathering: Part 1.](https://reader033.fdocuments.in/reader033/viewer/2022051315/56649e405503460f94b3155f/html5/thumbnails/16.jpg)
16
Strategic Planning Strategic Planning involves
determining long-term objectives by analyzing the strengths and weaknesses of an organization, studying opportunities and threats in the business environment, predicting future trends, and projecting the need for new products and services.
![Page 17: 1 SYS366 Week 3 Lecture 1 Introduction to Requirements Gathering: Part 1.](https://reader033.fdocuments.in/reader033/viewer/2022051315/56649e405503460f94b3155f/html5/thumbnails/17.jpg)
17
Strategic Plan Helps determine which projects go
ahead
![Page 18: 1 SYS366 Week 3 Lecture 1 Introduction to Requirements Gathering: Part 1.](https://reader033.fdocuments.in/reader033/viewer/2022051315/56649e405503460f94b3155f/html5/thumbnails/18.jpg)
18
How do you get projects justified?
Understand the relationship to the Strategic Plan
Support from Stakeholders Understand and quantify hard &
soft benefits Understand and calculate one-time
and ongoing costs
![Page 19: 1 SYS366 Week 3 Lecture 1 Introduction to Requirements Gathering: Part 1.](https://reader033.fdocuments.in/reader033/viewer/2022051315/56649e405503460f94b3155f/html5/thumbnails/19.jpg)
19
Some IT Examples
Software/system development Package implementation Selection of a turnkey solution Technology implementation Business process re-engineering Component assembly
![Page 20: 1 SYS366 Week 3 Lecture 1 Introduction to Requirements Gathering: Part 1.](https://reader033.fdocuments.in/reader033/viewer/2022051315/56649e405503460f94b3155f/html5/thumbnails/20.jpg)
20
Hard vs Soft Benefits Hard- quantifiable in terms of
dollars Soft - Intangible
![Page 21: 1 SYS366 Week 3 Lecture 1 Introduction to Requirements Gathering: Part 1.](https://reader033.fdocuments.in/reader033/viewer/2022051315/56649e405503460f94b3155f/html5/thumbnails/21.jpg)
21
Justification based on benefit Cost Savings New Services to clients Mandatory changes Strategic advantage Technical reasons
![Page 22: 1 SYS366 Week 3 Lecture 1 Introduction to Requirements Gathering: Part 1.](https://reader033.fdocuments.in/reader033/viewer/2022051315/56649e405503460f94b3155f/html5/thumbnails/22.jpg)
22
Project Parameters
Scope Quality--product and process Cost Time Resources Scope and Quality ARE DIRECTLY
IMPACTED BY Cost, Time, Resources
![Page 23: 1 SYS366 Week 3 Lecture 1 Introduction to Requirements Gathering: Part 1.](https://reader033.fdocuments.in/reader033/viewer/2022051315/56649e405503460f94b3155f/html5/thumbnails/23.jpg)
23
What is project scope? A definition of the boundaries of the project
![Page 24: 1 SYS366 Week 3 Lecture 1 Introduction to Requirements Gathering: Part 1.](https://reader033.fdocuments.in/reader033/viewer/2022051315/56649e405503460f94b3155f/html5/thumbnails/24.jpg)
24
When do you define scope? You define scope at the beginning of the project
You manage and control scope throughout the life of the project
![Page 25: 1 SYS366 Week 3 Lecture 1 Introduction to Requirements Gathering: Part 1.](https://reader033.fdocuments.in/reader033/viewer/2022051315/56649e405503460f94b3155f/html5/thumbnails/25.jpg)
25
How do you define scope? You talk to your stakeholders!
![Page 26: 1 SYS366 Week 3 Lecture 1 Introduction to Requirements Gathering: Part 1.](https://reader033.fdocuments.in/reader033/viewer/2022051315/56649e405503460f94b3155f/html5/thumbnails/26.jpg)
26
How do you define scope? In addition to talking to your stakeholders!, You research and clarify You document Identify expected capabilities of new
system Develop Business Use Case Diagrams Develop textual Business Use Case
descriptions Ask, “Is problem understood?”
![Page 27: 1 SYS366 Week 3 Lecture 1 Introduction to Requirements Gathering: Part 1.](https://reader033.fdocuments.in/reader033/viewer/2022051315/56649e405503460f94b3155f/html5/thumbnails/27.jpg)
27
Today Business Systems Projects Why do Projects Fail? The importance of Stakeholders
![Page 28: 1 SYS366 Week 3 Lecture 1 Introduction to Requirements Gathering: Part 1.](https://reader033.fdocuments.in/reader033/viewer/2022051315/56649e405503460f94b3155f/html5/thumbnails/28.jpg)
28
Why is scope important?
One of the biggest factors in project success Good scope definition = good client and IT
understanding of what will be delivered and when
Ensures you understand WHERE you are going, HOW you will get there and WHEN you will arrive
This is where most projects start to fail!
![Page 29: 1 SYS366 Week 3 Lecture 1 Introduction to Requirements Gathering: Part 1.](https://reader033.fdocuments.in/reader033/viewer/2022051315/56649e405503460f94b3155f/html5/thumbnails/29.jpg)
29
What defines project success?
On time Within budget Expected results achieved
![Page 30: 1 SYS366 Week 3 Lecture 1 Introduction to Requirements Gathering: Part 1.](https://reader033.fdocuments.in/reader033/viewer/2022051315/56649e405503460f94b3155f/html5/thumbnails/30.jpg)
30
The evil truth
Only 16.2% of all IT projects succeed! Fully functional, on time, within
budget Some studies show this as low
as 10%.
![Page 31: 1 SYS366 Week 3 Lecture 1 Introduction to Requirements Gathering: Part 1.](https://reader033.fdocuments.in/reader033/viewer/2022051315/56649e405503460f94b3155f/html5/thumbnails/31.jpg)
31
The evil truth
52.7% are “challenged” --less than fully functional, over budget, late
The remaining 31.1% get cancelled before they are fully implemented
![Page 32: 1 SYS366 Week 3 Lecture 1 Introduction to Requirements Gathering: Part 1.](https://reader033.fdocuments.in/reader033/viewer/2022051315/56649e405503460f94b3155f/html5/thumbnails/32.jpg)
32
The evil truth
Estimated cost of challenged and cancelled projects in 1 year?
$140 billion
![Page 33: 1 SYS366 Week 3 Lecture 1 Introduction to Requirements Gathering: Part 1.](https://reader033.fdocuments.in/reader033/viewer/2022051315/56649e405503460f94b3155f/html5/thumbnails/33.jpg)
33
More evil truth The average project:
exceeds planned budget by 90% exceeds schedule by 120%
How to estimate: take your best, most honest
guess multiply that by 4
![Page 34: 1 SYS366 Week 3 Lecture 1 Introduction to Requirements Gathering: Part 1.](https://reader033.fdocuments.in/reader033/viewer/2022051315/56649e405503460f94b3155f/html5/thumbnails/34.jpg)
34
Why do projects fail? Objectives not fully specified (51%) Poor planning/estimating (48%) New technology (45%) Poor or no project management
discipline (42%) Inadequate skills (42%)
and so on…
![Page 35: 1 SYS366 Week 3 Lecture 1 Introduction to Requirements Gathering: Part 1.](https://reader033.fdocuments.in/reader033/viewer/2022051315/56649e405503460f94b3155f/html5/thumbnails/35.jpg)
35
Today Business Systems Projects Why do Projects Fail? The importance of Stakeholders
![Page 36: 1 SYS366 Week 3 Lecture 1 Introduction to Requirements Gathering: Part 1.](https://reader033.fdocuments.in/reader033/viewer/2022051315/56649e405503460f94b3155f/html5/thumbnails/36.jpg)
36
To A Avoid Disaster “The team must
Establish a good understanding of the stakeholder community
Demonstrate an understanding of the problem to be solved…”*
*Use Case Modeling by Bittner and Spence, p. 50.
![Page 37: 1 SYS366 Week 3 Lecture 1 Introduction to Requirements Gathering: Part 1.](https://reader033.fdocuments.in/reader033/viewer/2022051315/56649e405503460f94b3155f/html5/thumbnails/37.jpg)
37
To A Avoid Disaster “The team must
Capture the real needs of the stakeholders and the system features required to fulfill them
Ensure that the views of the stakeholder community are actively and appropriately represented throughout the project” *
*Use Case Modeling by Bittner and Spence, p. 50.
![Page 38: 1 SYS366 Week 3 Lecture 1 Introduction to Requirements Gathering: Part 1.](https://reader033.fdocuments.in/reader033/viewer/2022051315/56649e405503460f94b3155f/html5/thumbnails/38.jpg)
38
Who is a Stakeholder? “An individual who is materially affected by
the outcome of the system or the project (s) producing the system” *
Or the people who suffer from the problem being addressed *
*Use Case Modeling by Bittner and Spence, p. 51.
![Page 39: 1 SYS366 Week 3 Lecture 1 Introduction to Requirements Gathering: Part 1.](https://reader033.fdocuments.in/reader033/viewer/2022051315/56649e405503460f94b3155f/html5/thumbnails/39.jpg)
39
Categories of Stakeholders
Five primary categories Users Sponsors Developers Authorities Customers
![Page 40: 1 SYS366 Week 3 Lecture 1 Introduction to Requirements Gathering: Part 1.](https://reader033.fdocuments.in/reader033/viewer/2022051315/56649e405503460f94b3155f/html5/thumbnails/40.jpg)
40
User Stakeholders Those who actually use the system Technology Adopters
Interested in using all of the features of the system; in pushing it to the limit of its capabilities
Standard Users Not interested in using all of the
features of the system. Rather they want a system that allows them to perform their business processes simply and in the same way that they are used to performing them
![Page 41: 1 SYS366 Week 3 Lecture 1 Introduction to Requirements Gathering: Part 1.](https://reader033.fdocuments.in/reader033/viewer/2022051315/56649e405503460f94b3155f/html5/thumbnails/41.jpg)
41
Standard Users Those in day-to-day business
operations use and change information
Those using queries view calculated/collected information
Management use reports, statistics demand controls
Executives strategic issues
![Page 42: 1 SYS366 Week 3 Lecture 1 Introduction to Requirements Gathering: Part 1.](https://reader033.fdocuments.in/reader033/viewer/2022051315/56649e405503460f94b3155f/html5/thumbnails/42.jpg)
42
User Stakeholders Non-human users
Mechanical devices that the system must interact with
Other business areas Other systems
![Page 43: 1 SYS366 Week 3 Lecture 1 Introduction to Requirements Gathering: Part 1.](https://reader033.fdocuments.in/reader033/viewer/2022051315/56649e405503460f94b3155f/html5/thumbnails/43.jpg)
43
Sponsor Stakeholders Indirect users Or those actually paying for the
development of the system Or those affected only by the business
outcomes that the system influences
![Page 44: 1 SYS366 Week 3 Lecture 1 Introduction to Requirements Gathering: Part 1.](https://reader033.fdocuments.in/reader033/viewer/2022051315/56649e405503460f94b3155f/html5/thumbnails/44.jpg)
44
Developer Stakeholders Those involved in the production and
maintenance
![Page 45: 1 SYS366 Week 3 Lecture 1 Introduction to Requirements Gathering: Part 1.](https://reader033.fdocuments.in/reader033/viewer/2022051315/56649e405503460f94b3155f/html5/thumbnails/45.jpg)
45
Authority Stakeholders Those who are expert in a particular
aspect of the problem or solution domain Ministries Technical experts Domain experts
![Page 46: 1 SYS366 Week 3 Lecture 1 Introduction to Requirements Gathering: Part 1.](https://reader033.fdocuments.in/reader033/viewer/2022051315/56649e405503460f94b3155f/html5/thumbnails/46.jpg)
46
Customer Stakeholders Those doing business with the company
![Page 47: 1 SYS366 Week 3 Lecture 1 Introduction to Requirements Gathering: Part 1.](https://reader033.fdocuments.in/reader033/viewer/2022051315/56649e405503460f94b3155f/html5/thumbnails/47.jpg)
47
Over to You Let’s get started on Work Package
1 In-Class Exercise 5