KennethTeo2002 / pe

0 stars 0 forks source link

Property name variable is crucial #6

Open KennethTeo2002 opened 2 weeks ago

KennethTeo2002 commented 2 weeks ago

image.png Real estate agents typically also require the street name, eg "Jurong west st..." or condo estate name to keep track of properties. Thus, only having the postal code makes the product less useful (as it is hard to remember these random 6 digit numbers)

nus-pe-script commented 1 week ago

Team's Response

No details provided by team.

The 'Original' Bug

[The team marked this bug as a duplicate of the following bug]

addproperty command does not allow naming of properties

Currently, addproperty only has the following data: c/POSTAL_CODE u/UNIT_NUMBER t/TYPE a/ASK b/BID

Real estate agents may want to attach property names to the property listing to help them remember what or where it is located, which would be very useful when buyers ask for properties in certain areas.


[original: nus-cs2103-AY2425S1/pe-interim#1346] [original labels: type.FeatureFlaw severity.Low]

Their Response to the 'Original' Bug

[This is the team's response to the above 'original' bug]

Thank you for your feedback! ClientGrid is a continual work in progress with many ways to continuously improve. At this juncture, we do not see adding addresses by adding property names, street names etc. as a conclusive means to identify properties because these are rather subjective as opposed to postal codes which are more objective. We have noted that your input is handled by the app gracefully by providing the requisite error message. We clarify the rationale as follows:

  1. Ensuring accuracy: Postal codes provide an objective and error-proof method to identify locations. Unlike street names, which may be prone to mistakes or omissions due to long inputs, postal codes ensure the address is precise and correct. We have understood that for property agents, precision of such details is very important lest they make the wrong decision. As fewer characters are used for postal codes, it ensures that users are less likely to make mistakes when inputting this value. Moreover, with the availability of apps like Google Maps, users can easily navigate to a location using the postal code, eliminating the risk of information loss from input errors or inconsistencies.
  2. Standardization and Simplified UI: Address names can be written in multiple formats, which may lead to inconsistencies and confusion when viewed on the UI. For example, "Blk 123, ABC St" and "123 ABC Street, Block 123" might refer to the same location but appear different to users. Using postal codes offers a standardized and uniform approach, ensuring a clean and cohesive presentation on the app.
  3. Adherence to making commands short: In lieu of making commands short so that it is friendly to CLI users who want to get things done fast, we have decided against placing an additional parameter to record such address names. We deemed it to be verbose in the presence of postal code which can give the requisite information as well, if not better.

That said, we acknowledge the importance of accommodating diverse user needs and are open to refining this feature further. We propose conducting additional surveys with real property agents to gather insights on how they prefer to input address details. Based on the feedback, we can consider adding an optional parameter for street names or other address fields in future iterations. For the current version, we believe the use of postal codes is sufficient to achieve the intended functionality of precisely adding property location while maintaining accuracy and simplicity.

Items for the Tester to Verify

:question: Issue duplicate status

Team chose to mark this issue as a duplicate of another issue (as explained in the Team's response above)

Reason for disagreement: [replace this with your explanation]


## :question: Issue response Team chose [`response.NotInScope`] - [ ] I disagree **Reason for disagreement:** [replace this with your explanation]
## :question: Issue severity Team chose [`severity.Low`] Originally [`severity.Medium`] - [ ] I disagree **Reason for disagreement:** [replace this with your explanation]