Business Requirements Document - JustAnswer



Hi – This document has three parts:

First is an overview of a Business Requirements Document, and the sections that I’d normally put in there. (In blue font) The template that you are using in your class might vary from this; go with what you have in class – unless there is a section in here that isn’t in your class template and you think it might be usefule.

Second is a rough outline of the business requirements as I see them from your problem statement. Not all sections of the BRD outline will be in the part that you have to do for the Business Requirements. (In standard black font) IMPORTANT: I have captured just a few of the main ideas as I see them in your problem statement. When looking at what I’ve written below, what other areas would you expect need to be added, based on your better understanding of the background from class, or your discussions with your other team members? This is a DRAFT – you’ll want to look over the sections for Requirements, and add anything that I didn’t get a chance to include, or forgot. Hopefully the examples give you and idea of the basic requirements description process.

Third, just to keep things together, is a copy of the problem statement as copied from the Just Answer web page (your posting). (In red font)

You need to cut/paste the sections that you like into your own document…. feel free to modify what you put in there to change it, or include more of your own words, and make the result more your own. Good luck!! Remove these notes from whatever you turn in.

Steve

Business Requirements Document (EXAMPLE)

This is a very high level example of a Business Requirements Document. They vary, based on the project you’re working on, but this dorm gives a general overview of the major topics you’d address in this document.

Purpose:

The business requirements define the key aspects of the business problem, and what requirements will resolve the problem. It also looks at the issues and risks that have an impact on the business system (such as not doing anything, or the issues of selecting a new technology).

Problem Definition:

Describe the basic problem / situation.

You might include – reports that need to be generated, heavy workloads, how long it takes to consolidate data, disconnected users, etc.

(These first two sections may be included in the Executive Summary, or repeat information from it.)

Objectives:

Describe the objectives of the system / solution that you need to put into place.

For example:

The selected system will allow data connections between the corporate divisions, and so expedite data consolidation, reduce the workloads required to generate inventory reports and result in faster report generation.

System Requirements:

Describe the required features and functions that the system will need to have. Which ones are mandatory (must haves). If possible to begin to define basic functional requirements, this is a good place to insert them.

Mandatory Requirements:

Functional Requirements:

Constraints:

Define any restraints that may be in place.

Budget limitations are xxxx….

Need to train IT resources on new technology

Etc.

Assumptions:

Describe any underlying assumptions that need be called out.

Ex: Budget will remain available for the project.

Project sponsor is ….., and will remain available for the project.

IT staff can be hired or trained to support the new system.

Exclusions:

Discuss things that the system will not address, or will not be accomplished by this version of the system.

Impact Statement:

What will happen when the system is put in place? What will happen if it doesn’t??

Risk Statement:

What are the risks of not doing the system? (Or of doing it?)

If the new system is not implemented, we project that a cost of $x in ongoing staff costs to manually re-enter data between systems, etc….

Business Requirements Document

Riordan Manufacturing

Inventory and Manufacturing Processes Integration

Executive Summary:

Specifically, end of month reports per facility are not accessible to corporate headquarters in San Jose within a timely manner. The Georgia and Michigan facility (different operating systems) convertibility and hardcopy reports are labor intensive and costly as they must be re-entered manually taking 15 to 20 days for final reports to reach San Jose corporate office. Additionally, inventory from the external facilities is in question. The lack of continuity between facilities is costly and timely.

The following actions are presented as alternatives for these issues

:

1. VirtualBox from Sun Microsystems,

Open Source Alternative: General purpose full virtualizer;

• Modularity: well-defined internal programming interfaces and a client/server design.

• Virtual machine descriptions in XML: Virtual machine definitions can therefore easily be ported to other computers.

• Guest Additions for Windows and Linux: special software installed inside Windows and Linux virtual machines to improve performance and make integration much more seamless.

• Shared Folders: Easy data exchange between hosts and guests, declaring certain host directories as shared folders, which can then be accessed from within virtual machines.

• USB controllers: No need to install device specific drivers on the host.

• Remote Desktop Protocol: VirtualBox supports the standard RDP.

2. VirtualBOS: Business Operating Systems,

