CMGT/410: Business Requirements Document for a Small Business Website

This Business Requirements Document (BRD) outlines the development of a website for a small business, aiming to enhance its online presence and revenue. The document covers various aspects, including project overview, product description, user characteristics, assumptions, constraints, and dependencies. It details functional requirements, user interface requirements, usability considerations, performance metrics (capacity, availability, latency), and manageability/maintainability aspects. System interface/integration, security protocols, data management, standards compliance, and portability are also addressed. The report includes a work breakdown structure with timelines and responsibilities, ensuring a structured approach to website development. The website aims to be responsive, user-friendly, and optimized for various devices, focusing on increasing customer reach and improving business operations. The project is divided into phases like research, design, programming and testing. The report emphasizes the importance of clear navigation, secure data handling, and adherence to web standards to ensure a successful and efficient website implementation.

CMGT/410 v19
Business Requirements Template
How to Use This Document
This document is a template for creating a Business Requirements Document (BRD); it includes
instructions and examples for guidance. As you complete your BRD using the template, only include
sections pertinent to your project.
Table of Contents
How to Use This Document......................................................................................................................... 1
Table of Contents........................................................................................................................................ 1
1. Executive Summary.............................................................................................................................. 2
1.1 Project Overview.......................................................................................................................... 2
1.2 Purpose and Scope of this Specification......................................................................................2
2. Product/Service Description................................................................................................................. 3
2.1 Product Context........................................................................................................................... 3
2.2 User Characteristics..................................................................................................................... 3
2.3 Assumptions................................................................................................................................ 3
2.4 Constraints................................................................................................................................... 3
2.5 Dependencies.............................................................................................................................. 3
3. Requirements....................................................................................................................................... 4
3.1 Functional Requirements............................................................................................................. 4
3.2 User Interface Requirements....................................................................................................... 5
3.3 Usability....................................................................................................................................... 5
3.4 Performance................................................................................................................................ 6
3.4.1 Capacity................................................................................................................................... 6
3.4.2 Availability................................................................................................................................ 6
3.4.3 Latency.................................................................................................................................... 6
3.5 Manageability/Maintainability....................................................................................................... 6
3.5.1 Monitoring................................................................................................................................ 6
3.5.2 Maintenance............................................................................................................................ 6
3.5.3 Operations............................................................................................................................... 7
3.6 System Interface/Integration........................................................................................................ 7
3.6.1 Network and Hardware Interfaces............................................................................................ 7
3.6.2 Systems Interfaces.................................................................................................................. 7
3.7 Security........................................................................................................................................ 8
Copyright© 2018 by University of Phoenix. All rights reserved.

Business Requirements Template
CMGT/410 v19
Page 2 of 14
3.7.1 Protection................................................................................................................................. 8
3.7.2 Authorization and Authentication............................................................................................. 8
3.8 Data Management....................................................................................................................... 8
3.9 Standards Compliance................................................................................................................. 9
3.10 Portability......................................................................................................................................... 9
4. User Scenarios/Use Cases.................................................................................................................. 9
5. Deleted or Deferred Requirements....................................................................................................... 9
6. Requirements Confirmation/Stakeholder Sign-Off..............................................................................10
Appendices................................................................................................................................................ 11
Appendix A: Definitions, Acronyms, and Abbreviations..........................................................................11
Appendix B: References........................................................................................................................ 11
Appendix C: Requirements Traceability Matrix......................................................................................12
Appendix D: Organizing the Requirements............................................................................................13
Copyright© 2018 by University of Phoenix. All rights reserved.

Business Requirements Template
CMGT/410 v19
Page 3 of 14
1. Executive Summary
The following report is all about development of website for a small business. Website is known to be much more
environment friendly for different aspects like marketing and advertisement. There are large number of ways for
advertising different product and service on the internet platform. Facebook Add is known to be an advertising
feature which is provided by Facebook. There is another method of advertising which is known as SEO. By the help
of good SEO service provide can easily boast the overall ranking of website that results in an increase in overall
sales and much higher profit. As this business is small in size it only has local popularity. A website can generate
more number of customers for this business outside their locality.
Copyright© 2018 by University of Phoenix. All rights reserved.

Business Requirements Template
CMGT/410 v19
Page 4 of 14
1.1 Project Overview
The report is all about website development for small business. It is the expected that the whole project will be
completed within 124 hours. The project will merely have four phase that is research, design, program and lastly
test. This particular small business is looking for a reflection of current site so that its diversity and uniqueness. The
proposed website needs to responsive to various mobile devices. It is very much easy to find the required
information which is accessible to whole community and visitors.
In the coming pages of the report, an idea has been provided with respect to purpose and scope of this project. The
next section of the report deals functional requirements, usability and performance of the website.
1.2 Purpose and Scope of this Specification
The project is all about development of website for a small business. This particular website can help in
improving the revenue and profit for business.
In-Scope
The in-scope of the website development project for small business are described below:
 It is expected that the project will be completely within a period of 124 hours.
 Creating a web site where project can consolidate and consistent image
 To increase the visibility of our service.
