| Table of Contents |
|---|
...
Components marked with orange colour are new components. Blue component are existing components.
Tag [FutureDev] is used for requirements, use cases or user stories that will be implemented in the future but may already have impact on the design. So they should be taken under consideration when designing planned features.
Tag [Nice-to-have]is used for requirements, use cases and user stories that would ideally be included. But may be moved for later stages without big impact on the outcome.
...
GUI must work in native ARM64 environment and in x64 environment.
GUI must work on native WOA OS browser Microsoft Edge.
If GUI is implemented as Web Script.
[FutureDev] GUI must work in environment without access to the Internet.
GUI users may be working inside private, closed test / lab networks and may not have access to the Internet.
This implied no external import / loads of external source scripts or libraries.
[FutureDev] GUI must be able to connect and interact with multiple wperf-relay instances to query, fetch, group and present counting and sampling data.
[FutureDev] GUI users may want to write “plugins” to add e.g. new graphs or other visualisations.
[FutureDev] GUI displays Flame Chart for profiled code.
[FutureDev] GUI displays Timeline for counting model.
...
Multi-host architecture proposal
[FutureDev] One wperf-gui instance should be able to connect to multiple wperf-relay instances. This architectural extension may be required in “clusters” of ARM64 systems, WOA testbeds / test labs. Users may want to gather “simultaneously” timeline, counding, sampling, metrics, analysis data from many (>1) WOA hosts. There’s a benefit to performance analysis on multiple systems at once. And we recognise this requirements.
...