【正文】 ement (SEI, 2020) principles, and six new CSD principles grouped into two focus areas: ? Effective collaboration includes level of trust, cultural sensitivity, collaborative munication, and effective interaction and focuses on building, maintenance, and effective use of ongoing relationships. ? Effective management includes aligned management support and responsibility for risk management and emphasizes the need to extend management policies, and risk management in particular, into the collaborative domain. Table 4 Risk Management Principles for Collaborative Software Development Risk Management Principles for Collaborative Software Development Domain Risk Management Focus Risk Management Principles RMMM Requirement Traditional risk management Riskaware orientation Global perspective Forwardlooking view Visualize the systems context Anticipate uncertainties Communication Open munication Enable effective munication Value the individual voice Management Integrated management Continuous process Make risk management integral Manage risks as an ongoing activity Keep the RMMM plan current Teambased/distributed risk management Shared objectives Shared product vision Create a product vision based on mon purpose, shard ownership, and collective mitment Shared development effort Work together to instantiate the shared vision Focus on joint results Effective teamwork Team processes Work cooperatively to achieve a mon goal Pool talent, skills, and knowledge Team risk Use consensusbased processes among team members Use consensusbased processes between customer and supplier Use consensusbased process among collaborating teams Collaborative risk management Effective collaboration Level of trust Build and maintain trust Cultural sensitivity Build awareness of cultural differences Collaborative munication Anticipate and mitigate interanizational and intercultural munication risks Effective interaction Work together to utilize all available resources Effective management Aligned management support Add new management function (perhaps distributed) to coordinate and support interanizational efforts Responsibility for risk management Define a layered risk management plan to avoid dangers and pitfalls of lack of ownership and authority In addition, one teambased/distributed principle (team risk) is modified to include consensus among collaborating teams. Ⅴ A FRAMEWORK FOR EFFECTIVE RISK MANAGEMENT FOR CSD: A LAYERED APPROACH The characteristics of collaborative software environments, together with the lack of a clear, universally accepted central authority, argue strongly that a new risk management strategy specifically directed at collaborative software development is required. Appropriate planning and welldefined policies, roles, and responsibilities form the foundation of an effective risk management framework, and a collaborationaware risk management plan bees a critical tool in implementing the strategy. This new plan must address not only the concerns related to traditional and distributed development, but also the risks that are specific to collaborative development across anizational, national, cultural, and/or linguistic borders. An effective risk management plan should be based on collaborativerisk management principles and should provide clear definition of decisions, actions, and responsibilities related to the risk management functions defined in Table 4. A collaborationaware risk management plan must (1) address traditional intraanization risk identification and management in collaborating agencies。 Nidumolu, 1996). From the literature (Pressman, 2020), risks are classified in several dimensions, such as the origin of the risk (nature and cause), the definiteness (from nearcertain to highly unlikely), the anticipated consequences (degree of risk), and the aspects affected. Ⅲ . COLLABORATIVE SOFTWARE DEVELOPMENT AND RISK MANAGEMENT Today39。 field research: trust, culture, and collaborative munication. Ⅱ RISK MANAGEMENT IN TRADITIONAL SOFTWARE ENGINEERING Traditional software engineering practices were developed to support project teams formed by functional subteams or crossfunctional teams operating under a single central authority. These practices have defined the scope and the elements of traditional risk management. Risk in general is denned by uncertainty and loss possibly imputed or indirect (., loss of reputation) rather than directly measurable (Gotterbarn, 2020。 untrusted channels SD/technical resources Single set of resources One set of resources per partner plus shared resources Risk management plan Single risk management plan with clear management Multiple risk management plans No central authority for risk mitigation Work practices Known set of anizational and professional standards Some variation in anization and professional standards Social amp。 capabilities and actions. Without a good relationship, all of the other systems ... cannot function effectively. (Handfield and Nichols, 1999) Trust can in part pensate for deficiencies of IT structure and partners39。 understanding cultural differences is the first step toward mitigating the disabling effe。 (4) drive incremental modification of policies, processes, and activities as needed。 munication Technical platform amp。Risk Management for Collaborative Software Development (管理信息系統(tǒng)課程作業(yè) 蔣艷輝 學(xué)號(hào)： 2020310050 ) Abstract: Collaborative software development involving multiple anizational units, often spanning national, language, and cultural boundaries, raises new challenges and risks that can derail software development projects even when traditional risk factors are being controlled. This article presents a framework th