Answer
This question has not yet been answered.
multi layer requirement structures
we are developing a complex medical device for which we need multiple requirement layers from system (including hardware) down to software units. This tree preferably consists out of 4 to 5 layers. The proposed epic/feature/requirement (we are using the CMMI template) does not do the job for us. In addition, we are struggling to model the necessary document structure in ADS so that we can extract readable requirements out of ADS. For that we tend to use the feature and epic layer, but also here this does not fully satisfy us. For both use cases, we feel we violate the initial intended use of epic and feature.
I guess we are not the first team struggling with this. Is there anyone who can share their experience with this dilemma.
Status:
Open Jan 05, 2022 - 12:52 AM
Modern Requirement4DevOps > Advance Reporting, Modern Requirement4DevOps > Trace Analysis
Do you have the same question? Follow this Question
Share Your Own Experience & Expertise
We look to ensure that every question is answered by the best people with relevant expertise and experience, the best answers include multiple perspectives. Do you have relevant expertise or experience to contribute your answer to any of these commonly asked questions?
