[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"detail-sidebar-cat-1-en-105":3,"doc-seo-240396-105":53,"doc-detail-240396-en":126},{"code":4,"msg":5,"data":6},0,"success",[7,14,19,24,29,34,39,44,49],{"id":8,"doc_module":9,"doc_module_name":10,"category_name":11,"show_sort_weight":12,"slug":13},11,1,"Template","Presentations",90,"presentations",{"id":15,"doc_module":9,"doc_module_name":10,"category_name":16,"show_sort_weight":17,"slug":18},12,"Resumes",80,"resumes",{"id":20,"doc_module":9,"doc_module_name":10,"category_name":21,"show_sort_weight":22,"slug":23},14,"Invoices",70,"invoices",{"id":25,"doc_module":9,"doc_module_name":10,"category_name":26,"show_sort_weight":27,"slug":28},15,"Posters",60,"posters",{"id":30,"doc_module":9,"doc_module_name":10,"category_name":31,"show_sort_weight":32,"slug":33},16,"Social Media",50,"social-media",{"id":35,"doc_module":9,"doc_module_name":10,"category_name":36,"show_sort_weight":37,"slug":38},17,"Forms",40,"forms",{"id":40,"doc_module":9,"doc_module_name":10,"category_name":41,"show_sort_weight":42,"slug":43},18,"Letters",30,"letters",{"id":45,"doc_module":9,"doc_module_name":10,"category_name":46,"show_sort_weight":47,"slug":48},21,"Paper Templates",5,"papers-templates",{"id":50,"doc_module":9,"doc_module_name":10,"category_name":51,"show_sort_weight":4,"slug":52},158,"General","general-158",{"code":4,"msg":54,"data":55},"ok",{"site_id":56,"language":57,"slug":58,"title":59,"keywords":60,"description":61,"schema_data":62,"social_meta":119,"head_meta":121,"extra_data":123,"updated_unix":125},105,"en","non-functional-requirements-nfr-framework","Non-Functional Requirements (NFR) Framework","","This white paper focuses on Non-Functional Requirements (NFR) for IT and IT-enabled business services, proposing enterprise-architecture artifacts that specifically address NFR. It defines an NFR lifecycle and framework, positioning NFR as a reusable set of requirements assets aligned with enterprise architecture planning and requirements management. It also discusses how service non-functional requirements vary across industries while enabling standard templates, dimensions, resiliency tiers, security requirements, and compliance-linked requirements for consistent delivery.",{"@graph":63,"@context":118},[64,80,101],{"@type":65,"itemListElement":66},"BreadcrumbList",[67,71,74,77],{"item":68,"name":69,"@type":70,"position":9},"https://docshare.wps.com","Home","ListItem",{"item":72,"name":10,"@type":70,"position":73},"https://docshare.wps.com/template/",2,{"item":75,"name":51,"@type":70,"position":76},"https://docshare.wps.com/template/general/",3,{"item":78,"name":59,"@type":70,"position":79},"https://docshare.wps.com/template/non-functional-requirements-nfr-framework/240396/",4,{"url":78,"name":59,"@type":81,"image":82,"author":87,"headline":59,"publisher":90,"fileFormat":93,"inLanguage":57,"description":61,"dateModified":94,"datePublished":95,"encodingFormat":93,"isAccessibleForFree":96,"interactionStatistic":97},"DigitalDocument",{"url":83,"@type":84,"width":85,"height":86},"https://docshare.wps.com/thumbnails/non-functional-requirements-nfr-framework/240396.png","ImageObject",442,249,{"name":88,"@type":89},"Cipher","Person",{"url":68,"name":91,"@type":92},"DocShare","Organization","application/pdf","2026-09-20","2026-09-11",true,{"@type":98,"interactionType":99,"userInteractionCount":76},"InteractionCounter",{"@type":100},"ViewAction",{"@type":102,"mainEntity":103},"FAQPage",[104,110,114],{"name":105,"@type":106,"acceptedAnswer":107},"What is the main purpose of the Non-Functional Requirements (NFR) Framework?","Question",{"text":108,"@type":109},"It defines and explains NFR for IT and IT-enabled business services and proposes enterprise architecture artifacts tailored to address NFR. It also provides an NFR lifecycle and framework to support requirements management.","Answer",{"name":111,"@type":106,"acceptedAnswer":112},"How does the framework relate to enterprise architecture and requirements management?",{"text":113,"@type":109},"It emphasizes alignment between business goals and IT capabilities and frames requirements management as the central element of architecture efforts. It positions NFR artifacts as key, reusable assets across enterprise architecture projects.",{"name":115,"@type":106,"acceptedAnswer":116},"How can organizations standardize non-functional requirements across varying industries?",{"text":117,"@type":109},"It highlights that while service functional and non-functional requirements vary by industry and business function, organizations can create standardized templates. These include NFR dimensions, resiliency tiers with metric targets, data security requirements, and compliance-related requirement sets.","https://schema.org",{"og:url":78,"og:type":120,"og:title":59,"og:site_name":91,"og:description":61},"article",{"robots":122,"canonical":78},"index,follow",{"doc_id":124,"site_id":56},240396,1789160932,{"code":4,"msg":5,"data":127},{"doc_id":124,"user_id":128,"nickname":88,"user_avatar":129,"doc_module":9,"category_id":50,"category_name":51,"doc_title":59,"doc_description":61,"doc_content":130,"file_id":131,"file_url":132,"file_type":133,"file_size":134,"view_count":76,"is_deleted":4,"is_public":9,"is_downloadable":9,"audit_status":9,"page_count":135,"language":136,"language_code":57,"site_id":56,"html_lang":57,"table_of_contents":137,"faqs":138,"seo_title":139,"seo_description":61,"update_tm":125,"read_time":140},687208528416,"https://ap-avatar.wpscdn.com/davatar_9964176cb1d06d4a9deccf72a44ae3dc","Non-Functional Requirements (NFR) Framework  \nA Subset of the Enterprise Architecture Framework  \nA White Paper by: Rajesh Radhakrishnan  \nSr. Managing Consultant/Sr. IT Architect  \nIBM Global Technology Services  \nSeptember 2009  \nNon-Functional Requirements (NFR) Framework  \nCopyright © 2009 The Open Group  \nAll rights reserved. No part of this publication may be reproduced, stored in a retrieval system, or transmitted, in any form or by any means, electronic, mechanical, photocopying, recording, or otherwise, without the prior permission of the copyright owners.  \nThis White Paper is an informational document and does not form part of the TOGAF documentation set. Readers should note that this document has not been approved through the formal Open Group Standards Process and does not represent the formal consensus of The Open Group Architecture Forum.  \nITIL® is a registered trademark of the UK Office of Government Commerce (OGC) .  \nBoundaryless Information Flow™ and TOGAF™ are trademarks and Making Standards Work®, The Open Group®, UNIX®, and the “X” device are registered trademarks ofThe Open Group in the United States and other countries.  \nAll other brand, company, and product names are used for identification purposes only and may be trademarks that are the sole property of their respective owners.  \nNon-Functional Requirements (NFR) Framework  \nDocument No.: W098  \nPublished by The Open Group, September 2009  \nAny comments relating to the material contained in this document may be submitted to:  \nThe Open Group  \n44 Montgomery St. \\#960  \nSan Francisco, CA 94104 or by email to:  \n[ogspecs@opengroup.org](ogspecs@opengroup.org)  \nComments on the content of this document may be submitted to the author at:  \n[rajesh.radhakrishnan@us.ibm.com](rajesh.radhakrishnan@us.ibm.com)  \n[www.opengroup.org](www.opengroup.org)  A White Paper Published by The Open Group 2  \nNon-Functional Requirements (NFR) Framework  \nTable of Contents  \nExecutive Summary 4  \nIntroduction 5  \nStakeholders for Non-Functional Requirements 7  \nNon-Functional Requirements for What? 8  \nService Non-Functional Requirements and Service Lifecycle 9  \nService Design and Development.......................................................................9  \nService Transition...............................................................................................9  \nService Operations ........................................................................................... 10  \nService Improvement........................................................................................ 10  \nArriving at Requirements 12  \nService Quality Dimensions (Service Non-Functional  \nRequirements) 13  \nPrioritizing Non-Functional Requirements 15  \nNFR Lifecycle 16  \nAnalysis and Planning for Non-Functional Requirements ............................... 16  \nArchitecture for Non-Functional Requirements ............................................... 17  \nEngineering for Non-Functional Requirements................................................ 17  \nOperating for Non-Functional Requirements ................................................... 17  \nNon-Functional Requirements-Related Monitoring ......................................... 18  \nNon-Functional Requirements-Related Improvements .................................... 18  \nSummary .......................................................................................................... 19  \nService Performance and Capacity...................................................................20  \nNFR Framework 22  \nService Availability ..........................................................................................23  \nService Continuity ............................................................................................25  \nReferences 26  \nAbout the Author 27  \nAbout The Open Group 27  \n[www.opengroup.org](www.opengroup.org)  A White Paper Published by The Open Group 3  \nNon-Functional Requirements (NF","cbCaiu8CzqAFZa0p","https://ap.wps.com/l/cbCaiu8CzqAFZa0p","pdf",1247389,27,"English","# Executive Summary\n# Introduction\n# Stakeholders for Non-Functional Requirements\n# Non-Functional Requirements for What?\n# Service Non-Functional Requirements and Service Lifecycle\n## Service Design and Development\n## Service Transition\n## Service Operations\n## Service Improvement\n# Arriving at Requirements\n# Service Quality Dimensions (Service Non-Functional Requirements)\n# Prioritizing Non-Functional Requirements\n# NFR Lifecycle\n## Analysis and Planning for Non-Functional Requirements\n## Architecture for Non-Functional Requirements\n## Engineering for Non-Functional Requirements\n## Operating for Non-Functional Requirements\n## Non-Functional Requirements-Related Monitoring\n## Non-Functional Requirements-Related Improvements\n# Summary\n# Service Performance and Capacity\n# Service Availability\n# Service Continuity\n# References\n# About the Author\n# About The Open Group","[{\"question\":\"What is the main purpose of the Non-Functional Requirements (NFR) Framework?\",\"answer\":\"It defines and explains NFR for IT and IT-enabled business services and proposes enterprise architecture artifacts tailored to address NFR. It also provides an NFR lifecycle and framework to support requirements management.\"},{\"question\":\"How does the framework relate to enterprise architecture and requirements management?\",\"answer\":\"It emphasizes alignment between business goals and IT capabilities and frames requirements management as the central element of architecture efforts. It positions NFR artifacts as key, reusable assets across enterprise architecture projects.\"},{\"question\":\"How can organizations standardize non-functional requirements across varying industries?\",\"answer\":\"It highlights that while service functional and non-functional requirements vary by industry and business function, organizations can create standardized templates. These include NFR dimensions, resiliency tiers with metric targets, data security requirements, and compliance-related requirement sets.\"}]","Non-Functional Requirements (NFR) Framework | PDF",9]