Content tagged with: non-functional
This video explains how to use agile practices to incrementally introduce non-functional requirements into the architecture in order to reduce the complexity of the solution. Non-functional requirements relate to qualities of the system that cut across user facing features, such as security, reliability, and performance. These requirements affect the system and it is possible to design tests that these qualities are present.
This article presents new concepts to formalize and apply non-functional requirements (NFR) for business processes in the context of Service-Oriented Architectures (SOA). Today, popular languages for modeling business processes do not support the specification of NFRs in a systematic manner. However, there is a strong demand to explicitly address such requirements when designing and deploying software systems.
In this blog post, Mike Cohn explains that for non-functional requirement you should estimate both the costs of initial compliance and then the costs of ongoing compliance.
The blog post “Non-functional requirements… the forgotten, overlooked and underestimated” discusses the role and impact of non-functional requirements in software projects.
This interesting article by Rachel Davies discusses if user stories can be used to express non functional requirements in agile software development projects.
Agile is all about closing the gap between business and software development. Agile teams work closely with a Product Owner who prioritizes user stories on their business value. So how does a team make sure they don’t lose sight of “non-functional requirements”?
This blog post is about understanding what non-functional requirements are, how they work, how to write them, and how to use them in real-life projects,