My blog has been opened and I haven't written any technical articles for a while. I have been busy working some time ago and have almost no time to reflect on my work. Although it is not very difficult to do things, however, it takes a lot of time to get familiar with new things. Solframework is a new framework developed by Microsoft. It is a MVC framework tailored by Microsoft for Cosco Real Estate, development on the basis of this platform causes a lot of subsequent troubles.
Let's talk about the recent work. Recently, my work has not been very satisfactory and many things have not been conducted according to my own plan. The most important manifestation is that no articles have been updated during this time, no technical articles or work-related studies have been conducted in a timely manner. It may be related to your work environment or the nature of your work.
I. demand change
Demand changes are troublesome. The most unsatisfactory thing in the recent period was the difficulty encountered in the work of data, which took over the new requirements demanded by the superior leadership, that is, demand changes. Ocean-going SOA platform has a total of 52 service packages. We are responsible for the on-site sales service packages, which mainly solve the problem of House selling. This service package was put into the production environment in May, the customer is currently in use, but a new requirement is raised during use. We are the maintenance personnel who need the new service package and further optimize the requirements, this is also the biggest headache for programmers. Developers are afraid of changing their needs if they are not afraid of development. Demand changes have to be paid at a cost. The most important one is the waste of time and money. demand changes may affect the progress of the entire project. Of course, labor, material resources, and financial resources are required, so how can we minimize the loss caused by demand changes and respond to demand changes? This is an issue that developers and designers need to consider. I checked some methods to cope with demand changes on the Internet. The most important difference is the division of the two aspects. First, we should make the best preparations for demand changes before project development, second, control of demand changes during the development process.
1.1 before development
1. reduce demand changes. To better cope with demand changes, pre-development work is very important. That is to say, before development, we should be able to predict where some requirements will change, respond to possible changes as soon as possible. What we are talking about here is not to circumvent demand changes. In fact, it is a wrong idea to try to circumvent demand changes. demand changes are a normal problem, although it may have an impact on project development, it is an inevitable problem. In case of demand changes, new demands and new demands are often raised, this will lead to an increase in the development time and cost, so we must proactively solve the demand change point before development. In addition, we recommend that developers or designers use prototype methods to inspire customers to think about functional requirements, so that customers and Ba can work together to develop requirements standards.
Second: standardized and rational design. Before developing a requirement document, you must pay attention to the completeness of requirements. Therefore, it is important to set standards for requirements. In addition, the requirement specification is an important interface between developers and customers throughout the development process. Therefore, the formulation of the requirement document must be complete, consistent, baseline control, historical records, and other features, when developing a requirement document, you must deliver the document to the customer for review and determine the baseline based on the customer's satisfaction. The second is a good structure system. When designing a software system, a good structure system can greatly reduce the changes caused by requirements, therefore, a qualified architecture must be developed during the design. The flexibility, scalability, and robustness of the data system must be considered first when designing the system structure, this is an essential feature of a good architecture. To design a high-reliability architecture design model, you must use the technology and use the design model properly, the design mode is used between various modules of the system or within the module to control the impact of demand changes on development.
1.2 demand change control
Demand changes are often inevitable. demand changes can be controlled not only before development, but also during the development process. The control of demand changes can be roughly divided into seven steps.
1. Change application. No matter what you want to do at the beginning, the customer must first apply for a change. As long as someone proposes a change, we need him to apply for a change. However, customers often ask for changes over the phone. How should we solve the changes at this time? Of course, we are not afraid. We can convert a customer's change into a text record. We can record the change. In this way, we will be able to communicate with the customer with evidence and not afraid of credit.
Second: technical approval. What approval? Technical approval is of course to assess whether a change in demand can be implemented technically. Sometimes the customer's requirements are difficult to solve technically. At this time, it is necessary to promptly consult the customer for problems, of course, in most cases, technology can still meet new requirements.
Third, period evaluation. The proposal of new requirements will not affect the construction period of the entire project. It is necessary to quantify the construction period, cost, and quality in order to force the project team to understand what a change means. At this time, a detailed change period evaluation is made for the entire project. Will the change affect the delay of the entire project period? If so, I must weigh the advantages and disadvantages and discuss the impact of customer communication on the period, finally, determine whether the change takes effect. If the product is in urgent need of release, it is best to delay the change.
4. Cost Estimation. Changes to project requirements may involve the addition of new developers. If no one needs to spend the corresponding project fee every day, the project cost must be estimated in detail, the purpose of estimation is to provide a more detailed understanding of demand changes.
5. analyze the impact on product quality. Changes in demand will not affect the stability, reliability, and security of the original system. In addition, the changes in demand need to be tested in detail to determine whether the changes have a great impact on the testing quality, will it cause other system problems.
6. Risk Analysis. A change in demand is a major event. A change means more functions, and more functions often mean more work and more variables, that is, there are more risks. A change in demand may result in a low morale of the project team and lead to a loss of personnel, which may cause risks to the project team. Therefore, the risk of the change should be evaluated.
7. Conclusion. It is important to make a decision. At last, someone needs to sign the customer's signature to let the customer know the desired change.
Ii. program code
There are many coding issues. Another headache is that, during the development and development process, there are hundreds of program problems. The most important issue is that the code of the number program is inefficient during the coding process, the code is not well optimized. Encoding mainly considers the stability, robustness, and scalability of the system. When using any object, you must remember to empty the object. Empty objects can easily cause errors, in addition, we should consider program optimization and try to avoid multiple accesses to the database. It is best to query all data at once. Finally, when encountering new problems, we must clarify the program development ideas, have detailed control over the overall needs, and have a clear understanding of the development ideas, do not develop blindly. Be sure to clarify the development ideas and use the same logic when it comes to the same problem. The development model should also use the same, and should not be different, otherwise, the maintenance will be burdened.
Conclusion
If you encounter problems, it is a good thing to explain whether you are still immature. The most important thing is demand change and program code. demand change is a headache for programmers. The difficulty is not due to new development requirements, instead, it is difficult to modify the original things repeatedly, which may involve understanding others' ideas, because it is troublesome to follow others' coding ideas, in addition, five or six projects have been developed since the beginning, but code for programs still needs to be refined, and the most functions can be implemented with the least code.
Two sins at work
