No. | Tasks | Activities |
---|
1 | Database schema ER diagrams and documentation | - Update existing ER diagrams on the wiki
|
| | - Capture changes in a change version document
|
| | - Identify changes made during the above specified timeframe and document justifications for changes
|
2 | Service layer implementation | - Ensure that business logic is not leaking to other layers
|
| | - Ensure that codebase follows the defined architecture. Document any abnormalities in implementation and present for discussion.
|
3 | Transaction pattern implementation | - Check if implementation follows pattern documented on the wiki
|
| | - Identify transactions which are not implemented
|
| | - Identify and documents challenges in implementing documented pattern
|
| | - Any concerns related to transaction pattern
|
4 | Data replication | - List of tables which are replicated to hubs
|
| | - How data portioning is handled and implemented
|
| | - Data replication conflicts
|
5 | Data security and confidentiality | - List of tables which store sensitive data
|
| | - How sensitive data is stored.
|
6 | Development process | - Level of documentation for changes
|
| | |
| | |
7 | User experience and engagement | - Rate of usage from end users
|
| | - User engagement level – completion rate
|
| | - List of CATS activities and screenflow map document
|
8 | Deployment and operation | - Process of pushing changes to production environment
|
| | - How database changes are propagated from dev environment to production
|
| | - Security of deployment parameters – user names, password, configuration files …
|
| | - Configuration and deployment instructions for provisioning new instance of CATS
|
9 | User manual and help instruction | - User manual evolution – has the user manual evolved together with the application?
|
| | - Accessibility of contextual instruction in the application. Here you can ask the question – how many pages have contextual instructions? How many pages have links to the user manual?
|