Software implementation process (eight stages) - software implementation engineer

Preface

软件实施工程师

The work of the software implementation engineer is a decisive link in the main line of software product services. The success of software is inseparable from implementation. Mainly responsible for project implementation: including installation, debugging, and maintenance of commonly used operating systems, application software, and software developed by the company, as well as a small amount of hardware and network work; Responsible for on-site training: On-site software application training; Assisting in project acceptance; Responsible for requirements Preliminary confirmation; control project progress; communicate with customers about individual needs; responsible for project maintenance.

软件产品

Software products, especially industry solution software products, are different from general commodities. After the user purchases the software product, it cannot be used immediately. It requires technical personnel from the software company to conduct research on software technology, software functions, software operations, etc. We call this series of work software project implementation, including system debugging, software function implementation, personnel training, software online use, and post-maintenance. A large number of software company project implementation cases prove that whether the software project is successful, whether the user's software usage is smooth, and whether the user's work efficiency and management level are improved, not only depends on the quality of the software product itself, but also the quality effect of the software project implementation. Later user application conditions play a very important impact. The project implementation specifications mainly include 项目启动阶段、需求调研确认阶段、软件功能实现确认阶段、数据标准化初装阶段、系统培训阶段、系统安装测试及试运行阶段、总体验收阶段、系统交接阶段 and other eight stages of work content. Each stage has different work items. There is a link between each stage. The successful completion of the previous stage is to ensure the next The basis for carrying out the work in each stage. Each project implementation stage will be introduced below.

1. Project startup stage

This stage is at the earliest stage of the entire project implementation and consists of four stages: establishment of the project team, preliminary research, preparation of the overall project plan, and kick-off meeting. Main tasks at this stage:

1.公司：After the contract is signed, a project manager is designated, a project team is established, and the project organization is authorized to complete the project goals.

2.公司项目组： Conduct preliminary project research, establish a project implementation organization with users, prepare an "Overall Project Plan", and hold a project kick-off meeting.

3.商务经理： Cooperate with the company’s project team and transfer accumulated project and user information to the project team. Formally introduce the project team to users and cooperate with the project team to establish contact with users.

4.用户： Establish a project implementation organization, cooperate with preliminary research and hold a kick-off meeting, and sign the "Overall Project Plan" and "Project Implementation Agreement".

成立项目组：

After receiving the implementation application, the department manager appoints a project manager and specifies the project goals. The department manager and the project manager jointly designate the project team members and their tasks, and report it to the general manager to sign the "Project Mission Statement".

前期调研：

The project manager and project team members, with the cooperation of business personnel, establish contact with users and conduct research on contracts and users. Fill out the "User and Contract Information Form". During project business negotiations, the business manager has accumulated a large amount of information. The project team should first collect business and contract information, and work with the business manager to identify those individuals and organizations that are project stakeholders, determine their needs and expectations, and how to meet them. Influence these needs and expectations to ensure project success.

编制《项目总体计划》：

The "Project Master Plan" is a document or a collection of documents that will be constantly changed as project information continues to enrich and change. It mainly introduces project goals, major project stages, milestones, and deliverables. It usually includes the following aspects: project description, communication management plan, determining the information and communication needs of project stakeholders: that is, who needs what information when and how to provide the information to them. A quality management plan that determines the quality standards appropriate to the project and how to meet their requirements. Each of the above plans can be included if necessary, with the level of detail required based on the requirements of each specific project. Resolve issues and pending decisions.

启动会：

A meeting held by the project team and users to announce the official start of project implementation. The agenda of the meeting is as follows: jointly establish a project implementation organization and implement the rights and responsibilities of the organization; both parties sign the "Project Implementation Agreement". The project team introduces the "Project Master Plan" and "Project Implementation Agreement", including the following: project objectives, main project stages, milestones, and deliverables. The planned distribution of responsibilities (including users); the necessity of project management during project implementation and how to conduct project management, and how to control the quality of the project; the important role of user participation and leadership support in project implementation; stage acceptance and technical handover And how to provide follow-up services to users after the project is completed.

2. Demand research and confirmation stage

The main work at this stage is for the project implementation staff of the software company to investigate users' needs for the system, including management process research, functional demand research, report requirement research, query demand research, etc. After the implementation staff completes the survey, they will compile a "Requirements Survey" Analysis Manual" and deliver it to the user for confirmation. After the user confirms the requirements mentioned in the "Requirements Research Analysis Manual", the project implementation personnel will use this as a basis to implement the software functions. If the user puts forward new requirements, the implementer will analyze the difficulty of the requirement and its impact on the entire system to determine whether to implement it. The demand research stage specifically includes the following contents:

