Document output checklist for task handover

As long as there is the handover of the task must have the output of the document, this should be a big principle!

Serial number	Deliverable Name	Whether the necessities	Deliverable Description	Deliverable Main Purpose	If the impact of the deliverable on the project is not provided
1	Product Design Documentation	Is	1. Functional Design Documentation	1. Review the relevant functional design when you need to evaluate	1. The demand is prone to omission, especially some changes in the larger product
			2. Database design documentation (the meaning that each value is required for enumeration types)	2. When the database is taken or the bug is verified, it is easy to check the data	2. Low development efficiency, need to constantly consult others
2	Report Designer, new workflow operations manual, etc.	Is	1. Basic configuration and Operation guidelines	1. Rapid development of reports	If you have problems, you can only find and seek others on your own, very low efficiency
				2. Quick configuration of workflow site, can find when encountering problems
3	Business Solutions	Is	1, the origin of the function. (such as the planning system of the Conference Management module, for what reason increased)	1, learn the new system, quickly grasp the customer's actual business	1, do not know the function added what is the use.
			2. Business Flow chart		2, if the project needs to adjust the function, do not know what impact on the business.
			3, CP point description
			4. Management value
4	function Specification Design Book	Is	1, must be described by the new function, not as the increment described before.	1, to evaluate the new version of the requirements, through the document to query the specific situation of existing functions, reduce the direct code reading work. (For the standard version, you can use the code without looking at the document, whichever is right)	1, only through the code to understand what the existing system is, low efficiency.
			2. Describe the flow of data clearly	2. Learn the new system
			3. Describe clear business logic
			4. Describe the system flow chart clearly
5	Data	Is	1, table relationship.	1, when learning a new system, combing data relations.	1, only through the code to understand what the existing system is, low efficiency.
			2, Data dictionary.	2, the evaluation of demand, combing data relations.
			3, stored procedures.
			4. View
6	Bug Fix Checklist	Is	1. New version fix bug list	1. Quick fix of known bug in old version	1, for a known bug if there is no unified, proven solution, the project team may be repaired due to bug or incomplete repair caused by a secondary bug
			2, each bug for each version of the old product code-level repair scheme	2, the project team according to the list of the old product bug active repair	2, do not know the old version of how many bugs, no inventory support active repair
7	Patch packs that can be updated directly by customers	Is	When publishing a large version of a patch pack, the product team is required to make a patch package that can be updated directly by the customer, rather than dropping a bunch of files onto the server (306 SP1)	1, for the new customers have not done development, you can directly use the patch package upgrade, do not need the project to do another upgrade package	1, each project team to make an update package, repeat Labor
					2, the product provides the patch package directory exists a large number of empty folders and redundant files, remove the risk, do not delete the update package too large
8	Mobile products and related documents	Is	1, micro-assistant and other mobile products with the release of the ERP, placed under each version	1, easy to find the corresponding version of the ERP mobile products, easy to project team learning and customer on-line development	1, now micro-assistant and standard products released separately, not clear which version corresponds to
			2, mobile operation manual, environmental deployment and other related information.		2, the new version of the product customers are already in use, and the corresponding mobile products are not released resulting in customers can not use
			3, the use of the framework and technology and related information		3, lack of channels, for the company's new products do not understand.

Document output checklist for task handover