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.

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

[MCU] Document structure for hardware driver modules #32

Open
AndreasFreund opened this issue May 8, 2024 · 0 comments
Open

[MCU] Document structure for hardware driver modules #32

AndreasFreund opened this issue May 8, 2024 · 0 comments

Comments

@AndreasFreund
Copy link
Contributor

AndreasFreund commented May 8, 2024

User story

  1. As a developer of hardware drivers / C modules
  2. I want / need a clear structure
  3. So that I can easily navigate my and others modules

Acceptance criteria

  • Agree on file naming scheme for generic (platform independent) vs implementation (platform specific) headers and source files
  • Agree on naming for functions

Definition of done (DoD)

  • Added only after week 5
  • The same for all features
  • Here goes the project specific part

DoD general criteria

  • Feature has been fully implemented
  • Feature has been merged into the mainline
  • All acceptance criteria were met
  • Product owner approved features
  • All tests are passing
  • Developers agreed to release
@AndreasFreund AndreasFreund converted this from a draft issue May 8, 2024
@AndreasFreund AndreasFreund moved this from Product Backlog to Sprint Backlog in amos2024ss07-feature-board May 8, 2024
@AndreasFreund AndreasFreund changed the title [MCU] Agree on structure for hardware driver modules [MCU] Document structure for hardware driver modules May 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

No branches or pull requests

1 participant