Lab46 Wiki

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
======dll0 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.

=====dll0 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).

^  20171017  ^  20171018  ^  20171019  ^  20171020  ^  20171021  ^  20171022  ^  20171023  ^  20171024  ^  20171025  ^  20171026  ^  20171027  ^  20171028  ^  20171029  ^  20171030  ^  20171031  |
|  0  |  1  |  2  |  3  |  4  |  5  |  6  |  7  |  8  |  9  |  10  |  11  |  12  |  13  |  14  |
^  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 = dll0 Individual Progress
size = 600x400
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,123,76,1,0,0,0,1,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,121,21,15,76,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,313,5,1,0,0,0,0,0
0,0,0,0,0,55,167,152,147,3,0,0,0,0,0
0,0,0,0,0,0,0,0,89,74,9,0,0,1,0
0,0,0,0,0,0,0,0,36,68,30,22,0,0,0
0,0,0,0,45,18,69,123,0,0,0,0,0,0,1
0,0,0,0,0,0,0,148,148,0,0,0,0,0,0
0,0,0,0,0,0,0,0,34,16,0,0,0,0,1
0,0,0,77,21,91,26,163,117,1,0,0,0,0,0
0,0,0,0,0,0,0,62,1,30,24,2,0,0,0
9,54,39,0,0,0,0,3,1,0,0,0,0,0,1
0,0,0,0,0,0,58,95,192,0,0,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 (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 = dll0 Individual Completion Progress
size = 600x400
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,72,142,142,142,142,142,142,142,142,142,142,142,142,142
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
0,0,0,0,0,0,0,77,111,126,150,150,150,150,150
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
0,0,0,0,0,0,0,108,142,142,142,142,142,142,142
0,0,0,0,0,23,49,72,110,110,110,110,110,110,110
0,0,0,0,0,0,0,0,101,101,101,101,101,136,136
0,0,0,0,0,0,0,0,24,25,26,28,28,21,21
0,0,0,0,23,35,114,129,129,129,129,129,129,129,0
0,0,0,0,0,0,0,81,142,142,142,142,142,142,142
0,0,0,0,0,0,0,0,142,142,142,142,142,142,142
0,0,0,51,53,76,60,0,142,142,142,142,142,142,0
0,0,0,0,0,0,0,109,109,130,141,142,142,142,142
21,72,142,142,142,142,142,142,142,142,142,142,142,142,142
0,0,0,0,0,0,21,92,129,129,129,129,129,129,129
</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 = dll0 Class and Quantity Progress 
size = 600x400
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,123,76,1,0,0,0,1,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,121,21,15,76,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,313,5,1,0,0,0,0,0
0,0,0,0,0,55,167,152,147,3,0,0,0,0,0
0,0,0,0,0,0,0,0,89,74,9,0,0,1,0
0,0,0,0,0,0,0,0,36,68,30,22,0,0,0
0,0,0,0,45,18,69,123,0,0,0,0,0,0,1
0,0,0,0,0,0,0,148,148,0,0,0,0,0,0
0,0,0,0,0,0,0,0,34,16,0,0,0,0,1
0,0,0,77,21,91,26,163,117,1,0,0,0,0,0
0,0,0,0,0,0,0,62,1,30,24,2,0,0,0
9,54,39,0,0,0,0,3,1,0,0,0,0,0,1
0,0,0,0,0,0,58,95,192,0,0,0,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 = dll0 Class Progress 
size = 600x400
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,10,10,10,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,0
0,0,0,0,0,0,0,10,10,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,10,10,10,0,0,0,0,0
0,0,0,0,0,10,10,10,10,10,0,0,0,0,0
0,0,0,0,0,0,0,0,10,10,10,0,0,10,0
0,0,0,0,0,0,0,0,10,10,10,10,0,0,0
0,0,0,0,10,10,10,10,0,0,0,0,0,0,10
0,0,0,0,0,0,0,10,10,0,0,0,0,0,0
0,0,0,0,0,0,0,0,10,10,0,0,0,0,10
0,0,0,10,10,10,10,10,10,10,0,0,0,0,0
0,0,0,0,0,0,0,10,10,10,10,10,0,0,0
10,10,10,0,0,0,0,10,10,0,0,0,0,0,10
0,0,0,0,0,0,10,10,10,0,0,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 performing build activities on the project, and counted up to one time per user per day.

=====Project Lifecycle Stats (Individual)=====

<charter>
title = dll0 Individual Project Duration
size = 600x400
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 = 

2672
0
4074
0
2102
4680
8583
4604
4591
2305
9421
9078
5252
3330
3647
</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 = dll0 Lifecycle Progress
size = 600x400
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
30,0,20,10,10,10,20,30,20,0,0,0,0,0,0
0,0,0,0,0,0,0,100,30,0,0,0,20,0,0
0,0,20,0,0,0,0,10,70,0,10,20,20,0,10
</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: Wed Nov  1 06:58:18 EDT 2017
Lab46 Wiki

User Tools

Site Tools

Page Tools
