Software Management

A. Project size
B. Planning process
C. Project complexity
D. Degree of structural uncertainty

Explanation: As size increases, the interdependence among various elements of the software grows rapidly.

A. team
B. project
C. customers
D. project manager

Explanation: The quality plan should set out the desired software qualities and describe how these are to be assessed

A. Project Management
B. Manager life cycle
C. Project Management Life Cycle
D. All of the mentioned

Explanation: A proven methodical life cycle is necessary to repeatedly implement and manage projects successfully.

A. Planning process
B. Software scope
C. External hardware
D. Project complexity

Explanation: Functions described in the statement of scope are evaluated and in some cases refined to provide more detail prior to the beginning of estimation.

A. Internship management
B. Change management
C. Version management
D. System management

Explanation: Configuration management policies and processes define how to record and process proposed system changes, how to decide what system components to change, how to manage different versions of the system and its components, and how to distribute changes to customers.

A. Keeg overall costs within budget
B. Delivering the software to the customer at the agreed time
C. Maintaining a happy and well-functioning development team
D. Avoiding customer complaints

Explanation: Projects need to be managed because professional software engineering is always subject to organizational budget and schedule constraints.

A. Process introduction
B. Process analysis
C. De-processification
D. Process distribution

Explanation: The current process is assessed, and process weaknesses and bottlenecks are identified.