what is analysis and design?

Analysis:
emphasize an investigation of the problem and requirements rather than a solution .for example if a new computerized library information system is desired,how will it be used?Analysis is a broad term, be qualified, as in requirements analysis or obje analysis.

Design:
Data Structures and Algorithms with Object-Oriented Design Patterns in C++
Ultimately design can be implemented.
As with analysis, the term is best qualified, as an object design or database design.

What is object oriented analysis and design?
During object oriented analysis, there is an emphasis on finding and describing the objects or concepts in the problem domain. For example in the case of the library information system, some of the concepts include Book, Library and patron.
Basically,it is a software engineering approach that models a system as a group of interrelated objects. Each object represents some objects of interest in the system being modeled, and is known by its class, its state and its behavior. Various models in a system can be created to show the static structure, dynamic behavior, and run-time deployment of these collaborating objects.
Object-oriented analysis OOA/D applies object-modeling techniques to analyze the functional requirements for a system, elaborates the analysis models to produce implementation specifications. OOA focuses on what the system does, OOD on how the system can do that.

Define use case:
Requirements analysis may include a description of related domain processes, these can be written as use case.
Use case:
are not object oriented artifacts they are simple written stories. However they are popular tools in requirements analysis and are important part of the unified process.
For example here is a brief description of a Dice game.
"play a dice game: a player picks up and roll the dice. if the die face value total seven, the wins otherwise they lose"

Problem Domain:
Object-oriented analysis looks at the problem domain with the aim of producing a imaginary model of the information that exists in the area being analyzed. Analysis models do not consider any implementation constraints that might exist, such as concurrency, distribution, persistence, or how the system is to be built. Implementation constraints are dealt during object-oriented design. Analysis is done before the Design because it is necessary to investigate about the project or system that the user need.
The sources for the analysis can be a written requirements statement, a formal vision document, interaction with stakeholders or other necessary parties. A system may be divided into multiple parts, representing different types and works, technological, or other areas of system, each of which are analyzed and describe separately.
There are many important parts on which a software or a system depends; like
1)Interaction diagrams.
2)UML class diagrams.
3)User interface
4)Requirements
5)Construction faces

•Pattern name:
a pattern name should really reflect the meaning of what it is abstracting. It should be simple so that one can refer to it during analysis.
•Object:
A scenario that illustrates the problem and how the analysis pattern contributes to the solution in the concrete scenario
•Necessities and context:
Discussion of forces and tensions which should be resolved by the analysis pattern
•Solution:
Description of solution and of the balance of forces achieved by the analysis pattern in the scenario in the motivation section. Includes all relevant structural and behavioural aspects of the analysis pattern.
•Consequences:
this should emphasise how the goal is achieved by the analysis pattern with its limitation.
•Design:
Suggestions of design implementations of this pattern.