Software development schedule

The company began to follow the regular path, so everything had to have a flowchart. To prepare a software development schedule, we had to strictly follow the schedule. The previous progress was basically only the actual work content, not subdivided into each stage

I found a good decision on the Internet, and then modified it based on actual needs. The record is shown as follows:

Software development schedule
Phase	Main Work	Documents to be completed	Planned Start Time	Planned End Time	Actual Start Time	Actual End Time	Owner
System Requirements	Survey user needs and user environment
	Demonstrate Project Feasibility	Project preliminary development plan schedule
	Prepare a project preliminary plan
	Development Plan Review
Requirement Analysis	Determine the system Runtime Environment	Requirement Specification
	Establish system logic model	Project development plan
	Determine system functions and performance requirements	User Manual Overview
	Prepare requirement specifications, user manual summary, and test plan
	Confirm the Project Development Plan
Outline Design	Establish the overall system structure and divide functional modules
	Define functional module Interfaces	Database Design Specification
	Database Design (if needed)
	Develop assembly test plan
	Review completed documents
Detailed Design	Design specific implementation algorithms for each module
	Determine the detailed interface between modules
	Develop a module test plan
Implementation	Compile program source code
	Test and debug modules	User Manual
	Compile User Manual
	Review implementation process and completed documents
Integration Test	Execute the integration test plan
	Compile the integration test report
Acceptance Test	Test the entire software system (robustness test)
	Trial User Manual	User Manual
	Compile the Development Summary Report	Development work summary
Maintenance	Modify to correct errors and improve applications
	Manage modifications
	Compile Fault Report and modification report
	Revise User Manual