EPIC: Work Product Reviews

[masc2023]

What

Plan and execute Work Product Review according to
https://eclipse-score.github.io/process_description//main/process_areas/quality_management/quality_workflow.html#wf__exe_wp_review

Review Platform as well selected Features

How

Compare https://eclipse-score.github.io/process_description//main/process_areas/quality_management/guidance/quality_work_product_review_guideline.html#gd_guidl__wp_review

Decide for spot check or full review

Estimates for realization

Per Feature / ? days
Platform / ? days

Category

• Affects Detailed Design

Requirements / Architecture

• Requirements / Architecture are not affected by this change?

[PandaeDo]

We performed a spot-check towards different repositories and work products. Some systematical issues where found. So we decide to stop the work product review, list the findings and share the results in the next lessons learned. The findings where analyzed. Whenever it's possible to solve them by fix the root cause it shall be done.

• Doubled entry "verification reports summaries" under more https://eclipse-score.github.io/reference_integration/main/
• Documentation for Kyron missing when opening short cut in the top navigation bar https://eclipse-score.github.io/reference_integration/main/_collections/score_kyron/docs/index.html
• Same for Orchestration https://eclipse-score.github.io/reference_integration/main/_collections/score_orchestrator/docs/index.html
• Orchestration module documentation is available under https://eclipse-score.github.io/score/main/modules/orchestrator/index.html and can be found also in the reference integration over documentation
• Under documentation in the release integration e.g. the document management plan for 0.5 can be found. That's not correct for the reference integration
• Additional documentation like all modules can be confusing. This might be described
• The module(s) have no filled out release notes as provided in the templates folders. To analyze if the process shall be changed to the release description. If not a check can be helpful that the release notes have to be updated to e.g. hash of the release
• Check if a release shall contain documents in draft / templates or even empty files according to the plan of the release
• Baselibs has valid static analysis that uses "...req__log__placeholder"
• Baselibs has empty / not filled out template for FMEA
• Baselibs has wrong Safety Manual. Seems to be a copy from Persistency

Suggestions for improvements

• Check for , TODO and other placeholders like placeholders. Could be helpful warning message
• Check if document management plan can be automated generated by the information's of the release / has to be adopted to the release
• Filters can be checked if they fit to the document. E.g. a list in Persistency documentation shall use "persistency" in the filter. We have several findings that occur from copy&paste failures
• Check if templates are listed in tables as in Baselibs Safety Manual
• Íntroduce Maturity Level for Modules/including Documents
• Check for validity of all documents