OO design process (1): Getting started-how to set priority

OO design process (1): Getting started-how to set priority
-------------------------------------------------------
The original author of this article, Allen Holub
Write Editor, JavaWorld
July 2000
-------------------------------------------------------
<Note> some places omit what I think is useless.
--------------------------------------------------------
I intend to allow you to experience the design and development process of object-oriented (OO. This column is not so much an activity as to say
It is a journey because it takes several months to complete the entire process. We will start from requirement collection, from analysis to design, and then complete the design.
Java implementation. By the end, you will go through the whole process of developing OO programs, from the beginning to the end. I will spend a lot of space on the discussion Base
This theory, however, focuses on the practical examples of how to apply this theory.
We will officially start next month. Before that, I have some advice, comments and comments which will tell you my personal opinions on the design subject.
Views and opinions.
I. OO is not about the structure
First, in terms of its core, object-oriented has nothing to do with derivation, class hierarchies, UML, and Java technologies. These are OO Designs
Tools used by people to form analysis, design, and implementation, but they are not the main part of making the program object-oriented. Of course, as the process expands
I will use all of these object-oriented structural components, but if you equate the implementation structure with object-oriented, then the first few columns
Chapter may be hard to understand. The key concept of object-oriented model is modeling. Therefore, before you start, you must decide what model to create. Adele
Goldberg (in Succeeding with Objects, see references) describes the religion of a Jewish priest at the beginning of the new year
Stories told at the Conference:
A coach boarded a train. Because he often takes this car, the train conductor knows him. The priest reached out and picked out his ticket in his pocket. But no
Yes. He started to flip his luggage. The conductor blocked him: "priest, I know you must have a ticket. Don't rush to find it now. Wait until it is found.
Show me ." The priest is still looking for the ticket. When the conductor saw him again, the priest said, "You don't understand. I know you believe I have a car
But -- where should I go?
Too many projects fail because they have no clear goals. The OO process tries to solve this problem first.
Difficult; several columns are required to achieve that step in detail, so as to continue the analysis and design phase. That is