Software Engineering II project carried out during the academic year 2017/18 @Politecnico di Milano. A full description of the context can be found here. We were asked to develop four subprojects: the first two of them are theoretically based (mandatory), the other two are about the implementation (optional). They are briefly explained below but check out the Deliverables folder for further info.
Short for Requirements Analysis and Specification Document. We give an initial introduction of the problem, all the goals and the functional and nonfunctional requirements are illustrated thereafter. Several diagrams such as UMLs, of sequence and statecharts are associated for most of the use cases. Finally a possible model of the context is shown using Alloy.
Short for Design Document. We present the underlying architectural and design patterns of Travlendar (such as MVVM, SoC, High Cohesion and IoC) as well as the user interface and the interactions among various components and the algorithms; by specifying in details the requirements previously shown in the RASD.
Short for Implementation and Test Document. We developed a cross-platform (iOS/Android) mobile application using Xamarin.Forms as framework. Just note that the login is handled with a third-part service and we used AWS Cognito to store data on the server. We did both tuning and testing (TDD). Here are some screenshots (others at ITD Document/screenshots).
Short for Acceptance Test Document. We evaluated another's group project and tested it.
Group registration (1/10/2017)Open discussion on RASD (11/10/2017)RASD submission deadline (29/10/2017)Presentation of RASD and peer review (8/11/2017)Open discussion on DD (8/11/2017)DD submission deadline (26/11/2017)Presentation of DD and peer review (30/11/2017)Implementation project request (7/12/2017)ITD submission deadline (7/01/2018)ATD submission deadline (14/01/2018)Final presentation and discussion deadline (21/02/2018)
By @antoniofrighetto, @leogivo and @hichame.