[REVIEW] - Review Use Case Diagram

[basak-tepe]

📌 Review Type

• Code Review
• Pull Request (PR) Review
• Documentation Review
• Meeting Notes Review

📝 Review Summary

Review use case diagram that @simalguven and @basak-tepe updated.

🔄 Changes Made

All 4 use cases have been merged into 1 use case diagram.

🔗 Related Topic

Design

⚠️ Concerns

None

🗒️ Additional Notes

None

[koybasimuhittin]

Hey @basak-tepe and @simalguven thanks for your efforts. I've reviewed your work and made some updates.

Changes in Garden Management according to the requirements:

• Added View Garden field and related extensions, inclusions.
• Added Create Custom Task Type field which only manager can do.

Changes in Task Tracking according to the requirements:

• Removed Create Task field since its a duplicate from the garden management.
• Removed Assign Task field since it's a duplicate from the garden management.
• Removed Delete Task field since it's a duplicate from the garden management.
• Removed / Updated non action fields.

Changes in Community forum according to the requirements:

• Added View Forum Post field and related extensions, inclusions.

Changes in Weather-Based Gardening Reminders according to the requirements:

• Updated "Send Weather Alerts" to "Receive weather alerts" directed from members to action.
• Added an arrow to weather API from "Fetch Weather Data" action.

Changes in Role Based Access Control:

• Added some extensions to "View User Profile" and "View Garden".

Changes in User Management:

• Added "View User Profile" action and related extensions, inclusions.

General Changes:

• Disambiguated some arrows.
• Fixed some typos.
• Removed / Updated non action fields.

Please see the updated diagram and let me know if its ok or not. Since there are major updates, I think it needs to be reviewed again. Feel free to request edit access or further clarifications about changes made.

[basak-tepe]

Hi, thank you for your efforts. We should also incorporate the following feedback on moodle. I am aware that we did some updates, but I am pasting this here if we have any other points that still apply.

• An extending use case cannot also serve as a base use case
• Extending use cases should not be presented as types of base use cases
• User management diagram resembles a sequence diagram
• Profile update types shouldn't be included in the general use case

[basak-tepe]

I did one final update on the Use Class Diagram about the conflicts we had with extending use cases being served as base use cases. Thank you so much @koybasimuhittin. We are all set, closing this issue.