feature time: Add stakeholder requirements #1600

lavrovvalera · 2025-08-05T14:45:22Z

Added stakeholder requirements
Updates Feature requirements

github-actions · 2025-08-05T14:50:07Z

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

hth9fe

overall I guess in IDs and requirement names we should use the word "mockup" or "mocking" instead of "fake" and "faking"

I believe Time Synchronization has Security relevance, but we can discuss this..

hth9fe · 2025-08-06T11:39:37Z

docs/requirements/stakeholder/index.rst

+   :rationale: Enables the system to synchronize its internal clock with external time sources, ensuring the data aging across distributed ECUs.
+   :status: valid
+
+   The software platform shall provide time synchronization framework to synchronize its clock with external time sources.


Suggested change

The software platform shall provide time synchronization framework to synchronize its clock with external time sources.

The software platform shall provide a time synchronization framework to synchronize its clock with external time sources.

hth9fe · 2025-08-06T11:44:12Z

docs/requirements/stakeholder/index.rst

+.. stkh_req:: Time Synchronization
+   :id: stkh_req__time__synchronization
+   :reqtype: Functional
+   :security: NO


I'm not sure what could happen if the time sychronization can be manipulated... Therefore I would expect that time sychronization is subject of necessary security measures...

For synchronization to external sources - definitely.
For in-vehicle,I would say - no

hth9fe · 2025-08-06T11:47:31Z

docs/requirements/stakeholder/index.rst

   The software platform shall provide a method and interface to enable
   debugging of the software on target and in vehicle.

+.. stkh_req:: Fake implementation for application testing


Suggested change

.. stkh_req:: Fake implementation for application testing

.. stkh_req:: Mockup implementation for application testing

Let's use the more development like term "mockup" or "Mocking". At least in the requirement headline.

hth9fe · 2025-08-06T11:48:56Z

docs/features/time/docs/requirements/index.rst

+Testability
+^^^^^^^^^^^^
+
+.. feat_req:: score::time fake APIs implementation


Suggested change

.. feat_req:: score::time fake APIs implementation

.. feat_req:: score::time mockup APIs implementation

Let's use mockup instead of fake

hth9fe · 2025-08-06T11:49:31Z

docs/features/time/docs/requirements/index.rst

+^^^^^^^^^^^^
+
+.. feat_req:: score::time fake APIs implementation
+   :id: feat_req__time__apis_faking


Suggested change

:id: feat_req__time__apis_faking

:id: feat_req__time__apis_mocking

hth9fe · 2025-08-06T11:49:52Z

docs/features/time/docs/requirements/index.rst

+   :reqtype: Functional
+   :security: NO
+   :safety: QM
+   :satisfies: stkh_req__dev_experience__fake_public_apis


Suggested change

:satisfies: stkh_req__dev_experience__fake_public_apis

:satisfies: stkh_req__dev_experience__mockup_public_apis

hth9fe · 2025-08-06T11:50:47Z

docs/features/time/docs/requirements/index.rst

 .. feat_req:: Time client PTP sync
   :id: feat_req__time__trec_external_sync_ptp
   :reqtype: Functional
   :security: NO


Suggested change

:security: NO

:security: NO

already mentioned below. I guess security is relevant here

hth9fe · 2025-08-06T11:51:20Z

docs/requirements/stakeholder/index.rst

   debugging of the software on target and in vehicle.

+.. stkh_req:: Fake implementation for application testing
+   :id: stkh_req__dev_experience__fake_public_apis


Suggested change

:id: stkh_req__dev_experience__fake_public_apis

:id: stkh_req__dev_experience__mockup_public_apis

- Update requirements - Fix review comments

lavrovvalera · 2025-08-08T15:10:54Z

docs/requirements/stakeholder/index.rst

+   :status: valid
+
+   The software platform shall provide a time synchronization framework to synchronize its clock
+   with external to ECU, but internal to vehicle time sources.


Suggested change

with external to ECU, but internal to vehicle time sources.

to Time Master within the vehicle

lavrovvalera · 2025-08-08T15:14:18Z

docs/requirements/stakeholder/index.rst

+   for event timestamping and chronological events comparison.
+   :status: valid
+
+   The software platform shall provide an API to read the synchronized time from Local Time Slave.


Suggested change

The software platform shall provide an API to read the synchronized time from Local Time Slave.

The software platform shall provide an API to access the synchronized vehicle time.

lavrovvalera · 2025-08-08T15:15:55Z

