Being Mentor

(Website and Android APP)

Business Requirements Document
(BRD)

1
Table of Contents

TABLE OF CONTENTS...................................................................................................................................................2
1. INTRODUCTION....................................................................................................................................................2
1.1. VISION OF PROJECT...........................................................................................................................................3
1.2. INTENDED AUDIENCE........................................................................................................................................3
1.3. OBJECTIVES OF THE PROJECT............................................................................................................................3
1.4. PURPOSE OF THE BUSINESS REQUIREMENTS.....................................................................................................4
1.5. SCOPE OF THE PROJECT.....................................................................................................................................4
2. OVERALL DESCRIPTION....................................................................................................................................5
2.1 PRODUCT FEATURES..................................................................................................................................................5
2.2 OPERATING ENVIRONMENT.......................................................................................................................................5
2.3 DESIGN AND IMPLEMENTATION CONSTRAINTS.........................................................................................................5
3. FUNCTIONAL REQUIREMENTS........................................................................................................................5
3.1. ACTIVITY DIAGRAM..........................................................................................................................................6
.........................................................................................................................................................................................7
3.2. ACTOR PROFILES SPECIFICATION......................................................................................................................8
3.3. FUNCTIONAL REQUIREMENTS FOR INDIVIDUAL ACTOR....................................................................................9

4. Market overview ……………………………………………………………………..10

4.1. MARKET SIZE ..................................................................................................................................................10
4.2 customer needs...........................................................................................................................................10
4.3 Direct or indirect compitition ...................................................................................................................11
4.4 COMPATITIVE ADVANTAGE..................................................................................................................................11
4.5 PRICING.................................................................................................................................................................12
4.6 promotion plan..................................................................................................................................................12
4.7 DISTRIBUTION PLAN..............................................................................................................................................12
4.8 SWOT ANALYSIS ...................................................................................................................................................14

5. NON-FUNCTIONAL REQUIREMENTS...........................................................................................................16
5.1. SECURITY REQUIREMENTS..............................................................................................................................16
5.1.1 Authentication............................................................................................................................................16
5.1.2 Authorization and Access Controls............................................................................................................17
5.2 AVAILABILITY REQUIREMENTS............................................................................................................................18
5.3 USABILITY REQUIREMENTS..................................................................................................................................19
5.4 SYSTEM HELP REQUIREMENTS.............................................................................................................................19
5.5 PERFORMANCE REQUIREMENTS...........................................................................................................................19
6. INTERFACE REQUIREMENTS.........................................................................................................................20
6.1. USER INTERFACE REQUIREMENTS...................................................................................................................20
6.2. SYSTEM INTERFACE REQUIREMENTS (APPLICATION).....................................................................................20

2
 1. Introduction to Company
Executive summary
Worldwide, mobile phones and internet are becoming the most widely available
communication platforms. The platform will be in the form of a website and mobile
app and allow student and mentors s to connect with height professionals who has
relevant experience or possibly came from a similar situation. We will provide
them with tools in the form of a messenger, Audio, video call so mentors and
mentees can start communicating right away. Build a website and Android
application of a platform in which students and professional who need any sort of
guidance meets the experienced mentors and interacts with each other’s for
resolution of their problems. It can help persons solve their problems when they
face obstacles in the process of learning something new. Our platform can give
people experienced mentors that will assist in the resolution of all problems related
to learning. The availability of mentors in different fields can also attract more
mentees to your mentor app. The more specialists your platform will have, the
more newcomers will see an advantage in your platform.

1.1 Vision
The vision of being mentor is to establish itself in the educational services
sector and facilitate the education for the users with providing easy access to
experienced mentors by this the students and professionals can get any type of
guidance.
1.2. Intended Audience
The intended audience for this website and application are;
 Admins (Multiple accounts)
 Students and Professionals (one or many depends upon the requirements)
 Mentors (one or many depends upon the requirements)

