process: add initial tool management #932

masc2023 · 2025-04-15T06:48:30Z

Resolves: #858

github-actions · 2025-04-15T06:49:17Z

License Check Results

🚀 The license check job ran with the Bazel command:

bazel run //:license-check

Status: ✅ Passed

Click to expand output

[License Check Output]
Extracting Bazel installation...
Starting local Bazel server and connecting to it...
INFO: Invocation ID: 32ad358d-22ad-4bef-9463-8764cfd7df83
Computing main repo mapping: 
Computing main repo mapping: 
Computing main repo mapping: 
Computing main repo mapping: 
Loading: 
Loading: 0 packages loaded
Analyzing: target //:license-check (1 packages loaded, 0 targets configured)
Analyzing: target //:license-check (1 packages loaded, 0 targets configured)

Analyzing: target //:license-check (90 packages loaded, 10 targets configured)

Analyzing: target //:license-check (98 packages loaded, 10 targets configured)

Analyzing: target //:license-check (132 packages loaded, 1596 targets configured)

Analyzing: target //:license-check (136 packages loaded, 1843 targets configured)

Analyzing: target //:license-check (140 packages loaded, 2430 targets configured)

Analyzing: target //:license-check (142 packages loaded, 2554 targets configured)

Analyzing: target //:license-check (149 packages loaded, 4600 targets configured)

INFO: Analyzed target //:license-check (150 packages loaded, 4737 targets configured).
[11 / 13] [Prepa] JavaToolchainCompileBootClasspath external/rules_java~/toolchains/platformclasspath.jar
INFO: Found 1 target...
Target //:license.check.license_check up-to-date:
  bazel-bin/license.check.license_check
  bazel-bin/license.check.license_check.jar
INFO: Elapsed time: 16.709s, Critical Path: 0.43s
INFO: 13 processes: 4 disk cache hit, 9 internal.
INFO: Build completed successfully, 13 total actions
INFO: Running command line: bazel-bin/license.check.license_check ./formatted.txt -review -project automotive.score -repo https://github.com/eclipse-score/score -token otyhZ4eaRYK1tKLNNF-Y
[main] INFO Querying Eclipse Foundation for license data for 76 items.
[main] INFO Found 52 items.
[main] INFO Querying ClearlyDefined for license data for 24 items.
[main] INFO Found 24 items.
[main] INFO Vetted license information was found for all content. No further investigation is required.

github-actions · 2025-04-15T06:51:27Z

The created documentation from the pull request is available at: docu-html

aschemmel-tech

see inline comments

aschemmel-tech · 2025-04-23T08:24:45Z

docs/process/process_areas/tool_management/tool_management_getstrt.rst

+
+In case you want to use a tool within **S-CORE** consider to:
+
+* Create your Tool Verification Report according to :need:`wf__tool__create_tool_verification_report`


First I think one should consider the tool list, if the tool and its use case is already part of it. And then one should follow the tool user guide. And only if it is not already there ...

aschemmel-tech · 2025-04-23T08:28:37Z

docs/process/process_areas/tool_management/tool_management_workflow.rst

+
+   The Tool Verification Report is created during identification of a tool.
+
+   Each identified tool to is evaluated and if applicable, qualified. During evaluation and


aschemmel-tech · 2025-04-23T08:29:24Z

docs/process/process_areas/tool_management/tool_management_workflow.rst

+
+   Finally the Tool Verification Report is verified and approved, and thus in Released state.
+
+   For creating the Tool Verification Report template must be used.


grammar "a template"

aschemmel-tech · 2025-04-23T08:34:31Z

docs/process/process_areas/tool_management/tool_management_workproducts.rst

+   proper tool documentation, guidelines, protection against malware introduction, etc.
+
+   Based on TCL the appropriate qualification methods shall be applied. For S-CORE per default
+   the method validation of software tool must be used.


consider to put the method name in "" for better readability

aschemmel-tech · 2025-04-23T08:40:14Z

docs/process/process_areas/tool_management/guidance/tool_management_checklist.rst

+Tool Management Checklist
+#########################
+
+.. gd_chklst:: Tool Verification Report Review Checklist


mismatch to title above?

aschemmel-tech · 2025-04-23T08:50:30Z

docs/process/process_areas/tool_management/guidance/tool_management_template.rst

+-------------
+[Describe here detailed information about the tool documentation]
+
+Where are the tool documents like User Manual, Guidelines, Erratas, etc. located?


