Developer Guide

About ClassMonitor

ClassMonitor is a Student Management System that empowers TAs and Professors to manage their student particulars and obtain insights about their students’ performance ratings. As a TA, you can easily view and edit your students’ particulars during your daily classes. Utilize ClassMonitor’s flexible tagging system to help you organize your students according to their modules and classes. Finally, streamline your performance grading decisions by deriving insights from your students’ performance indicators across time, through ClassMonitor’s statistics – you can allocate stars to students for good class participation and bolts for absenteeism!

The Developer Guide offers comprehensive documentation on the design and implementation of ClassMonitor. It includes details on the architecture of ClassMonitor, specifications for individual components, and an overview of the software’s functionality and operation.

Table of Contents

1. About ClassMonitor
2. Table of Contents
3. Acknowledgements
4. Setting up, getting started
5. Design
   1. Architecture
   2. UI component
   3. Logic component
   4. Model component
   5. Storage component
   6. Common classes
6. Implementation
   1. Awarding Stars to a Student
      1. Overview
      2. Feature Details
      3. Design considerations:
   2. Awarding Bolts to a Student
      1. Overview
      2. Feature Details
      3. Design considerations:
   3. Sorting Students
      1. Overview
      2. Feature Details
   4. Finding Students
      1. Overview
      2. Feature Details
   5. [Proposed] Undo/redo feature
      1. Proposed Implementation
      2. Design considerations:
   6. [Proposed] Data archiving
   7. [Proposed] Student Comments
      1. Feature Proposal
      2. Command Format
      3. UI Modifications
7. Documentation, logging, testing, configuration, dev-ops
8. Appendix: Requirements
   1. Product scope
   2. User stories
   3. Use cases
      1. Use case 1: Delete a student
      2. Use case 2: Add a student
      3. Use case 3: Add a tag to a student
      4. Use case 4: Find a student by name
      5. Use case 5: Add a star/bolt to a student
      6. Use case 6: Find students by a specific field
      7. Use case 7: Sort list of students by a specific field
   4. Non-Functional Requirements
9. Appendix: Instructions for manual testing
   1. Launch and shutdown
   2. Deleting a student
   3. Saving data
10. Glossary

---

Acknowledgements

