Add a comment

 

Re: Mapping software architecture to code

Great, you´re trying to bring light weight design to teams. However, what I´m missing is how the impedance mismatch between agility and code is addressed. All (?) the drawings just show technical views of software. Essentially it's about "component" dependencies. The nesting is deep. Logic is distributed across all "layers". But where are the user stories? Or any increment for that matter. They seem to be dissolved like sugar in a cup of coffee. It sounds as if once developers get their hands on requirements they get implemented - but it becomes hard to find the implementation. That makes understanding software difficult. And it makes software hard to change, I´d say.

Re: Mapping software architecture to code


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).