---
title: PROJ pages — Project method
lang: en
tags: [domaine, proj]
draft: false
source_fr: conduite/proj/index.md
source_sha256: 9efc5099390bfe142c6f03fd90b46fb81100fdf42f8b49f29a2bf37c039f2766
---

# PROJ — The cross-cutting project method

The core of the hub. The **PROJ** domain carries the project method from end to end: functional analysis, planning, concept trade-off, build and review. For the five phases in chronological order, see the [[en/conduite/index|project path]]. This index lists the pages by family of tools.

## The framework pages

The five phases of the V-model, plus the three cross-cutting threads that run from the start of the project to the end.

- [[specification-technique-en|Technical specification]] — turn a need into measurable requirements
- [[concept-en|Concept]] — choose an architecture and size it roughly
- [[preuve-de-concept-en|Proof of concept]] — resolve the technical unknowns before detailed design
- [[dossier-technique-en|Technical design file]] — produce the documents that make manufacturing possible
- [[integration-et-tests-en|Integration and testing]] — assemble, qualify, close the project
- [[gestion-de-projet-en|Project planning and tracking]] *(cross-cutting)* — plan, track, lead the team
- [[ecoconception-en|Eco-design]] *(cross-cutting)* — keep the environmental footprint under control through the choices made
- [[securite-et-qualite-en|Safety and quality]] *(cross-cutting)* — risks, compliance, quality of deliverables

## Functional analysis

The chain that expresses the need, from the initial brainstorming to the cahier des charges, the French functional requirements specification.

- [[mecatronique-en|Mechatronics]] — the perception → decision → action loop that defines the field
- [[mind-map-en|Mind map]] — cast a wide net over the surrounding environments and constraints, early on
- [[bete-a-cornes-en|Bête à cornes]] — the French "horned beast" need-statement diagram: for whom, on what, to what end
- [[pieuvre-en|Pieuvre]] — the French "octopus" diagram: list the functions against the surrounding environments
- [[fonction-en|Function]] — the FP / FS / FC typology, for main, secondary and constraint functions
- [[caracteriser-une-exigence-en|Characterising a requirement]] — the criterion / level / flexibility triplet
- [[etat-de-l-art-technique-en|Technical state of the art]] — map the solutions that already exist
- [[cahier-des-charges-fonctionnel-en|Cahier des charges fonctionnel]] — the document that formalises the spec
- [[afnor-nfx50-151-en|NF X50-151 standard]] — the normative framework of functional analysis

## Planning and tracking

The tools that anchor the project in time and keep watch on its risks.

- [[wbs-en|WBS]] — break the work down into work packages
- [[jalons-en|Milestones]] — set the control points of the project
- [[retroplanning-en|Backward planning]] — plan backwards from the deadline
- [[gantt-en|Gantt]] — lay the tasks out over time
- [[matrice-de-risques-en|Risk matrix]] — identify and rate the hazards of the project

## Concept and trade-off

Break a function down, explore the solutions, decide.

- [[decomposition-fonctionnelle-en|Functional breakdown]] — split the system into technical functions
- [[fast-en|FAST]] — link functions and solutions through the why / how chain
- [[matrice-de-decision-en|Decision matrix]] — compare the candidates against weighted criteria
- [[matrice-eco-criteres-en|Eco-criteria matrix]] — bring the environment into the trade-off
- [[ecodesign-en|Écodesign]] — the French design-discipline sense of the word, and how it differs from eco-design

## Build and review

The artefacts that give shape to the design and to its dependability.

- [[bom-en|BOM (bill of materials)]] — consolidate the components and the budget
- [[amdec-en|AMDEC]] — the French acronym for FMEA: analyse product failures and their criticality
- [[acv-simplifiee-en|Simplified LCA]] — assess the environmental impact over the life cycle