Docstoc

business requirements template

Document Sample
business requirements template Powered By Docstoc
					         [INSERT PROJECT NAME]

B U S I N E S S R E Q U I R EME N TS T EM P L A T E
(BUSINESS AND USER REQUIREMENTS)




          EXECUTIVE SPONSOR – [INSERT NAME]
            BUSINESS OWNER - [INSERT NAME]
           PROJECT MANAGER – [INSERT NAME]
    ORIGINAL PLAN DATE: [INSERT DATE, SPELLED OUT]
       REVISION DATE: [INSERT DATE, SPELLED OUT]

              Revision: [Insert Number]
  Business Requirements

ABOUT THIS DOCUMENT
  This document is to be used to articulate the business requirements for the project. In the State of
  New Mexico project methodology this involves the stated business objectives laid out in both the
  Project Charter and the Project Management Plan. These business objectives would be the
  starting point for the business requirements.
  This document is meant to be built using the requirements collection template or form presented
  in the Department of Information Technology REQUIREMENTS COLLECTION Template.
  Each requirement is to be filled out in that form and then copied into this document.
  This Business Requirements Document is used to capture the requirements of what the project
  must do, and the properties that the system(s) must have. This document has two key sections:


            Business Requirements – these describe the high-level statement of need for the
             project. These requirements are captured base lined during the Plan phase of the
             project.


            User Requirements – these describe the business users’ requirements in terms of
             functionality, usability, performance, security, legal compliance and globalization.
             These requirements are captured during the Define phase of the project, and are used
             to develop the system requirements.]




                                  Page 2 of 14
  Business Requirements



REVISION HISTORY
   REVISION NUMBER        DATE                  COMMENT
   1.0                    August 14, 2007       Original DoIT PMO Document




                                 Page 3 of 14
Business Requirements


                                                                Table of Contents


ABOUT THIS DOCUMENT ....................................................................................................................................... 2
REVISION HISTORY................................................................................................................................................. 3
INTRODUCTION ..................................................................................................................................................... 6
    USER PROBLEM/ PROJECT BACKGROUND ...........................................................................................................................6
    GOALS OF THE PROJECT ..................................................................................................................................................6
    SYSTEM SCOPE ..............................................................................................................................................................6
    CLIENT, CUSTOMER AND OTHER STAKEHOLDERS ..................................................................................................................6
    USERS OF THE PRODUCT..................................................................................................................................................6
ASSUMPTIONS AND OTHER RELEVANT FACTS ....................................................................................................... 7
BUSINESS REQUIREMENTS ..................................................................................................................................... 7
USER REQUIREMENTS ............................................................................................................................................ 8
    FUNCTIONALITY REQUIREMENTS .......................................................................................................................................8
       Processing Requirements .....................................................................................................................................8
       Information Requirements ...................................................................................................................................8
    USABILITY REQUIREMENTS...............................................................................................................................................9
       Ease-of-use Requirements ....................................................................................................................................9
       Documentation Requirements .............................................................................................................................9
       Safety Requirements ............................................................................................................................................9
    PERFORMANCE REQUIREMENTS ......................................................................................................................................10
       Availability Requirements ..................................................................................................................................10
       Responsiveness Requirements ...........................................................................................................................10
       Reliability Requirements ....................................................................................................................................10
       Capacity Requirements ......................................................................................................................................10
       Scalability Requirements ....................................................................................................................................10
       Disaster Recovery & Business Continuity Requirements ....................................................................................10
    SECURITY REQUIREMENTS .............................................................................................................................................10
       User Security Requirements ...............................................................................................................................10
       Data Security Requirements ...............................................................................................................................10
    LEGAL COMPLIANCE REQUIREMENTS ...............................................................................................................................11
       Notification Requirements .................................................................................................................................11
       Privacy Requirements .........................................................................................................................................11
       Funding Requirements or Appropriation Stipulations ........................................................................................11
REQUIREMENT CONSTRAINTS & DEPENDENCIES ................................................................................................. 12
    DESIGN CONSTRAINT ....................................................................................................................................................12
    PROJECT CONSTRAINT...................................................................................................................................................12




                                                         Page 4 of 14
Business Requirements

REFERENCE MATERIAL ......................................................................................................................................... 13
ACRONYMS AND GLOSSARY ................................................................................................................................ 14




                                                    Page 5 of 14
  Business Requirements

