use cases
Think of pages as use cases. Here are some conceivable, where components is system software + system hardware and benchmarks are the results:
1) Browse all components at will
2) Browse all benchmarks results at will
3) Browse benchmarks for 1 component
4) Browse component for 1 benchmark
5) Browse benchmarks for 2+ component using constraints
6) Browse component for 2+ benchmarks using constraints
For example, if I want to see the results for 7 zip only. The resulting page gives me
1) A long list of included submissions. The information is relevant but should be way down on the result page.
2) SYSTEM which is a nice scrollable description of the systems including 7zip benchmark.
3) "Overview" which is a huge table containing very little information. Just which other benchmarks are included by the current systems
4) A huge list of graphs with my 7zip results somewhere, deeply embedded among other graphs I didn't ask for. Take the 7zip graph and present that first on the page!!!
This approach could be used for the other use cases as well, present what is asked for at the very top. Other information can be included in other pages, expandable folders etc, but still, what the user asks for should always be presented first.
Originally posted by Michael
View Post
1) Browse all components at will
2) Browse all benchmarks results at will
3) Browse benchmarks for 1 component
4) Browse component for 1 benchmark
5) Browse benchmarks for 2+ component using constraints
6) Browse component for 2+ benchmarks using constraints
For example, if I want to see the results for 7 zip only. The resulting page gives me
1) A long list of included submissions. The information is relevant but should be way down on the result page.
2) SYSTEM which is a nice scrollable description of the systems including 7zip benchmark.
3) "Overview" which is a huge table containing very little information. Just which other benchmarks are included by the current systems
4) A huge list of graphs with my 7zip results somewhere, deeply embedded among other graphs I didn't ask for. Take the 7zip graph and present that first on the page!!!
This approach could be used for the other use cases as well, present what is asked for at the very top. Other information can be included in other pages, expandable folders etc, but still, what the user asks for should always be presented first.
Comment