DCI - Data, Context and Interaction @ Jug Lugano May 2011

DCI
Data, Context and
Interaction
Fabrizio Giudici, Senior Java Architect
Tidalwave s.a.s - fabrizio.giudici@tidalwave.it

Wednesday, May 18, 2011

About the speaker

DCI 2

About the speaker

• Senior Software Architect, Mentor, Technical Writer
• Fourteen years of Java experience (JSE, JEE, JME, etc...)
• Sun partner since 1998, Oracle consultant since 2010
• Author of a number of open source projects
• Speaker at JavaOne, Devoxx, Jazoon, JAX and other events
• Member of the NetBeans Dream Team
• Co-leader of JUG Milano
• Java.Net blogger at http://www.java.net/blogs/fabriziogiudici

DCI 2

Agenda

DCI 3

Agenda

• A real world example

DCI 3

Agenda

• DCI - Basic concepts

DCI 3

Agenda

• DCI - How to implement?

DCI 3

Agenda

• DCI - How to implement?
• Some simple examples

DCI 3

A real world example


Shameless Plug

DCI 5

Shameless Plug

• Exercises of Design - my design book...

DCI 5

Shameless Plug

• Just started!

DCI 5

Shameless Plug

• Just started!

• http://exercisesofdesign.java.net

DCI 5

The Observation API

• A core component of blueBill Mobile
• An application about recording bird observations
• Designed with a high degree of abstraction

DCI 6

DCI 7

The Taxonomy API

• Models the taxonomy of a philogenetic tree
• The standard way of biology for representing (bird) species

DCI 8

DCI 9

So, what about a Bird?

DCI 10


• Both a Taxon and an Observable

DCI 10


• Multiple inheritance?

DCI 10


• Multiple interface implementation?

DCI 10


• Composition

DCI 10


• Composition
• Taxon and Observable are roles

DCI 10


• Composition
• Taxon and Observable are roles
• A Bird, in some contexts, could be a Taxon and/or an
Observable

DCI 10

DCI - Basic Concepts


Data, Context and Interaction

DCI 12


• OOD best practice formalized by Trygve Reenskaug

DCI 12


• The formalizer of MVC

DCI 12



• Seen by somebody as an evolution of MVC

DCI 12



• But it doesn’t replace it

DCI 12



• It rather broadens the analysis scope

DCI 12



• It rather broadens the analysis scope

• http://www.artima.com/articles/dci_vision.html

DCI 12

DCI - aims

DCI 13

DCI - aims

• Improve readability of a OO system

DCI 13

DCI - aims

• Give system behaviour ﬁrst-class status

DCI 13

DCI - aims

• Recover readability of system properties on the whole

DCI 13

DCI - aims


• Separate responsibilities for behaviour and domain

DCI 13

DCI - aims


• Behaviour: what the system does

DCI 13

DCI - aims



• Domain: what the system is

DCI 13

DCI - aims



• Domain: what the system is

• Be close to people’s mental model

DCI 13

DCI - Data

DCI 14

DCI - Data

• What the system is

DCI 14

DCI - Data

• Relatively static with relations

DCI 14

DCI - Data

• Domain structure implemented with “conventional” classes

DCI 14

DCI - Data

• Hmm... perhaps anemic classes?

DCI 14

DCI - Data


• Typically it includes persistence

DCI 14

DCI - Data



• Comes from the mental model of system stakeholders

DCI 14

DCI - Data



• Close to the “model” in MVC

DCI 14

DCI - Data



• Close to the “model” in MVC
• E.g.: BankAccount with increase(), decrease(); no deposit()

DCI 14

DCI - Context (and Roles)

DCI 15


• Associated to a use case, user story, scenario, or
algorithm

DCI 15


algorithm
• Identiﬁes objects participating in a scenario

DCI 15


algorithm
• Assign to each object one or more stateless roles

DCI 15


algorithm
• Objects can have multiple roles at the same time

DCI 15


algorithm

• Decompose the scenario into roles, not objects

DCI 15


algorithm

• Contrast this with polymorphism and classic OO decomposition

DCI 15


algorithm

• Contrast this with polymorphism and classic OO decomposition

• E.g.: MoneyTransfer.{.withDraw(),.deposit()} with srcAccount
and destAccount

DCI 15

Quick terminology note

DCI 16


• Methodless role: abstract role

DCI 16


• Interface, abstract class

DCI 16



• Methodful role: concrete role

DCI 16



• Methodful role: concrete role
• Concrete class

DCI 16

DCI - Interaction

DCI 17

DCI - Interaction

• What the system does

DCI 17

DCI - Interaction

• Occurs among roles, which act as adapters among objects

DCI 17

DCI - Interaction

• Roles are bound in different ways for each context

