Harrier Open Standards
  • Open Standards
  • Technical
    • Best Practices
      • Naming conventions
        • Object / Metadata Type / Settings Conventions
        • Custom Permissions Conventions
        • Profile Conventions
        • Permission Set (Group) Conventions
        • Apex Style Guide
      • Feature flags
    • Documentation
      • GPT Instructions
    • Frameworks
      • flxbl - Continuous Delivery
      • fflib - Apex Framework
      • Nebula Logger - Logging
    • Integration Strategies
      • Data warehouse & Reverse ETL
    • Development & Deployment Strategies
  • Functional
    • Requirement definition
      • GPT Instructions
    • Documentation
Powered by GitBook
On this page
  • Diagrams
  • Rationale & overall documentation strategy

Was this helpful?

  1. Functional

Documentation

Diagrams

Rationale & overall documentation strategy

Functional documentation focuses on the narratives of completed stories. When acceptance criteria are clearly defined and articulated, the collective sum of these stories should illustrate a comprehensive behavioral overview.

Nonetheless, there exists a necessity for overarching business process documentation. This is accomplished not through written documentation but via flowcharts.

BPMN or alternative notations may be employed, provided they clearly delineate the various stages in a process, including their prerequisites or conditions that are assessed, and the subsequent effects across systems or actors.

PreviousGPT Instructions

Last updated 7 months ago

Was this helpful?