User Tools

Site Tools


Sidebar

projects

dsi0 (20180822)
wcp1 (20180822)
ael0 [faq] (20180829)
wcp2 (20180829)
sln0 [faq] (20180905)
wcp3 (20180905)
sln1 [faq] [metrics] (20180912)
wcp4 (20180912)
sll0 [faq] [metrics] (20180919)
wcp5 (20180919)
sll1 [faq] [metrics] (20180926)
wcp6 (20180926)
sll2 [faq] [metrics] (20181003)
wcp7 (20181003)
sll3 [faq] [metrics] (20181017)
sll4 [faq] [metrics] (20181017)
wcp8 (20181017)
dln0 [faq] [metrics] (20181024)
dll0 [faq] [metrics] (20181024)
wcp9 (20181024)
dll1 [faq] [metrics] (20181031)
wcpA (20181031)
dll2 [faq] [metrics] (20181107)
dls0 [faq] [metrics] (20181107)
wcpB (20181107)
dlq0 [faq] [metrics] (20181115)
wcpC (20181115)
dlt0 [faq] [metrics] (20181128)
EoCE (20181213-172959)
haas:fall2018:data:projects:eoce0:metrics

eoce0 Project Class Status Summary

Provided as a means of better understanding trends, the following charts and tables will visualize various indirect data points that, while not indicative of success (or deferrance thereof), may well correlate with such. Plus, being able to see trends on a large scale can aid in better decision making and planning.

eoce0 lifespan

Projects are typically released on Tuesday, and are due by the end of the following Wednesday. This allows for at least nine days to work on the project without penalty.

Following the due date, there is a period of three days (the late, or past due period), where 25% is docked each day, after which the project neither has nor can earn any value.

Here is a table with the pertinent dates for this project (the day number is the one that is also found on the x-axis of the graphs).

20151201 20151202 20151203 20151204 20151205 20151206 20151207 20151208 20151209 20151210 20151211 20151212 20151213 20151214 20151215 20151216 20151217 20151218 20151219 20151220
0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19
start date due date late day 1 (25% off) late day 2 (50% off) late day 3 (75% off)

Typically, any and all activity taking place to the left of the due date is preferable; it tends to indicate less procrastination and has the likelihood of involving better time management.

Progress By Day (Individual)

<charter> title = eoce0 Individual Progress size = 600×400 align = center type = bar XAxisName = Day YAxisName = Activity Level shadow = on titleColor = #efefef scaleColor = #efefef shadowColor = #000 bggradient = #333@50 graphGradient = #666@50 fontLegend = VeraMono.ttf@8 graphLabels =

0,0,0,0,0,0,2,1,0,0,0,0,0,22,0,0,0,0,0,0 4,5,1,16,5,1,7,1,1,4,0,0,0,0,0,0,2,0,0,0 0,0,0,0,0,0,0,0,0,2,0,0,0,0,0,7,37,0,0,0 0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 0,0,1,0,0,0,0,35,15,21,23,0,4,0,2,0,0,0,0,0 8,23,21,16,0,0,32,101,40,63,20,0,0,8,8,40,0,0,0,0 0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,10,0,0,0,0 1,0,1,0,0,0,0,16,0,1,10,12,24,5,0,0,10,0,0,0 0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 5,8,15,1,0,4,54,5,30,27,0,0,0,0,15,0,0,0,0,0 0,0,0,0,0,0,0,0,0,0,0,9,0,0,0,0,1,0,0,0 0,0,0,0,0,0,0,0,7,0,0,0,0,0,7,27,1,0,0,0 0,0,0,0,0,0,0,0,0,0,0,0,0,0,6,0,0,0,0,0 0,0,0,0,0,0,0,0,0,0,0,0,0,1,25,13,0,0,0,0 0,0,0,0,0,0,0,0,0,0,0,0,0,2,0,17,0,0,0,0 </charter>

Each line represents an individual class member's progress on the project. The more active they are, the higher the bar will rise.

The busier the day looks, the more active a development day it is by more of the class. And the more left shifted the activity, the less procrastination (lefter is betterer).

