Red Opal Innovations: Business Requirements & Specifications Report

This report, prepared by Red Opal Innovations, details the business requirements and specifications for Tough Trailer. It begins with project background and a stakeholder analysis, identifying key individuals and their roles. The report then outlines business rules, assumptions, and cost constraints, followed by an overview of data gathering methods. Functional requirements, such as customer order creation and real-time communication, are specified, alongside non-functional requirements like maintainability and security. The report also covers physical system requirements, proposed system changes including cloud storage and security enhancements, and includes use case and context diagrams. The conclusion emphasizes the importance of change management and training. The report references several academic sources supporting the analysis and recommendations.

Business Requirements & Specifications Report
Red Opal Innovations

Business Requirements & Specifications Report
Table of Contents
Project Background...............................................................................................................................2
Stakeholder Analysis Table...............................................................................................................2
Business Rules, Assumptions, and Cost Constraints..........................................................................2
Overview of Data Gathering..................................................................................................................2
Functional Requirement Specifications.................................................................................................3
Non-Functional Requirements...............................................................................................................3
Physical System Requirements..............................................................................................................4
Outline of Changes Needed...................................................................................................................4
Use case diagram...................................................................................................................................5
Context diagram....................................................................................................................................5
Conclusion.............................................................................................................................................6
References.............................................................................................................................................7
1

Business Requirements & Specifications Report
Project Background
Stakeholder Analysis Table
Stakeholder
Name
Role Interest Level Involvement
Level
Influence Level
Jenny Smith Office Manager High Moderate High
Sally
Bach/Angelo
Cassati
Sales & Market
Manager
High High High
Rumman-A-
Jannat
IT Trainee Moderate High Moderate
Terrence
Stewart
Supervisor Moderate Moderate High
PM Name Project Manager High High High
Name of the
Members
Project Team Moderate High Moderate
Business Rules, Assumptions, and Cost Constraints
The internal organization policies of Red Opal as well as Tough Trailer will be necessary to
adhere with. It is assumed that the contractual agreements will comprise of the requirements
from both the parties.
There will be 5% of the tolerance limits set for the project costs and it will be necessary that
the project costs are adhered with the estimated values.
Overview of Data Gathering
The three methods that have been shortlisted for the purpose of data gathering are interviews,
surveys, and observations (Eesley, 2018).
Some of the interview questions that shall be asked from all the stakeholders are:
 What is the workflow that is currently followed in the organization?
 What are the major set of issues and challenges that are witnessed?
 What are the expected functionalities that shall be present in the new system?
2

Business Requirements & Specifications Report
 What are the technical tools that are already being used?
 What are the security policies and protocols used?
 What are the access rights that are granted to you currently?
Functional Requirement Specifications
The following requirements must be included in the system that will be developed for Tough
Trailer by Red Opal.
 The customer shall be able to explore the trailer examples through the system.
 The customer shall be able to create order & place quote and make the payments
through the system.
 The employee shall be able to create brochure.
 The designer shall be able to manage quote and take trailer photograph.
 The dummy environment shall be created for the customers and the changes made to
the prototypes in this environment shall not have any impact on the original set of
prototypes.
 The real-time communication between the sales & manufacturing departments and the
customers shall be facilitated (Beimel & Kedmi-Shahar, 2018).
 The automated alerts shall be sent to the parties that fail to respond as per the agreed
time.
 The customized and automated reports shall be generated and extracted from the
system.
 The multi-dimensional designs shall be accessible and presented by the system.
Non-Functional Requirements
The new system shall incorporate the functional requirements as maintainability, security,
performance, usability, and reliability.
The system shall be easy to maintain, shall provide protection from the security attacks, must
be high on performance, shall be usable, and it must be reliable (Mahmoud & Williams,
2016).
3

Business Requirements & Specifications Report
Physical System Requirements
The requirement of a desktop or a mobile device will be needed to access the system. The
design and development tools will be needed for carrying on the design and development
processes.
The network peripherals and components will be needed for system development and
deployment.
Outline of Changes Needed
The new system that is proposed will introduce a few changes in the existing system and
processes. The following are the major changes that will come up.
 The storage of the data sets will be done on the cloud platforms in place of the current
database that is used by the organization. This will make sure that the abundant
storage space is provided. The changes in the access rights, back up schedule, and
retrieval processes will be done accordingly.
 The third-party involvement will be restricted and the changes made by the third-
parties will be exempted. The communication processes will be facilitated with the
third-parties involved (Seal & Kavanagh, 2015).
 There will be changes introduced in the security tools and protocols along with the
access rights and permissions. The overall information security and privacy will be
enhanced and the existing user roles will be revised. The identity verification and
authentication processes will also be revised which will introduce the changes for the
existing resources and the systems. The multi-fold authentication with biometric
recognition will be introduced and the verification procedures will also be improved.
The surveillance and security mechanisms will also be strengthened to enhance
overall security.
These changes will be made to the existing systems and organizations which will have an
impact on the resources as well as the stakeholders.
4

Business Requirements & Specifications Report
Use case diagram
Context diagram
5

Business Requirements & Specifications Report
Conclusion
The project that will be carried out by Red Opal for Tough Trailer will comprise of the
upgrade of numerous processes being conducted in the business organization. It will be
necessary that the handling of the changes is adequately done so that the overall management
and implementation can be improved. The use of trainings and interaction sessions with the
resources will make sure that the changes are effectively carried out and the overall control is
made possible.
6

Business Requirements & Specifications Report
References
Beimel, D., & Kedmi-Shahar, E. (2018). Improving the identification of functional system
requirements when novice analysts create use case diagrams: the benefits of applying
conceptual mental models. Requirements Engineering. doi: 10.1007/s00766-018-0296-z
Eesley, C. (2018). Alumni Surveys as a Data Collection Methodology. SSRN Electronic
Journal. doi: 10.2139/ssrn.3128628
Mahmoud, A., & Williams, G. (2016). Detecting, classifying, and tracing non-functional
software requirements. Requirements Engineering, 21(3), 357-381. doi: 10.1007/s00766-016-
0252-8
Seal, C., & Kavanagh, D. (2015). Organizations Don’t Resist Change, People Do.
Organization Management Journal, 12(3), 123-124. doi: 10.1080/15416518.2015.1082399
7