Out-Scope
 The overall budget for completing the website has not been mentioned.
 The target audience of this website is not clear.
2. Product/Service Description
2.1 Product Context
The website development is a self-contained system which is an architecture that emphasises
functionality separation for many systems. This will make the logical collaboration of small software
system. The interface of the website aims to vary in range of devices like mobile phones and computer.
Copyright© 2018 by University of Phoenix. All rights reserved.

Business Requirements Template
CMGT/410 v19
Page 5 of 14
Fig 1: Website on different devices
2.2 User Characteristics
The general public who will be using this website are stated below:
 The users of this website will be staff members, funding organization, partners, clients, job applicants,
service buyers and many other.
 The website has been designed in such a way that it can easily satisfy the need of the users.
 Only the technical department of the organization have in-depth knowledge about the website.
2.3 Assumptions
For this website, there are a list of assumption which should be taken into account like
 People have an idea to find out the website
 People known what to sell
 People known where to click
 People known how to buy product.
2.4 Constraints
A list of design constraint for this website are
Copyright© 2018 by University of Phoenix. All rights reserved.

Business Requirements Template
CMGT/410 v19
Page 6 of 14
Domain name: It is one of the important aspect for design feature for any of the website that has
a unique and memorable domain name. It comes up with huge number of challenges that helps in getting
the required domain name.
Live updates considering online presence: It will require some kind of CSS coding which the
developer is not very accustomed with. There are many tools for web design that allow the user to tap into
a single account on a various social media platform.
Mobile-friendly: This particular aspect of the website has been achieved successfully. The web
template aims to provide quick and clean dynamic which is based on the width of the screen.
Slow loading: Lack of good internet speed is one of the major reason for slow loading time of
web pages. The overall file size is all also impacted as a result of loading speed. Overloading of web
page with various images, graphics and videos can also affect the loading speed.
Browser compatibility: Most of the well-known browser in the current market are Microsoft
internet explorer, Google chrome and safari. Most of the browser come with difference in specification
and formats so the website performance mainly depends on its performance.
2.5 Dependencies
This particular website will download data from the customer website so that they can analyze their need
in a much better way.
3. Requirements
For designers, the minimum hardware requirement which is much more predictable is due to the scale of
work. It is not the board for overall development as the system requirement is the benchmark. There is list
of requirements which should be taken into account like
 Intel Pentium 4 or AMD processor (2Ghz or even faster)
 Microsoft Windows 7 with service pack 1
 Minimum 2 GB of memory space (recommended is 4 GB)
 2 GB of available hard disk for installation and additional space for installation
 Minimum 1024 * 768 display and the recommended one is VRAM
 Internet connection and registration is required for software activation
For a website, the input is the raw data which is processed for producing output. At the time of input
design, the developer is required to make input of certain things like PC and OMR. Quality of the system
input highlight the overall quality of output. Well-designed system from input forms and screen will have
certain number of properties like
1. It mainly ensures to complete it with accuracy.
2. It should focus user attention, consistency and simplicity
The design output for a website is considered to be as one of the important aspect. At the time of output
design, developer need to look for required output and necessary control and prototype. The objectives of
output design are
1. To provide the output design which meets the user requirement
2. To develop an output design which acts like intended purpose and removes the production of any
unwanted output.
Copyright© 2018 by University of Phoenix. All rights reserved.

Business Requirements Template
CMGT/410 v19
Page 7 of 14
Functional Requirements
The functional requirement of the system has been provided in tabular format :
Req # Requirement Comments Priority Date Received SME
Reviewed/Approved
BR_01
Website should
produce a weekly,
monthly and
yearly reports.
Business
Process =
“Maintenance
4 10/2/17 Joseph T. Cornett,
Derek L. Lanz
BR_03
The website
should produce a
receipt for dealing
customer
purchase
information.
Business
Process =
“Changing
Dues in the
System”
3 11/23/17 Ronald J. Lammers,
Daniel A. Odom
BR_05
The website shall
accept the
customer orders
and cash a sale.
Business
Process =
“Maintenance” 5 12/27/17 Shawn M. Nolan,
John E. Green
a. User Interface Requirements
User Interface design mainly focus on the fact that user need to do. In addition, it highlights what the user
need to do for ensuring that interface has certain number of elements. These elements are very much
easy to access and make use of facilities for the given action. UI needs to bring the given concepts with
respect to interaction design and visual design. Interface elements are merely inclusive of
Input Control: Buttons, text fields, checkbox, dropdown list, list box, date field.
Navigational Control: Search field, pagination, icons
Informational Control: Icons, progress bar, notification, message box and modal windows
Usability
Most of the business website split up their content which is there in between multiple pages. It merely
enables the user to easily navigate in between by making use of menus. Clear navigation is found to be
as one of the important aspect of usability of website.
Performance
Given below is the static and dynamic website design like
Copyright© 2018 by University of Phoenix. All rights reserved.

