Project Request / Business Requirements

Prepared by: <First name, Surname>Thinking problem

management!

Name / Description <Project name>

<Short description of project>

Sponsor <Job description, Last name, First name>

Impacted <Business unit name>

Requirements <Provide the business requirements that describe the basic work process or business process, and how and/or where the computer system will fit into that process (i.e. steps that will be automated). Spreadsheets, flowcharts, the process model, or similar documentation can be attached if applicable.>

Justification <Business need - Describe why the business needs this computer-based solution.>

Resources <Job description, Last name , First name>

Objectives <Strategic objectives - Provide a summary of the problem that describes the main concepts of the solution and the objective to be achieved with the solution >

Pros <Project benefits>

Cons <Impact of not doing project>

Constraints <Known business constraints>

Assumptions <Business assumptions>

Dependencies <Dependencies - Certain business dependencies exist that may affect the project team's ability to implement the project. These dependencies are listed below so that they can be communicated and addressed. The items listed here can affect the success of the project so they should be addressed as quickly as possible.>

<Add a dependency here.>

<Results of any project pre-work>

Budget <Estimated budget>

Timelines <Estimate completion date>

Headcount <Number of IT customers involved>

<Concurrency of IT customers - %>

Location <Location of users>

<Local users>

<International users>

Capacity <Projected data>

<Storage volume – Initial storage estimate – Estimate growth rates>

Thinking problem management! Project request - Business Requirements Form - Page: 1

<Transactional volume>

Priority <High, medium, low>

ChecklistTop level

1. Usage behaviourWill this project cause a significant change in geographical usage, increase in user numbers or data volumes?

<Yes, No, N/A>

2. Security

Will this project result in any new remote access requirement to internal applications by 3rd parties?

<Yes, No, N/A>

Will this project require modifications to existing internal security technologies or solutions?

<Yes, No, N/A>

3. InterfacesWill this project result in any new interfaces or modifications to any existing interfaces of production applications within the bank?

<Yes, No, N/A>

4. ClientWill this project require any additional software to be loaded on existing desktops or any modification to the standard enterprise desktop build?

<Yes, No, N/A>

5. Portal integrationDoes this project require any enhancements or integration to any of the existing web services or portals (e.g. dot com or dot net)?

<Yes, No, N/A>

6. Technical infrastructure

Does this project require hosting facilities either within the enterprise data centre or external at another location?

<Yes, No, N/A>

Principle: If all the above questions are answered with a “No”, then no further IT checklist is required to be completed. If a question is answered with a “Yes” then the relevant IT checklist must be completed below. The project requestor/sponsor will be held responsible for malfunctioning or delays if IT infrastructure requirements are overlooked if selecting “No” as a convenience or if knowingly not completing this request form.

Usage BehavioursGeographic components

1.1Will the project have an application or service that is currently or will in the future be a multi-site or global solution?

<Yes, No, N/A>

1.2 Will this project have users of an application that are external to the enterprise? <Yes, No, N/A>

1.3 Will this project have users in several locations? <Yes, No, N/A>

1.4 Will this project deploy regional servers? <Yes, No, N/A>

1.5 Will this project operate servers located at the enterprise data centre? <Yes, No, N/A>

1.6 Will this project operate servers located at the enterprise’s disaster recovery sites? <Yes, No, N/A>

Application components

1.7Does a solution exist within the enterprise with similar applications or requirements regardless of platform type?

<Yes, No, N/A>

1.8 If a similar solution does exist can it be used without major modifications? <Yes, No, N/A>

1.9 Will an existing solution be used with major development effort required? <Yes, No, N/A>

1.10Has the enterprise Technical Architecture Board approved the underlying technology?

<Yes, No, N/A>

Security

2.1Has the confidentiality of the data and information being used in this project been assessed?

<Yes, No, N/A>

Thinking problem management! Project request - Business Requirements Form - Page: 2

2.2Have the legal and operational data retention requirements for this project been assessed?

<Yes, No, N/A>

2.3Are enterprise users required to access the applications used in this project from non-enterprise premises?

<Yes, No, N/A>

2.4 Must 3rd party users be able to access the applications used in this project? <Yes, No, N/A>

2.5Have the authentication and encryption requirements of the project been accessed?

<Yes, No, N/A>

2.6 Do the applications used in this project require modifications to the firewall ports? <Yes, No, N/A>

2.7 Does the application require access to 3rd party feeds? <Yes, No, N/A>

2.8 Does the application require access to internal feeds? <Yes, No, N/A>

Interfaces

3.1 Does this project require interfaces to existing enterprise solutions? <Yes, No, N/A>

3.2 Is all data used by this project stored within existing enterprise infrastructure? <Yes, No, N/A>

3.3 Is a real time interface required? <Yes, No, N/A>

3.4 Can an existing interface be reused? <Yes, No, N/A>

3.5 Are the applications within this project web based? <Yes, No, N/A>

Client

4.1 Does this project require new applications to be installed on user PC’s or laptops? <Yes, No, N/A>

4.2 Does this project require newer versions of existing applications to be installed? <Yes, No, N/A>

4.3 Are the applications within this project purely browser based? <Yes, No, N/A>

4.4Are all users of this project’s applications using the enterprise owned and managed PC’s and laptops?

<Yes, No, N/A>

4.5Does the data or information from this project required local storage on the PC or laptop?

<Yes, No, N/A>

Portal

5.1 Does this project require integration with extranet? <Yes, No, N/A>

5.2 Does this project require integration with intranet? <Yes, No, N/A>

5.3 Does this project require integration with a separate stand alone BU portal? <Yes, No, N/A>

Technical infrastructure

