Do the Right Things & Do the Thing Right

Analysis = Do the right thing
Design = Do the thing right

Object-oriented analysis: there is an emphasis on finding and describing the objects and concepts in the problem domain.
Object-oriented design: there is an emphasis on defining software objects and how they collaborate to fulfill the requirements.

OOA -> OBJECTS and CONCEPTS (in problem domain)
OOD -> SOFTWARE OBJECTS and COLLABORATION (in software domain)

Further more:

Object-oriented analysis is concerned with creating a description of the domain from the perspective of objects. There is an identification of the concepts, attributes, and associations that are considered noteworthy. -> domain model -> domain model is not a description of software objects; it is a visualization of the concepts or mental models of a real-world domain. -> conceptual object model.

OOA -> domain model / conceptual object model -> concepts/objects, attributes, associations

Object-oriented design is concerned with defining software objects, their responsibilities and collaborations. A common notation to illustrate these collaborations is the sequence diagram.

OOD -> sequence diagram (or others) -> software objects, objects' responsibilities and collaborations.

Use Case

User Cases are not an object-oriented artifact. They are simply written stories.

---- Applying UML and Patterns

Requirements analysis may include stories and scenarios of how people use the application; these can be written as USE CASES.

USE CASES == STORIES