-
Notifications
You must be signed in to change notification settings - Fork 6
Requirements Specification
-
Account: A set of application related information individually for each person.
-
Admin: A person who is responsible for the management and sustainability of the system.
-
Admin panel: The interface admin uses to interact with the system.
-
Annotation: Explanatory content attached to an item.
-
Attendee: Number of users that have marked the event as "will attend".
-
Attendence information: Information of a user about attendence to an event. It can be "will attend", "may attend", "won't attend", "attended" or "didn't attend".
-
Application: The whole project as seen by guests, members and users.
-
Comment: A body of text, image or links shared in response to a post by a user.
-
Database: An organized collection of data.
-
Event: An organization that has a certain place, attendance information and a specific time.
-
Friend: A user that is followed by the original user.
-
Guest: A person who is not signed in to the system.
-
Interface: The visual part of the system.
-
Localization: Multilingual Support of the Platform
-
Location: Place that an event will be organized or a place around the user.
-
Member: A person who is signed up to the system.
-
Mobile application: Part of the application running on mobile phones, tablets etc.
-
Page: A screen view of the application which is exposed to the users or guests.
-
Password: A secret sequence of characters used by users to prove their right to enter the system.
-
Post: A body of text, image, event or links shared by a user.
-
Preferences: The choices a user made about which kind of events he/she might be interested in.
-
Profile: A number of specific information about the user including all the posts shared by that user.
-
Recommendation: Suggesting to a user some events to participate or users to follow.
-
Semantic search: Search algorithm which finds similar users and events based on the context information provided in the tags.
-
Sign in: Member's process of entering the application.
-
Sign up: Creating an account to be a member of the application.
-
System: The whole project, including design and functionalities.
-
Tag: A keyword that categorizes an event.
-
User: A person who is signed in to the system.
-
Username: A unique sequence of characters used to identify a user.
-
Vote: Users' rating on events, other users or other users' comments. Rating means number of followers for users, number of likes for events and comments. Comments and events can also be disliked.
-
1.1.1. Sign Up
- 1.1.1.1. Users shall be able to sign up by providing an appropriate password, an e-mail address, a name and a surname.
- 1.1.1.2. Users shall be able to sign up via their Facebook account.
- 1.1.1.3. Users should be able to select a unique username on sign-in.
-
1.1.2. Sign In
- 1.1.2.1. Users shall be able to sign in by their e-mail and password combination.
- 1.1.2.2. Users shall be able to sign in via their Facebook account.
- 1.1.2.3. Users shall have an option to reset their password.
-
1.1.3. Profile
- 1.1.3.1. Users shall be able to state their activity interests at any time.
- 1.1.3.2. Users should be able to state their personal information (date of birth, nationality).
- 1.1.3.3. Users should be able to select whether they will share their event history with non-friend or not.
- 1.1.3.4. Users should be able to select whether they want to take automatic recommendation or not.
- 1.1.3.5. Users should be able to select whether they want to take automatic emails for the notification
-
1.2.1. Communication
- 1.2.1.1. Users shall be able to follow each other.
- 1.2.1.2. Users shall be able to send message to each other.
-
1.2.2. Activity
- 1.2.2.1. Users and guests shall be able to see users' actions. [needs specification]
- 1.2.2.2. Users shall be able to share their experience to each other. [needs check]
- 1.2.2.3. Users shall be able to share events to each other. [needs check]
-
1.3.1. Creation
- 1.3.1.1. Users shall be able to create/edit pages for already passed and future events by providing the performing artist(s), venue (location), date and price of the event.
- 1.3.1.2. Users shall be able to add additional information by providing semantic tags.
-
1.3.2. Interaction
- 1.3.2.1. Users and guests shall be able to view any created events.
- 1.3.2.2. Users shall be able to state whether they attended to a passed event and, whether they will, they may or won't attend for a future event.
-
1.4.1. User Ratings
- 1.4.1.1. Users shall be able to vote on each other.
-
1.4.1.2. Users shall be able to comment on each other.
- 1.4.1.2.1. Users shall be able to vote on the comments on users.
-
1.4.2. Event Ratings
- 1.4.2.1. Users shall be able to vote on events.
-
1.4.2.2. Users shall be able to comment on events.
- 1.4.2.2.1. Users shall be able to vote on the comments on events.
-
1.5.1. User Searching
- 1.5.1.1. Users shall be able to search other users.
- 1.5.1.2. Users shall be able to search similar users by providing semantic tags to utilize semantic search.
-
1.5.2. Event Searching
- 1.5.2.1. Users shall be able to search events.
- 1.5.2.2. Users shall be able to search similar events by providing semantic tags to utilize semantic search.
- 1.5.2.3. Users shall be able to search events in a specific location.
-
1.6.1. Event Recommendation
- 1.6.1.1. Users shall be able to get recommendations based on their event history, user they follow and their activity interests.
-
1.7.1. Event Annotation
- 1.7.1.1. Users shall be able to annotate event information with text, link or location information.
- 1.7.1.2. Users shall be able to annotate part of the event multimedia with text, link or location information.