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)

Summary


This chapter outlined the methodology for discovering (elicitating) NFRs. It described a framework that can be leveraged by business analysts/solution architects/SMEs for elicitations of NFRs. The chapter also outlined a framework for prioritization of NFRs. The output of this stage will be the critical input for the solution architecture phase.

The next chapter outlines the solution part of NFRs, providing insights, guidance and principles for architecting NFRs. It covers all the key NFRs that are critical for any project; and, for each NFR, it provides the various alternatives pertaining to the solution and the design principles that need to be applied to achieve the desired outcome; for example, high availability, or scalability, or reliability, and so on. The chapter includes considerations for bespoke (Java, .NET) and COTS applications and are applicable for any IT applications/systems in different domains.