Tracking change and innovation in the enterprise software development community
Free Book Offer
SOA Demystified
$40 Value
Scaling Scrum
in the enterprise?
ScrumWorks Pro
can help.
Start a trial today
QCon London 2010!
March 10-12, 100
Speakers, 80 sessions,
"THE" team leads and,
architects conference.
Recorded at:
Presented by Rebecca Wirfs-Brock on Jan 24, 2009
Technical Debt and Design Death
Agile Development: A Manager's Roadmap for Success
Regaining control of the data centre
Unix, Linux Uptime & Reliability Increase While Patch Management Woes Plague Windows (Yankee Group)
Funny, I thought that requirements are the main driving force for the design.
Author made me fill like I was blind all these years...
Kidding aside, all these forces author mentions are secondary forces, while requirements should be the primary and the commanding force.
Of course requirements drive design, but in this talk I wanted to explore the values and practices that various "driven" methods have, their roots, and what they share in common and where they conflict.
It is all too simple to say "requirements drive design" and be done with it. What I am constantly amazed at are the myriad different ways people tackle software problems and all those subtle choices they make when crafting their solutions. I think it is good to reflect from time to time on why we do software design the way we do as well as what we personally value. I've just written a blog posting that might spur some discussion on this. www.wirfs-brock.com/2009/01/what-drives-design....
Curious thing that organizations sometimes missuse the word requirement, making it very difficult to understand the real needs. I have come across too many self acclaimed System Architects that "drive design" by requirement.
From Rebeccas blog; "But what then drives the way you approach your work?"
To me it is about implementing the design principles that Robert C Martin writes about in this article; www.objectmentor.com/resources/articles/Princip... . As he writes in the article I think it will help me create something which is "...flexible, robust, reusable, and developable.".
Is it a common and clear goal for all of the the design drivers to implement those principles?
I think that most of the people who have advocated xDD approaches and even talk about use of patterns or refactoring techniques are all trying to get at SOLID (or solid) design. They just have different emphasis and also a slightly different set of values. For example, Domain Driven Design from Eric Evans talks a lot about capturing the "ubiquitous" language of the domain and representing it in domain objects. While Robert Martin's principles lead you more towards well-structured organizations of objects and good use of inheritance and interfaces.
Most designers and design approaches I know wouldn't argue much w/ Martin's principles.
Brian Marick takes us through a quick tour of the most important values and challenges to adopting Agile successfully (they aren't the typical challenges and values we hear in the community).
The line between development and architecture is tricky. Does it exist at all? Is an ivory tower actually needed? There's a balance in the middle, but how do you move from developer to architect?
The word 'authority' sometimes produces an allergic response in hard-line agilists. Freedom and authority – both are bad if misused and both are good if used in right spirit for a noble cause.
"Getting Started with Grails" brings you up to speed on this modern web framework. Companies as varied as LinkedIn, Wired, and Taco Bell are all using Grails. Are you ready to get started as well?
Those familiar with only ITIL V2 often scoff at the thought that ITIL could serve as a governance framework for SOA. With ITIL V3, the focus of the framework shifted towards service-orientation.
SpringSource CTO Adrian Colyer discusses AspectJ, SpringSource's dm Server and tc Server products, OSGi and Scrum.
Heroku's Adam Wiggins talks about Rails, Background Jobs, Add-Ons, Ruby, and how Heroku manages to work around Ruby's inefficiencies using Erlang and other languages.
For Grady Booch the foundation of a good architecture is patterns, SOA being just one of many patterns. In this Second Life presentation, Booch attempts to bring more clarity on what architecture is.
5 comments
Watch Thread Reply