Merge branch 'main' of github.com:htw-imi-showtime/showtime-website

content/ss24/bachelor/b3-lunarfit/_index.md

@@ -6,7 +6,7 @@ claim = "Exercise in Harmony with Your Cycle"
 abstract = "More than a fitness or period tracker, LunarFit helps athletes better understand and adapt their training to their menstrual cycle. This reduces the risk of injury, aids in recovery, and supports long-term performance development."
 
 # Properties for displaying the project in the project list
-card_image = "lunarfit_preview-no-claim.jpg"
+card_image = "lunarfit-preview-no-claim.jpg"
 
 # card_description is deprecated, will be replaced by abstract/and or claim
 # card_description = "Exercise in Harmony with Your Cycle" 
@@ -43,7 +43,7 @@ All of this allows to make more informed decisions and communicate better with t
 {{</section>}}
 
 {{<section title="Process">}}
-The foundation of our project was provided by the Institute of Sports Science at the University of Bern, giving us a scientific basis to build upon. They initially presented their idea using a Miro Board, setting the stage for our development process. As we progressed, we continuously refined and expanded the concept, ensuring it evolved effectively the project.
+The foundation of our project was provided by the Institute of Sports Science at the University of Bern, giving us a scientific basis to build upon. They initially presented their idea using a Miro Board, setting the stage for our development process. As we progressed, we continuously refined and expanded the concept, ensuring it evolved effectively throughout the project.
 
 Before officially starting, we conducted a market analysis to assess the landscape and understand user requirements. Using the insights gained, we defined a set of features and created database and API schemas and clickable mockups in Figma to visualize the app's functionality.
 

content/ss24/bachelor/b4-sempy/_index.md

@@ -22,11 +22,13 @@ source_link = ""
 
 
 {{<section title="Our Goal">}}
-In recent years, artificial intelligence technology has advanced significantly, and today many people use technologies such as OpenAI's GPT-4, Google's TensorFlow, and IBM Watson because these tools make life easier. Our goal is to simplify the user experience on idealo, helping with purchasing decisions and saving time during researching for a product. Our SEMPY research aims to gather the most important product data and customer opinions in one place, avoiding the need to search on different platforms such as YouTube, Amazon, and Google. 
+In recent years, artificial intelligence technology has advanced significantly, and today many people use technologies such as OpenAI's GPT-4. Our goal is to simplify the user experience on idealo, helping with purchasing decisions and saving time during researching for a product. Our SEMPY research aims to gather the most important product data and customer opinions in one place, avoiding the need to search on different platforms such as YouTube, Amazon and Google. Instead SEMPY processes data from idealo and external websites (Amazon, Youtube) with OpenAI to generate summaries, pros and cons, customer reviews, FAQs, and targeted audience recommendations.
 {{</section>}}
 
+{{<image src="screenbildmodaln.jpg" alt="Screenshot vom Modal" caption="SEMPY-modal on the idealo Website.">}}
+
 {{<section title="The Team">}}
-Team SEMPY consists of us five young IMI students **S**on, **E**ldar, **M**athieu, **P**aul and **Y**asin (SEMPY) who came together to build this project. None of us had experience working with the OpenAI API, so it was quite a challenge for us. Through this project, we gained a lot of knowledge about working with AI and by supporting each other during the development.
+Team SEMPY consists of us five young IMI students **S**on, **E**ldar, **M**athieu, **P**aul and **Y**asin (SEMPY) who came together to build this project. None of us had experience working with the OpenAI API, so it was quite a challenge for us. Through this project, we gained a lot of knowledge about working with AI and by supporting each other during the development. To collaborate on coding, we used GitHub, and for communication, we relied on Miro, Discord, and WhatsApp. 
 
 
 {{</section>}} 

content/ss24/bachelor/b4-sempy/features.md

@@ -5,9 +5,12 @@ draft = false
 +++
 
 {{<section title="Features">}}
+
+{{<image src="button.jpg" alt="Screenshot vom Button" caption="SEMPY-Button on the idealo Website.">}}
+
 Our SEMPY Button offers a relaxed shopping experience that provides customers with recommendations based on the information from the three major platforms: idealo, Amazon, and YouTube. Whether the customer is interested in products like a "Victorinox Huntsman", an "MSR Hubba Hubba 2 NX", or "Apple AirPods 3", the SEMPY-AI Tool caters to the customer's individual needs.
 
