You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Overall you need to put more effort. You have put good effort in creating Use Cases. I have added my comments section-wise.
[2.2] This diagram appears very complicated. Consider having another diagram with sub-components instead of having a diagram for the entire UI component.
[3.1] The undo/redo feature appears as an exact replica of AB3. If you have this feature, update object names/diagrams to suit to your implementation. How do you differentiate between AB3 and this apart from refactoring?
[3.1] and Fig. 6
Once the object is deleted should not continue lifeline
[3.2] Appears incomplete. How are you going to not violate the constraint of human-editable file storage?
[3] Section 3 as a whole appears unchanged. Why have you updated it? You should explain your features along with design decisions.
[Appendix A] No change.
[Appendix 2] Is it testable? If yes, how?
Can you define easy to use, so that it is testable?
Why this is a requirement? What does it add to value proposition?
How to test this?
[Appendix E] Glossary not updated.
The text was updated successfully, but these errors were encountered:
Overall you need to put more effort. You have put good effort in creating Use Cases. I have added my comments section-wise.
[3.1] The undo/redo feature appears as an exact replica of AB3. If you have this feature, update object names/diagrams to suit to your implementation. How do you differentiate between AB3 and this apart from refactoring?
[3.1] and Fig. 6
Once the object is deleted should not continue lifeline
[3.2] Appears incomplete. How are you going to not violate the constraint of human-editable file storage?
[3] Section 3 as a whole appears unchanged. Why have you updated it? You should explain your features along with design decisions.
[Appendix A] No change.
[Appendix 2] Is it testable? If yes, how?
Can you define easy to use, so that it is testable?
Why this is a requirement? What does it add to value proposition?
How to test this?
The text was updated successfully, but these errors were encountered: