Process framework

Method — CMMI Level 3

Helveticore commits to delivering its technology bricks at CMMI-DEV v2.0, Level 3 “Defined” maturity. The process is defined, documented and reused identically from one project to the next.

Hybrid lifecycle

Level	Approach	Role
Macro-architecture	V-Model	Top-down design, bottom-up validation & verification (system → components → integration tests)
Micro-architecture	TDD	Test-driven development of proprietary components, with mocked inputs
Integration	CBSE	Qualification and reuse of proven open-source components; in-house builds for anything requiring strict control

CMMI practice areas → artifacts

CMMI area	Repository artifact
Requirements Development & Management (RDM)	`requirements/REQ.md` + `requirements/RTM.md`
Technical Solution (TS)	`design/SDD.md` + `src/`
Decision Analysis & Resolution (DAR)	`design/decision-log.md`
Verification & Validation (VV)	`testbench/` (virtual test benches, mocks)
Measurement & Analysis (M&A)	`performance/` (curves, KPIs, benchmarks)
Configuration Management (CM)	Git versioning + immutable `docs/`
Process & Product Quality Assurance (PQA)	Review criteria in `assets/`
Risk & Opportunity Management (RSK)	Risk register in each project README
Planning & Estimating (PLAN/EST)	Scope and milestones in each project README
Peer Reviews (PR)	Review checklist in `assets/`

Mandatory artifacts per project

Every projects/<project>/ folder must contain, at minimum:

requirements/   REQ.md, RTM.md          (requirements + traceability matrix)
design/         SDD.md, decision-log.md  (design + decision log)
testbench/      README.md                 (virtual test bench plan)
performance/    README.md                 (KPI measurement plan)
src/            technical sub-projects + README.md per sub-project
README.md       project charter (scope, KPIs, risks, milestones)

“Build vs Reuse” rule (CBSE)

Reuse

An open-source component when it meets footprint and latency criteria and its protocol compliance is proven (e.g. pymodbus, Eclipse Mosquitto).

Build in-house

Any component requiring strict “Fail-Fast” behavior, a proprietary data schema, or a CMMI L3 quality guarantee (e.g. protocol adapters, behavioral analysis engines).

Each choice is recorded in design/decision-log.md (criteria, options, decision, rationale) — see the EdgeStream-GW decision log.