eclipse-score / eclipse-score/logging
[feature logging] Feature FMEA creation
- Dominant language
- C++
- Stars
- 2
- Forks
- 28
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 20
Description
## What
Create the Feature FMEA (`wp__feature_fmea`) for the feature logging. The FMEA verifies the feature architecture as part of the SW Safety Concept, linking detections, preventions, and mitigations to Feature Requirements or Assumptions of Use.
## How
**Process step:** [wf__analyse_featarch](https://eclipse-score.github.io/process_description/main/process_areas/safety_analysis/safety_analysis_workflow.html#wf__analyse_featarch)
## Definition of Done
All criteria of the [Safety Analysis Checklist](https://eclipse-score.github.io/process_description/main/process_areas/safety_analysis/guidance/safety_analysis_checklist.html) are met.
## Template & Folder Structure
- **Template:** [Feature FMEA Template](https://eclipse-score.github.io/module_template/main/docs/features/feature_example/safety_analysis/fmea.html)
- **Folder:** `docs/features/logging/safety_analysis/` – see [Module Folder Structure](https://eclipse-score.github.io/module_template/main/index.html#module-layout)
*Please apply the linked template and folder structure to ensure consistency across the S-CORE project.*
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the Feature FMEA Template and the wf__analyse_featarch process step linked in the issue. Create the artifact under docs/features/logging/safety_analysis/ using the stated module folder structure, then check the Safety Analysis Checklist to verify completion and confirm that detections, preventions, and mitigations link to Feature Requirements or Assumptions of Use.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100