Requirements

#Glossary System: The software project that we are developing. User: A person that uses this system. Member: A user that is registered to the system. Guest User: A user that is not registered to the system.
#: Entering the system as a member with a correct username or e-mail address and a password. #: Registering the system as a member by providing an unregistered e-mail address and a proper password with 6-127 characters.
Topic: A subject that you talk or write about. Topics and their relations are shown in graph.
Post: Writings about a specific topic. Posts can include media.
Comment: Adding an opinion related to a specific post. Rate: Judging the quality of topics, posts, comments and relations between topics / posts. Relation: A connection between two topics.
Profile Page: Section that includes a user's personal information, profile picture and his\her activity in system. Emotion: An option for expressing thoughts to a post in a given set of feelings.
Trending: Topics that have contributions most often on website or application at a particular time.
Creating Topic: Adding a new topic to system.
Contribution : Everything that users produce and add to application such as topic, post or comment.
Notification : Information alerts for new posts that added to topics that are in favorites by user or new comments that are entered to a post that is posted by user.
Summary : A post that generally explains the topic and take some parts of others posts and summarize them.
Following: The user that you want to follow his/her activities.
Favorite: The post that you like.
Activity: Any contribution of a user or rating, adding relation, following a user.
Tag:.
Semantic Tag :

REQUIREMENTS

1 FUNCTIONAL REQUIREMENTS

1.1 #-Up

  1.1.1 The system shall let guest users register with an unique username, an e-mail and a proper password.
  1.1.2 The system shall let member # providing her\his correct e-mail and password.				
  1.1.3 The system shall let member have an option to reset password in case of that s/he forgets her/his password.

1.2 Rating

  1.2.1. Members shall be able to rate any posts and comments.					
    1.2.1.1. Members and guests shall be able to see rating of any post.		
  1.2.2. Members shall be able to rate relationships.					
  1.2.3. Members shall be able to select one of emotion in a given list in order to express his/her feelings.			

1.3 Topics

   1.3.1. The system shall let member create a topic.					
     1.3.1.1. The system shall let member approve the topic before they are posted. 	
     1.3.1.2. The system shall not allow a creation of a topic with same title.			
   1.3.2. The system shall let registered user relate a topic to earlier topics with relationship.	
   1.3.3. The system shall let registered user add tags to her/his topics.			

1.4 Posts

   1.4.1. The system shall let member create a post under a topic.				
     1.4.1.1. A registered user shall be able to add a media to the post.			
     1.4.4.2. A registered user shall be able to add tags to his/her post.
   1.4.2. The system shall let registered user add tags to posts.

1.5 Comment

   1.5.1. The system shall let members add their comments to any posts.			
     1.5.1.1. The system shall show comments according to written time.				
     1.5.1.2. The system shall not allow registered user comment to closed post.			
   1.5.2. A member shall be able to vote for a comment.

1.6 Search Topics And Users

   1.6.1. The system shall provide a searching algorithm.					
     1.6.1.1. Searching algorithm should be able to process according to the topics.					
     1.6.1.2. Searching algorithm should be able to process according to the users.					
     1.6.1.3. Searching algorithm should be able to process according to the content of the topics.					
     1.6.1.4. Searching algorithm should be accessible for both guests and users.					
     1.6.1.5. Searching algorithm should show the results according to similarity such as if bmw is searced, mercedes should be shown above dogs. 
     1.6.1.6. Searching algorithm should be able to sort result according to date, rate or popularity.
   1.6.2. The system shall suggest related topics according to the query if searched words are not found.					
   1.6.3. The system shall record the searches that have done by users.					
   1.6.4. The system shall show the search results with filters.					
     1.6.4.1. The system shall provide filtering according to update date of topics. 					
     1.6.4.2. The system shall provide filtering from the most related to least related.	 

1.7 Profile Page

   1.7.1. A member shall have a profile page.					
     1.7.1.1. A member shall have a profile picture in his/her profile page.				
     1.7.1.2. A member shall be able to change his/her profile information except the username.				
   1.7.2. A member shall be able to see his/her activity history such as his/her past topics, posts and comments.	
   1.7.3. Any user shall be able to see members’ profile pages.
   1.7.4. A member shall be able to follow any people.
     1.7.4.1. A member shall be able to see followers in his/her profile page.

1.8 Visualization

   1.8.1. The application should look like a great graph which related topics and posts are connected with strings.
     1.8.1.1 Topics and posts should look like a giant dot, unless clicking on it.	
     1.8.1.2 If a user clicks on a topic, the system shall show its related posts as a giant dot.	
     1.8.1.3 If a user clicks on a post, the system shall show its comments line by line.
     1.8.1.4 If a user clicks on a string, the system shall show all relationships between two posts/topics.
     1.8.1.5 Each relation should be in different HEX color depending on relation type.	
     1.8.1.6 Relations can be unidirectional or bi-directional.	
     1.8.1.7 There can be many relations between two topic/content. The system shows the relation with high rating.		
   1.8.2. Contributor, rating and emotions of a post should be connected to post with strings.				

1.9 Semantic Tag Content

   1.9.1 The system shall semantically tag the contents.    
     1.9.1.1 The system shall use a semantic tagging engine to add semantic tags to contents.				
   1.9.2 The system shall relate the contents, having common semantic tags, in the database.

1.10 Tag Content

   1.10.1 The system shall let users add tags to posts.
     1.10.1.1 The system shall let owner of a post tag the post.
     1.10.1.2 The system shall let users reading post tag the post.
   1.10.2 The system shall recommend tags to the users who want to tag a content.
   1.10.3 The system shall let members add tags to topics.

1.11 Subject Tracking

   1.11.1 The system shall keep the contents in subjects.
     1.11.1.1 The system shall collect contents corresponding the same subject in a group.
     1.11.1.2 The system shall let a content being in different subjects.
   1.11.2 The system shall keep information about statistics about subjects.
   1.11.3 The system shall let creator of a subject see statistics about the subject.

1.12 Relationships

   1.12.1 The system shall be able to add a relation among topics.
      1.12.1.1 Relations can be unidirectional or bi-directional.	
      1.12.1.2 There can be many relations between two topic.
   1.12.4 Members shall be able to rate relationships.

##2. NONFUNCTIONAL REQUIREMENTS ###2.1. Security

   2.1.1 Information of users shall not be shared with any person or third party companies.
   2.1.2 Password of users shall be stored as encrypted using RSA crypto system. 

###2.2. Availability

   2.2.1 The system shall be implemented as both web and Android application.
   2.2.2 The system shall be supported by latest versions of Mozilla Firefox, Google Chrome, Internet Explorer and Safari and it will be responsive. 

###2.3. Languages

   2.3.1 Default language of the system shall be English 
   2.3.2 The system shall provide a language selection section to user.

###2.4. Usability

   2.4.1 The system shall provide a well-structured user manual for newcomers.
   2.4.2 The system shall have an interface in which the system elements within the system including human elements interact with each other easily according to **IEEE 9.4.7**