This project is based on the AddressBook-Level3 project created by the SE-EDU initiative.

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, StudentListPanel, 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 Student 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("findStarsLT 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 ClassMonitorParser object which in turn creates a parser that matches the command (e.g., FindStarsLessThanCommandParser) 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., FindStarsLessThanCommand) which is executed by the LogicManager.
3. The command can communicate with the Model when it is executed (e.g. to return students with number of stars less than specified number).
   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 ClassMonitorParser 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 ClassMonitorParser 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 ClassMonitor data i.e., all Student objects (which are contained in a UniqueStudentList object).
• stores the currently ‘selected’ Student objects (e.g., results of a search query) as a separate filtered list which is exposed to outsiders as an unmodifiable ObservableList<Student> 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 ClassMonitor data and user preference data in JSON format, and read them back into corresponding objects.
• inherits from both ClassMonitorStorage 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.classmonitor.commons package.

---

Implementation

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

Awarding Stars to a Student

Overview

The star mechanism is facilitated by StarCommand, which is called by its execute method to add stars to a Student.

• StarCommandParser#parse() — Parses the parameters of the star command from its command-line String input.
• StarCommand#execute() — Updates the ClassMonitor with the added stars.

Feature Details

Here is the activity diagram showing the process of the star command:

Here is the sequence diagram showing how a star operation goes through the Logic, Model and Storage components.

Step 1. The user launches the application for the first time and enters in command: star 1 s/2.

Step 2. The LogicManager calls on ClassMonitorParser to parse the String.

Step 3. The ClassMonitorParser calls StarCommandParser.parse(), which returns a StarCommand.

Step 4. LogicManager calls on StarCommand.execute(), which updates the classmonitor with the new number of stars.

Design considerations:

Aspect: How star executes:

• Method 1: Updates the number of stars using Star command.
  • Pros: Easy to implement, easy to use.
  • Cons: Does not allow user to edit the number of stars.
• Method 2: Updates the number of stars using Edit command.
  • Pros: Able to edit the number of stars however one desires.
  • Cons: Command is not modularised, user have to calculate the number of stars themselves when updating.

Awarding Bolts to a Student

Overview

The bolt mechanism is facilitated by BoltCommand, which is called by its execute method to add bolts to a Student.

• BoltCommandParser#parse() — Parses the parameters of the bolt command from its command-line String input.
• BoltCommand#execute() — Updates the ClassMonitor with the added bolts.

Feature Details

Here is the activity diagram showing the process of the bolt command:

Here is the sequence diagram showing how a bolt operation goes through the Logic, Model and Storage components.

Step 1. The user launches the application for the first time and enters in command: bolt 1 b/2.

Step 2. The LogicManager calls on ClassMonitorParser to parse the String.

Step 3. The ClassMonitorParser calls BoltCommandParser.parse(), which returns a BoltCommand.

Step 4. LogicManager calls on BoltCommand.execute(), which updates the classmonitor with the new number of bolts.

Design considerations:

Aspect: How bolt executes:

• Method 1: Updates the number of bolts using Bolt command.
  • Pros: Easy to implement, easy to use.
  • Cons: Does not allow user to edit the number of bolts.
• Method 2: Updates the number of bolts using Edit command.
  • Pros: Able to edit the number of bolts however one desires.
  • Cons: Command is not modularised, user have to calculate the number of bolts themselves when updating.

Sorting Students

Overview

The sorting mechanism is facilitated by SortCommand, which is called by its execute method to sort the students based on one of its fields either in ascending or descending order

• SortCommandParser#parse() — Parses the parameters of the sort command from its command-line String input.
• SortCommand#execute() — Updates the ClassMonitor to display the sorted list.

Feature Details

Here is the activity diagram showing the process of the Sort command:

Here is the sequence diagram showing how a sort operation goes through the Logic, Model and Storage components.

Step 1. The user launches the application for the first time and enters in command: sort name desc.

Step 2. The LogicManager calls on ClassMonitorParser to parse the String.

Step 3. The ClassMonitorParser calls SortCommandParser.parse(), which returns a SortCommand.

Step 4. LogicManager calls on SortCommand.execute(), which updates the classmonitor with the new sorted list.

Finding Students

Overview

The find mechanism is facilitated by FindCommand, which is called by its execute method to filter the students based on one of its fields and a given criteria

• FindCommandParser#parse() — Parses the parameters of the find command from its command-line String input.
• FindCommand#execute() — Updates the ClassMonitor to display the filtered list.

Feature Details

Here is the activity diagram showing the process of the Find command:

Here is the sequence diagram showing how a find operation goes through the Logic, Model and Storage components.

Step 1. The user launches the application and enters in command: find name Alex.

Step 2. The LogicManager calls on ClassMonitorParser to parse the String.

Step 3. The ClassMonitorParser calls FindCommandParser.parse(), which then calls FindCommandParser.parseFindName(), which returns a FindCommand.

Step 4. LogicManager calls on SortCommand.execute(), which updates the student list with the new filtered list.

[Proposed] Undo/redo feature

Proposed Implementation

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

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

These operations are exposed in the Model interface as Model#commitClassMonitor(), Model#undoClassMonitor() and Model#redoClassMonitor() 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 VersionedClassMonitor will be initialized with the initial ClassMonitor state, and the currentStatePointer pointing to that single ClassMonitor state.

Step 2. The user executes delete 5 command to delete the 5th student in ClassMonitor. The delete command calls Model#commitClassMonitor(), causing the modified state of ClassMonitor after the delete 5 command executes to be saved in the classMonitorStateList, and the currentStatePointer is shifted to the newly inserted ClassMonitor state.

Step 3. The user executes add n/David …​ to add a new student. The add command also calls Model#commitClassMonitor(), causing another modified ClassMonitor state to be saved into the classMonitorStateList.

Step 4. The user now decides that adding the student was a mistake, and decides to undo that action by executing the undo command. The undo command will call Model#undoClassMonitor(), which will shift the currentStatePointer once to the left, pointing it to the previous ClassMonitor state, and restores ClassMonitor 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#redoClassMonitor(), which shifts the currentStatePointer once to the right, pointing to the previously undone state, and restores ClassMonitor to that state.

Step 5. The user then decides to execute the command list. Commands that do not modify ClassMonitor, such as list, will usually not call Model#commitClassMonitor(), Model#undoClassMonitor() or Model#redoClassMonitor(). Thus, the classMonitorStateList remains unchanged.

Step 6. The user executes clear, which calls Model#commitClassMonitor(). Since the currentStatePointer is not pointing at the end of the classMonitorStateList, all ClassMonitor 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 ClassMonitor.
  • 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 student 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}

[Proposed] Student Comments

Feature Proposal

This feature is an extension of the ‘Stars’ feature. When a TA gives a student stars, they can also leave a comment to explain why the Student received them. Each instance of a user giving stars (with optional comments) can be stored by Student.

.

Command Format

Users will be able to add comments to a student by using the star command:

Usage: star INDEX s/STARS [c/COMMENT]

the edit command will also be extended to allow users to edit the comments.

Usage: edit INDEX ...c/INDEX2 COMMENT...

The command will edit the comment at the student with index INDEX with comment index INDEX2.

UI Modifications

Alternative 1

• Users will be able to view the comments they have left for each student in a separate window. The components of the window will track changes to the student comments in the model.

Alternative 2

• Users will be able to view the comments they have left for each student in a separate display in the same window.

.

---

Documentation, logging, testing, configuration, dev-ops

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

---

Appendix: Requirements

Product scope

Target user profile:

• Teaching Assistant (TA) who is responsible for managing classes of students
• Has a need to track class participation across students
• prefers desktop apps on a laptop
• prefers typing in a CLI interface to mouse interactions

Value proposition: ClassMonitor empowers TAs to manage their students and obtain insights from students’ data.

User stories

