MSc Software Engineering student of the University of Southampton.
Student ID: rk11g14
As already illustrated in the Architectural Design, our system follows a traditional client-server infrastructure, where the mobile application is the client that communicates with a centralised server over a REST API using JSON. The reason why we chose REST over SOAP is because REST is simple (it uses standard HTTP methods like GET, PUT, POST and DELETE), infrastructure friendly (all… Read more →
The architectural design of our RESTful application follows a traditional client-server infrastructure (see graphic below), where many clients request and receive data from a centralised server. Further information on the architectural design can be found at Standards and Protocols.
The following functional requirements were derived from the user stories. Those requirements give an overview over the functions and capabilities of the system and form the basis for the implementation. Further explanations on how to implement those requirements will be given in the software design. Requirements: FRQ1: Unregistered users can login with their Facebook, Google and Linked account. On first login, an account… Read more →
The UML diagram below shows the main functionalities of the system from a user’s perspective that have been derived from the user stories. The actors of the system can be divided into unregistered users, registered users and meeting initiators. Unregistered users can either register with their social network accounts or by providing name, surname, e-mail address and age. Registered users… Read more →
In order to have a proper software engineering process, we had brainstorming sessions to collect user stories. Moreover, we conducted a survey and asked, among other questions, which functions are needed to make our application desirable for the customer. These user stories (see also use case diagram) are the basis for the derivation of functional and non-functional requirements, which in turn are the… Read more →