AB-3 Developer Guide

---

Acknowledgements

{ list here sources of all reused/adapted ideas, code, documentation, and third-party libraries -- include links to the original source as well }

---

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.

[Proposed] Undo/redo feature

Proposed Implementation

The proposed undo/redo mechanism is facilitated by VersionedAddressBook. It extends AddressBook with an undo/redo history, stored internally as an addressBookStateList and currentStatePointer. Additionally, it implements the following operations:

• VersionedAddressBook#commit() — Saves the current address book state in its history.
• VersionedAddressBook#undo() — Restores the previous address book state from its history.
• VersionedAddressBook#redo() — Restores a previously undone address book state from its history.

These operations are exposed in the Model interface as Model#commitAddressBook(), Model#undoAddressBook() and Model#redoAddressBook() respectively.

Given below is an example usage scenario and how the undo/redo mechanism behaves at each step.

Step 1. The user launches the application for the first time. The VersionedAddressBook will be initialized with the initial address book state, and the currentStatePointer pointing to that single address book state.

Step 2. The user executes delete 5 command to delete the 5th person in the address book. The delete command calls Model#commitAddressBook(), causing the modified state of the address book after the delete 5 command executes to be saved in the addressBookStateList, and the currentStatePointer is shifted to the newly inserted address book state.

Step 3. The user executes add n/David …​ to add a new person. The add command also calls Model#commitAddressBook(), causing another modified address book state to be saved into the addressBookStateList.

Step 4. The user now decides that adding the person was a mistake, and decides to undo that action by executing the undo command. The undo command will call Model#undoAddressBook(), which will shift the currentStatePointer once to the left, pointing it to the previous address book state, and restores the address book to that state.

The following sequence diagram shows how an undo operation goes through the Logic component:

Similarly, how an undo operation goes through the Model component is shown below:

The redo command does the opposite — it calls Model#redoAddressBook(), which shifts the currentStatePointer once to the right, pointing to the previously undone state, and restores the address book to that state.

Step 5. The user then decides to execute the command list. Commands that do not modify the address book, such as list, will usually not call Model#commitAddressBook(), Model#undoAddressBook() or Model#redoAddressBook(). Thus, the addressBookStateList remains unchanged.

Step 6. The user executes clear, which calls Model#commitAddressBook(). Since the currentStatePointer is not pointing at the end of the addressBookStateList, all address book states after the currentStatePointer will be purged. Reason: It no longer makes sense to redo the add n/David …​ command. This is the behavior that most modern desktop applications follow.

The following activity diagram summarizes what happens when a user executes a new command:

Design considerations:

Aspect: How undo & redo executes:

• Alternative 1 (current choice): Saves the entire address book.

  • Pros: Easy to implement.
  • Cons: May have performance issues in terms of memory usage.

• Alternative 2: Individual command knows how to undo/redo by itself.

  • Pros: Will use less memory (e.g. for delete, just save the person being deleted).
  • Cons: We must ensure that the implementation of each individual command are correct.

{more aspects and alternatives to be added}

[Proposed] Data archiving

{Explain here how the data archiving feature will be implemented}

---

Documentation, logging, testing, configuration, dev-ops

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

---

Appendix: Requirements

Product scope

Target user profile:

Independent Insurance Agents who manage the personal portfolio of clients, contracts and insurance policies.

Value proposition:

iCon helps insurance agents manage a large pool of clients and contracts, with the flexibility to add policies from any issuer. By enabling fast, accurate retrieval of critical client and policy data, it minimizes admin overhead and let agents focus more on delivering high-quality advisory services.

User stories

Priorities: High (must have) - * * *, Medium (nice to have) - * *, Low (unlikely to have) - *

Use cases

(For all use cases below, the System is iCon and the Actor is the user, unless specified otherwise)

Use Case: UC1 - Add a person

MSS

1. User requests to add a person with all details specified

2. iCon adds the person

   Use case ends.

Extensions

• 1a. Some compulsory details are missing.

  • 1a1. iCon shows an error message.

    Use case ends.

Use case: UC2 - Delete a person

MSS

1. User requests to list persons

2. iCon shows a list of persons

3. User requests to delete a specific person in the list

4. iCon deletes the person

   Use case ends.

Extensions

• 2a. The list is empty.

  Use case ends.

• 3a. The given index is invalid.

  • 3a1. iCon shows an error message.

    Use case resumes at step 2.

Use Case: UC3 - Edit a person's details

MSS

1. User requests to list persons

2. iCon shows a list of persons

3. User requests to edit a specific person in the list

4. iCon updates the person's details

   Use case ends.

Extensions

• 2a. The list is empty.

  Use case ends.

• 3a. The given index is invalid.

  • 3a1. iCon shows an error message.

    Use case resumes at step 2.

• 4a. Some compulsory details are missing.

  • 4a1. iCon shows an error message.

    Use case resumes at step 2.

Use Case: UC4 - Find persons by name

MSS

1. User requests to find persons by name

2. iCon shows a list of persons whose names contain the given keywords

3. User requests to view details of a specific person in the list

4. iCon shows the person's details

   Use case ends.

Extensions

• 2a. No persons found.

  • 2a1. iCon shows an empty list.

    Use case ends.

Use Case: UC5 - List all persons

MSS

1. User requests to list persons

