Software Management & Development · Group project · Team 6

Team 6 Project Runbook

One product, six modules. Each of us builds one module and takes one shared job. We join the modules through reviewed pull requests, run the product on Azure and demo it live.

Next due
Milestone 1
Submit
Blackboard, one assignment per milestone
Grade
30% of the course
Progress
0 steps
Connecting

The task

  • The six of us build one product together: Sara, Blas, Emile, Tomás, Susana and Jose Luis.
  • Each member builds one module of it. Your module is the app you build in your own repository, checkpoint by checkpoint.
  • Each member also takes one shared job for the whole product.
  • All modules go into one product through reviewed pull requests, then run on Azure.
  • On Tue 15 Dec we present and demo it live, and every member answers questions.

Your module

Entityone main thing, one table
APIendpoints for it
Calculated resultsomething worked out from the data
Teststhat pass
Frontend pageone page that uses the API

Shared jobs, one each: CI, Docker Compose, Azure deployment, frontend, database, code review, documentation. That is seven jobs for six people, so one stays open or is shared. We decide it in step 5.

What to hand in

Each milestone is a Blackboard assignment. Paste the links below in the Steps tab so the whole team sees them before someone submits. Both milestone pages on Blackboard still say "Placeholder", so the details can change.

M1Team and theme Mon 23 Nov, 12:00 · team repo, theme, one module and one job each, one issue per module on the board
M2Conventions Mon 23 Nov, 23:59 · conventions in the team README, first endpoint of each module in each member's repo
M3One product Fri 4 Dec · all modules together, through reviewed pull requests
M4On Azure Mon 14 Dec · running on Azure, built by GitHub Actions, plus a 5-minute backup video
M5Final presentation Tue 15 Dec, session 14 · live demo, questions to every member

How it is graded

  • 30% of the course, with individual assessment.
  • The team's product, its final presentation and demo.
  • Your own part: your module, your pull requests and reviews, and your answers to questions about the code.
  • The final exam is Thu 17 Dec (session 15), separate from this.

Rules

  • Every change to main goes through a reviewed pull request, merged with a merge commit.
  • AI is allowed and encouraged, except where an activity says otherwise (as Lab 5 did). You are responsible for every line and must explain it in the demo. Say which tool you used, for what and with which prompts.
  • Never commit passwords, keys or .env files. A secret that was committed must be revoked.
  • Never git push --force on a branch other people use.

Ask Alberto

  • How does each member's own repository relate to the team repository?
  • What exactly do we submit for Milestones 1 and 2: the team repo link, or more?
  • Seven shared jobs for six people: leave one open, or share it?
  • One shared database for all modules, or one per module?
  • Whose Azure account do we deploy to?