Project Description:
Purpose and scope
The aim of this Software Requirements Specification is to build a first version for a social network based upon events and activities, the difference between them being the passive or active participation of the activity logger. A strong interoperability with facebook is key requirement, as well as the geolocation (in the mobile version as well).
In the second phase, it will include targeted advertising for both mobile and non-mobile content.
Product Perspective
The product's tentative roadmap is made of the following steps:
base version – first city (events and activities),
mobile version
advertising and payment options
additional cities
additional countries
User Classes and Characteristics
The user classes to be implemented are the following:
guest
normal user
professional user
administrator
The guest is able to visualize all the website content and insert comments in the events' page.
The normal user has the same privileges as the guest, plus to create, sign as attending to events or activities and send message to the other users.
The professional user has the same privileges as the normal user, plus has the option of inserting advertising and sponsored content in some parts of the website (the latter to be implemented in the next step)
The administrator has the same privileges as the professional user, plus to delete public comments, suspend and delete user accounts (full read access to everything but private messages).
Operating Environment
The website will be running on a shared farm server in the first phase; linux platforms are to be preferred. The main interface for the first and second phase is the web browser (both for mobile and not-mobile access).
Android and/or iOS apps could be issued, but not in the first or second phase.
Design and Implementation Constraints
The solution must be scalable from the following points of view:
city
type of event/activities
number of event/activities
number of users
language
Documentation
A functional specification document must be provided as answer to this SRS; after the implementation, the document must be updated reflecting the 100% of the functionalities.
Popup messages could be used to suggest the users which actions are available, as a form of “light documentation”.
System Features :
3.1 Registered user profile
3.2 Registration/authentication
3.3 Interaction between users
3.4 Event
3.4.1 Add an event
3.4.2 Display event
3.4.3 Event interaction
3.4.4 Referral system
3.5 Activity
3.5.1 Adding an activity
3.5.2 Visualizing activities
3.5.3 Sharing activities
3.6 Feedback
Bidders will be provided the detailed Software Requirements Specification.