-{{<image src="screenbildmodaln.jpg" alt="Screenshot vom Modal" caption="Screenshot of SEMPY-modal on the idealo Website.">}}
+{{<image src="screenbildmodaln.jpg" alt="Screenshot vom Modal" caption="SEMPY-modal on the idealo Website.">}}
 
 We take information from idealo, YouTube and Amazon and give them to the OpenAi to process and summarize them. It then generates a text with all the important information in an overview with pros and cons, a short summary of customer reviews, a review video, FAQ's and a recommendation of a target audience. 
 

content/ss24/bachelor/b5-pam/_index.md

@@ -1,24 +1,23 @@
 +++
 project_id = "B5"
 title = "PAM"
-subtitle = "Project Modeling and Management"
+subtitle = "Process Modeling and Management"
 claim = "Redesigning and Improving a Tool to simplify the creation and organisation of Process Diagrams in the Business Process Modelling Notation"
 claim2 = "Upgrading and enhancing a tool used to create Process Diagrams and organize them, modernizing the design and more"
 abstract = "PAM is a tool that was originally developed for GlobalCT by Students of the Leibniz Universität in Hannover. The Tool's purpose is to allow for the simple creation of Process Diagrams using a simple interface, as well the saving and exporting of those diagrams in various formats as required, organizing them depending on the preferences of the creators by allowing for a custom repository structure of folders and sub-folders.It also has an internal organization scheme following a simple folder/file format. However, it was rather simple, focusing on the basic features initially. That's where we came in."
 
 # Properties for displaying the project in the project list
-card_image = "PAM.png"
+card_image = "pam2.png"
 # card_description is deprecated, will be replaced by abstract/and or claim
-card_description = "Upgrading, Reworking and rewriting a Project Tool for a certain Company" 
+card_description = "Upgrading, Reworking and rewriting a Process Tool for a certain Company" 
 # Names are optional, team size is sufficient
 team = ["Margarita Boiko", "Hamzeh Hamzeh", "Anh Phuc Hoang", "Lukas Oswald"]
 supervisor = ["Dr. Sue-Ann Bäsler", "Martin Singer", "Vu Minh Le", "Mariam Maisuradze"]
 draft = false
 
-# bitte hier zur projektwebseite verlinken. Der Verweis auf die Firma kann gerne in den Text.
-# website_link = "https://globalct.com/"
-# ist nicht öffentlich:
-# source_link = "https://github.com/SueAnnBaesler/PAM-Software-Project-HTW"
+
+website_link = "https://showtime.f4.htw-berlin.de/ss24/bachelor/b5-pam/"
+
 
 tags = []
 categories = ["External Stakeholder"]
@@ -42,11 +41,11 @@ The base PAM lacked quite a few features and had a very outdated design, so the
 
 {{</section>}}
 
-<!--
+
 {{<section title="The team">}}
 
 {{</section>}} 
--->
+{{<team-member image="pamgroup.jpg" name="Unser Team">}}
 {{<gallery>}}
 
 {{</gallery>}}

content/ss24/bachelor/b5-pam/process.md

@@ -21,3 +21,33 @@ Every two weeks, we presented the results and discussed the difficulties, keepin
 
 
 {{</section>}}
