OBJECT ORIENTED PROGRAMMING

← Back to document page

1 Copyright Atomic OBJECT , LLC 2009 OBJECT ORIENTED PROGRAMMING Carl Erickson Atomic OBJECT , LLC 2 Copyright Atomic OBJECT , LLC 2009 TABLE OF CONTENTS 1. Motivation for OBJECT ORIENTED PROGRAMMING . . . 3 2. The OBJECT ORIENTED Paradigm . . . 8 3. Visualizing Program Execution . . . 10 4. Naming Conventions . . . 14 5. The OBJECT Model . . . 15 6. Abstraction and Identity . . . 16 7. OBJECT ORIENTED Messaging . . . 26 8. Encapsulation and Modularity . . . 28 9. OBJECT ORIENTED Hierarchy . . . 29 10. OBJECT ORIENTED Typing . . . 30 11. OBJECT ORIENTED Concurrency and Persistence . . . 33 12. OBJECT ORIENTED Development Process . . . 35 13. OBJECT ORIENTED Analysis Techniques . . . 36 14. Pitfalls in OBJECT ORIENTED Analysis . . . 38 15. UML Notation . . . 40 16. CRC Cards.

programming world have learned to think in terms of algorithmic decomposition. This was hard to learn and is even harder to unlearn. Computing as simulation The primary difference between OT and structured HLLs is the fidelity of the abstraction to the real world. Fortran forces you into working with abstractions that are computer-language oriented

  Programming, Object, Oriented, Object oriented programming