Scope

• JOC is turning towards its end of life and will be replaced by a new component.
• The requirements management for the new JOC Cockpit has started.

Cockpit

Functional Requirements

• Basically the existing functionality shall be provided to monitor and control jobs, job chains etc. and to access logs.
• Visualisation of more details, e.g. for history.
• Support for any number JobScheduler instances
  • Active and Passive Cluster Instances
  • Supervisor and Workload Instances
  • Master and Agent Instances
  • Of specific concern will be the management of lager numbers of Agents
• Authentication and Authorization via Apache Shiro
  • Integration with Directory Services
  • Management of permissions, e.g. for folders and operations.
  • Grouping of permissions to roles and 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. The GUI will receive events from JobScheduler instances.
• Responsive Design for use with mobile devices as e.g. tablets.

Architecture

• JOC will be completely re-written.
• A new framework is introduced that will replace the existing XML Interface. 
• Implementation of a web service interface between JOC and JobScheduler

Milestones

• July 2015: requirements collection
• August 2015: web service interface
• November 2015: Release Candidate targeted for release 1.11