What is software development and implementation?

Question 1: What is the specific work of software implementation? Implementation engineers mainly install and debug software for customers at the software work site, train customers, organize completion acceptance and travel frequently.

Question 2: Software implementation or software development? Personal advice, since you feel that your "communication skills and affinity are not particularly good", why do you have to implement it? The technical difficulty of realization is certainly not as great as that of development. The main purpose of the implementation is to communicate with software users and help them use it normally. Of course, technical difficulty is nothing, the key is to exercise people's ability to do things. And development, that is, working on a machine, is relatively boring, but it can improve a person's internal strength. If you develop strongly, it is very easy to implement it in time. But if it is realized first, it will be difficult to do development in a few years.

Personal opinion, for reference only!

Question 3: What does a software project implementation engineer do? It is accounting, statistics, classification, negotiation and consultation. Just like the foreign minister's job, it is to break down the project tasks, organize and coordinate all aspects of resources, manpower and material resources, and complete all project tasks as planned.

I wonder if you will come to see it.

The implementation work is hard, and the so-called hard work is different from the hard work of programmers.

There is also the need for patience and familiarity with related products.

There is also the need to understand the relevant technology, not necessarily proficient.

Another estimate is a business trip.

... between R&D and the sales department.

Help customers install the software developed by the company correctly and listen to their suggestions.

Sometimes, I have to help with some tests. (Our company is like this) You need to know the installation of related software and hardware, be able to modify the database under the guidance, be familiar with the advantages and disadvantages of the installed software, and it is best to perform some minor operations on it. The other filebat(Mark) is right.

Question 4: What is the difference between software development and software implementation? Software development means that programmers develop a program from scratch, and the concept of software implementation is relatively broad. Some companies may just install training, and some companies need to implement some simple secondary development.

The former requires higher programming language, while the latter requires higher software application industry.

Question 5: What industry do software implementation engineers belong to? IT, all in the computer industry.

Question 6: What problems should be paid attention to in software implementation? Hello, software implementation is actually not an easy task. It may be a challenge, and it requires the confidence and courage to "know that there are tigers in the mountains and favor the tiger mountain trip". Why do you say that?

Because software realization can be said to be the decisive link in the main line of software product service, the success of software cannot be separated from realization. So what is the realization of success? I think it is to let users really use it and make users satisfied. The success of users is also the success of software companies. However, actually using the software is not as easy as you think. For the unsuccessful implementation, through some reports and my investigation in southern Shanxi, it often happens and the proportion is very high.

In view of the importance and difficulty of the above implementation, our implementation is no longer simple installation and debugging, user training, initialization, trial operation support and so on. Because, in the process of implementation, various problems will be encountered, and different customers may encounter different problems. Our software is like a daughter-in-law meeting her in-laws, who are always critical and always say that you are not good at this or that. But although my in-laws are very picky, we can still meet! As the saying goes, "an ugly daughter-in-law can see her in-laws"? Besides, we're not that ugly. This is about how to look at the process. In fact, for a software, the initial problems are caused like this. At the beginning, marketers went out and tried their best to instill good and attractive things into customers. If one or two bugs suddenly pop up in the presentation, I believe that the salesperson can always calmly save the day before the customer reacts. Salespeople always promise good functions, performance and quality, which has aroused great interest from customers. If all goes well, the manager can sign the purchase and service contract soon, so the most important thing seems to be the same for the software company. Then, the software company sends implementers to the customer site for installation and demonstration. Please note that this is the most vulnerable time of the product. The implementer brings the whole set of products to customers, and finally, the ugly daughter-in-law has to unveil the veil for her in-laws. There are so many problems at this time that people are at a loss for a while. Therefore, even if there are many problems, we need to solve them one by one. This requires our technical service personnel to have the following qualities in order to cope freely and satisfy customers.

First of all, the implementer should have the basic ability of network diagnosis and analysis, and at least make a more correct judgment on the problem. Because there may be many unexpected problems during the installation process. For example, the server and network environment are much worse than expected, which conflicts with other application software and even with anti-virus software. For the problems caused by insufficient machine configuration, you can make a list and give it to the customer responsible person for decision.

Secondly, there should be corresponding solutions to different problems. Sometimes the running speed of our client software is really embarrassing, and sometimes it takes a long time for users to log in, which leads to the customer's first impression of the software is slow. Even low-level errors such as timeout will pop up. For such a problem, we should start from two aspects, that is, we should pay attention to the factors of the customer's hardware environment and explain it clearly to the customer. It is also necessary to judge whether there are related problems in software products. Of course, we just need to know this in our hearts and don't let our customers know. We should feed it back to the company to improve it.

In addition, we should learn to associate with customer leaders, and leaders are leaders, which is different from ordinary employees. First of all, the leader has no patience to look at the specific functions of our software, but needs to hear or see a very general display, then we should do what he likes. Perhaps, we often can't answer some questions from the leaders. For such a problem, we must first understand the real intention of the leader, which is also an important source of software requirements. The use of software is nothing more than strengthening management of leaders. When the software is not used, many data of the leaders may not be known. When the employee's work data is integrated into the software, it should be of great help to the leaders. Other countermeasures include: let the bottom employees say yes to our software. Obviously, leaders are more willing to trust the judgment of their own units. In addition, our other answer can be that the software will gradually improve after use.

