Scope of system study: which phases are included in a typical system study project before implementation?

Introduction / Context:
A system study investigates what a system should do (analysis) and how it should be organized logically (design) before building and deploying it (implementation). This separation reduces risk and clarifies requirements.

Given Data / Assumptions:

• Analysis elicits requirements, constraints, current-state processes, and data needs.
• Design organizes solutions logically (data models, process models, architecture choices).
• Implementation is a subsequent build/deploy phase, not part of the initial study itself.

Concept / Approach:
The study phase culminates in specifications that guide development. Proceeding to implementation without rigorous analysis/design often leads to rework and misalignment with stakeholder needs.

Step-by-Step Solution:
1) Define the boundaries of “system study.”2) Map activities: requirements capture (analysis) then solution structuring (design).3) Exclude implementation as a later project phase.4) Choose the option that includes both analysis and design.

Verification / Alternative check:
Many methodologies (waterfall, iterative) maintain distinct analysis/design artifacts prior to construction.

Why Other Options Are Wrong:
Focusing on a single phase is incomplete; listing implementation conflates study with build.

Common Pitfalls:
Skipping design detail (e.g., ignoring data integrity rules) and pushing unresolved questions into development.

Final Answer:
Both system analysis and system design are included in the system study project prior to implementation.