Business Requirements Document (BRD)



centercenterBusiness Requirements Document (BRD)Project ManagementKEMISTRY - ABSTRACT[Draw your reader in with an engaging abstract. It is typically a short summary of the document. When you’re ready to add your content, just click here and start typing.]Your NameVersion: 0Last Updated: DATE \@ "d/MM/yyyy h:mm am/pm" 11/07/2016 3:33 PM9410077300Business Requirements Document (BRD)Project ManagementKEMISTRY - ABSTRACT[Draw your reader in with an engaging abstract. It is typically a short summary of the document. When you’re ready to add your content, just click here and start typing.]Your NameVersion: 0Last Updated: DATE \@ "d/MM/yyyy h:mm am/pm" 11/07/2016 3:33 PMVersion and ApprovalsVersion HistoryVersion #DateRevised ByReason for changeThis document has been approved as the official Business Requirements Document for <project name>, 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 ApprovalsApprover NameProject RoleSignature/Electronic ApprovalDateProject DetailsProject NameEnter Project NameProject Type(e.g. New Initiative or Phase II)Project Start DateProject End DateProject SponsorProject ManagerContents TOC \o "1-3" \h \z \u 1.Contents PAGEREF _Toc456017566 \h 22.Introduction PAGEREF _Toc456017567 \h 42.1Document Purpose PAGEREF _Toc456017568 \h 42.2Intended Audience PAGEREF _Toc456017569 \h 43.Document Resources PAGEREF _Toc456017570 \h 44.Glossary of Terms PAGEREF _Toc456017571 \h 45.Project Overview PAGEREF _Toc456017572 \h 55.1Project Background PAGEREF _Toc456017573 \h 55.2Purpose of Business Requirements PAGEREF _Toc456017574 \h 55.3Business Goals/Objectives to be achieved PAGEREF _Toc456017575 \h 55.4Benefits/Rationale PAGEREF _Toc456017576 \h 55.5Project Dependencies PAGEREF _Toc456017577 \h 55.6Stakeholders PAGEREF _Toc456017578 \h 56.Key Assumptions and Constraints PAGEREF _Toc456017579 \h 66.1Key Assumptions PAGEREF _Toc456017580 \h 66.2Constraints PAGEREF _Toc456017581 \h 66.3References PAGEREF _Toc456017582 \h 67.Scope Requirements PAGEREF _Toc456017583 \h 67.1Actor Profiles PAGEREF _Toc456017584 \h 67.2Use Cases PAGEREF _Toc456017585 \h 77.3In Scope PAGEREF _Toc456017586 \h 87.4Out of Scope PAGEREF _Toc456017587 \h 98.Business Requirements PAGEREF _Toc456017588 \h 98.1Business Domain PAGEREF _Toc456017589 \h 98.2Functional Requirements PAGEREF _Toc456017590 \h 99.Non-functional requirements PAGEREF _Toc456017591 \h 139.1Security Requirements PAGEREF _Toc456017592 \h 139.1.1Authentication PAGEREF _Toc456017593 \h 139.1.2Authorization and Access Controls PAGEREF _Toc456017594 \h 139.2Standards PAGEREF _Toc456017595 \h 139.3Usability PAGEREF _Toc456017596 \h 149.4Availability Requirements PAGEREF _Toc456017597 \h 149.5Performance Requirements PAGEREF _Toc456017598 \h 149.6Scalability Requirements PAGEREF _Toc456017599 \h 1410.Data Requirements PAGEREF _Toc456017600 \h 1410.1Data Architecture PAGEREF _Toc456017601 \h 1411.Interface Requirements PAGEREF _Toc456017602 \h 1412.Appendixes PAGEREF _Toc456017603 \h 1512.1Appendix A – Business Process Flows PAGEREF _Toc456017604 \h 1512.2Appendix B – Business Rules Catalog PAGEREF _Toc456017605 \h 1512.3Appendix C- Models PAGEREF _Toc456017606 \h 1612.4Use Case Narrative Instructions PAGEREF _Toc456017607 \h 1613.Approval PAGEREF _Toc456017608 \h 17IntroductionDocument PurposeThis document defines the high level requirements [insert project name]. It will be used as the basis for the following activities:Determining client business requirements?Developing test plans, test scripts, and test cases?Determining project completion?Assessing project success?Intended Audience< The main intended audience for this document are the business owners of the proposed system. This document should be readable by business owners of the proposed system. They must be able to verify that their business requirements have been documented here completely, accurately and unambiguously. Data Architects, Application Architects and Technical Architects would also find the information in this document useful when they need to design a solution that will address these business requirements. Since the requirements are documented here in Technology-independent manner, the end-users of the system should be able to comprehend the requirements fairly easily from this document. >Document ResourcesNameBusiness UnitRole<Identify all stakeholders and resources involved in gathering requirements>E.g. StefanGlossary of TermsTerm/AcronymDefinition<Identify any terms and acronyms used within this document>Project OverviewProject 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.>< This section describes if these Business Requirements are as a result of any previous meetings, correspondence, legislation etc.>Purpose of Business RequirementsThis section describes the purpose of the Business Requirements.Tick one or more of the appropriate check boxes and describe the purpose of the Business requirements briefly underneath. FORMCHECKBOX Business requirements for major enhancements to an existing application. FORMCHECKBOX Business requirements for new application development. FORMCHECKBOX Business requirements for replacement application development. FORMCHECKBOX Business requirements for a request for proposals (RFP).Business Goals/Objectives to be achievedThis section describes the major goals/objectives to be achieved with the implementation of the Business Requirements.Benefits/RationaleThis section describes the major benefits to be achieved with the implementation of the Business Requirements.Project Dependencies<List any related known projects that relate in whole or in part, or has a dependency on this project.>StakeholdersThe following comprises the internal and external stakeholders whose requirements are represented by this document:#StakeholdersKey Assumptions and ConstraintsKey Assumptions#AssumptionsA001List any assumptions the requirements are based onA002A003Constraints#ConstraintsC001List any constraints the requirements are based onC002C003References<This section lists the references to previous documentation, correspondence etc , if any, that are related to these Business Requirements.>Scope Requirements< 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>. Actor ProfilesActor NameActor TypeAccess Type neededComments FORMCHECKBOX Stakeholder FORMCHECKBOX Primary Actor FORMCHECKBOX Supporting Actor FORMCHECKBOX Create FORMCHECKBOX Print FORMCHECKBOX Read FORMCHECKBOX Export FORMCHECKBOX Update FORMCHECKBOX Others FORMCHECKBOX Delete FORMCHECKBOX Stakeholder FORMCHECKBOX Primary Actor FORMCHECKBOX Supporting Actor FORMCHECKBOX Create FORMCHECKBOX Print FORMCHECKBOX Read FORMCHECKBOX Export FORMCHECKBOX Update FORMCHECKBOX Others FORMCHECKBOX Delete FORMCHECKBOX Stakeholder FORMCHECKBOX Primary Actor FORMCHECKBOX Supporting Actor FORMCHECKBOX Create FORMCHECKBOX Print FORMCHECKBOX Read FORMCHECKBOX Export FORMCHECKBOX Update FORMCHECKBOX Others FORMCHECKBOX DeleteUse Cases<Each Use Case should be documented using this template. Refer to the Appendix for Use Case Narrative instructions> Use Case ID:Use Case Name:Created By:Last Updated By:Date Created:Date Last Updated:Actors:Description:Pre-conditions:Post-conditions:Normal Course:Alternative Courses:Exceptions:Includes:Priority:Frequency of Use:Business RulesSpecial Requirements:Assumptions:Notes and Issues:Use Case GraphicExample of a completed use case:Use Case ID:1Use Case Name:View Interactive Campus MapCreated By:Dan SwardLast Updated By:Date Created:4/19/09Date Last Updated:Actors:UserDescription: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:Open browserNavigate to campus map URLInteract with the campus map using available functionalityAlternative Courses:NoneExceptions:NoneIncludes:Priority:HighFrequency of Use:Once per visit.Business RulesTBD…Special Requirements:24/7 accessResponse times comparable to common web mapping solutions (e.g. Google Maps)U of M accessibility requirementsU of M eCommunications requirementsAssumptions:Notes and Issues:Use Case GraphicIn Scope<Scope List>Out of Scope<List of activities out of scope>Business RequirementsBusiness Domain<What is the client’s business domain all about? Who is his/ her target audience? What are the expectations of this target audience vis-à-vis the client’s business? What are the performance metrics of the website to be built?>Functional RequirementsThe following sections document the various business requirements of this project.Requirement TypeID – Prefix ??ID – NumberFunction – Feature - RequirementUse Case ReferenceRequiredDesirable????CommentsBusiness User RequirementsF0001F0002F0003F0004F0005F0007F0007F0008Reporting RequirementsF0001F0002F0003F0004F0005F0006F0007F0008User Access/Security RequirementsF0001F0002F0003F0004F0005F0007F0007F0008Service Level/Performance RequirementsF0001F0002F0003F0004F0005F0007F0007F0008Scalability RequirementsF0001F0002F0003F0004F0005F0007F0007F0008Support and Maintenance RequirementsF0001F0002F0003F0004F0005F0007F0007F0008Non-functional requirementsThis section describes the non-functional requirements part of the Business Requirements. <A non-functional requirement is typically a special requirement that is not easily or naturally specified in the text of the use case’s or function’s event flow. Examples of non-functional requirements include legal and regulatory requirements, application standards, and quality attributes of the system to be built including usability, reliability, performance or supportability requirements. These requirements define the overall qualities or attributes of the resulting Website. They place restrictions on the Website being developed, the development process, and specify external constraints that the site must meet. Examples are and not limited to safety, usability, reliability and performance requirements. Others can include supportability and being business critical.>Security RequirementsThis section describes the Security requirements part of the Business Requirements.Authentication<This section describes the Authentication requirements part of the Business Requirements. Authentication is the process of verifying the genuineness of claims that a person/group makes to establish identity/eligibility for access to services. In order to ascertain the Authentication requirements of the Application, it is required to analyse the type of transactions that different Use cases/Business Functions trigger within the Application.>Authorization and Access Controls <Authorization is the process of determining if the person/group, once identified through the “Authentication process”, is permitted to have access to certain services.><See Actors in Scope section if you used Use Cases otherwise define the authorised access here.>Standards<Adhering to any standards?>Usability<Usability is the ease with which a user can learn to operate, prepare inputs for, and interpret outputs of system or component. Usability requirements include but not limited to: Informative error messages, Well-formed graphical user interfaces with consistency in mind. Usability metrics can be used to analyse user-interface design requirements, including user needs and design principles>Availability Requirements<When should the website functions be available and to who when?>Use Case / Business Function NameAvailability Requirements- Regular work hours- 24x7- Any other (please describe)Performance Requirements This section describes system performance expectation levels (response times).Scalability Requirements<This section describes how the system is expected to scale to new higher or lower levels. Both user and application scalability requirements are described here. >Data RequirementsThis section describes the Data requirements part of the Business Requirements. Data ArchitectureThis section describes the Data Architectural requirements part of the Business Requirements. <Insert High level ERD>Interface RequirementsThis section describes User Interface requirements for the proposed system.Please list and describe here what other external systems/business functions are required to be interfaced with the proposed system from Business Requirements perspective. Example : This system needs to interface with the CAS in order to receive some input data. Please avoid describing system design and technical issues.AppendixesAppendix A – Business Process Flows<Describe the current existing process workflow using flow diagrams (i.e. Visio Flowcharts) and/or a detailed narrative.>Appendix B – Business Rules Catalog<Instructions: Use the following template for each business rule. >Business Rule Name:<The name should give you a good idea about the topic of the business rule.>Identifier<Defines unique identifier.> EXAMPLE: BR1Description<Defines the rule in detail.> EXAMPLE: “All employee labor is tracked, reported and billed in 15 minute increments.”Example<(Optional) An example of the rule>Source<Source of the rule. E.g. stakeholder>Related Rules<List of related rules, to support traceability>Appendix C- Models<Insert models here>Use Case Narrative Instructions<Instructions for completing the Use Case Narrative are included here. Remove these instructions from the completed Business Requirements Document>.Use Case Field NameDefinitionUse Case IDGive 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 NameState 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 versionCreated ByInclude the name of the person who initially documented this Use Case.Date CreatedEnter the date on which the use case was initially documentedDate Last UpdatedEnter the date on which the use case was most recently updatedLast Updated ByInclude the name of the person who performed the most recent update to the use case description.ActorEnter 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.DescriptionProvide 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.PreconditionsList 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 taskPost conditionsDescribe 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 valueNormal CourseProvide 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 <accomplish the task stated in the use case name>?” This is best done as a numbered list of actions performed by the actor, alternating with responses provided by the system.Alternative CoursesDocument 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.1ExceptionsDescribe 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.1IncludesList 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.PriorityIndicate 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 UseEstimate the number of times this Use Case will be performed by the actors per some appropriate unit of time.Business RulesList any business rules that influence this Use Case.Special RequirementsIdentify 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.AssumptionsList 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 IssuesList 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.ApprovalThis document has been approved as the official Business Requirements Document for the SUBJECT \* MERGEFORMAT Project Name project.Following approval of this document, changes will be governed by the project’s change management process, including impact analysis, appropriate reviews and approvals, under the general control of the Master Project Plan and according to Project Support Office policy.Prepared bySignatureDate DOCPROPERTY "Author" \* MERGEFORMAT Author's Name[Title][Organization]Approved bySignatureDate[Client Acceptor’s Name][Title][Organization] ................
................

In order to avoid copyright disputes, this page is only a partial summary.

Google Online Preview   Download