From 04767d93c1ede0d7779e6b41e01871182c6b94aa Mon Sep 17 00:00:00 2001
From: Michael McCool The following categories group Use Cases that share a common property.
+ In the definition of a User Story, use case categories can be cited as
+ motivations rather than (or in addition to) specific use cases. Provides a public service. Misuse can result in lack of support to other users. Handles personal or confidential information. Misuse could disclose privately identifiable information (PII) or sensitive business information. Misuse has the potential to cause personal injury. Misuse has the potential to cause financial injury or damage to business operations or reputation. Simplifying the process of TD construction is helpful to ease the task of TD writers and generators. User stories provide a high-level summary of a requirement in the form of
+ a single sentence that describes a stakeholder (Who has the need),
+ a technical requirement (What they need; a capability or condition; features),
+ and a functional requirement (Why they need it; the purpose or motivation; use cases).
+ These are often stated in the form of a sentence: "As a Who I need What so that I can Why."
+ For clarity, the following user stories break out each part in a list.
+ Each user story will in addition identify one or more Use Case (or Use Case Categories)
+ that establishes the motivation for the identified capability.
+ Capabilities correspond to sets of features in other technical specifications.
+ Define how user stories and features are linked. We can link back from
+ implemented features to user stories, but want to avoid unstable links e.g. to documents
+ maintained in github. If we have bidirectional links we need some mechanism to keep them
+ consistent. Reusable Connection descriptions in a TD. Better describe connection oriented protocols such as MQTT and WebSockets.Edge Computing
-
+
+
+
+ Use Case Categories
+ Security Public Service
+
+
+
+
+ Security Private Information
+
+
+
+
+ Security Safety Critical
+
+
+
+
+ Security Business Critical
+
+
+
+
+ TD Creation Simplification
+
+
+ Requirements
+ User Stories
+ Connection Oriented Protocols
+
+
+
+
+
+
Simplify TDs in cases without usage of default terms or to avoid redundancy
+There are at least three sub-problems that motivate this feature:
+We will keep this and following subsection for now but should consider reorganizing them into user stories.
This section defines the properties required in an abstract Web of Things (WoT) architecture.
@@ -8917,87 +9069,6 @@Provides a public service; misuse can result in lack of support to other users.
-Handles personal or confidential information. Misuse could disclose privately identifiable information (PII) or sensitive business information.
-Misuse has the potential to cause personal injury.
-Risks are defined in detail in the Security and Privacy Guidelines document.