Software design depth mining
One from the software engineering
Everyone will have such a confusion: When a project is in front of us, we don't know how to analyze it, we can't grasp their workload, which is not to be grasped for difficulty, or you can't determine if our processing method is The most advanced or most stable, etc. We can take a lot of books, always want to get new, but there is no result. We look for reasons, but there is always no answer. Let's talk about this problem.
1.1 Overall Concept This We don't explain the usage of a function, the meaning of a structure, here we explain the way a complete dismissive problem. In the face of a need, our main thing is to achieve it. We have two ways: first develop from head, followed by borrowing the stone of it. Nowadays, software development is basically based on a third-party software platform. We don't want to develop from head, so we have to learn this kind of learning. For example, we need a media player, MPEG1, MPEG2 is a standard thing, we need to have a criterion, see the standard coding? Now the software industry, if you are not a special decoding company, this practice is extremely stupid. If you are a software manager, then your approach will affect the entire software schedule, quality, so we need to make a correct analysis in order to ensure no correctness. There are already a lot of mature decoding standards, which don't say the waste of energy, even if the code developed is fast, but is it necessary to care about their differences? Nowadays, most of the software exhibited in the software interactively interactively, and the function is complete, we don't have to limit the pure theory of software. The current software update has arrived unprecedentedly. We used to be developers that they can think of innovation beyond, but our foundation is relatively weak. The intrinsic meaning included in a software is not on the surface. For example, Jinshan's WPS2000 is a better domestic software. It seems that it seems that it doesn't seem to be imagined, as if we can write it every module, then you can try to write some of these features. You may find something you miss, the entire software process control? Is the design pattern unclear? The language description of the data structure is hard? and many more. Then you need to start from the beginning, these basic skills don't need you to remember, but you can happen, it is a leap, and the image change will result in a qualitative change. Software is a big field, such as the programmer in the development interface, then you can see some of some data structures, if you are driver, then you can set it with your design mode. But this does not affect our level of software, so-called in its position, a certain government. From now on software development, the entire software industry is a small world, which develops programmers in a field, like Windows programmers, Linux programmers, etc., will become a separate industry. So there is also a problem that can be interlaced, such as hazelnuts. We don't ask for how perfect manifestations, the most important thing is to bring each programmer's highlight to a little. Therefore, the most important development program is the project manager - system analyst. He is our leader, but now there is still relatively small number of quality project managers.
1.2 About Software Engineering
Software Engineering This area is very large, and the depth of explanation is also a big phase. The software engineering we discussed here is just from a programmer's perspective. That is, the most practical part of the software engineering. Now we all know that there is a noun in the software industry called software engineering, and the domestic work is also lost. But if you have seen foreign software projects, we will know that our things are just part of them. Since the birth of software, China has been chasing the world's advanced technology since the birth. When the computer industry is in full swing in the past, we finally woke up, we also have to do software. But how difficult is this, the computer system established by all foreign standards has been rooted. So we can only learn from foreign experience and develop according to others. We chase, gradually, we learned some techniques, but others' operating system, development environment and other system software, we can't help but don't have everything, we have accepted everything. This will certainly include someone else's software engineering. So what we see is written out. We want to practice those theories, but we always fail, but there is also success. We are like a hundred years of history in that year, what do they use to understand our cultural culture, we can't fully understand their software engineering, we are working hard, we have some gains, we are slow Slowly understand the profoundness of their software engineering. Here I have explained the part of understanding. 1.1.1 How do we view the software engineering? Nice, software engineering is a management MBA in the software industry, but many cases in reality have not read management. Just their behavior follows some laws of management. Therefore, we understand that software engineering does not have to practice all theories. It is completely unnecessary, just like the ancients "Half-to-talk", they are not fully understood, but they must understand the essence of software engineering. We should pay attention to our management software is not in order to comply with software engineering, but in order to comply with the correct software rules, this is not a negative software engineering, but everyone must know that the software project will change as practices, but you solve the problem method. Maybe in accordance with future software engineering. Just like Newton's laws have been updated. We don't have to move hard. It is only difficult to have quality leap in the case of experience. So we can use all the software theories as foundations, a foundation of solving problems. When we need to solve problems, you can use them when we need to solve problems, and then join our project feature. I don't know if it is clear: It is the software engineering in accordance with us, not our follow-up software engineering. 1.1.2 Software Engineering We all know that software engineering explains software management. Many books now introduce some of the software engineering, but it really includes much content? Let's discuss the contents of the software. Software engineering has changed with programming ideas. The original program is structured, and now is object-oriented. This has led to different descriptions of software engineering. Therefore, most of our university is a structured software engineering description. Now, from the direction of software development, this is no longer applicable. A software is a product, so the content included in the software engineering should include a development process of a product. Therefore, the quality concept is very strong, which is the law of software engineering. This development process is actually a process of problem loop solving. It includes four distant phases: status description, problem definition, technical development and program review. The status description indicates the current state of the transaction; the problem definitions identifies a specific problem to be resolved; technology development is solved by applying certain techniques; the program reviews submit the results to those who need programs from the beginning.
Therefore, software projects should include: 1. Software project management part This is some basic principles to apply to all phases of software. 2. The traditional software engineering section includes an object-oriented software engineering for the original structured analysis section. 3. Object-Oriented Software Engineering Part This is now the most commonly used object-oriented software engineering method. 4. Some special engineering processing methods include some technologies for more advanced software engineering concepts, but may not promote those theories. For example, the user-oriented software engineering 5, the analysis of the software product process is the engineering theory that is controlled as software products. This is the control of a product, and the technology is different. The above part is the content of the software engineering. It can be different from everyone's needs, depending on person. Talking about Software Engineering We have to discuss this thing now. Now there is a powerful software company to find any CMM and so on, I have seen many software companies have a wrong point of view: I can change everything in line with the standard. This is actually a big mistake, we can't blindly attach the standard, you must figure out the scope and time limit. These standards are somewhat too big for software companies in our country (the general company), what is much, it is too large, and the organization is set to the development process to the final product. We can't expect dozens of people to complete a large project in three months, but also complete all documents, complete all quality assurance programs, complete ROSE, etc., the most important thing is that they cannot be in the development process. The technical problems we have encountered will generally be a lot. Then what should we do in line with the standard? For many standards of general software companies, it is not suitable for them, such as programs with less code than 10,000 rows.
Fried as a medium-sized project, followed by all development steps, it will be bound by rule.
It is said that the Indian software industry is good, in fact, they also have a lot of flexibility in their norms.
If all, you can't set it up, just like the 100,000-line code software, you can do not write an example of design, you can directly reach the detailed design instructions, you can also vary depending on the project, some can save users interface Design parts, some can automatically generate only those framework documents of RUP. Our development is flexible, but basic things must have, such as: code specification, general development process (different according to different software industries), company software system, etc. If our company still doesn't pay attention to this, it will be dragged by it, and he still thinks not enough. Most of those systems are for large and medium-sized enterprises, just like Window2000 Server, but very expensive, Window 95 is cheap but enough, we have to choose to be suitable for you, as the company grows, software configuration management It will also be gradually improved, and it is superimposed as the software development. Software configuration management is a big problem that reflects a company management level. The general company may use SourceSafe, and now I am very fireful, we may know. But the choice is still not selected, we did not agree, the same is the most important. If ClearCase is configured, a separate manager, separate maintenance, complex operation.
I have passed Cleaecase training, but it is still very fuzzy to practice.
Benefits, but gradually, you will find it, but how long is it. It is reflected in the pending benefits. If you think about it, how many companies can you have this stage? (I think Cleaecase is a better software configuration tool now)
(As far as I know much, the company has its own software standard to replace UML, so this is not discussed here.
I think it is necessary to popularize UML better)
We are still progressive.
