Object Thinking
Upcoming SlideShare
Loading in...5
×

Like this? Share it with your network

Share

Object Thinking

  • 3,289 views
Uploaded on

This is a presentation I gave a number of times to user groups in the UK during 2007 and will be giving again during 2008 (including at DDD Ireland).

This is a presentation I gave a number of times to user groups in the UK during 2007 and will be giving again during 2008 (including at DDD Ireland).

More in: Technology
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
No Downloads

Views

Total Views
3,289
On Slideshare
3,277
From Embeds
12
Number of Embeds
4

Actions

Shares
Downloads
48
Comments
0
Likes
2

Embeds 12

http://www.slideshare.net 9
https://twimg0-a.akamaihd.net 1
https://si0.twimg.com 1
http://www.slideee.com 1

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. Object Thinking
  • 2.  
  • 3.
    • The Philosophy of Development
    • formalism -vs- hermeneutics
    • From Philosophy to Culture
    • mentoring, metaphor & vocabulary
    • From Culture to Practice
    • object discovery & thinking
  • 4.
    • Formalism/Determinism
    • (software engineering)
    • uses traditional thinking
    -vs- Hermeneutics/Postmodernism (extreme programming) uses object thinking
  • 5. The Object Thinking Manifesto
    • Advocacy of behavioralism
    • Antagonistic towards formalism
    • Emphasis on analysis and conceptualization
    • Philosophy of extreme programming
    • Prefers the autonomous to the autocratic
  • 6. The Object Thinking Manifesto
    • Better people write better code
    • - not better tools
  • 7.
    • “ Let there be no doubt that object-oriented design is fundamentally different than traditional structured design approaches:
    • it requires different ways of thinking about decomposition, and it produces software architectures that are largely outside the realm of the structured design culture.”
    • Grady Booch, 1991
  • 8.
    • “ Let there be no doubt that object-oriented design is fundamentally different than traditional structured design approaches:
    • it requires different ways of thinking about decomposition, and it produces software architectures that are largely outside the realm of the structured design culture .”
    • Grady Booch, 1991
  • 9. Observing the Object Difference
    • Traditional thinking
    • Object thinking
    Data Structure operationX operationY operationZ
  • 10.
    • Anthropomorphization
    • is the attribution of human characteristics to inanimate objects, animals, forces of nature, the unseen author of things, and others.
  • 11.
    • “… if the diagram is an accurate depiction of an object, what is the difference between an object and a COBOL program?”
  • 12.
    • “ There is none. A COBOL program encapsulates data and operations and allows communication among programs. Object development – using this model – will have a tough time being anything more than the creation of lots of tiny COBOL programs.”
  • 13. Object Depictions
    • Entity
    UML Customer ID# dob gender fname … getID# setID# getDOB# setDOB# … Customer id# dob gender fname lname mi honorific generational …
  • 14. Object Depictions Object (Class-Responsibility-Collaboration) Customer ID self describe self indicate desires make decisions confirm information
  • 15. Encapsulation via Properties
    • public class Customer
    • {
    • public string Name
    • {
    • get { return _name ; }
    • set
    • {
    • // validate here
    • _name = value ;
    • }
    • }
    • private string _name ;
    • }
    • Known as information hiding
    • Traditionally taught as a key precept of OO
    • But many XP advocates say they should not be tested … why?
    • Why do objects keep trying to change type?
    • Is there a better way?
  • 16. Self-Describing Objects
    • public class Customer
    • : Dictionary < Uri , Object >
    • { }
    • Provides a property bucket
    • Looks alien to traditional thinking
    • Violates traditional encapsulation principles
    • How is validation carried out?
  • 17. Self-Evaluating Rules
    • Evaluate self-describing objects at runtime
    • Promote type re-use via separation of concerns
    • Embody data validation rules, business rules, or any other constraint
  • 18. Demo Self-Describing Objects & Self-Evaluating Rules
  • 19.
    • So all my objects should be self-describing?
  • 20.
    • Having a hammer
    • does not make everything a nail
  • 21. Non-Self-Describing Objects
    • Primitives
    • bool, int, float, enum, etc.
    • Some Standards
    • html elements, xpath predicates, industry, etc.
    • Self-Describing Objects tend to be actors
  • 22. Issues
    • Currently no standard supporting framework
    • I am considering a CodePlex or SourceForge project
    • Limited knowledge, few publications, no examples
    • Just try googling for the key terms…
    • Steep learning curve
    • Hard to ‘unlearn’ traditional thinking
    • Few practitioners or evangelists
  • 23.
    • Links
    • http://del.icio.us/alan.dean/object-thinking
    • http://thoughtpad.net/alan-dean
    • Email
    • [email_address]
    • © MMVII