... so that I can tell which facilities are more popular/ less popular.

Add the following to the DG, based on your project notes from the previous weeks:

• Target user profile, value proposition, and user stories: Update the target user profile and value proposition to match the project direction you have selected. Give a list of the user stories (and update/delete existing ones, if applicable), including priorities. This can include user stories considered but will not be included in the final product.
• Use cases: Give use cases (textual form) for a few representative user stories that need multiple steps to complete. e.g. Adding a tag to a person (assume the user needs to find the person first)
• Non-functional requirements: Note: Many of the given project constraints can be considered NFRs. You can add more. e.g. performance requirements, usability requirements, scalability requirements, etc.
• Glossary: Define terms that are worth recording.

Move the draft UG content into the User Guide page

Remove addressbook, tailor to new requirements.

...so that I will always keep myself updated on the latest room usage.

1. Create final UI mock up
2. update contents

Add UI mockup for intended final product into README

Set up boiler plate codes:

1. Venue
2. Booking
3. venueList
4. bookingList

Implement relevant class attributes and helper methods.

Rename classes and package names

Understand storage structure of addressbook, tailor storing process to our needs.

Adding details and suitable photos into AboutUs

Reorganize the UI so that it is easier to use

1. Target User Profile, value proposition
2. Use cases
3. Non-functional requirements
4. Glossary

filter_booking_by_date, filter_booking_by_venue and filter_booking_by_booker commands

Move the draft UG content into the User Guide page in your repository. Update the content as necessary. If a feature is not implemented in the current version, you can either omit it from the UG or mark it as 'Coming soon' (e.g., ## Archiving contacts [coming soon]).
As mentioned before, while it is more convenient for one person to update the entire UG, we recommend that each person updates their own part of the docs so that we can easily track the contribution of each member using RepoSense.

1. create_venue

1. Add team details and photos
2. Indicate different roles and responsibilities of team members

Implement command create_booking for Booking class.

Implement command delete_venue for the Venue class.

Switch the list contents when the user enters the command, the correct items are displayed.

Allow optional fields: description, tags, capacity

Implement command delete_booking for the Booking class.