Although not a guaranteed measure of progress or of success, it is intended as a guage to evaluate how the class as a whole is doing.

NOTE: As of sll2, activity is measured in units of partial project builds. Prior to sll2, only full project builds were counted.

Progress toward Completion (Individual)

<charter> title = eoce0 Individual Completion Progress size = 600×400 align = center type = line XAxisName = Day YAxisName = Correct Unit Test Results shadow = on titleColor = #efefef scaleColor = #efefef shadowColor = #000 bggradient = #333@50 graphGradient = #666@50 fontLegend = VeraMono.ttf@8 graphLabels =

0,0,0,0,0,0,0,0,0,0,0,0,0,11,11,11,11,11,11,11 0,0,2,5,5,5,5,5,5,5,5,5,5,5,5,5,5,5,5,5 0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,60,60,60,60 0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 0,0,1,1,1,1,1,44,52,53,52,52,52,52,52,52,52,52,52,52 0,35,35,36,36,36,36,56,58,63,66,66,66,68,71,80,80,80,80,80 0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,59,68,68,68,68 0,0,2,2,2,2,2,18,18,18,24,45,67,67,67,67,71,71,71,71 0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 0,35,35,35,35,35,35,36,36,36,36,36,36,36,36,36,36,36,36,36 0,0,0,0,0,0,0,0,0,0,0,0,0,0,11,11,11,11,11,11 0,0,0,0,0,0,0,0,45,45,45,45,45,45,45,0,0,0,0,0 0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 0,0,0,0,0,0,0,0,0,0,0,0,0,0,14,18,18,18,18,18 0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,49,49,49,49,49 </charter>

Each line represents the progress of a class member toward full implementation (as defined by the unit tests performed during a 'make check'). The higher the line, the more unit tests are being passed.

The busier the day looks, the more active a development day it is by more of the class. And the more left shifted upward activity starts, the better (as it shows work is well underway).

Although not a guaranteed measure of progress or of success, it is intended as a guage to evaluate how the class as a whole is doing.

NOTE: These data points were not being sampled prior to sll2.

Progress By Day and Quantity (Together)

<charter> title = eoce0 Class and Quantity Progress size = 600×400 align = center type = barStacked XAxisName = Day YAxisName = Activity Level shadow = on titleColor = #efefef scaleColor = #efefef shadowColor = #000 bggradient = #333@50 graphGradient = #666@50 fontLegend = VeraMono.ttf@8 graphLabels =

0,0,0,0,0,0,2,1,0,0,0,0,0,22,0,0,0,0,0,0 4,5,1,16,5,1,7,1,1,4,0,0,0,0,0,0,2,0,0,0 0,0,0,0,0,0,0,0,0,2,0,0,0,0,0,7,37,0,0,0 0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 0,0,1,0,0,0,0,35,15,21,23,0,4,0,2,0,0,0,0,0 8,23,21,16,0,0,32,101,40,63,20,0,0,8,8,40,0,0,0,0 0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,10,0,0,0,0 1,0,1,0,0,0,0,16,0,1,10,12,24,5,0,0,10,0,0,0 0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 5,8,15,1,0,4,54,5,30,27,0,0,0,0,15,0,0,0,0,0 0,0,0,0,0,0,0,0,0,0,0,9,0,0,0,0,1,0,0,0 0,0,0,0,0,0,0,0,7,0,0,0,0,0,7,27,1,0,0,0 0,0,0,0,0,0,0,0,0,0,0,0,0,0,6,0,0,0,0,0 0,0,0,0,0,0,0,0,0,0,0,0,0,1,25,13,0,0,0,0 0,0,0,0,0,0,0,0,0,0,0,0,0,2,0,17,0,0,0,0 </charter>

Each line represents the total class activity on the project for the given day. The higher and more colorful the line, the more activity by more people took place (upperer as well as lefterer is betterer).

Although not a guaranteed measure of progress or of success, it is intended as a guage to evaluate how the class as a whole is doing.

