We want the user class to represent a user or a contact. Furthermore we want to keep the user/contact separated from the block.
Actual behavior
This was not the case in our old codes, block objects were intertwined with the user objects. This makes it difficult for the overview and the debugging of the software.
Steps to reproduce this behavior
Refactor according to UML.
First step is to create the User class and this is the ticket for it.
Definition of Done
Class is made and test coverage >80%
The User class should be implemented according to this image below
Member responsible: Luat
Duration: 3h
Priority: Must
Claimed by: Luat
Expected behavior
We want the user class to represent a user or a contact. Furthermore we want to keep the user/contact separated from the block.
Actual behavior
This was not the case in our old codes, block objects were intertwined with the user objects. This makes it difficult for the overview and the debugging of the software.
Steps to reproduce this behavior
Refactor according to UML. First step is to create the User class and this is the ticket for it.
Definition of Done
Class is made and test coverage >80% The User class should be implemented according to this image below
Member responsible: Luat Duration: 3h Priority: Must Claimed by: Luat