1.3. Objective
The target of this website and application are students/professionals and
experienced mentors. As a platform we wants to provide the students/professionals
a facility to register and navigate through this app/website and share their
problems and the experienced mentors will interact with them through forums,
audio/video sessions and provide them solutions and guidance regarding their

3
problems. Three different types of accounts will be created and according to the
nature of the account users can see their data.

1.4. Purpose of the business requirements

We have requirements for new website and android application development
fulfilling our society need to get a guidance regarding regular problem students
and professional are facing in their journey and want to take guidance from those
who already passed these stages and now can help them to overcome those hurdles.
1.5. Project scope
Primarily, the scope pertains to students/professional and our mentors, who are
going to interact with each other’s by reviewing the profiles and interacting on
platform through questions, audio and video sessions etc. It focuses on the
problems, the students and professional are facing and replies of the mentors,
which allow for online information exchange through this platform.

4
 2. Overall Description

2.1 Product feature

This website or application allows users to view their profiles, interest areas,
questions, knowledge base, seminars or events details etc., using a computer or
smartphone. The contents visible will be governed by the role assigned by the
administrator.

2.2 Operating environment

The software will run on the Android operating system and website on internet. All
devices that support the internet and Android operating system will be able to run
the website and application.

2.3 Design and implementation constraints

The UI must be extremely attractive and initiative and easy to use.
The application must display the last accessed data even when there is no internet
connection.

3. Functional requirements

The Functionality of the website and application depend upon the users, we have
divided users into three categories and we are going to show you activity diagram,
so you can understand how this application is going to work.
Categories are;
 Admins (Multiple accounts)
 Students and Professionals (one or many depends upon the requirements)
 Mentors (one or many depends upon the requirements)


5
3.1 Activity Diagram

ADMIN/USERS
IS
REGISTERED
ADMIN/USERS
LOGIN NAME
& PASSWORD

CORRECT
LOGIN INVALID
PASSWOR LOGIN
PASSWORD

LOGIN
SUCCESSFULLY

STUDENT/
PROFESSIONAL MENTORS

ACTIVITY ACTIVITY
ADMIN ADMIN

PLATFORM ACCESS (based on Roles)

6
3.2. Actor profiles specification
This section describes all the Actors and their profiles within the context of the
Business Requirements being documented. An Actor is a person, organization or
an external system/sub-system/program that has interactions with the website and
application.

Actor Name Actor Type Access Type needed Commen

ts
Stakeholder Create and All
Admins Primary Actor manage both informati
Supporting students/professional on
Actor s and mentor is visible
Accounts to him
Read
Update Accounts
Delete Accounts
Stakeholder Create own
Students/ Primary Actor Accounts
Professionals Supporting Read own
Actor Information/activity
Update own
Accounts
Disable own
Accounts
Stakeholder Create own
Mentors Primary Actor Accounts
Supporting Read own
Actor Information/activity
Update own
Accounts
Disable own
Accounts

7
3.3. Functional Requirements for Individual Actor
3.3.1 Admins

Functional Requirement Id Admins

Description: This will be the primary actor, it will have the authority to
create and manage accounts of Student/professional and Mentors and this
user will be the Super User.
Impact This actor must have the permission to create and
manage student/professionals and mentor accounts with
full control over the platform content.

Primary Actor Owner of the project and related person to which the
owner with assign sub-admin accounts
Input information
Action System must able to give detailed information about the
student/professionals and mentors.
System must allow this actor to create/manage accounts
Output Users can be increased based on owner assignment to
sub-admins
Dependencies Owner Admin can assign sub-admins with limited
privileges but the super user is of owner account

3.3.2 Student/Professional
Functional Requirement Id Student/Professionals User
Description: This will be the user actor, it can only read/manager own
information on the platform.
Impact Read, inquiry response to own content and others (other
than mentors)
Primary Actor Student/Professionals
Input
Action
Output
Business Access to information about activities.
Rules
Dependencies Admin, Sub-admin and mentors

