Requirements Feedback - Githubissues

In a lot of places in the document, wording does not follow requirements 
conventions. You should only use the shall or should keywords in the following 
convention:

- Shall is used to indicate a requirement that is contractually binding, 
meaning it must be implemented, and its implementation verified.  

- Should is used to indicate a goal which must be addressed by the design but 
is not formally verified.

- Should or shall be able to: Functions that the user performs if he wishes. 
Like he/she shall be able to login but he/she shall login if he wants to submit 
content.

2.2.3.2 Applications shall have a simple user interface to maintain ease of 
using. (A good standard is to refer to and use established design guidelines. 
All requirements need to be verifiable. Having to verify “Simple User 
Interface” would be troublesome)

No mention of semantic searching. i.e. return results on earthquakes when I 
search natural disaster. Searching by tags does not provide that. 

No mention of a recommendation system. The system should display the user 
meaningful content. You should have an algorithm choosing what to display. When 
you have 10k + entries, you can’t list them all on the homepage.

On reorganizing content, also focus on reorganizing the organization of posts 
and their relations. You will be semantically connecting items. Think of all 
possible relations users may wish to allow not just similarity (causality etc)

Original issue reported on code.google.com by alpkindi...@gmail.com on 16 Mar 2015 at 9:25

mtozsahin / bounswe2015group5

Requirements Feedback #62