Fadi Sng - Project Portfolio

This command sorts the tasks in the task list of the current working project.
Format: sortTask INDEX

INDEX refers to the index of the list provided in the highlighted section above which corresponds to the type of sorting you wish to apply. For example, index 1 corresponds to sorting by alphabetical order. For the case of sorting tasks, only numbers between 1 and 4 are applicable.

Example:

Let’s say you have added many different tasks with different deadlines and progresses into MyProject.

The default sorting order that MyProject offers is by increasing order of time(index 2). However you wish to group those tasks that are done in one group and those not done in another group and then further sort each group by increasing order of time(index 4) to track the progress of your tasks.

Simply type in the command sortTask 4 and all the tasks in the list will immediately be sorted accordingly.

In addition, whenever you add a new task(Section 3.2.4) or edit the details of an existing task(Section 3.3.2), MyProject will automatically insert the newly added or edited task into the correct position based on this new sorting order so you don’t have to continuously type this command whenever you wish to add or edit tasks!

Here is a step by step process on how to do this.

Within every project, there are tasks to be done or milestones to be achieved within certain deadlines. The diagram below shows the class diagram of the task class and how it interacts with the model.

As shown in figure 2, each project stores multiple tasks in a list. These tasks can be stored, deleted, edited and sorted very easily. Here are some task related commands that can be executed by the app.

As seen in figure 2, each task consists of 3 parameters namely description, time and a boolean state to show whether the task is done/in progress. A typical task will look like this on the app:

Sorts some lists based on specifications provided by the user. There are 3 lists that are able to be sorted so far.

The implementation is similar for these 3 methods. It makes use of SortingOrder, which is a container class that stores the current sort order as well as methods to get and set these orders. SortingOrder can be found in the model package. Currently there are 5 different methods to sort the lists.

All sort commands take in a single integer as parameter. As mentioned in the note above, integers 1-4 are valid input for sortTask, integers 1, 2 and 5 are valid for sortSpending, and integers 1-2 are valid for sortMeeting.

An example command would be sortTask 1 which sorts the list of tasks by alphabetical order.

The following sequence diagram shows the process of obtaining a list with the new sorting order and updating the current sort order in SortingOrder class.

These are the stages shown in figure 3. Stages are similar for sort spending as well.

The diagram below shows sortTask works. There are 2 possible error messages that can occur. Firstly, if the user inputs an index that is not applicable to the type of items sorted. For example, sortTask 5 is invalid as index 5 is linked to a price sorting mechanism which is not applicable to sorting tasks. Secondly, an error will be shown if the user attempts to sort the items in the same order is the current sorting order. For example, since the default sorting order for tasks is by increasing order of date, the command sortTask 2 will be invalid if the sorting order has never been changed before. Otherwise if the input is valid, the sorting will occur and the newly sorted task list will be displayed.