You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
C87666: Asterisk should be escaped instead of back-slash on this example
Localization team has reported source content issue that causes localized version to have broken/different format compared to en-us version.
Description: Wrong escaped symbol ( \\ instead of \*) is preventing the right display in localized pages
Copy file name to clipboardExpand all lines: docs/vs-2015/modeling/uml-use-case-diagrams-guidelines.md
+4-4Lines changed: 4 additions & 4 deletions
Original file line number
Diff line number
Diff line change
@@ -164,11 +164,11 @@ In Visual Studio, you can draw a *use case diagram* to summarize who uses your a
164
164
165
165

166
166
167
-
- To state that several actors of the same class can take part in a single occurrence of a use case, set the multiplicity at the actor end of the association to **1..\\***.
167
+
- To state that several actors of the same class can take part in a single occurrence of a use case, set the multiplicity at the actor end of the association to **1..\***.
168
168
169
169
In the illustration, one or more restaurants can take part in fulfilling the same meal order.
170
170
171
-
- To show that each actor can participate at the same time in several occurrences of a use case, set the multiplicity at the use case end of the association to **\\***.
171
+
- To show that each actor can participate at the same time in several occurrences of a use case, set the multiplicity at the use case end of the association to **\***.
172
172
173
173
In the illustration, each restaurant can work on fulfilling more than one order at a time.
174
174
@@ -184,11 +184,11 @@ In Visual Studio, you can draw a *use case diagram* to summarize who uses your a
184
184
185
185
-**1** to state that exactly one instance of this role participates in each link.
186
186
187
-
-**1..\\*** to state that one or more instance of this role participate in each link.
187
+
-**1..\*** to state that one or more instance of this role participate in each link.
188
188
189
189
-**0..1** to state that participation is optional.
190
190
191
-
-**\\*** to state that zero or more instances of this role participate in the link.
191
+
-**\*** to state that zero or more instances of this role participate in the link.
192
192
193
193
> [!NOTE]
194
194
> Many teams do not place multiplicity information on use case diagrams, leaving the multiplicities at the default value of 1. Instead, they provide the information in separate descriptions of the use cases. In this case, all the multiplicities in the use case diagrams will be hidden.
0 commit comments