...
- Basically the existing functionality shall be provided.
- Improved navigation should be provided.
- More Visualisation of more details, e.g. for history.
- Suppot Support for multiple JobScheduler instances
- Cluster Instances
- Supervisor and Workload Instances
- Master and Slave Instances
- Authentication via Apache Shiro
- Authorisation via Apache Shiro
- Management of permissions, e.g. for folders and GUI operations.
- Grouping of permissions to roles.
- Associating roles to users.
- Workload visualisation
- Calendar preview
Non-Functional Requirements
- Reduced impact of JOC operations on the JobScheduler main process.
- Consistent logging.
Usability Requirements
- Improved navigation.
- Improved graphical presentation.
- Better responsiveness of the GUI.
- Responsive Design for use with devices as e.g. tablesReduced impact of JOC operations on the JobScheduler main process.
Architecture
- JOC will be completely re-written.
- A new framework will be introduced that currently is being decided on.
- Introduction of an interface between JOC and JobScheduler
- Presumably the Jetty container Web Server will operate that interface.
...