Repository navigation
Project plan
Roles will be assigned according to Scrum methodology. It best represents the view of Product owner.
Product owner: Lauri Liivamägi. Lauri will help the team to control the progress. He will also make key decisions about architecture and transform the stakeholder requirements into project tasks
Scrum master(Devops, Developer): Bolot Kasybekov. Bolot assigns tasks to other team members according to their competence and skills. He is also responsible for organizing team meetings and meetings with stakeholder. He is responsibility is setting up the infrastructure and various development tasks
Team member(Web-developer): Rando Tõnisson. Rando is responsible for various development tasks.
Team member(Tester): Laura Lilleste. Laura is main tester of the system.
Team member(Web-developer): Silver Pajumäe. Silver is responsible for various development tasks.
We have made a skype group and using it to contact each other and the client.
The customer will check our progress by looking at the tasks in Trello and Toggl. Trello will show what kind of functionality is implemented and Toggl will show how much time was taken. For some additional info the customer can access the github wiki page.
There will be an API document (using Swagger format) which will be clarified. Then some tests will be implemented and the code for service. If all tests pass, it meets the criterion.
Bolot will assign the tasks to team member based on each one's skills. Laura, Silver and Rando will implement the tasks. The test play a vital role in projects. The tests are written first. We'll follow TDD approach. The code review will be done in github by Lauri. Once the task is implemented, tests are implemented and functionality is working, it can be presented to our customer. The feedback will gathered after each Sprint. The task is done when in github somebody finishes the issue and the functionality is covered by tests.
2nd iteration
Set up development environment. Environment includes Docker containers (NodeJS and MongoDB). In subsequent iterations, those container can be ran in any computer. Two container must be linked so they could work with each other.
Make SpotScore API specification. API should be specified to provide necessary functionality. It should show map. Maps should be available in 3 different categories. Satellite, Ordinary and Mixed
Buld Demo app prototype in HTML/CSS. Prototype should consist of 4 pages. 1st Page shows default map. 2nd page shows three types of map. 3rd page shows radius and necessary points of interests. 4th page shows distance
Tests. Test must be written in order to check if functionality is set correctly. In other words, it is important check if API responds correctly.
3rd iteration
Integrate an app with GPS. On the lower edge there will be a GPS icon that will turn on the GPS and provide the location of the user. On the background there will be a map where the user can mark his location or his LOI. The app should choose a region so the search would not be that complex and time-consuming.
List of categories implemented. There will be a list of categories (of POI’s) from which the user can choose from. And also there will be a category search with tags. There will be a service providing the categories
Increase the functionality of POI's. Next to the map is a list of the results (POI’s with the object name, category and distance from LOI). When user clicks on a result from the list, both the list entry and the location on map should be highlighted.
Tests. Test must be written in order to check if the functionality is set correctly. It should check if the list of categories are correct.
4th Iteration
Show route. At final stage the app should draw route to the POI of an object. The functionality should enhanced as well. It should be able to add new vertices to the line and move vertex to new location.
Tests. Test must be written in order to check if the functionality is set correctly. It should check if vertices are added correctly and if vertices can be moved.