The Architect´s Napkin

Software Architecture on the Back of a Napkin
posts - 69 , comments - 229 , trackbacks - 0

My Links

News

Article Categories

Archives

Post Categories

Image Galleries

June 2014 Entries

The Inkremental Architect´s Napkin - #4 - Make increments tangible
The driver of software development are increments, small increments, tiny increments. With an increment being a slice of the overall requirement scope thin enough to implement and get feedback from a product owner within 2 days max. Such an increment might concern Functionality or Quality.[1] To make such high frequency delivery of increments possible, the transition from talking to coding needs to be as easy as possible. A user story or some other documentation of what´s supposed to get implemented ......

Posted On Thursday, June 12, 2014 5:26 PM | Comments (1) | Filed Under [ The Incremental Architect´s Napkin ]

The Incremental Architect´s Napkin – #3 – Make Evolvability inevitable
The easier something to measure the more likely it will be produced. Deviations between what is and what should be can be readily detected. That´s what automated acceptance tests are for. That´s what sprint reviews in Scrum are for. It´s no small wonder our software looks like it looks. It has all the traits whose conformance with requirements can easily be measured. And it´s lacking traits which cannot easily be measured. Evolvability (or Changeability) is such a trait. If an operation is correct, ......

Posted On Wednesday, June 4, 2014 5:17 PM | Comments (0) | Filed Under [ Software design The Incremental Architect´s Napkin ]

The Incremental Architect´s Napkin - #2 - Balancing the forces
Categorizing requirements is the prerequisite for ecconomic architectural decisions. Not all requirements are created equal. However, to truely understand and describe the requirement forces pulling on software development, I think further examination of the requirements aspects is varranted. Aspects of Functionality There are two sides to Functionality requirements. It´s about what a software should do. I call that the Operations it implements. Operations are defined by expressions and control structures ......

Posted On Monday, June 2, 2014 12:36 PM | Comments (0) | Filed Under [ Software design The Incremental Architect´s Napkin ]

Powered by: