Week 7 [Fri, Feb 19th] - Tutorial

1 Exercise on Requirements: PR Tracker

1. 10 minutes Write the answers to the following questions. You can write your answers in a local document file (e.g., a Word doc) first; when done, paste a screenshot in the workspace document. Writing the answer directly in the workspace document might result in too much lag.

   Question adapted from a past exam paper.

   Pull Request Tracker (PRT) is a desktop application meant to help tutors of a Software Engineering module deal with GitHub PRs more efficiently (compared to the GitHub Web interface). For example, it will help tutors find and review PRs from their mentees easily. It will help the managers of the module (e.g., professor, head TA) to easily keep track of how tutors are dealing with mentee PRs. PRT will communicate with GitHub using the GitHub API.

   1. Write 1 must-have and 1 nice-to-have user stories, covering user types tutor and manager.
   2. Write at least 1 Non-Functional RequirementsNFRs, related to performance/scalability and/or usability.
   3. Give at least 1 terms worth recording in the glossary.
   4. Complete the following use case. Give at least one extension. Note that the tutor should give comments in the order of PR size (i.e., give comments to smaller PRs first). Assume the following use cases exists already: U1. Sort PRs by a criterion, U2. Add comments to a PR

   System: PRT
   Use Case: U3. Add comments to mentee PRs
   Actor: ...
   Precondition: ...
   

   ...

2. Check a peer answer (provided by the tutor) for the bugs listed below and discuss, as directed by the tutor.

2 Refine your DG after the tutorial

• After the tutorial, if applicable, refine the relevant sections of your own DG based on what you learned from the tutorial activities.