Hashir
User Management System
Business Requirements
Document (BRD)
V.0.1
May 23, 2022
User Management System (BRD),V.0.1 May 23, 2022
Document Information
Document History
Date Version Description Author
23/05/2022 0.1 Initial Draft Hashir
Definitions, Acronyms and Abbreviations
Term Explanation
Domain A group of web pages defined by a common address, or URL
URL Web address, such as www.hashir.com
BRD Business Requirements Document (this document)
Wireframe Layout and functional blueprint for key pages
Def6 or D6 Refers to the company Definition 6
S&P Strategy and Planning
KPI Key Performance Indicators
UX User Experience
CTA Call to Action
ROI Return on Investment
CTR Critical to ROI
References
Name Description/Path
Shared Extranet Site Shared repository for key documents, deliverables, and
action items: https://hashir.com/GLSEN/default.aspx
Non Functional Specifications Document outlining technical requirements and quality
attributes.
Z:\Website Redesign\Account Services Docs
Platform Recommendations Document outlining CMS considerations and
recommendations.
Z:\hashir\Website Redesign\Account Services Docs
2
User Management System (BRD),V.0.1 May 23, 2022
Contents
Document Information.................................................................................................................. 2
Document History................................................................................................................ 2
Definitions, Acronyms and Abbreviations.........................................................................2
References............................................................................................................................ 2
Introduction................................................................................................................................... 4
What This Is.......................................................................................................................... 4
Why it’s Useful...................................................................................................................... 4
Requirements................................................................................................................................ 5
Business Need/Problem Statement........................................................................................ 5
Request Summary.................................................................................................................. 5
Strategic Requirements....................................................................................................... 6
1.Login/ Signup page.................................................................................................................... 7
Procedures:............................................................................................................................ 7
Password Recovery............................................................................................................... 7
Created profiles :.................................................................................................................... 7
Screen #1....................................................................................................................................... 8
Fields specifications..................................................................................................................... 9
2.Dashboard................................................................................................................................ 10
Right side of Dashboard Screen........................................................................................... 10
Left side of Dashboard Screen.............................................................................................10
For example......................................................................................................................... 10
Screen 2.1 (admin Dashboard).................................................................................................. 11
For Example......................................................................................................................... 11
Screen 2.2.................................................................................................................................... 12
3.Roles (Screen # 03).................................................................................................................. 12
Left side................................................................................................................................ 13
Screen 03.1( Roles pages )........................................................................................................ 13
New role............................................................................................................................... 14
Screen # 3.2 (New Role Window)............................................................................................... 14
Test Role.............................................................................................................................. 14
Screen 3.3(Test role)................................................................................................................... 15
Edit role................................................................................................................................ 16
For example:........................................................................................................................ 16
Delete................................................................................................................................... 16
4. permissions............................................................................................................................. 17
3
User Management System (BRD),V.0.1 May 23, 2022
Introduction
What This Is
The purpose of the Business Requirements Document (BRD) is to express the
requirements made by client about Controlling and managing user access to IT
resources which is essential for any organization.
The primary audience for the document is the project team, and specifically the
functional groups that must determine how to implement the user management system,
service, etc.To meet the customers’ requirements. The team is responsible for
determining how to develop what the Business has requested.
This Document will be showing detailed overview of this that, what featues should be
Included and what should not (Extcluded).
Why it’s Useful
This Document will help in directioning Audience(which is mentioned above) to make
resolutions concerning project preference, design, and structure.Further it was essential
for the greater efficiency, as it will be playing role of a brigde between USM requestor
and the Project team.
4
User Management System (BRD),V.0.1 May 23, 2022
Requirements
Business Need/Problem Statement
Implementing user roles and permissions is one of the basic functionality to implement
in our web applications to restrict the specific user with only admin allowed to access.
For this purpose , DEFINITION6 has requested for a well mentained User Management
System for their better online and Secured platform.
User Management System is a role-based system created for Security purposes
and permisions.
It also saves the last login date of each user with proper status and error
handling.
It also logs every model operation in the database.
if the user does not have certain permissions, they will be shown an error page.
Request Summary
create a personalized, centralized identity for each of their end users. Some common
user attributes include things like first and last name, email/phone number, address,
etc.Overall the system should be having all these functionalities listed below (as per
request:
RS.SERIAL REQUESTED ATTRIBUTES
RS.1 Role-Based User Management
RS.2 Create roles based on permissions
RS.3 assign roles to users
RS.4 Log every model event
RS.5 Save Last Login Date
RS.6 Proper Error Handling
RS.7 Shows Proper Error Messages
RS.8 Mobile Friendly Interface
RS.9 Login
RS.10 Register
RS.11 AdminLte Theme Included
5
User Management System (BRD),V.0.1 May 23, 2022
Access and Permissions
Admin should have access over all roles, permissions and users wheather the user
will have very limited access and could only access authorities which will be
assigned by admin. If any user trys to access those authorities which admin has not
assigned to user then in that case a error page will be displayed to user as shown in
Screen 0.
Screen 0
6
User Management System (BRD),V.0.1 May 23, 2022
Strategic Requirements
The primary function of the system is to to manage and monitor user
access permissions and access rights to
files
systems
services
Protect organizations from data loses
Protect securirt beaches
We will implement functionality to manage user operations like
User registration
User email verification
Login
Password
Reset and
Edit profile. We will also create Admin panel to manage users at
admin end to create new user, edit existing users details and delete
user.
Following web pages should be mentained in an appropriate maner(which
should have permission systems) :
Login/ Signup page.
Dashboard.
Roles.
Permissions.
7
User Management System (BRD),V.0.1 May 23, 2022
Users.
Posts.
1.Login/ Signup page
In screen 1 , login page should be designed so user can register himself. After
Registration user can log in with own email id and password.
Procedures:
User Registration
User Login
Forgot Password
Password Recovery
if the user forgot their own password then user can request for password
using their own email id.
For Forgot password , user have to provide his gmail credetails in password-
recovery. After that email function will work.
Created profiles :
Once a user creates his or her profile by performing registration , then the relavent
profile details should be saved in a linked database.for log in, the same database
should be checked for the given details if someone try to login and put his or her details
like email and password.
8
User Management System (BRD),V.0.1 May 23, 2022
If record of the entered details is saved then one should be loged in successfully
otherwise error message shoukd be displayed in the screen that the you(the user)
needs to register first.
Screen #1
Overveiw and Design of screen should be mentained as per screen 1
given below.
9
User Management System (BRD),V.0.1 May 23, 2022
Fields specifications
10
User Management System (BRD),V.0.1 May 23, 2022
Field Description Data Type Char Screen Action/check associated
limit No
Email username or Varchar/ 15 S1 User have to enter his/her
email to text char username or email to login
login. /compulsory
/ Unique
Password Password of Varchar/ 30 S1 User will input the Password
User text char
/compulsory
Login Button used Button S1 Clicking the button will check for
for the User name and password
Submitting the in database, upon successful
the form validation user will route to
Home page the of application. In
case of failure of validation
relevant messages will populate
on page.
Remember Check box Check Box S1 Checking the box will save user
Me for Name & password for web
rememberin Browser
g user name
and
password for
Web
Browser.
Forget Link for link S1 Clicking the link will route the
password resetting user to page/popup, email will
Password be asked, and reset link will
send to email.
2.Dashboard
11
User Management System (BRD),V.0.1 May 23, 2022
Once the user or Admin logs in successfully, the very first page which should be
displayed is dashboard . Dashboard have to show the role of one, who logs in.Top most
section should have a search bar as if the user needs to search something with in his
profile, also shown in Screen 2.1 and 2.2.
Right side of Dashboard Screen
The top right side will have to show ones profile (picture).on clicking the profile picture
user should be able to proceed either by:
visiting his profile
log out if he done his activites.
Left side of Dashboard Screen
Left side of the Dashboard screen should have the column of all pages and methods
which cloud be visited as per the role.
For example :
if the person who logs in is admin then the left column will have all functional pages
with respect to admin which are shown in Screen 2.1:
Role
Permission
User
Post
Screen 2.1
12
User Management System (BRD),V.0.1 May 23, 2022
(admin Dashboard)
The very main difference between the admin and non admin(user page) is the
permissions difference i.e the admin will have all the permissions and have the authority
to even edit and assign permissions to the users.
For Example:
If the person who logs in is a writer then the left column will have all functional pages
with respect to writer which are shown in Screen 2.2:
13
User Management System (BRD),V.0.1 May 23, 2022
Screen 2.2
(Non Admin page /user page / Writer’s page )
3.Roles (Screen # 03)
Permission to access the Roles should only be given to Admin or in other words, the
admin should be the only one who have to had rights of accessing roles and also should
be able to perform opertions like:
Access
Create
Edit
Update
Delete
14
User Management System (BRD),V.0.1 May 23, 2022
Left side and the top most section of screen should be always same as it should be
showing the column of all pages and methods which cloud be visited as per the role and
the Profile and search bar.
In roles screen, there will three main columns as role names, permissions and actions
for admin(as it is admin only).So the admin should be able to check all the roles and
permissions, and can take necessary actions like Edit and Delete on existing roles.
In roles screen admin admin should be given the authority to make a new role.For that
purpose, there should be a button at upper right on screen with the name of New Role
as shown in screen 03.0
Screen 03.1
( Roles pages )
15
User Management System (BRD),V.0.1 May 23, 2022
New role
New role button will allow the admin to make a new role if nessesary. Clicking this
button will lead him/her to a new window where he/she can assign name of the new role
as well as its permissions as shown in the screen 3.1.
There should be a submit button at very bottom of this window.This button will simply
end the creation process of a new role by creating the specific role with specific
permissions.
Screen # 3.2
(New Role Window)
16
User Management System (BRD),V.0.1 May 23, 2022
Test Role
For the purpose of clear understanding, let suppose the admin created a new role with
the name of test role and allowed three(3) permissions to it as shown the above screen
3.2.newly created role (test role ) should be updated in the roles pages as shown in
screen 3.3.
Screen 3.3
(Test role)
17
User Management System (BRD),V.0.1 May 23, 2022
Edit role
Admin should also be able to edit the existing role as discussed earlier. So if admin
decides to edit any role by clicking the edit option, this will take him to the same window
as 3.2 as that window will easily allow him to make his desired changes in any role.
For example:
If the admin chooses to edit the writer’s role and edits it from the activity section, then
after clicking on submit buttom, roles screen will be updated with writer’s roles as shown
in screen 3.4:
Screen 3.4
(Edited Role)
18
User Management System (BRD),V.0.1 May 23, 2022
Delete
If admin simple clicks on delete option in activity section, then the specific role will be
deleted and vanished from the role screen.also a message will be displayed as
(delete message on successful delete)
4. Permissions
This section should only be accessable by the admin.in this section all the permissions
should be listed, along with allowing admin the full control over permissions.Admin
should be able to create a new permission and edit every existing permission and
delete as well.
Basic authorities to give admin with respect to permissions are:
Create new permission
Edit existing permission
Delete existing permission
19
User Management System (BRD),V.0.1 May 23, 2022
Screen 4.1
Permissions page (admin only)
Same as roles screen , admin should will also get full control authority over permissions
as mentioned above .So, when he/she wishes to create or edit a permission. It will take
him/her to a different window as shown in screen 4.2
This page will have two major fields in it :
Enter permission
Submit
20
User Management System (BRD),V.0.1 May 23, 2022
Screen 4.2
Create or Edit permission
Test permission
These two fields will works to take input of name of permission from admin to save the
given permission to database
Let, if admin select to create a new permission with the name test permission and click
on submit button,First a green message will be displayed as:
Message on successful creation of permission
21
User Management System (BRD),V.0.1 May 23, 2022
Once the message is displayed then the permissions page should be updated and the
test permission should be added in permissions as shown in screen 4.3
Screen 4.3
Delete permission
Whenever admin needs to delete any permission in the permission page,he/she will
simply click on delete button in actions section and the specific permission will be
deleted with the deleted message as shown below:
Message on successful deletion of permission
22
User Management System (BRD),V.0.1 May 23, 2022
5. Users page
This page should be showing user name and their respective roles.Basic operational
authorities should also be given to admin like
Create a new user
Edit any existing user
Delete any existing user
User page should have 3 columns , which are User name , Role and Actions and a
Button at upper right as shown in screen 5.1
Screen 5.1
(User page/Admin’s authority over users)
23
User Management System (BRD),V.0.1 May 23, 2022
Create User
Clicking on Create user button will route to this page as shown in screen 5.2
admin should will also get full control authority over Users as mentioned above .So,
whenever Admin wishes to create or edit a User. It will take him/her to a different
window as shown in screen 5.2
This page will have 5 major fields in it :
User name
Email
Password
Confirm password
Role(admin or Writer)
Submit
Screen 5.2
(Create user)
24
User Management System (BRD),V.0.1 May 23, 2022
Fields Specifications:
Field Description Data Type Char Screen Action/check associated
limit No
User Name of user Varchar/text 15 char S5.2 The admin will input the user
Name /compulsory/ name.
Unique
Email Emails of the Varchar/text 30 char S5.2 Emails should be provided by
user /compulsory/ admin for the creation of new
Unique user.
Password Password of Varchar/text 30 char S5.2 admin will input the Password
User /compulsory
Remembe Check box Check Box S5.2 Checking the box will save user
r Me for Name & password for web
remembering Browser
user name
and
password for
Web
Browser.
Confirm Matching the S5.2 Matching of both the passwords
password Passwords will take place and if they don’t
match each other, error message
will be generated.
Role Two roles will Check boxes S5.2 One of two roles should be
offered selected for the creation of new
user.
If admin creates a User successfully following message will be displayed as under:
Once the message is displayed then the user page should be updated and the user
created should be added in users as shown in screen 5.3
25
User Management System (BRD),V.0.1 May 23, 2022
Screen 5.3
Updated user page after creation of new user
Seletion of user will work similar as roles and permissions and the message will
also be generated similarly.
6.Posts
Posts should be shown in this page with the clear discribtion and status.Here the
actions section will differ for admin and user as only admin will be giver the authority of
both editing and deleting any post and user will only be allowed to edit a post but not
delete.
Admin page will generally contain four sections as :
Title
Status
Publish
Draft
Actions
Edit
26
User Management System (BRD),V.0.1 May 23, 2022
Delete
New Post
Screen 6.1
Post page of admin
Creating new post should be allowed for both the admin and the user but user will not
be allowed to delete any post as it is the authority of admin only as shown in screen 6.2
Admin page will generally contain four sections as :
Title
Status
Publish
Draft
Actions
Edit (only)
27
User Management System (BRD),V.0.1 May 23, 2022
New Post
Screen 6.2 shows the post page for a user.
Screen 6.2
Post Creation
New Post button will allow the admin and user to make a new role if nessesary. Clicking
this button will lead him/her to a new window where he/she can assign Title of the new
post as well as its Discription and Role as shown in the screen 6.3.
There should be a submit button at very bottom of this window.This button will simply
end the creation process of a new post by creating the specific post with Provided
details.
28
User Management System (BRD),V.0.1 May 23, 2022
Screen 6.3
29
User Management System (BRD),V.0.1 May 23, 2022
30
