Business Requirements Specification 1 
D:\Docstoc\Working\ActivePDF\Input\$ASQBusiness Requirements Specification 1.doc.doc Project name Business Requirements Specification (Detailed 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 Revision date 11 October 2005 Status Draft/Final Review/Sign Off (delete 2 of) DMS ref. No. DMS Reference Number File/Doc no. File number/document number Project name Detailed Business Requirements Specification Queensland Transport and Main Roads Version 5.9 1st June2005 Page 2 of 17 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 Detailed Business Requirements Specification approval The following officers have approved this document. Customer Name Position Signature Date Sponsors Name Position Signature Date The following officer has endorsed this document. Name Position Signature Date Project name Detailed Business Requirements Specification Queensland Transport and Main Roads Version 5.9 1st June2005 Page 3 of 17 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 ...................................................... 7 7 Scope of Project .......................................................................................................... 7 7.1 In Scope........................................................................................................................ 7 7.2 Out of Scope................................................................................................................. 7 7.3 Related Projects............................................................................................................ 7 7.4 Constraints ................................................................................................................... 8 7.5 Urgency........................................................................................................................ 8 7.6 Assumptions................................................................................................................. 8 8 Impacts ........................................................................................................................ 8 8.1 Internal ......................................................................................................................... 8 8.2 External ........................................................................................................................ 8 9 Method to date............................................................................................................ 9 10 Business Processes.................................................................................................... 10 10.1 Business Process Name (BP001…N) ........................................................................ 10 10.2 Graphical Representation (Business Process Analysis Maps) ................................... 11 11 Business Requirements ............................................................................................ 11 11.1 Business Requirement Name (1…n).......................................................................... 11 12 Other Requirements ................................................................................................ 12 Project name Detailed Business Requirements Specification Queensland Transport and Main Roads Version 5.9 1st June2005 Page 4 of 17 12.1 Performance Requirements ........................................................................................ 12 12.1.1 Performance Requirement Name (1…n) ............................................................................... 12 12.2 Interface Requirements .............................................................................................. 12 12.2.1 Interface Requirement Name (1…n)...................................................................................... 12 12.3 Operational/Technical Requirements......................................................................... 12 12.3.1 Operational Requirement Name (1…n)................................................................................. 12 12.4 Resource Requirements.............................................................................................. 13 12.4.1 Resource Requirement Name (1…n)..................................................................................... 13 12.5 Acceptance Testing Requirements............................................................................. 13 12.5.1 Acceptance Testing Requirement Name (1…n).................................................................... 13 12.6 Documentation Requirements.................................................................................... 13 12.6.1 Documentation Requirement Name (1…n) ........................................................................... 13 12.7 Security Requirements ............................................................................................... 14 12.7.1 Security Requirement Name (1…n) ...................................................................................... 14 12.8 Portability Requirements............................................................................................ 14 12.8.1 Portability Requirement Name (1…n)................................................................................... 14 12.9 Availability Requirements ......................................................................................... 14 12.9.1 Availability Requirement Name (1…n)................................................................................. 14 12.10 Criticality Requirements ............................................................................................ 15 12.10.1 Criticality Requirement Name (1…n).................................................................................... 15 12.11 Legal Requirements ................................................................................................... 15 12.11.1 Legal Requirement Name (1…n)........................................................................................... 15 13 Continuity Planning................................................................................................. 15 14 Project Performance Measurement ....................................................................... 15 15 Project Benefits Realisation .................................................................................... 16 16 Policies, Processes and Forms ................................................................................. 16 17 Communications....................................................................................................... 16 18 Issues Outstanding ................................................................................................... 16 Project name Detailed Business Requirements Specification Queensland Transport and Main Roads Version 5.9 1st June2005 Page 5 of 17 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 Development phase of the project, a Detailed Business Requirements Specification (Detailed BRS) is prepared utilising the content from the High-Level BRS following the approval of the Business Case. and preceding the preparation of the Project Plan. The Detailed BRS focuses on a lower level of detail pertinent to the selected option as outlined in the Options Analysis and Business Case. The details establish a more accurate specification of the intended system,being the final delivered project/s to satisfy the business's needs. 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 and must maintain separate version control. Information from the High-Level BRS populates the Detailed BRS document. The Detailed BRS document must reflect a version numbering of 0.1 (draft). 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 Detailed Business Requirements Specification Queensland Transport and Main Roads Version 5.9 1st June2005 Page 6 of 17 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. 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 Project name Detailed Business Requirements Specification Queensland Transport and Main Roads Version 5.9 1st June2005 Page 7 of 17 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 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 Project name Detailed Business Requirements Specification Queensland Transport and Main Roads Version 5.9 1st June2005 Page 8 of 17 and managed. To delete this guidance text box, double click mouse in the left margin then press delete. Type here 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. To delete this guidance text box, double click mouse in the left margin then press delete. 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 Project name Detailed Business Requirements Specification Queensland Transport and Main Roads Version 5.9 1st June2005 Page 9 of 17 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 here Project name Detailed Business Requirements Specification Queensland Transport and Main Roads Version 5.9 1st June2005 Page 10 of 17 10 Business Processes If this project has a system component, then the Business Process Modelling Notations (BPMN) process is to be undertaken. Alternatively, use this section to describe the processes associated with your business requirements. As a guide, 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. 10.1 Business Process Name (BP001…N) Process n: For each new business process, copy and paste this section. Description From Business Requirement
Event Sequence Preconditions Typical Course of Events Step Action Step 1…n Alternate Course of Events <(Optional) Create an alternative to describe anything that may go wrong or may be different in the above process.> Step Action Alternate 'X' at Step 'N' Step A1… An Alternate 'X' at Step 'N' Step A1… An Project name Detailed Business Requirements Specification Queensland Transport and Main Roads Version 5.9 1st June2005 Page 11 of 17 10.2 Graphical Representation (Business Process Analysis Maps) Discuss with the System Analyst the use of a diagramming technique to represent this scenario. 11 Business Requirements The information is populated from the High-Level Business Requirements Specification and elaborated to accommodate in detail the business requirements. For each business function describe the business process in plain English. Repeat for each business function (1… N). 11.1 Business Requirement Name (1…n) Business Requirement n: For each new requirement, copy and paste these headings. Reference <> that is, RQ001...RQXXX 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 Detailed Business Requirements Specification Queensland Transport and Main Roads Version 5.9 1st June2005 Page 12 of 17 12 Other Requirements Identify any other requirements for the system. It is mandatory to complete the performance requirements section. Otherwise all sections are optional. 12.1 Performance Requirements 12.1.1 Performance Requirement Name (1…n) For each Performance Requirement copy and paste this section. A performance requirement may refer to the response time expected at a certain screen event. Example Reference: OR0001 Description: The search customer functionality must provide a response time of less than five seconds. Reference <> that is, OR001..ORXXX Description 12.2 Interface Requirements 12.2.1 Interface Requirement Name (1…n) For each Interface requirement copy and paste this section. An interface requirement will describe either internal or external interfaces requirements that are non functional. A particular function may require that the interface must be designed using a web interface or PDA. Alternately, an interface to an external party may require that a certain standard of security or encryption is used. Example Reference: OR002 Description: All screen interface must use support the use of Internet Explorer 6.1 or Netscape 7.0. Must conform to the accessibility standards as specified by Queensland government. Reference <> that is, OR001..ORXXX Description 12.3 Operational/Technical Requirements 12.3.1 Operational Requirement Name (1…n) For each Operational Requirement copy and paste this section. An Operation Requirement will specify requirements relating to the capabilities and characteristics required for the proposed system. Example Reference: OR003 Description: -The system downtime must not exceed 20 minutes within any 24 hour period. Project name Detailed Business Requirements Specification Queensland Transport and Main Roads Version 5.9 1st June2005 Page 13 of 17 Reference <> that is, OR001..ORXXX Description 12.4 Resource Requirements 12.4.1 Resource Requirement Name (1…n) For each Resource requirement copy and paste this section. A Resource Requirement specifies what hardware, software or technical requirements are required. Example Reference: OR004 Description: -The system must support transmission of messages to/from external systems using XML. Reference <> that is, OR001..ORXXX Description 12.5 Acceptance Testing Requirements 12.5.1 Acceptance Testing Requirement Name (1…n) For each Acceptance testing requirement copy and paste this section. The Acceptance Testing Requirements specify what provisions are to be made by the business to support the acceptance of the delivered system, including personnel and schedules. Example Reference: OR005 Description: -System Testing is to be undertaken on the customer site during the period of July 2004. Reference <> that is, OR001..ORXXX Description 12.6 Documentation Requirements 12.6.1 Documentation Requirement Name (1…n) For each Documentation requirement copy and paste this section. The Documentation Requirement specifies the deliverables that are expected by the customer . Example Reference: OR006 Description: ISB will provide at least a Functional requirements Specification which will be signed off by the business. A Logical Design and high level estimate of the costs for construction. Reference <> that is, OR001..ORXXX Description Project name Detailed Business Requirements Specification Queensland Transport and Main Roads Version 5.9 1st June2005 Page 14 of 17 12.7 Security Requirements 12.7.1 Security Requirement Name (1…n) For each Security requirement copy and paste this section The Security Requirement will specify policies and procedures which must be used in designated functional area of the system to be implemented.. Example Reference: OR007 Description: Credit Card information is not be stored within the system in accordance with Queensland government legislation. Reference <> that is, OR001..ORXXX Description 12.8 Portability Requirements 12.8.1 Portability Requirement Name (1…n) For each Portability requirement copy and paste this section. The Portability Requirement will identify which system architectures the system is to support. Example Reference: OR007 Description: The system must be supported on Windows XP and Linux desktops. Reference <> that is, OR001..ORXXX Description 12.9 Availability Requirements 12.9.1 Availability Requirement Name (1…n) For each availability requirement copy and paste this section. The Availability requirement specifies that the system will have a designed up-time of a specified period. Example Reference: OR008 Description: The system will be available for operation on a 24x7 basis, with provision for critical failure and recovery within 1 hour of any downtime. Reference <> that is, OR001..ORXXX Description Project name Detailed Business Requirements Specification Queensland Transport and Main Roads Version 5.9 1st June2005 Page 15 of 17 12.10 Criticality Requirements 12.10.1 Criticality Requirement Name (1…n) For each criticality requirement copy and paste this section. The Criticality requirement specifies what aspects of the system are of high importance and are essential to the effective operations of the customer. Example Reference: OR009 Description: The customer billing functionality is of critical importance and must provide failsafe backup mechanisms to ensure 99% accuracy and turnaround in invoicing and recovery of debt. Reference <> that is, OR001..ORXXX Description 12.11 Legal Requirements 12.11.1 Legal Requirement Name (1…n) For each legal requirement copy and paste this section. The Legal Requirement specifies legislative issues that impact the project. Example Reference: OR010 Description: The system must be operational by June 30th 2004 to support the announcement in parliament of the availability for the new services. Reference <> that is, OR001..ORXXX Description 13 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). Type here 14 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 Project name Detailed Business Requirements Specification Queensland Transport and Main Roads Version 5.9 1st June2005 Page 16 of 17 Success Criteria Responsibility 15 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. 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 16 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. -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 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 Issues Outstanding List any issues affecting requirements that have not yet been resolved. Type here -----ooooo-----Project name Detailed Business Requirements Specification Queensland Transport and Main Roads Version 5.9 1st June2005 Page 17 of 17 Appendix A – Process Maps Type here