Reference architectures
August 19, 2009 colink
Zapthink remind us of the value of reference architectures.
The Ujuzi take (with apologies):
- build on a pre-existing reference architecture where possible (this is the standing on the shoulders of giants bit)
- if you are committed to a vendor’s product, decide how deeply you are prepared to entrench it in your architecture and then build on their best practices for the chosen bits
- maintain a register of lessons learned (and solutions) as you go through projects
- document antipatterns and how to avoid them
- document new patterns and how to apply them
- document what doesn’t work as advertised – whether it is a vendor product capability or just an architectural approach
- PoC, PoC, PoC
Filed under: Uncategorized

Leave a Comment
XHTML: You can use these tags: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>
TrackBack URL | RSS feed for comments on this post.