Technical Checklist |
|---|
Development |
Task | Reviewed By | Review Date |
| Expand |
|---|
| Performed by IQX Developer Cover all user stories. Is an update to an existing app? If so, have you changed the workflow steps? Or the data model? Or the process? In this instance, consider:
- development tasks / data manipulation to ensure that forms that are in-flight (for example, submitted before change, approved after change) will function correctly.
- the cut-over tasks at go-live. Do you need to execute specific steps to ensure that forms that are in-flight (submitted before change, approved after) will function correctly? |
| | |
| Expand |
|---|
| Performed by IQX Developer Cover all test cases |
| | |
| Expand |
|---|
| Performed by IQX Developer IQX Code review checklist Self assessment |
| | |
| Expand |
|---|
| Performed by IQX Peer Developer IQX Code review checklist |
| | |
| Expand |
|---|
| Performed by IQX Business Analyst, IQX Developer and Business User |
| | |
- Maintain FAB configuration
| Expand |
|---|
| Performed by IQX Developer UI5 version
App roles
App user(s)
App admin user(s)
FAB Launchpad |
| | |
- Develop Admin / Matrix approval app
| Expand |
|---|
| Performed by IQX Developer |
| | |
- Include Number Range (NOT Intervals) in transport
| Expand |
|---|
| Performed by IQX Developer Prerequisite: Number Range created |
| | |
| Expand |
|---|
| Performed by IQX Developer |
| | |
- Include STVARV variables in transport (where applicable / possible)
| Expand |
|---|
| Performed by IQX Developer |
| | |
- Include System Alias in transport (must be generic)
| Expand |
|---|
| Performed by IQX Developer Prerequisite: System Alias created |
| | |
- Include activation of OData service in transport
| Expand |
|---|
| Performed by IQX Developer Prerequisite: OData Service created |
| | |
- Include FLP config and user roles / groups / catalogs to transport (if client chooses to use Fiori Launchpad, not FAB Launchpad)
| Expand |
|---|
| Performed by IQX Developer |
| | |
Testing |
Task | | Reviewed by |
| Expand |
|---|
| Performed by IQX Business Analyst
Cover all test cases and ensure testing in the target version.
Cover all devices specified in Non-Functional Requirements even if emulated.
NOTE: Cover all browsers, especially if there is even a remote possibility that Internet Explorer might be used. |
| | |
- Integration Testing
| Status |
|---|
| colour | Yellow |
|---|
| title | to be confirmed |
|---|
|
| Expand |
|---|
| To be confirmed for each Project |
| | |
| Expand |
|---|
| Performed by Business User Support if necessary, but end-to-end testing by system users with their own logons in |
| | |
Pre-Go-Live |
Task | | Reviewed by |
|---|
- Cutover Steps and Go-Live Checklist Document
| Expand |
|---|
| Performed by IQX Developer and/or IQX Business Analyst All manual pre-go-live steps required in QA, PRD or other systems, including external systems (OneList, SharePoint, DirectoryWatch, etc.).
All manual post-go-live steps required in QA, PRD or other systems, including external systems. |
| | |
- As Built Technical Specification Document
| Expand |
|---|
| Performed by IQX Developer |
| | |
- As Built Functional Specification Document
| Expand |
|---|
| Performed by IQX Business Analyst |
| | |
| Expand |
|---|
| Assigned resource to be confirmed per project Evidence to support release for go-live |
| | |
- Confirm the PRD has the correct version of FAB installed
| Expand |
|---|
| Performed by SAP BASIS |
| | |
- Create role for OData Service
| Expand |
|---|
| Performed by SAP Security or SAP BASIS |
| | |
- Create Service account user (if required for background jobs)
| Expand |
|---|
| Performed by SAP Security or SAP BASIS |
| | |
- Event linkages to be maintained (if required for background jobs)
| Expand |
|---|
| Performed by IQX Developer or SAP BASIS |
| | |
- Schedule background job for escalations (if required)
| Expand |
|---|
| Performed by SAP BASIS |
| | |
- Schedule other background jobs, as required
| Expand |
|---|
| Performed by SAP BASIS |
| | |
Post-Go-Live |
Task | | Reviewed by |
- Populate Admin / Matrix approval app in PRD
| Expand |
|---|
| Performed by Client Super User Prerequisite: Transports Completed |
| | |
- Maintain Number Range intervals
| Expand |
|---|
| Performed by SAP BASIS, IQX Developer or Client Super User |
| | |
| Expand |
|---|
| Performed by SAP BASIS |
| | |
- Refresh caches on Gateway
| Expand |
|---|
| Performed by SAP BASIS |
| | |
- Sanity check - run app in PRD if possible
| Expand |
|---|
| Performed by IQX Developer or Client Super User |
| | |
- Post-mortem and team feedback
| Expand |
|---|
| Performed by IQX Developer, IQX Business Analyst and IQX Project Manager - Did we meet the customer brief?
- What did we do well during this project?
- What did we do poorly during this project?
- What did we not foresee when planning for this project?
- What cool technology / software components did we build (that can maybe be reused in other projects)?
- Did we meet the budget for this project? If not, why not?
… and so on
|
| | |