I would like to have a tool list with all the information relevant for a user linked. So maybe we create a "tool" need with the respective attributes and generate the list from these?

see below, tool list exist, but not on need, but id, tags, let's discuss the better approach in next meeting

aschemmel-tech · 2025-04-23T08:52:27Z

docs/process/process_areas/tool_management/guidance/tool_management_checklist.rst

+        -
+
+      * - 20
+        - If applicable, are the analyses for software tool qualification defined?


see also below: analysis needed?

make it optional, let's discuss in next meeting

aschemmel-tech · 2025-04-23T08:58:31Z

docs/platform_management_plan/tool_management.rst

+For each tool the :need:`gd_temp__tool_management__verif_rpt_template` shall be used to document
+the relevant information.
+
+:need:`gd_chklst__tool__cr_review` may used to check that all relevant information is considered.


sentence unclear, needed? why only "may"?

changed, may was there, if it enforced by tool, may not needed?

aschemmel-tech · 2025-04-23T09:06:46Z

docs/platform_management_plan/tool_management.rst

+
+**To Step 3**
+
+If tool impact is judged to "YES" and tool error detection judged to "YES", the tool confidence


I think it should be "and tool error detection judged to "NO""

aschemmel-tech · 2025-04-23T09:13:30Z

docs/platform_management_plan/tool_management.rst

+.. list-table:: SW Platform tool overview
+    :header-rows: 1
+
+    * - tool Id


This is more a tool list for the "safety and security management". I would like to add here info/links relevant to the user like version, user manual, use case (or at least state that these are part of the "verification report").

add link, but see comment above, how to create tool list

Resolves: #858

masc2023 force-pushed the masc2023_add_initial_tool_management branch from 3242aa0 to af8341c Compare April 15, 2025 09:41

masc2023 marked this pull request as ready for review April 15, 2025 09:48

masc2023 requested a review from aschemmel-tech April 15, 2025 09:48

masc2023 force-pushed the masc2023_add_initial_tool_management branch from af8341c to c0e3042 Compare April 16, 2025 07:03

masc2023 self-assigned this Apr 16, 2025

masc2023 force-pushed the masc2023_add_initial_tool_management branch from c0e3042 to f8a7453 Compare April 16, 2025 08:03

aschemmel-tech requested changes Apr 23, 2025

View reviewed changes

proces: add initial tool management

37c6d46

Resolves: #858

masc2023 force-pushed the masc2023_add_initial_tool_management branch from f8a7453 to 37c6d46 Compare April 25, 2025 10:23

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

process: add initial tool management #932

process: add initial tool management #932

masc2023 commented Apr 15, 2025

github-actions bot commented Apr 15, 2025 •

edited

Loading

github-actions bot commented Apr 15, 2025

aschemmel-tech left a comment

aschemmel-tech Apr 23, 2025

masc2023 Apr 25, 2025

aschemmel-tech Apr 23, 2025

masc2023 Apr 25, 2025

aschemmel-tech Apr 23, 2025

masc2023 Apr 25, 2025

aschemmel-tech Apr 23, 2025

masc2023 Apr 25, 2025

aschemmel-tech Apr 23, 2025

masc2023 Apr 25, 2025

aschemmel-tech Apr 23, 2025

masc2023 Apr 25, 2025

aschemmel-tech Apr 23, 2025

masc2023 Apr 25, 2025

aschemmel-tech Apr 23, 2025

masc2023 Apr 25, 2025

aschemmel-tech Apr 23, 2025

masc2023 Apr 25, 2025

aschemmel-tech Apr 23, 2025

masc2023 Apr 25, 2025


		In case you want to use a tool within S-CORE consider to:

		* Create your Tool Verification Report according to :need:`wf__tool__create_tool_verification_report`


		The Tool Verification Report is created during identification of a tool.

		Each identified tool to is evaluated and if applicable, qualified. During evaluation and


		Finally the Tool Verification Report is verified and approved, and thus in Released state.

		For creating the Tool Verification Report template must be used.


		To Step 3

		If tool impact is judged to "YES" and tool error detection judged to "YES", the tool confidence

process: add initial tool management #932

Are you sure you want to change the base?

process: add initial tool management #932

Conversation

masc2023 commented Apr 15, 2025

github-actions bot commented Apr 15, 2025 • edited Loading

License Check Results

github-actions bot commented Apr 15, 2025

aschemmel-tech left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

github-actions bot commented Apr 15, 2025 •

edited

Loading