2. iCon shows a list of persons

   Use case ends.

Extensions

• 1a. The list is empty.

  • 1a1. iCon shows an empty list.

    Use case ends.

Use Case: UC6 - Clear all persons

MSS

1. User requests to clear all persons

2. iCon clears all persons

   Use case ends.

Extensions

• 1a. The list is empty.

  Use case ends.

Use Case: UC7 - Exit the App

MSS

1. User requests to exit the App

2. iCon saves all data to hard disk

3. iCon exits

   Use case ends.

Extensions

• 2a. iCon fails to save data to hard disk.

  • 2a1. iCon shows an error message.

    Use case resumes at step 3.

Use Case: UC8 - Add Policy

MSS

1. User adds policy using file path to policy file

2. iCon adds the policy

3. iCon shows a success message & generates a policy ID

   Use case ends.

Extensions

• 1a. File path is invalid

  • 1a1. iCon shows an error message.

    Use case ends.

Use case: UC9 - Remove Policy

MSS

1. User requests to list policies

2. iCon shows a list of policies

3. User requests to remove a specific policy in the list

4. iCon removes the policy

   Use case ends.

Extensions

• 2a. The list is empty.

  Use case ends.

• 3a. The given id is invalid.

  • 3a1. iCon shows an error message.

    Use case resumes at step 2.

Use Case: UC10 - View Policies

MSS

1. User requests to list policies

2. iCon shows a list of policies

3. User requests to view details of a specific policy in the list

4. iCon shows the policy's details

   Use case ends.

Extensions

• 2a. The list is empty.

  • 2a1. iCon shows an empty list.

    Use case ends.

• 3a. The given id is invalid.

  • 3a1. iCon shows an error message.

    Use case resumes at step 2.

• 3b. The policy file is missing/corrupted.

  • 3b1. iCon shows an error message.

    Use case resumes at step 2.

Use Case: UC11 - Add contract

MSS

1. User adds contract with specific details

2. iCon adds the contract

3. iCon shows a success message & generates a contract ID

   Use case ends.

Extensions

• 1a. Some compulsory details are missing.

  • 1a1. iCon shows an error message.

    Use case ends.

• 2a. The person ID is invalid.

  • 2a1. iCon shows an error message.

    Use case ends.

• 2b. The policy ID is invalid.

  • 2b1. iCon shows an error message.

    Use case ends.

• 2c. The contract is duplicate.

  • 2c1. iCon shows an error message.

    Use case ends.

Use Case: UC12 - Remove contract

MSS

1. User requests to list contracts

2. iCon shows a list of contracts

3. User requests to remove a specific contract in the list

4. iCon removes the contract

   Use case ends.

Extensions

• 2a. The list is empty.

  Use case ends.

• 3a. The given id is invalid.

  • 3a1. iCon shows an error message.

    Use case resumes at step 2.

Use Case: UC13 - View contracts

MSS

1. User requests to list contracts

2. iCon shows a list of contracts

3. User requests to view details of a specific contract in the list by id

4. iCon shows the contract's details

   Use case ends.

Extensions

• 2a. The list is empty.

  • 2a1. iCon shows an empty list.

    Use case ends.

• 3a. The given id is invalid.

  • 3a1. iCon shows an error message.

    Use case resumes at step 2.

Non-Functional Requirements

1. The system should work on any mainstream OS as long as it has Java 17 or above installed.
2. The application should be easily installable, with no additional third-party dependencies.
3. The application should function entirely offline.
4. The system should be able to hold up to 1000 persons, contracts, and policies without a noticeable sluggishness in performance for typical usage.
5. The system should respond to user input and commands within 100 milliseconds.
6. The system should manage its own copy of policies separate from the source file when adding or removing policies.
7. The save data should not take more than 100 MB in typical usage.
8. The system must save changes to the hard disk after 1 or a few user modifications and after exiting the program, to minimize data loss in the event of a crash.
9. 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
• Private contact detail: A contact detail that is not meant to be shared with others
• Contact: A customer of the insurance agent that has data fields, name, email, and NRIC
• Person(s): Another way of saying a contact
• Policy: The document that details the terms and conditions of a contract
• Contract: A contract that binds a customer to a certain policy

---

Appendix: Instructions for manual testing

Given below are instructions to test the app manually.

Launch and shutdown

1. Initial launch

   1. Download the jar file and copy into an empty folder

   2. 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

   1. Resize the window to an optimum size. Move the window to a different location. Close the window.

   2. Re-launch the app by double-clicking the jar file.
      Expected: The most recent window size and location is retained.

3. { more test cases …​ }

Deleting a person

1. Deleting a person while all persons are being shown

   1. Prerequisites: List all persons using the list command. Multiple persons in the list.

   2. Test case: delete 1
      Expected: First contact is deleted from the list. Details of the deleted contact shown in the status message. Timestamp in the status bar is updated.

   3. Test case: delete 0
      Expected: No person is deleted. Error details shown in the status message. Status bar remains the same.

   4. Other incorrect delete commands to try: delete, delete x, ... (where x is larger than the list size)
      Expected: Similar to previous.

2. { more test cases …​ }

Saving data

1. Dealing with missing/corrupted data files

   1. {explain how to simulate a missing/corrupted file, and the expected behavior}

2. { more test cases …​ }