Read the note: Ten Steps to Software requirements (ii)

What a programmer needs most is reflection, and often reflection is a very difficult and very painful thing, because you want to break your past ideas and ideas, to find their shortcomings and then correct.

The demand problem is a huge problem that surrounds the software development process, and even the whole book revolves around this topic to discuss. Availability of demand is the key to software success.

In the past, people have used various methods to analyze the requirements of software, such as structural analysis method, object-oriented method, problem domain analysis method, and so on, the results can be accomplished by Case tool and UML tool. Where the UML tools analyze requirements into

The result of automatic transformation into system design results, which solves the problem of the distortion between the requirement analysis and system design in the long-term software development. In our daily study, the UML pattern diagram also has the key, sophomore last semester comparison system

Learning the UML tools, to which all kinds also have a relatively simple understanding, in today's Wang Hui teacher's class, all kinds of software design patterns corresponding to the corresponding class diagram, and can not analyze the good picture of these class diagram, then learning UML played a vital role, learning is really tied up! In the use case description, the use case description is not enough integrity and accuracy is a drawback of the UML, there is the scope of the project and the goal is defined in the use case work before the beginning of the work needs to be completed, UML does not support, we need to cut into the discussion and analysis, before the project begins, if not to find a definite scope, It is like a well-drilled ground, hitting the ground is not necessarily able to hit the water.

People's study is like painting a lattice of a circle, the more learning, the larger the circle, things will often become more and more difficult, but no matter what things need to have a better mentality to face, can not be defeated by difficulties, and can not be too conceited in the face of difficulties, but delay the resolution of the key period of the problem. When people come to middle age when they hear someone say it's simple, the first instinct is that it's not easy. People on the principle of doing things have a very classic Hu summed up: "Complex things simple to do, simple things repeat, repeat things attentively." "This is the perfect expression of the state of mind, people without misfortune, without the root of the tree without birth."

Software construction needs the software specification Hu description.

In the book, often software requirements specification is the software developer's darling, is the core of software requirements, developers through the software requirements specification to understand what users want, what to achieve, and in fact, software Requirements specification is not the core of software requirements is not the goal of software requirements, the real core is the business requirements, Because the software analysis starts from the business requirement analysis, the non-functional requirement analysis on the basis of the user requirement analysis, the work result of the software requirement analysis is the software Requirement specification, and the software Requirement specification is mainly composed of functional requirement analysis and non-functional requirement. So software Requirements specification is the core of real software requirements.

Leave the business, the software is nothing; most people may scoff at this remark, generally said absolute words are often wrong, admittedly I first heard this sentence is so psychological, but carefully think, if a software without business needs, it will be like no vector, boundless increasing multiplicity, and finally silent in the software tide. In reality, we use scene cards, system prototypes, use case diagrams, user requirements documents to get the user's needs, to make sure that this is what he wants. In order to determine their business objectives, not to say no, the root of the method is to serve the purpose, as long as the search for the purpose to find more ways to do more to take some measures and can not be.

The deductive method of formal logic can be used to solve the problem of completeness of demand, and the argumentation method of formal logic can be used to solve the problem of demand accuracy.

In the process of finding the business root, often face a variety of changes, the world because of the change and wonderful, and programming and software development if faced with a variety of changes, the programmer will certainly have a headache, even a little more difference, the code of the program may be more than hundreds of lines. The root cause of the change of demand often lies in the customer, the customer thinks the developer is omnipotent, the programmer of oneself imagines will give oneself to complete, it is because one-sided does not understand often will produce many differences, delay the development process; Customer service object is the root of change, clear the task and ability of both sides, clear their original intention, Often will eliminate a lot of inconvenience.

Read the note: Ten Steps to Software requirements (ii)