Professional Documents
Culture Documents
27 PSO Business Requirements
27 PSO Business Requirements
Version 1
VERSION AND APPROVALS
UTORS
VERSION HISTORY
Version # Date Revised By Reason for change
This document has been approved as the official Business Requirements Document for <project name>,
and accurately reflects the current understanding of business requirements. Following approval of this
document, requirement changes will be governed by the project’s change management process, including
impact analysis, appropriate reviews and approvals.
DOCUMENT APPROVALS
Approver Name Project Role Signature/Electronic Approval Date
TABLE OF CONTENTS
Project Details........................................................................................................1
OVERVIEW...............................................................................................................1
DOCUMENT RESOURCES..........................................................................................1
GLOSSARY OF TERMS..............................................................................................1
PROJECT OVERVIEW................................................................................................1
4.1 Project Overview and Background.................................................................................................... 1
4.2 Project Dependencies....................................................................................................................... 2
4.3 Stakeholders..................................................................................................................................... 2
USE CASES..............................................................................................................2
Use Case Diagram.................................................................................................................................. 2
Use Case Narrative................................................................................................................................. 3
BUSINESS REQUIREMENTS.......................................................................................5
APPENDIXES............................................................................................................7
Appendix A – Business Process Flows................................................................................................... 7
Appendix B – Business Rules Catalog.................................................................................................. 10
Appendix C- Models.............................................................................................................................. 10
Traceability Matrix................................................................................................................................. 10
Use Case Narrative Instructions............................................................................................................ 10
PROJECT DETAILS
Project Name Enter Project Name
Project Type (e.g. New Initiative or Phase II)
Project Start Date
Project End Date
Project Sponsor
Primary Driver (e.g. Mandatory or Efficiency)
Secondary Driver
Division
Project Manager/Dept
OVERVIEW
This document defines the high level requirements [insert project name]. It will be used as the basis
for the following activities:
DOCUMENT RESOURCES
GLOSSARY OF TERMS
Term/Acronym Definition
<Identify any terms and acronyms
used within this document>
PROJECT OVERVIEW
4.3 Stakeholders
The following comprises the internal and external stakeholders whose requirements are represented
by this document:
Stakeholders
1.
2.
3.
# Assumptions
List any assumptions the requirements are based on
# Constraints
List any constraints the requirements are based on
USE CASES
< The primary purpose of the Use Case is to capture the required system behavior from the
perspective of the end-user in achieving one or more desired goals. A Use Case contains a
description of the flow of events describing the interaction between actors and the system. The use
case may also be represented visually in UML in order to show relationships with other the use cases
and actors>.
<Each Use Case should be documented using this template. Refer to the Appendix for Use Case
Narrative instructions>
Actors:
Description:
Preconditions:
Postconditions:
Normal Course:
Alternative Courses:
Exceptions:
Includes:
Priority:
Frequency of Use:
Business Rules
Special Requirements:
Assumptions:
Notes and Issues:
Actors: User
Description: This use case describes the main way this interactive campus map
will be used – as a web browser accessed application. The user
accesses the appropriate URL and interacts with the functionality
made available.
Preconditions: Web browser opened, and interactive campus map URL accessed.
Postconditions: User navigates from interactive campus map web site.
Normal Course: 1. Open browser
2. Navigate to campus map URL
3. Interact with the campus map using available functionality
Alternative Courses: None
Exceptions: None
Includes:
Priority: High
Frequency of Use: Once per visit.
Business Rules TBD…
Special Requirements: 24/7 access
Response times comparable to common web mapping solutions
(e.g. Google Maps)
U of M accessibility requirements
U of M eCommunications requirements
Assumptions:
Notes and Issues:
Use Case Graphic
BUSINESS REQUIREMENTS
The following sections document the various business requirements of this project. Please use the
existing template to document
ID – Prefix ??
TypeRequirement
??
??
??
Required
Reference
ID – Number
Use Case
Function – Feature - Requirement Comments
F 0005
F 0007
F 0007
F 0008
F 0005
F 0007
F 0007
F 0008
Security, Access Control, and Compliance Requirements (Includes roles, user access
needs)
F 0001
F 0002
F 0003
F 0004
F 0005
F 0007
F 0007
F 0008
F 0005
F 0007
F 0007
F 0008
F 0005
F 0007
F 0007
F 0008
APPENDIXES
Appendix A – Business Process Flows
<Describe the current existing process workflow using flow diagrams (i.e. Visio Flowcharts) and/or a detailed narrative.>
EXAMPLE: Business Process Flow Diagram – Project Accounting Closeout
Check Cost Resolve Cash Inactivate in
Set Status Wait 30 Days Reconcile Project Finalize PM Fees Capitalize Close Phase
Sheet Balance PeopleSoft
Client
POC
FCA Final
Administrator Notice
Legend
= Reject
Tools/Process - Unifier - N/A - Unifier - Unifier/Reports - P/S Excel S/S - Unifier Cost and - Unifier - PeopleSoft - Unifier
- E-mail Reports (3) - P/S - Unifier Funding Sheets - P/S - E-mail
- Unifier Report Umail - Cost Sheet
Risk/Issues - Starts 60 day - N/A - Balance must - PA makes - Duel - List risks to - N/A - No more
cycle time each be = or > $0 changes and adjustments – successful financial trans
time updates Unifier P/S and Unifier completion actions in P/S
Controls - Unifier Open PA - Unifier Open PA - Project Cost - Pay Apps - Cost Sheet - N/A - Accounting - PeopleSoft
Closeout Action Closeout Action Sheet - Invoice(s) Services Deprec Reporting
Item Report Item Report - Comments - Accounting List
fields Adjustments
As Is Diagrams
<Insert As Is Diagrams here (if applicable)>
Assignee
Start
Assignee
Process Process End
Assignee
Process
Assignee
Process
Assignee
Assignee
Assignee
Assignee
Assignee
Assignee
Start
Assignee
Process Process End
Assignee
Process
Assignee
Process
Assignee
Assignee
Assignee
Assignee
Assignee
Business Rule Name: <The name should give you a good idea about the topic
of the business rule.>
Identifier <Defines unique identifier.> EXAMPLE: BR1
Description <Defines the rule in detail.> EXAMPLE: “All employee
labor is tracked, reported and billed in 15 minute
increments.”
Example <(Optional) An example of the rule>
Source <Source of the rule. E.g. stakeholder>
Related Rules <List of related rules, to support traceability>
Appendix C- Models
<Insert models here>
Traceability Matrix
<Insert traceability matrix here>