search

jundatan / pe

1 stars 0 forks source link

Storage component for DG is not correct #15

Open jundatan opened 1 year ago

jundatan commented 1 year ago

After checking the files, i noticed that the Storage for both event and contact are different. I went to dig deeper into the code and found that the diagram in DG is not logical.

image.png

The storage image does not reflect what you have in the code.

soc-se-bot commented 1 year ago

Team's Response

No details provided by team.

Items for the Tester to Verify

:question: Issue severity

Team chose [severity.Low] Originally [severity.Medium]

Reason for disagreement: Severity should be medium as there is a clearly missing component of the UML diagram. The entire storage for contact part is missing. Developers might miss that there is an entire missing storage who wishes to use or fix the contact storage which is common as storage is one of the important component of the application. As a person who also worked on storage, DG is definitely one of the places i will look at first on the design of the storage (which is very common). If the entire storage for event is missing, it is fatal and inconvenient. Hence, that is why i set the severity as medium. The team did not give any details on why they set it to low.