INTRODUCTION

   USER PROBLEM/ PROJECT BACKGROUND
     Give a brief description of the business problem being addressed, and the background to the
     project. This includes:
                A description of the work the user is currently doing and why it is not as good as
                 it could be.
                A clear statement of the business opportunity
     This can be copied from the project charter or agency documents used to secure funding.

   GOALS OF THE PROJECT
     Provide a short description of what the product/system needs to do, or how it will contribute
     to the overall goals of the project. Having a short sharp goal will make the project’s intent
     clear to stakeholders and will aid in achieving consensus. The goal must provide direct
     benefit, e.g., value in the marketplace, reduced operations cost, and/or increased value or
     service to customers.

     SYSTEM SCOPE
     Give a brief description of scope of work for the project, which defines the boundaries of the
     work and how it fits in the environment.

   CLIENT, CUSTOMER AND OTHER STAKEHOLDERS
     List the following:
                The Client – The person/organization who pays for the product development
                The Customer – The person/organization(s) who will use the product, or who will
                 benefit by the existence of the product.
                Other Stakeholders – The people/organizations that have a vested interest in the
                 product



   USERS OF THE PRODUCT
     Detail all of the roles of people who will interact directly with the product. This information
     may be available in the Organization Impact Analysis document.




                                  Page 6 of 14
  Business Requirements



ASSUMPTIONS AND OTHER RELEVANT FACTS
     Include any assumptions that were made with regards to the analysis/decisions of the project,
     its systems, and its requirements. Also include any other relevant facts regarding external
     factors that have an effect on the system, but are not covered by the other sections.
BUSINESS REQUIREMENTS
     Business requirements simply stated are a high level description of what the system must do.
     They are based on the process vision and architecture vision of the to-be design. Business
     Requirements are listed as major features that are needed to satisfy the stated goals,
     objectives, and strategies for the project. The Business Requirements provide the guiding
     direction for the project, and become the foundation for the User Requirements.
     [Note: Requirements regarding functionality needed to satisfy specific tasks, operational
     needs, user groups, etc. are captured later in the User Requirements.]
     Insert the completed requirements collection template forms here: Note the form below
     leaves off fields used in lower level requirements.
   Requirement ID <Unique id
                  #>
   Status              Ne    <x>      Agreed-to   <x>        Baselined       <x>       Rejected    <x>
                       w
   Description         <Enter concise description of requirement>


   Rationale           <Provide a brief rationale, and or business value for the requirement.>
   Source              <Name of Reqmnt.               Source                <filename>
                       Provider>                      Document
   Acceptance/Fit      <Provide a target that makes it possible to test if requirement was satisfied>
   Criteria
   Dependencies        <List other requirement. Id#s that this requirement is dependent on>
   Priority            Essential    <x>    Conditional   <x> Optional        <x>
   Change History      <List history of changes to this requirement>




                                   Page 7 of 14
Business Requirements


USER REQUIREMENTS
   The User Requirements provide detail to the Business Requirements. These requirements
   describe the functionality needed to satisfy specific tasks, operational needs, user groups, etc.
   They cover the requirements that the user(s) need to perform the to-be design. They include
   functional requirements (describe what the system must do (Functional/Behavioral
   Requirements), the data manipulated by its functions (Data Requirements), the interfaces
   required (External Interface Requirements), and the architecture that it is built on
   (Architecture Requirements)) and non-functional requirements.


   To ensure that each requirement has the necessary amount of information, use the
   Requirements Information Collection Template to capture the required data for each
   requirement. This template should be used for all types of requirements, and then the data
   from that template placed in this specification document under the appropriate requirement
   type section.


   Note: To ensure that the user requirements are valid and support the scope and Business
   Requirements, all User Requirements should call out the Business Requirement in the
   parent requirement field of gathering template.


   FUNCTIONALITY REQUIREMENTS
      PROCESSING REQUIREMENTS
      From the perspective of the business user, document the business processes that are to be
      implemented by the system. This section should describe what the system is to do,
      without specifying how the solution is to be implemented. For example, prototypes and
      screen mock-ups should not be included. Detailed user interface requirements are
      captured in the System Requirements.


      INFORMATION REQUIREMENTS
      From the perspective of the business user, document the information requirements of the
      solution. Include any known requirements to retrieve information from, or provide
      information to, other systems. This document should only address the type of
      information required, and not, for example, reference specific data tables. Detailed data
      requirements are captured in the System Requirements. The following table may be used
      to provide definition for each reporting requirement.




                                Page 8 of 14
Business Requirements




       Report        Report         Description                 Stakeholde   Frequency
       Type          Name                                       r Audience
       [Examples:                   [In a couple of sentences                [Example:
       Financial,                   describe the information                 Daily, weekly,
                                    that the stakeholder                     monthly, etc.]
       Operational                  audience would like to
       ,                            obtain from this report]
       Executive,
       etc.]