Priority	As a …​	I want to …​	So that I can…​
* * *	TA using the App for the first time	see usage instructions	refer to instructions when I forget how to use the App
* * *	TA	add a new student
* * *	TA	edit a student’s details
* * *	TA	delete a student	remove entries that I no longer need
* * *	TA	know the majors of my students	understand their learning needs
* * *	TA	find a student by name	locate details of students without having to go through the entire list
* * *	TA	track a student’s participation	gauge their engagement in class
* * *	TA	track a student’s attendance	mark and record attendance efficiently
* * *	TA	tag the students by their TGs	remember which class my students are in
* * *	TA	tag the students by their modules	remember which module my students are in
* *	TA	filter the students by their TGs	view all the students from a TG
* *	TA	filter students by their modules	view all the students from a module
* *	TA	exit the program
* *	TA	sort students based on participation	praise those who have taken initiative and remind those who have not to be more proactive
*	TA	have a personal description of the student	know more about them
*	TA	clear all students’ details	remove all entries quickly
*	TA with many students in ClassMonitor	sort students by name	locate a student easily

Use cases

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

Use case 1: Delete a student

MSS The Main Success Scenario (MSS) describes the most straightforward interaction for a given use case, assuming that nothing goes wrong.
Click to view glossary :

1. TA requests to list students
2. ClassMonitor shows a list of students
3. TA requests to delete a specific student in the list

4. ClassMonitor deletes the student

   Use case ends.

Extensions:

• 2a. The list is empty.

  Use case ends.

• 3a. The given index is invalid.

  • 3a1. ClassMonitor shows an error message.

    Use case resumes at step 2.

Use case 2: Add a student

MSS The Main Success Scenario (MSS) describes the most straightforward interaction for a given use case, assuming that nothing goes wrong.
Click to view glossary :

1. TA requests to add a student in the list
2. TA includes the relevant student’s info

3. ClassMonitor adds the student

   Use case ends.

Extensions:

• 2a. TA did not follow the correct format as stated in the instructions.

• 2a1. ClassMonitor shows an error message.

  Use case ends.

Use case 3: Add a tag to a student

MSS The Main Success Scenario (MSS) describes the most straightforward interaction for a given use case, assuming that nothing goes wrong.
Click to view glossary :

1. TA requests to list students
2. ClassMonitor shows a list of students
3. TA requests to add a tag to a specific student in the list

4. ClassMonitor adds the tag

   Use case ends.

Extensions:

• 2a. The list is empty.

  Use case ends.

• 3a. The given index is invalid.

  • 3a1. ClassMonitor shows an error message.

    Use case resumes at step 2.

Use case 4: Find a student by name

MSS The Main Success Scenario (MSS) describes the most straightforward interaction for a given use case, assuming that nothing goes wrong.
Click to view glossary :

1. TA requests to list students
2. ClassMonitor shows a list of students
3. TA searches a specific student in the list

4. ClassMonitor returns the specific student’s details

   Use case ends.

Extensions:

• 2a. The list is empty.

  Use case ends.

• 3a. The given keyword does not match any student’s name.

  • 3a1. ClassMonitor shows an error message.

    Use case resumes at step 2.

Use case 5: Add a star/bolt to a student

MSS The Main Success Scenario (MSS) describes the most straightforward interaction for a given use case, assuming that nothing goes wrong.
Click to view glossary :

1. TA requests to list students
2. ClassMonitor shows a list of students
3. TA adds a star/bolt to a specific student in the list

4. ClassMonitor adds a star/bolt to the student

   Use case ends.

Extensions:

• 2a. The list is empty.

  Use case ends.

Use case 6: Find students by a specific field

MSS The Main Success Scenario (MSS) describes the most straightforward interaction for a given use case, assuming that nothing goes wrong.
Click to view glossary :

1. TA requests to list students
2. ClassMonitor shows a list of students
3. TA requests to filter students by a specific field and criteria

4. ClassMonitor shows a filtered list of students based on the field and criteria specified.

   Use case ends.

Extensions:

• 2a. The list is empty.

• 3a. The given field does not exist.

  • 3a1. ClassMonitor shows an error message.

    Use case resumes at step 2.

  Use case ends.

Use case 7: Sort list of students by a specific field

MSS The Main Success Scenario (MSS) describes the most straightforward interaction for a given use case, assuming that nothing goes wrong.
Click to view glossary :

1. TA requests to list students
2. ClassMonitor shows a list of students
3. TA requests to sort students by a specific parameter in ascending/descending order

4. ClassMonitor shows a sorted list of students based on the field and order specified.

   Use case ends.

Extensions:

• 2a. The list is empty.

• 3a. The given field does not exist.

  • 3a1. ClassMonitor shows an error message.

    Use case resumes at step 2.

  Use case ends.

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 students 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. All user operations should be completed within 100 milliseconds.
5. The project must adhere to a bi-weekly iterative development schedule, ensuring continuous delivery or improvement of a working product every two weeks.

---

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 student

1. Deleting a student while all students are being shown

   1. Prerequisites: List all students using the list command. Multiple students 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 student 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 …​ }

Glossary

Quick Reference
Course	Main Success Scenario (MSS)	Mainstream OS	Teaching Assistant (TA)	Tutorial Group (TG)

C

M

T