The Unified Modeling Language is a standard graphical language for modeling object-oriented software（）can show the behavior of systems in terms of how objects interact with each other.

（）is a property of object-oriented software by which an abstract operation may be performed in different ways in different classes.

The strategies for handling risk comprise of two main types: negative risks, and positive risks. The goal ofthe plan is to minimize threats and maximize opportunities. When dealing with negative risks, there are three main response strategies（）,rransfer ,Mitigate.

The （）process ascertains which risks have the potential of affecting the project and documenting the risks＇ characteristics.

Developing the project schedule is often an iterative process. It determines the planned start and finish dates for project activities and milestones. Schedule development can require the review and revision of duration estimates and resource estimates to create an approved project schedule that can serve as a baseline to（）progress.

Estimating activity durations uses information on activity scope of（），required resource types, estimated resource quantities, and resource calendars.

Project work packages are typically decomposed into smaller components called activities to provide a basis for（）scheduling, executing, and monitoring and controllingthe proj ect work.

Define Activities is the process ofidentifying the specific actions to be performed toproduce the（）

During the project, requirements change for a variety of reasons. As needs change and as work proceeds, additional requirements are derived and changes may have to be made to the existing requirements. It is essential to manage these additions and changes efficiently and effectively. To effectively analyze the impact of the changes, it is necessary that the source of each requirement is known and the rationale for any change is documented. The project manager may, however, want to track appropriate measures of requirements volatility to judge whether new or revised（）are necessary.

The receiving activities conduct analyses of the requirements with the requirements provider to ensure that a compatible, shared understanding is reached on the meaning of the requirements. The result ofthis analysis and dialog is an（）set of requirements.