search

nus-cs2103-AY2223S2 / forum

12 stars 0 forks source link

The reason of using the name for `ReadOnlyAddressBook` interface #291

Closed QQH0828 closed 1 year ago

QQH0828 commented 1 year ago

Hi, prof and peers, May I ask that the reason of ReadOnlyAddressBook interface is used by this name is because AddressBook is the project name or is it a name used for storing all the person's details (readability)? My teammates and I are thinking about this question, and we have different thoughts. Regarding the UML diagram below image Model -> AddressBook and UserPrefs; AddressBook -> person's details.

Some of us think we should change AddressBook to our own project name, and some of us think should keep it.

damithc commented 1 year ago

May I ask that the reason of ReadOnlyAddressBook interface is used by this name is because AddressBook is the project name or is it a name used for storing all the person's details (readability)?

@QQH0828 The classes are named based on what the class/component represents, not based on the product name. In this case it happens to match product name as well.

QQH0828 commented 1 year ago

Thanks, prof!