Position Papers

[Corey Haines]

Well, I finally got my head enough in place to actually register and
write a small blurb about what I'm looking to talk about. And I even
got a pretty delegate number!

Are we planning on putting these blurbs up on the wiki somewhere, so
we can have some thoughts formed about other people's ideas?

Here's mine:

I've been thinking a lot lately about the effect of behavior-focused
development/design on the standard object-oriented constructs. For
example:
When using functional-style concepts in an OO language, where an
object is a container for similarly focused behaviors, what is the
role of the constructor? Could it be considered a currying function?
Does a traditional n-tier (i.e. presentation, business, data
layer-oriented) system truly fit a behavior-oriented, test-driven
system. What are the roles of layers as refactoring brings more and
more abstractions out?
How do you decide when to split a collection of behaviors into several
objects? What is meant by responsibility when creating behavior-based
constructs in an object-oriented system?

These are some of the thing that I've been thinking about in my
day-to-day job over the last year, and I'd like to explore with some
of the great people at SDTConf.

-Corey