We’ll keep it short. Here’s a quick overview of what we have done in semester number three: Use Cases (POst) Start Canteen Bets SRS SRS Document Feature FILES Feature files will be delivered in 4th semester due to a technology change. GIT Repository Azure DevOps Architecture / WIKI Class Diagrams & Models MVC Architecture Azure […]
Until the last sprint, we set the rails for our microservices’ architecture. For all the ASP.NET Core backends we make use of Domain Driven Development. Without going too much into details, here is a basic gist of our architecture: Domain models are persisted and may consist of a root aggregate, value objects (immutable child of […]
UML, Code Map & Domain Models Creating class diagrams is especially fun when you work with many different domains and boundary contexts. Our challenge was to come up with loosely coupled data classes that don’t cross each others’ boundary context. Bounded Context is a central pattern in Domain-Driven Design. It is the focus of DDD’s […]
Today’s lecture was hosted by an external Scrum master who assigned various tasks that should help us to boost our retro, an essential part of project planning. We’ve looked into our strengths and weaknesses, and outlined them below: Our Strengths Our Weaknesses & Measurements We’ve noticed that we haven’t really implemented anything huge in the […]
As we have already mentioned in previous posts, we are utilizing Azure DevOps as a single solution for all things planning, SCRUM, Git, CI/CD, automated/manual testing and so on. After weeks of using it, we must say that we are pretty much satisfied with it. There’s no need to leave the tool for other tasks, […]
This week we looked into Cucumber’s Gherkin, a language syntax specification that accelerates behavior-driven development and allows us to specify features. The syntax is not hard to learn. We were able to outline our first feature file within 15 minutes. However, we noticed that we can’t really specify many feature files since most of our […]
A look into first use cases and mockups. Read more.
This week we learned about SRS and started to incorporate it into our project. SRS help us to stick to our processes and goals by defining requirements that cover different areas during development. Read more.
This week we defined and assigned our team roles. As suggested during the last lecture, we referred to IBM’s PUR guideline – a standardized guideline which is being used for many enterprises – and picked the roles that suit us individually:
In this post we are going to present our vision, our previous project and some brief technical details. Read on for details.