II.
Methodology JSON
Structured · livemethodology:waterfall
Waterfall json
Inspect the normalized record payload exactly as the atlas UI reads it.
{
"id": "methodology:waterfall",
"_kind": "Methodology",
"_file": "domain/methodologies/methodologies.yaml",
"_cluster": "domain",
"attributes": {
"displayName": "Waterfall",
"description": "The linear and sequential approach to software development where progress flows\nthrough distinct phases: Requirements, Design, Implementation, Testing, Deployment,\nand Maintenance. Each phase must be completed and formally approved before the\nnext begins. Document-driven with heavy documentation requirements, phase gates\nrequiring formal approval, and requirements fixed early. Well-suited for stable\nrequirements, regulatory environments, and fixed-price contracts.\n",
"methodologyKind": "plan-driven",
"origin": "Winston W. Royce",
"yearIntroduced": "1970"
},
"outgoingEdges": [
{
"from": "methodology:waterfall",
"to": "domain:software-engineering",
"kind": "applies_to"
}
],
"incomingEdges": [
{
"from": "lib-process:shared--waterfall",
"to": "methodology:waterfall",
"kind": "follows_methodology",
"attributes": {
"weight": 1
}
}
]
}