Skip to content
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.

Sign up for GitHub

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

Jump to bottom

D2.7 OETCS API Requirements Version 1.2: Review: Chapt. 3, 3.1, 3.2 #50

Open
UweSteinkeFromSiemens opened this issue Feb 27, 2014 · 1 comment
Open

D2.7 OETCS API Requirements Version 1.2: Review: Chapt. 3, 3.1, 3.2 #50

UweSteinkeFromSiemens opened this issue Feb 27, 2014 · 1 comment
Labels
D2.7 Review

Comments

@UweSteinkeFromSiemens
Copy link
Contributor

  • 3.1: The API and its location should be shown in the diagram.
  • 3.1, "It does not cover the implementation of the peripheral functions and modules such as ...": An architectural overview should be provided to clarifiy which functions and features are located in the application SW, in the API, the Basic SW of the Core board and the peripheral function modules.
  • 3.1: "... notice that the API SW belongs to the Application SW component": What are the aim and the impact of this sentence?
  • 3.2: "services ... hat are specific to the implementation of some constructor (ALSTOM ..." : These services should be abstracted to become vendor-unspecific.
@UweSteinkeFromSiemens
Copy link
Contributor Author

This issue is part of the review in #47 .

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
D2.7 Review
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@UweSteinkeFromSiemens @BerndHekele