Under the Architecture -> How the architecture components interact with each other:
UML diagram demonstrating the scenario for when user issue the command delete-person n/Amy is not updated
The diagram specifies a method saveAddressBook() which Logic component calls Storage Component. However, the application is not an addressbook, but rather an application directed at handling module planning. Hence the Logic of this application should not involve the saving of an addressbook. The application does not handle the address of any person at all.
Bug Description:
Under the Architecture -> How the architecture components interact with each other:
UML diagram demonstrating the scenario for when user issue the command
delete-person n/Amyis not updatedThe diagram specifies a method saveAddressBook() which Logic component calls Storage Component. However, the application is not an addressbook, but rather an application directed at handling module planning. Hence the Logic of this application should not involve the saving of an addressbook. The application does not handle the address of any person at all.