alperdokay/cse3063f20p1_grp20

cse3063f20p1_grp20's Issues

Requirement Analysis Document

Requirement analysis document for the first iteration is ongoing in the following link. Please check and revise the document to finalize.

https://docs.google.com/document/d/175f1GIbSwjzHl9m7UozdYp1-pNkT1CNNPlWEkITGB-c/edit

Requirement Analysis Document

• Non-functional part should be updated.
• Grammer Check.
• Add new features to Functional Features part if needed.

https://docs.google.com/document/d/1VLAbuXy85o_uV9md31iVbYiuhBOoINcEhw5nDRZO3o8/edit?usp=sharing

Design Class Diagram

Please share your comments about DCD over here so that we can have a common understanding of our current UML versions.

Evaluation Metric

Please share your calculations for evaluation metric file from here. We can check our work together by individual responses.

UML Diagram

I have some suggestions for UML class diagram which is made by Emre and Alper, here are my suggestions:

• Firstly there is a class named as ClassLabel, it is already a class there is no need for it to call as ClassLabel, just name it as Label.
  *Secondly, I think UML class diagram has too much associations. In my opinion we need to be little more flexible.
  *In class teacher recommend to have a user class (can be abstract) and have 2 subclasses one for AdminUser other for LabellingUser. Admin user can do labellings with datasets and labelling user will do it with user interface.
  *There is no need for connecting Dataset and User I think.
  *I am not sure it will be beneficial to connect label with dataset, maybe we shouldn't in order to be more flexible but I think we should definately connect instance with label since each instance has a label. We can use many to one relationship.
  *In Assignment class since we connect it with user, label and instance classes, it will be more logical to take them as objects in attributes not as with their id's. In code we can reach objects id's easily.
• Each class has a method with the same name with class if there are created for creating classes' object their name should be at least createInstance() for example to provide better understanding for the communication.

Design Sequence Diagram

We can share our own thoughts and work on DSD here in order to finalize our work on this item.

Java Code

Once we finished the DCD and DSD, we can start discussing on Java Code from here.