People, Memberships, and Decisions

Here is a list of everyone in the FAE course. As this needs to be a public repo (otherwise Github Pages are not allowed), we won't use real names here. Instead, everyone is identified by a 3-letter acronym (one letter first name, two letters last name). This means that "Stefan Bente" goes as "SBE".

In addition, the table lists team and SIG memberships, and decision(s) the person is responsible for.

Akronym	Nickname	Team	SIG	Decisions
SBE	Stefan Bente	???	???	Asynchronous over synchronous communication for all sub-domains   Conventions for REST URIs   All documentation (apart from the decision log itself) has to be stored in a Github wiki, in repo evatool-backend   A DTO pattern should be used in the APIs   UUIDs are to be used for Entity IDs (PKs and API IDs)   Some basic styleguide for domain modelling   In the backend, we will follow the "Modulith" architecture style   The package structure should reflect the DDD layer architecture   In the backend, Spring is used as predominant programming framework   In the backend, Java is used as programming language   Development model is "Single Repo"
HBU	hbuhl	Impact	DevOps	API Testing   Tool Chain for Build Pipeline - GitHub Actions vs. Jenkins   Event Testing   Testing Automation with GitHub Actions   Source code and test structure (and how to run applications and tests)   API Specification for Team "Impact"   Domain model for team "Impact"   Event Specification for Team "Impact"
MHA	mhallweg	Analysis	DevOps	Maven is used as build tool   Definition of Quality Gates in Sonarcloud   SonarLint and SonarCloud are used as code-quality tools   Domain model for team "Analysis"   Event Specification for Team "Analysis"
PKL	Peter Klein	???	???	All documentation (apart from the decision log itself) has to be stored in a Github wiki, in repo evatool-backend
AKO	akosmehl	Variants	Eventing	Branch strategy during development   Spring eventing is used as Eventing Solution   API Specification for Team "Variants"
JLÜ	jalue	Requirements	APIs	Conventions for REST return codes and error handling   Events need to be defined in a public package within the domain   The preferred way of synchronous communication between modules are api calls   JSON   API Style is REST Level 3   The Uri style is lower camel case   Domain model for team "Requirements"   Event Specification for Team "Requirements"
FOB	FalahSama	Analysis	APIs	Relational database vs. NO-SQL DB   Configuration database state dev and prod   MYSQL used as database   Database version control   API-Documentation is done using Swagger   API Specification for Team "Analysis"   Domain model for team "Analysis"
KRU	kruck	Variants	Eventing	We maintain a high-level global "Domain Story Telling" model   Communication pattern for events is "Full-Payload"   Research method to define the domain is Domain Story Telling   Domain model for team "Variants"   Event Specification for Team "Variants"
JSP	SohleDelfin6504	Requirements	APIs	Branch strategy during development   Logging Strategy   JSON   Web MVC with manual link   API Style is REST Level 3   Single module project   Development model is "Single Repo"   API Specification for Team "Requirements"
MTO	TheBuro	Requirements	APIs	Relational database vs. NO-SQL DB   Access security through REST-API authentication methods   Configuration database state dev and prod   MYSQL used as database   Database version control   API Specification for Team "Requirements"
DUZ	Duzun	Variants	Eventing	We maintain a high-level global "Domain Story Telling" model   Communication pattern for events is "Full-Payload"   Research method to define the domain is Domain Story Telling   API Specification for Team "Variants"   Domain model for team "Variants"
TZA	tzaika	Impact	DevOps	Branch strategy during development   Rules regarding Git-Merge (Merge-Workflow)   Tool Chain for Build Pipeline - GitHub Actions vs. Jenkins   Containerization - VM vs. Docker   Local Debugging using Docker   Choice of Hosting provider   API Specification for Team "Impact"   Domain model for team "Impact"   Event Specification for Team "Impact"