用例1——从何处开始？
与病例1有些类似。
Case 1: Too complex an expression.
情况1：表达式太复杂。
Listing 4. Code snippet for Case 1.
清单4。
Case 1: Return all XML "company" data.
案例1：返回所有XML“company”数据。
Case 1: Multiple heterogeneous sources.
案例1：多个异构源。
Case 1 - why did we lose this customer?
案例1-我们为什么丢掉了客户？
Case 1: everyone has at least one friend.
情形1：每个人至少有1个朋友。
Create two use cases called use case 1 and use case 2.
创建两个用例，叫useCase 1和use Case2。
Use Case 1: How many items are stored in a SharePoint list?
用例1：在SharePoint列表中，存储了多少项目？
Case 1: the point is connected to (at least) three other points.
情形1：这个点(至少)与其它三个点相连。
The document in Case 1 had section numbers included as part of the data.
案例1 之中的文档拥有作为数据部分包含的段落编号。
Part 1 in the series focused on two case studies.
本系列的第 1部分重点讨论了两个案例研究。
Consider the case that the code in Listing 1 illustrates.
考虑一下代码清单1中所演示的代码的情况。
Figure 1 illustrates the case study architecture.
图1说明了这个案例研究的架构。
In this case, you mostly follow the same steps as scenario 1.
在这个案例中，您大体上按照和情景说明1相同的步骤执行。
In that case, import file 2 first, followed by file 1.
在这种情况下，首先是导入文件2，接着才是文件1。
To begin, you can select a case (Label 1 in Figure 6).
首先，您可以选择一个案例(图6中的Label1)。
There is a case on in Courtroom No 1.
有案子在第1号法庭里审理。
In Listing 1, you see a condensed test case with two tests.
清单1中所示的是具有两个测试的浓缩测试用例。
In the case of the button, you could rewrite this as shown in Listing 1.
如果遇到这个按钮，可以按清单1所示的方式重写。
Case study 1 focused on customer order analysis.
案例研究1重点讨论客户订单分析。
Figure 1: Every use case has an assigned set of scenarios.
图1：每个用例都有一组分配的情境。
With proper treatment, the case fatality rate should remain below 1%.
经过适当治疗，病死率应保持在1％以下。
In this case, you could change the code as shown in listing 1.
在这里，可以像清单1那样更改代码。
考虑一下图1之中的事例。
The right side of Figure 1 shows the paravirtualization case.
图1的右边是半虚拟化示例。
But worst case scenario, if only 1 percent... that's still awesome!
但最坏的情况，如果只有百分之一的话…那还是棒极了！
Step 1: Identify variables for each use case step
步骤1：为每个用例步骤确定变量
Step 1: Identify variables for each use case step
步骤1：为每个用例步骤确定变量
应用推荐