Java project development process


Project development process

1. project

a. the planning stage

  • The draft plan project : should include a description of the product introduction, product goals and functions needed to develop the resources, development time;
  • Risk Management Plan : the factors that can go wrong or can not be determined now listed, and to develop appropriate solutions. Risk found sooner, the better for the project;
  • Software Development Plan : The purpose of the project is about to start resource reasonable, cost estimates, schedule. Software development project manager arranged according to plan resource requirements, tracking the progress of the project; the project team members understand their tasks, working hours and other activities according to rely on the software development plan. In addition, the software development plan should include acceptance criteria and acceptance of project tasks (including determining the need to develop test cases);
  • Structure and Definition of personnel with : a common organizational structure perpendicular art embodiment, three kinds of programs and a hybrid scheme level. Vertical program, each member will act as multiple roles, and the horizontal program, each member will act as one or two characters, rich novice and experienced personnel sucked hybrid solution integrated with each other. Specific programs should be selected based on the actual skills of the Company's personnel;
  • Process Control Plan : The aim is to collect all the information needed to properly execute the project plan, to monitor the progress of the project to guide and adjust the plan to ensure the project can be completed on time;

b. the requirements phase

  • Capture requirements : refers to multiple developers and users to communicate and reach an agreement, the function of the project to be achieved is described in detail;
  • Analysis of demand : the demand for access to information for analysis, and remove errors and make up, to ensure that the requirements document correctly reflect the user's real intentions, eventually transforming user demand for software requirements, software requirements specification form;?

2. Development

a. the development phase

i. Summary of design software

  • (1) functional requirements of the software architecture design, software architecture and determine the components of the preparation of structural design reporting system;
  • (2) an internal interface and data structure design, report the preparation of database design;
  • (3) writing software outline design specification;

ii. Software detailed design

  • (1) Summary of design by software manual to understand the structure of the software;
  • (2) determining the respective constituent units software, the detailed design of the interface module;
  • (3) a module internal data structure design;
  • (4) a module design internal algorithms, can be flowchart, pseudocode, and the like described in detail with particular requirements and implementation details of each step, writing software detailed design specification;

b. encoding stage

i. Write code

  • Developer detailed design specification based software to write code to implement a software configuration module and the internal data structures and algorithms, and to ensure that compile;

ii. Test Unit

  • After the code is written, the code unit testing and integration testing, record, find and fix software problems;

3. Test

a. the testing phase

  • The main question to verify the availability of output for a given input in accordance with a predetermined result, found that the actual production output software, systems or do not meet the definition of a local conflict. System testing process typically includes the development of system test plans, test design, test case development and testing, and finally to assess the testing activities and results;

b. acceptance stage

  • System acceptance stage is consistent with the customer to confirm the output of software and project requirements, to determine whether the end of the project, the project plan the next step, the final formation of project acceptance report;

4. Maintenance

  • Any software project are more or less there are some problems in the production process. In the system maintenance phase, should be carried out depending on the software running on software appropriate changes to meet the new requirements, such as running and correct errors found. At the same time, also need to write software problem reports and software modifications reporting;
Published 201 original articles · won praise 201 · Views 7072

Guess you like

Origin blog.csdn.net/Regino/article/details/104740470