Collaborative software engineering
I built booking screens and API logic in a five-person academic team. When someone picks a time, the API checks for a conflict before saving the appointment. Payment and chat use that same appointment. I also wrote controller tests and set up the Azure deployment. The prototype uses fictional data.
I worked across the Angular client, .NET API and SQL data layer in a five-person academic team. The project uses fictional users and appointment data.
Pick a step to see where it runs, from choosing a time to saving the appointment.
The Angular screen sends the chosen professional and time to the API.
I checked that the slot was available and didn’t overlap an existing appointment.
After validation, the API saves the appointment to SQL Server through Entity Framework Core.
Angular shows the state returned by the API. Payment and chat both refer to the saved appointment.
I connected professional availability, conflict checks and appointment states to the booking interface. Payment, refund and chat behaviour then had to refer to the same appointment.
I worked on the EF Core models, queries and migrations behind those flows and kept the client services and API contracts in step as the team changed them.
Changes crossed Angular forms, request data and controller behaviour. I added xUnit/Moq controller tests for agendas, appointments and management, using SQLite and InMemory databases.
I also configured GitHub Actions to build the backend, create its deployment artifact and deploy it to Azure Web App.
I built shared Angular routes, forms and components for authenticated areas. Account access, bookings and appointment-linked chat use the backend's validation and stored state.
The wider feature set was team work. The platform's endpoint and test totals below describe that shared delivery.
Across the five of us, the prototype reached 104 REST endpoints across ten controllers and 29 test methods. My own tests covered the agenda, appointment and management controllers.
I learned to follow a booking change all the way through. If the server changes how it validates a slot, I need to check what the form sends and what the payment flow sees after the appointment is saved.