Scope and applicability
Jump to navigation
Jump to search
Scope and Applicability Document
| Field | Value |
|---|---|
| Document ID | PGCBL-SAD-001 |
| Document Type | Scope and Applicability Document |
| System | pgcobol — Prime Numbers Application v1.0 |
| Version | 1.0 |
| Status | Approved |
| Owner | Lead Developer |
| Author | [reverse-engineered from source artifacts] |
| Created | 2026-03-17 |
| Last modified | 2026-03-17 |
| Classification | Internal |
Version History
| Version | Date | Author | Status | Change Summary |
|---|---|---|---|---|
| 0.1 | 2026-03-17 | — | Draft | Initial reverse-eng draft |
| 1.0 | 2026-03-17 | — | Approved | Baselined |
Table of Contents
1. Purpose
This document defines what is and is not covered by the pgcobol specification set. It exists to prevent readers from applying any single document outside its intended context, and to provide a navigational entry point to the full document set.
2. System Scope
2.1 What the system is
pgcobol is a three-tier batch COBOL application that:
- Generates prime numbers by trial division and stores them in a PostgreSQL database.
- Reads stored primes from the database and produces a formatted line-printer report.
It runs as a command-line batch job on Linux. There is no interactive interface.
2.2 System boundary
Inside scope:
- The four COBOL programs:
primesmain,primesgen,primes,primesui. - The five copybooks that define the inter-tier interfaces.
- The PostgreSQL schema
primesand its objects. - The output file
primes.prt. - The console log output.
Outside scope:
- The GnuCOBOL compiler and GixSQL pre-processor (third-party tools, not modified).
- The PostgreSQL server installation and administration.
- The operating system, file system, and network infrastructure.
- Any job scheduler or wrapper scripts.
- Any downstream processing of
primes.prt.
2.3 System version covered
This document set describes pgcobol as found in source artifacts dated November–December 2025, compiled under GnuCOBOL 4.0-early-dev.
2.4 What is explicitly not covered
| Excluded topic | Reason |
|---|---|
| Prime numbers beyond 999,999,999 | Hard-coded upper bound in the source |
| Even primes (2) | The algorithm tests odd candidates only; prime 2 is a known seeding gap |
| Interactive or web interfaces | Not implemented |
| Concurrent execution | Single-process batch design; no concurrency controls present |
| Encryption or secure credential storage | Not implemented in this version |
| High-availability or disaster recovery | Not in scope for this version |
3. Document Set Scope
3.1 Documents in this set
| Document ID | Type | Title | Covers |
|---|---|---|---|
| PGCBL-SAD-001 | SAD | Scope and Applicability | Navigation and scope |
| PGCBL-BRD-001 | BRD | Business Requirements | What the system must do |
| PGCBL-NFR-001 | NFR | Non-Functional Requirements | Quality attributes |
| PGCBL-TSD-001 | TSD | Technical Specification | Architecture and pseudocode |
| PGCBL-DDD-001 | DDD | Data Dictionary | All fields and structures |
| PGCBL-FLD-001 | FLD | Flow Diagrams | Mermaid process diagrams |
| PGCBL-PLG-001 | PLG | Program Logic Guide | Step-by-step paragraph logic |
| PGCBL-BRG-001 | BRG | Business Rules Guide | Rules, calculations, validations |
| PGCBL-IOB-001 | IOB | I/O Behaviour | File, console, DB I/O |
| PGCBL-CFD-001 | CFD | Control Flow Document | PERFORM/CALL trees |
| PGCBL-ADD-001 | ADD | Architecture Decision Records | Design decisions and rationale |
| PGCBL-TTM-001 | TTM | Test Traceability Matrix | Requirements → design → tests |
| PGCBL-NCS-001 | NCS | Naming and Coding Standard | COBOL conventions |
| STD-DOC-001 | STD | Document Engineering Standard | This document set’s scaffolding |
3.2 How to use this set
| I want to… | Start with… |
|---|---|
| Understand what the system must do | PGCBL-BRD-001 |
| Understand the overall architecture | PGCBL-TSD-001 §1–2 |
| Look up a specific data field | PGCBL-DDD-001 |
| Understand how a program works step-by-step | PGCBL-PLG-001 |
| Understand why a design decision was made | PGCBL-ADD-001 |
| Check what tests cover a requirement | PGCBL-TTM-001 |
| Write new COBOL code to the same standards | PGCBL-NCS-001 |
4. Audience
| Audience | Assumed knowledge | Documents most relevant |
|---|---|---|
| COBOL developer | COBOL syntax, batch processing | TSD, PLG, CFD, NCS |
| Database developer | SQL, PostgreSQL | TSD §5, DDD §12, IOB §3 |
| Business analyst | None technical required | BRD, BRG |
| QA engineer | Testing concepts | TTM, BRD, BRG |
| Architect / reviewer | Systems design | TSD, ADD, NFR |
| New team member | None | SAD (start here), then BRD |
5. Related Documents
| Document ID | Title | Relationship |
|---|---|---|
| STD-DOC-001 | Document Engineering Standard | Governs the format of all documents in this set |
6. Open Issues
| ID | Issue | Owner | Target | Status |
|---|---|---|---|---|
| OI-01 | System version identifier not present in source; version inferred from compiler listing date | Lead Dev | — | Open |
Terug naar: Design standards