# About the map

This map connects software development practices across the journey from requirements to operations.
It offers starting points for exploration, rather than a complete catalog or prescribed process.

## How to read the map

Stages describe where a practice often contributes.
A practice can span several stages.
The lower groups contain methods, lifecycle models, and concerns spanning the process.

Relationships distinguish structure, support, verification, combinations, and comparisons.
Their captions describe the connection from the selected practice's perspective.
Placement and relationships are editorial choices, not universal rules.

### Descriptions and sources

Each practice has a short description and a link to a primary source.
That source introduces the practice; it does not substantiate every suggested relationship.
Use the original publications when choosing an approach for your project.

## The project

Created by [cNoNim](https://cnonim.name/) ([GitHub](https://github.com/cNoNim)).

### Built with

- [React](https://react.dev/) — interface and HTML rendering.
- [Fuse.js](https://www.fusejs.io/) — practice search.
- [TypeScript](https://www.typescriptlang.org/) — application code and type checking.
- [Vite](https://vite.dev/) — development server and production builds.
- [unified](https://unifiedjs.com/) — Markdown processing with remark and rehype.
- [Cloudflare Pages](https://developers.cloudflare.com/pages/) — website hosting.

### License

The source code and original descriptions use the [MIT License](/license.txt).
Linked publications retain their own copyrights.
Third-party notices: [React and Fuse.js](/third-party-licenses.txt).

[HTML](https://dpm.cnonim.name/about/)