iter4 testing,GUI, and finishing the project
This is the final iteration. In this iteration we will complete all the features that are left from the previous iteration, such as the search and the menu features, we will be connecting all the features together, and finally creating a working and usable GUI in AngularJS and testing our final product.
This document summarizes this iteration, it is about finishing the project.
The goal of this iteration is to deliver our final version of the product after testing it in order to insure that we deliver a working and usable product that is free from bugs.
In this iteration:
- Finish search engine.
- Connect all the components to AngularJS.
- Test the product.
During the meeting we were asked to change some features, mostly the menu feature. The client have also asked us to fix some information that was changed after we have collected the information about the staff. In a minimal time, we were able to fix what was required.
- Cooperated with John in order to finish the search engine.
- Fixed the Json file.
- Cooperated with John in order to finish the menu feature.
- Worked on fixing the translation file and the json file in order to fix the information that the client required our group to fix.
- Finished the menu feature.
- Connected the map to all the other services.
- Finished the GUI.
- finished the graphing service
- finished and connected the routing, navigating, and geoService components.
-
Lina and Muhammad: cooperated with John in order to complete the menu and the search features, fixed the Json file in order to fulfill the requirements from the final meeting with the client.
-
Carlos and Antonio: finish the graphing, routing, navigating, and geoService components.
-
John: finish the menu, connect the map to the other members services, finish the GUI.
this iteration went smoothly, mostly because it was connecting the components -which were made previously- together to the final application environment. there weren't any major problems that appeared in this iteration
we have updated our product documentation as requested.
the team values that were published in the beginning has helped us a lot overcoming the problems that we faced during some of the iterations, for example: when google indoor API didn't work and we had to look for an alternative, we worked hard on finding the solution and avoided blaming the others on the decision. the same was for the angular 2 environment, in which we replaced it with angularJS and didn't waste time contemplating on the issue.
the work went smoothly and fitted really well with the iterations, all the problems that we faced were solved inside the relevant iteration. this is thanks to the careful planning and the helpful guidance of the teacher, TA, and the documented course materials.
the course has help us a lot in understanding what it means to be a software engineer
- we learned that planning is a really important part that isn't to be skipped in any project.
- we learned that choosing teams is a really difficult job, and has to be planned for.
- we learned that not everything will go as planned, but with hard work and dedication the project will not suffer from these things.
SRS
SDS
User Manual
Product documentation
Project Board
Issues
