In which of the following phases does IT Architecture Development take place?

A typical IT project lifecycle moves through distinct stages, each with a specific purpose: agreeing on business direction, turning that direction into a detailed technical blueprint, building the solution against that blueprint, and finally releasing it. The system's IT Architecture — its conceptual, logical, and physical design — has to be fully worked out before any coding begins, because construction work implements an architecture rather than inventing one on the fly.

1. Setting the high-level business direction and IT goals — deciding WHAT the organisation wants to achieve, without yet specifying HOW the systems will be built.

2. Turning that direction into detailed technical work: requirements, cost and schedule estimates, and the IT Architecture itself — its conceptual, logical, and physical design — so that building the system has a concrete blueprint to follow.

3. Building and coding the system's components using the architecture and specifications already produced earlier.

4. Releasing the completed, tested solution into the live production environment.

Distinguishing the phases:

• Strategy Phase only fixes business direction and objectives; it precedes the detailed technical architecture work.

• Development Phase writes and assembles the actual code, consuming an already-finalised architecture rather than creating one.

• Deployment Phase releases the finished, tested product into production, well after the architecture has already been designed and built against.

Reasoning through the four offered phases this way, IT Architecture Development is best placed in the Planning Phase — the stage where the technical blueprint for the system is created, consistent with how standard IT project/SDLC frameworks sequence architecture design before coding and release.