LittleLogBook Developer Guide

---

Acknowledgements

No third party libraries were used in the development of LittleLogBook

---

Setting up, getting started

Refer to the guide Setting up and getting started.

---

Design

Architecture

The Architecture Diagram given above explains the high-level design of the App.

Given below is a quick overview of main components and how they interact with each other.

Main components of the architecture

Main (consisting of classes Main and MainApp) is in charge of the app launch and shut down.

• At app launch, it initializes the other components in the correct sequence, and connects them up with each other.
• At shut down, it shuts down the other components and invokes cleanup methods where necessary.

The bulk of the app's work is done by the following four components:

• UI: The UI of the App.
• Logic: The command executor.
• Model: Holds the data of the App in memory.
• Storage: Reads data from, and writes data to, the hard disk.

Commons represents a collection of classes used by multiple other components.

How the architecture components interact with each other

The Sequence Diagram below shows how the components interact with each other for the scenario where the user issues the command delete 1.

Each of the four main components (also shown in the diagram above),

• defines its API in an interface with the same name as the Component.
• implements its functionality using a concrete {Component Name}Manager class (which follows the corresponding API interface mentioned in the previous point.

For example, the Logic component defines its API in the Logic.java interface and implements its functionality using the LogicManager.java class which follows the Logic interface. Other components interact with a given component through its interface rather than the concrete class (reason: to prevent outside component's being coupled to the implementation of a component), as illustrated in the (partial) class diagram below.

The sections below give more details of each component.

UI component

The API of this component is specified in Ui.java

The UI consists of a MainWindow that is made up of parts e.g.CommandBox, ResultDisplay, PersonListPanel, StatusBarFooter etc. All these, including the MainWindow, inherit from the abstract UiPart class which captures the commonalities between classes that represent parts of the visible GUI.

The UI component uses the JavaFx UI framework. The layout of these UI parts are defined in matching .fxml files that are in the src/main/resources/view folder. For example, the layout of the MainWindow is specified in MainWindow.fxml

The UI component,

• executes user commands using the Logic component.
• listens for changes to Model data so that the UI can be updated with the modified data.
• keeps a reference to the Logic component, because the UI relies on the Logic to execute commands.
• depends on some classes in the Model component, as it displays Person object residing in the Model.

Logic component

API : Logic.java

Here's a (partial) class diagram of the Logic component:

The sequence diagram below illustrates the interactions within the Logic component, taking execute("delete 1") API call as an example.

How the Logic component works:

1. When Logic is called upon to execute a command, it is passed to an AddressBookParser object which in turn creates a parser that matches the command (e.g., DeleteCommandParser) and uses it to parse the command.
2. This results in a Command object (more precisely, an object of one of its subclasses e.g., DeleteCommand) which is executed by the LogicManager.
3. The command can communicate with the Model when it is executed (e.g. to delete a person).
   Note that although this is shown as a single step in the diagram above (for simplicity), in the code it can take several interactions (between the command object and the Model) to achieve.
4. The result of the command execution is encapsulated as a CommandResult object which is returned back from Logic.

Here are the other classes in Logic (omitted from the class diagram above) that are used for parsing a user command:

How the parsing works:

• When called upon to parse a user command, the AddressBookParser class creates an XYZCommandParser (XYZ is a placeholder for the specific command name e.g., AddCommandParser) which uses the other classes shown above to parse the user command and create a XYZCommand object (e.g., AddCommand) which the AddressBookParser returns back as a Command object.
• All XYZCommandParser classes (e.g., AddCommandParser, DeleteCommandParser, ...) inherit from the Parser interface so that they can be treated similarly where possible e.g, during testing.

Model component

API : Model.java

The Model component,

• stores the address book data i.e., all Person objects (which are contained in a UniquePersonList object).
• stores the currently 'selected' Person objects (e.g., results of a search query) as a separate filtered list which is exposed to outsiders as an unmodifiable ObservableList<Person> that can be 'observed' e.g. the UI can be bound to this list so that the UI automatically updates when the data in the list change.
• stores a UserPref object that represents the user’s preferences. This is exposed to the outside as a ReadOnlyUserPref objects.
• does not depend on any of the other three components (as the Model represents data entities of the domain, they should make sense on their own without depending on other components)

Storage component

API : Storage.java

The Storage component,

• can save both address book data and user preference data in JSON format, and read them back into corresponding objects.
• inherits from both AddressBookStorage and UserPrefStorage, which means it can be treated as either one (if only the functionality of only one is needed).
• depends on some classes in the Model component (because the Storage component's job is to save/retrieve objects that belong to the Model)

Common classes

Classes used by multiple components are in the seedu.address.commons package.

---

Implementation

This section describes some noteworthy details on how certain features are implemented.

View Command

Implementation

The view command displays detailed information about a specific person in a pop-up window.

Operation: view INDEX

How it works:

1. User Input Parsing:

   • User enters a view command (e.g., "view 1")
   • AddressBookParser identifies it as a view command and delegates to ViewCommandParser
   • ViewCommandParser extracts and validates the index format

2. Index Validation:

   • Validates that the index is a positive integer
   • Checks that the index is within bounds of the current filtered person list using Model#getFilteredPersonList()

3. Command Creation:

   • Creates a ViewCommand object with the validated target index

4. Command Execution:

   • When executed, the command retrieves the corresponding person from the filtered list using the stored index
   • Opens a pop-up window (ViewWindow) displaying all the person's details
   • The main window remains fully accessible while the view window is open (non-modal)

Design Rationale

The view command was implemented as a separate window to fulfill the requirement of displaying all of a contact's fields simultaneously, which was not feasible within the constrained rows of the main contact list. This design offers a clean separation between the high-level list view and the detailed single-contact view.

A key design constraint was managing application stability and data consistency. To prevent potential performance issues or system resource exhaustion, the application is restricted to having only one ViewWindow open at any time. Attempting to open a second view window will replace the existing contact with the new contact.

Furthermore, to ensure that the UI never displays outdated information, the view window is automatically closed upon the execution of any other command that modifies the model or the viewed state (e.g. edit, delete). This guarantees that if a user views a contact, then edits another, the view window will close, preventing a scenario where it shows details that may no longer be accurate or where the indexed person in the list has changed.

Overall Sequence Diagram for View:

Below is the more in depth breakdown of the Logic and UI Sequence diagrams.

Remind Command

Implementation

The remind command shows current and upcoming birthdays.

Operation: remind

How it works:

1. User launch the program
2. Remind command is automatically called
3. Get list of persons whose birthdays is today or in the upcoming 7 days
4. Displays a list of upcoming events/birthdays
5. Can show both students and colleagues with upcoming dates

Sequence Diagram for Automated Remind on start:

Key Classes:

• RemindCommand - Handles the command execution
• Birthday - Contains date logic for reminder calculations
• Person - Stores birthday information

Validation for Birthday:

• The Birthday class implements comprehensive date validation with the following constraints:
• Format Validation
  • Required Format: dd-MM-yyyy (e.g., 24-12-2005)
  • Regex Pattern: ^\d{2}-\d{2}-\d{4}$ ensures exactly 2 digits for day, 2 for month, and 4 for year
  • Strict Parsing: Uses ResolverStyle.STRICT to reject invalid dates like 31-04-2023 (April has only 30 days)
• Temporal Constraints
  • Minimum Date: 01-01-1900 - Prevents unrealistically old birth dates
  • Maximum Date: Current date - Prevents future birth dates
  • Range Validation: Ensures birthday falls between January 1, 1900 and today
• Student's age must be either 3, 4, 5 or 6 years old. (by Singapore Education requirements)
• Colleague's age must be above 18 years old. (Of working age)

Overall Sequence Diagram for Remind:

Below is the more in depth breakdown of the Logic, Model and UI Sequence diagrams.

Future improvement:

• Students that are currently 6 years old would be 7 years old next year and would be invalid in the system
• Possibly remind the teacher to remove the graduated students

---

Documentation, logging, testing, configuration, dev-ops

• Documentation guide
• Testing guide
• Logging guide
• Configuration guide
• DevOps guide

---

Appendix: Requirements

Product scope

Target user profile: Kindergarten Teacher

• an avid user of typed user commands interface
• prefer desktop apps over other types
• has multiple classes that holds multiple students
• has multiple colleagues

Value proposition: Little LogBook helps kindergarten teachers stay organised by managing student and colleague details in one place, making parent contacts quick to access and freeing up more time for teaching.

User Stories

Priority Legend

• * * * : Must-have (High priority)
• * * : Good-to-have (Medium priority)
• * : Nice-to-have (Low priority)

Use cases

Non-Functional Requirements

1. Should work on any mainstream OS as long as it has Java 17 or above installed.
2. Should be able to hold up to 1000 persons without a noticeable sluggishness in performance for typical usage.
3. A user with above average typing speed for regular English text (i.e. not code, not system admin commands) should be able to accomplish most of the tasks faster using commands than using the mouse.

Glossary

• Mainstream OS: Windows, Linux, Unix, MacOS
• Contact: A person's name, class (for student), birthday (for student), phone number's (colleague, student's parents), emails (colleague, student's parents)
• Notes: A section inside contact for additional information

---

Appendix: Instructions for manual testing

Given below are instructions to test the app manually.

Launch and shutdown

1. Initial launch
   • Download the jar file and copy into an empty folder
   • Double-click the jar file
     
   • Expected: Shows the GUI with a set of sample contacts. The window size may not be optimum.

2. Saving window preferences
   • Resize the window to an optimum size. Move the window to a different location. Close the window.
   • Re-launch the app by double-clicking the jar file.
     
   • Expected: The most recent window size and location is retained.

---

Adding contacts

Adding a valid contact

1. Adding a student contact with all fields
   • Test case: add n/John Doe p/98765432 e/john.doe@gmail.com a/123 Main Street c/K1A b/15-03-2019 t/student desc/Allergic to peanuts
   • Expected: New student contact added successfully with all specified fields.

2. Adding a colleague contact with optional note
   • Test case: add n/Mary Tan p/91234567 e/marytan@e.nut.edu a/123 Jurong West Ave 6 c/K2B b/24-12-2000 t/colleague desc/Allergic to peanuts
     
   • Expected: New colleague contact added with note.

3. Adding a colleague contact with mandatory fields only
   • Test case: add n/Marie p/98765432 e/john.doe@gmail.com a/123 Main Street c/K1A b/15-03-2000 t/colleague
   • Expected: New colleague contact added with only required fields.

4. Adding contact with different tag (same info excluding birthday year)
   • Prerequisites: Student contact "John Doe" exists (from point 1)
   • Test case: add n/John Doe p/98765432 e/john.doe@gmail.com a/123 Main Street c/K1A b/15-03-2000 t/colleague desc/Allergic to peanuts
     
   • Expected: Success - different tags allow identical info (other than birthday).

5. Some Invalid parameter formats
   • Test case: add n/John123 p/123 e/invalid-email a/ c/class b/32-13-2020 t/invalidtag
     
   • Expected: The system validates parameters sequentially and shows only the first validation error encountered. Users must fix each error one by one as they are revealed.

---

Editing contacts

Editing contact fields

1. Editing a contact's basic information
   • Prerequisites: List all persons. Note the details of contact at index 1.
   • Test case: edit 1 n/New Name p/87654321 e/new.email@school.edu
   • Expected: The command box shows the edited information, and the contact list refreshes with the updated entry.

2. Editing contact with duplicate detection
   • Prerequisites: Add 2 contacts with the same details for every field EXCEPT name. Assume they are at index x and y
   • Test case: edit x n/{y's name} (e.g., If y's name is Bob then run edit x n/Bob)
   • Expected: The command box shows a duplicate alert message. No changes are made to the contact list.

3. Editing contact with missing parameters
   • Test case: edit, edit 1 (assuming 1 is a valid index)
   • Expected: No detail is edited. Error details shown in the status message. Status bar remains the same.

4. Editing a contact with invalid parameter format
   • Test case: edit 1 p/abc, edit 1 e/not-an-email (assuming 1 is a valid index)
   • Expected: No detail is edited. Error details shown in the status message. Status bar remains the same.

---

Deleting contacts

Deleting by index and name

1. Deleting a contact by valid index
   • Prerequisites: List all persons. Multiple persons in the list.
   • Test case: delete 1
   • Expected: A confirmation popup appears. The contact is deleted upon confirmation, otherwise, the app returns to the main window. The command box shows a success or cancellation message.

2. Deleting a contact by invalid index
   • Test case: delete, delete x, ... (where x is larger than the list size)
   • Expected: No person is deleted. Error details shown in the status message. Status bar remains the same.

3. Deleting a contact by name with full name
   • Prerequisite: List all persons. Alex Yeoh is in the person list.
   • Test case: delete n/ALex Yeoh
   • Expected: If only one person has this name, a confirmation popup appears, and the contact is deleted upon confirmation. Otherwise, a popup showing multiple matches appears first, followed by a confirmation popup for the selected contact.

4. Deleting a contact by name with partial name
   • Prerequisites: List all persons. Multiple persons in the list with lex in their name.
   • Test case: delete n/lex
   • Expected: A popup shows possible matches for selection. After the user makes a selection, a confirmation popup appears.

5. Deleting a contact by name with a invalid name
   • Prerequisites: List all persons. No person in the list with random name in their name.
   • Test case: delete n/random name
   • Expected: Press Escape to cancel the deletion or Enter to return to main window.

---

Sorting contacts

Sorting by different fields

• All sort comparison is done alphabetically.

1. Sorting contacts by name
   • Test case: sort f/name
   • Expected: Contacts sorted alphabetically by name.

2. Sorting contacts by class in descending order
   • Test case: sort f/class o/desc
   • Expected: Contacts sorted by class in reverse alphabetical order.

---

Birthday reminders

Checking birthday notifications

1. Manual reminder check with birthdays today and upcoming
   • Prerequisites: At least one contact has birthday today, and at least one has birthday within next 7 days
   • Test case: remind
     
   • Expected: Shows two sections: "Happy Birthday to these people today!" and "Upcoming birthdays in the next 7 days:" with numbered lists.

2. Manual reminder with only upcoming birthdays
   • Prerequisites: No contacts have birthday today, but some have birthdays within next 7 days
   • Test case: remind
     
   • Expected: Shows "No birthdays today!" followed by "Upcoming birthdays in the next 7 days:" section.

3. Manual reminder with no upcoming birthdays
   • Prerequisites: No contacts have birthdays today or within next 7 days
   • Test case: remind
     
   • Expected: Shows "No upcoming birthdays found." message.

4. Manual reminder with empty address book
   • Prerequisites: Clear all contacts using clear command
   • Test case: remind
     
   • Expected: Shows "No contacts in LittleLogBook." message.

5. Automatic reminder on startup
   • Prerequisites: Contacts with birthdays today and/or upcoming exist
   • Action: Close and reopen the app
     
   • Expected: Birthday reminders shown automatically in the result display when app starts.

6. Reminder formatting verification
   • Prerequisites: Contacts with various birthday scenarios exist
   • Test case: remind
     
   • Expected: Each entry shows:
     • Name in correct format
     • Birthday in dd-MM-yyyy format
     • Tags in square brackets (if present)
     • "(TODAY!)" for today's birthdays
     • "(in X day(s))" for upcoming birthdays

7. Reminder with extraneous parameters
   • Test case: remind extra parameter
     
   • Expected: Command works normally (extraneous parameters ignored).

8. Cross-year birthday handling
   • Prerequisites: Test in late December with contacts having January birthdays
   • Test case: remind
     
   • Expected: Correctly shows upcoming birthdays that cross into next year.

Testing Tips for remind command:

• Use system date changes to simulate different scenarios
• Test across month and year boundaries
• Verify the "in X days" calculation is accurate
• Check that both automatic (startup) and manual execution work
• Ensure the output is helpful and actionable for kindergarten teachers

---

Note management

Adding and editing notes

1. Adding a note to a contact
   • Test case: note 1 desc/Allergic to peanuts and dairy products
   • Expected: Note successfully added to contact.

2. Removing a note from a contact
   • Test case: note 1
   • Expected: Existing note removed from contact.

---

Viewing contacts

Detailed contact viewing

1. Viewing valid contact
   • Prerequisites: Multiple contacts in list
   • Test case: view 1
     
   • Expected: Popup window shows full contact details.

2. Viewing student vs colleague
   • Test cases: view 1 (student), view 2 (colleague)
     
   • Expected: Different layouts shown (student shows attendance, colleague does not).

3. Viewing with invalid index
   • Test case: view 0
     
   • Expected: Error message about invalid index.

---

Attendance management

Marking attendance

1. Marking attendance for a single student
   • Prerequisites: Ensure contact at index 1 is a student.
   • Test case: attendance 1 s/present
   • Expected: Attendance marked successfully for current date.

2. Marking attendance for multiple students with specific date
   • Prerequisites: Ensure contact at index 1, 2, 3 is a student.
   • Test case: attendance 1,2,3 s/late d/15-03-2024
   • Expected: Attendance marked for all specified students on given date.

3. Marking attendance for multiple contacts (student and colleague)
   • Prerequisites: Ensure you have at least one student and one colleague at index 1, 2, 3.
   • Test case: attendance 1,2,3 s/late
   • Expected: Attendance marked ONLY for students.

4. Marking attendance for a colleague
   • Prerequisites: Ensure contact at index 1 is a colleague.
   • Test case: attendance 1 s/sick
   • Expected: Error message and attendance rule reminder.

5. Marking attendance with invalid date
   • Test case: attendance 1 s/present d/29-02-2023
   • Expected: Error message for invalid date.

---

Attendance reports

Downloading reports

1. Downloading individual student monthly report
   • Prerequisites: Ensure contact at index 1 is a student with attendance records.
   • Test case: attendanceD 1 m/03-2024
   • Expected: CSV report downloaded successfully.

2. Downloading multiple individual students monthly report
   • Prerequisites: Ensure contact at index 1, 2, 3 is a student with attendance records.
   • Test case: attendanceD 1-3 m/03-2024
   • Expected: CSV report downloaded successfully.

3. Downloading individual student daily report
   • Prerequisites: Ensure contact at index 1 is a student with attendance records.
   • Test case: attendanceD 1 d/01-03-2024
   • Expected: Error message. Individual report are monthly only.

4. Downloading class-based daily report
   • Test case: attendanceD c/K1A d/15-03-2024
   • Expected: Class attendance report downloaded for specified date.

5. Downloading multiple class-based daily report
   • Test case: attendanceD c/K1A c/K2B d/15-03-2024
   • Expected: Class attendance reports downloaded for specified date.

6. Downloading class-based monthly report
   • Test case: attendanceD c/K1A
   • Expected: Class attendance report downloaded for current month.

7. Downloading multiple class-based monthly report
   • Test case: attendanceD c/K1A c/K2B
   • Expected: Class attendance reports downloaded for current month.

---

Saving data

Dealing with missing/corrupted data files

1. Simulating missing data file:
   • Navigate to the data/ folder in your LittleLogBook directory
   • Delete or rename the littlelogbook.json file
   • Launch LittleLogBook
   • Expected: LittleLogBook should start with a fresh empty address book and create a new littlelogbook.json file automatically

2. Simulating corrupted data file:
   • Open the data/littlelogbook.json file in a text editor
   • Manually modify the JSON structure to be invalid, for example:
     • Remove essential fields like "name", "phone", etc. from a contact
     • Change field types (e.g., change a phone number to an array: "phone": [12345678])
     • Introduce JSON syntax errors (remove closing braces, add extra commas)
     • Add invalid date formats in birthday/attendance fields
     • Remove the entire "persons" array or make it null
   • Save the file and launch LittleLogBook
   • Expected: LittleLogBook should detect the corruption and start with an empty address book.

3. Testing with invalid birthday formats:
   • Change a contact's birthday to an invalid format (e.g., "32-13-2020", "birthday": "not-a-date")
   • Expected: LittleLogBook should detect the corruption and start with an empty address book.

---

Finding contacts

Similar process for the different find commands (find-n, find-c, find-t, find-p )

1. Simulating find for no-matches:
   • Add contacts to the LittleLogBook with no names containing z or y, no classes containing K1A
   • Input the find command with required parameter(s) to find for an information such as partial name that does not exist in your contacts
     • Test case: find-p 123456789
     • Test case: find-n zy z y
     • Test case: find-c k1A
   • Press enter
   • Expected: LittleLogBook should show empty contact list with information on how to proceed.

2. Simulating find for matches:
   • Add contacts to the LittleLogBook with class starting with K, names containing b and/or d
   • Input the find command with required parameter(s) to find for an information such as partial phone number that exists in your contacts
     • Test case: find-p 8 9
     • Test case: find-c k
     • Test case: find-n b d
     • Test case: find-t stu coll
   • Press enter
   • Expected: LittleLogBook should show filtered contact list of only those that match the input string with information on how to proceed.

3. Simulating find with no parameter inputs:
   • Input the find command with no parameter
     • Test case: find-c
   • Expected: LittleLogBook should say invalid command format and guide users on next steps.

4. Simulating find with wrong parameter inputs:
   • Input the find command
     • Example: passing in alphabetic string for find-p command
     • Test case: find-p ala
     • Test case: find-t 1
     • Test case: find-n @ !
     • Test case: find-c !
   • Press enter
   • Expected: LittleLogBook should state the valid inputs that are allowed to guide user.

---

Favourite contacts

1. Simulating adding a contact to favourites for the first time:
   • Add a new contact to a LittleLogBook
   • Input the fav command with index of newly added contact
     • Test case: fav 1 assuming added contact is the first contact
   • Press enter
   • Expected: LittleLogBook should show a successful message with the name of the added contact. There will be a star icon indicated next to that contact.

2. Simulating removing a contact from favourites:
   • Add a new contact to the LittleLogBook
   • Do the process of adding that contact to favourites (Refer to point 1 in this section)
   • Input the favourite command with index of that specific contact
     • Test case: fav 1 assuming added contact is the first contact
   • Press enter
   • Expected: LittleLogBook should show succesful message with information on the contact that is removed from favourites. The star icon next to the contact will disappear.

3. Checking list behaviour:
   • Add two new contacts to the LittleLogBook
   • Do the process of adding one of the two contacts to favourites (Refer to point 1 in this section)
     • Test case: fav 2 assuming added contacts are the first and second respectively
   • Input list command
   • Press enter
   • Expected: LittleLogBook should show those added to favourites on the top of the list

---

Edge Cases and Error Handling

1. Command case sensitivity
   • Test: ADD, Add, add
     Expected: only commands in lower case should work (case-sensitive).

2. Parameter order variations
   • Test: add t/student b/15-03-2018 c/K1A a/Blk 456, Den Road, #01-355 e/john.doe@gmail.com p/98765432 n/John Doe (reverse order)
     Expected: Should work correctly.

3. Extra spaces in commands and parameters (ONLY for n/, p/, and a/)

   • Test: add n/Johns Doe p/9876 5432 e/john.doe@gmail.com a/Blk 456, Den Road, #01-355 c/K1A b/15-03-2018 t/student
     Expected: Should handle gracefully (trim spaces).

     Note: When you copy the above command, the spaces may not appear as markbind does not allow spacings. Hence, for your testing purpose, you may add spaces to the command when you copy it into the GUI.

---

System commands

Basic system operations

1. Listing all contacts
   • Test case: list
   • Expected: All contacts displayed with favourites at top.

2. Clearing all contacts
   • Test case: clear
   • Expected: Confirmation and removal of all contacts.

3. Viewing help
   • Test case: help
   • Expected: Help window opens with link to our user guide.

4. Exiting application
   • Test case: exit
   • Expected: Application closes gracefully.

Note: These instructions provide a starting point for testers. Testers should perform additional exploratory testing beyond these specified cases, including:

• Testing concurrent operations
• Testing boundary conditions
• Testing error recovery
• Testing UI responsiveness with different data volumes

---

Appendix: Planned Enhancements

Team Size: 5

1. Edit

• Display a confirmation pop-up window when changing contact's tags: Currently, users can change tags freely from student to colleague and vice versa. However, there is a possibility that the user did not intend to do this action in the first place. Having a confirmation window will also increase user experience and prevent accidental deletion of student's attendance history (although right now, we keep attendance record even if a contact's tag was edited form student to colleague).

• Add birthday validation to edit command: Currently, the edit command accepts birthdays that would make a student younger than 3 or older than 6 years old or the colleague to be younger than 18. We will modify the edit command to apply the same age validation checks as the add command, preventing invalid birthdays from being set through editing.

  • Example: edit 1 b/01-01-2024 would show an error: "Birthday would make student 1 year old. Students must be between 3 and 6 years old."

2. Delete

• Allow bulk deletion: Currently, our delete command only accept singular index (or partial name) as the parameter. However, this would be very tedious for user who wants to delete multiple contacts at once. In the future, we plan to use the same index parsing in attendance and attendanceD to allow multiple contacts to be deleted at once (after confirmation).

3. Find

• Unified search command: Currently, we have four find-commands whereby to cumulatively filter from class to names, users must do a find-c command first and then a find-n which may be inconvenient for users to get to the contacts they want. In the future we plan to unify these find commands to allow multiple different fields such as name(s) and class(es) to be searched at once.

4. Attendance

• Change attendance report into a more readable format: Currently, attendance reports will be downloaded in CSV format which might be a little hard for some users to open (although we provide steps to take it in our User Guide). We plan to format it into a XLSX, XLS, or other format that might not require external libraries to achieve the same result.

• Limit attendance calendar range in view window: Currently, users can browse attendance records for dates far beyond the valid range (student's birth date to 6 years later, not exceeding today's date), creating confusion between viewing capability and actual marking permissions. We plan to limit calendar navigation to only display dates within the valid attendance marking range to maintain consistency between attendance marking and viewing.

5. Birthday field

• Handle age-based expiration for existing students by creating graduated students reminder system: Currently, students who are 6 years old will become invalid next year when they turn 7. We will implement an annual check that automatically flags or archives students who have reached the maximum age with a confirmation prompt for deletion. Afterward, LittleLogBook will remind the teacher to remove graduated students.
  • Example: Running the app after a year would show: "3 students have reached invalid age. Use cleanup_age to review and remove them."

6. General

• Smarter parsing for all parameter: Currently, some parameter parser like a/ADDRESS, b/BIRTHDAY, c/CLASS, and t/TAG does not accept input which has multiple spaces inside. We plan to apply the same smart parsing detection to the rest of the command to reduce error and increase user experience.
  • Example: User accidentally typed double space instead of one → should still allow the code to run if that is the only mistake.

• Enhanced duplicate action feedback: Currently, commands like note provide identical success messages for both adding/removing notes and repeated identical actions.
  • Example: When a user executes note 1 to remove a note, then runs the same command again, the system should detect there's no note to remove and provide appropriate feedback.