Talking Architects with Len Bass

Sign in to queue

Description

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?

Embed

Download

Download this episode

The Discussion

  • User profile image
    jwwjnr

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

Comments closed

Comments have been closed since this content was published more than 30 days ago, but if you'd like to send us feedback you can Contact Us.