8
3.3.3 Mentors

Functional Requirement Id Mentors User

Description: This will be the user actor, it can only read the information
about their transactions
Impact R Read, inquiry response to own content and others (to
students/professionals )
Primary Actor Mentors
Input
Action
Output
Business Access to information about activities
Rules
Dependencies Admin, Sub-admin and mentors

9
 4. Market Overview
Being mentor is competing for attention within the general market of mobile
applications. This is a massive market. There were 149.3 billion downloads in
2016, and during the year 2021 there is expected to be 352.9 billion downloads.
Currently there are around 2.2 million apps available in the Apple App Store
and about 3.5 million available in the Android Store. Now within the app
industry, we are competing specifically with mentoring and networking apps.
There is not much data on mentoring apps since it is a very niche market. Just
searching the Apple App Store, most of the mentoring apps are designed to
connect businesses with mentors or just people in general. Our app will operate
in a niche market within the mentoring app industry.

4.1. Market size

Our target market is going to be a combination of young adults and older
professionals and executives. The young adult’s age will range from 16-22 and the
professionals and executives will be 30+. We will specifically target young adults
with low income housing. We are aiming for people who have a desire to succeed
and improve their lives, but do not have the same resources. Anyone seeking a
mentor can join the app. We will search for executives in a variety of different
companies and professionals in many different areas of expertise. We want to be
able to match the right young adult with the right mentor so both parties can get
the most out of their relationship.

4.2. Customer needs

10
Most people aspire to be successful and strive to be a better version of themselves.
Our service requires two different customers; the youth looking for guidance and
professionals looking to share their experience and help people in need. Our
service solves the needs of both customers by connecting them and then providing
them with the tools they need. The youth are getting a mentor that will create a
positive impact on their lives and give them opportunities they didn’t have before.
The professionals have the chance to use their years of knowledge and expertise to
help the less fortunate and give them brighter futures. Mentors can also gain
management and leadership experience that could eventually help them for a
management position within their company. It is also useful for businesses to use
our service since the youth being mentored are not too far from entering the
workforce. By maintaining relationships and instilling some of the values of the
company, mentors will generate potential employees. Also, one of the most
important aspects of a company is their image. By using our app, companies will
be helping the community and improving their corporate social responsibility. Our
young customers need a quick and easy to use platform that will seamlessly
connect them with a mentor or based on their interests and aspirations. Ultimately,
we want to create and promote a positive and motivational environment for the
youth in the Worcester community and then expand from there.

4.3. Competitive advantage

Our service will be unique in that it will be an open network that connects the
youth with an ever-increasing selection of mentors with a variety of different
backgrounds. Most mentoring platforms charge subscriptions or fees to use their
service. Our plan is to remain a free mentoring platform to encourage as many
users as possible to join. Our service will be able to improve communities by
providing the youth with great mentors and companies with a better image and
employee feeding system. By targeting large business and having a free easy to use
interface with personalized mentor generators, we hope to be the preferred
mentoring platform for the youth, professionals, and companies looking give back
to the community and help people in need.

4.4. Pricing

11
Since we are a free application/website platform, we are going to need many users
to generate revenue off advertisements. We will insert non-disruptive
advertisements, sponsorships, or native ads within the platform. As we advance we
will offer in app purchases that will give access to more communication tools and
networking opportunities. We want to generate a large user base and offer space
for local and big companies to place their advertisements on our platform. There
will be no pop up ads or anything that will hinder the user from being able to use
the app effectively. We want to incorporate sponsored ads and native ads seamlessly
so they catch people’s attention, but are non-intrusive.

4.5. Promotion/ Discount plan

