Currently use cases are all under one big subsection, 4.1. There is no 4.2, and nesting is quite deep, and not entirely logical. Some suggested changes to clean this up:
Get rid of "Accelerated Workloads", and move everything up a level. All the use cases are accelerated, pretty much.
Online Video Conference is an example of a "streaming acceleration" feature. Combine these, or just keep UV-VC since it is more concrete.
Robustness is a feature (called "Resiliency" in General Requirements). Get rid of this section header, raise UCs under it up a level, and incorporate "robustness" content into the description of each use case, as appropriate. Perhaps use "Resiliency" instead of "Robustness" for consistency.
Maybe just flatten all the specific use cases to a single list, then explain the "categories" in the general requirements section. It's hard to make a tree-like categorization of use cases precisely because the specific use cases can fall into more than one category. "Streaming" may have to be added as a general requirement to make this work (since UC-VC is just a special case of UC-SA).
In the slides I am just going to use a flat list rather than sections etc.
Currently use cases are all under one big subsection, 4.1. There is no 4.2, and nesting is quite deep, and not entirely logical. Some suggested changes to clean this up:
In the slides I am just going to use a flat list rather than sections etc.