CS 4971

Monday, April 28th, 2014

• Today will be a regular group work day
  • My course conclusion will be during the final exam period next week
• We are half-way through iteration 14
  • Leads, your first weekly reports are due tomorrow by noon
  • You will still need to complete the TPS reports next week!
• Don't forget to report your hours! This is factoring into your course grade (that you submit them, not how many hours you report)
• Pegasus is up, but Jenkins keeps bringing it down, hence why Jenkins is not back up
  • I found why Jenkins is bringing down pegasus, and it's not good...
• You must still be able to run all your unit tests successfully, even if not through Jenkins...

What you have left to do

• Complete your tutorial (due by 9 a.m. on Tuesday, May 6th)
  • Did you reserve your topic? Be sure to check both the Collab wiki and the existing mediawiki for already taken topics
• Complete the required things for this iteration
  • Final touches on: user manual, installation instructions, programming reference
  • Tweaks to the system based on customer feedback
• Final hand-off of the system to the customer
• Prep your final presentation
• All Redmine tasks should be completed!
• Completion of TWO surveys; you will receive notices about them this week
• Submission of the materials to me
  • This will include creating screen shots and the one-slide version
  • This can be turned in by the end of the day on Tue, May 6

Final Exam Period

• It's from 9 a.m. to noon on Tuesday, May 6th
• Everything is due by 9 a.m. on that day (when the period starts)
• Each group will give their presentation
• I'll conclude with a course wrap-up
• Like any final, everybody is required to attend

Monday, April 21st, 2014

• Evaluations for iteration 11 and 12 have been completed -- please check them!
  • I could not find some of the required parts...
• We are almost at the end of iteration 13
  • Leads, your TPS reports are due tomorrow by noon
• Montanova had a phase change (and now has an end-of-phase survey due) two weeks ago; the other groups did not
• Don't forget to report your hours! This is factoring into your course grade (that you submit them, not how many hours you report)
• Pegasus is up, but Jenkins keeps bringing it down, hence why Jenkins is not back up
  • I found why Jenkins is bringing down pegasus, and it's not good...
• You must still be able to run all your unit tests successfully, even if not through Jenkins...

Deliverables

• As discussed in the deliverables slide set, there are several artifacts to be completed
• Things that are done, presumably:
  • Transition plan (and all the various sub-parts)
  • Requirements document
• Things to complete:
  • User Manual
  • Installation Instructions
  • Programming Reference
  • STS Technical Report
  • Final Presentation
  • Tutorials
• Plus, some non-documentation:
  • Wrting unit tests
  • Doing other tests

Artifacts to be completed

• User Manual: start in iteration 12, edit in iteration 13, complete in interation 14
• Installation Instructions: start in iteration 13, complete in interation 14
• Programming Reference: start in iteration 13, complete in interation 14
• STS Technical Report: up to your group
  • I just need it 2 weeks prior to the due date for STS
• Final Presentation: iteration 14
  • They are during the final exam time (Tue, May 6, from 9 a.m. to noon)
• Tutorials: iteration 14, but you may want to reserve them now (create/edit a mediawiki page with your topic, NOT a Collab wiki page)

Iteration 13 deliverables

• A completed version of the user manual
  • This should be a reasonably polished PDF
  • I should be able to find it from your main Redmine wiki page
• Installation instructions, first (and likely last) draft
• Programming reference, first draft
• The remainder of your unit tests
• Ensure that your customer is actively using the system
  • And handle any feedback / tweaks / updates / bug fixes from him/her
  • If this is not the case, you must let me know!!!

Iteration 14

• Final hand-off of the system to the customer at the end of the iteration (details about how to do this will be forthcoming)
• Submission of all the materials to me (details forthcoming, but mentioned in the deliverables slide set)
• Polished user manual and installation instructions
• Tweaks to the system based on customer feedback
• Completion of TWO surveys
• All Redmine tasks should be marked as completed!
• Demonstration of the system to me (separate meetings)
• Artifacts to be completed this iteration:
  • Completed programming reference
  • Tutorial -- did you reserve your topic? Be sure to check both Collab and the existing mediawiki for already taken topics
  • Final presentation (during the finals period: Tuesday, May 6, from 9-noon)

