A. Performance risk
B. Cost risk
C. Support risk
D. Schedule risk
A. Design & Test specification
B. Source code
C. Log information
D. All of the mentioned
Explanation: A configuration item is an approved and accepted deliverable, changes have to be made through formal procedure.
A. B.Beizer
B. Rajiv Gupta
C. B.W.Bohem
D. Gregg Rothermal
Explanation: Barry Boehm introduced a hierarchy of software estimation models bearing the name COCOMO, for COnstructive COst MOdel
A. Compartmentalization
B. Defined milestones
C. Defined responsibilities
D. Defined outcomes
Explanation: These responsibilities are domain specific.
A. people
B. product
C. popularity
D. process
Explanation: Effective software project management focuses on the four P’s: people, product, process, and project.
A. Codeline
B. Configuration control
C. Version
D. Workspace
Explanation: In configuration control changes are managed and all versions of components are identified and stored for the lifetime.
A. Product risk
B. Project risk
C. Business risk
D. Programming risk
Explanation: Risks that affect the quality or performance of the software being developed.