1. Neil Schiller Business Analysis Work Profile

2. Project Engagement

3. Scoping

4. Business Requirements Definition Office Admin Y A mechanism is required which enables dedicated users to maintain a set of dummy reference data for append to actual datasets in order to support existing operational processes BR3 Account Management Y Performance monitoring measures are required new services to enable pro-active management of service failures BR2 N A mechanism is required which produces, on a weekly basis, 3 relevant reference datasets for distinct service level transactions, published in the same format as currently utilised by specific customers BR1 Bus. Unit Impacted Process Change? Yew Requirement Definition Requirement Ref:

5. Functional Requirements Definition

7. Business Rule Definition Business Rules Catalogue: with Project Cross-Reference:

8. Non Functional Requirements Downtime of the service should not result in any loss of data – ie. data recovery and resubmission routines must be in place DNFR1.1 Non-availability of the service (and associated functions) should not be greater than 1 hour DNFR1.0 Non Functional Requirement Continuity and Disaster Recovery Service downtime should be restricted to an absolute minimum – ie. availability should adhere to an excess of 99% ANFR1.0 Non Functional Requirement Reliability & Availability The solution should be available 24 hours a day, 7 days a week and should fall into a support model which maintains this CNFR1.2 The solution should support Peak transactional timings between 01:00 and 03:00 where up to 90% of the transaction volume could be processed CNFR1.1 The solution should support anticipated daily volumes of 100,000 records CNFR1.0 Non Functional Requirement Capacity & Scalability The Solution should support key functions and departments as listed: Team 1 Team 2 Team 3 UNFR1.1 All data maintenance functions should support volumes of 10 concurrent users UNFR1.0 Non Functional Requirement User Base

9. Performance Test Requirements – Process Timeline

12. Requirements Governance

13. Requirements Traceability

15. Enterprise Business Modelling System Box Business Rules Interfaces N/F Process Step Hyperlink - Component Specs Model Navigation Additional Business Rules

16. Enterprise Business Modelling INT-01 Interface Descriptions Hyperlinks to Component Specs Hyperlinks to Interface Specs Business Rule Descriptions