Book Image

Mastering Non-Functional Requirements

By : Sameer Paradkar
Book Image

Mastering Non-Functional Requirements

By: Sameer Paradkar

Overview of this book

Non-functional Requirements are key to any software/IT program and cannot be overlooked or ignored. This book provides a comprehensive approach to the analysis, architecture, and measurement of NFRs. It includes considerations for bespoke Java, .NET, and COTS applications that are applicable to IT applications/systems in different domains. The book outlines the methodology for capturing the NFRs and also describes a framework that can be leveraged by analysts and architects for tackling NFRs for various engagements. This book starts off by explaining the various KPIs, taxonomies, and methods for identifying NFRs. Learn the design guidelines for architecting applications and systems relating to NFRs and design principles to achieve the desired outcome. We will then move on to various key tiers/layers and patterns pertaining to the business, database, and integrating tiers. After this, we will dive deep into the topics pertaining to techniques related to monitoring and measurement of NFRs, such as sizing, analytical modeling, and quality assurance. Lastly, we end the book by describing some pivotal NFRs and checklists for the software quality attributes related to the business, application, data, and infrastructure domains.
Table of Contents (14 chapters)

Chapter 4. Solutions Addressing NFRs

NFRs are the software quality attributes that impact runtime functions, software architecture, and customer experience. NFRs have the potential for application-wide impact across tiers and layers. Some NFRs are related to the design time attributes, while others are specific to runtime, or customer focus. The degree to which the architecture displays amalgamation of software quality attributes, such as scalability or capacity, indicates the success of the architecture and the quality of the overall solution.

When architecting solutions to meet the software quality attributes, it is essential to consider the impact on other NFRs as well. An architect has to analyze the trade-offs between different NFRs as they are interlinked or interdependent. The criticality of each NFR differs from application to application; for example, interoperability will be less critical in a single common off-the-shelf (COTS) application for the retail domain than in a business...