-
Notifications
You must be signed in to change notification settings - Fork 26
process: document quality management process according to template structure #835
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
process: document quality management process according to template structure #835
Conversation
License Check Results🚀 The license check job ran with the Bazel command: bazel run //:license-check Status: ✅ Passed Click to expand output
|
f1c0343
to
e9a441b
Compare
The created documentation from the pull request is available at: docu-html |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Propose to have dedicated working meeting to address the major topics and relations to other process areas
docs/process/process_areas/quality_management/quality_concept.rst
Outdated
Show resolved
Hide resolved
docs/process/process_areas/quality_management/quality_concept.rst
Outdated
Show resolved
Hide resolved
docs/process/process_areas/quality_management/quality_concept.rst
Outdated
Show resolved
Hide resolved
docs/process/process_areas/quality_management/quality_concept.rst
Outdated
Show resolved
Hide resolved
Ref: closes eclipse-score#316
e9a441b
to
ba662f0
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
May update also Process Area Image and color the Quality Management with yellow
Workflows | ||
--------- | ||
|
||
todo: need to add guidance and standard links |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Shall this todo stay?
:responsible: rl__quality_manager | ||
:approved_by: rl__technical_lead | ||
:supported_by: | ||
:input: wp__policies, wp__issue_track_system |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
may add as input, wp__platform_mgmt, compare Create/Maintain Safety Plan
:responsible: rl__quality_manager | ||
:approved_by: rl__technical_lead | ||
:supported_by: rl__committer | ||
:input: wp__qms_plan, wp__process_definition |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Shall we not add here your overview table as input
Workproducts | ||
############ | ||
|
||
.. workproduct:: Quality Management Plan |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
BPs should not be mapped to WOs, only IIC, BPs should be mapped to Guidances only, compare Meta Model
General Workflow | ||
**************** | ||
|
||
.. figure:: _assets/quality_workflow.drawio.svg |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Are the numbers in the figure used/referenced somewhere?
This includes an approach to providing an independent and objective assurance that work products and processes | ||
comply with predefined provisions and plans and that non-conformances are resolved and further prevented. | ||
This document includes quality assurance activities, roles and responsibilities, goals, schedule, etc. and a | ||
general strategy to implement quality assurance process in this platform. The quality assurance is |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
implement "a" quality assurance process
|
||
The :need:`rl__quality_manager` provides only support to the project with consulting them to improve the | ||
quality of the project/platform product. Although the quality report is also sent to the :need:`rl__technical_lead`, | ||
the :need:`rl__quality_manager` is independent of the delivery of the product. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I do not fully understand the content of this sentence, may reforumlate it
| All tool requirements have bidirectional traceability to and from process requirements or guidance | ||
- 100% | ||
- None | ||
- Ensured by process configuration and tool management, only valid requirements can be merged, review required, script based check |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Metric may here not correct, this wp is not a requirement, found also other wps, where the metric is not correct and should be
- | All requirements were inspected by review with inspection checklist. | ||
- 100% | ||
- None | ||
- Ensured by process configuration and tool management, only valid requirements can be merged, review required, script based check |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
check metric
|
||
The project roles are defined in the processes and are aligned to Eclipse roles. | ||
|
||
.. needtable:: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
here only the roles for quality management should appear, not all, that should be part of project management plan, or not?
Replace in-score starpls tool with the one from tooling repo. Signed-off-by: Nicolae Dicu <[email protected]>
Correct term is now Change Request with types Feature request, modification, et. Resolves: eclipse-score#1039
- Arrange elements in a grid - Fix a few typos - Disable dark-mode as the diagram looks bad in this mode
Ref: closes eclipse-score#317 Signed-off-by: aschemmel-tech <[email protected]>
Signed-off-by: aschemmel-tech <[email protected]>
Ref: closes eclipse-score#538 Signed-off-by: aschemmel-tech <[email protected]>
Stakeholder, Risk Management
Ref: closes eclipse-score#313 Signed-off-by: aschemmel-tech <[email protected]>
Rename cross-functional teams to feature teams and update the links.
Initial draft
Update of draft document
Signed-off-by: Sven Bachmann <[email protected]>
International Requirements Engineering Board (IREB) Signed-off-by: Sven Bachmann <[email protected]>
These requirements are not needed at a feature level. Signed-off-by: Sven Bachmann <[email protected]>
Signed-off-by: Sven Bachmann <[email protected]>
Signed-off-by: Sven Bachmann <[email protected]>
Ref: closes#316
Ref: closes #316