Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Save more on your purchases! discount-offer-chevron-icon
Savings automatically calculated. No voucher code required.
Arrow left icon
All Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Newsletter Hub
Free Learning
Arrow right icon
timer SALE ENDS IN
0 Days
:
00 Hours
:
00 Minutes
:
00 Seconds
Arrow up icon
GO TO TOP
Mastering Non-Functional Requirements

You're reading from   Mastering Non-Functional Requirements Templates and tactics for analysis, architecture and assessment

Arrow left icon
Product type Paperback
Published in May 2017
Publisher
ISBN-13 9781788299237
Length 230 pages
Edition 1st Edition
Arrow right icon
Author (1):
Arrow left icon
 Paradkar Paradkar
Author Profile Icon Paradkar
Paradkar
Arrow right icon
View More author details
Toc

Table of Contents (14) Chapters Close

Title Page
Credits
About the Author
About the Reviewer
www.PacktPub.com
Customer Feedback
Preface
1. Understanding NFRs 2. Taxonomy and Framework for NFRs FREE CHAPTER 3. Methodology Eliciting - Non Functional Requirements 4. Solutions Addressing NFRs 5. Architectural Patterns and its Impact on NFRs 6. Sizing, Measurement and Monitoring 7. Understanding Pivotal NFRs and Closing Thoughts

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...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $15.99/month. Cancel anytime
Visually different images