Software Development and Management

The analysis phase focuses on understanding and documenting requirements - what the software should accomplish. Option B describes the design phase (planning how), and option C describes the implementation phase (coding). Option D incorrectly combines analysis with design.

Explanation: To answer this question, we need to understand the phases of project development and the associated costs.

The typical phases of project development are Analysis, Design, Implementation, Maintenance, and Documentation.

• Analysis: This phase involves identifying the problem, gathering requirements, and analyzing the feasibility of the project. This phase usually incurs moderate costs, as it involves a lot of research and data gathering.

• Design: This phase involves designing the system architecture, developing the user interface, and creating detailed specifications. This phase typically incurs moderate costs, as it involves a lot of planning and design work.

• Implementation: This phase involves coding, testing, and integrating the system components. This phase typically incurs high costs, as it involves a lot of coding and testing work.

• Maintenance: This phase involves ongoing support, bug fixing, and system updates. This phase typically incurs high costs, as it involves ongoing maintenance and support work.

• Documentation: This phase involves creating user manuals, system documentation, and training materials. This phase typically incurs low costs, as it involves documentation work.

Therefore, the correct answer is D) Maintenance. This phase typically costs the most, as it involves ongoing maintenance and support work.

Composition in OOP means building complex objects by combining simpler objects. Option B best captures this - composing projects with different objects. Options A and C are wordplay on composed rather than the technical concept. Option D is incorrect since A and C are wrong.

The Delphi Technique is a structured communication method used to reach a consensus among a panel of experts. It involves multiple rounds of anonymous questionnaires, making it a key tool for securing expert judgment in project management.

A Work Breakdown Structure (WBS) decomposes the total project scope into smaller, manageable components. By systematically breaking down all work packages, the WBS ensures no project work is overlooked or omitted. A scope statement defines boundaries but doesn't guarantee completeness of all work items.

A scope statement clearly defines what is in scope and out of scope for the project, establishing explicit boundaries for completion. Scope verification is about acceptance, while scope definition is the process. The scope statement is the documented boundary that guides all scope decisions.

Inputs to project plan execution include the project plan, corrective action, and preventive action. The work authorization system is a tool or technique used during execution - it's the mechanism that authorizes work to begin, not an input itself. This makes A the correct answer as the item that is NOT an input.

Bar charts (Gantt charts) are widely used for performance reporting because they clearly show progress, status, and timelines in an easily understood visual format. Pareto diagrams, control charts, and RAMs are tools for quality management or planning, not standard performance reporting formats.

To answer this question, the user needs to have an understanding of the project management process and the steps involved in project closing.

Option A: Client appreciates your product. This statement is not necessarily a step in project closing. While it is important to have client satisfaction, it is not a defined step in the project closing process.

Option B: Client has accepted the product. This statement is a possible step in project closing. When the client accepts the final product, it signals the end of the project and the satisfaction of the client.

Option C: Lessons learned are documented. This statement is a possible step in project closing. It is important to document any lessons learned during a project to improve future projects and avoid making the same mistakes.

Option D: Archives are complete. This statement is a possible step in project closing. It is important to archive all project documents and deliverables to ensure that they are available for future reference.

Therefore, the correct answer is:

The Answer is: D (Archives are complete).

Alternate path flowcharts use icons/pictures to visually represent different process paths and decision points. They make process flow more intuitive than standard symbols. Process Flowcharts use standard symbols, Deployment charts show responsibility, and cross-functional maps show departments.

Project Milestones define key deliverables with target dates throughout a project timeline. Goal Statements state objectives, Project Scope defines boundaries, and Problem Statements describe issues - none provide detailed step-by-step plans with dates.

The CTQ/Project Y matrix helps identify the best measurable metrics for Critical to Quality (CTQ) characteristics. While CTQs themselves are customer requirements, this matrix specifically helps determine how to measure each CTQ effectively. It bridges the gap between vague customer needs and specific, measurable metrics (Project Y) that can be tracked and improved.

The Define phase in Six Sigma DMAIC focuses on clearly defining the problem and project scope. Its three key deliverables are: (1) Project Charter - documenting the problem, goal, scope, and team; (2) CTQs (Critical to Quality) - translating customer needs into measurable requirements; (3) COPIS diagram - mapping the process at a high level from Customer through Supplier. These form the foundation for the remaining phases.

DMAIC phases: Define (the problem), Measure (current performance), Analyze (root causes), Improve (develop and implement solutions), Control (sustain gains). Brainstorming solutions is the core activity of the Improve phase. Control (A) focuses on monitoring. Measure (B) is data collection. Analyze (C) identifies causes but doesn't generate solutions.