1. The goal of project development, meaning
1. The goal of this product
2. Project Description
Project code
2. Personnel configuration (project manager, system analyst, software engineer, tester, art document administrator)
3. Responsibilities of various roles
1. Project Manager (1): Responsible for schedule plan, formulate workflow, coordinate various roles, formulate work objectives and plans, report to the project supervisor, inspiring, employee recruitment
2. System Analyst (1): Responsible for customer communication, demand research, analysis requirements, design report, development plan during the development stage, formulate test plan, establish test plan, new developer training
3. Software Engineer (3): Responsible for the development, unit test, and assist in the development plan based on demand report
4. Tester (1): Responsible to assist in developing test plans, module testing, integration testing
5. Artist document administrator (1): Responsible for the system's art, the management of the project, the VSS maintenance, the method of use of BBS and BUG and Project tools, daily build, new employee tool training
3. Overall project
1. Project demand research, analysis
Widely investigate customer needs, analyze system auxiliary users
Write << Requirements Analysis Manual >>, establish a business model of various business models, consider system support methods in various business models.
2. Project technology framework ready
The development training instructions of the new framework is organized, and the development specification is developed. << Development Technology Framework >> << Programming Specification >>
The overall style of the project, interface design. << Software artist description >>
3. Project summary design, detailed design (loop)
Summary design: System module division, system naming specification, establish core entity model, core object status model, module, and object collaborative model. << Profile Design Manual >>
Detailed Design: The prototype of each page, each page provides the function, the key field of each page (interface prototype, first); build detailed program interface, establish a related object and attributes and methods, establish a module sequence Fig. << Module Design Manual >>, << Database Manual >>.
4. Project development, unit test
Developers must write code based on project design and must be tested after each function is completed, and ensure that the code is 100% overwritten. Fill in << Unit Test Report >>
5. Project integration, system testing phase, write using documents.
Developers write installed installations, testers test the process of various business models based on project objectives, and document administrators write usage. Project Manager contact the Sales Department to organize product packaging, publicity.
4. Detailed flow chart
Periodic role responsibility
2.BUG management mechanism:
5. Detailed plan for each phase of the project
6. Project test overall plan
7. Detailed test plan for each phase of the project
8. About project risks
1. Design from the customer's demand, does not have operability
2. The system is not friendly interface
3. Poor quality
4. Cost uncontrollable
5. Project lack of management
6. Typical error
7. Employee participation is low
9. Project cost
10. Project performance
