Sign In Start Free Trial
Account

Add to playlist

Create a Playlist

Modal Close icon
You need to login to use this feature.
  • Book Overview & Buying Mastering Non-Functional Requirements
  • Table Of Contents Toc
Mastering Non-Functional Requirements

Mastering Non-Functional Requirements

By : Paradkar
4.2 (10)
close
close
Mastering Non-Functional Requirements

Mastering Non-Functional Requirements

4.2 (10)
By: 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 (8 chapters)
close
close

NFR - Sizing


Software Non-functional Assessment Process (SNAP), a measurement of non-functional software size. SNAP point sizing is a complement to a function point sizing, which measures functional software size. It is a product of the International Function Point Users Group (IFPUG), and is sized using the SNAP manual.

The overall size of software consists of separate components, functional and non-functional, for example, 400 function points and 200 SNAP points. The two sizes do not sum up to one single size. The IFPUG functional sizing methodology does not change when measuring the non-functional requirements using SNAP. Non-functional sizing requires recognition of similar artifacts of software used to measure functional size, for example, data element types (DETs) and file types referenced (FTRs).

Separating functional and non-functional requirements is important when performing a cost forecast (or other forecast, such as scheduling or staffing) for software development. In principle...

Visually different images
CONTINUE READING
83
Tech Concepts
36
Programming languages
73
Tech Tools
Icon Unlimited access to the largest independent learning library in tech of over 8,000 expert-authored tech books and videos.
Icon Innovative learning tools, including AI book assistants, code context explainers, and text-to-speech.
Icon 50+ new titles added per month and exclusive early access to books as they are being written.
Mastering Non-Functional Requirements
notes
bookmark Notes and Bookmarks search Search in title playlist Add to playlist font-size Font size

Change the font size

margin-width Margin width

Change margin width

day-mode Day/Sepia/Night Modes

Change background colour

Close icon Search
Country selected

Close icon Your notes and bookmarks

Confirmation

Modal Close icon
claim successful

Buy this book with your credits?

Modal Close icon
Are you sure you want to buy this book with one of your credits?
Close
YES, BUY

Submit Your Feedback

Modal Close icon
Modal Close icon
Modal Close icon