Monday, April 14th, 2014

• Evaluations for iteration 11 and 12 will be out "soon"
• We are in the middle of iteration 13
  • Leads, your first weekly reports are due tomorrow by noon
• Montanova had a phase change (and now has an end-of-phase survey due); the other groups will not
• Don't forget to report your hours! This is factoring into your course grade (that you submit them, not how many hours you report)
• Pegasus is up, but Jenkins keeps bringing it down, hence why Jenkins is not back up
  • Also remember that Jenkins must always build during the transition period; you may not leave a commit/push that breaks it (if you are actively working on it, that's fine)
  • Due to it (and the server) being down lately, I am not going to be checking until this iteration is done...

Deliverables

• As discussed in the deliverables slide set, there are several artifacts to be completed
• Things that are done, presumably:
  • Transition plan (and all the various sub-parts)
  • Requirements document
• Things to complete:
  • User Manual
  • Installation Instructions
  • Programming Reference
  • STS Technical Report
  • Final Presentation
  • Tutorials
• Plus, some non-documentation:
  • Wrting unit tests
  • Doing other tests

Artifacts to be completed

• User Manual: start in iteration 12, edit in iteration 13, complete in interation 14
• Installation Instructions: start in iteration 13, complete in interation 14
• Programming Reference: start in iteration 13, complete in interation 14
• STS Technical Report: up to your group
  • I just need it 2 weeks prior to the due date for STS
• Final Presentation: iteration 14
  • They are during the final exam time (Tue, May 6, from 9 a.m. to noon)
• Tutorials: iteration 14, but you may want to reserve them now (create/edit a mediawiki page with your topic, NOT a Collab wiki page)

Iteration 13 deliverables

• A completed version of the user manual
  • This can be as a PDF, or as a Redmine wiki page at this point
  • When finished, it will need to be a (relatively) polished PDF
  • I should be able to find it from your main Redmine wiki page
• Installation instructions, first (and likely last) draft
• Programming reference, first draft
• The remainder of your unit tests
• Ensure that your customer is actively using the system
  • And handle any feedback / tweaks / updates / bug fixes from him/her
  • If this is not the case, you must let me know!!!

Wednesday, April 9th, 2014

• Evaluations for iteration 11 and 12 will be out "soon"
• We are in the first day of iteration 13
  • Leads, your first weekly reports were due yesterday tomorrow by noon
• Montanova is having a phase/lead/secretary change (and an end-of-phase survey); the other groups will not
• Don't forget to report your hours! This is factoring into your course grade (that you submit them, not how many hours you report)
• Pegasus is up, but Jenkins keeps bringing it down, hence why Jenkins is not back up
  • Also remember that Jenkins must always build during the transition period; you may not leave a commit/push that breaks it (if you are actively working on it, that's fine)
  • Due to it (and the server) being down lately, I am not going to be checking until this iteration is done...

Deliverables

• As discussed in the deliverables slide set, there are several artifacts to be completed
• Things that are done, presumably:
  • Transition plan (and all the various sub-parts)
  • Requirements document
• Things to complete:
  • User Manual
  • Installation Instructions
  • Programming Reference
  • STS Technical Report
  • Final Presentation
  • Tutorials
• Plus, some non-documentation:
  • Wrting unit tests
  • Doing other tests

Artifacts to be completed

• User Manual: start in iteration 12, edit in iteration 13, complete in interation 14
• Installation Instructions: start in iteration 13, complete in interation 14
• Programming Reference: start in iteration 13, complete in interation 14
• STS Technical Report: up to your group
  • I just need it 2 weeks prior to the due date for STS
• Final Presentation: iteration 14
  • They are during the final exam time (Tue, May 6, from 9 a.m. to noon)
• Tutorials: iteration 14, but you may want to reserve them now (create/edit a mediawiki page with your topic, NOT a Collab wiki page)

Iteration 13 deliverables

• A completed version of the user manual
  • This can be as a PDF, or as a Redmine wiki page at this point
  • When finished, it will need to be a (relatively) polished PDF
  • I should be able to find it from your main Redmine wiki page
• Installation instructions, first (and likely last) draft
• Programming reference, first draft
• The remainder of your unit tests
• Ensure that your customer is actively using the system
  • And handle any feedback / tweaks / updates / bug fixes from him/her
  • If this is not the case, you must let me know!!!

Monday, April 7th, 2014

• Evaluations for iteration 11 will be out "soon"
• We are in the last day of iteration 12
  • Did you complete your end-of-phase survey last week?
  • Leads, your first weekly reports are due tomorrow by noon
• Montanova will have an end-of-survey to do after today; the other groups will not
• Don't forget to report your hours! This is factoring into your course grade (that you submit them, not how many hours you report)
• Jenkins is back up, as is pegasus
• Also remember that Jenkins must always build during the transition period; you may not leave a commit/push that breaks it (if you are actively working on it, that's fine)
  • Due to it (and the server) being down lately, I am not going to be checking until this iteration is done...

Deliverables

• As discussed in the deliverables slide set, there are several artifacts to be completed
• Things that are done, presumably:
  • Transition plan (and all the various sub-parts)
  • Requirements document
• Things to complete:
  • User Manual
  • Installation Instructions
  • Programming Reference
  • STS Technical Report
  • Final Presentation
  • Tutorials
• Plus, some non-documentation:
  • Wrting unit tests
  • Doing other tests

Artifacts to be completed

• User Manual: start in iteration 12, edit in iteration 13, complete in interation 14
• Installation Instructions: start in iteration 13, complete in interation 14
• Programming Reference: start in iteration 13, complete in interation 14
• STS Technical Report: up to your group
  • I just need it 2 weeks prior to the due date for STS
• Final Presentation: iteration 14
  • They are during the final exam time (Tue, May 6, from 9 a.m. to noon)
• Tutorials: iteration 14, but you may want to reserve them now (create/edit a mediawiki page with your topic, NOT a Collab wiki page)

Iteration 12 deliverables

• A first draft of the user manual
  • This can be as a PDF, or as a Redmine wiki page at this point
  • When finished, it will need to be a (relatively) polished PDF
  • I should be able to find it from your main Redmine wiki page
• The majority of your unit tests
  • This is the big workload for this iteration!
• Ensure that your customer is actively using the system
  • And handle any feedback / tweaks / updates / bug fixes from him/her
  • If this is not the case, you must let me know!!!

Monday, March 31st, 2014

• Evaluations for iteration 11 will be out "soon"
• We are one week into iteration 12
  • Did you complete your end-of-phase survey last week?
  • Leads, your first weekly reports are due tomorrow by noon
• Don't forget to report your hours! This is factoring into your course grade (that you submit them, not how many hours you report)
• Jenkins is down, but will be up "soon"
• Also remember that Jenkins must always build during the transition period; you may not leave a commit/push that breaks it (if you are actively working on it, that's fine)

Deliverables

• As discussed in the deliverables slide set, there are several artifacts to be completed
• Things that are done, presumably:
  • Transition plan (and all the various sub-parts)
  • Requirements document
• Things to complete:
  • User Manual
  • Installation Instructions
  • Programming Reference
  • STS Technical Report
  • Final Presentation
  • Tutorials
• Plus, some non-documentation:
  • Wrting unit tests
  • Doing other tests

Artifacts to be completed

• User Manual: start in iteration 12, edit in iteration 13, complete in interation 14
• Installation Instructions: start in iteration 13, complete in interation 14
• Programming Reference: start in iteration 13, complete in interation 14
• STS Technical Report: up to your group
  • I just need it 2 weeks prior to the due date for STS
• Final Presentation: iteration 14
  • They are during the final exam time (Tue, May 6, from 9 a.m. to noon)
• Tutorials: iteration 14, but you may want to reserve them now (create/edit a mediawiki page with your topic, NOT a Collab wiki page)

Iteration 12 deliverables

• A first draft of the user manual
• The majority of your unit tests
  • This is the big workload for this iteration!
• Ensure that your customer is actively using the system
  • And handle any feedback / tweaks / updates / bug fixes from him/her

Lecture ??: March 26th, 2014

• Evaluations: I'm all caught up!
  • Please check them! If your lead did not submit a TPS report, then I was unable to judge progress, and everybody in the group received a poor evaluation
  • For secretaries, having an entry of "no notes present in Redmine" is bad
• Today is the first day of iteration 12
  • New leads and new secretaries!
  • And an end-of-phase survey to complete
  • All development should have been completed
  • Leads, your TPS reports were due yesterday at noon
• Don't forget to report your hours! This is factoring into your course grade (that you submit them, not how many hours you report)
• Remember that pegasus will be taken down Friday and Saturday, as it will be used for the High School Programming Contest
• Also remember that Jenkins must always build during the transition period; you may not leave a commit/push that breaks it (if you are actively working on it, that's fine)

Deliverables

• As discussed in the deliverables slide set, there are several artifacts to be completed
• Things that are done, presumably:
  • Transition plan (and all the various sub-parts)
  • Requirements document
• Things to complete:
  • User Manual
  • Installation Instructions
  • Programming Reference
  • STS Technical Report
  • Final Presentation
  • Tutorials
• Plus, some non-documentation:
  • Wrting unit tests
  • Doing other tests

Artifacts to be completed

• User Manual: start in iteration 12, edit in iteration 13, complete in interation 14
• Installation Instructions: start in iteration 13, complete in interation 14
• Programming Reference: start in iteration 13, complete in interation 14
• STS Technical Report: up to your group
  • I just need it 2 weeks prior to the due date for STS
• Final Presentation: iteration 14
  • They are during the final exam time (Tue, May 6, from 9 a.m. to noon)
• Tutorials: iteration 14, but you may want to reserve them now (create/edit a mediawiki page with your topic, NOT a Collab wiki page)

Iteration 12 deliverables

• A first draft of the user manual
• The majority of your unit tests
  • This is the big workload for this iteration!
• Ensure that your customer is actively using the system
  • And handle any feedback / tweaks / updates / bug fixes from him/her

Lecture ??: March 24th, 2014

• Evaluations: I'm all caught up!
  • Please check them! If your lead did not submit a TPS report, then I was unable to judge progress, and everybody in the group received a poor evaluation
  • For secretaries, having an entry of "no notes present in Redmine" is bad
• Today is the last day of iteration 11
  • Leads, your TPS report is due tomorrow at noon
  • Remember that today is the deadline to complete development! (well, tomorrow at noon)
• Tomorrow starts iteration 12: there is a lead/secretary change, and end-of-phase evaluations to complete
• Don't forget to report your hours! This is factoring into your course grade (that you submit them, not how many hours you report)
• As mentioned on the first day, at some point we would run out of relevant topics to cover in lecture
  • We've reached that point, so now both Mondays and Wednesdays will be group meeting days

Deliverable for Iteration 11

• The unit tests from the last iteration
  • There was confusion (amid trips, snow days, and spring break) in getting them done fully correctly in the last iteration
  • You should have them already done, but not necessarily in the right "form"
  • Details on the next slide
• An updated requirements document (this should have been kept up-to-date)
• The full transition plan: this contains:
  • An updated deployment plan (iteration 7)
  • An updated master test plan (iteration 8)
  • A working Jenkins build for your unit tests (iteration 9)
  • A half dozen (or so) unit tests (iteration 10)
  • The updated requirements document (iteration 11)
• Some of these may require editing from the original
• This should be "packaged" into a single document
  • A single Redmine wiki page, with links to the various parts (which are presumably sub-pages), is fine

Unit Tests

• For iteration 10 (and will be checked for iteration 11) you should have a half-dozen or so unit tests written
  • These should be real unit tests that test real code
  • Have a variety: test a model, a controller, a view, etc.
• They should be scripted to run with the Jenkins build
• You should indicate to me how this is done so that I can find them
  • In the lead's TPS report is fine
  • But you need to tell me where to find the unit tests!

You should be aware of this!

Your ability to pass this course is contingent on the fact that, as of Tuesday, March 25th (tomorrow!) at noon, you have a fully working system deployed to the final deployemnt host.

• "Fully working system" means that you have implemented all the features in the requirements document, and they (more or less) work
  • There can be bugs, of course, at this point
  • Hence the need for an updated requirements document
  • And you need to speak to me if there are any major changes to that document
• "Final deployment host" is what is specified in your deployment plan; it is not pegasus!

 
As mentioned on day 1 of this semester, if these are not done, then you will fail this class and then likely not graduate.

Transition Phase

• It's 3 iterations (6 weeks) long
• During the transition phase, Jenkins must always build successfully
  • If your commit breaks something, then you should immediately fix it
  • This means that you need to run the test after you do a commit (which is the point of this type of testing, anyway)
  • I will be regularly checking that the builds work...
• There will be iteration deliverables (the various artifacts in the deliverables slide set
  • I will detail these as we go through the transition phase
  • The only one I leave to you to schedule is the final STS technical report
    • I need that two weeks before it is due to your STS professor (so take the earliest deadline of the group)
    • 1 week for me to read it, and 1 week for you to make edits to the document after I comment on it
• 6-person groups will have one lead for the entire transition period
  • The 7 person group will change leads one iteration into the transition phase

Lecture ??: March 16th, 2014

• Evaluations: I'm all caught up!
  • Please check them! If your lead did not submit a TPS report, then I was unable to judge progress, and everybody in the group received a poor evaluation
  • For secretaries, having an entry of "no notes present in Redmine" is bad
• We are half-way into iteration 11
  • Leads, your first weekly report is due tomorrow at noon
• Remember that next Monday, March 24th, is the deadline to complete development!
• Don't forget to report your hours! This is factoring into your course grade (that you submit them, not how many hours you report)
• As mentioned on the first day, at some point we would run out of relevant topics to cover in lecture
  • We've reached that point
  • So now both Mondays and Wednesdays will be group meeting days
• There is a CS dept "town hall" this Thursday @ 5 in Olsson 120 from 5-6
  • Free pizza!
  • This will be your best chance to have your opinions heard by the department chair!

Deliverable for Iteration 11

• The unit tests from the last iteration
  • There was confusion (amid trips, snow days, and spring break) in getting them done fully correctly in the last iteration
  • You should have them already done, but not necessarily in the right "form"
  • Details on the next slide
• An updated requirements document (this should have been kept up-to-date)
• The full transition plan: this contains:
  • An updated deployment plan (iteration 7)
  • An updated master test plan (iteration 8)
  • A working Jenkins build for your unit tests (iteration 9)
  • A half dozen (or so) unit tests (iteration 10)
  • The updated requirements document (iteration 11)
• Some of these may require editing from the original
• This should be "packaged" into a single document
  • A single Redmine wiki page, with links to the various parts (which are presumably sub-pages), is fine

Unit Tests

• For iteration 10 (and will be checked for iteration 11) you should have a half-dozen or so unit tests written
  • These should be real unit tests that test real code
  • Have a variety: test a model, a controller, a view, etc.
• They should be scripted to run with the Jenkins build
• You should indicate to me how this is done so that I can find them
  • In the lead's TPS report is fine
  • But you need to tell me where to find the unit tests!

You should be aware of this!

Your ability to pass this course is contingent on the fact that, as of Tuesday, March 25th at noon, you have a fully working system deployed to the final deployemnt host.

• "Fully working system" means that you have implemented all the features in the requirements document, and they (more or less) work
  • There can be bugs, of course, at this point
  • Hence the need for an updated requirements document
  • And you need to speak to me if there are any major changes to that document
• "Final deployment host" is what is specified in your deployment plan; it is not pegasus!

 
As mentioned on day 1 of this semester, if these are not done, then you will fail this class and then likely not graduate.

Transition Phase

• It's 3 iterations (6 weeks) long
• During the transition phase, Jenkins must always build successfully
  • If your commit breaks something, then you should immediately fix it
  • This means that you need to run the test after you do a commit (which is the point of this type of testing, anyway)
  • I will be regularly checking that the builds work...
• There will be iteration deliverables (the various artifacts in the deliverables slide set
  • I will detail these as we go through the transition phase
  • The only one I leave to you to schedule is the final STS technical report
    • I need that two weeks before it is due to your STS professor (so take the earliest deadline of the group)
    • 1 week for me to read it, and 1 week for you to make edits to the document after I comment on it
• 6-person groups will have one lead for the entire transition period
  • The 7 person group will change leads one iteration into the transition phase

Lecture 16: Wednesday, February 19th, 2014

• Iteration 8
  • Evaluations will be out very soon
  • Montanova, your end-of-phase surveys are due by this Friday
• We are half-way through iteration 9
  • Leads, your first weekly report was due yesterday at noon
  • Deliverable for this iteration is the Jenkins continuous integration job (we'll talk about that today)
• Next week starts iteration 10
  • This will be a phase change for the 6-person groups, but not for the 7-person group
  • This will require filling out the end-of-phase surveys!
• Don't forget to report your hours!
• Guest lecture by the mentor for LEAP, likely next week
  • If you are late class that day, I will get VERY cranky
• Today we will start (and finish) the 05-ci slide set
  • As mentioned on the first day, the lectures will end in a few more weeks, and Wednesdays will become a second group work day

Lecture 13: Wednesday, February 12th, 2014

• Iteration 7
  • Evaluations were released last week. Please read them! Some of them contain issues to be addressed in this iteration.
  • The attendance has now been entered
• Iteration 8 ended yesterday
  • Leads: TPS reports were due yesterday
  • This is NOT a phase change for the 6-person groups; only for the 7-person group
  • Deliverable for this iteration is the MTP (in the 03-testing slide set)
• We are just starting iteration 9
  • Deliverable is the continuous integration plan (more on this later)
  • All 6-person groups will have a phase change (new lead and new secretary) at the end of this iteration (i.e., in two weeks)
  • This will require filling out the end-of-phase surveys!
• Don't forget to report your hours!
• Guest lecture (by the mentor for LEAP). Two choices:
  • Unit testing in Ruby projects using RSpec
  • Version control using git
• Today we will start (and finish) the 04-maintenance

Lecture 10: Wednesday, February 5th, 2014

• Iteration 7
  • Evaluations have been released. Please read them! Some of them contain issues to be addressed in this iteration.
    • But attendance has not been entered yet...
• We are half-way through iteration 8
  • Leads, your weekly reports were due by noon yesterday
  • Don't forget to report your hours!
  • Deliverable for this iteration is the MTP (in the 03-testing slide set), which we will finish talking about today
• Reports
  • TPS report due by next Tuesday at noon
  • Meeting reports due by the end of each meeting
• Today we will finish the 03-testing

Favorite color scheme?

Reveal.js comes with a few themes built in:
Default - Sky - Beige - Simple - Serif - Night
Moon - Solarized

Lecture 7: Wednesday, January 29th, 2014

• Iteration 7 ended this past Monday
  • Evaluations will be out this weekend
  • The deployment plan may need some work, as additional customer meetings clarify details; this is fine
  • One group is missing their TPS report...
• Today is day 2 of iteration 8
  • Deliverable is the master test plan (in the 03-testing) slide set, which we will hopefully get to today
  • All groups will have a phase change (new lead and new secretary) at the end of this iteration (i.e., in two weeks)
• Reports
  • Weekly report due by next Tuesday at noon
  • Meeting reports due by the end of each meeting
• Today we will finish the 02-deliverables slide set, and start on 03-testing