有效的软件风险管理能够主动防范风险,降低损失。
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.
软件风险和质量问题总是伴随着软件开发的全过程而存在的,软件项目规模越大,这种潜在的危机就越明显。
The risk of a software and quality problems always exist in the whole process of its development. The larger and more complex a project is, the more obvious the potential risk will be.
本文在分析了安全系统软件的安全性和风险度量概念的基础上,详细讨论了黑箱条件下的软件风险度量等问题。
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.
该实现把软件风险管理分成五个步骤:风险识别、风险评估、风险计划、风险跟踪和风险控制,进而对风险进行全面管理。
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.
如您在本迭代旅行的简单实例中所见到的,对于软件风险、特性蔓延、超出控制的未预料的崩溃,和恢复计划,我们遇到了相似的事件。
As you can see in this simple example of iterative traveling, we've encountered similar events to software risks, feature creep, unexpected breakdowns beyond our control, and recovery plans.
在CMMI模型中,在严格定义级给出了一个软件风险管理的过程域,本文介绍的软件风险管理实现就是基于这个规范的。
In Defined level of CMMI criterion, there is a process area of risk management, which is the base of our software risk management implementation.
以此,他展开了一个关于如何最好地管理软件开发中的风险和不确定性的讨论。
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.
如果他们计划只是内部地使用公开源码软件而不准备发布产品,风险就是很小的。
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.
灵活的进化软件开发的风险是不连贯和不一致的终端结果。
The risks of flexible and evolutionary software development are incoherent and inconsistent end results.
在任何软件开发项目中,团队试图识别风险、发生的可能性、对整个项目的影响以及应急计划。
In any software development project, the team tries to identify risks, the probability of occurrence, impact to the overall project, and contingency plans.
于是你不得不去找一份更好的工作、经历跳槽、承担风险、编写软件、尝试新鲜事物、不再走老 路、去上学、去工作、去做事...
You have to find a better job, change jobs, take risks, write software, try new things, stop doing old things, go to college, work, act, do.
不幸的是,大多数应用程序开发人员对于他们生产的软件的风险透明度一无所知。
The sad fact is that most application developers have no idea whatsoever as to the risk profile of the software that they produce.
这些集成帮助减少与软件开发相关联的风险,并且令应用程序开发更可预测。
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.
更具体的说,使用RUP是为了减小软件开发相关的风险。
In particular, the RUP is used to mitigate the risks associated with software development.
作为一个需要被提炼,确定风险,可执行的软件构建和经验总结的结果,重要元素的设置可能会改变。
As a consequence of requirements being refined, risks identified, executable software built, and lessons learned, the set of significant elements may change.
随着世界变得越来越平,越来越小,忽视世界范围内潜在的软件用户的风险也越来越大。
As the world gets flatter and smaller, it becomes riskier to ignore the worldwide audience that exists for your software.
搜索和重用别人的软件可能有风险,但重用工程师是确定可用服务的专家,可以减少这些风险。
Searching for and reusing someone else's software can be risky, but reuse engineers mitigate these risks in that they are experts at locating available services.
这意味着越狱手机的用户可能无法体验软件改进,而且还要承受保修无效的风险。
That means owners of such phones might not be able to take advantage of software improvements, and they still run the risk of voiding their warranty.
每个MDM项目都有独特的困难和风险,在选择软件和实现战略时需要考虑这些因素。
Every MDM project will have its own unique set of challenges and risks that need to be considered for the selection of software and the implementation strategy.
他还说,现在的公司不再认为使用免费软件会带来风险了。
And companies no longer perceive free software as riskier, he adds.
软件项目管理中的风险也是众所周知的,尽管它通常在质量方面表示于编制的风险列表中。
Risk in software project management is also well-known, although it is usually expressed qualitatively in a documented risk list.
过去,IT界已经提出了,向商业相关利益方正确定义需求存在一定风险,但是还是假设交付软件的风险取决于这些需求。
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.
你的年收入还在增长,而客户也不愿意为软件而冒巨大的风险。
Your Annual Maintenance Revenues continue to grow, as clients cannot risk a problem with software that is mission critical and complex.
应用推荐