Document directory
- 1.1 Background
- 2.1 XXX Module
- 2.1.1 front-end of XXX Module
- 2.1.2xxx module backend
My new employee has to hand over some projects from my colleague because of my resignation. There are only some development document-related templates in the company, and there is no document handover template, so the document handover template is determined by ourselves. Based on my work experience, I have developed the following templates. You are welcome to correct them if they are inaccurate.
Document handover instructions
Deliverable:
Recipient:
Acceptance person:
Handover date:
Overview 1.1 Background
Deliverable business function module 2.1 XXX Module
Module owner: |
Jj |
Frontend owner/completion: |
Jj |
Backend owner/completion: |
CJ |
Interaction with databases: |
Yest_systemreceive |
Whether the requirement document exists |
Cnxx/requirement document |
Whether the detailed design document exists |
Cnxx/Detailed design documentation |
2.1.1 front-end of XXX Module
2.1.1.1 interface display
Shows the display interface of this function.
2.1.1.2 front-end architecture
Including the interaction between pages and whether to introduce external plug-ins
2.1.1.3 source code location
../Cnxxx/Front/srccode. js
2.1.1.4 business flow chart
If this module involves flow chart conversion, you can use a flow chart to describe the status conversion in the system.
2.1.1.5 development progress
Not yet developed |
|
Development Process |
|
Development is basically completed, but bugs are not completed |
|
Development complete |
|
2.1.2xxx module backend
2.1.2.1 backend Architecture
Display the call relationships between different service layers in a sequence chart
2.1.2.2 source code location
../Cnxxx/office/srccode. Java
2.1.2.3 associated database
If this part interacts with the database, write the database table that interacts with it.
2.1.2.4 development progress
Not yet developed |
|
Development Process |
|
Development is basically completed, but bugs are not completed |
|
Development complete |
|