1. Prepare for demand research

   Requirements research is the beginning stage of system development for an application software development. Its output "software requirements analysis report" is the input of the design phase. The quality of requirements research is an extremely important stage for an application software. , its quality determines the delivery results of a software to a certain extent. How to listen to and analyze user needs from customers has become the most important task for researchers.

2. Prepare "Demand Research Plan"

   Whether the internal review passes the "Requirements Research Plan"

   The project team, department managers, business and other personnel will review the draft of the "Requirements Research Plan" based on the contract requirements and the actual situation of the project. If it passes the review, it will be signed at a later time. If it does not pass the review, it will be revised again.

   Whether the user signs the "Demand Research Plan"

   If the user signs the "Demand Research Plan", it will serve as a guide for future demand research work. Otherwise revise again.

3. Is there any change in the "Demand Survey Plan"?

   If there are changes to the plan, the change control process is executed, otherwise follow-up work is carried out as planned.

4. Prepare and issue "Demand Survey Notice"

   The project team prepares a "Demand Survey Notice", determines the relevant matters for conducting the demand survey, and sends it to users to prepare for the successful completion of the demand survey.

5. requesting research

   Based on the "Demand Research Manual", the project team conducted in-depth and comprehensive research on business processes, document usage, printing formats, and report queries, and collected users' personalized needs.

6. Demand research and analysis based on the results of the survey

   The project team and other technical departments of the company will conduct further analysis to determine reasonable and feasible requirements, and formulate the analysis results into a draft "Requirements Analysis Report".

   Whether the internal review passes the "Requirements Analysis Report"

   The project team, department managers, and personnel from other technical departments of the company will review the draft of the "Requirements Analysis Report". If it passes the review, it will be signed by the user later. If it does not pass the review, it will be revised again until it passes the internal review.

   Prepare and issue the "Requirements Analysis Report Confirmation Notice"

   The project team prepares the "Requirements Analysis Report Confirmation Notice" and sends it to users to determine the relevant matters for demand confirmation, inform relevant departments and personnel to arrange the work, and participate in the demand confirmation work on time to prepare for the successful completion of the demand confirmation work.

   Whether the user confirms the "Requirements Analysis Report"

   If the user confirms and signs the "Requirements Analysis Report", the demand research phase is over and the subsequent software function implementation work will be carried out; if not confirmed, further research and analysis will be carried out until the user finally confirms and signs the "Requirements Analysis Report" 》. Both parties signed the "Requirements Analysis Report". After the demand research work is completed, if the user proposes new requirements or changes existing requirements, the process of adding new requirements and changing requirements will be implemented.

3. Software function implementation confirmation stage

The main work at this stage is for project implementers to implement specific software functions based on the user needs in the "Requirements Research Analysis Manual" confirmed during the needs research stage. In the process of realizing the software functions, the project implementation personnel will record the detailed process of software implementation. Convenient for the company’s after-sales service. Each implementation technician must record and archive in strict accordance with the requirements. After all functions according to the survey requirements are implemented, the project implementation personnel will prepare a "Software Function Confirmation Form" and customize the software functions for user confirmation. The user will determine whether the software functions meet the requirements one by one based on the functions on the "Software Function Confirmation Form". For functions that do not meet the requirements, the project implementation personnel will record them and modify the functions until the user requirements are met.

4. Initial installation stage of data standardization

The main work at this stage is for the project implementation personnel to guide users in the preparation of system standardization data, and to provide users with software operation training for initial installation of data, so that users can enter standard data into the system in a timely manner. After the initial installation is completed, project implementation personnel The initial installation of data will be checked to lay the foundation for the development of specific business functions in the future.

5. System training stage

The system training phase is a relatively important task in the entire project implementation. Whether the user is proficient in the operating functions of the software will directly affect the subsequent software application effects, so both the software company and the user must pay enough attention to this phase of the work. We must fully understand the importance and arduousness of training. It is very necessary to conduct systematic and standardized product training for users' relevant personnel before the project is implemented, so that users can understand the software products and ultimately be able to solve specific problems during use.

In this stage of training, the personnel who participate in product training for users are divided into three levels:决策层、技术层、操作层. The training contents for personnel who participate in product training for users at different levels are:< /span>

