Use Case Template - BilalSh10/Ekhtar-Al-Saadah GitHub Wiki
| Name | Log in |
|---|---|
| Brief Description | Allows for the admin to access his personal page to manage the website as he like. |
| Actors | Admin |
| Pre-conditions | The user must be an admin with user name and password. |
| Basic flow |
1. Admin Press “log in” button. 2. The log in page display. 3. The system asks the admin for a user name and password. 4. The system verify the user name and the password. 5. The system display the personal page for the admin. |
| Exception flow |
4-a.The system does not recognize the user name or the password. 4-b. Shows to the user an error massage. |
| Post conditions | The admin will enter his personal page successfully. |
| Name | Edit information about association |
|---|---|
| Brief Description | This operation allows the admin to change the information about the association, he can add or remove texts and images.(The “About” tab in the navigation bar). |
| Actors | Admin |
| Pre-conditions | The admin must have successfully logged in the system. |
| Basic flow |
1. The admin enters the “About” page via the navigation bar in the homepage. 2. He presses the “Edit page” button. 3. The system represents the current textual information appearing in a TextBox. 4. The system represents the current picture appearing in a specific section. 5. The admin can edit the textual information, either delete, add, or replace parts of the current text. 6. The admin can modify the picture, either by replacing it or deleting it. 7. In order to save the modifications to the “About” page, the admin has to press the “Save changes” button. 8. The system receives the new information and updates the current information to it. |
| Exception flow |
1. An internet problem from the admin’s side, information can not be sent to the server, the admin gets an alert: “no internet connection”. 2. Server problem, there is a problem on the server side, the admin receives a message: “Please retry this operation in a few minutes”. 3. The image is of incorrect format, the image can be of format jpeg only. 4. The image’s size exceeds the size defined in the requirements. |
| Post conditions | Modifications to the text and image appearing in the “About” page are saved on the server. |
| Name | Contact association |
|---|---|
| Brief Description | This operation allows the website's visitor to contact the association by sending it a message. |
| Actors | Website visitor |
| Pre-conditions | The visitor must be on one of the website's page. |
| Basic flow |
1. The visitor enters the “Contact us” page via the navigation bar in the homepage. 2. The system shows three TextBoxes for receiving the inputs from the visitor, one for the visitor's name, one for his email address and one for the message content. 3. The visitor fills the relevant information. 4. The visitor presses the "send" button. |
| Exception flow |
1. An internet problem from the visitor's side, information can not be sent to the server, the visitor gets an alert: “no internet connection”. 2. Server problem, there is a problem on the server side, the visitor receives a message: “Please retry this operation in a few minutes”. 3. The email address is invalid, the visitor gets the alert: "Invalid email address". |
| Post conditions | The message from the visitor is sent to the website's email address. |
| Name | Fill donation form |
|---|---|
| Brief Description | This operation allows the website's visitor to fill a donation form. |
| Actors | Website visitor |
| Pre-conditions | The visitor must be on one of the website's page. |
| Basic flow |
1. The visitor enters the “Fill donation form” page via the navigation bar in the homepage. 2. The system shows four TextBoxes for receiving the inputs from the visitor, one for the visitor's name, one for his cellphone number, one for his email address and one for the message content. 3. The visitor fills the information. 4. The visitor presses the "send" button. |
| Exception flow |
1. An internet problem from the visitor's side, information can not be sent to the server, the visitor gets an alert: “no internet connection”. 2. Server problem, there is a problem on the server side, the visitor receives a message: “Please retry this operation in a few minutes”. 3. The email address is invalid, the visitor gets the alert: "Invalid email address". |
| Post conditions | The form is sent as a message to the website's email address. |
| Name | Manage articles |
|---|---|
| Brief Description | This operation allows the admin to modify information about events shown in the articles section, he can enter textual and photographic descriptions of an event, replace or delete them to one already existing in the gallery. |
| Actors | Admin |
| Pre-conditions | The admin must have successfully logged in the system. |
| Basic flow |
1. The admin enters the “articles” page via the navigation bar in the homepage. 2. He presses the “Edit page” button. 3. The page reloads into a new one that contains “add article button”, and “modify article” buttons appearing next to each event in the gallery. 4. In order to add a new article the admin presses the “add article” button. 5. A new section appears on the page that contains a textbox, and a button called “load image” and the “save button”. 6. The admin fills the textbox and loads an image, then presses the “save” button. 7. In order to modify an existing article the admin presses the “modify article” button appearing next to it. 8. The current textual information appears in a textbox, he can make changes to them, or to the image by pressing “delete image” or “replace image”, also there is a “delete article” button which deletes the article from the gallery, to save modifications the admin presses the “save” button. 9. A request with the relevant information is sent to the server. 10. Server saves them in the database. |
| Exception flow |
1. An internet problem from the admin’s side, information can not be sent to the server, the admin gets an alert: “no internet connection”. 2. Server problem, there is a problem on the server side, the admin receives a message: “Please retry this operation in a few minutes”. 3. An added image is of incorrect format, the image can be of format jpeg only. 4. The image’s size exceeds the size defined in the requirements. |
| Post conditions | Modifications to the “gallery” page are saved on the server. |
| Name | Manage events |
|---|---|
| Brief Description | Allows for the admin to add and modify the events in the website. |
| Actors | Admin |
| Pre-conditions | The admin must be successfully logged into the system. |
| Basic flow |
1. Press the “Manage events” button. 2. the website shows the events that have been created. 3. press the “ + “ button. 4. the system shows to the admin a form of the event to fill it, in other words it shows(the name of the event, description, photo). 5. press “confirm” button to confirm adding the event. 6. the event will be shown in the manage events page. |
| Alternate flows |
3-a. press on the event to modify it. b- the website shows the details of the event. c. the admin can modify one or more of (name the event, description, photo) or even delete it. d. press “confirm” button to confirm the changes. |
| Exception flow | 5-a. A problem occurs in the server sends the error message “Please retry the operation in few minutes”. There is an internet connection on the admin’s part, the error message “Internet connection problem”. |
| Post conditions | An event has been added or modified successfully, the new changes will appear on the visitor’s page. |
| Name | Join mailing list |
|---|---|
| Brief Description | This operation registers the visitor’s email in a list, whose members are emails that get notifications when there is an upcoming event with information about it. |
| Actors | Visitor |
| Pre-conditions | The visitor must be on the subscribe page. |
| Basic flow |
1. The visitor presses “Subscribe to mailing list”. 2. A window shows asking him to enter his first name, last name, and email address. 3. The user presses the “done” button. 4. A request is sent to the server, the information is saved in the database. |
| Exception flow |
1. An internet problem from the visitor’s side, information can not be sent to the server, the visitor gets an alert: “no internet connection”. 2. Server problem, there is a problem on the server side, the admin receives a message: “Please retry this operation in a few minutes”. 3. Invalid email, the user enters an invalid email address, and receives the message “The email address is invalid”. 4. Email already registered in the mailing list, the visitor receives the message “This email address is already registered in our mailing list”. |
| Post conditions | The visitor’s email is registered in the database, he receives an email confirming this. |