General Guidelines

Throughout the entirety of the course, you will be working on your own software project. The course project is a major component of your evaluation.

  • You will need to work in teams of size 5-7 students. No teams with less than 5 and more than 7 students will be allowed.
  • Work on a topic of your choice, with a team of your choice.
  • Your app need to be designed according to one of the following architectural models:
    • MVC architecture
      (Our recommedation goes to MVC, since you have been introduced to it since CSC207. However, if you are willing to learn other architectures, feel free to do so!)
    • Three-tiered architecture
    • Microservices architecture
    • If you have other architecture in mind, talk to your instructor.
  • You will follow Agile Development methodology, with frequent deliveries, as specified below.
  • Project tracking will be done using Jira , one of the Agile tools much in demand in the modern software engineering.
  • How to have a successful team

Project Topics

TBD

Project Deliverables

Stage Instructions Files + Resources Due Date/Time
Sprint 0 Team Registration:
    TBA
To do list & notes for Sprint 0
  • Complete documentation using the handout material and the marking rubric as a guide
  • Personas and User Stories and all other necessary concepts overed in class
  • Keep in mind - sprint 0 documentation is due at the end of the day of the specified date
  • The termination of sprint 0 signifies the start of sprint 1
  • To start sprint 1, you will need to do the following:
    • Agree (as a team) on the point scale you will use to evaluate your stories
    • Ask the product owner to prioritize thge backlog
    • Agree (as a team) how many points you will do in sprint 1 (your velocity)
    • Evaluate (using poker play) top priority stories (just enough to fill in the points for sprint 1)
    • Record PB on Jira
    • Add a few stories to your sprint 1 on Jira
    • Divide stories into tasks
    • Start sprint 1.

Jan 20th, 11:59PM EST (team.md due)

Jan 20th, 11:59PM EST (first draft of project proposal due) (optional, for feedback)

Jan 27th, 11:59PM EST (Sprint 0 deliverables)

Sprint 1 To do list & notes for Sprint 1
  • RPM.md
  • sprint1.md
  • Standups
  • Documentation
  • System Design Document
11:59pm Feb 10th
Sprints 2-4 To do list & notes for Sprint N
  • SR(n-1).md
  • sprintN.md
  • Standups
  • Update Documentation, System Design Document
TBD
Final Presentation Read over all the documents carefully, read over the piazza post regarding the project, and sign up for a time slot to present. Wednesday, April 5th. See piazza for more detais.