In order to strengthen the work management of the company's software R & D department, shorten the development cycle, improve the quality of software development, reduce development costs, and improve development efficiency, the management system of the software R & D department is specially formulated.
Chapter One, General
In order to ensure the normal and orderly execution of daily work and make all links in the development more compact and more controllable, it is necessary to formalize the project management of the software R & D department as much as possible and the work process to be streamlined in order to improve the quality of software and development efficiency The target that the project can be delivered on schedule according to quality and quantity.
1. Software development generally follows the basic principles of project management and software engineering.
2. Project management involves project establishment, project planning and monitoring, and configuration management.
3. Software engineering involves requirements analysis, system design, software implementation, system testing, user testing, trial operation, system acceptance, system on-line and data migration, and product maintenance.
Chapter II, Stage Results
According to the process theory of software engineering and the current actual situation of the company, the following work flow is formulated, and the deliverables to be submitted for each important link are specified.
1. Project establishment: market demand analysis (or contract), project establishment application form, and project risk analysis list.
2. Requirements analysis: software requirements report or design plan, requirements specifications.
3. Overall design: summary design specification or functional module description.
4. Detailed design: detailed design specification, including software interface description and unit test plan.
5. Software implementation: software function description, source code, source code description or notes
6. Product testing: test report
7. Product release: product manual, user manual
8. Product maintenance: problem feedback record
9. Project summary: Submit the project summary of the client and the PPT of the company's project report
Software process results table:
| stage |
Form a document |
Description of responsibilities and documentation |
principal |
Remarks |
| Demand stage |
Project Initiation Report (Word) |
Clarify the responsibilities and obligations of both parties |
project manager |
Most business modeling and requirements, a small part of analysis and design |
| Business Requirements Specification (Word) |
Definition of requirements, elaboration of business scope and content, development team is responsible for formulating optimal technical design plan |
Project manager / demand analysis engineer |
||
| Project Development Plan (Project) |
Formulate a project development plan so that all project stakeholders can timely understand the project progress |
project manager |
||
| Project Risk Analysis Checklist (xls) |
Analyze the risks that will occur in the project and formulate corresponding measures |
All stakeholders |
||
| design phase |
Business process overall design book, detailed design specification (Word / Visio) |
Discuss the technical architecture of the project and possible technical difficulties, sort out business processes, unify development rules and styles, etc. |
Project manager / architect |
Most of the analysis and design, part of the implementation of programming and testing, began to consider deployment |
| Database relation design drawing, flow chart (PowerDesigner) |
Structure diagram and flow chart of the database required for the project |
Architect / Senior Software Engineer |
||
| Task Assignment Document (Word) |
Clarify the development tasks and responsibilities of each team member |
project manager |
||
| Problem Description Report (Word) |
Let users, leaders and team members understand and discover problems in a timely manner |
project manager |
||
| Business Change Document (Word) |
Record the changes in business requirements raised by users during the development process |
Demand analysis engineer |
||
| Implementation phase |
Software function description (Word) |
Record all software functions implemented in the software development process |
Software Development Engineer |
Final software development product and description |
| Source code |
Achievements that can be deployed, as well as source code and database backup files that generate the achievements |
Software Development Engineer |
||
| Source code description (Word) |
Explain each module of the submitted source code |
Software Development Engineer |
||
| Test phase |
Project test plan and report (Word) |
Record the method of project testing, verify the system function and performance records |
Test Engineer |
Repeat the test until the system is stable |
| User Manual (Word) |
Instructions for users to use the software |
Test Engineer |
||
| Go online and run |
System usage report |
Operation record after system deployment |
project manager |
Deployment and maintenance |
| User training report |
User training documentation |
project manager |
||
| Project Acceptance Report (Word) |
Record the acceptance report signed by both parties |
project manager |
||
| Project summary report |
The project team summarizes the experience and deficiencies through this project |
project manager |
Chapter III, Job Setup
According to the company's current development process, it is mainly divided into three stages: analysis, development, and testing. The analysis stage completes the writing of user requirements documents and the overall design of the system; the development stage completes the writing of design documents, code writing, and code maintenance. Complete the system test, test documents and other materials in the test phase. By gradually adjusting positions, clarifying job responsibilities, and gradually realizing the post settings of project manager, demand analysis engineer, senior software development engineer, software development engineer, and test engineer
| post |
Work content |
responsibility |
| project manager |
1. Select members of the project team, set up a project team, and arrange tasks. 2. Communicate and coordinate with customers (in terms of business requirements or non-business requirements), as well as demand research. 3. Formulate project development plans, including requirements, design, coding, and testing of these stages. 4. Estimated project development costs. 5. Develop a team development schedule and monitor the work progress of the team members. 6. Check and check the quality of the documents. 7. Guide the work of the members of the group. 8. Hold regular project meetings to control project risks and progress. |
1. Responsible for customer communication and coordination. 2. Responsible for software development efficiency, quality and cost. 3. Responsible for the quality of overall system design and detailed design documents. 4. Responsible for the progress, quality, cost and risk of the entire project. |
| demand analysis engineer |
1. Communicate with customers, be responsible for demand research, summarize demand analysis documents, and write the overall system design plan. 2. When meeting the demand change, analyze the content of the demand change, and be responsible for evaluating the demand change together with the project manager. 3. Compile detailed design documents with senior software development engineers.
|
1. Responsible for the quality of user needs analysis. 2. Responsible for all members of the project team to correctly understand the project requirements. |
| Advanced software Development Engineer |
1. Responsible for system module design, detailed design documents. 2. Draw the interface prototype demo, etc., the specific description of the use of design functions, actors, preconditions, postconditions, UI descriptions, business processes / subprocesses / branch processes, interface descriptions, etc., complete most of the front-end design, small Part of the back-end design. 3. Responsible for the preparation and maintenance of the code of the technically difficult module or the common module code. 4. Responsible for the detailed design and coding of the module. 5. Provide technical guidance to the team members. |
1. Responsible for the development efficiency of the people in the group. 2. Responsible for the overall style of the product. 3. Responsible for the overall design process of the project. 4. Responsible for the development efficiency and quality of your own modules. |
| Software Development Engineer |
1. Communicate with the project manager and confirm the needs and implementation methods of a certain module. 2. Responsible for writing and maintaining the code of a certain module. 3. Maintain the code of other modules. 4. Responsible for interacting with testers and handling testers' problems. |
1. Responsible for the development efficiency and quality of your own modules. |
| Test Engineer |
1. According to user needs analysis and overall system design, write test documents and test cases. 2. Test the function, performance and abnormality of the system. 3. Write test documents and operation instruction manuals. |
1. Responsible for the quality of the test. 2. Responsible for the quality of test documents and operation manuals. |
Chapter IV, Project Establishment
1. The demand analysis engineer conducts application survey and analysis to confirm the application requirements of the software.
2. To establish a project review meeting, the development director, department manager and designated personnel must participate. Conduct feasible ××× for the project, prepare project proposals, evaluate the difficulty and workload of the project, and form a feasible ××× report.
3. Set up a project development team according to the pros and cons of the project configuration, formulate a software development plan, determine the project manager, and the department and project manager jointly determine the specific project configuration, knowledge and skills requirements, team members and team roles.
Chapter V, Project Planning and Monitoring
1、以项目为单位，项目经理负责整个项目的计划、组织和控制。
2、在整个项目过程中，项目经理定期检查项目进度和完成情况，调整人员分工和安排。
3、项目计划需要变更时，需要明确变更内容并及时汇报。项目经理需要说明客户变更原因并将变更说明提交公司领导审核，以便根据变更内容及时调整计划。。
第六章、需求分析
1、对用户提出的需求进行分析汇总，梳理用户的业务流程和详细的功能定义。
2、做出简单的界面原型，与客户进行有效的沟通， 编写需求详细说明书。
3、根据现有条件进行估计，制定项目进度，制定详细的软件开发计划。
第七章、总体设计
1、在该阶段确定总体结构和软件开发架构，文件命名规范，编码规范。可按软件需求划分成子系统，也可直接定义目标系统的功能模块及各个功能模块的关系。
3、确定软件模块结构，给出每个功能模块的功能描述、数据接口描述，并完成系统概要设计说明书。
4、完成数据库的设计，并编写数据库设计说明书。
5、完成的文档需提交公司进行归档管理。
第八章、详细设计
1、调整前一步设计的不足，确认各模块之间的详细接口信息。
2、设计功能使用的具体描述、行为者、前置条件、后置条件、UI描述、业务流程/子流程/分支流程，界面说明等。
3、确定模块内的数据流或控制流，对每个程序模块必须确定所有输入、输出和处理功能。
4、汇总并提交所有相关文档，审核确认质量和进度。
第九章、软件实现
1、项目组根据概要设计说明书、详细设计说明书制定系统实现计划
2、有条件的情况下保证开发、测试和生产环境独立。选择软件工具，明确项目成员的职责分工，按照编码规范和详细设计实现软件功能。
3、代码应满足结构良好，清晰易读，且与设计一致，符合编码规范。
4、开发人员需要软件实现过程中编写软件功能说明，源代码说明。软件功能说明文档应说明项目名称、编号、软件名称和版本号，软件功能、主要功能实现过程。源代码说明应说明项目编号、源代码类名称、编写人员、编写日期、变更履历、功能、全局变量、数据库字典、函数功能、接口。该文档包含在源代码文件中，以注释形式存在。
5、项目组进行单元测试和集成测试。开发人员处理测试人员反馈的测试问题，并以书面形式反馈主要问题及解决办法，直至系统运行稳定。
6、汇总并提交所有相关文档，提交公司备案，形成项目知识库。
第十章、软件测试
1、根据单据测试和集成测试两个过程，制定测试计划。按阶段设计测试实例，并将测试结果记录，未通过的的反馈给开发人员调整。
2、完成测试文档、操作手册、安装维护手册的编写。
第十一章、用户培训
1、准备用户培训计划、培训手册
2、确定培训时间、培训地点，向用户进行系统使用培训、操作指导及提供软件操作手册。
3、保留培训签到表，用户意见等存档。
第十二章、系统上线
1、 制定上线计划，确定上线工作时间表，部署的环境。
2、上线操作步骤以及问题处理步骤；
3、根据软件特点、客户需求进行软件部署，并记录软件部署和运行结果；
4、项目组根据系统运行请款对系统进行优化，记录系统的运行情况、系统问题和处理后的版本。
第十三章、系统验收
1、验收工作准备，按要求整理项目成果物，打印装订成册，并提交客户方。
2、系统主要使用部门及信息技术部门联合成立项目验收小组，从需求功能及技术需求层面对系统进行综合评估和项目成果物的审核，根据验收情况形成系统验收报告
3、应用部门及信息技术部门负责人根据系统试运行情况签署验收意见。
第十四章、产品维护
1、调出项目主要开发人员，按照合同要求安排维护人员对系统进行技术支持。
2、系统需求变更或调整，记录变更原因和软件及源代码的版本控制，按照软件变更要求对系统进行维护。
第章十五、源码和文档
1、源代码/文档管理采用版本控制软件VisualSourceSafe。
2、按项目的阶段性完成源代码、文档的上传。项目负责人每天对代码进行检查，开发总监或部门经理定期进行抽查。
3、文档分为项目文档和个人文档，文档上传前进行归类和汇总。
第十六章、质量检查
1、项目负责人每天要检查成员的工作完成情况，特别是新员工的工作进展；
2、工作抽查制度：不定期的进行抽检，并将检查对象、检查时间、检查内容、检查结果反馈给被抽检人。
3、内部审核制度：针对业务需求、概要设计(功能界面、数据库)或疑难问题组织评审会，提出意见或解决方案。
第十七章、文档规范
1、需按照软件实施的阶段落实成果物，参照《软件过程提交成果表》。
2、如果客户有特殊要求，请按照客户要求的规范完成。并将最终的问题提交公司归档备份。
第十八章、软件变更
为规范软件变更与维护管理，特制定本制度。本制度适用于应用系统开发完毕并正式上线，移交给客户方之后的运行支持及系统变更工作。
1、系统变更工作可分为功能完善维护、系统缺陷修改、统计报表生成。
2、需求部门提出系统变更需求，项目经理同开发人员一起根据重要性和紧迫性做判断，确定其优先级和影响程度，并进行相应处理，同时将变更需求整理成系统变更申请表。
3、系统变更实现过程按照软件开发过程规定进行，遵循软件开发过程统一的编码标准和版本控制，并经过测试通过才能完成部署和上线。
4、在系统变更完成后，开发人员需将系统变更表的执行结果提交给项目经理，测试人员确认执行结果后，项目经理与需求提出方确认签字后，提交至公司进行归档管理。