Nina is a postgraduate student at the University of Southampton. She is a curious person and has a lot of different interests. Therefore, she studied multiple subjects. She heard other students that they are looking for a supervisor, but she wants something more: she wants an excellent one! Continue reading “Storyboard”
After identifying the application purpose and target group, based on these we developed a set of requirements that should be met on the application. But before the actual development of the software, we needed to decide what is essential for the first version of it [1] and what features are recommended for the future work. Thus, we chose to prioritize the requirements. We used the MoSCoW technique to do so. This way, we selected an appropriate set of requirements from the overall set in order to develop cost-effective software that respects its purpose. We, also, identified the desired or nice to have features in the future versions. A brief description of the MoSCoW technique we applied can be found below: Continue reading “Application Requirements”
Click the image to zoom
*Notes:
The application architecture falls into the so-called “Three Tier Architecture” model (click the image for zoom). We chose this architectural model in order to ensure the flexibility, security and performance of the application. The functionality is separated into three different tiers.
Continue reading “System Architecture”
The featured image displayed above (for zoom, click the image) is a brief representation of the application flow. It is styled as a pseudocode graphic. Continue reading “Application Screens Flow Chart”
