This use case describes the steps to create a repository on GitHub. A user clicks "Create a New Repo" and enters a name and privacy setting for the new repository before clicking "Create Repository". Payment details may be required for a private repository. Once created, the new repository is added to the user's account.

1. IDENTIFICATION SUMMARY
TITLE: Create Repository
SUMMARY: This use case describes the steps associated with creating a repository.
ACTOR(S):
1. User – interfaces with GitHub’s web application
CREATION DATE: July 6, 2013 DATE OF UPDATE: July 6, 2013
VERSION: 1.0 PERSON-IN-CHARGE: Jeric Paolo V. Arimado
FLOW OF EVENTS
PRE-CONDITIONS:
1. User must have already gone through the “Sign-in account” use case.
MAIN SUCCESS SCENARIO:
1. User clicks “Create a New Repo” button at the top-right part of any page.
2. GitHub presents a settings page for creating a new repository.
3. User must select which account he/she wishes to create the repository on.
4. User must also enter a name for the new repository and select the privacy of the repository.
5. User clicks “Create Repository” button.
6. Use case ends successfully.
ALTERNATIVE SEQUENCE:
A4 User chooses “Private” as the level of the repository’s privacy.
1. GitHub asks for payment details if the user is not a premium member.
2. User enters payment details.
3. Use case proceeds to step 5.
ERROR SEQUENCE:
E4 User enters incorrect payment details when asked by the system.
1. GitHub throws an error about incorrect payment details.
2. Use case will not proceed unless user enters correct payment details or chooses “Public”
as privacy setting of the new repository.
POST-CONDITIONS:
1. New repository is created on the user’s account.

2. IDENTIFICATION SUMMARY
TITLE: Delete Repository
SUMMARY: This use case describes the steps associated with deleting a repository.
ACTOR(S):
1. User – interfaces with GitHub’s web application
CREATION DATE: July 6, 2013 DATE OF UPDATE: July 6, 2013
VERSION: 1.0 PERSON-IN-CHARGE: Jeric Paolo V. Arimado
FLOW OF EVENTS
PRE-CONDITIONS:
1. User must have already gone through the “Sign-in account” use case.
2. User must have already chosen a repository to delete.
MAIN SUCCESS SCENARIO:
1. User navigates to the repository to be deleted.
2. User selects “Settings” button on the repository’s page.
3. User selects “Delete this repository” button on the settings page.
4. As a final check, GitHub presents a confirmation dialog and asks the user for the name of the
repository to be deleted.
5. User must press the final warning button to confirm deletion of the repository.
6. GitHub deletes the repository.
7. Use case ends successfully.
ERROR SEQUENCE:
E4A User decides to cancel the deletion of the repository.
a. User selects the close button of the confirmation dialog.
b. GitHub cancels the deletion process of the repository.
c. Use case ends.
E4B User enters incorrect repository name.
a. The final warning button is greyed out (cannot be selected).
b. Use case will not proceed unless user enters the correct repository name.
POST-CONDITIONS:
1. Selected repository should be deleted from the user’s account.

3. IDENTIFICATION SUMMARY
TITLE: Watch Repository
SUMMARY: This use case describes the steps associated with watching a repository.
ACTOR(S):
1. User – interfaces with GitHub’s web application
CREATION DATE: July 6, 2013 DATE OF UPDATE: July 6, 2013
VERSION: 1.0 PERSON-IN-CHARGE: Jeric Paolo V. Arimado
FLOW OF EVENTS
PRE-CONDITIONS:
1. User must have already gone through the “Sign-in account” use case.
2. User must have already chosen a repository to watch.
MAIN SUCCESS SCENARIO:
1. User navigates to the repository to be watched.
2. User selects “Watch” button on the repository’s page.
3. User’s account starts receiving notifications regarding any changes made to the repository.
4. Use case ends successfully.
ERROR SEQUENCE:
E2 User decides to unwatch the repository.
1. User selects the “Unwatch” button on the repository’s page.
2. User’s account stops receiving notifications regarding any changes made to the
repository.
3. Use case ends.
POST-CONDITIONS:
1. The user should receive notifications regarding any changes made to the selected repository.