Add a comment

 

Design Decisions document

I just listened to your talk on the role of a Software Architect on InfoQ. I'm a software testing and QA guy. On one project, I decided to write a Design Decisions document as the project evolved. This was very technical, but was designed to give context as to why a feature was implemented a certain way. This came about as certain features seemed odd to me and wasn't sure why they worked the way they worked - was it some technical limitation that forced this decision? I don't know if this practice was continued after I left the company - I doubt it.

Design Decisions document


Title
Body
HTML : b, strong, i, em, blockquote, br, p, pre, a href="", ul, ol, li, sub, sup
Name
E-mail address
Website
Remember me Yes  No 

E-mail addresses are not publicly displayed, so please only leave your e-mail address if you would like to be notified when new comments are added to this blog entry (you can opt-out later).