uskudarli / bounswe2015group1

Automatically exported from code.google.com/p/bounswe2015group1
0 stars 0 forks source link

HW1-4 Feedback #29

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
HW 1

Google Code homepage should have links to all the wiki documents you created in 
an hierarchical fashion.
Google Code homepage should have links to the personal pages (preferably at the 
bottom of the page).
Find a name for your project!
Who is furiouscolorlessgreenidea? (Is he Mustafa?)
I would appreciate if you could add a photo to your personal pages (for those 
who haven’t added already).

HW 2

Overall nicely done!
I could not spot Arda Çınar in any of the issues. (Also for Şevket but I 
believe he won’t be participating in the course work)
Some of the related issues have the estimated and actual job time missing.

HW 3

User Stories:
Nicely done!

Domain Analysis:
Information about the environment is missing but otherwise nicely done.

Requirements
Individual requirements should also have numbers, so that we can reference them 
easily (e.g., 1.1.1.2. Valid username…)
In many requirements, wording does not follow the 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.
Requirement 1.1.4.2: Are you sure you understand what a semantic tag is and how 
they can be used for semantic search? Semantic search should also return 
content with semantically related tags. For instance, searching for the tag 
cappuccino should also bring content with the coffee tag. You must also add 
some requirements for allowing the users to supply such semantic relations 
(semantic tagging).
Requirement 1.1.6.2: What about creating content?
Requirement 1.2.2.1: I think the nutrition values should not be stored in tags, 
they must be held in a separate data structure.
Requirement 1.2.2.2: More details about recommendations are needed. How are 
they presented to the users? In the search results or in the user profile page?
Requirement 1.2.3.2: How is an abusive action detected?
Requirements about tracking the diet and the nutritional intake of the users 
are needed.
About non-functional requirements: As we have talked in the PS, these 
requirements must be quantifiable and measurable.
Please add tag and semantic tag definitions to the dictionary.

Original issue reported on code.google.com by cantu...@gmail.com on 22 Mar 2015 at 4:06

GoogleCodeExporter commented 9 years ago
Also you must switch my role (Can Tunca) from collaborator to owner, so that I 
can edit the other fields (like cc, owner, type) of the issues I create.

Original comment by cantu...@gmail.com on 22 Mar 2015 at 4:11

GoogleCodeExporter commented 9 years ago

Original comment by caglabal...@gmail.com on 29 Mar 2015 at 2:21