6.1. Is this a new system or an upgrade to an existing system?<New, Upgrade>

6.2 Does this project require any new servers? <Yes, No, N/A>

6.3 Does this project deliver new functions to be delivered using thin clients? <Yes, No, N/A>

6.4 Are any components of the project’s infrastructure being outsourced? <Yes, No, N/A>

6.5 Are they any requirements for remote management? <Yes, No, N/A>

6.6 Has a WAN impact assessment been conducted by the Communications team? <Yes, No, N/A>

Risk impactThe following is a scaled down version of CRAMM, known as Meerkat Risk Methodology:

Risk impact (Mark with a X) Dashboard designation = I

Evaluate the data and information that is directly effected by the incidentConfidentiality (Information is accessible only to those Secure

Thinking problem management! Project request - Business Requirements Form - Page: 3

authorized) ConfidentialRestricted*

PublicIntegrity (Safeguarding the accuracy and completeness of information)

Very highHighModerate*

LowAvailability (Authorised users have access to information when required.)

MandatoryVery highHighModerate*

LowRating Taking into account the above please rate the Risk impact

Critical Major Moderate Low

Risk vulnerability (Rate as either low, moderate, high or major) Dashboard designation = V

Rate the vulnerability in the following categories of the information or data that is affected by the incidentLoss <low, moderate, high, major>Error <low, moderate, high, major>Failure* <low, moderate, high, major>Rating Taking into account the above please rate the Risk vulnerability

Critical Major Moderate Low

Countermeasures Dashboard designation = CM

What measures are in place to mitigate any risks identified with the information or data affected by the incident<Due diligence>

Rating Taking into account the above please rate the Risk Countermeasures

Critical Major Moderate Low

The risk ratings are then aggregated into a dashboard. The dash board calculation is performed by assigning the ratings a value:

Critical = 4 Major = 3 Moderate = 2 Low = 1

The maximum score is 12 so the risk management dash board value is that combined aggregated ratings score worked out as a percentage of 12.

Risk Management Example (84%)

Impact Vulner. Counter

4 4 2

Business Processes Current Business Flow Diagram

<Insert diagram here.>Thinking problem management! Project request - Business Requirements Form - Page: 4

<Add any comments about the diagram here> Proposed Business Flow Diagram

<Insert diagram here.><Add any comments about the diagram here.>

Functional requirements Current System Context Diagram

<Insert diagram here.><Add any comments about the diagram here.>

Proposed System Context Diagram <Insert diagram here.><Add any comments about the diagram here.>

Technical requirements Technical environment

<Describe the current technical environment and the proposed new technical requirements for improving/correcting the current technical environment (include performance requirements, hardware requirements, and operating environment). Describe what technical requirements are necessary to meet the stated business requirements>

Data acquisition<Requirement.>

Data analysis<Requirement.>

Data output<Requirement.>

Security Physical security

<Requirement> Logical security

<User ID><Password>

Compliance<Address all compliance issues, such as architecture, security, regulatory, legal, electronic record, electronic signature requirements, etc. These items can impact the design and maintenance of the computer system.>

Audit trail<Address requirements for audit trail.>

Data retention<Address the company policy on records retention and how those relate to the requirements of this system.>

Financial

Information Systems Business

Exp / R Cap / R Hours Exp / R Cap / R Hours

Software 0.00 0.00 — 0.00 0.00 —

Hardware 0.00 0.00 — 0.00 0.00 —

Personnel Resources 0.00 0.00 — 0.00 0.00 —

Consultants/Contractors 0.00 0.00 0 0.00 0.00 0

Support Resources 0.00 0.00 0 0.00 0.00 0

Maintenance Contracts 0.00 0.00 0 0.00 0.00 0

Miscellaneous 0.00 — — 0.00 — —

Total 0 0 0 0 0 0

Figures in thousands for estimated life of product.

Thinking problem management! Project request - Business Requirements Form - Page: 5

Checklist for business requirements

Organization Are all internal cross-references to other requirements correct? Are all requirements written at a consistent and appropriate level of

detail? Do the requirements provide an adequate basis for design? Is the implementation priority of each requirement included? Are all external hardware, software, and communication interfaces

defined? Have algorithms intrinsic to the functional requirements been defined? Are all known customer or system needs included?

Is the expected behaviour documented for all anticipated error conditions?

<√>

Correctness Do any requirements conflict with or duplicate other requirements? Is each requirement written in clear, concise, unambiguous language? Is each requirement verifiable by testing, demonstration, review, or

analysis? Is each requirement in scope for the project? Is each requirement free from content and grammatical errors? Can all of the requirements be implemented within known constraints? Are any specified error messages unique and meaningful?

<√>

Quality attributes Are all performance objectives properly specified? Are all security and safety considerations properly specified? Are other pertinent quality attribute goals explicitly documented and

quantified, with the acceptable tradeoffs specified?

<√>

Traceability Is each requirement uniquely and correctly identified? Is each software functional requirement traceable to a higher-level

requirement (e.g., system requirement, use case)?<√>

Special issues Are all requirements actually requirements, not design or

implementation solutions? Are the time-critical functions identified, and timing criteria specified for

them? Have internationalization issues been adequately addressed?

<√>

Internal Use Only

Sign off <Objectives and requirements signed off by stakeholder> <√>

Impact assessed:

Networks <Description of capacity and resource impact> <√>

Service Desk <Description of capacity and resource impact> <√>

Procurement <Description of capacity and resource impact> <√>

Operations <Description of capacity and resource impact> <√>

Projected Man Days

<days> Project <days> <√>Task <days>

Thinking problem management! Project request - Business Requirements Form - Page: 6