-
Notifications
You must be signed in to change notification settings - Fork 0
Iter1 Minimal Viable Product
This document summarizes the MVP iteration, it is about following the plan that we made in the previous iteration , we will follow, extend, and optimize the kanban board and the tasks required to complete the project in the product backlog, we also begin to plan for the next iteration.
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 the rest of the code and data to rest upon, in order to do so we split performing each task into two steps, the first is making a simplified version for each function, class, and json object and testing it for readiness, suitability and optimization, and then filling it with the proper data. we have to do so because there is a huge amount of data that need to go into each object and in case the format needs to be changed we will have to start from the beginning wasting a lot of time, we have chosen to use javascript as our simplified version language because it allows us to easily change core elements in the object without problems, compared to angular in which we have to modify other parts of the program because of compilation errors. and after much consideration we have come to the conclusion it's the best to use javascript first to implement the features, and then porting it to angular.
We split into three teams, that will do the following:
- collect office data and compile it
- build the college tile map
- start designing the routing algorithms that will be used
- review the achieved work that we have reached
- document the achieved progress and the proper documentation for the project.
- Nearly finished collecting data for the offices in the college
- Finished converting the college map into tile map format
- Started processing the office information
- Started on building the code algorithms and internal class and functions design
- Started on using leaflet js to build the user interface for the map
source code
routing algorithm
this algorithm is yet to be added to the AzrieliMap.js module
Unfortunately leaflet js doesn't support all the functionality needed for the navigation feature, and in order to continue with the project, we have decided that it's best to continue using it (instead of trying to find an alternative) and implementing the missing feature by ourselves. because of this the navigation functionality will take an extra amount of time to be finished, most likely by the start of the next iteration.
leaflet splits it's view into three layers (map, markers, and buttons), that are stacked on top of each other. each layer will be responsible for different things, and they will be connected with each other through the program logic.
This service knows all the available paths, and if we pass a starting point and a destination to it, it will calculate the best route to get to the destination, this information will then be translated into a routing layer that leaflet js will draw above the map layer.
-
Team 1: collect all office information including locations and services.
-
Team 2: design the internal structure of the classes and functions, build the navigation algorithms, document these information, started documenting the MVP page and making it ready for the other team members results.
-
Team 3: Create the college map using photoshop to remove sensitive information and modified the map for our purpose, build the tile maps, tested the tile maps using javascript, and built the tile map prototype.
- start using leaflet js
- Create tiled map for each floor.
- Collect destinations information for each floor
- decide json objects internal format for the routing service
The next iteration we will be completing the office information service, compile the destination information that we collected in this iteration and add it to the maps that we created, initialize angular project and start adding javascript modules to angular, we will also be working on the routing service that will manage the back-end of the navigation part.
SRS
SDS
User Manual
Product documentation
Project Board
Issues