Software project development plan template 1
Project name: * * * * * *
Review date:
1 Introduction
The use of 1. 1
Explain the purpose of writing this project development plan and point out the expected audience.
1.2 background
Description:
A. the name of the software system to be developed;
B. The task proposer, developer and user of the project, and the computing center or computer network for implementing the software;
C. Basic interaction between software systems and other systems or institutions.
1.3 definition
List the definitions of technical terms used in this document and the original phrases of foreign initial words.
1.4 reference
List useful reference materials, such as:
A. Approved project plan or contract and approval from higher authorities;
B. Other published documents belonging to this project;
C documents and materials cited in this document, including the software development standards to be used.
List the titles, document numbers, publication dates and publishing units of these documents, and explain the sources where these documents can be obtained.
2 Project overview
2. 1 Work content
Briefly explain the main work to be done in the development of this project.
2.2 Main participants
Briefly describe the main personnel involved in the development of this project, including their technical level.
2.3 products
2.3. 1 program
List the name of the program to be handed over to the user, the programming language used and the media form of the stored program, and cite relevant documents to explain its functions and capabilities one by one.
document
List the name and content point of each file to be handed over to the user.
service
List the services provided to users, such as training, installation, maintenance and operation support. , and specify the start date, support level and service period item by item.
2.3.4 Non-transferred products
Explain that the development group should give products (documents and even some programs) to the unit rather than to the users.
2.4 acceptance criteria
For the above-mentioned products and services to be delivered, explain item by item or quote information to explain the acceptance criteria.
2.5 deadline for completing the project
2.6 Approver and approval date of this plan
3 implementation plan
3. 1 Work task decomposition and personnel division
The work to be completed in project development includes requirements analysis, design, implementation, testing and maintenance, including document preparation, approval, printing, distribution, user training, software installation, etc. , step by step decomposition, and indicate the person in charge and participants of each task.
3.2 Interface personnel
Explain the personnel responsible for interface work and their responsibilities, including:
A. personnel responsible for the interface between the project and users;
B. Responsible for the interface between this project and various management organizations of this unit, such as contract planning management department, finance department and quality management department;
C. Interface personnel responsible for this project and units responsible for each contract, etc.
3.3 progress
For requirements analysis, design, coding implementation, testing, handover, training and installation, the forecast of each task is given.
Set the start date, completion date and required resources, specify the completion order of each task and the landmark events (so-called "milestones") that represent the completion of each task.
3.4 Budget
List the required labor (including the number and time of personnel), budget and sources of funds (including office expenses, travel expenses, machine time expenses, information expenses, communication equipment and special equipment rent, etc.). ) item by item.
3.5 Key issues
List the key problems, technical difficulties and risks that can affect the success or failure of the whole project one by one, and point out the impact of these problems on the project.
4 support conditions
Explain the various conditions and facilities needed to support the development of this project.
4. 1 computer system support
List the computer system support needed in the development and operation process, including computers, peripherals, communication equipment, simulators, compiled (or assembled) programs, operating systems, data management packages, data storage capabilities and test support capabilities. , and give the requirements of delivery date and use time item by item.
4.2 Work undertaken by users
List the tasks and deadlines that users need to undertake one by one.
Include the conditions provided by the user and the providing time.
4.3 Conditions provided by other units
List the work to be undertaken by the contractor of the other unit and the completion time item by item, including the conditions and time to be provided by the other unit.
Five main points of special planning
Explain the main points of various special plans (such as subcontracting plan, developer training plan, test plan, safety plan, quality assurance plan, configuration management plan, user training plan, system installation plan, etc.). ) need to be formulated in the development of this project.
How to effectively plan application software development requirements document II
Efficient planning of application software development requirements documents needs to define the long-term development strategy of products, define the core functions of products, carefully analyze competing products, make front-end and back-end requirements documents, design UI, interact with each other, improve copywriting and complete high-assurance prototypes.
First, define the long-term development strategy of application software development.
To make a product, we need to clarify several questions first: Who are the users? What can users get from using the product? What do the company's products do? Only when these problems are clarified can the development direction be clear.
Second, define the core function of development.
Different products need different core functions, such as e-commerce APP, and planners need to clarify the core function requirements from both front-end and back-end aspects.
The main functions that need to be provided for users at the user end include: browsing goods, viewing goods by category, joining collections, joining shopping carts, buying directly, etc.
In the process of building the back-end system, different architectures need to be designed according to different e-commerce models. The main planning direction is whether the merchants operate by themselves or develop the joining mode.
The main architecture includes account architecture and functional architecture. The functions displayed by users in the front end need to be given corresponding fields and data interfaces in the background.
Third, application software development competitive product analysis
In addition to determining the requirements of core functions and polishing the details, what needs to be done next is a detailed analysis of competing products, such as e-commerce APP. It is necessary to find five products, which are downloaded for Android and IOS respectively, and analyze different products vertically and horizontally, including UI style, color, icon, text, button color, size and location. The advantages and disadvantages of its design are analyzed to provide necessary reference for its product design.
Fourth, make the requirement document.
When making requirements documents, we need to start from the front end and the back end. In this process, we need to consider the back-end architecture, the form of the interface, whether it is developed with H5 webpage or client.
Take UI design, interaction design, IOS development group, Android development group and background development group as examples to output product requirements documents.
Firstly, according to the defined functional blocks, draw the brain diagram of the whole application software front-end and the brain diagram of the background architecture;
Secondly, make a block diagram, which can be made mainly by software such as axure and sketch, and further list the function points, display forms and content examples;
Thirdly, the flow chart is listed, including nodes, judgments of different situations, processing methods, required copies, etc.
Description of the overall framework, tables and fields in the background, attributes of different roles needed, number of loading columns, overall process, etc.
Fourth, make a low-assurance prototype, work with the interaction designer to make a low-assurance prototype, and integrate the block diagram, brain diagram, flow chart and text description into a file;
Fifth, organize personnel from R&D, operations and other relevant departments to meet and review the requirements, follow the prototype, improve the details, and add text and picture descriptions?
Verb (abbreviation of verb) UI design and interaction design
After the delivery design and copywriting are confirmed, when the UI design interacts with the interaction designer, it is necessary to find relevant department personnel to improve the copywriting requirements, subdivide the work with the project manager, confirm the time node, and finally the interaction designer outputs a set of high-assurance prototypes.
Six, delivery of high assurance prototype
In this process, we need to pay attention to fully improve all the details, and have a clear design idea for the work requirements and workflow of design, interaction, R&D, operation, etc., including everyone's specific work and corresponding time nodes, and then the application software development team will implement it according to the specific requirements document.