EXECUTIVE SUMMARY SNAPSHOT
Provide a brief executive summary (overview of your business requirements)
here. Your executive summary should be a “snapshot” of the purpose of your
business requirements, including a brief description of any analysis,
findings, project description, scope, business drivers, proposed process,
current process, and functional requirements.
CURRENT PROCESS
In this section, describe the project for which you are writing this business
requirements document. Describe the projet´s purpose, what the current
process/solution is for the project, what the challenges are, and why you need
to undertake the project.
Provide details of your current process for addressing the primary issue your
project attempts to solve. Feel free to include diagrams, flowcharts, or other
visuals to illustrate the current process.
PROPOSED PROCESS
Provide details of the proposed process for addressing the primary issue your
project attempts to solve. Feel free to include diagrams, flowcharts, or other
visuals to illustrate the proposed process. For this process, we recommend you
use the same illustrative tool/style that you used for your current process (above).
FUNCTIONAL REQUIREMENTS
Detail the project’s functional requirements by enumerating the ways in which the current process addresses the issue and by describing the functional requirements necessary to the project’s success.
PRIORITY
Use the following priority table. It allows you to apply a ratings system to
your requirements, so you have the visibility (into the value, status, and
description of each requirement) that’s necessary for determining whether a
particular requirement is essential to project success:
REQUIREMENTS CATEGORIES (RC1)
Detail the project’s functional use; break down your project’s requirements
into categories so that they’re easy to understand. You can duplicate this
section for any successive project categories as needed. The following table
includes a unique ID for each requirement, the details of each requirement,
the priority of each requirement, and the position of the person who is driving
or is responsible for the requirement. You may also have requirements that
outline how your software will interact with other tools, which brings us to
external interface requirements. External Interface Requirements External
interface requirements are specific types of functional requirements. These
are especially important when working with embedded systems. They outline how
your product will interface with other components. There are several types of
interfaces you may have requirements for, including:
* User
* Hardware
* Software
* Communications System Features System features are a type of functional requirements. These are features that are required in order for a system to function
NON-FUNCTIONAL REQUIREMENTS
Detail all non-functional requirements (NFRs) of the project, including such
things as features, system behaviour, and project characteristics that relate
to user experience. Examples, Performance requirements, Saftey requirements,
Security requirements, Usability requirements, Scalability.
Standard non disclosure agreement for software development projects
The software development non-disclosure agreement (NDA) is intended for use
when sharing software business trade secrets with consultants, investors,
contractors, potential licensees, and anyone else who has access to your
company’s confidential information. Such information could include your
unpublished computer code, design definitions and specifications, flow
diagrams and flowcharts, formulas and algorithms, system and user documentation,
data structures and data compilations, marketing and sales data, customer
lists, and pending patent applications.
Software development non-disclosure agreement (NDA)
Click to download