Tagged articles
requirement analysis
44 articles · Page 1 of 1
Through two case studies, this article outlines the five core responsibilities of product managers: identifying real user problems behind feature requests, scoping requirements with clear boundaries, designing detailed solutions for cross-team collaboration, validating implementations against full business flows, and measuring post-launch impact to drive the next iteration.
Acceptance Testingfeature prioritizationiteration planning
0 likes · 11 min read

This article outlines a comprehensive methodology for data planning, covering historical context, requirement analysis with subtractive thinking, Data Requirements Document (DRD) design, data flow diagrams, data dictionaries, and internal versus external data collection strategies including web scraping considerations.
DRDbig datadata collection
0 likes · 15 min read

The article demonstrates how the pyramid principle — conclusion-first, categorized grouping, and layered decomposition — turns vague client requests into structured, verifiable AI prompts, using a contract bulk-import example to show a four-level breakdown from delivery conclusion to executable tasks.
AI collaborationAI promptingacceptance criteria
0 likes · 21 min read

This article details how to engineer a production‑grade AI requirement‑analysis engine using a modular Skills framework, covering problem definition, architecture, compilation pipeline, conflict detection, impact analysis, scalability, multi‑tenant governance, and deployment best practices.
AIKnowledge RetrievalLLM
0 likes · 34 min read


We-DesignJul 6, 2026 · User Experience Design
The article examines how AI can quickly decompose requirements but stresses that designers must distinguish facts from assumptions, organize judgment criteria, and make AI's analysis traceable and continuously verifiable to avoid misleading conclusions.
AIHuman Interface Guidelinesdesign process
0 likes · 16 min read

Misunderstandings between developers and product managers often stem from talking past each other, but by clarifying goals, using business language for technical complexity, estimating with concrete breakdowns, assessing change impact promptly, and reviewing issues together, teams can turn collaboration into a strategic advantage.
communicationproduct-managerrequirement analysis
0 likes · 6 min read

This article shares a step‑by‑step framework for systematically discovering hidden user requirements in rule‑intensive B2B applications, using real‑world case studies, the McGovern iceberg model, four investigative dimensions, and funnel‑style questioning to turn vague requests into concrete, auditable features.
B2B Product ManagementFMEATask Analysis
0 likes · 20 min read

This guide explains how B2B product managers can handle everything from multi‑system integration projects to a single‑click UI tweak by classifying requirements into three levels, applying appropriate documentation depth, and using stakeholder maps, value‑driven goals, and lightweight specs to keep PRDs both rigorous and agile.
Agile DocumentationB2BPRD
0 likes · 9 min read

The article explains how test engineers can shift from passive quality checkers to proactive quality guarantors by preparing before reviews, asking targeted questions on testability, completeness, edge cases, and non‑functional needs during requirement meetings, and following up with clear issue lists, early test design, and continuous communication.
quality assurancerequirement analysissoftware testing
0 likes · 6 min read

The article outlines a step‑by‑step process for software test engineers to analyze product requirements, design comprehensive test cases, conduct peer reviews, and continuously maintain them, while also providing a concrete case study that shows how to handle ambiguous or unreasonable specifications through proactive communication and risk mitigation.
QA processTest Case Designrequirement analysis
0 likes · 9 min read

This guide walks product managers through the full lifecycle of requirement analysis, management, prioritization, delivery, and verification, emphasizing data‑driven decisions, multi‑dimensional evaluation, clear acceptance criteria, and continuous feedback loops to ensure products truly solve user problems and align with business goals.
deliveryfeedback loopprioritization
0 likes · 7 min read

This article guides engineers on evolving from merely executing requirements to creating business value by understanding the entire product lifecycle—covering requirement discovery, collaborative design, safe release, data‑driven operation, and continuous personal growth—offering practical questions and actionable principles for each stage.
Design PrinciplesR&D mindsetcareer growth
0 likes · 11 min read

Autogen_demo, built with Streamlit and AI technologies, offers an end‑to‑end solution that parses PDF or Word requirements, stores them in a version‑controlled database, and automatically generates comprehensive functional, boundary, and exception test cases, exportable as Excel, Markdown, or JSON, boosting efficiency for developers, testers, and analysts.
AIStreamlitTest Case Generation
0 likes · 8 min read

This article explains how product managers can distinguish genuine needs from superficial feature requests, uncover underlying pain points, quantify expectations, and define clear success metrics, using practical examples like a customer asking for an ice cream versus needing temperature relief.
business valuefeature prioritizationproduct management
0 likes · 7 min read