+
+{{<section title="Future">}}
+
+As this is a project on a limited-time basis, we are not planning on adding new features. However, we are going to add enough comments and documentation so that the next group to pick it up and try to improve on it will have an easier time. Future improvements to PAM would include Syntax Investigation of the diagrams, more in-depth filtering, perhaps even a social media share function. We ended up creating a solid base program that can allow for future improvements by the next group to work on it as we pass them the torch.
+
+As for our personal futures, we plan on taking the skills we developed in this project and perhaps improving on them in our repertoire to use in our future jobs and prospects.
+
+
+{{</section>}}
+
+{{<section title="Personal Reflections">}}
+
+Lukas Oswald: While the project was initially off to a rocky start due the new language we had to learn and the fact that we had to organize ourselves, we took our time and quickly managed to settle into roles we were comfortable with. Everyone quickly learned how to use their strengths to provide valuable updates and upgrades to the program, as well as the general working atmosphere, and it definitely helped us all become a more close-knit group as well.
+Each of us managed to find a way to implement our respective strengths into the project, and used them to support each other in various ways to create a project we can honestly be proud of. I was initially a bit nervous about my role in the project, but once I found out how valuable the organization was and how much it helped everyone, I took to it with gusto and was proud of all the ways I helped people with preparation as well as learning even further how to improve my own presentation skills as well as my organization skills.
+I'd definitely say the project was an overall success, and we all learned a lot about the Scrum Methodology and Agile Development, as well as learning more about the code and working a programming project. It was definitely a peek into our future if we ever have to work in a similar environment, but all in all, I felt it was a very relaxed and friendly environment. The Supervisors from GlobalGT were immensely helpful, and made us feel like we were part of the company, as well as helping with any questions we had, or worries we had throughout the project.
+I would say I learned quite a bit, and I'm looking forward to seeing how people take to our project.
+
+Margarita Boiko: I am immensely grateful for this project. I discovered my strengths and also understood what I need to work on, both professionally and personally. For the first time, I created a design from scratch, learned React, practiced SCSS more, and learned a lot about Scrum management.
+
+Anh Phuc-Hoang: Participating in the PAM project for SS2024 has been a great and comprehensive experience for us students. From being newbies in web programming in the early days, we now feel confident in taking on similar tasks. With the dedicated help of the supervisors at GlobalCT, we have learned a lot—not only about web programming but also about teamwork (SCRUM), problem-solving skills, and, importantly, professional presentation skills. These valuable skills will undoubtedly benefit us in the long run.
+Additionally, the fun and comfortable moments in meetings and lunches are unforgettable. Perhaps this is the catalyst that makes us, the newbies, work productively and effectively (we have completed 95% of the backlog - I'm not lying ^^).
+In short, I am very grateful to be a member of the PAM project in SS2024.
+
+Hamzeh Hamzeh: The project PAM was a great learning experience for me. I learned how to work in a team by using agile working ways, how and when to communicate with team members to ensure a smooth workflow and I learned a lot about web development. How to use react and some parts of spring boot. I learned about implementing an API.
+We had some challenges at first with our teamwork regarding which technologies, structure and dividing the tasks among us, but sprint after sprint we learned how to decide together on what to use and how to do things. I am very happy about that. I feel like we had very good team synergy once we learned how to work together.
+Regarding the project itself I sometimes wished we would’ve had a brand-new project which we did from scratch. Our project already had a backend. We were supposed to create a new frontend for it and we ended up extending the backend. Although it is more fun to do the backend from scratch, I think in the real world I will be working on projects I didn't create myself, so it was good practice to work with someone else's code. The code of the backend wasn't ideal. The structure wasn't the best, and it took me a bit to understand it because it wasn't clean code. I had the option to refactor it, but considering the time we had and the fact that it was working, I decided not to touch it and just extend it the way it was. I would’ve enjoyed refactoring it, but it would have taken a lot of time.
+I also felt like we had very good supervisors. Dr. Sue-Ann Bäsler did a very good job explaining to us how to work in a scrum team and all the aspects of sprints like review, retrospective and planning. Vu Minh Le helped us with technical challenges and sent us in the right direction when we had a problem to solve.
+So overall I'd say I learned a lot during this project, and I’m happy with the outcome, the teamwork and all the knowledge I acquired.
+
+{{</section>}}

content/ss24/bachelor/b5-pam/techstack.md

@@ -9,7 +9,7 @@ draft = true
 We used the following technologies in our Project:
 {{</section>}}
 
-{{<image src="Techstack.png" alt="Tech Stack">}}
+{{<image src="techstack2.png" alt="Tech Stack">}}
 
 {{<section title="Future">}}
 
@@ -20,3 +20,4 @@ As for our personal futures, we plan on taking the skills we developed in this p
 
 {{</section>}}
 
+

content/ss24/master/m1-gaming-for-future/_index.md

@@ -17,17 +17,6 @@ draft = false
 
 website_link = ""
 source_link = ""
-
-# imagemagick befehl
-# magick team_kenneth.png -strip -interlace Plane -gaussian-blur 0.05 -quality 85% team_enneth.jpg
-# magick team_adib.jpeg -strip -interlace Plane -gaussian-blur 0.05 -quality 85% team_adib.jpg
-# magick team_elliot.png -strip -interlace Plane -gaussian-blur 0.05 -quality 85% team_elliot.jpg
-# magick team_martin.jpg -strip -interlace Plane -gaussian-blur 0.05 -quality 85% team_martin.jpg
-# magick team_sebastian.jpg -strip -interlace Plane -gaussian-blur 0.05 -quality 85% team_sebastian.jpg
-
-# magick game_logo.png -strip -interlace Plane -quality 85% game_logo.png
-# magick nabu_logo.jpg -strip -interlace Plane -quality 85% nabu_logo.jpg
-# magick game_image.png -strip -interlace Plane -quality 85% game_image.png
 +++
 
 {{<section title="The Goal">}}
@@ -37,14 +26,15 @@ Our project aims to transform a simulation game from previous term ([Aquasolace
 
 {{<section title="The Team">}}
 Our team consists of five IMI-Master students.
+{{</section>}} 
+
 {{<gallery>}}
-{{<team-member image="team_elliot.jpg" name="Eliot">}}
+{{<team-member image="team_eliot.jpg" name="Eliot">}}
 {{<team-member image="team_kenneth.jpg" name="Kenneth">}}
 {{<team-member image="team_martin.jpg" name="Martin">}}
 {{<team-member image="team_adib.jpg" name="Adib">}}
 {{<team-member image="team_sebastian.jpg" name="Sebastian">}}
 {{</gallery>}}
-{{</section>}} 
 
 {{<section title="The Responsibilities">}}
 <div style="display: flex; flex-wrap: wrap;">
@@ -62,6 +52,7 @@ Our team consists of five IMI-Master students.
     <ul>
       <li>Game Development</li>
       <li>UI/UX Design</li>
+      <li>Website</li>
     </ul>
   </div>
 

content/ss24/master/m1-gaming-for-future/features.md

@@ -1,22 +1,30 @@
 +++
 title = "Features"
 weight = 20
-draft = true
+draft = false
 +++
 
 {{<section title="Features">}}
 
-* **Roles**
+* **Supervised tile based gridmap interactions**
 
-Lorem ipsum dolor sit amet, consectetur adipiscing elit. Nulla facilisis neque id vulputate malesuada. Quisque dignissim finibus urna sed sagittis. 
+Map interactions are controlled and supervised in order to restrict specific player interactions, removing some of the previous sandbox-aspect of the game. 
 
+* **Ground water level sensitive game winning conditions**
 
-* **Game-Flow**
+Player actions directly influence groundwater levels. These influence changes are computed by respecting a data-table though and built to try and mimic somereal-life behavior in the environment.
 
-Lorem ipsum dolor sit amet, consectetur adipiscing elit. Nulla facilisis neque id vulputate malesuada. Quisque dignissim finibus urna sed sagittis. 
+* **Reviving species**
 
-* **Voting Systems**
+Such objectives are displayed in the form of quests and can be achieved in the game by modifying the biomes configuration on the map and applying the right configurations and some other hidden conditions.
 
-Lorem ipsum dolor sit amet, consectetur adipiscing elit. Nulla facilisis neque id vulputate malesuada. Quisque dignissim finibus urna sed sagittis. 
+* **Suitable habitat identification**
+
+Identifying complex habitats that can be considered suitable for a specie appeared quite challenging and asked many experiments. 
+Our actual solution uses a flood-fill algorithm and allow a fluid a peridodic update of the potential suitable habitats for the species.
+
+* **Localization**
+
+The game is supported in English & German language version to provide better accessiblity.
 
 {{</section>}}

content/ss24/master/m1-gaming-for-future/process.md

@@ -1,7 +1,7 @@
 +++
 title = "Process"
 weight = 10
-draft = true
+draft = false
 +++
 
 {{<section title="Initial Meetings">}}
@@ -12,8 +12,8 @@ The three of us, who had worked on the simulation last semester, provided the ne
 We held weekly Scrum meetings with product owners to iterate on and refine project details, working in sprints to ensure continuous progress and alignment with our goals.
 {{</section>}}
 
-{{<section title="Programming">}}
-We primarily programmed in Unity. Our workflow involved pushing our code to GitLab, where we collaborated on different branches, including 'development' and 'main'.
+{{<section title="Programming Workflow">}}
+We managed our Source Code using the Gitflow Workflow and GitLab. Features were implemented, tested and reviewed before integrating them into the devolpment and later the main branch.
 {{</section>}}
 
 {{<section title="Issue Assignment">}}
@@ -22,4 +22,8 @@ Each team member chose a specific issue to address based on their individual ski
 
 {{<section title="Testing">}}
 We conducted regular game testing sessions with the product owners to gather feedback. This feedback was crucial for making necessary adjustments and improvements to the game.
+{{</section>}}
+
+{{<section title="System Architecture">}}
+<figure style="margin:0;"><img src="../architecture_diagram.jpg" alt="System Architecture Diagram"></figure>
 {{</section>}}

content/ss24/master/m1-gaming-for-future/techstack.md

@@ -1,7 +1,7 @@
 +++
 title = "Tech Stack"
 weight = 30
-draft = true
+draft = false
 hasMermaid = true
 +++