Business Requirements Template
CMGT/410 v19
Page 8 of 14
 Static website requirement is mainly inclusive of number of terminals it supported. The website
can support around 100 users at a single time.
 Dynamic requirement of this website is around 10 number of transaction and task which can be
processed in the given time period.
Capacity
The design website can easily have simultaneous user in between 100 to 200 users at single instance.
The maximum simultaneous user load is 200 for this website. Per user memory requirement of this
website is 500 Mb for storing different files.
Availability
There is some specific requirement for website like
 The website is available on 24 * 7 basis.
 It is available as per the user need.
 The website is accessible from any geographical location
 The downtime of website will have a direct impact on user and business requirements.
 Schedule and Unscheduled maintenance of website will have direct impact on business.
Latency
The maximum acceptable time for the website is around 30 seconds.
Manageability/Maintainability
Monitoring
Website user needs to have a certain product or service for error detection and correction of the website.
Maintenance
Modular design aims to encourage the design and think for UI and UX in the given patterns. Instead of
designing a series of web pages for completing a task. User will have a design process by analyzing UI
system structure and how the components can be used for building user flow.
Operations
The website has been designed in such a way for small business that it can have certain number of
options like
 Back up of data for providing support to important client information
 Safety aspects
 Recovery in case of disaster.
Copyright© 2018 by University of Phoenix. All rights reserved.

Business Requirements Template
CMGT/410 v19
Page 9 of 14
System Interface/Integration
Network and Hardware Interfaces
There is a list of aspects required for developing website
 Computer
 Camera
 Mobile devices
 Server
Systems Interfaces
The system interface requirement for the website are discussed below like
 Keeping the interface of the website simple as much as possible
 Consistency and common UI elements
 Purposeful layout of a web-page
Security
Protection
The website needs to make use strong and protected password so that it can protect the vital information
of both employee and client. Both client and employee need to change their password on regular interval.
Authorization and Authentication
This particular website can implement pubcookie on their browser so that they can identify the user on
server. The mechanism has certain number of advantages like
 The cookie will stay in the browser for the time being and so the user does not give login and
password.
 The login page for different application requires to be identified on pubcookie login page.
Data Management
Web database management is considered to be as one of the important aspects of DBMS which requires
various application to be store application data. It is generally required for handling database which have
data with respect to e-mail and blog.
Standards Compliance
Standard compliance can be defined as the compliance of either website or web browser in the given web
standard. It is with respect to the world wide web consortium. There is need to ensuring the
interoperability of standard complaint website that does not support to software methods.
Copyright© 2018 by University of Phoenix. All rights reserved.

Business Requirements Template
CMGT/410 v19
Page 10 of
14
3.10 Portability
Portability can be defined as the characteristic attribute for system program which can be used in a
various operating system. It can be stated as the task of doing the required work so that the system
program can run in the current environment.
3. User Scenarios/Use Cases
Fig 1: Use Case of Developed Website
(Source: Created By Author)
Copyright© 2018 by University of Phoenix. All rights reserved.

Business Requirements Template
CMGT/410 v19
Page 11 of
14
4. Deleted or Deferred Requirements
Identify any requirements that have been deleted after approval or that may be delayed until future
versions of the system.
Example:
Req # Business
Requirement Status Comments PRI Date
Reviewed
SME
Reviewed/Approved
BR_06 The website
should be
easy to use
by employees
including
sales
representative
and
managers
Replaced Business
Process =
“Assigning a
Bargaining Unit
to an
Appointment”
4 12/22/17 Joseph T. Cornett,
Derek L. Lanz
BR_07 Website
should be
available in
various
languages
Replaced Business
Process =
“Assigning a
Bargaining Unit
to an
Appointment”
8 12/27/17 Ronald J. Lammers,
Daniel A. Odom
BR_08 The website
should allow
various sales
to be done at
the same time
without
degrading the
performance
.Replaced Business
Process =
“Assigning a
Bargaining Unit
to an
Appointment”.
This will
eliminate the
need, typically,
for the user to
enter the
bargaining unit
code, union
code, and
supervisor
indicator.
9 12/29/17 Shawn M. Nolan,
John E. Green
5. Requirements Confirmation/Stakeholder Sign-Off
Include documentation of the approval or confirmation of the requirements.
Example:
Copyright© 2018 by University of Phoenix. All rights reserved.

Business Requirements Template
CMGT/410 v19
Page 12 of
14
Meeting Date Attendees (Name and Role) Comments
01/12/18 Joseph T. Cornett, Labor Relations SME
Derek L. Lanz, Labor Relations SME
Ronald J. Lammers, Technical Project Manager
Daniel A. Odom, Technical Analyst
Shawn M. Nolan, Technical Analyst
John E. Green, Project Manager
Confirmed BR_01 – BR_05
01/25 /18 Joseph T. Cornett, Labor Relations SME
Derek L. Lanz, Labor Relations SME
Ronald J. Lammers, Technical Project Manager
Deleted requirements BR_06
to BR_08
Copyright© 2018 by University of Phoenix. All rights reserved.