Report - (3rd Sem.) Week 7 📢

[FurKay00]

Welcome to the seventh report of our progress. We are excited to share the latest news with you! 🥳

Capturing our architecture significant requirements 🛠️

Last week, we discussed about important quality attributes regarding our project by capturing the most essential scenarios. Thus, we created a table regarding many individual events which include the end users or developers and thought about methods which we could use to counter occuring problems. You can either see the full table here or some examples in the following picture:

From these quality attributes, we have extracted three important use cases and created an utility tree which you can see below and will also be described in more detail afterwards. We have also updated our srs with the non-functional requirements section, if you are even more interested!

Quality attribute 1 - Feedback 💬

Throughout the whole application, the usabilty of our web application should be simple and easy to understand. One way to achieve this goal is through visual feedback. If a user changes his settings or tries to create new posts and comments, he should get a visual hint, whether his transactions applied successfully or not e.g. a temporary label 'post has been successfully created' or 'Something has gone wrong'.
The amount of information displayed also needs to be balanced. It should be as little as possible yet enough to help the user if problems occur. One example would be the attempt to sign in onto our website. If the credentials are wrong, we tell the user that the username or the password is incorrect without further hints that could indicate our database architecture to provide more security!

Quality attribute 2 - Modularity ♻️

This attribute rather appeals to the developers but also includes the end users. Our main design should stay modular in order to allow easier und faster development of new features. On the one hand, it helps the end users to navigate through our application without getting confused. On the other hand, developers can extend the application with new code components without disturbing the already existing system. One way to reach this goal is through an previously established CI/CD pipeline which already covers most areas. Another way is through atomic component architecture. The web design is composed of several small components which are composed of even smaller different components. By reusing already programmed assets, the addition of new features should reduce the development time drastically.

Quality attribute 3 - Quick response ⏩

If an end user wants to use the features of our website or requests certain components, the response time shouldn't take more than a maximum of 10 seconds (our first estimation, might change later). High latency worsens the mood of the end user. Thus, some structures need to be established to be responsive all the time:

• Giving visual feedback and stopping request, if response time takes too long.
• Using intermediate data layers where important data is already stored and only waits for a request.
• Already storing frequently requested data in a database view which can be delivered immediately when needed.
• Asynchronous loading in the background if the user doesn't need the feature at the moment but might use it later on.

Finished calendar mockup 📆

We have finished the mockup to our calendar which contains events that could be interesting for university students. We want to keep the calendar static at the moment which means that every student can see the same events.
Right below is the monthly view of the calendar:

This is the weekly view of the calendar:

Post with event mockup 📅

We have created a new version of our post mockup which displays an event post. A map with the event location is also included:

Implementation of login/sign-up window 🪟

The first step towards the actual sign-in/up process is ready! The windows are designed just like the respective mock-ups, the functioniality however is not implemented yet. You can see them in the following pictures:

Implementation of contact form 📞

We have finished the actual implementation of our contact form. You have to enter your e-mail, name and message to send it to the site administrators!

Sprint 4: What have we achieved ❓ What's to come❔

✅ Finish Calendar Mockup in Figma
✅ Implement Login Window
✅ Implement Sign Up Window
✅ Implement contact page
🚧 Discuss search opportunities and create mockup
🚧 Implement post menu
🚧 Implement first frontend endpoints
🚧 Implement e-mail verification
🚧 Setup postman for whole team
🚧 Create endpoints for search
🚧 Create endpoints for the sort options of posts
🚧 Removing Herobrine

Until next week 💯

Your DHBWhub Team 🚀

[ins305]

Hi Team DHBWhub,

You have a very good collection of different quality attributes. Also, your top 3 scenarios are a good choice for your project as they cover important topics.
Overall, your descriptions of the quality attributes are very clear and detailed. Good job!

I can see that you also put a lot of effort into your really nice design for your project.

Keep up the good work!

[dolerich-hirnfiedler]

Dear DHBWhub Team,

Impressive progress report! 🌟 Your detailed analysis and strategic approach to quality attributes showcase a deep understanding of project intricacies.
The utility tree visualizes key use cases effectively, emphasizing user-friendly feedback, modularity, and quick response times.
Your commitment to simplicity, modular design, and efficient development through CI/CD and atomic components is commendable. The proposed strategies for quick response times reveal a keen awareness of user satisfaction.
The finished calendar mockup adds a tangible highlight to your achievements. Kudos to the team for a thoughtful and impactful update! 🚀👏

[LeonmAndreesen]

Hi,
your weekly update is stunning. For sure, the best report so far. It is so detailed. Moreover the amount of tasks, that you achieved is superb.
Your mock-ups are really great to look at. Nicely chosen colors enhance the visual perception of the first impression.
Even though you did not implement functions on them, you are on a good way.