EffiTrack Developer Guide

---

Acknowledgements

This project is based on the AddressBook-Level3 project created by the SE-EDU initiative. Redo, undo and history commands are adapted from AddressBook-Level4 project.

---

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 EffiTrack 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.addressbook.commons package.

---

Implementation

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

[Implemented] Undo/redo feature

Current Implementation

The implemented 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}

[Implemented] Assign task feature

Current Implementation

The implemented assign task mechanism is facilitated by AddressBook.

• AddressBook#UniquePersonList: Represents the list of persons stored in the address book.
• AddressBook#UniqueTaskList: Represents the list of tasks assigned within the address book.

Given below is an example usage scenario and how the assign task features works.

1. Ui

   • The user executes the command assign task/Proposal by/20-05-2024 2359 to/2 to assign a task named "Proposal" with a specified deadline to the 2nd person in the address book.

2. Parser

   • The input command is parsed by the AddressBookParser component.
   • The assign command keyword triggers the AssignTaskCommandParser to extract task details (name, deadline) and the index of the person to assign the task to.
   • By parsing in AssignTaskCommandParser, a Task object is created to encapsulate the task details and returns an AssignTaskCommand object representing the command to assign the task.

3. Logic execution

   • The Command object - AssignTaskCommand is executed in the LogicManager.
   • The AssignTaskCommand invokes the assignTask method in the Model component.

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

3. Model operation
   • The model#assignTask internally triggers the AddressBook#assignTask to:
     • a. The Task is added to the UniqueTaskList in the address book.
     • b. Set the person in charge of the Task to the identified person.
     • c. Set the Person's task to the specified task.

The following sequence diagram shows how an assign task operation goes through the Model component:

Design considerations:

Aspect: How assign task executes:

• Alternative 1 (current choice): Saves all tasks in an additional task list.

  • Pros: Provides a centralized task management system independent, making it easier to track and manage tasks across different persons..
  • Cons: Each task need to store additional information, such as the person in charge, leading to redundancy if not managed efficiently.

• Alternative 2: Add task list as a field for each person.

  • Pros: Easy to implement.
  • Cons: Increases complexity in managing and updating task lists, especially in scenarios involving task delegation or reassignment.

[Proposed] Efficiency Leaderboard

HR will be able to view the top performing staff on a leaderboard

Proposed Implementation

1. List of unique people will be fetched and sorted based on efficiency
2. Top 3/5/10 performing people will be showcased on the leaderboard

---

Documentation, logging, testing, configuration, dev-ops

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

---

Appendix: Requirements

Product scope

Target user profile:

• has a need to manage all the employees in company.
• can assign tasks to employees.
• has a need to check employees' efficiency.
• can generate a fire list to cut company costs.
• prefers smooth and eye-catching GUI.
• prefers typing to mouse interactions.
• is reasonably comfortable using CLI apps.

Value proposition: EffiTrack simplifies the task of measuring and monitoring employee efficiency for HR departments.
Instead of using time-consuming and error-prone methods like manual documentation or outdated systems, EffiTrack offers a centralized platform for easy and accurate monitoring of employee performance.

User stories

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

Use cases

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

Use case: Delete a person

MSS

1. User requests to list persons

2. AddressBook shows a list of persons

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

4. AddressBook deletes the person

   Use case ends.

Extensions

• 2a. The list is empty.

  Use case ends.

• 3a. The given index is invalid.

  • 3a1. AddressBook shows an error message.

    Use case resumes at step 2.

Use case: Editing a person

MSS

1. User requests to list persons

2. AddressBook shows a list of persons

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

4. AddressBook edits the person

   Use case ends.

Extensions

• 2a. The list is empty.

  Use case ends.

• 3a. The given index is invalid.

  • 3a1. AddressBook shows an error message.

    Use case resumes at step 2.

• 3b. The necessary edits are missing

  • 3b1AddressBook shows an error message.

    Use case resumes at step 2

Use case: Change deadline of a task

MSS

1. User requests to list tasks

2. AddressBook shows a list of tasks

3. User requests to edit a specific task in the list with a new deadline

4. AddressBook edits the task

   Use case ends.

Extensions

• 2a. The list is empty.

  Use case ends.

• 3a. The given index is invalid.

  • 3a1. AddressBook shows an error message.

    Use case resumes at step 2.

• 3b. The new deadline is missing.

  • 3b1. AddressBook shows an error message.

    Use case resumes at step 2.

• 3c. The new deadline is before the current date.

  • 3c1. AddressBook shows an error message.

    • Use case resumes at step 2.

• 3d. The given index does not have a task assigned.

  • 3d1. AddressBook shows an error message

    • Use case resumes at step 2.

Use case: Assign a task

MSS

1. User requests to list tasks

2. AddressBook shows a list of tasks

3. User requests to list persons

4. AddressBook shows a list of people

5. User requests to assign a task to a person

6. AddressBook assigns the task to the person

   Use case ends.

Extensions

• 2a. The list is empty.

  Use case ends.

• 4a. The list is empty.

  Use case ends.

• 5a. The given index is invalid.

  • 5a1. AddressBook shows an error message.

    Use case resumes at step 4.

• 5b. The person already has a task.

  • 5b1 AddressBook shows an error message.

    Use case resumes at step 4.

Use case: Set priority tag for a task

MSS

1. User requests to list tasks

2. AddressBook shows a list of tasks

3. User requests tag a task with a priority status

4. AddressBook tags the task

   Use case ends.

Extensions

• 2a. The list is empty.

  Use case ends.

• 3a. The given index is invalid.

  • 3a1. AddressBook shows an error message.

    Use case resumes at step 2

• 3b. The given index is invalid.

  • 3b1. AddressBook shows an error message.

    Use case resumes at step 2

Non-Functional Requirements

1. Should work on any mainstream OS as long as it has Java 11 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.
4. The respond time for any action should be less than 5 seconds.
5. The app should have an uptime of at least 99.5%, ensuring data accessibility for managers.
6. There should be at most 2 hours of downtime in a day for maintenance or updates.
7. The app should efficiently store and manage data for at least 10 years of employee history.
8. There should be a daily scheduled backup of the app's data.
9. The app should allow data export in at least three common formats like CSV, XLSX and PDF.

{More to be added}

Glossary

• Efficiency: The employee's default efficiency score is 80% and capped at 100%. Efficiency will increase by 1% when the employee completes an assigned task within the deadline and decrease by 1% for each subsequent day the deadline is exceeded.
• Efficiency Threshold: A user-defined benchmark in the app, classifying employee performance. For instance, a threshold below 20% indicates poor performance (colour coded in red), while 21-79% suggests problematic performance requiring attention (colour coded in yellow).
• Fire list: List of employees who are below the efficiency threshold.
• Key Performance Indicators (KPIs): Quantifiable measures used to evaluate the success of an employee or a department in achieving specific objectives.
• Duplicate Person: Person of the same name.
• Dupicate Task: Task of the same task title.

---

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 …​ }

---

Appendix: Planned Enhancements

Team size: 5

1. Handle extreme inputs for name, address, department, tags, email, comment (e.g., a person name with 1000 characters, an index that exceeds the range of int). For this version the text will be truncated or not fully shown as handling extreme input is considered as a nice to have feature, which will be implemented in the future version.
2. Simplify mark task command by only taking in index of the person in charge (e.g., mark 1)
3. Fix collapsed task card when a new task is assigned.