Business Requirements Specification 
D:\Docstoc\Working\ActivePDF\Input\$ASQBusiness Requirements Specification.doc.doc Project name Business Requirements Specification (High Level BRS) Action statement Date Name Position Action required (Review/Endorse/Approve) Due date Prepared by Name Title Job title Branch/District Branch/District Division/Region Division/Region Location Floor, street, city Version no. 0.1 Version date 18 July 2006 Status Draft/Final review/Sign off (delete 2 of) DMS ref. no. DMS reference number File/Doc no. File number/document number Project name High-Level BRS Queensland Transport and Main Roads Version 18 July 2006 Page 2 of 15 Document control sheet Contact for enquiries and proposed changes If you have any questions regarding this document or if you have a suggestion for improvements, please contact: Project Manager Insert Project Manager's name here Phone Insert phone number here Version history Version no. Date Changed by Nature of amendment 09/07/2002 Initial draft. High-Level Business Requirements Specification approval The following officers have approved this document. Customer Name Position Signature Date Sponsor Name Position Signature Date The following officer has endorsed this document. Name Position Signature Date Project name High-Level BRS Queensland Transport and Main Roads Version 18 July 2006 Page 3 of 15 Contents 1 Introduction................................................................................................................ 5 1.1 Purpose of this Document ............................................................................................ 5 1.2 References .................................................................................................................... 5 1.3 Definitions.................................................................................................................... 5 2 Project Customer, Sponsor and Project Manager.................................................. 6 2.1 Project Customer.......................................................................................................... 6 2.2 Project Sponsor ............................................................................................................ 6 2.3 Project Manager ........................................................................................................... 6 3 Stakeholders ............................................................................................................... 6 4 Background................................................................................................................. 7 5 Current Situation ....................................................................................................... 7 6 Purpose/Objectives of the Project ............................................................................ 7 6.1 Purpose/Objectives....................................................................................................... 7 6.2 Links with the Department’s Strategic Objectives ...................................................... 8 7 Scope of Project .......................................................................................................... 8 7.1 In Scope........................................................................................................................ 8 7.2 Out of Scope................................................................................................................. 8 7.3 Related Projects............................................................................................................ 8 7.4 Constraints ................................................................................................................... 9 7.5 Urgency........................................................................................................................ 9 7.6 Assumptions................................................................................................................. 9 8 Impacts ........................................................................................................................ 9 8.1 Internal ......................................................................................................................... 9 8.2 External ...................................................................................................................... 10 9 Method to date.......................................................................................................... 10 10 Business Process Analysis........................................................................................ 11 11 Business Requirements ............................................................................................ 12 12 Continuity Planning................................................................................................. 13 13 Project Performance Measurement ....................................................................... 13 14 Project Benefits Realisation .................................................................................... 13 Project name High-Level BRS Queensland Transport and Main Roads Version 18 July 2006 Page 4 of 15 15 Policies, Processes and Forms ................................................................................. 13 16 Security ..................................................................................................................... 14 17 Communications....................................................................................................... 14 18 Outstanding Issues ................................................................................................... 14 Appendix A – Process Map/s................................................................................................. 15 Project name High-Level BRS Queensland Transport and Main Roads Version 18 July 2006 Page 5 of 15 1 Introduction Text in this document which has been copied forward from the previous document has been shown bold and italics “words copied from previous documents”. 1.1 Purpose of this Document To record and obtain agreement on the new or changed business requirements resulting from the implementation of the project. Creation of the Business Requirements Specification is one component of the department’s standard approach to project management. During the Concept phase of the project, a High-Level Business Requirements Specification (High-Level BRS) is to follow the approved Options Analysis, and is required for submission with the Business Case. The High-Level BRS content is at a higher level of detail than the Detailed BRS, which is prepared at a later stage of the project (within the Development Phase). The High-Level BRS describes what functions are required by the Business but not necessarily how. The Detailed BRS addresses not only the “what” but the “how” of the project’s implementation. The two Business Requirements Specification documents should be viewed as distinctly separate documents. To delete this guidance text box, double click mouse in the left margin then press delete. 1.2 References This item lists any documents to which this document refers and could include reports on any previous investigations carried out. Include all previous documents prepared as part of this project. To delete this guidance text box, double click mouse in the left margin then press delete. Type here 1.3 Definitions In the table below contains the working definitions for any term which this document’s audience may not understand, including specific terms, abbreviations and acronyms. This table will be expanded throughout the life of the project. To delete this guidance text box, double click mouse in the left margin then press delete. Business Terms, Abbreviations and Acronyms Detailed Description of its Meaning Project name High-Level BRS Queensland Transport and Main Roads Version 18 July 2006 Page 6 of 15 Business Terms, Abbreviations and Acronyms Detailed Description of its Meaning 2 Project Customer, Sponsor and Project Manager 2.1 Project Customer Enter the name of the Project Customer. To delete this guidance text box, double click mouse in the left margin then press delete. Insert name is the Project Customer who carries responsibility for the end result of the project. 2.2 Project Sponsor Enter the name of the Project Sponsor. To delete this guidance text box, double click mouse in the left margin then press delete. Insert name is the Project Sponsor who carries responsibility for the end result of the project. 2.3 Project Manager Enter the name of the Project Manager. To delete this guidance text box, double click mouse in the left margin then press delete. Insert name is the Project Manager who is responsible for the preparation of this document. 3 Stakeholders This section should illustrate the consultation undertaken with stakeholders in developing this document and the key findings of that consultation. List all stakeholders with an interest in this document including internal stakeholders (from regions/districts/divisions/branches with the department) and external stakeholders. Stakeholders may be listed in tabular form (as below) if considered appropriate. Project name High-Level BRS Queensland Transport and Main Roads Version 18 July 2006 Page 7 of 15 Stakeholders may be categorised (internal, external and so on) if appropriate. To delete this guidance text box, double click mouse in the left margin then press delete. Stakeholder area Stakeholder representative Responsibility Interest/context 4 Background Provide a brief history to bring the reader up to date on the subject matter and associated business issues. This section should describe the history of the project. It should include details of: -Who initiated the project and how it was initiated -Describe the products and/or services -Describe any other initiatives carried out previously to address related issues. To delete this guidance text box, double click mouse in the left margin then press delete. Type here 5 Current Situation Describe here the current situation and the problems, needs and/or opportunities along with their associated impacts on internal and external stakeholders. To delete this guidance text box, double click mouse in the left margin then press delete. Type here 6 Purpose/Objectives of the Project 6.1 Purpose/Objectives A statement of what the project is expected to achieve including potential benefits based upon the current state of knowledge and understanding. To delete this guidance text box, double click mouse in the left margin then press delete. Type here Project name High-Level BRS Queensland Transport and Main Roads Version 18 July 2006 Page 8 of 15 6.2 Links with the Department’s Strategic Objectives A statement of how the project links to the department’s Strategic Plan and objectives. If the project has not originated from the Strategic Plan then the need/justification for the project should be stated, together with some demonstration that this project is the right one to satisfy the need or to solve the problem. To delete this guidance text box, double click mouse in the left margin then press delete. Type here 7 Scope of Project 7.1 In Scope This defines the project boundaries to facilitate effective management of deliverables on time and to agreed/approved cost. The scope outlined in any previous document should be confirmed here or updated as necessary. List all items that are included in the scope of this project. To delete this guidance text box, double click mouse in the left margin then press delete. Type here 7.2 Out of Scope List identified items that will not be delivered as part of this project. This is most important as it specifies items which will not be undertaken as part of this project. This assists in managing/avoiding scope creep. The importance of individual out of scope items should be mentioned. Such items may pose significant risks to the project if they are not done at all by others. This may create risks for the project which need to be recognised and managed. To delete this guidance text box, double click mouse in the left margin then press delete. Type here 7.3 Related Projects List any related projects or proposals affecting this project (whether past, current or planned) and their relationship to this project. The impact of these on your project should be described. Such projects may pose significant risks to the project if they are not done at all by others or not completed in time. This may create risks for the project which need to be recognised and managed. To delete this guidance text box, double click mouse in the left margin then press delete. Type here Project name High-Level BRS Queensland Transport and Main Roads Version 18 July 2006 Page 9 of 15 7.4 Constraints Restrictions which will limit the way the objective is to be achieved (describe anything that might impact on the successful development and/or implementation of the project). This may include restrictions on budget /funding, political issues, limited resources to work on the project, timing constraints or constraints on the implementation of the outcomes of the project. To delete this guidance text box, double click mouse in the left margin then press delete. Type here 7.5 Urgency Identify the urgency of the project stating reasons. To delete this guidance text box, double click mouse in the left margin then press delete. Type here 7.6 Assumptions List all assumptions made in producing this document. To delete this guidance text box, double click mouse in the left margin then press delete. Type here 8 Impacts This can be completed in narrative or table format. Identify areas of potential impact, the nature of impact and who will be impacted (internal and external). Include both the impacts envisaged during the life of the project (that is, costs, disruptions, temporary arrangements, and so on) and ongoing impacts resulting from the project’s product/deliverables. To delete this guidance text box, double click mouse in the left margin then press delete. Type here 8.1 Internal This item describes when, where and how the project will impact on areas within the department and should include an outline of both positive and negative influences. Consider here the culture change and change management aspects that will be needed to introduce the proposed changes the project will bring. Impacts on staff and likely staff attitudes need to be considered as well as the impacts on the business. To delete this guidance text box, double click mouse in the left margin then press delete. Project name High-Level BRS Queensland Transport and Main Roads Version 18 July 2006 Page 10 of 15 Area within the department Nature of impact 8.2 External This item describes the impact that the project will have outside the department and includes both positive and negative impacts on external stakeholders. To delete this guidance text box, double click mouse in the left margin then press delete. Area external to the department Nature of impact 9 Method to date In this section describe the steps taken in developing this document. Describe any investigations carried out, research methodology used and consultation carried out to date. To delete this guidance text box, double click mouse in the left margin then press delete. Type hereProject name High-Level BRS Queensland Transport and Main Roads Version 18 July 2006 Page 11 of 15 10 Business Process Analysis If this project has a system component, then the Business Process Modelling Notation (BPMN) process is to be undertaken. Alternatively, describe in steps the business processes and procedures associated with your business requirements that will be undertaken to complete each function. Process mapping of end-to-end business processes supporting the functional change requirements should be developed or refined if pre-existing. Each business requirement may need a separate process description to describe it adequately. However, sometimes a single process description can be used to describe more than one business requirement. Sometimes you may also find that more than one process description is needed to fully describe how a business requirement works processes are outlined Refer to the process map/s for the current process (as is) from the Business Process Analysis, updated as required. Detail any changes/updates to the Business Process which have occurred since completion of the Business Process Analysis. Add the process map/s for the future process (to be) from the Business Process Analysis and update as required. To delete this guidance text box, double click mouse in the left margin then press delete. Refer to Appendix A for the current process maps from the BPA document. Project name High-Level BRS Queensland Transport and Main Roads Version 18 July 2006 Page 12 of 15 11 Business Requirements Broadly outline the current business processes (as is) and the future requirements (to be)by describing the business functions, purpose of each function, consideration to audit, legislation, governance, (etc) and interfaces (both technical and business). -The high level description of the identified business functions that support products and services (for example, driver licence renewals, cancellations, testing, and so on). Include details of who are the users and any constraints applicable to those users. -Provide a brief description of what each function is set out to achieve (for example, capture current information for driver’s licence purposes). To delete this guidance text box, double click mouse in the left margin then press delete. Reference <
> that is, RQ001...RQXX X Benefit Status To Business Process Purpose Summary of Current Process (As Is) Summary of Proposed Process (To Be) Business Rules Cross reference to existing document(s) Project name High-Level BRS Queensland Transport and Main Roads Version 18 July 2006 Page 13 of 15 12 Continuity Planning Outline the alternative business processes that will support business continuity when the main business processes and/or systems are unavailable (for example, if the business process is TRAILS-dependent, how will the business continue to operate should TRAILS become unavailable for a significant period of time other than routine downtime and so on). To delete this guidance text box, double click mouse in the left margin then press delete. Type here 13 Project Performance Measurement Detail how the performance of the project will be measured during the project’s life. An example table format is shown below. To delete this guidance text box, double click mouse in the left margin then press delete. Success Criteria Responsibility 14 Project Benefits Realisation Detail how the benefits of the project will be measured. This may or may not be during the life of the project. Consider business outcomes such as triple bottom line here. An example table format is shown below. To delete this guidance text box, double click mouse in the left margin then press delete. Success Criteria Responsibility Measurement Method KPI Target 15 Policies, Processes and Forms Identify all policies, processes and forms requiring changes/amendments as well as new forms to be developed or old forms that will become obsolete as a result of the Project name High-Level BRS Queensland Transport and Main Roads Version 18 July 2006 Page 14 of 15 project. -Policies -Processes -Forms -Legislation (identify any potential legislative changes or reviews that may be required as a result of proposed changes coming from the project). To delete this guidance text box, double click mouse in the left margin then press delete. Type here 16 Security Identify security issues (including user access) -physical -systems -authority levels -assets (for example, special storage). To delete this guidance text box, double click mouse in the left margin then press delete. Type here 17 Communications Where applicable, outline any additional communications requirements identified in the business requirements phase of the project that are not already included in the Communications Plan. Specify what needs to be communicated and the target for the communication. To delete this guidance text box, double click mouse in the left margin then press delete. Type here 18 Outstanding Issues List here any requirements that have been broadly identified but are, as yet, unresolved at the appropriate level of detail. To delete this guidance text box, double click mouse in the left margin then press delete. Type here When all information has been put into this document and the guidance text boxes have been deleted, it will be necessary to reformat the document taking out any blank lines. Once this is done, right click mouse in the table of content, click Update Fields, Update entire table, then click OK. This will update the table of contents to show the new page numbers. To delete this guidance text box, double click mouse in the left margin then press delete. -----ooooo-----Project name High-Level BRS Queensland Transport and Main Roads Version 18 July 2006 Page 15 of 15 Appendix A – Process Map/s Type here