1. Chapter 3: Object-Oriented Design Presentation slides for Object-Oriented Programming by Yahya Garout KFUPM Information & Computer Science Department

2. Outline b Responsibility Implies Noninterference b Programming in the Small and in the Large b Why Begin with Behavior? b A Case Study in RDD The Interactive Intelligent Kitchen HelperThe Interactive Intelligent Kitchen Helper Working with ComponentsWorking with Components Identification of ComponentsIdentification of Components b CRC Cards-Recoding Responsibility Giving Components a Physical RepresentationGiving Components a Physical Representation The What/Who CycleThe What/Who Cycle DocumentationDocumentation

3. Responsibility Implies Noninterference b The conventional programming proceeds largely by doing something to something else b One portion of code in a software system is often tied to many other sections of the system b A responsibility-driven design attempts to cut these links b This notion might at first seem no more than information hiding and modularity b Responsibility-driven design elevated information hiding from a technique to an art b One major benefit of object-oriented programming is the reuse of software subsystems

4. Programming in the Small and in the Large b Programming in the small has the following attributes: Code is developed by a single programmer who understand all aspects of a projectCode is developed by a single programmer who understand all aspects of a project The major problem is the design and development of algorithms for dealing with the problem at handThe major problem is the design and development of algorithms for dealing with the problem at hand b Programming in the large has the following features: The software system is developed by a large team of programmers with no one understanding all aspects of the projectThe software system is developed by a large team of programmers with no one understanding all aspects of the project The major problem is the management of details and communication of information between diverse potions of the projectThe major problem is the management of details and communication of information between diverse potions of the project

5. Why Begin with Behavior? b Understood long before any other aspect b Can be described almost from the moment an idea is conceived b Can be described in terms meaningful to both programmer and client

6. The Interactive Intelligent Kitchen Helper

7. Working with Components

8. Identification of Components

9. Giving Components a Physical Representation

10. The What/Who Cycle

11. Documentation