Business Requirements–Insert name of project (w/ Eclipse #)
This document is used to capture project business requirements. The information gathered here will be used in the identification of an appropriate service or application solution. The approach is intended to reveal the business requirements of the client or service (i.e. what is the desired behaviour), as opposed to starting with a solution with the goal of tailoring the requirements to fit it.
Identifying Information
Project Lead:Name of person who will lead project (represents project team)
Sponsor:Person who would be sponsoring the project
ITS Service Owner:Person who owns (or will own) the service the proposal relates to within ITS
Client/Business Owner:Contact name + department name, if for someone outside of ITS
Date:
RequirementsSummary
GeneralWhat is the purpose of the proposed application? What prompted the search for a technical solution?
What do you need ITS to do?
- build something,
- install something
- project management
- investigate solutions
- decommission a service
- archive data
- support
- liaison with third party company
Have you investigated other technical solutions currently available at Queen’s?
What is the anticipated timeline for a solution to be in place?
What if any approvals have been granted for this project/investigation/funds, etc.?
Application
What is your development budget for this application? Will the application generate revenue, or are you planning to cover the development costs with other funds?
Will the application have a specific lifecycle (e.g. academic year)? If so, please identify key dates.
Please describe the application you would like developed, and identify who the primary customers are:
- students, staff, applicants, faculty, researchers
- for all of Queen’s or a certain program/area?
Please describe the process you currently use to meet this business need.
How do you determine who should have access to the system?
If there is an existing system, will the existing information need to be imported into the new system?
Existing system:
- Lifecycle
- Documentation
- Current support/who? (internal/external)
- Secure?
- Accessible?
- PCI compliant? (if payments required)
How many yearly transactions do you expect?
Will online payments be required?
If an application is submitted, is there a unique confirmation number generated, and/or an email generated?
Will the application generate revenue for your department?
What level of support will be required once the application is implemented in your area?
- ITS supported?
- Does your area have its own technical support?
Will this application handle or store data that is confidential or personal in nature?
Do you have a preference which technology is used to build the application? (e.g. PHP, Java, etc).
System Integration
Should your new application be accessed from:
- MyQueen’sU
- elsewhere? (if elsewhere, please provide details)
Will people log in using their Queen’s NetID? If not how will they authenticate in this application?
Is this a standalone system or will data from other systems be required:
- Student data
- Finance data
- HR data
- Research data
If you are going to need information from other systems, how are you currently getting/sending information to/from those systems?
Will the application be hosted on central servers?
Administrative Functionality
What administrative functions are required?
- sort by date submitted?
- view in PDF format?
- mass printing functionality?
Will administrative functions (ongoing operation requirements) to update the online application be required?
- update cutoff dates
- change certain text
- rollover from one year/cycle to another?
Do you require access to more than one year/cycle’s data at a time?
If yes, does the older data need to be accessed from the online application or can it be exported and accessed with other tools (e.g. Excel, offline archives)?
ITServices_BusinessRequirements_ProjectName_YYYY-MM-DD_v#_TEMPLATEv1.docxPage | 1 of 4