POD System - Use Case Scenarios - Ver 3_3

POD System – Features and RequirementsThe following document explains the main functionalities and features for POD system. The documentwill address the users for the applications based on 4 main roles (Management – Account Manager –Administrator – User) noting that the POD hierarchy has multiple authorizations described as:Management Account Senior Account Manager Executive Account Executive Media MonitorThe client has a production cycle described as the following:Account Project RequestManager Request Client

1. Login To be able to access the system, client must be logged in using credentials provided byPOD.Primary Actor POD UserPost Condition • A session is created for the user saving all the data that was being browsedMain Success • User is logged inScenario 1. User enters the website link address 2. A web form is shown to the user 3. User inserts username 4. User inserts password 5. User Presses on “Login” button 6. User is redirected to the home page2. Create User Any user with Administrator privilege could create and update users within the system.Primary Actor POD Administrator UserPost Condition • New user is created/updatedMain Success 1. User logs inScenario 2. User is redirected to the home page 3. User presses on “Users” button 4. A list of users is shown 5. User can select a user to edit its data 6. A pop up is shown to the user containing the fields: o Name o Username o Password o Privilege o Account Manager [Not Mandatory] 7. User presses on save button 8. User can create new user(s) by clicking on “Create New User” button 9. A pop up is shown to the user containing the fields: o Name o Username o Password o Privilege o Account Manager [Not Mandatory] 10. User Presses on save button 11. A new user record is shown in the users list3. Create Client and Project Any user with Administrator privilege can create and update client and projectsbelonging to a client within the system.Primary Actor POD Administrator User

Post Condition • New Client is created/updatedMain Success 1. User logs inScenario 2. User is redirected to the home page 3. User presses on “Clients/Projects” button 4. A list of clients is shown 5. User can select a client to edit its data 6. A pop up is shown to the user containing the fields: o Client Name o Account Manager [List of account managers] o List of Project(s) ▪ User can click on a project name to edit it o Add a new project button ▪ Project Name 7. User presses on save button 8. User can create new client(s) by clicking on “Create New Client” button 9. A pop up is shown to the user containing the fields: o Client Name o Account Manager [List of account managers] o List of Project(s) ▪ User can click on a project name to edit it o Add a new project button ▪ Project Name 10. User Presses on save button 11. A new client record is shown in the clients list4. Notifications The system allows the users to receive notifications based on a new request update or asuggested service passed by another user.Primary Actor Logged in UserPost Condition • Notification marked as read and included in the report with the reading dateMain Success 1. User Logs inScenario 2. User is redirected to the home page 3. User Presses on “Notification” button 4. A list of notifications is shown chronologically including the request change or task assignment. 5. User clicks on any notification to check it for more details 6. A Pop-up of “Service Request” is shown to the client including the fields: o Project Name [Not Mandatory] o Client Name o Request/Service Title o Request/Service Description o Attachment(s) [Not Mandatory] ▪ Uploader Name ▪ Date ▪ Time o Request Status (urgent – normal – cancelled)

5. Accepting Request, Updating Request and Assigning Tasks Account manager can view all requests belonging to a client under his/her authorization tocreate, update as well as forwarding the request to another authorization level. Account Manager can update request status, the request status is not just acceptance orrejection; it also includes uploading attachment(s), adding a title, writing a brief and writing adescription. Any system user that has authorization for a certain request can upload attachment(s) tothe request. Account manager can assign multiple tasks to several users (Senior Account Executive –Account Executive – Media Monitor) for a selected request. The tasks are based on a requestmade for a client managed by the account manager.Primary Actor Logged in POD Account Manager UserPost Condition • Request updates are saved in the systemMain SuccessScenario 1. User Logs in 2. User is redirected to the home page 3. User Presses on “Requests/Services” 4. A list of requests/services is shown chronologically by week including a field that indicates the status of each request in the system. 5. User can filter the requests/services based on [Client – Request - Project] 6. User can select any request to edit it by pressing on request/service name 7. A Pop-up of “Service Request” is shown with the ability to edit its fields: o Select a Project from the drop-down menu [Not Mandatory] o Client Name o Request/Service Title o Request/Service Description o Attachment(s) [Not Mandatory] ▪ Uploader Name ▪ Date ▪ Time o Request/Service Status (Approved – Rejected – Not Seen – Important) 8. User Presses “Update” button 9. User Presses “Forward Request” button [Found next to the request in the list] o A Dropdown Menu is shown containing the account manager and the user with access to the client account o User selects a user to forward the request to o User inserts the request briefing written in the “briefing” field o User Presses “Send” Button o A confirmation message is shown to the user confirming the delivery of the task 10. User can create a new request/service in the system by pressing on “Create A New Request” button 11. A Pop-up of “Service Request” is shown with the ability to edit its fields: o Select a Project from the drop-down menu [Not Mandatory] o Client Name o Service Title o Service Description o Attachment(s) [Not Mandatory]

▪ Uploader Name ▪ Date ▪ Time o Service Status (Approved – Rejected – Not Seen – Important) 12. User presses on “Save” button 13. A message should appear to the user confirming the delivery of the service 14. Request/Service is added to the list6. Production ReportAccount manager & management level can export production reports. The reports should besorted by date (Day Number  Week Number  Month  Year) and sorted by the productionof a certain level (Account Manager(s)  Client(s)  Project(s)  Request(s)).Primary Actor Logged in POD Account Manager UserPost Condition • Notification marked as readMain Success 1. User Logs inScenario 2. User is redirected to the home page 3. User Presses on “Reporting” button 4. A list of options is popped up to the user including: o Day Number o Week Number (Start & End) [Mandatory] o Month o Year [Mandatory] 5. User then selects the production level to be shown in the report: o Account Manager o Client o Request o Project o Senior Account Executive o Account Executive o Media Monitor 6. After selecting the attributes included in the report user presses on “Export” button. 7. User selects the desired format of the report. (PDF – HTML) 8. In case of selecting “PDF” format, a PDF containing report details is downloaded to the browser. 9. In case of selecting “HTML” format, the user is redirected to an html page containing the details of the exported report.