DCI 17

DCI - Interaction

• Roles life cycle is likely to be bound to a given interaction

DCI 17

DCI - Interaction


• Roles should be generic

DCI 17

DCI - Interaction


• Interaction should be explicit given roles nature

DCI 17

DCI - Interaction


• Interaction should be explicit given roles nature
• Hmm.... rather than emergent as in agile design?

DCI 17

DCI - Execution Model

DCI 18


• The Context ﬁnds object participants

DCI 18


• Then, it assigns (injects?) roles to them

DCI 18


• Roles are discovered by type (methodless roles)

DCI 18



• Then, it triggers a method on the ﬁrst role

DCI 18



• Then, it triggers a method on the ﬁrst role
• Interaction goes on among other roles until the job is done

DCI 18

Some issues

DCI 19

Some issues

• What about anemic objects?

DCI 19

Some issues

• Perhaps not a problem considering clusters object + roles

DCI 19

Some issues


• Object schizophrenia

DCI 19

Some issues


• Which is the identity of an object in a cluster?

DCI 19

Some issues


• What about equals() / hashcode()? Are roles parts of identity?

DCI 19

Some issues



• Possible solution is an Identifiable role

DCI 19

Some issues



• Injected by context

DCI 19

Some issues



• Injected by context

• Objects with the same identity are “equals”

DCI 19

DCI - How to
implement?


Implementation issues

DCI 21

• Static vs dynamic

DCI 21

• Java

DCI 21

• Java
• AOP, annotation-driven code generation (e.g. Qi4J)

DCI 21

• Java
• Other languages

DCI 21

• Java
• Other languages
• Traits, mix-ins

DCI 21

• Java
• Other languages
• Traits, mix-ins

• First, acknowledge that DCI is a best practice

DCI 21

• Java
• Other languages
• Traits, mix-ins

• Some languages can ﬁt better than others

DCI 21

• Java
• Other languages
• Traits, mix-ins

• Frameworks might help... but they force a new nature

DCI 21

• Java
• Other languages
• Traits, mix-ins

• Frameworks might help... but they force a new nature

• My point: DCI must be addressed in design
DCI 21

Abstracting and sweetening

• Would be nice to be technology independent
• Would be nice to have some syntactic sugar

• Note: not central in this presentation, but needed for code
examples

DCI 22

NetBeans Platform Lookup; as()

DCI 23

• Role role = object.getLookup().lookup(Role.class) ...

DCI 23

• NetBeans Platform’s Lookup, as a bag of roles

DCI 23

• Allows both static implementation and dynamic injection

DCI 23


• Role role = object.as(Role);

DCI 23


• Role role = object.as(Role);
• My syntactic sugar around Lookup

DCI 23

Some examples


Some example reusable roles

DCI 25

• Displayable:

DCI 25

• Displayable:
• String s = myObject.as(Displayable).getDisplayName();

DCI 25

• Displayable:

• IconProvider:

DCI 25

• Displayable:

• IconProvider:
• Icon i = myObject.as(IconProvider).getIcon(16);

DCI 25

• Displayable:

• IconProvider: “ask” approach

DCI 25

• Displayable:


“tell” approach

DCI 25

• Displayable:


• Renderable:
“tell” approach

DCI 25

• Displayable:


• Renderable:
• PrintWriter pw = ... // “tell” approach
myObject.as(TextRenderable).render(pw);

DCI 25

• Displayable:


• Renderable:
• JLabel label = ... // from Swing
myObject.as(JLabelRenderable).render(label);

DCI 25

• Displayable:


• Renderable:
• TextView textView = ... // from Swing
myObject.as(TextViewRenderable).render(textView);
DCI 25

Roles can be dynamically injected,
• Displayable: so myObject does not depend on them


• Renderable:
• TextView textView = ... // from Swing
myObject.as(TextViewRenderable).render(textView);
DCI 25

Examples from blueBill

• ObservationSet set = ... ;
set.as(ObservationSetTraverser)
.visit(new KMLReportGenerator()); // visitor pattern
• ObservationItem item = ...;
TextView textView = ...;
item.as(Taxon)
.as(TextViewRenderable)
.render(textView);

DCI 26

Example: decorating roles

DCI 27

Q &A

• Question Time

DCI 28

DCI - Data, Context and Interaction @ Jug Lugano May 2011

Recomendados

Recomendados

Más contenido relacionado

Similar a DCI - Data, Context and Interaction @ Jug Lugano May 2011

Similar a DCI - Data, Context and Interaction @ Jug Lugano May 2011 (20)

Más de Fabrizio Giudici

Más de Fabrizio Giudici (16)

Último

Último (20)

DCI - Data, Context and Interaction @ Jug Lugano May 2011