如果您不只想处理代码，但是又想文档化，那么就使用这种模式。
If you want to work not only in the code but also want documentation, use this mode.
花了很长时间把会议结果文档化。
也允许测试人员评估非文档化的协议。
It also allows the tester to assess non-documented agreements.
法规遵循是对决策的正确执行的文档化。
Compliance is the documentation of the proper execution of decisions.
在模型中文档化数据结构。
捕获和文档化使用用例模型的功能需求。
Capturing and documenting functional requirements with use case models.
文档化正确的过程包括定位问题更甚于缺乏文档。
Documenting the right process involves addressing problems deeper than the lack of documentation.
它还允许您将规划归档，这一点对文档化很重要。
It also allows you to archive the plan, which is very important for documentation purposes.
用基本原理定义决策，并文档化和传达这些决策。
Define decisions with a rationale, then document and communicate those decisions.
例如，“全面文档化”和“工作软件”相对立吗？
For instance, is "comprehensive documentation" at the opposite pole from "working software"?
文档化的流程对软件开发项目的成功没有任何作用。
Documented process means NOTHING for success of software development project.
对架构文档化很有价值。
There is usually considerable value in documenting the architecture.
这十分便于查看和欣赏，而且仍然尽量保持自文档化。
That's a very easy distinction to see and appreciate, and still manages to be self-documenting.
它们将个人对于戒烟，减肥，增加储蓄之类的承诺文档化。
They document a person's commitment to, for example, stop smoking, lose weight, or save more money.
因此，确信你已把使用这个架构和原因文档化就非常重要了。
Thus, an important consideration is to ensure that you document the decisions that have led to this architecture and the rationale for those decisions.
如果您只想处理代码，但是又想文档化，那么就使用这种模式。
If you want to work only in the code but also want documentation, use this mode.
什么与用户接受他们需要的结果有关，不仅仅是文档化的需求。
What matters is that customers receive the results they need, not just what was documented as a requirement.
然后，假设您的站点策略已文档化并向整个团队解释了，对吗？
But then suppose your site's policies that are documented and explained to your entire team, right?
按照我的经验，有两个关键性的问题制约着软件开发的文档化。
In my experience, two key problems plague documentation in software development.
必须要指出的是，一个人能够文档化一个好的过程或者差的过程。
It must be said that one can document a good process or a poor process.
注意，架构和设计使用统一建模语言(uml)9进行文档化。
Note that architecture and design are documented using the Unified Modeling Language (UML) 9.
而且，这还不能处理那些没有文档化的环境变量的问题。
And that still doesn't deal with the problem of undocumented environment variables.
文档化范式是一种有趣的用于持久化复杂对象结构的途径。
The document paradigm is an interesting approach for persisting complex object structures.
RationalRose的全部模型被文档化并且适合交付吗？
Was the Rational Rose model complete, documented, and suitable for delivery?
用于文档化并定义与应用过程标准，体系和规定一致的IT治理过程。
Responsible for documenting and defining an IT governance process, in accordance with applicable process standards, frameworks and regulations.
维护人员关注易理解性，一致性，和文档化的设计方法，与易修改性。
The maintainer is concerned with a comprehensible, consistent, and documented design approach, and the ease with which modifications can be made.
对服务相关的业务和技术进行适当的文档化，根据服务消费者和提供者。
Appropriately document both business - and technical aspects of services, with respect to service consumers and providers.
这里有一个关于上述讨论的需求应该在哪里进行文档化的问题。
There is a question about where requirements like those just discussed should be documented.
类似地，评估活动也将利用软件开发方法的产品，提供明确文档化的输入。
Similarly, estimation activities can make use of artifacts produced by software development methodologies, provided these inputs are explicitly documented.
在不同程度上，它们都有安装、文档化、设计工具、打包和部署方面的问题。
To varying degrees, they all have issues with installation, documentation, design tools, packaging, and deployment.
应用推荐