Acceptance of the elderly care system should be carried out along a service process. Each page can be saved separately, which does not mean that appointments, tasks, handovers and bills have been connected; before going online, you need to check the results from the starting point of the business and cover common exceptions.

Scenario list

Organize acceptance based on real business processes, such as appointment changes, bed transfers, task handovers and cost adjustments. It is not enough to check whether the page can be opened alone. It is also necessary to confirm whether the records of the same business in multiple modules are consistent.

Role Test

Use different job accounts to check the scope of operations and data visibility. The test data should use specially prepared sample data, focusing on observing the system processing of unauthorized operations, repeated submissions and incomplete data.

Delivery materials

It is recommended to organize module descriptions, deployment configurations, data backup and recovery steps, and problem lists. The acceptance conclusion should correspond to the agreed scope, and subsequent optimization needs should be recorded separately to facilitate the team to clarify maintenance responsibilities and change boundaries.

Scenario verification

Acceptance can start from an appointment of the service object and sequentially check task assignment, handover, completion and billing records. After the normal process is passed, the abnormal entry for verification of insufficient permissions and data supplement scenarios will be added.

Specific verification method

Start from the appointment confirmation, check the task assignment, completion and billing association; try to handle the process using an account with insufficient permissions to confirm that the original record has not changed; continue the process after filling in the missing information and check whether the order is repeated; during handover, verify whether the person taking over can read the necessary background.

Acceptance is based on the complete service link, and the problem record clearly states the prerequisite information, account number and operation steps. After repairing, check the same path again to confirm that the page feedback is consistent with the business results.