A proven leader in on-demand, web-based inventory and warehouse management solutions. Increased visibility and control of inventory moving through purchasing, receiving, fulfillment and shipping.

• Real-TimeView: Of all inventory on-hand, centralized system for inventory control and accuracy across multiple locations.

• Reduces Lead time: Alert’s you when preferred inventory levels all below optimal thresholds, purchasing and re-order as needed.

• Web-based: No need for IT solutions.

3. Microsoft Office Accounting Express:

Easy to integrate and use with current MS server.

Purpose:

The proposed systems would integrate incorporating all balance sheets, income statements, and general ledgers at each facility to corporate headquarter. This will include update software for inventory.

Problem Definition:

Riordan Manufacturing is headquartered in San Jose, and operates several facilities, in Georgia, Michigan, and the People’s Republic of China. Consolidation of inventory and manufacturing information from each of the locations is time consuming and effort intensive – and is complicated because the different locations use different systems that are not compatible. As a result, data consolidation and summaries require a manual re-entry of data from different locations. This makes it difficult for the San Jose headquarters

System Requirements:

The selected solutions system will improve data connections between the Riordan locations. The objective is to provide an improved system for data consolidation and reduce the workloads, costs, and time required to generate inventory reports, and result in faster report generation. Improved inventory management and updates will be an important component of this new system.

The following high level requirements have been extracted from the problem statement.

1. Integrate accounting systems between locations, including balance sheets, income statements, and general ledgers.

a. Remove current manual data entry and consolidation processes.

2. Integrate Inventory Management (including update) processes.

a. Maintain inventory accuracy across multiple locations

b. Improve order management and reduce inventory carrying costs.

3. Consolidation of accounting information must be quickly accomplished at corporate offices.

4. Rapid Report generation (financials, inventory, manufacturing) at corporate headquarters using consolidated data.

5. Solution needs to be implemented with a minimum of disruption to manufacturing locations. (?? Do you want this in here?)

6. Improved data transmission

7. A web based solution, that causes a minimum of disruption to existing locations, while providing data integration, consolidation, and manufacturing and inventory control is preferred.

Functional Requirements: (This may be more detailed that the problem statement provides, not sure…. but look at these and include what looks pertinent, remove the rest. These are general examples)

1. Business User Requirements

a. specify the required training time for a normal users and a power user to become productive at particular operation. For example: The User Interfaces will be designed for usage with minimal or no user training.

b. specify measurable task times for typical tasks or base the new system’s usability requirements on other systems that the users know and like. For example: The user should be able to reach the widget details after only 3 mouse clicks

c.

2. Reporting Requirements

a.

3. User Access/Security Requirements

a.

4. Service Level/Performance Requirements

a. response time for a transaction (average, maximum)

b. throughput, for example, transactions per second

c. capacity, for example, the number of customers or transactions the system can accommodate

d. degradation modes (what is the acceptable mode of operation when the system has been degraded in some manner)

e. resource utilization, such as memory, disk, communications, etc.>

5. Reliability

a. Mean Time Between Failures (MTBF) — this is usually specified in hours, but it could also be specified in terms of days, months or years.

b. Accuracy—specify precision (resolution) and accuracy (by some known standard) that is required in the system’s output.

c. Maximum Bugs or Defect Rate—usually expressed in terms of bugs per thousand of lines of code (bugs/KLOC) or bugs per function-point (bugs/function-point).

d. Bugs or Defect Rate—categorized in terms of minor, significant, and critical bugs: the requirement(s) must define what is meant by a “critical” bug; for example, complete loss of data or a complete inability to use certain parts of the system’s functionality.

6. Scalability Requirements

a.

7. Support and Maintenance Requirements

a. The reports and software interface created as part of this project will be online / operational during normal business hours.

b. The maximum allowable downtime will be 3 working days outside the XXXX periods.

c. During the XXXX periods the maximum allowable downtime will be 8 hours.

d. System maintenance will be scheduled on a monthly basis and performed from Friday 5:00 p.m. through Monday at 8:00 am. Maintenance at other times can be performed with a minimum of two days advance notice to the affected parties.

