This website uses cookies to ensure you have the best experience. Learn more

Business Requirement Document Essay

1366 words - 6 pages

IS 390 Group Project Milestone Two
Due: Oct. 29th

In this milestone, you are to deliver a document called BRD (Business Requirement Document). Although difference formats exist for BRD, the one you are required to present is popularly used in current IS practice. It serves as a “contract” between you and your client on the scope, schedule & expected outcome of your project. A BRD contains seven sections.

I. Version Control

Since a BRD might go through several rounds of revision (iterative process, remember?), this first section is simply used to keep track of the project history.

A. Revision history:
Simply a table with the following columns: Version# (0.1, 0.2…), Date of ...view middle of the document...

This is the person assigned to get it done (Could be more than one).

* An ‘A’ designation indicates that the person is accountable. This might be the person who manages the responsible person in some organizations. This person will be “called into account” if the task is not completed. In our project, this should be the project manager (you can take turn to serve as project manager during each stage). In other words, if I find a task not ideally completed, the person with an “A” in the cell will be the one I talk to.

* Others might be 'C' consulted about aspects of the task but are not directly accountable or responsible for that matter involved. For example, both your client and people outside of your group (including me) could be consulted regarding your project.

* An 'I' person (informed) is affected by the activity/decision and therefore need to be kept informed, but do not participate in the effort. (They are notified after the final decisions are made.)

Below is a sample RACI table:

RACI Table Example |
 Activity | Deployment
Ownership | Project
Identification | Project
Selection | Project
Execution | Project
Results | Team
Support | Sustain
Changes |
Executive Team | A | R | A |   |   |   |   |
Champion | R | A | R |   |   | R |   |
P&L Managers |   | I |   |   | A | R | R |
Process Owner |   | C |   | R | R | R | A |
Black Belt |   | C |   | R | R | A |   |
Team Leader/
Green Belt |   |   |   | R | A |   |   |

II. Executive Summary

You need to write a concise summary using one to two pages. It must cover:

* Overview (1 – 2 sentences: this project is for a system that…)
* Background: domain knowledge! Should cover the industry and the company
* Objectives of the project --- what are the final deliverables?
* Requirements --- resources required for the project in terms of hardware, software, personnel, finance, etc. Don’t worry too much about it for your project.
* Proposed strategy --- in-house development? Package solution? Outsourcing? Don’t worry about it for this milestone

This is where you insert your PROJECT CHARTER AND SYSTEM SERVICE REQUEST (SSR) (please refer to day 5, page 10). Your SSR is basically a one-page summary that contains the information listed above.

III. Scope

What tasks are included in your scope? What are not included (for example, you know that implementation of the system is NOT)? What are the constraints (for example, time is certainly an issue here)? Be VERY specific. For example, do not say: “our project is on a very tight schedule”. Instead, say: “the final report of the project is due on ..., and the design is expected to be finalized by …”

IV. Risk Analysis

Risk is anything that could impact the completion of a project on time, in budget and according to specification. Try to estimate any potential risk involved in the project. There are five areas of risks: technological (the availability of a...

Other Papers Like Business Requirement Document

Read the Case Study Can Detroit Make the Cars Customers Want? and Answer the Following Questions:

2605 words - 11 pages skills. Education includes: Professional Summary Business Requirements Gathering, Business Process Flow, System Analysis, Business Process Modeling and Business Analysis. Industry experience in Healthcare, Finance, Health Insurance and Banking sector. Expertise experience in writing Business requirements document, System requirements specifications, Functional requirements document, developing Use Cases, creating screen mockups, and

Vendor Selection Process Essay

3921 words - 16 pages first task that the vendor selection team needs to accomplish is to define, in writing, the product, material or service that you are searching for. Next define the technical and business requirements. Also, define the vendor requirements. Finally, publish your document to the areas relevant to this selection process and seek their input. Have the team analyze the comments and create a final document. In summary: Assemble an Evaluation Team

Strategic Hr

576 words - 3 pages organisations and they offer support to key business applications and information systems. The most common database model used commercially is the relational one. The aim of this unit is to: * Provide a knowledge and understanding of database systems, including * Design principles * Practical implementation and development skills for both the system designer and software engineer. The importance of structured query

Google Error Leaks Website Owners' Personal Info

5699 words - 23 pages [pic] Ministry/Agency Name [Complete file/properties to populate fields on this page and in the document headers] Project Name Project #: Business Requirements Document (BRD) Template Prepared by: Author's Name Prepared for: Date Submitted: [Date] Project Sponsor: Project Sponsor's Name Client Acceptor: Project

Innovation in a Requirement Life-Cycle Framework

2961 words - 12 pages Innovation in a Requirement Life-Cycle Framework Abstract In this paper, a requirements-based framework of innovation is discussed. Both customer and expert defined requirements are considered. The proposed framework treats requirements as evolving entities and is implemented using a data-driven approach. It provides a new perspective in support of the innovative product development process. Keywords: Innovation, requirements management

Electricity Supply Business Models

1078 words - 5 pages financial inputs they can raise. The contributions would reinforce the communities’ commitment to the initiatives and again the sustainability level would be increased. It should be noted that although both generation and distribution types of business models are discussed, the requirement for the PACEAA project output is the latter. This is as stipulated under Work Package 3 (see the Appendix) of the project contract sheets. The generation

System Design

1319 words - 6 pages Presentation for Dennis, Wixom, & Roth Systems Analysis and Design, 4th Edition Copyright 2009 © John Wiley & Sons, Inc. All rights reserved. What is a Requirement? 1) A statement of what the system must do 2)A statement of characteristics the system must have 3)Focus is on business user needs during analysis phase 3 - 10 PowerPoint Presentation for Dennis, Wixom, & Roth Systems Analysis and Design, 4th Edition Copyright 2009 © John Wiley

