Portfolio

By Joris Brugman & Morris Hannessen

Overview

• Portfolio
  • Overview
  • Introduction
  • Project organizations
  • Learning outcomes
  • Research documents
  • Learning outcome rating table

Introduction

This document serves as the guide through semester 3 demand-based software. Here we shall connect all our documentation to our learning outcomes. The goal here is to demonstrate the skills necessary to pass this semester.

Project organizations

• Individual project repository

  • Frontend
  • Backend
  • Portfolio

• Group project organisation

  • Frontend
  • Backend
  • One-drive documentation

Learning outcomes

• 1. Web Application
• 2. Software Quality
• 3. Agile Method
• 4. CI/CD
• 5. Cultural differences & ethics
• 6. Requirements & design
• 7. Business processes
• 8. Professional

Research documents

• Security
• Privacy research

Learning outcome rating table

Learning outcome	Proficiency rating	Elaboration
Web application	${\textsf{\color{lightgreen}Proficient}}$	User-friendly : The develop frontends have gone through a design phase and were tested both internally and externally (classmates/POs). Full-stack : The applications in both the team and individual projects have a functional backend using an ORM which implement asynchronous communication. To view the specific tech stacks see the outcomes.
Software quality	${\textsf{\color{lightgreen}Proficient}}$	Tooling and methodology : All backend code is tested using xUnit, the frontends are tested using Jest. These are automatically executed upon creating a pull request. Sonarcloud is used to apply static code analysis to ensure low code duplication, no security hotspots nor code smells are present within the code. Next to that we use code reviews to ensure one another's quality upon creating pull request.
Agile method	${\textsf{\color{lightgreen}Proficient}}$	Choose : Iterative and in sprints: During the semester, our team overcame challenges in adopting Scrum, including adapting to three-week sprints and using tools like Jira. Through regular reviews, we received valuable feedback, fostering a culture of continuous improvement. Despite initial struggles in defining our "Definition of Done," collaboration with teachers enhanced our understanding. The efficient management of the final sprint demonstrated our team's growth, positioning us well for future projects and further mastery of Scrum.
CI/CD	${\textsf{\color{violet}Advanced}}$	Design and implement : CI/CD was implemented for our project using GitHub Actions and Docker, creating Dockerfiles for NexJs and .NET. Automation was enhanced with GitHub Actions and SonarCloud for code and security checks, complemented by additional workflows for pushing the frontend and backend to DockerHub.
Cultural differences	${\textsf{\color{lightgreen}Proficient}}$	Recognize : During the semester we have learned different ways to communicate and how to handle a difference in expectations with regard to deadlines, communication and argeements. Take into account : We have learnt how to handle different views and accompany those into the development and eventual result of our application(-s). ACM : To address this, ACM 1.2 and 1.6 have been taken into account in the projects. ACM was a valuable source of information and inspiration in regard to ethics & ICT.
Requirements & Design	${\textsf{\color{violet}Advanced}}$	Multiple types of test techniques : The functional/technical requirements set by the product owners were taken into account, analyzed and used in the group project. In the documentation of each project the architectural choices have been explained and documented where deemed neccessary. There are multiple type of tests within each project, mostly in the category of UI, unit and integration. These were made to validate the exisiting requirements and ensures any future ammends to features don't break existing ones.
Business processes	${\textsf{\color{lightgreen}Proficient}}$	Simple and related : For the group project, a business process was visualised to show the improvement that the app is able to offer with alternative flows for both existing and potential paths.
Professional	${\textsf{\color{violet}Advanced}}$	Professional manner : During the semester we have worked in duos for the individual project, the group project was a group of 6 teammates. The GP was a great place to learn and use agile principles. We learnt the importance of proper communication both in the team aswell as between the team and stakeholder(-s).