HW1-3 Feedback

[GoogleCodeExporter]

HW 1

Find a name for your project!
I would appreciate if you could add a photo to your personal pages (for those 
who haven’t added already).
There is a typo in the link for Levent’s personal page. (just saying… :))

HW 2

I do not see how virtual reality applications relate to your project.
The type of some of the issues are incorrect. Such research tasks are not 
actually defects.
I could not spot İsmail Enes Yılmaz and Buğrahan Şahin in any of the 
related issues.

HW 3

User Stories:
Nicely done!

Domain Analysis:
Similarities to other domains are missing.

HW 4

In the background section, it is important that you give some technical 
information about the architecture of your system. For instance, the system 
will have a web and a mobile app, it will have a client-server architecture, 
etc.
Requirements 1.2-1.7: The phrases like “groups shall let users…” are not 
always good. You must write most of the requirements from the users’ 
perspective, as you have done in section 1.1. For instance, Req. 1.2.1 may be 
revised as follows: The users shall be able to provide and edit textual 
information about a group. Req. 1.2.2 may stay as it is, since it is about a 
passive functionality, automatically maintained by the system. Moreover, the 
section titles do not necessarily denote the “who” of the requirements. For 
instance, Req. 1.1.7 may go in the section about groups (1.2).
Please add some requirements about semantic tagging, semantic search and 
recommending content to the users. These are important aspects of your system. 
Actually Req. 1.5.2. seems to be about semantic search, but you should provide 
more details on what “similar” means in the scope of you system. A little 
information about semantic search/tagging: 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).
Section 1.4: Content is a very broad term. You should find a more specific term 
instead of content.
About non-functional requirements: As we have talked in the PS, the 
non-functional requirements should be quantifiable and measurable. In this 
regard, Reqs. 2.2.1, 2.2.2, 2.3.1, 2.3.2 and 2.3.5 are problematic. Also, Req. 
2.1.1. is kind of unrealistic. Instead, you might say that the maximum time to 
recover in case of failure will be x (whatever you like) hours.

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

[GoogleCodeExporter]

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:21

[GoogleCodeExporter]

In the original issue message, I made a mistake. The items under HW 4 are 
actually about requirements. Feedback about HW 4 is coming soon.

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

[GoogleCodeExporter]

Can Tunca added to the owners.

Original comment by mertcanc...@gmail.com on 22 Mar 2015 at 8:26

• Changed state: Started