Embed Size (px)
Citation preview
1
BTS330
Introduction to Stakeholders & Business Areas
2
Today
More on Requirements Gathering Identifying Stakeholders Identifying Business Areas
3
Requirements Gathering
Analyst needs to find out what the user requires in the new system or what the user requires to be changed in an existing system Gather the requirements by doing
fact finding Document the requirements
4
Requirements Gathering For a new system, analyst needs to
find out: Functionality
What are the activities the system needs to perform?
How is the user to interact with the system? Are other systems to interact with the
system? Data needs
What information is needed?
5
Requirements Gathering
For an existing system, analyst needs to find out: Functionality
Some of the functionality of the existing system will be included in the new system
Some of the data of the existing system may need to be migrated into the new system
6
Requirements Gathering
What is the analyst determining? Scope of the System
Who is going to use the system? What is the new system going to do? What information does the system need
to have available? How large is this system going to be? How small is the system going to be ?
7
Requirements Gathering
Scope of the System
Functional Technical DataRequirementsRequirements Requirements
8
Requirements Gathering Functional Requirements
Describes what a system does or is expected to do
Includes: Descriptions of the processing which the system will
be required to carry out Details of the inputs into the system from paper forms
and documents or the interactions between people and the system or transfers from other systems
Details of the outputs that are expected from the system in the form of printed documents and reports, screen displays and transfers to other systems
9
Requirements Gathering
Technical Requirements Describes the aspects of the system
that are concerned with how well it provides the functional requirements.
Includes: Performance criteria Anticipated volumes of data Security requirements
10
Requirements Gathering
Data Requirements Describes what information the
system is going to need or produce – really a part of Functional and Technical Requirements
Includes Details of the data that must be held in
the system
11
Requirements Gathering Techniques for Gathering
Requirements Interviews Prototypes Questionnaires Observation Reviewing existing documentation Review Strategic and Tactical Plans Other Methods
12
Requirements Gathering As part of the process to begin
gathering requirements, it is necessary to understand the organizational structure of the organization to ensure that you use the correct people within the organization to get useful requirements
Need to identify where those people are
13
Today
More on Requirements Gathering Identifying Stakeholders Business Areas
14
Identifying Stakeholders
A stakeholder is an individual who is materially affected by the outcome of the system or the project(s) producing the system
Need to conduct a stakeholder analysis
15
Identifying Stakeholders
A stakeholder analysis identifies: the key stakeholders the organizations they are with their overall organizational
responsibilities their relationship to the project
16
Identifying Stakeholders
Types of stakeholders: Users Sponsors Developers Authorities Customers
17
Identifying Stakeholders
Users/Sponsors/Authorities/Customers: Provide user requirements for
validation Developers:
Provide the framework within which the system can be developed (architecture)
18
Identifying Stakeholders
*Use Case Modeling by Bittner and Spence, Figure 3-3, p. 56.
19
Identifying Stakeholders
Who are the users of the system? Who is the sponsor of the
development? Who else will be affected by the
outputs that the system produces? Who will evaluate and sign off on
the system when it is delivered and deployed?
20
Identifying Stakeholders
Are there any other internal or external users of the system whose needs must be addressed?
Are there regulatory bodies or standards organizations to which the system must comply?
Is there anyone else?
21
Today
More on Requirements Gathering Identifying Stakeholders Business Areas
22
Business Areas
Organizational grouping of responsibilities
Discovered from stakeholder analysis
The organizational areas needed to support a business
23
Business Areas
To identify a business or organizational area, think of the business functions needed to support the business and group them into major areas of responsibility
We will create a ‘package’ for each business area
24
Business Areas
i.e. Loan Processing System Loan Submission
Submit Load Request Evaluate Load Request Loan Program Inquiry Generate Loan Agreement
Credit Management Retrieve Customer Profile Request Credit Report Perform Credit Analysis
25
Business Areas
i.e. Loan Processing System Loan Account Maintenance & Care
Close Out Loan Loan Account Status Inquiry Generate Late Notice
Loan Portfolio Analysis & Reporting Generate Account Activity Sheet Delinquent Loan Inquiry Portfolio Performance Inquiry
26
Business Areas
i.e. Gym Management System Employee Management Class Management Membership Services Management ProShop Management
27
Identifying Business Areas
Based on your experience at Seneca College, identify as many business areas as you can for the Book Store at Seneca College.
28
Identifying Business Areas
In class exercise: A Movie Theatre think of the processing to support a
movie theatre and group the business functions a movie theatre provides and group these into major areas of responsibility
