Confirmed users
353
edits
Auto-tools/Projects/BugHunter: Difference between revisions
→Design and Approach
| Line 21: | Line 21: | ||
One of the goals of the system design of the bughunter webservice and UI was 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. | One of the goals of the system design of the bughunter webservice and UI was 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. | ||
== Data View == | |||
The fundamental unit of data display in the bughunter UI is referred to as a "data view". The default representation of a data view is tabular but can also be graphical. An example data view is depicted below: | The fundamental unit of data display in the bughunter UI is referred to as a "data view". The default representation of a data view is tabular but can also be graphical. An example data view is depicted below: | ||