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)

Core architecture patterns


This section describes the core architecture patterns and its impact on NFRs:

Component-based architecture

To create a good starting point for for a scalable application architecture, a typical system may require a product catalog, registration and personalization, online ordering for the e-commerce domain and various information-based applications, such as a retail outlet finder, and online troubleshooting. Each of these must be logically separated to some degree. As part of the separation, each could be implemented on its own hardware as a set of 'collaborating semi-autonomous applications'. However, they must all combine at different times and in various ways to deliver a 'seamless' experience for the end user.

Context

Creating a business application requires many different types of functionalities, as well as high levels of non-functional characteristics, such as availability, manageability, and performance.

Drivers

Drivers for the component-based architecture...