USABILITY REQUIREMENTS

      EASE-OF-USE REQUIREMENTS
      From the perspective of the business user, document the requirements pertaining to the
      ease with which the user must be able to interact with the system. Examples include the
      accessibility of information, high-level user interface guidelines, and support for various
      levels of user expertise (e.g., novice vs. power user).


      DOCUMENTATION REQUIREMENTS
      From the perspective of the business user, document the kinds of user documentation that
      will need to be produced. This should include not only printed user manuals, but also any
      requirements for on-line help, tutorials, and installation instructions.


      SAFETY REQUIREMENTS
      From the perspective of the business user, document any requirements pertaining to
      possible loss, damage, or harm that could result from the use of the system. Define any
      safeguards or actions that must be taken, as well as actions that must be prevented. Refer
      to any external policies or regulations that govern the system’s design or use. Define any
      safety certifications that must be satisfied.




                               Page 9 of 14
Business Requirements

   PERFORMANCE REQUIREMENTS
      AVAILABILITY REQUIREMENTS
      From the perspective of the business user, document the expected availability of the
      system, such as hours of operation and expected uptime requirements.
      RESPONSIVENESS REQUIREMENTS
      From the perspective of the business user, document the expected responsiveness of the
      system, such as online response times and report deadlines.
      RELIABILITY REQUIREMENTS
      From the perspective of the business user, document the expected reliability of the
      system, such as acceptable time the system could be unavailable before the business
      functions supported would be impacted. This is especially important in planning business
      continuity or levels of disaster recovery.
      CAPACITY REQUIREMENTS
      From the perspective of the business user, document the expected and maximum volumes
      the system must be able to accommodate. Examples include number of concurrent users
      and transactions per time period. If there are different types of users, provide usage
      volume for each user type.
      SCALABILITY REQUIREMENTS
      From the perspective of the business user, document the expected increase in the usage of
      the system over time.
      DISASTER RECOVERY & BUSINESS CONTINUITY REQUIREMENTS
      From the perspective of the business user, document the requirements for operation of the
      system in the event of a disaster. This can be obtained from the Business Continuity
      Plan.
   SECURITY REQUIREMENTS
      USER SECURITY REQUIREMENTS
      From the perspective of the business user, describe the user security requirements of the
      system. Include known user roles and their associated security authorizations. Refer to
      any external policies or regulations containing security issues that affect the system.
      Define any security or privacy certifications that must be satisfied.
      DATA SECURITY REQUIREMENTS
      From the perspective of the business user, describe any requirements pertaining to
      accessing, storing or transmitting confidential and/or sensitive information.




                              Page 10 of 14
Business Requirements




   LEGAL COMPLIANCE REQUIREMENTS
      NOTIFICATION REQUIREMENTS
      Document any necessary legal disclaimers, warranties, copyright notices, patent notice,
      trademark or other compliance requirements for the system
      PRIVACY REQUIREMENTS
      Document requirements relating to the storage and use of personal data collected from
      external users
      FUNDING REQUIREMENTS OR APPROPRIATION STIPULATIONS
      Document requirements tied into Federal funding or Legislative Appropriations language.




                              Page 11 of 14
Business Requirements


REQUIREMENT CONSTRAINTS & DEPENDENCIES
   Constraints and dependencies often impact and/or provide direction on how the system must
   ultimately be developed. Dependencies are a form of constraint in that they can influence the
   timing, content, risk, etc. for a project. Business Rules can also be a form of constraint and
   need to be comprehended and captured here.


   Use the following table to detail and uniquely identify any conditions that restrict the
   requirements to specifying a system that fits within the constraint for the project. There are
   two types of constraints.
       Design Constraints
          o These are pre-existing design decisions that mandate how the final system must
              look, or the technology that it must use.
       Project Constraints
          o These are constraints that cover things like budget, schedule, deadlines, etc.


   DESIGN CONSTRAINT
           ID       Constraint
           C.1.1
           C.1.2

   PROJECT CONSTRAINT
           ID      Constraint
           C.2.
           1




                                Page 12 of 14
Business Requirements


REFERENCE MATERIAL
   Use this table to consolidate all reference documents, their filenames, and their location.


    Description              Filename and Version            Location




                                Page 13 of 14
Business Requirements


ACRONYMS AND GLOSSARY
   Include definitions for any unique symbols or notations that are used in the document, which
   may cause confusion with the intended message, or may result in multiple interpretations of
   some key terms. Define all the terms necessary to properly interpret the specification
   document, including acronyms and abbreviations. Include definitions for terms that have
   multiple uses, or unique agency uses.




                              Page 14 of 14

				
DOCUMENT INFO
Shared By:
Tags:
Stats:
views:3641
posted:1/6/2008
language:English
pages:14
ocak ocak
About