Version and Approvals



Download 257.77 Kb.
Date conversion05.02.2017
Size257.77 Kb.


[Insert Project Name]

Business Requirements Document (BRD)


Version 

Version and Approvals


UTORS


Version History




Version #

Date

Revised By

Reason for change
















































This document has been approved as the official Business Requirements Document for


, and accurately reflects the current understanding of business requirements. Following approval of this document, requirement changes will be governed by the project’s change management process, including impact analysis, appropriate reviews and approvals.


Document Approvals




Approver Name

Project Role

Signature/Electronic Approval

Date

















































Table of Contents


Version and Approvals ii

Project Details 1

Overview 1

Document Resources 1

Glossary of Terms 1

Project Overview 1

Key Assumptions and Constraints 2

Use Cases 2



4

Business Requirements 5



Appendixes 7


Project Details


Project Name

Enter Project Name

Project Type

(e.g. New Initiative or Phase II)

Project Start Date




Project End Date




Project Sponsor




Primary Driver

(e.g. Mandatory or Efficiency)

Secondary Driver




Division




Project Manager/Dept





Overview
This document defines the high level requirements [insert project name]. It will be used as the basis for the following activities:


  • Creating solution designs

  • Developing test plans, test scripts, and test cases

  • Determining project completion

  • Assessing project success


Document Resources


Name

Business Unit

Role














































Glossary of Terms


Term/Acronym

Definition































Project Overview

4.1 Project Overview and Background


<This information can be taken from the Project Charter. This is a brief description of what the project is about. It includes the current situation, the problem and the objectives. This section serves as the vision statement for the requirements. Each requirement should bring the project closer to the vision.>

4.2 Project Dependencies



4.3 Stakeholders


The following comprises the internal and external stakeholders whose requirements are represented by this document:





Stakeholders

1.




2.





3.






Key Assumptions and Constraints

5.1 Key Assumptions and Constraints





#

Assumptions




List any assumptions the requirements are based on































#

Constraints




List any constraints the requirements are based on
































Use Cases

< The primary purpose of the Use Case is to capture the required system behavior from the perspective of the end-user in achieving one or more desired goals. A Use Case contains a description of the flow of events describing the interaction between actors and the system. The use case may also be represented visually in UML in order to show relationships with other the use cases and actors>.

Use Case Diagram




Use Case Narrative






Use Case ID:




Use Case Name:




Created By:




Last Updated By:




Date Created:




Date Last Updated:







Actors:




Description:




Preconditions:




Postconditions:




Normal Course:




Alternative Courses:




Exceptions:




Includes:




Priority:




Frequency of Use:




Business Rules




Special Requirements:




Assumptions:




Notes and Issues:



Use Case Graphic




Example of a completed use case:


Use Case ID:

1

Use Case Name:

View Interactive Campus Map

Created By:

Dan Sward

Last Updated By:




Date Created:

4/19/09

Date Last Updated:







Actors:

User

Description:

This use case describes the main way this interactive campus map will be used – as a web browser accessed application. The user accesses the appropriate URL and interacts with the functionality made available.

Preconditions:

Web browser opened, and interactive campus map URL accessed.

Postconditions:

User navigates from interactive campus map web site.

Normal Course:

  1. Open browser

  2. Navigate to campus map URL

  3. Interact with the campus map using available functionality

Alternative Courses:

None

Exceptions:

None

Includes:




Priority:

High

Frequency of Use:

Once per visit.

Business Rules

TBD…

Special Requirements:

  • 24/7 access

  • Response times comparable to common web mapping solutions (e.g. Google Maps)

  • U of M accessibility requirements

  • U of M eCommunications requirements

Assumptions:




Notes and Issues:




Use Case Graphic



Business Requirements


The following sections document the various business requirements of this project.


Requirement Type

ID – Prefix ??

ID – Number



Function – Feature - Requirement


Use Case Reference



Required

??

??

??

Comments





Business User Requirements




f

0001

























f

0002

























f

0003

























f

0004
























F

0005

























F

0007

























f

0007

























f

0008

























Reporting Requirements




f

0001

























f

0002

























f

0003

























f

0004
























F

0005

























F

0007

























f

0007

























f

0008

























User Access/Security Requirements




f

0001

























f

0002

























f

0003

























f

0004
























F

0005

























F

0007

























f

0007

























f

0008

























