This document outlines the required documented need for project transition into the service delivery team. Project to Operation transition begins with a document analysis. Information should be forwarded to allow the service team to review and ask questions around clarification. In cases, where documentation is not available, the project team will work with the service team via knowledge sharing workshops to address any gaps.
DOCUMENTATIONS/DELIVERABLES:
Documentation type | Available Y/N | Document format | Document location |
|---|---|---|---|
Project Charter |
|
| 311 P1 Project charter to be used, new governance structure/body
|
High Level Business Requirements |
| JIRA User Stories , Confluence page summary | Required Confluence page with a summary of all features in the MVP delivered in final release. Each Epic/feature can drill down to user stories, tasks etc. which were approved and delivered
https://toronto.atlassian.net/secure/Dashboard.jspa?selectPageId=11258
|
Detailed Business Requirements |
|
| o High Level Bus.Reqmts: /wiki/spaces/EP2/pages/421134364 § Ref Appendix J.2 § Appendix V (Spark recommendation included in the RFP) o User Stories : https://toronto.atlassian.net/secure/Dashboard.jspa?selectPageId=11258 o Project Docs : ECRM - Phase II- 311 Toronto CRM Project - Confluence (atlassian.net)
Service Request Categories (Updated document that includes comments from CCG and 311 responses (https://toronto.atlassian.net/browse/EP2-5546 )
Special Characters: Special Characters
|
Business Impact Assessment |
|
| Documentation of impact assessment if any conducted for any major change. Feature, product or deliverable
JIRA Tasks labelled as Decisions ( Shine/Roopy)
The link to the EARB minutes can be found at https://toronto.atlassian.net/browse/EP2-1687?atlOrigin=eyJpIjoiOWFkOTgzYWUxMzJlNDNkOGIxYTBiYzEyNGU5MTU3YjIiLCJwIjoiaiJ9 . Attached Email for below decision.
|
Documentation of Cloud assessment and approval |
|
| Email or Documentation with assessment details and final approval from Cloud & Internet Services Team
Assessment from 311 P1 used ( Documentation from 2018) CARB review not done as CARB was created only in 2019 ( Shine/Roopy to send emails related to this decision)
|
Architectural Design Documents |
| Confluence | Is Confluence page to be referred for Architectural details?
Require updated information to reflect new system architecture delivered by project. Require documentation, diagram depicting the architectural components, integration with external systems etc.
Document 'Toronto Architecture': the architectural components /information seem to be related to current state (311p1). /wiki/spaces/EP2/pages/1865678863
Below link has Webex recordings only. |
Functional Design Documents |
|
|
Functional Specifications or Wireframes/Mock up's provided by 311 PMO team Link:
· Salesforce SPARK : https://toronto.atlassian.net/l/c/XD0FyNu8
|
Data Model |
|
| Logical and Physical Data Model documentation required. · Data Model & ERD : https://toronto.atlassian.net/l/c/3y03a1bH
Data Model – Design Document – is this the most recent version? |
Technical Design Documents |
|
|
Design Elements: Technical Design Documentation should include details for all custom Salesforce components. Example: API Name, purpose, working details etc. to be included against each component.
Sustainment Team - Session #4 - Custom Code Utilized Services (GCC services etc.) Process Builders Email templates Validation Rules Custom Metadata Custom Settings Mobile Application custom development Global Configurations etc. Scheduled jobs, batches etc.
· Adding a SmartLink to an Article · Reports and Dashboards Questions from IBD · Regex pattern: Sustainment Team - Session #2 - Solution & Self-Service Configuration - ECRM - Phase II- 311 Toronto CRM Project - Confluence (atlassian.net) · P1 to P2 Field Mapping (MLS Noise Field Mapping): /wiki/spaces/EP2/pages/1726775385
Field Validation: /wiki/spaces/EP2/pages/1463877732
|
Integrations |
|
| Middleware API endpoints for web, mobile and Salesforce
/wiki/spaces/EP2/pages/2173861909
/wiki/spaces/EP2/pages/2001404015
/wiki/spaces/EP2/pages/1865678863
Certificate and Mutual Authentication Certs installed 2 Mutual authentication 2 certs Integration cert installed on downstream systems Connected apps 311 Integration
Certificates – Downstream ( for connection with Divisional systems) Mutual Auth – Upstream ( WP)
The permanent links to the API specifications are: https://app.swaggerhub.com/apis-docs/cityoftoronto/ECRM_311_to_backend/ https://app.swaggerhub.com/apis-docs/cityoftoronto/ECRM_Backend_to_311/
Service callout to Geocoder ( PIS/GCC) – Middleware API endpoints for web, mobile and Salesforce Phase 1 - Data Migration Requirements and Mapping /wiki/spaces/EP2/pages/2275770377
|
Documentation of change to architectural or technical design |
|
|
|
Documentation of Prototype |
|
|
|
Documentation of Prototype feedback/ approval |
|
|
|
Data Dictionary (includes all relevant objects, fields and data types) |
|
| Field and data type information from Salesforce to be extracted and provided in Excel format.
|
Test Plan(s) |
|
| Salesforce Unit Test plan, related documentation for each user story or deliverable.
Xray Link: Code to be transitioned to City Gitlab ? |
Unit Test Scripts |
|
| Salesforce Apex Test scripts, Overall coverage, test classes, etc.
|
Unit Test Results |
|
| Salesforce Unit test results documentation - custom code |
System Integration Test Scripts |
|
| Integration Test Scripts documentation
|
System Integration Test Results |
|
| Integration Test results documentation
|
Performance Test Scripts |
|
| Performance Test Scripts documentation
|
Performance Test Results |
|
| Performance Test Results documentation
Action Item: follow up with Marco and Johan
|
Capacity |
|
| Data storage - growth plan ( volume forecasted) · Additional Storage Analysis : https://toronto.atlassian.net/l/c/h13v91c6
Salesforce additional storage procured Staff report – Shine to send Powerpoint - Shine to send Council approval
|
Security Test Results (PIA/VA/TRA), Security Audit |
|
| Security test results Approval email, related documentation provided by Security ( CISO) Team after security screening the application and integrations.
Executive Go/NO GO Readiness Checklist – to be uploaded by Shine prior to GO Live
311 Toronto - Consolidated Security Matrix
|
Security Framework |
| Confluence | Salesforce security set up: /wiki/spaces/EP2/pages/1115357201
/wiki/spaces/EP2/pages/1106935907
Security matrix link: 311 Toronto - Consolidated Security Matrix Field level security
|
Email Management |
|
| |
Mobile Application |
| Confluence | /wiki/spaces/EP2/pages/844529721
REACT framework? Mobile app delivery has been postponed to Nov /Dec 2021 KT sessions will be arranged later part of the year.
|
User Acceptance Testing Scripts |
|
| UAT scripts ( Xray link)
|
User Acceptance Testing Results |
|
| Link to test results (Example : A link with all stories in a Sprint with test results attached) |
Accessible Testing Scripts |
|
| Testing details, use cases provided by AODA project team
Issue navigator - Jira (atlassian.net)
|
Accessible Testing Results(AODA) |
|
| Testing results , Email of AODA testing approval provided by AODA project team |
Traceability documentation |
|
| Confluence page to summarize the traceability and mapping for delivered items Epic > user story > tasks Traceability matrix Test case> user story Traceability matrix
No Traceability documentation |
Approval of Testing results |
|
| UAT Sign off Email
Waiting for final 311 sign off (Oct 08) |
Training documentation |
| Confluence | Training: /wiki/spaces/EP2/pages/2072969270
Sustainment handoff: /wiki/spaces/EP2/pages/2190999553
/wiki/spaces/EP2/pages/2196865128
https://toronto.atlassian.net/l/c/11z41eW3
|