All Free Software Engineering MCQs with Answers

• A. Software people don't understand their customers needs
• B. Changes are managed poorly
• C. Sponsorship is gained
• D. Users are resistant

Explanation: Gaining sponsorship is a positive project condition, not a warning sign.

• A. Changing customer requirements that are not reflected in schedule changes
• B. Technical difficulties that could not have been foreseen in advance
• C. Human difficulties that could not have been foreseen in advance
• D. All of the mentioned

Explanation: Late delivery can result from unplanned requirement changes, unforeseen technical problems, and unforeseen human or organisational…

• A. Formal approaches
• B. Formal, interpersonal procedures
• C. Informal, interpersonal procedures
• D. All of the mentioned

Explanation: Project coordination uses formal approaches as well as formal and informal interpersonal procedures.

• A. project delay
• B. poor quality work
• C. project failure
• D. all of the mentioned

Explanation: Unrealistic estimates can force rushed work and reduced quality, cause schedule delays, and ultimately lead to project failure.

• A. project control
• B. project management
• C. project planning
• D. project design

Explanation: Project managers plan, manage, and control projects, but project design is normally a technical or system-design responsibility rather…

• A. Practitioners
• B. Project managers
• C. Senior managers
• D. None of the mentioned

Explanation: Practitioners, such as analysts, designers, programmers, and testers, provide the technical skills needed to engineer the product.

• A. Problem solving
• B. Organization
• C. Motivation
• D. Project management

Explanation: Project management is people-intensive because it coordinates communication, motivation, conflict resolution, and work among team members…

• A. Controlled decentralized (CD)
• B. Democratic decentralized (DD)
• C. Controlled Centralized (CC)
• D. None of the mentioned

Explanation: A democratic decentralized team has no permanent leader, so leadership and decisions are shared among members.

• A. Software Project Manager's Plan
• B. Software Project Management Plan
• C. Software Product Management Plan
• D. Software Product Manager's Plan

Explanation: SPMP expands to Software Project Management Plan, the document that defines how a software project will be planned, monitored, controlled…

• A. Software Macroscopic schedule
• B. Software Project scheduling
• C. Software Detailed schedule
• D. None of the mentioned

Explanation: Software project scheduling distributes the estimated effort over the project duration and assigns it to specific engineering tasks.

• A. The difficulty of the problem to be solved
• B. High frustration caused by personal, business, or technological factors that causes friction among team members
• C. The degree of sociability required for the project
• D. The rigidity of the delivery date

Explanation: The degree of sociability required is not a standard project factor used to plan software team structure.

• A. Controlled decentralized (CD)
• B. Democratic decentralized (DD)
• C. Controlled centralized (CC)
• D. None of the mentioned

Explanation: A controlled decentralized team has a defined coordinating leader plus secondary leaders responsible for subtasks.

• A. End-users
• B. Client
• C. Project (technical) managers
• D. Senior managers

Explanation: End-users interact directly with the released software during production use, whereas clients and managers mainly specify, fund…

• A. asynchronous paradigm
• B. open paradigm
• C. closed paradigm
• D. synchronous paradigm

Explanation: The open paradigm combines the control and organization of a closed team with the creativity and innovation of a random team.

• A. Problem solving
• B. Managerial identity
• C. Influence and team building
• D. None of the mentioned

Explanation: Problem solving, managerial identity, and influence with team building are all recognized traits of effective project managers.

• A. Empirical
• B. Heuristic
• C. Analytical
• D. Critical

Explanation: Empirical, heuristic, and analytical methods are established approaches for estimating software cost.

• A. people
• B. product
• C. popularity
• D. process

Explanation: Effective software project management focuses on people, the product, and the development process.

• A. LOC
• B. FP
• C. Fuzzy Logic
• D. LOC and FP

Explanation: An indirect sizing approach measures software size through functionality, commonly using Function Points (FP).

• A. EV = (Sopt + 4Sm + Spess)/4
• B. EV = (Sopt + 4Sm + Spess)/6
• C. EV = (Sopt + 2Sm + Spess)/6
• D. EV = (Sopt + 2Sm + Spess)/4

Explanation: The three-point PERT estimate gives four times the weight to the most likely value, so the formula is (Sopt + 4Sm + Spess) / 6.

• A. LOC
• B. FP
• C. LOC and FP
• D. None of the mentioned

Explanation: A direct sizing approach measures a tangible implementation quantity, most commonly Lines of Code (LOC).