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:dll1:metrics

dll1 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.

dll1 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).

20171024 20171025 20171026 20171027 20171028 20171029 20171030 20171031 20171101 20171102 20171103 20171104
0 1 2 3 4 5 6 7 8 9 (TODAY) 10 11
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 = dll1 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 =

89,87,9,2,3,0,0,1,0,1,0,0 0,0,0,0,0,0,0,0,0,0,0,0 0,0,0,3,0,0,0,0,143,0,0,0 0,0,0,0,0,0,0,0,0,0,0,0 0,0,0,0,0,0,248,48,271,0,0,0 0,0,6,68,25,52,130,115,86,2,0,0 0,0,0,0,0,0,34,70,104,0,0,0 0,1,0,0,0,0,20,99,74,31,0,0 0,0,0,0,0,0,0,64,8,18,0,0 0,0,0,0,0,0,21,50,75,0,0,0 0,0,0,0,4,2,6,18,9,0,0,0 0,0,0,38,8,2,114,192,6,0,0,0 0,0,0,0,0,8,46,64,0,0,0,0 0,99,49,61,33,0,0,1,0,0,0,0 0,0,4,0,0,15,0,36,159,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 (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.

Progress toward Completion (Individual)

<charter> title = dll1 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 =

135,162,153,162,162,162,162,162,162,162 0,0,0,0,0,0,0,0,0,0 0,0,0,0,0,0,0,0,93,93 0,0,0,0,0,0,0,0,0,0 0,0,0,0,0,0,84,110,144,144 0,0,0,38,38,48,69,108,153,153 0,0,0,0,0,0,0,0,0,0 0,0,0,0,0,0,36,95,116,129 0,0,0,0,0,0,0,93,110,132 0,0,0,0,0,0,0,62,153,153 0,0,0,0,75,82,93,162,162,162 0,0,0,0,0,0,96,158,0,0 0,0,0,0,0,30,105,162,162,162 0,63,139,162,195,195,195,195,195,195 0,0,0,0,0,0,0,69,153,153 </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.

Progress By Day and Quantity (Together)

<charter> title = dll1 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 =

89,87,9,2,3,0,0,1,0,1,0,0 0,0,0,0,0,0,0,0,0,0,0,0 0,0,0,3,0,0,0,0,143,0,0,0 0,0,0,0,0,0,0,0,0,0,0,0 0,0,0,0,0,0,248,48,271,0,0,0 0,0,6,68,25,52,130,115,86,2,0,0 0,0,0,0,0,0,34,70,104,0,0,0 0,1,0,0,0,0,20,99,74,31,0,0 0,0,0,0,0,0,0,64,8,18,0,0 0,0,0,0,0,0,21,50,75,0,0,0 0,0,0,0,4,2,6,18,9,0,0,0 0,0,0,38,8,2,114,192,6,0,0,0 0,0,0,0,0,8,46,64,0,0,0,0 0,99,49,61,33,0,0,1,0,0,0,0 0,0,4,0,0,15,0,36,159,0,0,0 </charter>

Each bar represents the total class activity on the project for the given day. The higher and more colorful the bar, 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.

Class Member Activity Per Day

<charter> title = dll1 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 =

10,10,10,10,10,0,0,10,0,10,0,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,0,0,0,0 0,0,0,0,0,0,10,10,10,0,0,0 0,0,10,10,10,10,10,10,10,10,0,0 0,0,0,0,0,0,10,10,10,0,0,0 0,10,0,0,0,0,10,10,10,10,0,0 0,0,0,0,0,0,0,10,10,10,0,0 0,0,0,0,0,0,10,10,10,0,0,0 0,0,0,0,10,10,10,10,10,0,0,0 0,0,0,10,10,10,10,10,10,0,0,0 0,0,0,0,0,10,10,10,0,0,0,0 0,10,10,10,10,0,0,10,0,0,0,0 0,0,10,0,0,10,0,10,10,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 performing build activities on the project, and counted up to one time per user per day.

Project Lifecycle Stats (Individual)

<charter> title = dll1 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 =

3434 0 7699 0 6196 9509 3476 3593 2904 3372 5493 6578 3644 4801 9234 </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 = dll1 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 20,10,20,20,20,10,30,10,0,0,0,0 0,0,0,0,0,0,0,0,0,0,0,0 0,10,0,0,10,0,0,10,80,30,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: Thu Nov 2 10:14:01 EDT 2017

haas/fall2018/data/projects/dll1/metrics.txt · Last modified: 2017/11/02 14:14 by 127.0.0.1