Short explanation

For the Requirements Analysis course in the first semester of the second year, we were divided into different groups to work together to prepare a requirements analysis for a client. I was in a group with Matthias Verstappen, James Ceesay, Badr Azougagh, Emile De Vlieger and Simon Horemans and we had as a client Bart Portier. He is care coordinator within the Electronika-ICT direction at Thomas More, and helps students with disabilities increase their chances of success, by looking together at what facilities they are entitled to. As care coordinator, he is responsible for managing every file within his direction. Teachers who want to know before an exam, for example, which students are entitled to which facilities, must communicate with him about this.

At the time when we started preparing the analysis, all communication was still done via email, and various files were sent back and forth. Managing the file was also done manually. A lot of time was lost with repetitive tasks and procedures, which could be automated. Our goal was to design an application that would keep an overview and make the care coordinator's job easier. To do this, we sat down several times with our client, to identify the functional requirements and to show the interim progress of the requirements analysis.

My part within this group work was to design some views and make sure the documentation was on point. During this assignment, in terms of hard skills, I learned to work with Axure to create prototypes and with StarUML to create use case diagrams. Before each talk, we agreed on who was going to say what and when. Clear introductions were made beforehand, with what the purpose of the conversation was, and at the end we made clear agreements with the client, about what was going to be finished by the next time.