NOTE: Activity is measured in units of partial project builds. Prior to sll2, activity was measured in terms of full project builds.

Class Member Activity Per Day

<charter> title = eoce0 Class Progress size = 600×400 align = center type = barStacked XAxisName = Day YAxisName = Activity Level shadow = on titleColor = #efefef scaleColor = #efefef shadowColor = #000 bggradient = #333@50 graphGradient = #666@50 fontLegend = VeraMono.ttf@8 graphLabels =

0,0,0,0,0,0,10,10,0,0,0,0,0,10,0,0,0,0,0,0 10,10,10,10,10,10,10,10,10,10,0,0,0,0,0,0,10,0,0,0 0,0,0,0,0,0,0,0,0,10,0,0,0,0,0,10,10,0,0,0 0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 0,0,10,0,0,0,0,10,10,10,10,0,10,0,10,0,0,0,0,0 10,10,10,10,0,0,10,10,10,10,10,0,0,10,10,10,0,0,0,0 0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,10,0,0,0,0 10,0,10,0,0,0,0,10,0,10,10,10,10,10,0,0,10,0,0,0 0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 10,10,10,10,0,10,10,10,10,10,0,0,0,0,10,0,0,0,0,0 0,0,0,0,0,0,0,0,0,0,0,10,0,0,0,0,10,0,0,0 0,0,0,0,0,0,0,0,10,0,0,0,0,0,10,10,10,0,0,0 0,0,0,0,0,0,0,0,0,0,0,0,0,0,10,0,0,0,0,0 0,0,0,0,0,0,0,0,0,0,0,0,0,10,10,10,0,0,0,0 0,0,0,0,0,0,0,0,0,0,0,0,0,10,0,10,0,0,0,0 </charter>

Each day shows the quantity of project builds per day of the project's lifespan.

Although not a guaranteed measure of progress or of success, it is intended as a guage to evaluate how the class as a whole is doing. As such, the lefterer and upperer the betterer.

NOTE: Activity is measured in units of a user building, and counted once per user per day.

Project Lifecycle Stats (Individual)

<charter> title = eoce0 Individual Project Duration size = 600×400 align = center type = bar XAxisName = Person YAxisName = Minutes shadow = on titleColor = #efefef scaleColor = #efefef shadowColor = #000 bggradient = #333@50 graphGradient = #666@50 fontLegend = VeraMono.ttf@8 graphLabels =

20200 23160 13230 0 16731 21800 21810 927 22677 0 23035 12003 23155 23043 21691 11386 </charter>

Each bar represents the number of minutes taken from initial upgrade to project through project submission (final submission).

Although not a guaranteed measure of progress or of success, it is intended as a guage to evaluate how the class as a whole is doing.

Obtains/Upgrades/Updates/Submits By Day

<charter> title = eoce0 Lifecycle Progress size = 600×400 align = center type = barStacked legendEntries = obtain, upgrade, update, submit XAxisName = Day YAxisName = Activity shadow = on titleColor = #efefef scaleColor = #efefef shadowColor = #000 bggradient = #333@50 graphGradient = #666@50 fontLegend = VeraMono.ttf@8 graphLabels =

0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 150,10,10,0,0,0,0,20,10,0,10,0,0,0,0,10,0,0,0,0 60,0,60,40,0,0,10,110,40,10,0,0,0,20,20,60,30,10,0,0 30,0,0,0,0,0,20,0,10,0,0,0,0,0,0,50,120,10,0,0 </charter>

Each day shows the quantity of project obtains, upgrades, revision updates, and submissions per day of the project's lifespan.

Although not a guaranteed measure of progress or of success, it is intended as a guage to evaluate how the class as a whole is doing. As such, the lefterer and upperer the betterer.

NOTE: Activity is measured in units of specific actions taken (upgrading, submitting, etc.), and counted once per user per day.

Status Page last updated: Mon Dec 21 02:36:15 EST 2015

haas/fall2018/data/projects/eoce0/metrics.txt · Last modified: 2015/12/21 07:34 by 127.0.0.1