Senior Capstone

• 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: Drop-in or by appointment 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

Using a combination of empathy maps, agile methodologies, burn down charts, story points, and Kanban boards, 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 menn environment.

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.

Important Dates

• No class (week 13): 27 November (Thanksgiving recess)
• Assignment 1 due: 25 September
• Assignment 2 due: 21 October
• Assignment 3 due: 22 November
• Assignment 4 due: 20 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	Working with your browsers’ dev tools Open GitHub accounts Intro to Git Git cloning Git pushing Git pulling	Read about the basic Git cli commands Watch these GitHub ui tutorials Read GitHub’s Git Handbook Read all the items under the Getting Started from Atlassian’s Git tutorial Watch videos 1–8 from GitHub’s YouTube channel on Git and GitHub
Three	Clone the examples repo Project groups assigned Discuss common Git branching models used by teams Git committing Git merging Git branching Git forking Project pitches	Study the in-class code examples and notes Install the ZenHub browser extension Read Better Software & Stronger Teams
Four	Assignment 1 due Git tagging html and css refresher Install Atom linters for html (w3c-validator)and css (linter-stylelint). cli/Terminal tutorial	Install Mongodb Install Node Follow these instructions on installing and configuring Gulp Read Semantic Versioning 2.0.0 Read A Successful Git Branching Model Study the in-class code examples and notes
Five	Gulp tutorial CSS modular architecture using variables and file stacks Linters for HTML, Sass, and JavaScript Working with editorconfig	Study the in-class code examples and notes
Six	Assignment 2 due More Gulp	Study the in-class code examples and notes
Seven	json refresher Observing json formatting conventions Linters demo	Study the in-class code examples and notes
Eight	Assignment 2 due Intro to Sass Intro to JavaScript templating with Nunjucks	Study the in-class code examples and notes
Nine	More Nunjucks: Reading keys from json files	Study the in-class code examples and notes
Ten	More Nunjucks: Interpolating Nunjucks with html using Gulp	Study the in-class code examples and notes
Eleven	Working with typography, including proper single- and double-quotes and dashes Using icons from Font Awesome Using icons from The Noun Project Intro to Nunjucks	Study the in-class code examples and notes
Twelve	Assignment 3 due Working with permission bits on files More Nunjucks Using Nunjucks with Gulp Intro to MongoDB	Study the in-class code examples and notes
Thirteen	Intro to Mongodb crud operations in MongoDB Holiday break	Holiday break
Fourteen	crud operations using the full menn stack and Gulp	Study the in-class code examples and notes
Fifteen	Open lab	Study the in-class code examples and notes
Sixteen	Assignment 4 due	Holiday break

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

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

• Advice for Succeeding in Class (in Markdown)
• Advice for Succeeding in Class (in pdf)

There are four 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 (due 25 September 2019)
2. Assignment (due 21 October 2019)
3. Assignment (due 22 November 2019)
4. Assignment (due 16 December 2019)

Grading Formula

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

• Assignment 1 — Project Planning (25%)
• Assignment 2 — Project Scaffolding and Database Design (25%)
• Assignment 3 — Design, Front-End Execution, Database Verification, and JS Templating (25%)
• Assignment 4 — Final Implementation, using MongoDB, Express, Nunjucks, and Node (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.

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

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

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 (see below).

My office hours are walk-in for quick questions and by appointment for more involved academic inquiries.

• 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

If neither of the aforementioned times agrees with your schedule, we can make alternate arrangements to meet.