OO design process (II): Start to design software (--- problem definition ---)

1. OO requirement collection
Because "requirement Collection" usually contains incorrect assumptions about the requirement and how you collect it (at least from OO
Angle)
The first task is to solve what must be done, rather than how to do it.
-------- In the OO statement, the first step of the problem definition is the formal Problem description ----------------
2. Problem Description
In any design, it is always the first step to accurately present the problem. Here, your goal is to provide a concise and accurate description of what you want to solve
. I reiterate that your attention should be focused on what to do and why, not how to do it.
Knowledge about this issue
3. refine your manual
Do not do the minor work.
Explain it in a clear and well-organized language
The question to be discussed must be fully expressed in terms of the problem field.
The general principle of complete design is that a competent programmer can complete
Fully understand the specific problem to be solved and the general solution to the problem. If this level of understanding cannot be achieved, the design is incomplete.
The Problem description should involve the problem itself, rather than a computer-based solution.
4. Confirm the problem and solution as much as possible
All OO systems must be modeled. If there is a good solution to the existing problems, but the real problem is that people cannot
To quickly execute existing solutions, you need to model the existing solutions. That is, manual process automation is all necessary, and your
The manual process should be fully described in the Problem description.
One important thing to confirm is the user's goal. What exactly do users need to accomplish?
You must also specify the expected results. What is the final result of solving the problem? What information does the final result express?
Define the problem. Then, use the vocabulary in this field to explain the problem, so that your users can take a look at the problem manual.
5. Pre-encoding details
As a matter of fact, when designing and executing, the definition of the problem changes. That's why there is an end user in the design team.
Cause: to ensure that you will not damage some things because of improving them.
The initial issue definition should be as detailed as possible. Write everything you want on paper. Do not omit any details, even the simplest
I am preparing for OO development and hope to get some advice from my friends,
The above is my learning summary.
Hope you can give me some advice!