The Blog
Features that do not fit into architecture
published August 12, 2010
So you got an application. You have analyzed business requirements and coded a domain model that represents business domain from some perspective. You start building features on that model and it all seems to work out pretty well. Then you get the first requirement that does not fit into the domain model and you will have to make a special rule for this case. You decide to solve this by writing logic for it into your UI layer. And so it begins, your code starts to rot.
These “special cases” are very nasty. Root cause for them is usually a mismatch between domain model and business requirement. Building a domain model that can handle beautifully all special rules is very, very hard and will require multiple iterations. However, when you notice a feature that needs a special rule, it is wise to inform your product owner about it and try to come up with a solution that works with current domain model and does not cause your code to rot.
No Comments to Features that do not fit into architecture
Subscribe to RSS feed
The Tag Cloud
Agile Business Coaching Coding horror Conference Customer Design of Experiments Future Group dynamics ITIL It should not be that hard Java EE Kanban Leadership Lean Liferay Methodologies Natural UI Performance tuning Process Productivity Quality Retrospective RIA Scrum Six Sigma Social psychology Software Software architecture Testing This is great TOGAF
WP Cumulus Flash tag cloud by Roy Tanck and Luke Morton requires Flash Player 9 or better.
Samuli's Links
The Blog Archive
February 2012 (1)
January 2012 (1)
November 2011 (1)
June 2011 (2)
May 2011 (1)
April 2011 (2)
March 2011 (2)
February 2011 (1)
January 2011 (1)
December 2010 (1)
November 2010 (1)
October 2010 (3)
September 2010 (3)
August 2010 (5)
July 2010 (2)
June 2010 (3)
May 2010 (4)
April 2010 (2)
March 2010 (6)
February 2010 (7)
January 2010 (3)
December 2009 (7)
November 2009 (6)
