Talking Architects with Len Bass
- Posted: Oct 28, 2009 at 4:54 AM
- 6,928 Views
- 1 Comment
Quality Attributes (Non-functional requirements) as first class citizens of a project? Too far fetched?
Len Bass, co-author of
Software Architecture in Practice and longstanding member of the Software Engineering Institute (SEI), thinks he has an answer.
But how does this fit in an agile world?
But how does this fit in an agile world?
Comments Closed
Comments have been closed since this content was published more than 30 days ago, but if you'd like to continue the conversation,
please create a new thread in our Forums,
or
Contact Us and let us know.
More posts in this blog
-
Talking Architects with Len Bass
-
Talking Architects - Neil Ward-Dutton
-
Talking Architects - Angela Yochem
Follow the Discussion
Oops, something didn't work.
What does this mean?
Following an item on Channel 9 allows you to watch for new content and comments that you are interested in. You need to be signed in to Channel 9 to use this feature.What does this mean?
Following an item on Channel 9 allows you to watch for new content and comments that you are interested in and view them all on your notifications page.sign up for email notifications?
Learning to express NFR's in a form which is useful to the project is a good thing. However, the software domain is hard to measure - when did you last see a set of performance figures for a third party library, a protocol or a comms. channel ? That is, actual numbers and real world data which allow you to make "on the project" decisions ? So ! - knowing the behaviour of one component is very tricky, build a full stack for a complex application and it gets real difficult. So - rank those use cases, get early code delivery on a high risk use case, then spend HOWEVER MUCH TIME IT TAKES getting that use case to comply with the NFR's as best you can. Realising the remaining use cases is a piece of cake...?
Remove this comment
Remove this thread
close