[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"detail-sidebar-cat-1-en-105":3,"doc-seo-242057-105":53,"doc-detail-242057-en":127},{"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":120,"head_meta":122,"extra_data":124,"updated_unix":126},105,"en","managing-software-requirements-second-edition-a-use-case-approach","Managing Software Requirements - Second Edition - A Use Case Approach","","Systematically addresses the problem of software requirements and the high cost of requirements errors, presenting a practical, use-case-driven approach to improving project outcomes. Covers definitions of software requirements and requirements management, then maps requirements work across the software lifecycle, team organization, and business and systems engineering. Guides readers through problem analysis, root-cause thinking, elicitation challenges, and effective workshops, interviewing, brainstorming, storyboarding, and defining systems. Emphasizes structured handling of requirements information and vision documentation for iterative versions.",{"@graph":63,"@context":119},[64,80,102],{"@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":11,"@type":70,"position":76},"https://docshare.wps.com/template/presentations/",3,{"item":78,"name":59,"@type":70,"position":79},"https://docshare.wps.com/template/managing-software-requirements-second-edition-a-use-case-approach/242057/",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/managing-software-requirements-second-edition-a-use-case-approach/242057.png","ImageObject",442,249,{"name":88,"@type":89},"Pentious","Person",{"url":68,"name":91,"@type":92},"DocShare","Organization","application/pdf","2026-10-14","2026-09-12",true,{"@type":98,"interactionType":99,"userInteractionCount":101},"InteractionCounter",{"@type":100},"ViewAction",13,{"@type":103,"mainEntity":104},"FAQPage",[105,111,115],{"name":106,"@type":107,"acceptedAnswer":108},"What is the book’s main goal regarding software requirements?","Question",{"text":109,"@type":110},"The book focuses on reducing requirements errors by understanding their root causes and applying structured requirements management techniques throughout development.","Answer",{"name":112,"@type":107,"acceptedAnswer":113},"How does the book describe requirements work across the software lifecycle?",{"text":114,"@type":110},"It explains how requirements activities fit within traditional and iterative process models, including lifecycle phases, iterations, and relevant disciplines.",{"name":116,"@type":107,"acceptedAnswer":117},"What are the five steps in the problem analysis process?",{"text":118,"@type":110},"They are: gain agreement on the problem definition, understand root causes, identify stakeholders and users, define the solution system boundary, and identify constraints for the solution.","https://schema.org",{"og:url":78,"og:type":121,"og:title":59,"og:site_name":91,"og:description":61},"article",{"robots":123,"canonical":78},"index,follow",{"doc_id":125,"site_id":56},242057,1791744367,{"code":4,"msg":5,"data":128},{"doc_id":125,"user_id":129,"nickname":88,"user_avatar":130,"doc_module":9,"category_id":8,"category_name":11,"doc_title":59,"doc_description":61,"doc_content":131,"file_id":132,"file_url":133,"file_type":134,"file_size":135,"view_count":101,"is_deleted":4,"is_public":9,"is_downloadable":9,"audit_status":9,"page_count":101,"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":140,"read_time":47},1374404730887,"https://ap-avatar.wpscdn.com/davatar_6f874abed73319feea01a86fa6f0fab8","ANAGING SOFTWAREREQUIREMENTSSECOND EDITION  \nA USE CASE APPROACH  \nDEAN LEFFINGWELLDON WIDRIGForeword by Ed Yourdon  \nBO0CHJACOBSONRUMBAUGHSERIES EDITORS  \nsanas  \nForeword  \nxixXXYXxxi  \nPreface to the Second Edition  \nPreface to the First Edition  \nIntroduction  \n15The Goal of Software Development5ALook at the Data6The Root Causes of Project Success and Failure7The Frequency of Requirements Errors9The High Cost of Requirements Errors10Summary13Definitions15What Is a Software Requirement?15What Is Requirements Management?16Application of Requirements Management Techniques17Types of Software Applications17Systems Applications18The Road Map18The Problem Domain19Stakeholder Needs20  \nChapter 1 The Requirements Problem  \nChapter 2 Introduction to Requirements Management  \n15  \nMoving Toward the Solution Domain  \nFeatures of the System  \nSoftware Requirements  \nSummary  \n# Chapter 3 Requirements and the Software Lifecycle\n\nTraditional Software Process ModelsThe Waterfall ModelThe Spiral ModelThe Iterative ApproachLifecycle PhasesIterationsDisciplines  \nRequirements in the Iterative ModelSummary  \n# Chapter 4 The Software Team\n\nSoftware Development as a Team Activity  \nRequisite Team Skills for Effective Requirements ManagementTeam Members Have Different SkillsThe Organization of Software Teams  \n# The Case Study\n\nBackground for the Case Study  \nThe HOLIS Software Development TeamSummary  \nTeam Skill 1 Analyzing the Problem  \n# Chapter 5 The Five Steps in Problem Analysis\n\nStep 1:Gain Agreement on the Problem Definition  \nThe Problem Statement  \nStep 2:Understand the Root Causes—The Problem Behindthe Problem  \nAddressing the Root Cause  \nStep 3:Identify the Stakeholders and the Users  \nStep 4:Define the Solution System Boundary  \nStep 5:Identify the Constraints to Be Imposed on the SolutionSummary  \nLooking Ahead  \n20  \n20  \n21  \n41  \n43  \n21  \n23  \n23  \n24  \n26  \n27  \n28  \n28  \n29  \n30  \n31  \n33  \n34  \n35  \n36  \n36  \n37  \n37  \n38  \n39  \n45  \n45  \n46  \n48  \n50  \n52  \n55  \n57  \n57  \n# Chapter 6 Business Modeling\n\n59  \nThe Purpose of Business Modeling60Using Software Engineering Techniques for Business Modeling60Choosing the Right Technique61The Unified Modeling Language61Business Modeling Using UML Concepts62From the Business Model to the Systems Model64When to Use Business Modeling65Summary65Looking Ahead66  \n# Chapter 7 Systems Engineering of Software-Intensive Systems\n\n67  \nWhat Is Systems Engineering?68Pragmatic Principles of Systems Engineering69The Composition and Decomposition of Complex Systems69Requirements Allocation in Systems Engineering71On Derived Requirements71A Quiet Revolution72When Generations Collide:Graying Baby BoomerMeets Generation X-er73Avoiding the Stovepipe System Problem75When Subsystems Are Subcontracts75Addressing the Conundrum76The Case Study:Systems Engineering for HOLIS77Preliminary User Needs78Problem Analysis78HOLIS:The System,Actors,and Stakeholders80HOLIS Systems Engineering81The Subsystems of HOLIS83Summary85Team Skill 1 Summary86  \n# Team Skill 2 Understanding Userand Stakeholder Needs\n\n87  \n# Chapter 8 The Challenge of Requirements Elicitation\n\n89  \nBarriers to Elicitation90The\"Yes,But\"Syndrome90The“Undiscovered Ruins”Syndrome91The\"User and the Developer\"Syndrome92  \nSummary  \n93  \n95  \n# Chapter 9 The Features of a Product or System\n\n95  \nStakeholder and User Needs  \n96  \nFeatures  \nManaging Complexity by Picking the Level of AbstractionAttributes of Product Features  \n98  \n99  \n99  \nSummary  \n101  \n# Chapter 10 Interviewing\n\nContext-Free Questions102Solutions-Context Questions102The Moment of Truth:The Interview103Compiling the Needs Data106The Analyst's Summary:10+10+10≠30106The Case Study106A Note on Questionnaires107Summary108  \nChapter 11 Requirements Workshops109Accelerating the Decision Process109Preparing for the Workshop110Selling the Concept110  \nEnsuring the Participation of the Right Stakeholders111Attending to Logistics111Providing Warm-Up Materials111Choosing the Facilitator112  ","cbCaid87nlI0voxe","https://ap.wps.com/l/cbCaid87nlI0voxe","pdf",278277,"English","# Preface to the Second Edition\n# Introduction\n## The Goal of Software Development\n## Look at the Data\n## The Root Causes of Project Success and Failure\n# Definitions\n## What Is a Software Requirement?\n## What Is Requirements Management?\n# Chapter 1 The Requirements Problem\n# Chapter 2 Introduction to Requirements Management\n## Moving Toward the Solution Domain\n# Chapter 3 Requirements and the Software Lifecycle\n## Traditional Software Process Models\n## Requirements in the Iterative Model\n# Chapter 4 The Software Team\n## Software Development as a Team Activity\n# Chapter 5 The Five Steps in Problem Analysis\n## Step 1: Gain Agreement on the Problem Definition\n## Step 2: Understand the Root Causes—The Problem Behind the Problem\n## Step 3: Identify the Stakeholders and the Users\n## Step 4: Define the Solution System Boundary\n## Step 5: Identify the Constraints to Be Imposed on the Solution\n# Chapter 6 Business Modeling\n## The Purpose of Business Modeling\n## Using Software Engineering Techniques for Business Modeling\n# Chapter 7 Systems Engineering of Software-Intensive Systems\n## What Is Systems Engineering?\n## Requirements Allocation in Systems Engineering\n# Chapter 8 The Challenge of Requirements Elicitation\n## Barriers to Elicitation\n# Chapter 9 The Features of a Product or System\n## Managing Complexity by Picking the Level of Abstraction\n# Chapter 10 Interviewing\n## Context-Free Questions\n## The Analyst's Summary","[{\"question\":\"What is the book’s main goal regarding software requirements?\",\"answer\":\"The book focuses on reducing requirements errors by understanding their root causes and applying structured requirements management techniques throughout development.\"},{\"question\":\"How does the book describe requirements work across the software lifecycle?\",\"answer\":\"It explains how requirements activities fit within traditional and iterative process models, including lifecycle phases, iterations, and relevant disciplines.\"},{\"question\":\"What are the five steps in the problem analysis process?\",\"answer\":\"They are: gain agreement on the problem definition, understand root causes, identify stakeholders and users, define the solution system boundary, and identify constraints for the solution.\"}]","Managing Software Requirements - Second Edition - A Use Case Approach | PDF",1789185109]