BUSINESS ANALYSIS DOCUMENT

Online

1. Identifying stakeholder....................................................................................................................3
Stakeholder List:...............................................................................................................................3
RACI Matrix:.....................................................................................................................................4
2. Identify the problem statement in this system................................................................................4
Fish-bone Diagram...........................................................................................................................4
3. Identify objectives of the new Library Management System...........................................................5
Objectives:.......................................................................................................................................5
4. Create as-is and future process map (using flowcharts)..................................................................5
As-is process.....................................................................................................................................5
To-be process...................................................................................................................................6
5. Find out the scope of the Canteen Ordering System........................................................................6
Use-case Diagram:...........................................................................................................................7
6. Write down the main features that need to be developed..............................................................8
Functional De-composition Diagram:...............................................................................................8
7. Write the in-scope and out-of-scope items for this software..........................................................8
In Scope:...........................................................................................................................................8
Out of Scope:...................................................................................................................................9
8. Draw an activity diagram for the system..........................................................................................9
Order and delivery activity diagram.................................................................................................9
9. Draw an ER diagram of the system................................................................................................10
Entity Relationship Diagram:..........................................................................................................10
10. Write out the business requirements, both the functional and nonfunctional requirements.....10
Business Requirements:.................................................................................................................10
Functional and Non-functional requirements:...............................................................................11
11. Draw wireframes or mock screens...............................................................................................11
Wireframe: Book record creation..................................................................................................11
Wireframe: Issue book...................................................................................................................12
Canteen Ordering System

1. Identifying stakeholder
Create a list of stakeholders (as taught in Business Analysis Planning and Monitoring
knowledge Area)

Stakeholder List:

Actor / Role Responsibilities Influence Interest Key Engagement Strategy

Stanford Board of Monitor initiative High Low Ensure satisfaction. Project
Trustees status reporting for key
milestones.
Dean of the University Sponsor for the project. High Medium Work closely. Gather
Interested in the benefit Stakeholder requirements
realized from the and keep informed regularly
project on the progress.
Library Staff Users of the online Medium High Involve in requirement
Library Management gathering,
system keep informed regularly on
the progress.
May include for sprint
reviews and UAT
University Faculty Users of the online Medium High Involve in requirement
Representative Library Management gathering,
system, have a say on keep informed regularly on
the requirements of the the progress.
system May include for sprint
reviews and UAT
University Student Users of the online Medium High Involve in requirement
Representative Library Management gathering,
system, have a say on keep informed regularly on
the requirements of the the progress.
system May include for sprint
reviews and UAT
Students of the End users of the online Low Medium Inform when closer to
university ordering system deployment

University Faculty End users of the online Low Medium Inform when closer to
ordering system deployment
Implementation Medium High Active engagement
Manager throughout the project
Domain SME Medium High Active engagement in
requirement gathering
sessions, Include for sprint
reviews and UAT
Implementation SME Medium High Active engagement
throughout the project
Developers Low High Active engagement
throughout the project
Test Manager Low High Active engagement
throughout the project
Test Analyst Low High Active engagement
throughout the project
RACI Matrix:

RACI for key deliverables is in the attached.

2. Identify the problem statement in this system.

Problem:
Managing library manually was time consuming and ineffective

Root cause analysis of the problem was done to identify the key concerns and the factors which
contributed to it.

Fish-bone Diagram

No reports

 Stanford has over 4 million books

 A lot of time is wasted managing the manual library.
 The number of employees needed to manage the library is high.
 Fine calculation is a tedious and time-consuming affair.
 No reports could be generated on books issued due to the manual system.
 Students could deposit the books only in the library timings.

3. Identify objectives of the new Library Management System.

Objectives:
The new library management system needs to address the problems of the current system and
make it more efficient. Its main objectives are as below:
1. Reduce overheads and increase the productivity of the library staff by a minimum of 30%
within 6 months from following the release of the new online ordering system
Scale: Time taken to address one user must be reduced
• Previous average handling time: 5 mins (avg.)
• Must Plan for: 2 – 3 mins (avg.)
2. Reduce the Library operating system by 15% within a period of 12 months, following the
initial release of the new system.
3. Improve the funds available to run the library by effectively tracking the collection of fines,
alerting any attempts to steal books
4. Making library management system an automated process with RFID tracking, the library
will be able to operate with lesser manpower.

4. Create as-is and future process map (using flowcharts).

You can use any of the popular tools in the market like Microsoft Visio, Lucid Chart, Creately,
Pidoco, or Balsamiq

As-is process

To-be process
5. Find out the scope of the Canteen Ordering System.
To find the scope you can use the case diagram (UML) or context diagram for the same.
Scope modelling techniques:
Use-case Diagram:
Create a use case diagram including all the actors and processes for an end to end process of the
system.
6. Write down the main features that need to be developed.
Functional De-composition Diagram:

7. Write the in-scope and out-of-scope items for this software.

In Scope
● Mention the name of features and what they are used for.
Out of Scope
● What are the facilities or features—for both patron and the canteen—the are out of scope or
cannot be implemented now.

In Scope:
- Building smart application for library management linking RFID to the books for ease of
tracking
- Application would include Login feature which allows Library staff, university faculty and
students and university management to sign-up and login to the system
- Application would include User services feature which allows users of the library system to
browse books, return or issue books, view books in the account and its due dates, receive
notification on due dates and fine applicable, access to free e-journals and e-books
- Application would include Books Management feature which allows library staff to record
book details the first time, link RFID with the book it is tagged to, Categorise books, assign
due dates and fines accordingly
- Application would support returns from a Dropbox. This allows members to drop books to
be returned into a drop box which has a RFID scanner and updates the system based on the
RFID tag.
- Application would allow the information of book’s status to be read by an RFID scanning
interface, which can alert if the books is being taken out of the library premises without
being issued.
- Application would include Reporting feature which allows University management and
library staff to view reports to gain insights on the performance of the new application

Out of Scope:
- Books dropped into the dropbox but having fines
- Data entry for books that are currently checked out to users
- Books stolen from the dropbox

8. Draw an activity diagram for the system.

Preconditions and Triggers: Example

 What user/manager should be able to do in a step?

 What are the triggers?
 What is the basic flow?
 What are the data elements?
 In case of errors, what happens?

Order and delivery activity diagram

9. Draw an ER diagram of the system.
Create an ER Diagram for the system you have designed.

Entity Relationship Diagram:

10. Write out the business requirements, both the functional and
nonfunctional requirements.
Business Requirements:

1. Reduce overheads and increase the productivity of the library staff by a minimum of 30%
within 6 months from following the release of the new online ordering system
Scale: Time taken to address one user must be reduced
• Previous average handling time: 5 mins (avg.)
• Must Plan for: 2 – 3 mins (avg.)
3. Improve student engagement in the library
4. Making library management system an automated process with RFID tracking, the library
will be able to operate with lesser manpower.
5. Improve tracking of books, research papers, magazines and other materials in the library
6. Reduce the Library operating costs by 15% within a period of 12 months, following the initial
release of the new system.
Functional and Non-functional requirements:

11. Draw wireframes or mock screens

Draw wireframes or mock screens for any 2 of the features namely book record creation and any
other feature as deemed fit by the student. (Use the technique prototyping or wireframing that is
taught in the training)

Wireframe: Book record creation

Wireframe: Issue book