[ZT] The OO design process

Getting started
Http://www-128.ibm.com/developerworks/webservices/library/ws-oo-design1/index.html

A rabbi boarded a train, one on which he often rode and one whose conductor, therefore, recognized him. the rabbi reached into his coat pocket for his ticket. not finding it, he began a search of his belongings. the conductor stopped him: "Rabbi, I know you must have the ticket somewhere. don't bother searching now. you can send it later, when you do find it. "But the Rabbi kept searching. when approached by the conductor yet again, the rabbi replied: "You do not understand. I know you trust me for the ticket,But -- Where am I going?

This is an example cited by the author. It is said that a scholar often takes a train and the conductor on the bus knows him. A scholar cannot find a ticket because the conductor knows him, just tell him you don't need to find it. It's okay. The scholar kept looking for it. The conductor said that I don't mind. Why are you still in a hurry? The scholar said, "You don't understand. I know you believe me. But -- I don't know where I want to go without a ticket? ". Great sweat!

In fact, it is far-fetched. I don't know how to ask the conductor ?!

In fact, the author wants to say that many people are happy to use derivation, class hierarchies, UML, and Java. But they don't know why to use it? In the end, there is a lack of OO theory. Many people follow suit.

First, at its core, object orientation is not at all about derivation, class hierarchies, UML, Java technology, and so forth. these are tools that the OO designer puts to use in order to structure the analysis, the design, and the implementation, but they aren't central to what makes an OO program object-oriented.

All too processing projects fail because they begin without a clear idea of where they're going. the oo process tries to solve this dilemma by defining the problem to be solved as its first step; it will take me a few columns to do that in sufficient detail so that the actual analysis and design phase can proceed. that is, before you can analyze, you have to have something to analyze.

Beginning to design software
Http://www-106.ibm.com/developerworks/webservices/library/ws-oo-design2/index.html

Refining the problem definition
Http://www-128.ibm.com/developerworks/webservices/library/ws-oo-design3.html

Verifying the analysis
Http://www-106.ibm.com/developerworks/webservices/library/co-design4.html

Use cases, an introduction
Http://www-128.ibm.com/developerworks/webservices/library/co-design5.html

Use cases applied, Part 1
Http://www-128.ibm.com/developerworks/webservices/library/co-design7.html

Use cases applied, Part 2
Http://www-128.ibm.com/developerworks/webservices/library/co-design8/index.html