Software Implementation Engineer Overview __ software Implementation Engineer Road

Overview of the overall software implementation process
I. Overview of software implementation
The software implementation personnel work content is the reasonable allocation company, the field resources, the formulation promotion plan and guarantees the implementation, strives for the cost saving and completes the project acceptance in the contract time scope. The specific work includes: Common operating system, application software and the company developed software installation, commissioning, maintenance, on-site software application training, assist project acceptance, the initial confirmation of the requirements and the project later maintenance.



Third, the system implementation process
3.1 Project Launch
Project launches include both internal and external launches. Internal start-up is the project manager, the implementation staff, the project leader, in the context of understanding the project signature, together to determine the overall project plan, as well as the project internal staff contact information. External start-up is the implementation of personnel, project managers, marketing staff to organize the user to launch the project meeting, the specific announcement of the project implementation plan milestones and the need for user coordination work.

Output Document:
"Project implementation Plan" internal contact person
Risk:
1, the system signs the background is not clear.
Solution: and project manager and sales confirmation signed the background, System Research mode.
Precautions:
1, the project launches the General Assembly, you must become the project formulation, but is not a participant.

Implementation cycle: 3 days
3.2 Demand and user confirmation
Implementation personnel in understanding the actual customer business situation, in accordance with the "Requirements Specification document" departments, modules to carry out the demand function confirmation and confirm the user (access to all sections of the user contact information).

Output Document:
"User Contact" "Demand Confirmation List"
Risk:
1, the user's vision and requirements of the document inconsistent
Solution: Strengthen user communication, guide users to the same as the existing products
2, the user does not cooperate
Solution: Find the project manager to coordinate
3. Temporary change of demand
Solution: Research plan with the user confirmed beforehand, and then according to the actual situation of the project flexible adjustment
Implementation cycle: 5 days
3.3 Environmental Preparedness and inspection
Prior to deploying the system, the implementation needs to check the onsite environment (database server, application server, and related domain name servers, storage devices), and have the deployment conditions to schedule the deployment.

Output Document:
"Implementation of the Environmental inspection form"
Risk:
Hardware device not properly in place
Solution: Contact the account owner as soon as possible to prepare the deployment environment
Implementation cycle: 2 days
3.4 Data collection
The implementation personnel collects the basic data required by the system and the data related to the user's business before the initial deployment.
Output Document:
System Installation Deployment Data list
Risk:
1, the user does not provide data in accordance with the required format
Workaround: First with the user to determine the dictionary code, in accordance with the corresponding dictionary code to provide data
Implementation cycle: 5 days
3.5 System Installation Deployment
With the hardware and software environment installed, the implementation personnel installs the JDK, the Web server, the database server, deploys the project, and ensures that the modules are functioning properly.
Output Document:
Installation of Deployment record list
Risk:
1. After the system is deployed, the module will not function properly.
Workaround: Strictly follow the configuration of the system deployment (specific installation deployment reference implementation technical knowledge documentation)
2, the system should be completed after the deployment of timely backup procedures
Implementation cycle: 2 days
3.6 Initialization and backup of data
After the system is installed and deployed, after the project owner audits (System readiness and integrity), the implementation personnel import the user-supplied underlying data and back up the database. (Import documents by reference to the implementation database)
Output Document:
The Import list of data
Risk:
1, the user does not complete the one-time full supply of data
Solution: Strengthen the user communication, let the user as far as possible to provide data,
2, the data initialization, the need for the overall database environment backup
3. When the data is imported, the data coding is consistent.
Implementation cycle: 3 days

3.7 System Inspection and confirmation
The implementation personnel verifies the installation and deployment of the system, carries out a summary test of each module of the system, checks the requirement manual for functional verification, and ensures that the system matches the requirement specification.
Output Document:
"System Checklist"
Risk:
1, after the deployment of the system and the requirements of the specification is inconsistent
Solution: Follow up the development status in time
Implementation cycle: 7 days
3.8 System Delivery Confirmation
The implementation personnel and each module user confirms the module function, the collation user opinion, and the user signs "The System function confirmation list" (according to the actual situation uses the whole confirmation or the module confirmation form).
Output Document:
"System function Confirmation List"
Risk:
1, the user confirmed the system function confirmation list, has not signed
Solution: Timely Contact the user for function confirmation, and sign
Implementation cycle: 5 days
3.9 Requirements Change
When the requirements of the user beyond the scope of the requirements specification, need to submit requirements change. And let the user sign the demand change list.
Output Document:
"Requirements Change List"
Risk:
1, the user does not change the cost pressure, change the demand at will;
Solution: Starting from the start of the project, awareness and the user to instill cost awareness;
2, and the user signed the confirmation, but the demand audit does not pass
Solution: Strengthen communication with Project manager, sales and users prior to changing requirements;
Implementation cycle: 3 days
3.10 User Training
The implementation personnel informs the user in advance the system training, and prepares the login system the account number, instructs the user how to use the system, and forms the training record form, simultaneously provides "the system Operation Manual".
Output Document:
"Training record Sheet"
Risk:
1, during the training, system error
Solution: Strengthen the system test before training, use the preset account to demo during training;
2, during the training, the user put forward new ideas
Solution: Communicate with Business Department before training to confirm the rules of dealing with the new ideas, and suggest to ensure the existing process to operate stably and avoid big adjustment and modification.
Precautions:
1, the use of the manual to the user point of view, and inform users how to enter the system
2, explain the use of the system involved in the business background, the implementation of training as a supplement, the main guidance system use;
Implementation cycle: 3 days

3.11 System test Run
After the system function is rectified and confirmed, completes the customer's training at the same time. We can find the pilot Department for the module Test run, and then carry out a comprehensive promotion
Output document: "System trial Run Application Form"
Risk:
1, through the trial run, resulting in new requirements change
Solution: Communicate with Business department, try to keep the original system running stably, avoid large process adjustment
Precautions:
1, completes the data and the procedure backup work
2, strengthen the business unit and pilot operating units of communication, collect pilot unit trial run during the problem, and timely adjustment of the system
Implementation cycle: 30 days
3.12 Project Acceptance
After the project trial run, the implementation personnel prepare to accept the related materials, after the project manager approves, and the user signs the project acceptance.

Output document: Prepare the appropriate document according to the user's requirements
Risk:
1, the acceptance of the material is not fully prepared
Solution: In strict accordance with the requirements of the user acceptance of the request to prepare the relevant documents
Precautions:
Implementation cycle: 5 days
3.13 Implementation Work Summary
The implementation staff summarizes the whole implementation process, and summarizes the problems encountered in the implementation process and the experience or suggestions.
Output Document:
"Implementation of the work summary"
Precautions:
1, need to listen to participate in the project members of the role of opinion
2, the summary of the implementation of the key to reflect the experience and lessons in the process


--------------------------------