软件风险管理的数据库模型

风险管理是软件项目开发过程中一个关键过程域,直接影响到软件的质量、进度及资金投入,决定项目的成败。目前,风险管理原始数据从本质上来源于领域专家已有经验,具有较大的主观性,并且各个项目开发客观条件都不尽相同,不能完全借鉴。本文从风险管理过程出发,总结CMMI软件风险管理模型,建立风险管理数据库模型,将不断修正的数据积累值作为软件风险的识别标准,以保证风险识别的客观性。     

Can software risk management improve system development: an exploratory study

Software risk management can be defined as an attempt to formalise risk oriented correlates of development success into a readily applicable set of principles and practices. Earlier research suggests that it can reduce the likelihood of a system failure. Using a survey instrument we investigate this claim further. The investigation addresses the following questions: (1) which characteristics of risk management practices; and (2) which other environmental and process factors (such as development methods, manager's experience) relate to improved performance in managing software risks? Our findings support in general the claim that the use of risk management methods improves system development performance. Yet, little support was found for the claim that specific risk management methods are instrumental in attacking specific software risks. Overall, risks are better managed with combined measures of having experienced project managers, selecting a correct project size, and investing in and obtaining experience in risk management deliberations.     

浅谈信息系统项目的风险管理

随着信息技术的高速发展,各种信息系统项目发展迅速。然而,类似建设工程项目一样,信息系统项目也存在各种不确定因素。在项目实施过程中,随时都有可能出现风险,从而产生各种问题。所以,我们需要做好信息系统项目的风险管理。在经过风险管理计划的编制、风险识别、定性和定量风险分析之后,笔者认为项目实施中最主要的风险有:项目频繁变更、系统功能和质量达不到要求、团队效率低下等,需要对其进行重点管理,采取相应的应对措施。对于其他相对次要的风险,也要给予一定的关注。最后,做好风险监督与控制。鉴于风险管理的重要性,我们必须高度重视,做到理论与实际相结合,真正做好信息系统项目的风险管理。     

软件项目风险评估实践

论文旨在说明软件风险评估在软件项目管理中所起的重要作用以及软件风险评估的具体方法。结合笔者的实践经验,从风险管理引出风险评估,并详细描述了风险识别、风险分析以及确定风险优先级的步骤和方法。     

Putting risk management into practice

The authors use an SEI designed road map as a guide to discussing effective and ineffective risk management methods based on six years' experience with software intensive DoD programs. These programs followed the SEI approach of continuous and team risk management, selecting processes and methods that would best fit their work cultures     

Categorization of risk factors for distributed agile projects

ContextOrganizations combine agile approach and Distributed Software Development (DSD) in order to develop better quality software solutions in lesser time and cost. It helps to reap the benefits of both agile and distributed development but pose significant challenges and risks. Relatively scanty evidence of research on the risks prevailing in distributed agile development (DAD) has motivated this study.ObjectiveThis paper aims at creating a comprehensive set of risk factors that affect the performance of distributed agile development projects and identifies the risk management methods which are frequently used in practice for controlling those risks.MethodThe study is an exploration of practitioners’ experience using constant comparison method for analyzing in-depth interviews of thirteen practitioners and work documents of twenty-eight projects from thirteen different information technology (IT) organizations. The field experience was supported by extensive research literature on risk management in traditional, agile and distributed development.ResultsAnalysis of qualitative data from interviews and project work documents resulted into categorization of forty-five DAD risk factors grouped under five core risk categories. The risk categories were mapped to Leavitt’s model of organizational change for facilitating the implementation of results in real world. The risk factors could be attributed to the conflicting properties of DSD and agile development. Besides that, some new risk factors have been experienced by practitioners and need further exploration as their understanding will help the practitioners to act on time.ConclusionOrganizations are adopting DAD for developing solutions that caters to the changing business needs, while utilizing the global talent. Conflicting properties of DSD and agile approach pose several risks for DAD. This study gives a comprehensive categorization of the risks faced by the practitioners in managing DAD projects and presents frequently used methods to reduce their impact. The work fills the yawning research void in this field.     

Test-Driven Development for Spreadsheet Risk Management

Spreadsheet technology is central to the functioning of the financial sector, but professionally created spreadsheets have a high level of error, which highlights the need for innovative supporting processes and tools. The current global financial crisis will likely accelerate this need because anticipated regulation will require novel, innovative risk management methods and technologies that cover development, risk assessment, review, and other spreadsheet activities. These methods will need to be easy to understand and use and will have to serve multiple stakeholders' needs. Test-driven spreadsheet development (TDSD) is one such method. TDSD provides an ideal fit with existing market-leading spreadsheet management processes and can assist managers and auditors in the assessment and control of spreadsheet risk.     

Vendor Risk Assessment

This article seeks to draw the attention of the executive management of enterprises to the growing importance of vendor risk assessments. Given that modern enterprises outsource non-core processes and operations to business partners and vendors, it is immensely important that a thorough risk assessment is performed of all control aspects and at all times—before the outsourcing and continuing risk assessments. Regulators hold enterprises responsible for data leakages by business partners and vendors. Therefore, enterprises need to ensure that appropriate metrics for measurement of vendor and business partner performance is well laid out in the agreements with the vendors and business partners. Indicative reference framework such as COBIT 5 framework for vendor management, how we manage a cloud service provider and key risk assessment processes have been provided to assist the executive management. Third party audits of businesses and operations of key vendor and business partners need to be conducted.     

Product Innovation: The Pitfalls of Entrapment

This article examines the concept of entrapment and compares it with Yang and Dougherty's (1993) theory of anchoring, each within the framework of innovation management. It is argued that entrapment can occur for different reasons. Among these are the need of executives to defend and confirm their initial decisions and judgement; the desirability of avoiding the waste of sunk costs; the possibility of providing an opportunity for the project to succeed; the treatment of negative feedback as a learning experience (a cue to revise inputs rather than cancel them); and the social costs and benefits relating to image and reputation which are at risk if a project is terminated. Suggestions have been made as to how entrapment might be avoided by making organisational adjustments.     

基于先验知识的缺损数据研究

缺损数据是企业在实现信息化管理过程中需要重视和处理的重点问题之一。以粮食企业信息化管理系统为实际操作的样本,在其关系型数据库中,属性之间的相互关联关系(称之为先验知识或领域知识)为修正和填充缺损数据提供了大量有益的帮助。采用了基于先验知识的缺损数据处理方法,重点针对系统中的离散属性的缺损数据进行了研究．对该系统中的缺损数据的处理有着很强的实用性,并为其他类似问题的解决提供了可借鉴的方案。     

小型水库运行管理问题与对策

我国小型水库量多面广,加强小型水库运行管理对防洪保安意义重大。基于小型水库除险加固遗留问题和典型案例、安全运行专项督察中发现的主要问题、雨水情测报和监测设施现状等数据,分析小型水库在除险加固、运行管理体制、管护能力、信息化建设等方面存在的不足之处及原因,结合全国小型水库管理体制改革样板县创建经验,从提升除险加固标准、消除安全隐患,理顺管理机制、创新管护模式,强化责任落实、提高管护能力,加强科技应用、提升智慧化管理水平等方面提出建议和对策,并以重庆市永川区为实例,总结小型水库运行管理经验和智慧水利系统情况,为保障全国各地小型水库安全运行提供参考。     

高校计算机类实验室管理的实践与探讨

计算机类实验室的管理是一项综合性较强的工作。管理人员不仅需要具备扎实的技术知识,丰富的排除故障的经验,还要掌握一定的管理技巧。文章主要讨论如何科学管理计算机类实验室,使实验室管理不再是一项体力劳动,而变得更加科学、高效、规范。     

Risk Management in a Disaster Management Context

This paper discusses how the adoption of a systematic risk management framework can enhance disaster management. In the analysis of risk, a focus on the interactions between sources of risk and elements at risk, rather than a pre-occupation with hazards, adds more value to management. Vulnerability is the crucial modifier of consequences and, as such, its analysis highlights critical areas and opportunities for developing effective intervention strategies. Risk communication processes based on community involvement need to underpin the development and application of evaluation criteria to determine which risk treatments will be implemented. Closing considerations reflect on how risk management may be used within public administration to re-define emergency management service provision. The paper concludes that Emergency Risk Management provides a framework which, by focusing on managing community exposure to major risks, facilitates the identification and implementation of intervention options which address socially significant problems.     

高校计算机类实验室管理的实践与探讨

计算机类实验室的管理是一项综合性较强的工作。管理人员不仅需要具备扎实的技术知识。丰富的排除故障的经验，还要掌握一定的管理技巧。文章主要讨论如何科学管理计算机类实验室，使实验室管理不再是一项体力劳动，而变得更加科学、高效、规范。     

IMS 中基于策略QoS 管理模型

IMS（IP多媒体子系统）给客户带来丰富的多媒体体验的同时,也对服务质量（QoS）管理提出了更高的要求,即针对不同用户定制的不同服务,网络运营商应该制定差异化的策略进行QoS管理。3GPP定义了基于策略的QoS管理框架,但这个框架只是逻辑上的架构,没有定义具体物理实施的方案。对基于策略QoS管理模型进行了分析,在参照3GPP定义的标准基础上,提出了一种管理模型的实现方案,设计并实现了该模型中两个关键服务器策略决策服务器（PDF）和策略执行服务器（PEP）。经过测试,两个服务器能互相配合,正确完成查询策略信息,做出策略决策,执行带宽请求预留、QoS等级协商功能,为网络运营商提供了参考。     

Components of software development risk: how to address them? Aproject manager survey

Software risk management can be defined as an attempt to formalize risk oriented correlates of development success into a readily applicable set of principles and practices. By using a survey instrument we investigate this claim further. The investigation addresses the following questions: 1) What are the components of software development risk? 2) how does risk management mitigate risk components, and 3) what environmental factors if any influence them? Using principal component analysis we identify six software risk components: 1) scheduling and timing risks, 2) functionality risks, 3) subcontracting risks, 4) requirements management, 5) resource usage and performance risks, and 6) personnel management risks. By using one-way ANOVA with multiple comparisons we examine how risk management (or the lack of it) and environmental factors (such as development methods, manager's experience) influence each risk component. The analysis shows that awareness of the importance of risk management and systematic practices to manage risks have an effect on scheduling risks, requirements management risks, and personnel management risks. Environmental contingencies were observed to affect all risk components. This suggests that software risks can be best managed by combining specific risk management considerations with a detailed understanding of the environmental context and with sound managerial practices, such as relying on experienced and well-educated project managers and launching correctly sized projects     

Measuring the Deliverable and Impressible Dimensions of Service Experience

Service innovation has become a priority within the field of innovation management and is increasingly focused on creating memorable experiences that can result in customer loyalty. Studies of experience design suggest individual service elements to be managed when staging an experience, whereas conceptual models in the literature emphasize the holistic way in which an experience is perceived. In short, service experience is greater than the sum of its parts. Therefore, successful innovation management requires the ability to understand and measure the mechanisms by which service innovations impact customers' experiences. Our research addresses this need by identifying dimensions of service experience and developing a tool for their measurement. Using a three stage process of systematic literature review, rigorous scale development and reduction, and validation, we identify six dimensions of the service experience and develop scales to measure each one. This results in a model of service innovation that highlights the levers through which a company's service innovation efforts can result in memorable experiences and ultimately new service success.     

A risk management ontology for Quality-by-Design based on a new development approach according GAMP 5.0

A new approach to the development of a risk management ontology is presented. This method meets the requirements of a pharmaceutical Quality by Design approach, good manufacturing practice and good automated manufacturing practice. The need for a risk management ontology for a pharmaceutical environment is demonstrated, and the term “ontology” is generally defined and described with regard to the knowledge domain of quality risk management.To fulfill software development requirements defined by good manufacturing practice regulations and good automated manufacturing practice 5.0 for the novel development approach, we used a V-model as a process model, which is discussed in detail. The development steps for the new risk management ontology, such as requirement specification, conceptualization, formalization, implementation and validation approach, are elaborated.     

基于量子门线路神经网络的射击试验安全风险评估

为提高射击试验安全,在分析现有安全管理机制基础之上,结合射击试验安全管理实践经验,采用量子旋转门控制量子位的翻转与相位的偏转,建立风险评估指标模型,通过仿真实验来验证文章所采取研究方法的有效性,并与传统BP神经网络性能进行风险评估精度的比较;通过分析及比较,文章构建的量子门线路模型降低了安全试验相关数据处理的复杂度,对射击试验安全风险评估的收敛速度更高,提高了对射击试验过程中安全风险的预测精度,为射击试验相关管理人员评估试验危险及制定措施提供了理论依据.     

Examining mobile banking user adoption from the perspectives of trust and flow experience

Due to the high perceived risk and poor experience associated with using mobile banking, it is critical for service providers to build users’ trust and improve their experience. Integrating both perspectives of trust and flow experience, this research examined the factors affecting mobile banking user adoption. The results indicate that structural assurance is the main factor affecting trust, whereas ubiquity and perceived ease of use are the main factors affecting flow experience. Trust has a significant effect on flow experience, and both factors determine usage intention, which in turn affects actual usage. Thus mobile service providers need to concern both trust and flow experience to facilitate user adoption and usage of mobile banking services.