After the "Investigation of the Investment Management System", the heart is really a little uneasy, because I really don't know what to rewrite below, according to my own reasoning, define this topic as the "Overview of the class in the hotel management system", go 9CBS looked at the previous chapter, and there was a problem. Two peers gave a reply as follows:
Tobato (2003-7-16 20:41:55)
Insert a sentence, look at it carefully, the use of the use case seems to have problems. ^ O ^ Tobato (2003-7-16 20:39:26)
Oh, use cases can be said that there is nothing to do with OO. The use case is to better understand the problem you have to solve. But what you can solve this problem You can use OO or oo. Do_young (2003-7-16 16:05:24)
Also, I can't help but remind you: So far, your things and OO have not stained. Problem definition, process analysis, these things can be served in OO or in non-OO. Dove_Young (2003-7-16 16:02:33)
After completing the use case process analysis, I found that I have fallen into a dilemma, what is the meaning of this vocabulary? ? ? ? Don't be so exaggerated? You will scare the children. My gosh……
Sure enough, the rookie is a rookie, but I still have to declare it. This is my first real design, and I am not born, and the content written is truth. It is not to attract eyeballs. This conceptually has just been exposed to. It can be said that everything about the design is first contact. So there is absolutely no psychology of children, and I sincerely hope that I can learn from this series, it is best to learn something. So I still have to stick to it before I haven't reached the cliff, and I hope that the programming has a deep understanding of the peers to give more points. Thank you.
Before entering our topic, I first said, "Building User Interfaces for Object-Oriented Systems" (http://www.javaworld.com/javaworld/jw-07-1999/jw-07) Toolbox.html gives me a lot of confusion and questions.
The first confusion is that the author of Allen Holub ("Building User Interfaces for Object-Oriented Systems" and "OO Design Process") very focused on: we conducted OO design, not CB (class-based) WE'R Doing Object-Oriented Design, NOT Class-Based Design. Originally, the title of the next section as an overview of the class in the hotel management system now seems to be changed to the Overview of the Objects in the hotel management system. Maybe this seems irrelevant, but since Allen Holub clearly puts this, I think he has to have its own sense (it is correct, the approximate method used in the previous use of Delphi) Most Methods That is, the static method is not reflected in OO. He mentioned in this article "We use a set of objects in the running period, not the class (the description of the object) (the description of the object) (the description of the object) (the description of the object) (NOT CLASSES - Animals, NOT THEIR DESCRIPTIONS"
The next question is even more unbearable (really wants to scare your child): Allen Holub has a comprehensive negation for the definition of the object. He believes that the object is a collection of capabilities, which is defined by it, but not what he did to define - how the data is done. He believes that the subject is not a data structure (which includes a set of methods for operating the data structure) [1]. Allen Holu uses more actual terms to define objects as: an object is a message definition he accepts and transmitted, and how the message is handled in this object uniquely interface [2]. Third, Allen Holub believes that OO is that an program is more easily developed and maintained, and it is not to do this (I have always thought that one of the multi-layer structure is to provide better maintenance. Program). The original text of this paragraph can't be found, but it is quite reasonable.
......
Allen Holub has a standard for OO system (only English): 1, All Data is private. Period. (This Rule Applies To All Implementation Details, Not Just The Data) 2, Get and Set Functions Are Evil. . They're just elaborate ways to make the data public) 3, Never ask an object for the information you need to do something;. rather, ask the object that has the information to do the work for you 4, It must be possible To make any change to the war owned.
It seems that there is still a lot to learn, and several of the estimated hotel management systems may be about Allen Holub theory. thanks for your support.
[1] You may have read in a book somewhere that an object is a datastructure of some sort combined with a set of functions, called methods, that manipulate that datastructure. Balderdash! Poppycock! First and foremost, an object is a collection of capabilities ......................................................................................................................................................................................................................................................................................................... Can received and send; The Methods this.
to be continued
