Build a web site and web server for a photo/video sharing service

[Formated .docx file attached] 1. Description a. The service The system should be able to allow owners of special events (like, for example, a birthday party) and his/her guests to exchange photos and videos (content) of the event with the event owner. If the owner desires, he can share the pool of contents he received with his guests and other people too. Content of the event will be shared by the guests with the owner using a mobile application (not included in this scope). b. Short description A web page and a web server to run a photos and videos (content) sharing service. c. Long description A couple of web pages, some with authorization and authentication capabilities, and a web server with a secure API to run a photos and videos (content) sharing service. The system should allow owners of special events to create events and invite his guests to share the photos and videos they will probably do during the event with him. The owner of the event has total control over the content that was shared with him, such that he may decide to keep the content only to himself or to share it with other users of the system. The web server requires a secure API to exchange data (photos and videos) with a mobile application which will be created for the service but that is not included in this work scope. Content uploaded to the server should remain stored until a system administrator decides to delete it. d. Actors descriptions i. Users: those who have registered to the system; related to an event, they can be an: 1. Event owner (EO): this is a user of the service that have created his own event on the system; 2. Event guests (EG): these are the users of the service that have been invited by the EOs to their events; 3. Event readers (ER): these are the users that have been granted access to an event’s content by its owner; ii. System administrator (SA); iii. Not an user (NU): this is a person that entered the web site but haven’t registered to it yet; P.S.: a user can be both an event owner, an event reader or an event guest, depending on the event (if he have created it, if the event content was shared with him or if he was invited to one). [much more details on the attached .docx file]