8000 GitHub - vifraa/se-project
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

vifraa/se-project

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

SE-project

Project Contributors:
Gustav Darhult: GustavDarhult
Viktor Franzen: Vifraa, ViktorFranzen
Tobias Lindroth: rothen98, TobiasLindroth
Spondon Siddiqui: SpondonSiddiqui
Alexander Solberg : Solen, AlexSolberg
Oscar Thornander: OscarThornander
Viktor Torkelsson: viktortorkelsson

Folder Structure:

In the documents folder we have all the documents which are supporting for the product.
Team reflections are in the weekly reflections folder
Individual reflections for each week are in the personal_reflection folder and then in each users respective folder
Other live documents can also be found in this folder. Such as BMC, project ideas, and mockups

In the code folder there are alternatives to either go into the backend service source (split-backend) or our frontend application (split)

In split-backend folder:
The tests can be found in src-> test->java->gyarados->splitbackend
The general code for the backend can be found in src->main->java->gyarados->splitbackend

In split folder:
To find the general code go into main->java->com->chalmers->gyarados->split The xml views can be found in main->res->layout All additional layout components such as images, items, etc can be found in main->res

Git Info:
The gitinspector info can be found under documents->gitinspectorsplit.html:
Alternatively the gitinspector info can be opened from the PNG version of gitinspector
From the first table we can see all the users inputs and deletions over the course of the entire project
The second table shows all the code which has survived and currently resides in our project

Explanation:
The reason that there is a massive difference in the number of lines of code is because we have done pair programming which can be seen from our social contract and weekly reflections.
Usually within the group we worked on one computer so then one user has almost all the lines of code on gitinspector. Towards the end of the project we tried to even this our a bit by programming on the other persons computer
When we apply the groups we can see that the lines of code start to become fairly similar across all teams within our group

Trello Link:
https://trello.com/invite/b/yU65Nje6/85f1cf26f7c61b43bf7c097d90ceb8d9/sep-gyarados

About

No description, website, or topics provided.

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Contributors 7

0