rusty-mermaid Gallery

25 diagram types — 297 diagrams rendered by rusty-mermaid

requirement (5)

req_all_types
<<contains>> <<derives>> <<satisfies>> <<traces>> <<verifies>> COMP_01 <<Element>> Type: Module Doc: arch_spec.pdf DC_01 <<Design Constraint>> Id: DC01 Text: Budget constraint Risk: Low Verify: Analysis FREQ_01 <<Functional Requirement>> Id: FR01 Text: Functional spec Risk: Medium Verify: Test PREQ_01 <<Performance Requirement>> Id: PR01 Text: Performance target Risk: High Verify: Demonstration REQ_01 <<Requirement>> Id: R01 Text: Base requirement Risk: Low Verify: Inspection
Source (.mmd)
requirementDiagram

    requirement REQ_01 {
        id: R01
        text: "Base requirement"
        risk: low
        verifymethod: inspection
    }

    functionalRequirement FREQ_01 {
        id: FR01
        text: "Functional spec"
        risk: medium
        verifymethod: test
    }

    performanceRequirement PREQ_01 {
        id: PR01
        text: "Performance target"
        risk: high
        verifymethod: demonstration
    }

    designConstraint DC_01 {
        id: DC01
        text: "Budget constraint"
        risk: low
        verifymethod: analysis
    }

    element COMP_01 {
        type: Module
        docref: "arch_spec.pdf"
    }

    REQ_01 - contains -> FREQ_01
    FREQ_01 - derives -> PREQ_01
    DC_01 - satisfies -> REQ_01
    COMP_01 <- traces - FREQ_01
    PREQ_01 - verifies -> COMP_01
req_basic
<<contains>> REQ_001 <<Requirement>> Id: SYS_001 Text: System shall process data in real-time Risk: High Verify: Test REQ_002 <<Functional Requirement>> Id: SYS_002 Text: UI must respond within 100ms Risk: Medium Verify: Analysis
Source (.mmd)
requirementDiagram

    requirement REQ_001 {
        id: SYS_001
        text: "System shall process data in real-time"
        risk: high
        verifymethod: test
    }

    functionalRequirement REQ_002 {
        id: SYS_002
        text: "UI must respond within 100ms"
        risk: medium
        verifymethod: analysis
    }

    REQ_001 - contains -> REQ_002
req_direction
<<traces>> COMP <<Element>> Type: Service Doc: api_spec.md REQ <<Requirement>> Id: R1 Text: Horizontal layout Risk: Medium Verify: Test
Source (.mmd)
requirementDiagram
    direction LR

    requirement REQ {
        id: R1
        text: "Horizontal layout"
        risk: medium
        verifymethod: test
    }

    element COMP {
        type: Service
        docref: "api_spec.md"
    }

    REQ - traces -> COMP
req_nested
<<contains>> <<satisfies>> AuthModule <<Element>> Type: module SEC001 <<Functional Requirement>> Id: SEC001 Text: Encrypt all data at rest Risk: High Verify: Inspection SYS001 <<Requirement>> Id: SYS001 Text: System shall be secure Risk: High Verify: Test
Source (.mmd)
requirementDiagram
    requirement SYS001 {
        id: SYS001
        text: "System shall be secure"
        risk: high
        verifymethod: test
    }
    functionalRequirement SEC001 {
        id: SEC001
        text: "Encrypt all data at rest"
        risk: high
        verifymethod: inspection
    }
    element AuthModule {
        type: module
        docRef: auth.rs
    }
    SYS001 - contains -> SEC001
    AuthModule - satisfies -> SEC001
req_relationships
<<contains>> <<copies>> <<derives>> <<satisfies>> <<verifies>> <<refines>> <<traces>> A <<Requirement>> Id: A Text: Source B <<Requirement>> Id: B Text: Target C <<Requirement>> Id: C Text: Another E <<Element>> Type: Component
Source (.mmd)
requirementDiagram

    requirement A {
        id: A
        text: "Source"
    }
    requirement B {
        id: B
        text: "Target"
    }
    requirement C {
        id: C
        text: "Another"
    }
    element E {
        type: Component
    }

    A - contains -> B
    A - copies -> C
    B - derives -> C
    C - satisfies -> A
    E <- verifies - B
    A - refines -> E
    C - traces -> E