| A common challenge with
agile software development is how to address non-functional
requirements. A non-functional requirement specifies "how well" the
"what" must behave. Also known as "technical requirements",
"quality attributes" or "quality of service requirements", they
focus on characteristics that typically cut across functional
requirements such as usability, correctness, reliability,
maintainability, availability, performance, portability,
testability and many others. As you can see from that list,
non-functional requirements are often referred to as "-ilities"
because of the suffix many of the words share. Improperly dealing
with non-functional requirements leads to the source code difficult
to evolve or software with an unpleasant execution quality. During
this session, you will learn the agile practices to transform these
recurring concerns into self-contained quality targets that can be
satisfied iteration after iteration, in a finite period of time.
Overall, you will acquire a different perspective on how to connect
requirements and architecture using agile practices. |
Download the presentation deck here.