docs/requirements/stakeholder/index.rst

+
+   * for AVB nodes the maximum difference in the synchronized time between two AVB ports/ECUs while
+   both are in state SYNC, and could be 1 usec
+   * for non-AVB node the precision is released, comparing to AVB ones


add the upper limit: 200-500 usec

lavrovvalera · 2025-08-08T15:16:19Z

docs/requirements/stakeholder/index.rst

+   precision, based on the system setup.
+
+   Note:
+


the particular thresholds depends on the system setup

lavrovvalera · 2025-08-08T15:19:41Z

docs/requirements/stakeholder/index.rst

+   timestamping, converting and so on) which take part in time communication, based on the system setup.
+   Note:
+
+   * for AVB nodes the threshold the threshold might be 100 nsec


Suggested change

* for AVB nodes the threshold the threshold might be 100 nsec

* for AVB nodes the threshold might be 100 nsec

lavrovvalera · 2025-08-08T15:22:05Z

docs/requirements/stakeholder/index.rst

+   :rationale: Enables the system to compare high frequent events chronologically.
+   :status: valid
+
+   The software platform shall keep the threshold for all local clock adaptations (including


The software platform shall make local clock adaptations (...) within the predefined time window

When it starts?
Does it make sense tomove it to the feature level?

lavrovvalera · 2025-08-08T15:32:11Z

docs/requirements/stakeholder/index.rst

+
+   The software platform shall provide the APIs to read the current monotonic clock from the system time provider.
+
+   Note: to which clock the monotonic clock is mapped, depends on the system design.


synchronization to Time master with external to ECU (shall support)

synchronization to external time base ECU (UTC) 8shall support)

provide tha access to differnet timebases (or per timebase)

all the rest move to feature reqs.

* feature time: Add stakeholder requirements * feature:time: Update stakeholder requirements - Update requirements - Fix review comments * feature:time: Update stakeholder requirements * feature:time: Update stakeholder requirements * Fix review comments

feature time: Add stakeholder requirements

664b4eb

hth9fe reviewed Aug 6, 2025

View reviewed changes

lavrovvalera added 3 commits August 6, 2025 17:11

feature:time: Update stakeholder requirements

83961de

- Update requirements - Fix review comments

feature:time: Update stakeholder requirements

b520a28

feature:time: Update stakeholder requirements

6cb5ddc

lavrovvalera commented Aug 8, 2025

View reviewed changes

lavrovvalera force-pushed the vala_time_feature_stkh_reqs branch from 4e4b026 to e415463 Compare August 11, 2025 09:31

Fix review comments

701b157

lavrovvalera force-pushed the vala_time_feature_stkh_reqs branch from e415463 to 701b157 Compare August 11, 2025 11:36

lavrovvalera marked this pull request as ready for review August 11, 2025 11:39

qor-lb merged commit f03cc0d into eclipse-score:lb_time_feature_request Aug 11, 2025
6 checks passed

	The software platform shall provide time synchronization framework to synchronize its clock with external time sources.
	The software platform shall provide a time synchronization framework to synchronize its clock with external time sources.

	.. stkh_req:: Fake implementation for application testing
	.. stkh_req:: Mockup implementation for application testing

	.. feat_req:: score::time fake APIs implementation
	.. feat_req:: score::time mockup APIs implementation

	:id: feat_req__time__apis_faking
	:id: feat_req__time__apis_mocking

	:satisfies: stkh_req__dev_experience__fake_public_apis
	:satisfies: stkh_req__dev_experience__mockup_public_apis

	:id: stkh_req__dev_experience__fake_public_apis
	:id: stkh_req__dev_experience__mockup_public_apis

	with external to ECU, but internal to vehicle time sources.
	to Time Master within the vehicle

	The software platform shall provide an API to read the synchronized time from Local Time Slave.
	The software platform shall provide an API to access the synchronized vehicle time.

	* for AVB nodes the threshold the threshold might be 100 nsec
	* for AVB nodes the threshold might be 100 nsec


		The software platform shall provide the APIs to read the current monotonic clock from the system time provider.

		Note: to which clock the monotonic clock is mapped, depends on the system design.

feature time: Add stakeholder requirements #1600

feature time: Add stakeholder requirements #1600

Uh oh!

Conversation

lavrovvalera commented Aug 5, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

github-actions bot commented Aug 5, 2025

Uh oh!

hth9fe left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

lavrovvalera commented Aug 5, 2025 •

edited

Loading