补充规约(几乎100%完成)？
补充规约（大约20％完成）
当时的规约还需要大量的修订。
The specification at that time was still under significant revision.
较低层次的是特性，用例和补充规约。
On the lower levels are features, use cases, and supplementary specifications.
合并之后的原始用例规约。
补充规约（大约80％完成，取决于迭代目标）
Supplementary Specifications (about 80% complete, depending on iteration goals)
关于举办什么类型的庆祝，并没有规约可循。
There are no rules when it comes to the type of celebration you host.
对机构工作的改进，应该在机构《规约》的框架内进行。
Any reform of the Agency's work should be carried out within the framework of the Statute.
无论如何明智，没有规约能够替代感情和策略。
No rules, however wise, are a substitute for affection and tact.
但是由于法规约束和技术改进，媒体垄断被打破。
它规约了开发人员必须收集的信息和控制需求变更的机制。
It specifies information the developers must collect and mechanisms for controlling requirements changes.
此项活动以用例和补充规约的形式，完成了系统的详细需求。
This activity completes detailing the requirements of the system in terms of use cases and Supplementary Specifications.
一旦确定了一些用例和补充规约，就可以决定它们的开发次序。
Once some use cases and supplementary requirements are identified, they are prioritized, so that their order of development can be decided.
将注解作为“规约优于配置”法则的补充(如spring)。
Implement Annotations as complementary to "Convention over Configuration" principle (e.g. in Spring).
我们可以阅读需求规约和代码，并能够很好地保证实现是正确的。
We can read the requirements specification and the code and do a very good job of ensuring that the implementation is correct.
一致性是关键；每个规约文档应该用相同的标题、字体、缩进等等。
Consistency is the key; each specification document should use the same headings, fonts, indentions, and so forth.
构建补充规约环境安全的指南，包括商业规则的例子和一般的约束。
A guide to building supplementary specifications surrounding security, including sample business rules and common constraints.
穆巴拉克说：“就像美国一样，我们还没有批准建立国际刑事法院的《罗马规约》。”
"Just like the United States of America we have not ratified the Statute of Rome, which created the ICC," said Mubarak.
插件的Eclipse规约是使用像图2中显示的URI领域。
The Eclipse convention for plug-ins is to use a URI domain like the one shown in Figure 2.
与此相似，如果你的需求规约只是一张毫无规则的大列表，你也没办法使用它。
Similarly, if your requirements specification is merely a giant list in no particular order, you will not be able to use it.
例子是用例、用例模型、业务规则、类、类图、序列图、数据模型和补充规约。
Examples are use cases, use case models, business rules, classes, class diagrams, sequence diagrams, the data model, and supplementary specifications.
不适合放在用例中的需求（功能性和非功能性）应当在补充规约中进行详细描述。
The requirements (functional and non-functional) that do not fit appropriately within the use cases should be detailed in the Supplementary Specifications.
也如我们前面注意到的，属性提供了补充信息，使你更加有效地理解和使用需求规约。
As we also noted earlier, attributes provide supplemental information that helps you understand and use requirements specifications more effectively.
例如，你如果决定用用例来规约软件需求，你的指南就应该告诉你如何写出事件流程。
For example, if you decide to specify software requirements with use cases, then your guidelines should tell you how to write the flows of events.
计划鼓励你考虑和规约你需要的需求类型，它反过来确保需求编写的一致性与可读性。
A plan encourages you to think about and specify requirement types you will need, which in turn helps to ensure consistency and readability for written requirements.
从功能上来说这没有什么明显的问题，只要你想，你总可以根据规约实现基于类的OO。
And there is no obvious problem in power, since you can always do class-based OO by convention, if you want.
凡此种种显示，Google在全力挑战商业传统及文化规约的时候，有时还真是失策。
The pattern suggests that it can sometimes misstep when it tries to challenge business traditions and cultural conventions.
凡此种种显示，Google在全力挑战商业传统及文化规约的时候，有时还真是失策。
The pattern suggests that it can sometimes misstep when it tries to challenge business traditions and cultural conventions.
应用推荐