It is not enough to learn to communicate with customer leaders. The most important thing is to have a good relationship with customers and employees. As mentioned earlier, leaders are more willing to trust their own judgment. Some users may not cooperate from the beginning of installation. In the training course, most of the staff who may come will be interested in the software. There is a simple reason. The use of software increased their workload. China is a society ruled by man, and its management is vague and inaccurate. Strict management of employees makes them unaccustomed. And people are somewhat inert in nature. Therefore, it is conceivable that ... >>

Question 7: Which is easier, software development or software implementation? Obviously, software implementation!

Of course, this result is based on the question you asked.

Reason:

You ask this question, obviously you don't know what is software development and what is software implementation. Or you are very vague about their specific job responsibilities. So, you don't learn computer, even if you are not a computer semi-irrigation! So, it's like a child learning to speak to code. It will take two or three years to get it. Software implementation is different. The software has been completed. You just need to deploy or install some software, learn to use it, and then teach users what you have learned. Relatively speaking, the latter is closer to life and your reality!

Question 8: What is the job of a software implementation engineer? Generally speaking, he does technical support for software, including installation, training and maintenance, and some of them have to do some code writing. This kind of work deals with customers more, which is suitable for developing technical sales types in the future. If you have been doing software implementation, unless your company's business is very good and you attach great importance to your department, there will be no good future. Of course, you can also develop in the direction of software development, but I'm afraid you don't have the time and opportunity to develop.

Supplement: there is nothing to be detailed, just a few points: first, I know programming and have some experience in program development; 2. Skilled computer operation, able to solve customers' trivial problems; Third, familiar with network configuration (generally, the company software is B/S or C/S structure); Fourth, it is best to have customer service experience and be good at communication. Generally speaking, these are the items, depending on the requirements of the recruiting company.

Question 9: What is the daily work of the project manager of software development? Collected an article about project management in software development, have a look.

When there are many projects, they need to be standardized and defined to details. Only in this way can we support large-scale development.

PM is very important, and its ability will directly lead to the final quality of the project.

This article is described according to the current situation of the company, which is not necessarily universal-the right one is the best.

Responsibilities of the project manager:

1. The basic responsibility is to ensure the realization of the project objectives and lead the project team to complete all the work on time and with high quality.

2. Communicate with customers to understand the overall needs of the project. And keep in touch with customers, feedback the phased results immediately, and change the reasonable demands put forward by customers immediately.

3. Make the project development plan document, quantify the tasks and allocate them to the corresponding personnel reasonably.

4. Track the progress of the project and coordinate the cooperation among project team members.

5. Supervise the production of documents at all stages of project progress, and immediately communicate with QA to ensure the completeness and standardization of documents.

6. When the requirements change during the development process, the project manager needs to understand the requirements with the customers. In the case that he can't judge the influence of the new requirements on the project arrangement, he needs to discuss with the project team members, finally decide whether to accept the customer's requirements, and then negotiate with the customer. When it is determined that requirements need to be changed, it is necessary to generate requirements change documents, change development plans and notify QA.

7. After the project is submitted for testing, the project manager needs to know the test results and change the development plan again according to the severity of the bug tested.

8. Report upwards. Report all project information to the superior, such as project progress and demand changes.

9. Project summary is required when the project is completed, and a project summary document is generated.

Project manager's rights:

1, development headquarters. Allocation and adjustment of project developers.

2. Technical decision-making power. Mainly to review and approve major technical measures and technical schemes to prevent decision-making mistakes and cause heavy losses.

3. Apply for the right of cooperation. When there are problems that cannot be solved in project development, you can apply for cooperation from your superiors.

4. Assess the rights of members. Assessment of project team members, vision and test team only assess the team leader.

Necessary process:

1. Every afternoon at 5:00 and 6:00, the project manager will call relevant personnel (including developers and artists) to make a daily summary of the project, including:

(1) Understand the work progress of each member.

(2) Understand the difficulties encountered by members in their work and find resources to solve them.

(3) Whether the cooperation among members is consistent (for example, the project to be submitted is not submitted on time or forgotten to submit, etc.). ).

(4) If necessary, adjust the project plan according to the current progress.

(5) Arrange each member's work for the next day.

(6) If it is considered that the current progress of the project may lead to the delay of the project, the project manager has the right to arrange the project team to work overtime to ensure the construction period.

2. If the project manager receives new requirements, the project manager should raise them at the daily summary meeting of the project in the afternoon and assign work. Unless the new requirements are particularly urgent or affect the current task of the project team, it is necessary to convene the project team members for urgent discussion, otherwise the current work of the project team should not be interrupted.

If new requirements are received after work every day, the project manager will call the project team members to discuss and assign tasks the next morning.

Question 10: What is the development direction of being a software implementation engineer? Hello, my friend, I am a software implementation and development engineer. Let me briefly introduce the development direction of this position.

First of all, unlike software development engineers, implementation developers seldom contact with project coding, and mainly focus on database operation, coding storage process and data conversion, so their coding ability is very weak after working for many years. However, the implementation development engineer knows the business logic of the project very well and is good at customer communication. Then, demand communication analysis is the main task, and for implementation engineers, project managers and management administration are the development direction. Of course, the database administrator is the most ideal position.

In other words, we actually have two development plans, the first is the project manager, and the second is the administrative management. You must be a project manager before becoming a database administrator.

The income of pre-implementation engineers is much higher than that of developers, because it involves subsidies. However, if you don't make your own direction clear as soon as possible in the later period, your income will enter a bottleneck period after 2-3 years, and your income will be at the lower-middle level, which is ok in Shandong. But working in Shanghai is too difficult for you ... but not bad for a fresh student.

Make your own plan as soon as possible, I believe you will have no problem!