The world’s Largest Sharp Brain Virtual Experts Marketplace Just a click Away
Levels Tought:
Elementary,Middle School,High School,College,University,PHD
| Teaching Since: | Jul 2017 |
| Last Sign in: | 304 Weeks Ago, 2 Days Ago |
| Questions Answered: | 15833 |
| Tutorials Posted: | 15827 |
MBA,PHD, Juris Doctor
Strayer,Devery,Harvard University
Mar-1995 - Mar-2002
Manager Planning
WalMart
Mar-2001 - Feb-2009
Here you go, this is week one, weeks 2 and 3 are attached. Thank you.
Â
Enter Assignment Name Here
Business Requirements Document (BRD)
Â
Â
Â
Â
Prepared by: xx
Instructor: xx
Date: xx/xx/xx
Â
Table of Contents
Â
Revision History                                                                             3
1.    Assumptions, Constraints, and Dependencies                       3
1.1     Related Projects and Dependencies                                 3
1.2     Assumptions and Constraints                                           3
2.    Business and Customer Requirements                                   3
2.1     Strategic Business and Customer Requirements               3
3.    References                                                                              3
Â
Â
Â
Â
Â
Â
To update table of contents
Â
1.     Make changes to the document
2.     Right click on the table of contents
3.     Select Update Field
Â
Delete instructions in blue before submitting BRD
Â
Revision History
Name
Date
Changes and Reason for Changes
Version
Â
1.   Assumptions, Constraints, and Dependencies1.1   Related Projects and Dependencies
Enter any dependencies here.
Â
1.2Â Â Â Assumptions and Constraints
Â
ID
Assumption or Constraint
1.2.1
1.2.2
2.   Business and Customer Requirements
Enter any summary requirement information here.
Â
2.1Â Â Â Strategic Business and Customer Requirements
List requirements that are needed to align with the business goals or objectives and strategic initiatives. These could also include Customer Requirements from the end users of our products and services. List the goal, objective, or strategic initiative with which the requirement is aligning.
·      Req. ID
·      Date:  Date the requirement was identified.
·      Requirement: Enter the requirement description.
·      Priority:  Enter the priority of the requirement – MH (Must Have) or WH (Want to Have).
·      Status:  Enter the status of the requirement at final sign-off (A: Approved, C: Cancelled, D: Delayed). Changes to the status after final sign-off should be made directly into this document and recorded in the revisions log. Approved requirements will be used to write test cases for the solution.
Req ID
Date
Requirement
Priority
Status
2.2.1
3.   References
Enter any references here.
#
Req ID Related
Reference Description
Location
Owner
3.1.1
3.1.2
Attachments:
----------- Â ----------- H-----------ell-----------o S-----------ir/-----------Mad-----------am ----------- Th-----------ank----------- yo-----------u f-----------or -----------you-----------r i-----------nte-----------res-----------t a-----------nd -----------buy-----------ing----------- my----------- po-----------ste-----------d s-----------olu-----------tio-----------n. -----------Ple-----------ase----------- pi-----------ng -----------me -----------on -----------cha-----------t I----------- am----------- on-----------lin-----------e o-----------r i-----------nbo-----------x m-----------e a----------- me-----------ssa-----------ge -----------I w-----------ill----------- be----------- qu-----------ick-----------ly