Project Deliverable 6 Project Plan

812 words - 4 pages Document all revisions made to the written project plan in the Document Control section of the business requirements document from Project Deliverable 2: Business Requirement. Note: This documentation must outline the revisions made to the previous deliverables required in Section 1: Written Project Plan. Section 3: Project Plan PowerPoint Presentation Additional to your detailed executive summary you must present your findings to the executive

This Assignment Consists of Three (4) Sections: a Written Project Plan, Revised Business Requirements Document,

694 words - 3 pages revisions made to the written project plan in the Document Control section of the business requirements document from Project Deliverable 2: Business Requirement. Note: This documentation must outline the revisions made to the previous deliverables required in Section 1: Written Project Plan. Section 3: Project Plan PowerPoint Presentation Additional to your detailed executive summary you must present your findings to the executive team and the

System Evaluation

711 words - 3 pages knows the end result. We encountered a few shortfalls. Why not purchase an existing Commercial off the shelf (COTS) product that other agencies are using? This system may involve attributes we really don’t need. After months of studies and analysis, we developed a solid, Business Requirement Document to deliver to a vendor. The vendor was provided a detailed document of the requirements needed to create our new Time and Attendance Systems

Public Issue

1791 words - 8 pages least 1000 prospective allottees in its issue. Draft Offer Documents• Draft offer document is an offer document filed with SEBI for specifying changes, if any, in it, before it is filed with the Registrar of companies (ROCs). Draft offer document is made available in public domain including SEBI website, for enabling public to give comments, if any, on the draft offer document. Red Herring Prospectus • Red herring prospectus is an

Related Essays

System Analysis And Design

2783 words - 12 pages | |Requirement text: |When items are purchased and reached at the gate of store receiving document is used | |Requirement type: |Functional – Data | |Requirement details |Items should be purchased and reached at the store and Items are added to the stock | |and constraints: |Purchase

Project Plan Essay

1201 words - 5 pages What is a Project Plan? The Project Plan is the central document by which the project is formally managed. A Project Plan is a document which lists the activities, tasks and resources required to complete the project and realise the business benefits outlined in the Project Business Case. A typical Project Plan includes: • A description of the major phases undertaken to complete the project • A schedule of the activities, tasks, durations

Lyt 2 Task 1 Essay

849 words - 4 pages for the business. While each location has access to the documents on its file server, the documents are not synchronized between the locations. This requires that when documents are required by another branch (branch A), branch A must contact the branch location with the document (branch B) and request the document. Branch B must then, locate the document and email or fax the document to branch A. Once branch A has the document, any edits or

The Functional Consultant Has Tounderstand The Modules They Are Implementing And The Set Up And Configuration Options Available

365 words - 2 pages knowledge about the current business process, design current business flows, study current business processes and its complication -in all we can say that this is getting through with the current business setupFlow diagrams and DFDs are prepared, all this forms the part of the AS IS document.""Everything configured has to be documented according to their categories in the form of predefined templates; these then have to be approved by the team