Decision-making level: the role and importance of leadership in implementation, decision-making inquiry.

Maintenance layer: system maintenance knowledge and operation methods.

Operation layer: operation method.

具体的培训工作流程为：

1. 调研培训信息：Three days before the start of the training, the person in charge of user implementation will fill in the "Trained Department Summary Table" and "Trained Personnel Status List" with the departments and personnel participating in the training.
2. 编制培训计划：Based on the survey results, discuss the specific training content, time, venue, personnel, etc. with the person in charge of user implementation. The project team prepares a "Training Plan".
3. 签署培训计划：Users sign the "Training Plan" to further confirm the training arrangements.
4. 发培训通知：Two days before the start of the training, the user implementation manager will be notified of the training content, time, venue, personnel and other information in accordance with the signed "Training Plan".
5. 搭建培训环境：Before the training begins, the company's project team will set up and check the training environment properly, and prepare the training outline and training manual.
6. 组织培训：The person in charge of training of the company's project team and the person in charge of user implementation organize relevant personnel to participate in training, and strictly assess according to the training system. The user will fill in the attendance information into the "Trainer Sign-in Form".
7. 培训考核：The person in charge of training of the company's project team and the person in charge of user implementation organize the trainees to participate in computer and theoretical examinations.
8. 培训总结：The person in charge of training of the company's project team and the person in charge of user implementation will summarize the attendance and assessment status, fill in the "Training and Assessment Statistics Form", and report to the relevant person in charge in a timely manner.

6. System installation, testing and trial operation stage

The main work at this stage is to test the user network and hardware equipment in the user's real environment, and conduct capacity and performance pressure tests on the software system. The purpose of testing and trial operation is to ensure that all functions of the system can be used normally and meet the requirements described in the "Requirements Analysis Report" signed by the user, and to discover and correct as many potential problems as possible before official operation; at the same time, the purpose It also depends on the user's relevant personnel to further improve their operating level and master the operating specifications before official operation. The main work contents of this stage are:

1. 编制计划：Discuss with the person in charge of user implementation the specific testing and trial operation time, location, personnel and other arrangements, and the project team prepares a "Testing and Trial Operation Plan".
2. 签署计划：Users sign the "Testing and Trial Operation Plan" to further confirm the testing and trial operation arrangements.
3. 发测试及试运行通知：1. Two days before the start of testing and trial operation, notify the user implementation person in charge of the time, location, personnel and other information in accordance with the signed "Test and Trial Operation Plan". 2. Set up environment and prepare data. 3. Before the trial operation begins, set up the software environment, hardware environment, network environment, and adjust the lines; check whether there are any problems in the software, hardware, network, lines, etc.;
4. 组织测试及试运行：User-related leaders at all levels will provide full cooperation and organize relevant personnel to conduct testing and trial operations. The company's project team is responsible for commanding, checking the user's personnel organization and providing guidance, and tracking and checking the following situations: Tracking document circulation status. Track new information login sessions. Observe the execution status of business processes. Observe the operator's performance. Observe the system running speed and abnormal performance. Observe the correctness of key data. Correct incorrect operations in a timely manner, communicate with relevant personnel in a timely manner for new problems, and determine solutions.
5. 测试及试运行总结：After the test and trial operation are completed, summarize the operation of the equipment and software during the trial operation, summarize the business processes and operating links during the trial operation, and notify the relevant person in charge of the test and trial operation results in the form of a written summary.

7. Overall acceptance stage

This stage is to accept the overall completion of the project. The acceptance is carried out in stages. At the end of each project stage, the user will accept the deliverables of this stage. After the test and trial operation are completed, the system will be generally accepted.

需要验收的可交付成果：

8. System handover stage

This stage is the last stage of project implementation. The main task is that the software company project team hands over the software project to the user, including software products and various documents generated during the project implementation process, and signs the "After-sales Service Agreement". The project will enter after-sales service stage. The software company project team also needs to ask users to fill in the "User Satisfaction Survey Form" to evaluate the entire project implementation of the software company's project implementers. The software company will listen to the users' opinions and strengthen and improve it in future project implementation management. .

Summarize

项目实施规范主要包括以下八个阶段

1. Project start-up stage
2. Demand research and confirmation stage
3. Software function implementation confirmation stage
4. Data standardization initial installation stage
5. System training stage
6. System installation, testing and trial operation phase
7. Overall acceptance stage
8. System handover phase