User Tools

Site Tools


Sidebar

projects

ntr0 (due 20220119)
pct1 (bonus; due 20220119)
wcp1 (due 20220119)
fwf0 (due 20220126)
pct2 (due 20220126)
wcp2 (due 20220126)
pct3 (bonus; due 20220202)
sof0 (due 20220202)
wcp3 (due 20220202)
dow0 (due 20220209)
pct4 (due 20220209)
wcp4 (due 20220209)
cbf0 (due 20220216)
gfo0 (due 20220216)
pct5 (bonus; due 20220216)
wcp5 (due 20220216)
bwp1 (bonus; due 20220302)
pct6 (due 20220302)
wcp6 (due 20220302)
cnv0 (due 20220309)
pct7 (bonus; due 20220309)
wcp7 (due 20220309)
cnv1 (due 20220316)
pct8 (due 20220316)
wcp8 (due 20220316)
cos0 (due 20220323)
gfo1 (due 20220323)
pct9 (bonus; due 20220323)
wcp9 (due 20220323)
bwp2 (bonus; due 20220406)
pctA (due 20220406)
sam0 (due 20220406)
wcpA (due 20220406)
oop0 (due 20220413)
pctB (bonus; due 20220413)
wcpB (due 20220413)
oop1 (due 20220420)
pctC (due 20220420)
wcpC (due 20220420)
oop2 (due 20220427)
pctD (bonus; due 20220427)
wcpD (bonus; due 20220427)
gfo2 (due 20220504)
pctE (bonus; due 20220504)
wcpE (bonus; due 20220504)
EoCE (due 20220512)
haas:spring2022:cprog:projects:pnc1:metrics

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

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

20171016 20171017 20171018 20171019 20171020 20171021 20171022 20171023 20171024 20171025 20171026 20171027 20171028
0 1 2 3 4 5 6 7 8 9 10 11 12 (TODAY)
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 = pnc1 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,0,0,0,174,0,0,0 0,0,0,0,0,0,0,0,0,0,0,0,0 0,0,17,0,0,0,11,7,18,0,0,0,0 0,0,0,0,0,0,0,0,49,81,0,0,0 0,0,0,0,0,0,0,0,5,5,0,0,0 0,0,40,0,0,0,0,70,25,6,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 = pnc1 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,4,4,4,4 0,0,0,0,0,0,0,0,6,1,1,1,1 0,0,9,9,9,9,24,23,23,23,23,23,23 0,0,0,0,0,0,0,0,1,5,5,5,5 0,0,0,0,0,0,0,0,0,0,0,0,0 0,0,0,0,0,0,6,6,6,5,5,5,5 </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 = pnc1 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,0,0,0,174,0,0,0 0,0,0,0,0,0,0,0,0,0,0,0,0 0,0,17,0,0,0,11,7,18,0,0,0,0 0,0,0,0,0,0,0,0,49,81,0,0,0 0,0,0,0,0,0,0,0,5,5,0,0,0 0,0,40,0,0,0,0,70,25,6,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 = pnc1 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,0,0,0,10,0,0,0 0,0,0,0,0,0,0,0,0,0,0,0,0 0,0,10,0,0,0,10,10,10,0,0,0,0 0,0,0,0,0,0,0,0,10,10,0,0,0 0,0,0,0,0,0,0,0,10,10,0,0,0 0,0,10,0,0,0,0,10,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 = pnc1 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 =

521 11786 7226 3397 1502 10124 </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 = pnc1 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 =

10,0,20,0,0,0,0,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,0,0,0 0,0,10,0,0,0,10,30,10,40,0,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: Sat Oct 28 02:24:03 EDT 2017

haas/spring2022/cprog/projects/pnc1/metrics.txt · Last modified: 2017/10/28 06:24 by 127.0.0.1