• Welcome to the Guide
    • How to use this Guide
    • Frequently Asked Questions
      • Understanding Architecture
      • Architecture Characteristics
      • Architecture Styles
      • Visualizing Architecture
      • Architecture Process
      • Sample Architecture
      • What is an Architecture Characteristic?
      • Identifying Characteristics
      • Availability
      • Interoperability
      • Modifiability
      • Performance
      • Security
      • Testability
      • Usability
      • Scalability
      • Modeling and Analysis
      • Measuring and Governing
      • Addressing Characteristics
      • Catalog
      • Foundations
      • Layered Monolith
      • Modular Monolith
      • Pipeline Monolith
      • Microkernel Monolith
      • Service-Based
      • Event-Driven
      • Space-Based
      • Orchestration-Driven
      • Microservices-Based
      • Selecting a Style
      • What is Domain Driven Design?
      • What is the business domain?
      • Modeling Business Domain
      • Domain Model Building Blocks
      • Bounded Contexts
      • Integration of Bounded Contexts
      • Discovering Domains and Contexts
      • Domains Evolution
      • Best Practices
      • Applying DDD in Practice
      • What is Coupling?
      • What is Modularity?
      • Dimensions of Coupling
      • Balancing Coupling
      • What is Component?
      • Defining components
      • What is a Service?
      • Sharing
      • Managing Operational Data
      • Managing Analytical Data
      • Managing Distributed Workflows
      • Contracts
      • Trade off analysis
      • Overview
      • Diagraming and Presenting
      • Producing Architectural Models
      • Architectural Description
      • Architectural Decisions Records
      • Documentation Management
      • Architecture, Implementation, and Testing
      • Architecture Metrics
      • Measuring System Qualities
      • Architecture Reconstruction and Conformance
      • Architecture Evaluation
      • Risk Analysis
      • Economic Analysis
      • Architecture Governance
    • Team
    • Value Streams
    • Engineering
    • Product
    • Company
    • Alignment
    • Goals
    • Role Overview
    • Classification
    • Collaboration
    • Career
      • Modeling Overview
        • Overview
        • C4 Model
        • Viewpoints and Perspectives
        • 4+1
        • TOGAF
        • Overview
        • C4 Notation
        • Flowchart
        • Event Storming
        • UML
        • Archimate
      • Visual
      • Written
      • Spoken
      • Effective
      • Documentation
      • Remote
      • Multi Culture
      • What Is a Requirement?
      • How to Collect Requirements?
      • Business Use Cases
      • Collecting Scenarios
      • Selecting Requirements
      • Writing Requirements
      • Functional Requirements
      • Non-Functional Requirements
      • Testing Requirements
      • Communicating Requirements
      • Facilitation Overview
      • Leadership Overview
      • Management Overview
      • Overview
      • Overview
      • Overview
      • Overview
    • Guide
    • Blog
    • Courses
    • Authors
    • Udemy
    • SubstackSubstack Streamline Icon: https://streamlinehq.com
    • GitHub
  • to navigate
  • to select
  • to close
    • Home
    • Competencies
    • Requirements
    On this page
    search_check

    Requirements

    This section explains what software requirements are and provides a comprehensive guide on how to collect, define, communicate, and test them effectively in software development to ensure successful project outcomes.

    article

    What Is a Requirement?

    This article explains what a software requirement is, distinguishing between functional, …

    article

    How to Collect Requirements?

    This article explains how to effectively collect software requirements, focusing on structured …

    article

    Business Use Cases

    This article explains how to identify and define business use cases (BUCs) to align software …

    article

    Collecting Scenarios

    This article explains how to effectively collect and use scenarios in software development to …

    article

    Selecting Requirements

    This article explains how to effectively select software requirements by focusing on the business …

    article

    Writing Requirements

    This article explains how to write effective software requirements by translating business events …

    article

    Functional Requirements

    This article explains what functional requirements (FRs) are, how they differ from non-functional …

    article

    Non-Functional Requirements

    This article explains what non-functional requirements (NFRs) are, why they are critical for system …

    article

    Testing Requirements

    This article explains how to effectively test software requirements by pairing each with a …

    article

    Communicating Requirements

    This article explains how to effectively communicate software requirements to diverse audiences, …

    © 2026 Software Architecture Guild | Built with Lotus Docs | Privacy & Cookies Policy | Manage Cookie Preferences

    We use cookies to improve your experience and collect analytics data. By accepting, you agree to our use of cookies. Please read our Privacy & Cookies Policy for more details.