This article explores the definition of business, why it is often hard to grasp, the undeniable need for developers to understand it, the benefits of such understanding, and practical step‑by‑step methods—including implementation, requirement, business, and industry perspectives—to bridge the gap between technology and real‑world needs.
R&D managementbusiness understandingproduct collaboration
0 likes · 10 min read

This article explores comprehensive requirement analysis techniques for game testing, covering document analysis, mind‑mapping, 5W1H expansion, equivalence class handling, risk mitigation, and implementation details, aiming to improve test case creation, reduce ambiguities, and ensure smoother cross‑functional reviews and overseas releases.
QAgame developmentgame testing
0 likes · 16 min read

This article explains how to transform business modeling into concrete requirements by analyzing a face‑recognition payment system for school canteens, covering vision definition, target organization identification, goal measurement, use‑case modeling, and detailed use‑case specifications to ensure valuable, well‑scoped software development.
Business ModelingUse Caseface recognition
0 likes · 29 min read

The article presents a systematic method for converting business modeling into precise, measurable software requirements by illustrating a face‑recognition payment system for a school canteen, detailing how to identify the target organization and decision‑maker, define improvement metrics such as cutting payment time from five to three minutes, and develop a complete use‑case specification that aligns with organizational value.
case studyface recognitionpayment system
0 likes · 29 min read


DevOpsNov 16, 2023 · Product Management
This article presents a comprehensive five‑step, thirteen‑element framework for analyzing B2B product requirements, illustrated with a CRM message‑center case study, detailed role analysis, scenario reconstruction, and practical design recommendations for product managers.
B2BCRMrequirement analysis
0 likes · 31 min read

The article shows how AI large‑language models such as ChatGPT can support every stage of the software development lifecycle—from extracting requirements and designing solutions to generating code, tests, deployment scripts, and operational diagnostics—while warning about model inaccuracies, hallucinations, intellectual‑property and privacy risks.
AIChatGPTGitHub Copilot
0 likes · 8 min read

Requirement analysis, also known as requirements engineering, defines user expectations for new or modified software, covering goal identification, stakeholder conflict resolution, modeling, and validation, and includes activities such as gathering, analyzing, modeling, reviewing, and techniques like BPMN, ArchiMate, use cases, user stories, and data flow diagrams.
Requirements Engineeringrequirement analysissoftware engineering
0 likes · 16 min read

This article outlines a complete software testing workflow—including requirement analysis, technical review, test design, developer self‑testing, test involvement, gray release, and full launch—highlighting key activities, stakeholder participation, and best practices for ensuring quality throughout the development lifecycle.
deploymentdevelopment lifecycleprocess
0 likes · 5 min read


DevOpsDec 16, 2022 · R&D Management
The article narrates a software team's shift from a traditional waterfall model to an iterative, value‑driven agile approach, detailing the coach’s demand‑analysis meetings, three‑week sprints, lightweight documentation, continuous feedback, and the eventual successful delivery while highlighting common agile practices.
Agileiterative developmentrequirement analysis
0 likes · 8 min read

This article explains how interaction designers can identify and manage demand and technical boundaries, use functional specifications to define scope, and balance optimal user experience with project constraints to deliver feasible, high‑quality designs on time.
Product DesignUXboundary management
0 likes · 18 min read

This article presents a systematic, six‑point approach for developers and testers to decompose UI‑related requirements—covering UI scope, data sources, data‑UI binding, user interaction handling, behavior tracking, and post‑release monitoring—to improve implementation clarity, collaboration, and delivery quality.
UI Developmentdata flowrequirement analysis
0 likes · 13 min read

This article explains requirement analysis in software engineering, covering its purpose, key activities, business versus software requirements, and various techniques such as BPMN, ArchiMate, data flow diagrams, use cases, and user stories for capturing and modeling stakeholder needs.
ArchiMateBPMNbusiness requirements
0 likes · 16 min read

This guide outlines a comprehensive UI standard design process—from requirement analysis and interaction design to visual design, design system creation, and implementation tracking—providing UI, interaction, and experience designers with structured steps, evaluation criteria, and best‑practice principles to deliver business‑driven, high‑quality products.
Design ReviewUI designdesign-system
0 likes · 13 min read

The article explains how software‑engineering’s planning‑to‑maintenance lifecycle benefits from UML, then demonstrates using the open‑source textual tool PlantUML to quickly create version‑controlled use‑case, activity (swimlane), state, sequence, and class diagrams, detailing each syntax element and illustrating real‑world examples.
PlantUMLState DiagramUML
0 likes · 13 min read

This article provides a thorough overview of system architecture methodology, covering core concepts, business and requirement analysis, domain and business modeling, architectural design (logical and physical), high‑level and detailed design, and subsequent development, testing, deployment, and operation phases.
business analysisdesign methodologyrequirement analysis
0 likes · 14 min read


