PART A Answer

Healthy Body Wellness Center
Business Requirements Document Template

Healthy Body Wellness Center/Initiative
Month 20YY
Version X.XX
Company Information
Tech Comm Template BRD
1 Document Revisions (Not required for performance assessment)
Version
Date Document Changes
Number
05/02/20xx 0.1 Initial Draft
2 Approvals (Not required for performance assessment)

Role Name Title Signature Date
Project Sponsor
Business Owner
Project Manager
System Architect
Development Lead
User Experience
Lead
Quality Lead
Content Lead
Template provided by TechWhirl.com

copyright INKtopia Limited | All Rights Reserved 1
3 Introduction
3.1 Project Summary
3.1.1 Objectives
The purpose of Healthy Body Wellness Center is to help the patients and society to take proper care of
their wellbeing. It is further responsible for distributing the medical grants and The Small Hospital Grant
Tracking System (SHGTS) is used for managing and tracking its data. It records the first delivery of the
grant funds and then follows the other hospitals in which the unused grants are further rotated. All the
grant evaluation work has to be done through an application and due to the paper reduction Act, the
paper based manual applications are transferring to computer based online application submission which
has ultimately increased the number of medical grants. The OGG is expecting to get more grants thus
need to engage more office staff that requires the need to update the infrastructure and to grow the grant
sources. They are also heading towards the development of the web-based portal which will contain
information of patients.
3.1.2 Background
The need of upgrading from LAN to WAN created a need for a security audit of the Healthy Body
Wellness Center to address the changes that needs to be implemented in order to ensure a modernized
and secured network. The key findings include that the system’s infrastructure needs to be updated, web
based services lack the security checks, lack of a proper database. The data backup and recovery systems
should be developed and the security analysis needs to be conducted to the system’s security needs and
develop a secure system to be used by the recipients.
3.1.2.1 Business Drivers
The major driver for this business is the security needs and lack of cryptographic controls, customer
satisfaction and relationship, employee development, quality improvement and financial analysis and
accountability and backup and recovery management. Another major reason was expanding business
engaging new employments and the unavailability of patches for current system by Microsoft after 2020
that prompted them to move to MySQL.

3.2 Project Scope
3.2.1 In-Scope Functionality
The scope of project is to upgrade the infrastructure to handle the increase in work force with patient
satisfaction and to create a web portal to manage all patient’s information and important details that
need to be secured during transmission and processes.
3.2.2 Out-of-Scope Functionality

Problems due to any change in demand of stakeholders, or issues due to unavailability of resources, changes in
time, cost and scope.
3.3 System Perspective

3.3.1 Assumptions
 System will be complete in agreed upon cost and time.
 System will be available to end users all the time.
 System will be delivered with all agreed upon requirements.
 The scope of the project will be same as decided by stakeholders
 System will be reliable.
3.3.2 Constraints
 Time schedule
 Cost
 Unavailability of Resources
 Quality of the system
3.3.3 Risks
 Change in demands by stakeholders
 Change in resources, decided time and cost
 Exploitation of vulnerabilities
 Hacking attacks or virus
 Loss of potential data as we are upgrading the existent system.
3.3.4 Issues
 System proposed is web-based portal, so unavailability of internet can cause issues like loss of data,
hinderance in process completion
 Availability, confidentiality, reliability of system
 Training of employees
 Requirements are not complete

4 Business Process Overview
4.1 Current Business Process (As-Is)
The current business processes only contain Sales and marketing, information storing in a database,
service delivery management. The system is only capable of storing the information but does not
provide any backup or recovery in case of data failure. Moreover, it is not protected to unauthorized
access.
4.2 Proposed Business Process (To-Be)

The proposed business processes include a good customer relationship by providing a convenient system
to use and by accommodating a greater number of staffs, quality process and improvement management
by considering the vulnerabilities and developing a more secure and vulnerable system. Financial
analysis in which all the transactions will be recorded and tracked, and accountability will be
considered. Technology management to convert the paper-based tasks to completely computer-based
system. Security management to secure all the information and create backup and recovery in case of
data failure.
Tracking Customer Security