Service Level/Performance Requirements




f

0001

























f

0002

























f

0003

























f

0004
























F

0005

























F

0007

























f

0007

























f

0008

























Scalability Requirements




f

0001

























f

0002

























f

0003

























f

0004
























F

0005

























F

0007

























f

0007

























f

0008

























Support and Maintenance Requirements




f

0001

























f

0002

























f

0003

























f

0004
























F

0005

























F

0007

























f

0007

























f

0008






















Appendixes

Appendix A – Business Process Flows





As Is Diagrams





To Be Diagrams



Appendix B – Business Rules Catalog





Business Rule Name:



Identifier

EXAMPLE: BR1

Description

EXAMPLE: “All employee labor is tracked, reported and billed in 15 minute increments.”

Example

<(Optional) An example of the rule>

Source



Related Rules


Appendix C- Models




Traceability Matrix




Use Case Narrative Instructions


.


Use Case Field Name

Definition

Use Case ID


Give each use case a unique numeric identifier, in hierarchical form: X.Y. Related use cases can be grouped in the hierarchy. Functional requirements can be traced back to a labeled Use Case.

Use Case Name

State a concise, results-oriented name for the use case. These reflect the tasks the user needs to be able to accomplish using the system. Include an action verb and a noun. Some examples:

  • View part number information.

  • Manually mark hypertext source and establish link to target.

  • Place an order for a CD with the updated software version

Created By

Include the name of the person who initially documented this Use Case.

Date Created

Enter the date on which the use case was initially documented

Date Last Updated

Enter the date on which the use case was most recently updated

Last Updated By

Include the name of the person who performed the most recent update to the use case description.

Actor

Enter the person or other entity external to the software system being specified who interacts with the system and performs use cases to accomplish tasks. Different actors often correspond to different user classes, or roles, identified from the customer community that will use the product. Name the actor(s) that will be performing this Use Case.

Description

Provide a brief description of the reason for and outcome of this use case, or a high-level description of the sequence of actions and the outcome of executing the Use Case.

Preconditions

List any activities that must take place, or any conditions that must be true, before the Use Case can be started. Number each precondition. Examples:

  • User’s identity has been authenticated.

  • User’s computer has sufficient free memory available to launch task

Post conditions

Describe the state of the system at the conclusion of the use case execution. Number each post condition. Examples:

  • Document contains only valid SGML tags.

  • Price of item in database has been updated with new value

Normal Course

Provide a detailed description of the user actions and system responses that will take place during execution of the use case under normal, expected conditions. This dialog sequence will ultimately lead to accomplishing the goal stated in the use case name and description. This description may be written as an answer to the hypothetical question, “How do I ?” This is best done as a numbered list of actions performed by the actor, alternating with responses provided by the system.

Alternative Courses

Document other, legitimate usage scenarios that can take place within this use case separately in this section. State the alternative course, and describe any differences in the sequence of steps that take place. Number each alternative course using the Use Case ID as a prefix, followed by “AC” to indicate “Alternative Course”. Example: X.Y.AC.1

Exceptions

Describe any anticipated error conditions that could occur during execution of the use case, and define how the system is to respond to those conditions. Also, describe how the system is to respond if the use case execution fails for some unanticipated reason. Number each exception using the Use Case ID as a prefix, followed by “EX” to indicate “Exception”. Example: X.Y.EX.1

Includes

List any other use cases that are included (“called”) by this use case. Common functionality that appears in multiple use cases can be split out into a separate use case that is included by the ones that need that common functionality.

Priority

Indicate the relative priority of implementing the functionality required to allow this use case to be executed. The priority scheme used must be the same as that used in the software requirements specification.

Frequency of Use

Estimate the number of times this Use Case will be performed by the actors per some appropriate unit of time.

Business Rules

List any business rules that influence this Use Case.


Special Requirements

Identify any additional requirements, such as nonfunctional requirements, for the use case that may need to be addressed during design or implementation. These may include performance requirements or other quality attributes.

Assumptions

List any assumptions that were made in the analysis that led to accepting this use case into the product description and writing the use case description.

Notes and Issues

List any additional comments about this use case or any remaining open issues or TBDs (To Be Determined) that must be resolved. Identify who will resolve each issue, the due date, and what the resolution ultimately is.




The database is protected by copyright ©dentisty.org 2016
send message

    Main page