Consolidate/Reorganize Use Cases

[mmccool]

Some use cases overlap, some are special cases of other more general use cases, and there are various other issues. For example:

• Online Video Conference is a special case of "Streaming Acceleration"
• Professional Web-Based Media Production is a special case of "Image Processing" (especially if we extended the latter to "Image and Video Processing", although there are also aspects of AI workloads mentioned, so perhaps also "Machine Learning".
• "Robot Navigation Acceleration" is a non-web app example: acceleration of computation on an IoT device, using the same infrastructure as would be made available for web apps. This category is not mentioned in the opening set of Use Case categories.
• Persistent Tasks is also not something that is covered by the initial categorization, but may be useful even for non-IoT applications, for example, to do a background rendering job.
• High Availability is more of a feature, not a use case. A "Use Case" here would be something like a safety-critical system (maybe intrusion detection) or something like home automation, which would probably also be instances of IoT or persistent applications.
• Automatic License Plate Recognition is a special case of both Machine Learning and Image Processing, but raises some other points too about availability.
• Machine Learning should be Machine Learning and Inferencing (not just training, in fact most applications will probably be inferencing)

Probably two broad categories: traditional Web Apps, and Non-Web Apps (e.g. IoT devices using the same service).

[mmccool]

Easy cases:

• Online Video Conference + Streaming Acceleration (first is a special case of the second)
• Machine Learning + Image Processing -> "Image and Video Processing and Understanding", then Profession Web-Based Media Production is an special case/example

Others are trickier; for example, the License plates use case is more like an IoT use case (maybe it is being used by a smart camera, for example), but also has some migration, availability, and reliability requirements. So it's not as easy as just putting "License plates" under "Image and Video Processing".

Maybe we need a similar structure to what I did for requirements, e.g. have a "general" and a "specific" use cases section, or talk about "workload types" (e.g., persistent workloads, stateless and stateful workloads, accelerated workloads, iot vs web app workloads, etc.) in a different section.

[mmccool]

Assigning labels would also be useful for cross-referencing, but not numbered, something like "UC-PT" for "Persistent Tasks"