We have two kinds of customers so we have two different strategies of attracting
customers. To attract the mentors our plan is to reach out to businesses looking to
improve their CSR. We will ask the companies to spread the word to employees and
those who are interested will sign up. The company will be able to talk about all the
good they are doing for the community and employees looking to become a mentor
will have that opportunity. To attract the mentees, we will begin by going to schools
in low income areas. The schools will show the platform to their students and
explain how it can help them. The cost of going businesses and schools would be
our time and any marketing material we would bring. It will take some time to go
to each school and explain and present our business. The benefit will be we are
forming personal connections with people so they are more likely to use our service
and continue to use it. Another strategy is to reach out to some big names directly
and ask them if they would be willing to sign up for our service. If we can get one
or two big names on our platform as mentors from the beginning, it will give us
some credibility and a greater chance of gaining customers in the future.

4.6. Distribution plan

12
Since our business is completely on the internet, we don’t have to worry about the
traditional distribution of a physical product or service. Our product is stationary
so we are going to distribute it by driving traffic to it. We generate revenue by
getting people to sign up on our platform and continue to visit and use our service.
We will ensure quality by making sure the platform is reliable, safe, and constantly
being improved. It is extremely important for us to collect feedback from our
customers so we can update and make changes accordingly. If there is a bug or
flaw many users are unhappy with, we want to know so we can make an
adjustment. If there is a feature that users like, we want to know so we can make
sure it is working well for them. We will collect feedback through surveys and
listing to what people are saying on our social media sites.

4.7. Operational Plan

We will eventually be hiring labor. Our platform will be holding a large amount of
personal and sensitive information such as emails, passwords, and messages so we
are going to need to hire people who are experts in information security. Once the
initial platform is up and running we are also going to need to find a developer
who can update the platform and continue to add new features. Our day to day
responsibilities will become mainly business development and marketing. Once we
hire people who can keep the app up and running, we will need to focus on finding
new customers and pushing the platform into new locations.

In six months, we want to have about 500 hundred users. Beginning users will
mostly consist of people we reach out to personally. During the six months after the
Ureka Competition, we will develop the app further and then bringing it to market.
Our target is to do a soft launch in October and then fix any bugs or issues we
come across. Once it is ready for the market, we will have a launch party and
notify all the businesses and high schools who showed interest, and push the app to
all the local press. As we continue to develop the business we will be constantly A/B
testing to see what users like and don’t like. We can’t know for sure what people
will want to know, but as we go along we will be able to test and figure it out.

13
4.8. SWOT ANALYSIS

Strengths

Communication skills

14
Work well in a team

Sound knowledge base

Business continuity and mobility.

Shared computer resources

Cost savings

Experienced

Timekeeping

Organised

Willingness to teach

Weakness

Legacy systems

User attitude and control

Lack of experience as a mentor

Find it hard to delegate, ‘need to be in control’

Unsure about teaching skills

Don’t know much about curriculum

Little leadership experience

Opportunities

Agility and flexibility

Growth in cloud services

Consolidation in legal and regulatory environment

15
Threats

In house IT Personnel

Data Protection

Security

Time constraints, not being able to give the students enough time

Pressurised ward/heavy case load

Staff shortages

Stressful environment at times

No other mentors on ward

Little support from other staff

5. Non-Functional requirements
1. Standard disclaimer must be inserted when downloading the application
2. Standard security checks must be applied to deny unauthorized users from
accessing the system/website.
3. App should be lean on bandwidth usage and must work on last available
data when link is down

16
 4. Performance should be reliable and efficient and inconsistent data should
not be displayed

5.1. Security Requirements

This section describes the Security requirements part of the Business

Requirements.

5.1.1. Authentication

This section describes the Authentication requirements part of the Business

Requirements. Authentication is the process of verifying the genuineness of claims
that a person/group makes to establish identity/eligibility for access to services. In
order to ascertain the Authentication requirements of the Application/website, it is
required to analyse the type of transactions that different Pages within the
Application/website. The following criteria is used in determining transaction types
of each use case/function:

Level 0: Anonymous transaction

