janinejams

Niño Francisco Alamol,

V 1.0 – January 05, 2021

MRT_FARE_MATRIX
ADMIN_USER_EPIC

© Sample Business Requirement Document

Developing the Card-Based MRT Fare Matrix System

janinejams

Contents for

Parent USNNN
Child USNNN ‘s

1.0 Document Management.......................................................................................................................... 3

Background.................................................................................................................................................. 4
Requirement................................................................................................................................................ 4
Performance................................................................................................................................................. 4
Dependencies............................................................................................................................................... 4
Assumptions................................................................................................................................................. 4
Pending/Issues............................................................................................................................................. 4
Verification points........................................................................................................................................ 4
Implementation Requirements..................................................................................................................... 6
Database changes......................................................................................................................................... 7
Software Design Specification....................................................................................................................... 7
Process Flows............................................................................................................................................... 7
Appendix...................................................................................................................................................... 7

© Sample Business Requirement Document

Developing the Card-Based MRT Fare Matrix System

janinejams

1.0 Document Management

This should be approved (APP) by JC before going to dev team

Version/Status Date Author Description (what has been changed high level) i.e. field
name
1.0 WD 01/05/2021 NFCA Initial draft

Note: WD (working draft); D (draft); App (approved/signed off)

© Sample Business Requirement Document

Developing the Card-Based MRT Fare Matrix System

janinejams

Background
The application is to be developed to simulate the process of a real card-based MRT Fare Matrix system.

Requirement / Epic
For the epic, the system must be able to login users as well as register, remove, change roles or deny
access to users of the system. This epic is limited only to the aforementioned requirements, other
requirements will have their own epics and user stories

Dependencies
A seeded database should be present with default accounts in place.

Assumptions
1. There is an existing default admin account in place.
2. Roles should also be seeded initially but open to CRUD operations

Pending/Issues
N/A

Verification Points | User Stories

Registration | US_001_001
1. User is able to register as a new user so that he can have a proper credential that has relevant
authorization to perform certain tasks.
Acceptance Criteria
1. System should have register page where unregistered users can sign up to be able to access the
system.
2. User can input details needed to register to the system.
3. After a successful registration, an email is sent with a URL link that user needs to click to be able to
verify email address used.
4. User is automatically logged in when the URL is clicked - but URL must be only clicked once,
repeating clicks should redirect to an Link Has Expired Page.

© Sample Business Requirement Document

Developing the Card-Based MRT Fare Matrix System

janinejams

Login | US_001_002
1. User is able to login on the system - upon logging in role of the user will be fetched, that will
determine which pages or actions the user is allowed to do.
Acceptance Criteria
1. System should be able to identify the access role that is given to the user logged in. A separate
document will be provided for the mapping of pages that each role is allowed to navigate and
perform actions to.
Forget Password | US_001_003
1. User is able to change password by clicking a ‘Forget Password’ on the Login Page. This will redirect
user to a Forget Password Page where user must input email address registered.
Acceptance Criteria
2. System must send email to the user with a URL link.
3. User receives an email containing the URL link that navigates to the Change Password Page.
4. System must not allow previous password to be used.
5. System must verify that new password adheres to these rules:
i. At least one upper case
ii. At least one lower case
iii. At least one non-alphanumeric character
iv. At least one numerical character
v. Must not contain user name
vi. Should be at least 8 characters long
2.
Image 1.0
N/A

Image 1.1
N/A

Image 1.2
N/A

Implementation Requirements

© Sample Business Requirement Document

Developing the Card-Based MRT Fare Matrix System

janinejams

1. Database should be set and seeded initially (for first deployment only)

Data source/input : US_001_001

Field Name Display Data Value Data Required Source Sample*** DB
Type Type Column
Search Filter Text / String Text / String Y Free Text

Field Name Display Data Value Data Required Source Sample*** DB

Type Type Column
Search Filter Text / String Text / String Y Free Text

#US_001_002
Field Name Display Data Value Data Required Source Sample*** DB
Type Type Column
Search Filter Text / String Text / String Y Free Text

#US_001_003
Field Name Display Data Value Data Required Source Sample*** DB
Type Type Column
Search Filter Text / String Text / String Y Free Text

Database changes

Software Design Specification

Process Flows
1. User logs in to the system (ERP)
2. User performs operations described above
3. User logs out of the system

© Sample Business Requirement Document

Developing the Card-Based MRT Fare Matrix System

janinejams

Signoff

Discipline Name Date

Professor
Sol. Arch Nino Francisco Alamo
Developer Nino Francisco Alamo
Marketing
Director / Direct
Supervisor
Stakeholders:

Appendix

© Sample Business Requirement Document

Developing the Card-Based MRT Fare Matrix System