Team Blog Week 4

This week we finally have a clear sight of what we need to do and how we are going to do it. Below there is the preliminar arquitecture for our project with the different technologies we are going to use:




We are going to use Heroku to host the whole project, Postgress for our DB, Go for the API and VUE for our web client. Travis is used for CI and solid still has a grey area defined for it as we dont know exactly how much we are going to implement.

We are also going to be splitting our work load so that each of us focuses on the different areas, Martell will be focusing on data analysis, Lucia on front-end design and implementation and Jesus on API integration. From the other courses we will have a group focusing on creating tests for our project. The Go API will probably have a TDD focused approach, while front end tests will be developed after those parts are done. On the Web development course we are focusing on the Go API and postgress integration as well as mounting the services on Heroku.

We will begin working on the project next week, with a basic iteration.

Comentarios

Publicar un comentario

Entradas más populares de este blog

Team Blog Week 3

Imagen
This week, following our meeting on Monday, our communication with the Alberta team has been more constant. They've let us in some of the details we missed from our video meeting and informed us of some specific requirements their clients have. We've also been discussing with them about which technologies we've used in the past and feel most comfortable with. This has led to some agreement on the most part, deciding that (mostly) we'll be taking on the web development side of the project and them on the mobile client. We were also presented with a general idea of what this app is planned to look like: With all this in mind, we've decided as a team to go with the following system features: visualization of points of Interest in map routes creation with multiple points of interest, in order routes can be approved or dismissed by other users information about MiBici stations for routes information about points of interested can be edited by users automat...
Leer más

Week 1 Planning

Imagen
This week we plan to continue researching about similar projects to what “Yeg AR” aims for, to get a better understanding of what existing products are out there already. Using the document that explains what the project is about, we identified some technologies that are proposed to be used in the project. We will research the technologies as well as how to implement them with AR. It would be great if we find sometime for us to actually chat with the students from Alberta, to agree on the requirements, specifications, tools to be used and how we’ll distribute the work. From what we’ve read in the project description, details aren’t so clear. So we’ll write down concrete questions we would like to ask them. All our team posts will be published with the teampost tag, immediately available through https://martellsmartcities.blogspot.com/search/label/teampost We created a repository for the project but depending on how we organize with the alberta team we might create a...
Leer más

Plan Week 6

Imagen
This week we plan to continue developing our back-end side of the project. Mostly though, we'll be centered on figuring out how to use the Steps API previously developed by the Alberta team so that we add there additional info and media for important landmarks. The thing is, right now the Steps project is structured around "sidewalks", routes. We're not yet sure how we'll add landmarks, perhaps as routes that start and end at the same coordinates? The documentation for Steps is not very clear for where we can add this information. Hopefully we'll figure out a way, or a workaround, soon. image obtained from https://searchengineland.com/founder-openstreetmap-good-better-google-maps-already-192089
Leer más