diff --git a/AboutUs.html b/AboutUs.html index a662268c9ac..69829db8da3 100644 --- a/AboutUs.html +++ b/AboutUs.html @@ -18,7 +18,7 @@ [portfolio]
{ list here sources of all reused/adapted ideas, code, documentation, and third-party libraries -- include links to the original source as well }
Refer to the guide Setting up and getting started.
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.
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),
interface
with the same name as the Component.{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.
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,
Logic
component.Model
data so that the UI can be updated with the modified data.Logic
component, because the UI
relies on the Logic
to execute commands.Model
component, as it displays Person
object residing in the Model
.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.
Note: The lifeline for DeleteCommandParser
should end at the destroy marker (X) but due to a limitation of PlantUML, the lifeline continues till the end of diagram.
How the Logic
component works:
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.Command
object (more precisely, an object of one of its subclasses e.g., DeleteCommand
) which is executed by the LogicManager
.Model
when it is executed (e.g. to delete a person).Refer to the guide Setting up and getting started.
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.
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),
interface
with the same name as the Component.{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.
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,
Logic
component.Model
data so that the UI can be updated with the modified data.Logic
component, because the UI
relies on the Logic
to execute commands.Model
component, as it displays Person
object residing in the Model
.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.
Note: The lifeline for DeleteCommandParser
should end at the destroy marker (X) but due to a limitation of PlantUML, the lifeline continues till the end of diagram.
How the Logic
component works:
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.Command
object (more precisely, an object of one of its subclasses e.g., DeleteCommand
) which is executed by the LogicManager
.Model
when it is executed (e.g. to delete a person).Model
) to achieve.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:
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.XYZCommandParser
classes (e.g., AddCommandParser
, DeleteCommandParser
, ...) inherit from the Parser
interface so that they can be treated similarly where possible e.g, during testing.API : Model.java
The Model
component,
Person
objects (which are contained in a UniquePersonList
object).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.UserPref
object that represents the user’s preferences. This is exposed to the outside as a ReadOnlyUserPref
objects.Model
represents data entities of the domain, they should make sense on their own without depending on other components)Note: An alternative (arguably, a more OOP) model is given below. It has a Tag
list in the AddressBook
, which Person
references. This allows AddressBook
to only require one Tag
object per unique tag, instead of each Person
needing their own Tag
objects.
API : Storage.java
The Storage
component,
AddressBookStorage
and UserPrefStorage
, which means it can be treated as either one (if only the functionality of only one is needed).Model
component (because the Storage
component's job is to save/retrieve objects that belong to the Model
)Classes used by multiple components are in the seedu.address.commons
package.
This section describes some noteworthy details on how certain features are implemented.
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
.
Note: If a command fails its execution, it will not call Model#commitAddressBook()
, so the address book state will not 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.
Note: If the currentStatePointer
is at index 0, pointing to the initial AddressBook state, then there are no previous AddressBook states to restore. The undo
command uses Model#canUndoAddressBook()
to check if this is the case. If so, it will return an error to the user rather
than attempting to perform the undo.
The following sequence diagram shows how an undo operation goes through the Logic
component:
Note: The lifeline for UndoCommand
should end at the destroy marker (X) but due to a limitation of PlantUML, the lifeline reaches the end of diagram.
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.
Note: If the currentStatePointer
is at index addressBookStateList.size() - 1
, pointing to the latest address book state, then there are no undone AddressBook states to restore. The redo
command uses Model#canRedoAddressBook()
to check if this is the case. If so, it will return an error to the user rather than attempting to perform the redo.
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:
Aspect: How undo & redo executes:
Alternative 1 (current choice): Saves the entire address book.
Alternative 2: Individual command knows how to undo/redo by -itself.
delete
, just save the person being deleted).{more aspects and alternatives to be added}
{Explain here how the data archiving feature will be implemented}
Target user profile:
Value proposition: track students’ test scores, submissions, progress and also, access their particulars with ease, all in one place!
Priorities: High (must have) - * * *
, Medium (nice to have) - * *
, Low (unlikely to have) - *
Priority | As a … | I want to … | So that I can… |
---|---|---|---|
* * * | prepared teacher | add student's email | email the student when I need to |
* * * | caring teacher | add student's name | call a student by his/her name |
* * * | efficient teacher | add student's register number | identify a student more quickly |
* * * | teacher wanting to split students for group project | add student's sex | see how many students of each gender I have |
* * * | caring teacher | add student's address | visit a student who may be sick at home |
* * * | prepared teacher | add student's contact number | call up the student when I need to contact him/her |
* * * | prepared teacher | add student's emergency contact name | identify the person I am calling if there are emergencies |
* * * | prepared teacher | add student's emergency contact number | notify the person in case of emergencies |
* * * | prepared teacher | add student's class | identify which student is in which class |
* * * | diligent teacher | remove a student from the app | ensure my records are accurate when they drop out |
* * | caring teacher | add student's photo | know what my students look like |
* * | lazy teacher | mass add student information | save the trouble of adding them one by one |
* * | lazy teacher | mass delete all dummy data | save the trouble of removing them one by one |
* * | diligent teacher | assign roles to students | manage students with the specific roles |
* * | neat teacher | group students by their class | manage and access information by class |
* * | teacher wanting to split students for group project | separate students into project groups | manage their project work within the app |
* * | prepared teacher | update a student's information | have the most current details when there is a change |
* * | diligent teacher | assign progress tags to individual students | categorise their performance in class |
* * | efficient teacher | sort the students by name | arrange the students lexicographically for exam conditions |
* * | caring teacher | add a comment for a student | take note of that student's particular trait |
* * | strict teacher | track a student's submissions | see which students did not submit tasks on time |
* * | strict teacher | track student attendance | address absenteeism and its impact on student performance |
* * | diligent teacher | add a new test for all my students | keep track of all the students' results |
* * | diligent teacher | add the scores of the students | have an overview of everyone's results |
* | picky teacher | customize the app settings | align the configuration with my preferences |
* | teacher who likes to have everything in one app | create a seating arrangement for the class | edit the seating arrangement any time |
* | diligent teacher | export information of all my graduated students | store them into the school database |
(For all use cases below, the System is the StudentManagerPro
and the Actor is the user
, unless specified otherwise)
System: StudentManagerPro
Use case: UC01 Add Student's Name
Actor: User
Preconditions: StudentManagerPro is open.
Guarantees:
MSS
delete
, just save the person being deleted).Target user profile:
Value proposition: track students’ test scores, submissions, progress and also, access their particulars with ease, all in one place!
Priorities: High (must have) - * * *
, Medium (nice to have) - * *
, Low (unlikely to have) - *
Priority | As a … | I want to … | So that I can… |
---|---|---|---|
* * * | prepared teacher | add student's email | email the student when I need to |
* * * | caring teacher | add student's name | call a student by his/her name |
* * * | efficient teacher | add student's register number | identify a student more quickly |
* * * | teacher wanting to split students for group project | add student's sex | see how many students of each gender I have |
* * * | caring teacher | add student's address | visit a student who may be sick at home |
* * * | prepared teacher | add student's contact number | call up the student when I need to contact him/her |
* * * | prepared teacher | add student's emergency contact name | identify the person I am calling if there are emergencies |
* * * | prepared teacher | add student's emergency contact number | notify the person in case of emergencies |
* * * | prepared teacher | add student's class | identify which student is in which class |
* * * | diligent teacher | remove a student from the app | ensure my records are accurate when they are no longer in the class |
* * | caring teacher | add student's photo | know what my students look like |
* * | lazy teacher | mass add student information | save the trouble of adding them one by one |
* * | lazy teacher | mass delete all dummy data | save the trouble of removing them one by one |
* * | diligent teacher | assign roles to students | manage students with the specific roles |
* * | neat teacher | group students by their class | manage and access information by class |
* * | teacher wanting to split students for group project | separate students into project groups | manage their project work within the app |
* * | prepared teacher | update a student's information | have the most current details when there is a change |
* * | diligent teacher | assign progress tags to individual students | categorise their performance in class |
* * | efficient teacher | sort the students by name | arrange the students lexicographically for exam conditions |
* * | caring teacher | add a comment for a student | take note of that student's particular trait |
* * | strict teacher | track a student's submissions | see which students did not submit tasks on time |
* * | strict teacher | track student attendance | address absenteeism and its impact on student performance |
* * | diligent teacher | add a new test for all my students | keep track of all the students' results |
* * | diligent teacher | add the scores of the students | have an overview of everyone's results |
* | picky teacher | customize the app settings | align the configuration with my preferences |
* | teacher who likes to have everything in one app | create a seating arrangement for the class | edit the seating arrangement any time |
* | diligent teacher | export information of all my graduated students | store them into the school database |
(For all use cases below, the System is the StudentManagerPro
and the Actor is the user
, unless specified otherwise)
System: StudentManagerPro
Use case: UC01 Add Student's Name
Actor: User
Preconditions: StudentManagerPro is open.
Guarantees:
MSS
Extensions
2a. User enters invalid characters.
3a. User leaves the name field empty.
System: StudentManagerPro
Use case: UC02 Add Student's Email
Actor: User
Preconditions: @@ -157,7 +157,7 @@ Expected: Similar to previous
{ more test cases … }
Sorts all students currently in the list based on the specified attribute
Prerequisites: List all students using the list
command. Multiple students in the list.
Test case: sort register number
Expected: List of students is sorted according to register number. Confirmation message shown in the status message.
Test case: sort abc
Expected: List is not sorted, Error details shown in the status message.
Other incorrect sort commands to try:
sort
sort 1
-Expected: Similar to previous
{ more test cases … }
Dealing with missing/corrupted data files
{ more test cases … }
{ more test cases … }
Dealing with missing/corrupted data files
{ more test cases … }
docs/
folder contains the source files for the documentation website.Style guidance:
Converting to PDF
docs/
folder contains the source files for the documentation website.Style guidance:
Converting to PDF
java.util.logging
package for logging.LogsCenter
class is used to manage the logging levels and logging destinations.Logger
for a class can be obtained using LogsCenter.getLogger(Class)
which will log messages according to the specified logging level..log
file.logLevel
setting in the configuration file (See the Configuration guide section).java.util.logging
package for logging.LogsCenter
class is used to manage the logging levels and logging destinations.Logger
for a class can be obtained using LogsCenter.getLogger(Class)
which will log messages according to the specified logging level..log
file.logLevel
setting in the configuration file (See the Configuration guide section).StudentManagerPro is a desktop application for managing your students' details. While it has a GUI, most of the user interactions happen using a CLI (Command Line Interface).
Acknowledgements
StudentManagerPro is a desktop application for managing your students' details. While it has a GUI, most of the user interactions happen using a CLI (Command Line Interface).
Acknowledgements