58UXDMar 4, 2021 · Operations
Learn how effective requirement analysis and clear communication can elevate operational design, with a four‑step framework, real‑world Spring Festival campaign case study, and reflective insights that help designers align user experience with business goals for more efficient, impactful outcomes.
UXcase studycommunication
0 likes · 7 min read

The biggest challenge for software engineers isn’t writing code but continuously questioning requirements, clarifying details, uncovering the real problem behind requests, and understanding the people behind the system, a mindset the article calls “upstream thinking.”
communicationproduct developmentrequirement analysis
0 likes · 8 min read

This article explains how to conduct thorough requirement analysis, classify and prioritize needs, and translate them into solid software architecture decisions, highlighting demand capture, functional, quality, and constraint considerations, as well as practical steps for prioritization and implementation.
R&D managementdesign methodologyrequirement analysis
0 likes · 6 min read

The article examines a seemingly trivial request to add a hyperlink, revealing hidden user‑tracking, localization, and security considerations, and demonstrates how thoughtful requirement analysis can lead to more elegant, cost‑effective, or even non‑development solutions.
ROIlink implementationproduct management
0 likes · 6 min read

The article shows how product‑thinking—identifying users, their pain points, and translating them into concrete solutions through an Ask‑Think‑Experience loop—can deeply uncover real needs, illustrated by a hot‑pot analogy and a customer‑service chatbot case that evolved from simple FAQs to a 70% automated response system.
Customer Servicecase studyproduct thinking
0 likes · 8 min read

This article explains the importance of requirement analysis in software testing, outlines its necessity, consequences of neglect, and provides a step-by-step guide on how to perform effective requirement analysis to improve test scope, priority, and overall quality.
quality assurancerequirement analysissoftware testing
0 likes · 8 min read

The article explains what requirement analysis is, why it is essential for successful testing projects, outlines a step‑by‑step approach to performing it, and offers practical tips for improving analysts' skills, emphasizing business knowledge, user perspective, continuous learning, and proactive collaboration.
quality assurancerequirement analysissoftware testing
0 likes · 7 min read


转转QAJun 20, 2019 · Product Management
The article explains how QA professionals can adopt product‑thinking by first understanding requirement background, feasibility, and characteristics, then using a coarse‑grained evaluation process and detailed analysis to design comprehensive test cases that align with business goals and resource constraints.
QAproduct thinkingrequirement analysis
0 likes · 7 min read


网易UEDCMay 23, 2019 · Product Management
This article outlines a step‑by‑step approach for designers to handle intricate product requirements—starting with deep requirement understanding, structuring them into a functional matrix, applying design subtraction to focus on core flows, and then adding detailed edge‑case considerations to ensure a robust, user‑centric solution.
interaction designproduct managementrequirement analysis
0 likes · 10 min read

This article explains the essential steps of requirement analysis, covering how to decompose and refine business needs, choose appropriate modeling structures, create effective UML diagrams, and avoid common mistakes that can lower requirement quality and increase change risk.
UMLbusiness processmodeling
0 likes · 20 min read

This article provides a comprehensive guide to software project management, covering risk assessment, cost budgeting, client communication, requirement analysis, development planning, quality assurance, and product delivery to help teams deliver successful software solutions.
Risk Assessmentcost budgetingrequirement analysis
0 likes · 26 min read


DevOpsOct 24, 2017 · Product Management
User stories are essential for agile development and continuous delivery, and this article explains why they matter, contrasts them with traditional waterfall requirements, and provides a detailed, step‑by‑step template—including examples and acceptance criteria—to help teams transition smoothly from legacy requirement documents to effective, deliverable user stories.
BDDContinuous Deliveryproduct management
0 likes · 11 min read

This article explores how product managers can decide between business‑oriented and technology‑oriented requirement‑analysis approaches for large‑scale IT systems, highlighting the trade‑offs, impact on user experience, and practical tips for combining both methods to build robust, user‑friendly solutions.
User Experiencebusiness vs technicalproduct management
0 likes · 5 min read

The article presents four practical interaction‑design case studies that show how designers can validate requirement reasonableness, leverage product data, eliminate redundant logic, and combine multiple factors to propose better solutions for mobile product features.
UXcase studydata‑driven design
0 likes · 9 min read

Learn how the KANO model, a Japanese product‑quality framework, categorizes features into must‑be, one‑dimensional, attractive and other types, and discover practical steps—questionnaires, Better‑Worse metrics, and analysis techniques—to prioritize and improve user satisfaction in product development.
Better-Worse metricproduct managementrequirement analysis
0 likes · 4 min read
