[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"detail-sidebar-cat-1-en-105":3,"doc-seo-241967-105":53,"doc-detail-241967-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","mastering-the-requirements-process-second-edition","Mastering the Requirements Process - Second Edition","","Mastering the Requirements Process presents a practical, end-to-end approach for discovering, organizing, and validating software and business requirements. The second edition structures the work around an explicit requirements process, including requirements gathering, systems modeling, and agile use-case thinking. It guides teams through defining scope and stakeholders, trawling the work for requirements, writing scenario-driven specifications, and transforming requirements into measurable fit criteria. Coverage also spans functional and nonfunctional requirements types, quality review, reuse, iterative refinement, and project retrospective practices.",{"@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/mastering-the-requirements-process-second-edition/241967/",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/mastering-the-requirements-process-second-edition/241967.png","ImageObject",442,249,{"name":88,"@type":89},"Finn","Person",{"url":68,"name":91,"@type":92},"DocShare","Organization","application/pdf","2026-09-20","2026-09-12",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 does the book mean by a “requirements process”?","Question",{"text":108,"@type":109},"It refers to a structured approach for gathering, organizing, and validating requirements, supported by templates and review practices. The book also frames this process in agile context so teams can apply it iteratively.","Answer",{"name":111,"@type":106,"acceptedAnswer":112},"How does the book distinguish functional and nonfunctional requirements?",{"text":113,"@type":109},"Functional requirements describe what the product must do, while nonfunctional requirements specify quality attributes such as usability, performance, security, maintainability, and legal or cultural constraints. The text also discusses granularity and ways to avoid ambiguity.",{"name":115,"@type":106,"acceptedAnswer":116},"What are “fit criteria” used for?",{"text":117,"@type":109},"Fit criteria turn requirements into something unambiguous and testable by defining how measurement will be performed. They support both objective tests for nonfunctional requirements and test case development for functional requirements.","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},241967,1789183939,{"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},34359740700684,"https://ap-avatar.wpscdn.com/avatar/1f400023980c374ae676?_k=1777273430885731487","Mastering the Requirements Process Second Edition  \nMastering the Requirements Process Table of Contents  \nContents  \nPreface to the Second Edition Foreword to the First Edition Acknowledgments  \n1 What Are Requirements? in which we consider why we are  \ninterested in requirements Requirements Gathering and Systems Modeling Agile Software Development  \nWhy Do I Need Requirements?  \nWhat Is a Requirement?  \nFunctional Requirements  \nNonfunctional Requirements  \nConstraints  \nEvolution of Requirements  \nThe Template  \nThe Shell  \nThe Volere Requirements Process  \n2 The Requirements Process: in which we look at a process forgathering requirements and discuss how you might use it  \nAgility Guide  \nRequirements Process in Context  \nThe Process  \nA Case Study  \nTable of Contents  \nProject Blastoff Trawling for Requirements  \nPrototyping the Requirements  \nScenarios  \nWriting the Requirements  \nThe Quality Gateway  \nReusing Requirements  \nReviewing the Specification  \nIterative and Incremental Processes  \nRequirements Retrospective  \nYour Own Requirements Process  \nIn Conclusion  \n3 Project Blastoff: in which we establish a solid foundation for the requirements, and ensure that the members of the project team all start rowing in the same direction  \nAgility Guide  \nIceBreaker  \nScope, Stakeholders, Goals  \nSetting the Scope  \nDomains of Interest  \nFirst-Cut Work Context Stakeholders  \nThe Client  \nThe Customer  \nThe Users: Get to Know Them Other Stakeholders  \nConsultants  \nManagement  \nTable of Contents  \nSubject Matter Experts  \nCore Team  \nInspectors  \nMarket Forces  \nLegal  \nNegative Stakeholders  \nIndustry Standard Setters  \nPublic Opinion  \nGovernment  \nSpecial-Interest Groups  \nTechnical Experts  \nCultural Interests  \nAdjacent Systems Finding the Stakeholders  \nGoals: What Do You Want to Achieve?  \nKeeping Track of the Purpose Requirements Constraints  \nSolution Constraints  \nProject Constraints  \nNaming Conventions and Definitions  \nHow Much Is This Going to Cost?  \nRisks  \nTo Go or Not to Go  \nBlastoff Alternatives  \nSummary  \n4 Event-Driven Use Cases: in which we discuss a fail-safe way of partitioning the work into use cases, and along the way discover the best product to build  \nAgility Guide  \nTable of Contents  \nUnderstanding the Work  \nUse Cases and Their Scope  \nThe Work  \nThe Context of the Work  \nThe Outside World Business Events  \nTime-Triggered Business Events  \nWhy Business Events and Business Use Cases Are a Good Idea  \nFinding the Business Events  \nBusiness Use Cases  \nThe Role of Adjacent Systems  \nActive Adjacent Systems  \nAutonomous Adjacent Systems  \nCooperative Adjacent Systems  \nBusiness Use Cases and Product Use Cases  \nActors Summary  \n5 Trawling for Requirements: in which we drag the net through the work area looking for requirements, and discuss some useful techniques for doing so  \nAgility Guide  \nResponsibility  \nThe Requirements Analyst Trawling and Business Use Cases The Role of the Current Situation Apprenticing  \nObserving Structures and Patterns  \nInterviewing the Stakeholders  \nTable of Contents  \nAsking the Right Questions Getting to the Essence of the Work Solving the Right Problem Innovative Products  \nBusiness Use Case Workshops  \nOutcome  \nScenarios  \nBusiness Rules Creativity Workshops Brainstorming Personas  \nMind Maps  \nWallpaper  \nVideo and Photographs  \nWikis, Blogs, and Discussion Forums  \nDocument Archeology  \nSome Other Requirements-Gathering Techniques  \nFamily Therapy  \nSoft Systems and Viewpoints Determining What the Product Should Be  \nThe True Origin of the Business Event Does Technology Matter?  \nChoosing the Best Trawling Technique  \nSummary  \n6 Scenarios and Requirements: in which we look at scenarios as away of helping the stakeholders to discover their requirements  \nAgility Guide  \nScenarios  \nTable of Contents  \nNormal Case Scenarios  \nDiagramming the Scenario  \nAlternative Cases  \nException Cases  \nWhat If? Scenarios  \nMisuse Cases and Negative Scenarios  \nScenario Te","cbCaiuV4UrS6RMME","https://ap.wps.com/l/cbCaiuV4UrS6RMME","pdf",199205,24,"English","# Preface to the Second Edition\n# Foreword to the First Edition\n# Acknowledgments\n# What Are Requirements?\n## Requirements Gathering and Systems Modeling\n## Why Do I Need Requirements?\n## What Is a Requirement?\n## Functional Requirements\n## Nonfunctional Requirements\n## Constraints\n## Evolution of Requirements\n## The Template\n# The Requirements Process\n## Agility Guide\n## Requirements Process in Context\n## The Process\n## A Case Study\n## Project Blastoff\n# Project Blastoff\n## Scope, Stakeholders, Goals\n## Goals: What Do You Want to Achieve?\n# Event-Driven Use Cases\n## Understanding the Work\n## Use Cases and Their Scope\n# Trawling for Requirements\n## Interviewing the Stakeholders\n## Document Archeology\n# Scenarios and Requirements\n## Normal Case Scenarios\n# Functional Requirements\n## Finding the Functional Requirements\n# Nonfunctional Requirements\n## Look and Feel Requirements\n## Performance Requirements\n# Fit Criteria\n## Why Does Fit Need a Criterion?","[{\"question\":\"What does the book mean by a “requirements process”?\",\"answer\":\"It refers to a structured approach for gathering, organizing, and validating requirements, supported by templates and review practices. The book also frames this process in agile context so teams can apply it iteratively.\"},{\"question\":\"How does the book distinguish functional and nonfunctional requirements?\",\"answer\":\"Functional requirements describe what the product must do, while nonfunctional requirements specify quality attributes such as usability, performance, security, maintainability, and legal or cultural constraints. The text also discusses granularity and ways to avoid ambiguity.\"},{\"question\":\"What are “fit criteria” used for?\",\"answer\":\"Fit criteria turn requirements into something unambiguous and testable by defining how measurement will be performed. They support both objective tests for nonfunctional requirements and test case development for functional requirements.\"}]","Mastering the Requirements Process - Second Edition | PDF",8]