Metrics

Since the team is following Agile practices, the Mobile Trail Mapping project's success will depend in part on the feedback the team receives from various metrics kept over the course of the project. The team can generally divide these metrics into two categories: code-based metrics and personnel-based metrics.

Code-based metrics

This set of metrics deals with the actual code placed in the GitHub repositories, as well as edits to the wiki hosted there. The team aims to keep individual people out of these metrics as much as possible, instead focusing on measures of code quality.

Files per language

Repo	XML	C/C++ Header	Java	Python	Javascript	Objective C	HTML	XSD	Ruby	Bourne Shell	CSS	Total
Android	14	0	14	0	0	0	0	0	0	10	0	38
Architecture	1	0	3	3	5	0	2	3	1	11	4	33
Architecture.wiki	0	0	0	0	0	0	0	0	0	10	0	10
Server	0	0	0	0	0	0	0	1	12	10	0	23
iPhone	1	42	0	0	0	20	0	0	0	10	0	73
Total	16	42	17	3	5	20	2	4	13	51	4	177

Personnel-based metrics

This set of metrics has to do with the contributions of individual team members, both in terms of the working codebase and the documentation contributed (including that on the wiki and the entries in the shared team blog, which functions as an engineering journal).

Source control metrics

One of the primary ways the team communicates with the LCTA and Rose-Hulman faculty is via the GitHub system. This system makes it possible for the team to share code, documentation, and tracked issues easily. In addition, the Git system underlying GitHub allows for very granular tracking of the actions developers have taken over the history of the project. We present a few of these metrics here. (Note that some of these metrics reflect some duplication of commit history due to the recent repository split.)

Commits per person

Repo	Pete Brousalis	Tim Ekl	David Pick	Eric Stokes
iPhone	15	13	49	117
Architecture	8	12	49	117
Architecture.wiki	15	84	0	0
Android	2	5	32	122
Server	2	11	59	117
Total (%)	42 (5%)	125 (15%)	189 (23%)	473 (57%)