This documentation is presenting the UX and UI principles designed by CYBNITY as presentation layer that allow final user to use the software suite. Find here some usage scenario of CYBNITY (e.g as a CISO’s point of view) which show what are the UI concepts allowing to manage the security information, to collaborate with other stakeholder of security team, and that constituate the UI of ISMS managed by a company via CYBNITY solution.
A UI mockup is a visual representation of a final digital product (e.g ui cockpit of CYBNITY), including layout/hierarchy, color, typography, icons, and other UI elements. While mockups are high-fidelity designs, they are static and have no functionality-like a screenshot.
CYBNITY developed a System Design approach from some typical and important use test scenario to identify the key screens, functions, visual components and screen interactions that are required by user to execute their missions in an ergonomic and safe way.
The implementation documentation includes many types of support deliverables produced during the UX/UI system design life cycle. You can find documentations relative to software maintenance like:
These technical documentations are supporting the UI components development.
The visual and ergonomic rules regarding the components used in CYBNITY graphic user interfaces are standardized via a reference library according each type of reusable component type.
See the visual components library documentation which present the component sets.
The Product Requirements Definition (PRD) of CYBNITY cockpit (main screens organization of CYBNITY web presentation layer as Graphic User Interface) is detailed per test scenario on Cockpit PRD - Usage Scenarios Functional Tests.
Each scenario have been identified as a key and representative type of security use case which determine the visual behavior and/or interaction types that are required by a user with CYBNITY functions to reach a specific security mission (according to a security role like risk analysis, or CISO).
The global UI cockpit approach is inspired by the fighter jets cockpit organization which allow planification (e.g mission, operations), coordination (e. between team member), instant reaction (e.g during crisis or alert) and management of large information (e.g weapon systems, procedures, trajectory, environment metrics).
Usage Scenarios: Behavior-Driven Design (BDD) method is implemented for definition of each usage scenario into a test case driven approach. A scenario is always targeting a goal to reach that is measurable as an end fact (e.g produced by the cockpit user and/or a state changed into the defense system).
The scenario of usage are categorized per capability type covered by a CYBNITY application domain allowing to identify which application domain shall be owner of the user interface elements (presentation layer of application domain) required to have interaction with the provided features.
The link to specification documentation are mentionned like Scenario Detail Card for access to more detail on the usage scenario description.
| Use Scenario Name | Specification Card | UI Mockup | | :—————- | :—————– | :——– | | Permanent activities expected of a security team member are updated and aligned with his committed roles | Scenario Card | Image | | Recipient’s attention of new assigned tasks is visually captured to animate his motivation to treat them | Scenario Card | Image | | User is automatically alerted and notified of the exceeding of an acceptable threshold defined around a cyber risk score relating to a perimeter of assets (e.g information type) | Scenario Card | Image |
| Use Scenario Name | Specification Card | UI Mockup | | :—————- | :—————– | :——– | | The treatment of an urgent high-level task is quickly started by its assigned actor who was not connected on a CYBNITY user interface | Scenario Card | Image | | A task defined and assigned to the user is easily managed in accordance with its level of priority | Scenario Card | Image |
| Use Scenario Name | Specification Card | UI Mockup | | :—————- | :—————– | :——– | | The established risk appreciation process is quickly started to frame the evaluation of a new asset | Scenario Card | Image| | Severity of weaknesses or deficiencies regarding an asset and usage is identified via risk appreciation | Scenario Card | Image |
| Use Scenario Name | Specification Card | UI Mockup | | :—————- | :—————– | :——– | | Risk assessment process is edited and approved as new revision | Scenario Card | Image|
| Use Scenario Name | Specification Card | UI Mockup | | :—————- | :—————– | :——– | | Organization roles and responsibilities matrix is managed with visible approvals status regarding each stakeholder | Scenario Card | Image |
