Which set describes typical lifecycle phases and activities in a MIPC project?

• A. Only design and implement.
• B. Maintenance is not part of the lifecycle.
• C. Only deployment and testing.
• D. Requirements, design, implementation, testing, deployment, and maintenance; activities: stakeholder analysis, architecture decisions, coding standards, test plans, deployment automation, and monitoring.

Answer: (D)

A complete software project lifecycle for MIPC projects spans from gathering requirements to ongoing maintenance, with purposeful work in each phase. The best description includes requirements, design, implementation, testing, deployment, and maintenance, plus activities that support quality and operations: stakeholder analysis to understand who is affected and what they need; architecture decisions to shape the system’s structure; coding standards to keep the codebase consistent and maintainable; test plans to ensure quality and catch defects early; deployment automation to make releases reliable and repeatable; and monitoring to observe how the system behaves in production and inform improvements. This combination reflects both the sequence of work and the governance needed to deliver a usable, maintainable product over time. Other options miss essential pieces, such as excluding design or maintenance, or limiting activities to only a subset of phases, thus failing to capture the full lifecycle.