COSC 499: Capstone Software Engineering Project


Administration

Office Hours: By appointment only.

Download course outline and review it carefully. It covers course objectives, grading, and various course and university policies.

Important Dates: See http://okanagan.students.ubc.ca/calendar/

Available Projects: See the list of projects.


Tentative Schedule

Note: All items under THINGS TO SUBMIT are due at the beginning of class on the date it is listed. The sign ⊗ denotes the weekly git stat report in PDF for each team. The sign denotes deliverables that your client will rank.

Term 1 (September - December)
Week Things to Submit (by Wed 10:30am) Date/Topic Resource
1 9/11
  • Course overview
  • Project overview
  • Complete background survey (Canvas)
  • Lecture slides
  • Video from the University Industry Liaison Office
  • IP agreement template
  • 2 9/16
  • Toy individual Github exercise
  • 09/18
  • Form teams
  • Team responsibilities and expectations
  • Meeting format and how to take minutes
  • Lecture slides
  • Team roles
  • How to run gitstats on your repo
  • Criteria for weekly contributions (see slides)
  • 3 9/23
  • Weekly client meeting day and time
  • Complete Google doc
  • Mini team Github exercise
  • 09/25
    Suggested steps:
  • Setting up your project in GitHub
  • Make sure everyone has a basic understanding of the project
  • Know who your user groups are, and be able to think about how they each want to use the system differently
  • Agile Software Development and the Agile Manifesto
  • Defining features as tasks, exploarations, or chores
  • Task estimation
  • Using the Project Dashboard in GitHub (be sure you read about sprint planning too)
  • 4 09/30
  • Project repo
  • 10/02
    Suggested steps:
  • Know the timeline for each milestone (Requirements, Peer Testing #1, Peer Testing #2, Final)
  • Agree with client and instructor on the features for each milestone
  • Identify possible extra features if time allows
  • If your client is flexible on the tech stack: provide at least 3 options and document all pros and cons for each before letting your client make a choice
  • Develop your test strategy
  • More on git flow
  • Sprint retrospective
  • Learn about different levels of testing and include them in your requirements document
  • 5 10/07
  • 10/09
    Suggested steps:
  • Have an initial draft of the DFDs completed
  • Flush out all the requirements needed
  • Prepare for the video presentation
  • 6 10/14
  • Requirements video presentation
  • Share the link to your video presentation
  • Create account on evaluation website
  • 10/16
    Suggested steps:
  • Incorporate feedback received from video presentation into report
  • Finalize requirements report
  • Criteria for Requirements Milestone
  • 7 10/21
  • Requirements report
  • Group evals (due the Saturday before)
  • Peer evals
  • 10/23
  • Criteria for Peer evaluations
  • Criteria for Group evaluations
  • Student evaluation rubric
  • 8 10/28
  • 10/30
  • Read/review best practices
  • Adopt a continuous integration approach
  • See how to implement continuous integration
  • 9 11/04
  • 11/06
    Suggested steps:
  • Heuristic evaluation experiment instructions created
  • User tasks for each user group identified
  • Estimate/Time your experiment
  • 10 Midterm break -- No classes
    11 11/18
  • Sign up for Peer Testing
  • 11/20
  • How sign up works
  • Do dry-runs with your teammates to ensure tech setup works for both conditions
  • Criteria for Peer Testing
  • 12 11/25
  • Video demo
  • Peer Testing #1 (Any time during the week)
    13 12/02
  • Peer Testing #1 report
  • Peer evals (no group evals needed)
  • 12/04 Client feedback - I will coordinate them with your clients
  • Criteria for Client evaluation
  • Term 2 (January - April)
    Week Things to Submit (by Wed 10:30am) Date/Topic Resource
    1 01/06
  • 01/08
  • Client feedback review
  • 2 01/13
  • 01/15
    3 01/20
  • 01/22
    4 01/27
  • 01/29
    5 02/03
  • 02/05
    Suggested steps:
  • Update your experiment instructions
  • Update your user tasks for each user group
  • Estimate/Time your experiment
  • 6 02/10
  • Sign up for Peer Testing
  • 02/12
  • Reminder of how sign up works
  • Do dry-runs with your teammates to ensure tech setup works for both conditions
  • 7 Reading break -- No classes
    8 02/24
  • Video demo
  • Peer Testing #2 (Anytime during the week)
    9 03/03
  • Peer Testing #2 report
  • Peer evals (no group evals needed)
  • 03/05
    10 03/10
  • 03/12
    11 03/17
  • 03/19
    12 03/24
  • 03/26
  • Wrap up
  • 13 Good Friday -- No classes 04/02
    14 Last day of classes is April 08 -- No classes 04/09
    FINAL EXAM PERIOD
  • Final report, code repo, video demos
  • Share the link to your video demo
  • Group evals (due the Saturday before)
  • Peer evals
  • Client feedback - I will coordinate them with your clients
  • Criteria for Final Milestone