Audit IDC Charging System Acceptance

Two days ago in the conference room, I first saw the legendary master's apprentice acceptance scene. It gave me the feeling that I was doing a thesis reply! A bunch of teachers listened to a classmate about his thesis or design, pointed out the flaws or bright spots in his work, and then gave comments. He had strict requirements on various details. Fortunately, we are also people here. We are not afraid of such scenes, (* ^__ ^ *)!

 

Looking at what they have done, they have a lot of technical knowledge, such as what package diagram, UML diagram, B and U layers, however, many of the ideas and design methods mentioned are of great benefit to our future study. Let's talk about the points I have seen.

1. Importance of design during project development

As the saying goes, it seems that it takes a lot of time to design the ideas in the early stage. If you feel that it is not worth it, you may encounter various errors during development, it is even serious to the point where reconstruction is needed! We can't just see the building on the ground, but forget the principle that the Foundation is deeper than the tall building! This is like the relationship between strategy and tactics. The strategic direction is wrong. Even if the tactics are advanced and savvy, it is difficult to escape the bad luck of failure. Therefore, planning and design are really important!

2. Reasonable and complete document writing in various periods

A complete software or system R & D process is not only reflected in the development code, but also in the overall design, various stages, and documents recorded in various situations. Reasonable Writing of documents allows developers to understand them at a glance, rather than making them confused in the cloud after reading the documents. The overall layout and details of the document are understood to make tables, drawings, and texts clean and concise, avoiding clutter and complexity. From the overall architecture of software to the naming and wording of documents, we need to carefully consider these issues. In our learning process, there may be document templates written by people who have learned well in the previous or current period, if we add a little bit of something to cope with errands according to their documents, empty, uniform, and without our own soul, we will eventually suffer ourselves.

 

3. Tools and division of labor for teamwork

Team Cooperation, as the name suggests, is the development of the same project by more than N people. The division of labor is really important, not only to give everyone the opportunity to develop, but also to train them to refine the accepted division of labor, such as to do things on the B layer of UML will not be placed on the u layer. Only when everyone makes a good part of themselves can the entire software be healthy and complete. The various tools used during this period should also be unified as much as possible. Otherwise, unexpected errors such as incompatibility may occur.

 

4. Proactive System Maintenance

Every time a new software is developed, various bugs are inevitable. But how can users enjoy and use your software? So that consumers can see error opportunities as few as possible! In fact, software development relies on technology, and is even more rational! We should design R & D and maintenance for consumers in the spirit of serving the people wholeheartedly. After an error is detected (small of course), we will not tell the user to send it to the maintenance personnel quietly for improvement, upgrade, and maintenance, which will make people happy. Like a peacock screen, you must present your excellent side to others. After all, no one is perfect and no software is perfect! During development, the system can specially design an error collection system and processing module to centrally handle unavoidable exceptions and unexpected errors! Of course, the standardization and rigor of code and comments are necessary!

5. Design and consumption habits of Chinese towards software

Our Chinese attitude towards software is two words: make up! Buying things and using things are both cheap and cost-effective. As long as the performance is similar, it can work properly. I 'd rather spend 0.1 million at a time and 0.1 million at a time.
At last, it took 1 million yuan to buy a software with high quality and good reputation. The thought is to be able to run together and maintain together, but to make a big profit! Then developers will design software that suits their appetite according to such users. The gradual vicious circle has created a common characteristic of our National Software Industry: low price (that is, small profits), high maintenance costs, and short life cycle. The software designed by many Western developed countries is relatively rigorous and expensive, but the product quality is high and the maintenance cost is low. Therefore, most of the software and operating systems used in the world are not designed and developed by Chinese people!

 

6. Getting
Things Done

Try to make your mind not remember anything, learn without pressure, and learn happily. Use various tools to include reminders. As long as you arrive, let the tool remind you. For example, if you want to lend something to someone else, you should not remember it in your mind. Instead, you can use a pen, mobile phone, or computer to write down the details. You can check the details directly when you need it, process them in a centralized manner. Otherwise, if our brains remember too many things, they will get tired and affect their mood and learning efficiency.

 

There are other knowledge, such as the basic knowledge, the use of shortcut keys, the construction of real graphs, class diagrams, packet diagrams, state diagrams, activity diagrams, and the difference between components and controls, the harvest is really big. I will sort it out and share and discuss it with you!