High level architecture proposal for scope of v1.0 F2F Workshop

[arsibo]

• Agenda
  • create a first draft of the scope of s-core v1.0 as a proposal to be discussed in architecture workshop April 8th – 10th
  • AoB

Date: 14.03.2025 12:00-18:00

[ZoranCutura]

• Agenda

  • create a first draft of the scope of s-core v1.0 as a proposal to be discussed in architecture workshop April 8th – 10th
  • AoB

Date: 14.03.2025 12:00-18:00

Meeting Minutes:

Attendance:
Markus Bechter
Andrey Babanin
Nico Hartmann
Arvid Sievert
Ulrich Freund
Zoran Cutura

- Proposal for v1.0 Platform API components discussed
- Platform API shall be the generic API of the stack
- Application Specific Frameworks (ie. FEO) utilize Platform API
- Platform API shall have a realization component underneath the API (i.e. daemon, library, shared service, hw, …)
- There are Platform Libraries and Application Libraries
	○ Platform Libs only used in platform services
	○ Application Libs are part of the Platform API
- Diagnostics functionality shall be mapped to existing APIs (see foto)
- Fault-Management shall be introduced
- OS-AL: we introduce a language specific area in the architecture picture to reflect extensions or replacements of standard libraries
- Communication-Architecture needs to be discussed dedicatedly
- User Management needs additional discussion

@4og please add the picture we discussed and adapted during the workshop.

[4og]

The proposal for S-CORE v1.0

[4og]

@ZoranCutura, can you please attach the whiteboard photo about the Diagnostics functionality?

[ZoranCutura]

Discussion on Diagnostics :

[ZoranCutura]

Read as follows:
left side are Diagnostics features as defined in UDS. Most of them can be mapped to parts in s-core that we already define. Hence no dedicated Diagnostics APIs towards applications would be implmented