Senior Capstone

Preamble

  • Course Title: Senior Capstone (mwd 410)
  • CRN: 44657
  • Credits: 4
  • Prerequisites: mwd 310 and senior standing (87+ credits); or, permission from the Dept
  • Days: Mondays and Wednesdays
  • Time: 8:10–9:50 am
  • Room: 316, Charles A Dana Hall
  • Dates: 4 September–14 December 2019
  • Professor: Roy Vanegas (pronounced “vuh-nay-gus”)
  • Email: vanegas at hartford dot edu
  • Phone: 860.768.5925
  • Office: Charles A Dana Hall, Room 310B
  • Office hours: By appointment via Compass on the following days…
    • Mondays: 10:00–11:00 am and 1:30–2:30 pm
    • Tuesdays: 9:00–11:00 am
    • Wednesdays: 10:00–11:00 am and 1:30–2:30 pm

Description

Using a combination of empathy maps, agile methodologies, burn down charts, story points, and Kanban boards, terms explained throughout the course, students will work in teams to create web-based software projects in an agile-focused manner that observe the entire software development life cycle. Projects will be developed as full stack applications using either the lamp or mern environment.

Learning Outcomes

Upon successful completion of this course, students will understand...

  • how to effectively collaborate on a development/design team;
  • how to plan a sprint and course-correct for delays in deliverables;
  • how to keep to a burn down chart;
  • how to use ZenHub as a Kanban tool;
  • how to write, update, and move issues in a Kanban board;
  • how to clearly define story points for better delivery times;
  • how to carry out a daily stand-up;
  • how to implement a codebase that is near free of errors;
  • how to implement linters and code-quality tools into one’s tool chain;
  • and, how to iterate over the software development life cycle.

Schedule

Important Dates

  • No class (week 13): 27 November (Thanksgiving recess)
  • Assignment 1 due: 25 September
  • Assignment 2 due: 9 October
  • Assignment 3 due: 23 October
  • Assignment 4 due: 6 November
  • Assignment 5 due: 13 November
  • Final project due: 16 December

Check the University’s official calendar for other important dates.

Note: Time permitting, I will make every attempt to cover the topics listed below in order. However, depending on the cadence of the class, some topics may be overlooked.

Week Topics Homework
One
  • Syllabus breakdown and course expectations
  • Start bringing personal laptops to class on a weekly basis
  • Prepare an informal final project pitch idea for 11 September
Two
  • Open GitHub accounts
  • Intro to Git
  • Git cloning
  • Git committing
  • Git pushing
  • Git pulling
  • Git branching
  • Git forking
Three
Four
  • Assignment 1 due
  • tbd
  • Study the in-class code examples and notes
Five
  • tbd
  • Study the in-class code examples and notes
Six
  • Assignment 2 due
  • tbd
  • Study the in-class code examples and notes
Seven
  • tbd
  • Study the in-class code examples and notes
Eight
  • Assignment 3 due
  • tbd
  • Study the in-class code examples and notes
Nine
  • tbd
  • Study the in-class code examples and notes
Ten
  • Assignment 4 due
  • tbd
  • Study the in-class code examples and notes
Eleven
  • tbd
  • Study the in-class code examples and notes
Twelve
  • Assignment 5 due
  • tbd
  • Study the in-class code examples and notes
Thirteen
  • tbd
Happy holidays!
Fourteen
  • tbd
  • Study the in-class code examples and notes
Fifteen
  • tbd
  • Study the in-class code examples and notes
Sixteen
  • Final project due
  • tbd
Happy holidays!

Class Policies

  • Consuming food in class. There is no eating inside our classroom, either during class or while on break. Eat before or after class. Drinks in covered containers, however, are allowed.
  • Grading. I do not give grades — students earn them. The grade you earn is based strictly on a formula clearly listed in your syllabus, under the Grading Standards section.

Advice on Succeeding in Class

We will go over the following document in detail on the first day of class.

Assignments

There are five projects for the semester, each one a component of the final project. (See the grading standards section regarding how each is used to calculate your grade.)

  1. Assignment (Project Requirements)
  2. Assignment (User-Centered Design)
  3. Assignment (Backend Development)
  4. Assignment (Frontend Development)
  5. Assignment (Final Implementation)

Grading Standards

Grading Formula

Your grade for this course — explained by The University of Hartford here — will be computed using the following formula:

  • Assignment 1 — Requirements (5%)
  • Assignment 2 — User-Centered Design (20%)
  • Assignment 3 — Backend Development (25%)
  • Assignment 4 — Frontend Development (25%)
  • Assignment 5 — Final Implementation (25%)

This grading formula is unbending and will be adhered to strictly.

Important Note

Please, please do not try to negotiate a grade with me. By asking me to treat you favorably, you’re asking me to put you above your classmates. Manage your time well; I do not accept late work.

Academic Honesty

You are reminded of the college’s academic honesty policy. Ensure all the work you submit is your own.

Students with Disabilities

Read about how The University of Hartford supports students with disabilities: https://www.hartford.edu/academics/academic-support/accessibility-services/default.aspx

Contact

My email address is vanegas at hartford dot edu. However, I only communicate with students over email in emergency situations (pet emergency, personal tragedy, etc). For matters related to the class, you’re advised to see me in person before or after class, or during my office hours via Compass.

Office Hours

My office hours are walk-in for quick questions and by appointment via Compass for more involved sessions.

  • Office: Charles A Dana Hall, Room 310B
  • Office hours:
    • Mondays: 10:00–11:00 am; 1:30–2:30 pm
    • Tuesdays: 9:00–11:00 am
    • Wednesdays: 10:00–11:00 am; 1:30–2:30 pm