Member level 4
We would like to use some process to grade embedded software maturity for our ADAS application. On any day, we want to know how much of the v-cycle work has been completed. For all ADAS features such as Lane Departure Warning(LDW), Automatic Cruise Control(ACC), and many more, we want to know the following:
- In calculating software maturity for our ADAS software application, what specific requirements characteristics should be emphasized when grading maturity and why? The characteristics are testability, measurable, completeness, traceability, and stability.
- With respect to software architecture documents, software design documents, state diagrams, and any v-cycle documents that are created to understand software operation, what specific characteristics should be emphasized when grading software maturity and why?