About the development plan
1. The purpose of the software development plan.
The software development plan is to control the work schedule of the various development phases of the software. The software development plan is starting with a clear goal.
2. The basic elements developed by the software development plan.
Including the project name start time End Time Project Starting the Conditions and Completion Signs of the People's Project.
3. The requirements for the development plan of the software development plan.
(1) The development of software development plans should be reflected in the phased characteristics of software development.
(2) The development of software development plans should be reflected in the continuity characteristics of software development.
(3) The project can be divided into project overall planning and sub-item details.
(4) The project is extended or the project adjustment plan should be developed in advance, and the reason should be explained. The project adjustment plan starts from the current.
4. Software development plan check.
The project manager should check at least once a week on the software project development plan, and the project progress is reported to the leadership per week.
5. Software tools that develop project development plans.
Use MS Project.
6. Application Software Development Project should have a preliminary plan during project startup, and planned in the process of project progress. The general plan should include the following major and add deleted according to the actual situation. There must be a phased document for each goal, otherwise it is not finished.
(1) System feasibility analysis;
(2) System project;
(3) Demand analysis discussion and determination;
(4) System summary design;
(5) System detailed design;
(6) System programming;
(7) User manual, center maintenance manual system;
(8) Technical testing;
(9) User test;
(10) User training;
(11) The system is officially running;
(12) System acceptance.
Technical requirements for application development stage sex documents
One. Demand Analysis Document Technical Requirements
The writing of the demand analysis document should include the following:
1. The purpose of the project, expected results, and units of use.
2. Function Description:
(1) Functional division.
(2) Function Description.
3. A brief flow of data processing.
4. The screen format of the user input interface:
(1) including data items, data type, length
(2) Screen design.
5. Output interface:
(1) Picture output:
Screen design.
Query keyword.
Screen content.
(2) Report output:
The period of output is output.
Report format.
6. Calibration and standard:
(1) Calibration requirements.
(2) Quote standard.
7. Data estimation:
(1) Includes storage time periods.
(2) The amount of data of the unit cycle.
(3) Treatment requirements for overdue data.
8. If there is an inside and outside exchange, it should be clear: (1) The way the data is exchanged inside and outside.
(2) The frequency of the exchange.
(3) The amount of data / unit of the exchange is exchanged.
9. other requirements.
2. Document technical requirements for system profile design
1. Software and hardware environment for system development and operation
(1) System development environment
l hardware environment
l Supported operating system
l Network environment
l Use development language, tool, database
The software should describe the version of the clear use;
Hardware should specify space requirements, and if the server should be required to request the server's indicator.
(2) Requirements for environmental operations
Except for the development environment, external should be described:
1 Data space requirements, storage cycle
2 Data backup strategy (including software backup, data off site saving, backup cycle, backup media, backup is responsible for that part of the development department notifies backup, backup data inspection system, etc.)
3 system maintenance strategy after running
Software run error, and demand changes reporting process, software maintenance record and save method, software version management requirements
2. Detailed process description of system data
(1) Input Process Description
Describe the input stream with input, verification, operation, or processing, to describe the input stream, indicated by data flow graph
(2) Output process description
Describe the output stream with the requirements of the output requirements, data processing requirements, output to file or database.
3. Subsystem division
If the system is large, the system should be divided into a number of separate subsystems.
(1) Basic guidelines for subsystem division
(2) Basic function of each subsystem
(3) Processing flow of each subsystem
4. System agreement
(1) System naming standard
Includes: Subsystem, Program, Job Name, Module, File, Database, Field
(2) The code list (including reference to those systems) used)
(3) Management Measures for System Relations
5. System interface file description
(1) If the system consists of subsystem, the field of interface files should be described.
(2) If the interface, the number of interface files, the field of each file, the generated period, save, and backup recovery requirements, etc.
6. System test outline
(1) Test method
(2) Test content
l Describe the contents of the test, data preparation requirements, expected test results (correct or wrong)
l Data Preparation should include two major categories: correct and wrong
l Tested in terms of function or data processing.
(3) Test tool
three. Technical requirements for system detailed design
1. System data dictionary
Should include field name, attribute, length, field meaning (record with electronic data format)
2. Document design, database design
(1) Document list (2) List of database tables
(3) Detailed description of files and database tables
3. programming
(1) List of programs (units in child systems)
(2) Description, and function description of program input, processing, output
(3) Module and level map of program call
4. The design of the common module (module that needs to be called by more than two procedures)
(1) Module list (in system-based)
(2) The function of the module
(3) Ways and conditions called
(4) Return results called
(5) Basic algorithm of the module
(6) Module list of external systems
The result of the module name, system, call mode, condition, and return should be specified.
5. System error processing design
(1) An error list that needs to be restored
(2) After various errors, the steps of system recovery and the maximum possible analysis of data loss
(3) The flow of each resume process (in a detailed manner, the program is specified)
6. Design of system backup
(1) Software backup design
(2) Data backup design
(3) Software version management
7. System confidential design
(1) Secure measures taken by the system
(2) User rights management
(3) Software developers' authority management (refer to development and maintenance of two different working conditions)
four. Technical requirements for system technology test
1. Technical test introduction
(1) Test purpose, task, test content
(2) Participate in testers and time
(3) Test method, step
(4) The goal is expected to achieve
2. Test environment soft, hardware environment
(1) Hardware environment
(2) Supported operating system
(3) Network environment
(4) Development Tools, Language, Database
3. Preparation for test data
4. Technical test planning and results
Including tasks, purpose, tester, time schedule, completion time, test results
4. Test results analysis
Contrast and analysis with test outline
Project development summary document technical requirements
One. Project development overview.
1. Project development purposes
2. Requirements Confirmation: Overview The proposed process of proposal to the needs of the needs.
3. The environment developed by software.
4. The brief process of development.
5. Overview of project acceptance.
6. Delivery of the start date.
two. The main function of the project.
three. The main members of the project and their respective tasks are completed.
four. The actual effect analysis of project delivery use.
Fives. Value Analysis of Project Promotion Application.
six. Project maintenance contact personnel, communication address, telephone. Seven. The management of the user's permissions, contact personnel, communication address, telephone.
Approval procedure for authority.
Eight. System maintenance, the management system of the backup.
