Visualisation

MVC

Code reuse - Separation of concern principle will provide code reusability as the design will have a proper domain model and business logic in its logical unit.

Adaptable design - A good design is closed for changes and open for additions. Isolated code in controller, domain model, view, and data access provide the freedom of choosing a number of views and data sources.

Layering - MVC forces to separate data access login for the other layers and various other patterns would be opted to implement the data access layer.

Test driven approach - Isolated implementation allows to test each component separately.

Simultaneous development - Because MVC decouples the various components of an application, we are able to work in parallel on different components without affecting or blocking one another.

Components

CPU and memory usage monitors

Lets the user see what is the cause of if the algorithm runs slowly.

Node and edges graph

Need the user to easily visualize what is shown in the input dot files rather than having to open up the dot file. Non interactable because it would take cpu resources from the algorithm, which is the important part of the application. Also it would draw the user's attention away from the output, which is meant to be the more important component of the two.

Final schedule

Lets the user easily visualize what is outputted in the dot file rather than having to open up the dot file. Can visualize idle times, final times, which processors have more nodes scheduled to them.

Start button

Make a start button rather than automatically starting the application on launch. This is because it lets the user decide exactly when they want to start running the algorithm, lets them get set up. Otherwise, the time to run the algorithm would not be accurate if cpu resources are used in opening the GUI.