-
Notifications
You must be signed in to change notification settings - Fork 0
ZFR Zero Feature Release
This document summarizes the first iteration which is iteration zero, the first iteration is about planning, we create a kanban board and list all the tasks required to complete the project in the product backlog, we also begin to plan for the next iteration (iteration 1).
All tasks are represented as an issue, when a task is done the issue is closed. (the board is automatically updated this way)
Our goal in this iteration is to provide a stable and good cornerstone for our development process, in order to do so we have focused our efforts on choosing and building a good development environment for our team members, we have chosen to use angular as our main programing language and after some consideration we have come to the conclusion it's the best to use the class's version control and other equipment, such as git, visual code, and firebase.
| Task | Priority | Estimate (its) |
|---|---|---|
| Create a tiled map for each floor | 1 | 1 |
| Collect destinations information for each floor | 2 | 1 |
| Write languageService component and connect it to map | 3 | 1 |
| Write locator component and connect it to map | 4 | 2 |
| Write routingService component and connect it to map | 5 | 2 |
| Write GUI and connect it with all the components | 6 | 2 |
We will follow the class in dividing the project into iterations, which means four iteration that are in sync with the class submission, these four iterations will respectively focus on these subjects: navigation, offices description and search, multi-language support, and GUI. each iteration will involve some parts of the rest of the iteration -to insure compatibility- but will focus on it's current objective.
Our prototype is to build an indoor map with all destination locations listed in the map, in the SDS document we mentioned that we are trying to upload the floor plans to Google Indoor, we tried Google Indoor and turns out it will take at least 4 months to be done, and so we chose to switch to Indoor Atlas API but in the end it turns out that it's not compatible with angular, therefore we have finally decided to make our own navigation service, to create our own tiled map and to use Leaflet js which is a javascript library for mapping, we are currently in the process of creating a map for each floor.
this is the navigation prototype, it is implemented using angular 2
https://navigation-prototype1.firebaseapp.com
floor -1 tiled map : Click Here
floor -2 tiled map : Click Here
We have presented our project SRS to our costumer, we still didn't receive a response from them.
we will use Agile programming method with Kan-ban, which will be used to guide us through the process of finishing each iteration.
We will be using angular 2 framework. we will use Github to share the code between our programmers, which will make it easier to submit iteration results. we will use Github services to implement Agile programming method, such as Github Issues, Github Project,...
The next iteration we will be completing making tiled maps for each floor , collect all the destination information and add it to the maps created.
SRS
SDS
User Manual
Product documentation
Project Board
Issues