It can take the initiative to prevent risks and reduce losses with effective software risk management.
有效的软件风险管理能够主动防范风险，降低损失。
Software risk can be controlled more detailedly and more precisely, and the rate of success about software projects is improved.
有助于更细致、更精确地控制软件风险，提高软件项目的成功率。
The basic concept of software risk is introduced, the characteristic of software risk and the ways to distinguish software risk are analysed.
首先介绍了软件风险的基本概念，分析了软件项目风险的特点，以及如何识别软件风险。
In Defined level of CMMI criterion, there is a process area of risk management, which is the base of our software risk management implementation.
在CMMI模型中，在严格定义级给出了一个软件风险管理的过程域，本文介绍的软件风险管理实现就是基于这个规范的。
We divide Software risk Management into five steps: risk Identify, risk Analyze, risk Plan, risk Track and risk Control, thus we total manage the risks.
该实现把软件风险管理分成五个步骤：风险识别、风险评估、风险计划、风险跟踪和风险控制，进而对风险进行全面管理。
After analyzing the software risk concept of safety-critical system and metrics definition of software risk, this paper discusses metrics definition of software risk based on black-box.
本文在分析了安全系统软件的安全性和风险度量概念的基础上，详细讨论了黑箱条件下的软件风险度量等问题。
There are strict traffic light software risk control systems, traffic lights in strict accordance with the trading operation will be no large losses, but profit can be enlarged indefinitely.
红绿灯软件有严格的风险控制系统，严格按照红绿灯进行买卖操作不会发生大额的亏损，但是获利则可以无限放大。
In so doing he opened up a conversation on how best to handle risk and uncertainty in software development.
以此，他展开了一个关于如何最好地管理软件开发中的风险和不确定性的讨论。
This plan is used along with the software development plan and the risk management plan to assess the project feasibility.
这个计划与软件开发计划和风险管理计划共同作为评估项目可行性的依据。
It USES risk considerations to balance software discipline and flexibility, and to answer other key "how much is enough?" questions.
它使用风险分析来平衡软件规范和灵活性，并解答其它关键“多少是足够的”的问题。
User stories are best for dealing with projects where the risk of software invisibility is high.
用户情景对于处理软件不可见性风险最高的项目来说，是最佳的方法。
Automated tools help reduce risk by enabling managers to understand and manage the evolution of business and software requirements throughout the software development lifecycle.
通过使经理理解和管理贯穿软件开发周期的业务和需求的演进自动化工具帮助你减少风险。
If they plan to use the open source software internally only, with no intent to distribute it, the risk is quite low.
如果他们计划只是内部地使用公开源码软件而不准备发布产品，风险就是很小的。
Reuse of all of these types of patterns makes for better quality software, reduced risk, productivity gains, consistency, and better interoperability across the enterprise.
所有这些类型的模式的重用都能在整个企业内提高软件质量，减少风险、提高效率和提高互操作性。
Regardless, requiring humans to perform deployment procedures introduces the risk of errors and causes time bottlenecks that delay the release of software into the multiple target environments.
但是无论如何，要求人员执行部署流程都会增加出错的风险，导致时间瓶颈，延误软件在多个目标环境中的发布。
In addition to understanding what's at risk, you also have to constantly adapt your plans to match the changing state of your software.
除了了解处于风险中的部分以外，您还必须不断调整您的计划以匹配软件变化的状态。
The sad fact is that most application developers have no idea whatsoever as to the risk profile of the software that they produce.
不幸的是，大多数应用程序开发人员对于他们生产的软件的风险透明度一无所知。
A third risk area is committing too early to a specific implementation of hardware, software, and firmware, resulting in brittle systems that cannot be easily extended.
第三大风险区域是对硬件、软件和固件的特定实施承诺过早，最后导致短暂的系统，不能被容易的扩展。
These integrations help reduce the risk associated with software development and make application development more predictable.
这些集成帮助减少与软件开发相关联的风险，并且令应用程序开发更可预测。
It is best to think of continuous integration as a mindset or statement of intent that allows you to reduce risk by frequently integrating incremental software development changes.
最好是将持续集成认为是一种意识思维和描述，使你通过频繁地集成增量的软件开发变更以减少风险。
At the risk of using a word that disturbs many in the field of software engineering, requirements management is just a process.
冒险使用的这个可能会搅乱软件工程，需求管理领域的单词其实就是过程。
Risk in software project management is also well-known, although it is usually expressed qualitatively in a documented risk list.
软件项目管理中的风险也是众所周知的，尽管它通常在质量方面表示于编制的风险列表中。
Controlling the quality processes across and between software and systems delivery cycles gives companies many ways to lower risk.
在软件与系统交付周期中控制质量流程为组织提供了更多降低风险的方式。
In the past, IT assigned the risk of properly defining requirements to business stakeholders but assumed the risk of delivering software based on those requirements.
过去，IT界已经提出了，向商业相关利益方正确定义需求存在一定风险，但是还是假设交付软件的风险取决于这些需求。
But building on code from third parties brings new business and licensing concerns issues that can put software projects at risk.
但是，在第三方引入的代码上进行构建会带来令软件项目处于风险中的新的业务和许可关系问题。
In addition, because the project is focused now on requirements and software architecture, the software project manager is responsible for compiling a risk list.
除此之外，由于项目已进入到关注需求和软件架构的阶段，此时软件项目经理有必要编写一份风险列表。
Even with such measures in place, though, any server is a potential security risk: The software could have undiscovered bugs or be misconfigured in some way.
即使采用了这类措施，任何服务器仍然存在潜在的安全威胁：软件可能存在问题，或者配置方式可能出错。
Most popular software engineering methodologies strongly advocate that risk analysis be tracked throughout the development lifecycle.
大多数流行的软件工程方法都大力提倡对整个开发生命周期进行风险分析。
Most popular software engineering methodologies strongly advocate that risk analysis be tracked throughout the development lifecycle.
大多数流行的软件工程方法都大力提倡对整个开发生命周期进行风险分析。
应用推荐