| Table of Contents |
|---|
| Page Properties | ||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Stakeholder Registry
Name | Party | Project Roles |
Pam Stevenson | Treasury | Project Manager, UAT Tester & Sign-off authority |
Carraman | Treasury | Project Manager & UAT Tester |
Daria Story | Treasury | Project Manager, UAT Tester & Sign-off authority |
|
| |
Ethan Mata | Tyler Tech Alabama | Director of Development |
Marla Vickers | Tyler Tech Alabama | General Manager |
Robert Hines | Tyler Tech Alabama | Director of Operations |
Bruno Litman | Tyler Tech Alabama | Director of Technology |
Lauren Littlefield | Tyler Tech Alabama | Account and Project Manager |
| Child pages (Children Display) |
|---|
👋 Objective
· Create a new 'Transaction Tracker’ feature within the existing SAFE application.
· Allow QPDs (and Custodians with QPD access) to submit requests for pledges and withdrawals. Once submitted the pledge request will follow a workflow until Treasury approves or Cancels the request. If approved, the request will become a pledge or withdrawal.
· Create new user roles for Custodians (and Custodians with QPD access) to access SAFE.
· Allow Treasury users to approve, edit, or deny requests for pledges and withdrawals.
Out of Scope
Agreements
Generation/creation
Treasury can save document uploads to each QPD
User Authorization Form
Treasury would like logic added to SAFE for User Authorization, this is outside of the scope of this project but needs to be quoted separately.
Custodian Transfers
Treasury would like logic added to SAFE that would require Custodians to attach receipts to open/active securities when a Custodian Transfer is completed on the Admin portal. This is outside of the scope of this project but needs to be quoted separately.
⏲ Schedule Control
Project Timeline: November 1st 2023, Test Environment
| Roadmap Planner | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Sites
Test:
Production:
Test Cases and Credentials
Change Management
Change Request Document | Timeline Extension |
|---|---|
| Jira Legacy | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
UAT
UAT Acceptance: At the end of UAT the system will be considered accepted if no more than Zero (0) Level 1 (Blocker) defects are identified, no more than one (1) Level 2 (High) defects are identified, no more than eight (8) Level 3 (Moderate) defects are identified. For Level 4 (Minor), because processing is not substantially affected, defects of this type will not preclude acceptance. Severity levels are defined as follows:
Severity 1 - Blocker: The defect prevents the system or application from meeting the majority of Treasury’s requirements. Catastrophic defects involve any situation where the loss of service is non-recoverable.
Severity 2 – High: No mutually-agreed work around: The defect prevents a major function of the system or application from meeting Treasury’s requirements and there is no effective work around to meet these requirements. Appropriate for instances where service or delivery has been impacted although not completely disabled, and there are no workaround procedures available to fix the problem.
Severity 3 – Moderate: With a mutually-agreed work around: The defect prevents a major function of the system or application from meeting Treasury’s requirements, but there is an effective work around to meet these requirements. This is appropriate for instances where service or delivery has been impacted, although not completely disabled, and workaround procedures are available to fix the problem.
Severity 4 - Minor: The defect prevents a minor function of the system or application from meeting Treasury’s requirements. Appropriate for instances where minor functions are disabled, but service or delivery is not affected.
UAT Feedback Provided Date | Severity | Jira ticket |
|---|---|---|