Answer
The purpose of OO analysis and design is Identifying the objects of a system. Identify their relationships. Make a design which can be converted to executables using OO languages.

Answer
Industry known visual modeling notations are:

Answer

• Less project failure, better productivity, and lower defect rates. Shown by research into iterative and evolutionary methods
  
• Early rather than late mitigation of high risks (technical, requirements, objectives, usability, and so forth)
  
• Early visible progress
  
• Early feedback, user engagement, and adaptation, leading to a refined system that more closely meets the real needs of the stakeholders
  
• Managed complexity, the team is not overwhelmed by “analysis paralysis” or very long and complex steps
  
• The learning within an iteration can be methodically used to improve the development process itself, iteration by iteration
  

Answer

Because they try to accomplish the following two goals:

1. Identify and drive down the highest risks
   
2. Build visible features that the client cares most about
   

Answer

• Feedback from early development, programmers trying to read specifications, and client demos to refine the requirements.
• Feedback from tests and developers to refine the design or models.
• Feedback from the progress of the team tackling early features to refine the schedule and estimates.
• Feedback from the client and marketplace to re-prioritize the features to tackle in the next iteration.
  

Answer
In this life-cycle approach, development is organized into a series of short, fixed-length (for example, three-week) mini-projects called iterations; the outcome of each is a tested, integrated, and executable partial system.

Answer

Test-driven development (TDD) is a software development process that relies on the repetition of a very short development cycle, first the developer writes automated test case that defines a desired improvement or new function, then produces the minimum amount of code to pass those tests, and finally refactors the new code to acceptable standards.

Answer

• UML as sketch

  Incomplete diagrams with text

• UML as blueprint

  Detailed design diagram to visualize and understand the code
1. Forward Engineering: Design to code
2. Reverse Engineering: Code to design synchronization

• UML as Programming Language

  Implementation in a programming language

Answer

Conceptual:

The diagrams are interpreted as describing things in a situation of real word or domain of interest.

Specification:

Diagrams describe the software abstraction or components with no commitment to particular implementation

Implementation:

Diagrams describe software implementation in a particular technology.

Answer
Following are the basics Object Oriented Programming concepts:

• Encapsulation
• Information Hiding
• Inheritance
• Polymorphism