OBJECT ORIENTED PROGRAMMING - Atomic Object

← 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.

Some factors that impact on and reflect complexity in software: • The number of names (variables, functions, etc) that are visible • Constraints on the time-sequence of operations (real-time constraints)

  Programming, Software, Impact, Object, Oriented, Object oriented programming