Confirmed users
353
edits
Auto-tools/Projects/BugHunter: Difference between revisions
→Design and Approach
| Line 19: | Line 19: | ||
= Design and Approach = | = Design and Approach = | ||
One of the goals of the system design of the bughunter webservice and UI | One of the goals of the system design of the bughunter webservice and UI is to get as close to a configuration file driven system as possible. The system will likely be extended with different data types for different products, the UI was designed with this in mind, the impact of new data on the architecture will be minimal. The core concepts in the UI should stay the same. The UI can represent data in tabular or graphical form, a set of controls are provided for filtering data, and connecting one data display to another. Any data type can be connected to any other data type if they have a field in common. This is referred to as signaling. | ||
== Data View == | == Data View == | ||
| Line 25: | Line 25: | ||
[[File:DataViewPanel.png|750px|center]] | [[File:DataViewPanel.png|750px|center]] | ||
== Data View Navigation == | |||
A hierarchical menu is available on each data view. This menu can be used to jump to any data type available. | |||
= Architecture= | = Architecture= | ||