Simply - OOP - Simply

Loading...

Flash Player 9 (or above) is needed to view presentations.
We have detected that you do not have it on your computer. To install it, go here.

0 comments

Post a comment

    Post a comment
    Embed Video
    Edit your comment Cancel

    Notes on slide 1

    I'll mainly talk about the what is and the why of OOP. The how — i. e. the syntax — is relatively easy to look up, when you've understood the concepts. Image: http://www.sxc.hu/photo/998467

    3 Favorites

    Simply - OOP - Simply - Presentation Transcript

    1. simply — OOP — simply Let's talk about concepts .
    2. Thomas Bahn [email_address] +49/4307/900-401 assono GmbH http://www.assono.de http://www.assono.de/blog
    3. You can use a pocket watch.
    4. The manufacturer must know how to build the clock.
    5. A concept called information hiding . Reduce complexity by hiding details beneath the surface.
    6. This is the power of OOP .
    7. Everything is an object . Everything consists of objects.
    8. There are many objects. Concurrently . Objects interact .
    9. OOP maps real world objects to software objects.
    10. A concept called encapsulation . Object = state + behavior + identity
    11. „Think of an object as a fancy variable; it stores data, but you can „make requests“ to that object, asking it to do operations on itself.“ Bruce Eckel, Thinking in Java
    12. Models of an office chair
    13. A concept called abstraction . Reduce complexity by ignoring unnecessary details.
    14. This is the power of OOP .
    15. A concept called class .
    16. Divide and conquer : Software design class for class
    17. This is the power of OOP .
    18. A concept called inheritance .
    19. This is the power of OOP .
    20. A concept called polymorphism .
    21. Change behavior without changing code.
    22. This is the power of OOP .
    23. Everyone has his responsibilities . Every object, too.
    24. A concept called delegation .
    25. This is the power of OOP .
    26. Construction and destruction of objects
    27. Let's talk about principles . Keep it simple .
    28. The public interface of a class is a contract .
    29. Make the public interface as small as possible. You can always add later, but never remove , nor modify .
    30. Remember: You can always change the private internals .
    31. Reduce coupling between objects.
    32. Test your classes separately first. A concept called Unit Testing .
    33. Let's talk about OOP in LotusScript .
    34. Demo of the Watch class.
    35. Demo of the Email class.
    36. The end Ask questions now — or later Blog: www.assono.de/blog Email: [email_address] Phone: +49/4307/900-401

    + Thomas BahnThomas Bahn, 2 years ago

    custom

    1075 views, 3 favs, 0 embeds more stats

    Session from ILUG 2008, see http://www.ilug2008.org more

    More info about this document

    © All Rights Reserved

    Go to text version

    • Total Views 1075
      • 1075 on SlideShare
      • 0 from embeds
    • Comments 0
    • Favorites 3
    • Downloads 145
    Most viewed embeds

    more

    All embeds

    less

    Flagged as inappropriate Flag as inappropriate
    Flag as inappropriate

    Select your reason for flagging this presentation as inappropriate. If needed, use the feedback form to let us know more details.

    Cancel
    File a copyright complaint
    Having problems? Go to our helpdesk?

    Categories