Service and Relationsh
Sales and Quality Manageme Financial
sharing ip
Marketing Delivery informatio
Inspection nt and Analysis
Bacup
n

5 Business Requirements
[The specific business requirements elicited from stakeholders should be listed and categorized by both priority and area of functionality to
smooth the process of reading and tracking them. Include links to use case documentation and other key reference material as needed
to make the requirements as complete and understandable as possible. You may wish to incorporate the functional and nonfunctional
requirements into a traceability matrix that can be followed throughout the project.]
The requirements in this document are prioritized as follows:
Value Rating Description

1 Critical This requirement is critical to the success of the project. The project will not be
possible without this requirement.
2 High This requirement is high priority, but the project can be implemented at a bare
minimum without this requirement.
3 Medium This requirement is somewhat important, as it provides some value, but the
project can proceed without it.
4 Low This is a low priority requirement, or a “nice to have” feature, if time and cost
allow it.
5 Future This requirement is out of scope for this project and has been included here for a
possible future release.

5.1 Functional Requirements
Use Case Impacted
Req# Priority Description Rationale
Reference Stakeholders
General / Base Functionality
High Customer relationship and satisfaction Hospital staff,

patients
to store, edit and update the information Patients

Critical of the patients in a database
to track the grant funds, to record the Hospital staff and

Critical employee payroll, online grant employees
application submission.
Security Requirements
The need to protect the system against All Stakeholders

High
any vulnerabilities
Hospital staff
To provide backup and recovery in case
High ()one managing
of data loss or any failure
the ystem
To upgrade the cryptographic controls All stakeholders

High and protect the system from
unauthorized access

Reporting Requirements
Usability Requirements
Ease of use, simple and convenient Recipient (users

Medium
interface of system)
Audit Requirements
5.2 Nonfunctional Requirements

[Include technical and operational requirements that are not specific to a function. This typically includes requirements such as processing time,
concurrent users, availability, etc.]
ID Requirement
1 Privacy
2 Reliability
3 Customer Relationship
4 Fault Tolerance
5 Accessibility and efficiency

6 Quality and security
7 Backup and recovery
8 Increased capacity.

6 Appendices (Not required for performance assessment)

6.1 List of Acronyms
[If needed, create a list of acronyms used throughout the BRD document to aid in comprehension.]
6.2 Glossary of Terms

[If needed, identify and define any terms that may be unfamiliar to readers, including terms that are
unique to the organization, the technology to be employed, or the standards in use.]
6.3 Related Documents

[Provide a list of documents or web pages, including links, which are referenced in the BRD.]


PART A Answer

Uploaded by

Copyright:

Available Formats

PART A Answer

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

PART A Answer

Uploaded by

Copyright:

Available Formats

Healthy Body Wellness Center

Business Requirements Document Template

2 Approvals (Not required for performance assessment)

Template provided by TechWhirl.com

Template provided by TechWhirl.com

3.2.2 Out-of-Scope Functionality

3.3 System Perspective

Template provided by TechWhirl.com

4.2 Proposed Business Process (To-Be)

Tracking Customer Security

Template provided by TechWhirl.com

Value Rating Description

Template provided by TechWhirl.com

General / Base Functionality

High Customer relationship and satisfaction Hospital staff,

to store, edit and update the information Patients

to track the grant funds, to record the Hospital staff and

The need to protect the system against All Stakeholders

To upgrade the cryptographic controls All stakeholders

Template provided by TechWhirl.com

Ease of use, simple and convenient Recipient (users

5.2 Nonfunctional Requirements

Template provided by TechWhirl.com

Template provided by TechWhirl.com

6 Appendices (Not required for performance assessment)

6.2 Glossary of Terms

6.3 Related Documents

Template provided by TechWhirl.com

You might also like