e. This section indicates any requirements that will enhance the supportability or maintainability of the system being built, including coding standards, naming conventions, class libraries, maintenance access, maintenance utilities.

Software Selection:

Based on the Business Requirements and Objectives, a software selection process should be developed. The requirements – Inventory management, Remote location access and data consolidation, Financial information and reporting – will be the basis of developing a software selection grid / scorecard. Each other shortlisted software packages are then evaluated to see which best meets as many of the requirements as possible. A method to fulfill any missing requirements should be included (such as additional modules, custom package development, etc.)

Constraints:

Define any restraints that may be in place.

• The Integrated System will require system (server, workstation, and network) upgrades/improvement.

• The budget available for the project is xxxx….

• Need to train IT resources on new technology

• Etc.

Assumptions:

Describe any underlying assumptions that need be called out.

• Budget will remain available for the project.

Project sponsor is ….., and will remain available for the project.

• IT staff can be hired or trained to support the new system.

Exclusions:

Things that the system will not address, or will not be accomplished by this version of the system.

Impact Statement:

The proposed systems to improve Inventory and Manufacturing Management will have multiple positive impacts, these include:

• Increased materials and work-in-process inventory management will reduce manufacturing lead times, and allow faster delivery of product to customers due to fewer delays while waiting for critical manufacturing materials to be ordered and arrived.

• Faster and more complete management reporting due to consolidated financial information

• add more….

Risk Statement:

The risk of NOT implanting this system is great. Costs of manually consolidating and inputting data, and the risk of data entry errors, will remain high. Lead times for reporting and management will be long, which reduces the ability of Riordan to quickly adjust to market changes such as rapid changes in materials costs or customer requirements. ….

Original Problem Statement:

Organization Name:

Riordan Manufacturing

Locations:

All Locations

Requester:

Hugh McCauley, COO

Description of Request:

Suggest specific systems changes that improve our inventory or manufacturing processes.

Background of Request:

We would like to use computer system utilization to become more efficient.

Expected Results/Impact when completed:

Create a business requirements definition for system upgrades/improvement to be given to the IT department or information systems consultants     

Here is the abstract of the assignment:

Roirdan Manufacturing requiring systems upgrade of all locations (Georgia, Michigan, and People’s Republic of China) to corporate headquarters, San Jose, California. A presentation of the issues along with solutions for incorporating all balance sheets, income statements, and general ledgers at each facility to corporate headquarter. This will include update software for inventory.

Here is the executive summary:

Specifically, end of month reports per facility are not accessible to corporate headquarters in San Jose within a timely manner. The Georgia and Michigan facility (different operating systems) convertibility and hardcopy reports are labor intensive and costly as they must be re-entered manually taking 15 to 20 days for final reports to reach San Jose corporate office. Additionally, inventory from the external facilities is in question. The lack of continuity between facilities is costly and timely.

The following actions are presented as alternatives for these issues:

1.     VirtualBox from Sun Microsystems, Open Source Alternative:

General purpose full virtualizer;

•     Modularity: well-defined internal programming interfaces and a client/server design.

•     Virtual machine descriptions in XML: Virtual machine definitions can therefore easily be ported to other computers.

•     Guest Additions for Windows and Linux: special software installed inside Windows and Linux virtual machines to improve performance and make integration much more seamless.

•     Shared Folders: Easy data exchange between hosts and guests, declaring certain host directories as shared folders, which can then be accessed from within virtual machines.

•     USB controllers: No need to install device specific drivers on the host.

•     Remote Desktop Protocol: VirtualBox supports the standard RDP.

2.     VirtualBOS: Business Operating Systems, a proven leader in on-demand, web-based inventory and warehouse management solutions. Increased visibility and control of inventory moving through purchasing, receiving, fulfillment and shipping.

•     Real-TimeView: Of all inventory on-hand, centralized system for inventory control and accuracy across multiple locations.

•     Reduces Lead time: Alert’s you when preferred inventory levels all below optimal thresholds, purchasing and re-order as needed.

•     Web-based: No need for IT solutions.

3.     Microsoft Office Accounting Express: Easy to integrate and use with current MS server.

................
................

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

Google Online Preview   Download