Triggers transactions that do not require or allow a person to be identified, or

transactions which require protection of a person's identity. For example, access
to online information about government programs or services or protecting a
person's identity. Combining the transaction data with other data must not allow
identification of a particular individual.

Level 1: Pseudonymous transaction –

Triggers transactions that do not require a person to be identified but do require
a means for further contact to deliver a product or service. For example, a note
from someperson@internet.cannot be readily translated into an individual’s
name, but it may be sufficient to request information, to provide some services,
or on-going follow up.
Level 2: Identified transaction
Triggers transactions that require that a person be specifically identified. The
nature of the transaction may require confirmation of a person's identity (e.g.,
name, address, birth date, etc.) and/or data linking the person to a transaction
(e.g., invoice number, personal health number, etc.).

17
 Level 3: Verified transaction
Triggers transactions that require: the person to be specifically identified;
verification of the integrity of the data exchanged and the exchange itself; and,
the creation of sufficient evidence to indicate that the person agreed to be
bound by the transaction. For example, a note signed with a digital certificate,
audit trails and security logs may provide sufficient evidence that a specific
person intended to conduct a transaction.

Pages Transaction type

triggered
(Level 0 : Anonymous,
Level 1 : Pseudonymous,
Level 2 : Identified,
Level 3 : Verified)
Login Page 1
Account Creation Page 3
Information Page 1

5.1.2. Authorization and Access Controls

This section describes the Authorization and Access Control requirements part of
the Business Requirements at a high-level. Authorization is the process of
determining if the person/group, once identified through the “Authentication
process”, is permitted to have access to certain services. The Authorization and
Access Control requirements are best described through a matrix.

Actor / Business Unit Conceptual Class / Type of Access Control needed

Name Business Entity on the Conceptual Class /
Name Business Entity :

C  Create
R  Read
U  Update
D  Delete

18
Owner ADMIN C,R,U,D (all)
Admins ADMIN C,R,U,D
(Students/Professionals/Mentors
)
Student/Professional USER C,R,U,D
s (Students/Professionals)
Mentors USER C,R,U,D
(Students/Professionals)

5.2. Availability Requirements

This section describes the system availability requirements.

Function Name Availability

Requirements
- Regular work hours
- 24x7
- Any other (please
describe)
Login Function 24x7
Account Creation 24x7
Transaction’s detailed 24x7
information

5.3. Usability Requirements

User should be able to use the application/website with ease. All data should be
visible to the user. All the features of the application/website can be easily used by
the user.

19
5.4. System Help Requirements

This section describes what kind of System Help features are needed to be built
into the system.

Function Name Help Requirements

Login Function Narrative to help users

Account Creation Help in creating
accounts
Transaction’s detailed At each page guide users
information

5.5. Performance Requirements

This section describes system performance expectation levels (response times).

Function Name / Performance

Transaction description Requirements
(response time)
(in seconds or
minutes)
Login Function seconds
Account Creation seconds
Transaction’s detailed seconds
information

6. Interface Requirements

This section describes User and System Interface requirements for the proposed
system.

20
6.1. User Interface Requirements

UI-1: All users shall be able to zoom into information using the standard gestures
on mobile devices.
UI-2: All Users will be able to view the next page by swiping left to right
(application).
UI-3: All users should be able to go back to the previous page via the back button
provided in application.
UI-4: All users should be able to search by keyword or order.

6.2. System Interface Requirements (Application)

This will be an Android phone application, and as such, will be designed to

interface with the hardware present on the Android phones. In theory the
application will be able to run by other devices that can emulate the Android, but
this will not be a consideration during design.
As this is a mobile device, it will be using the cellular network or Wi-Fi to connect
to the Internet, which will allow it to communicate with the database servers. This
means that it will be using the infrastructure, be it wireless communication points
or physical lines, of the network in order to perform properly. There will have to
be some sort of error checking for if the network is down or inaccessible.

21