Answer & Solution
Answer: Option
D
Solution:
The correct answer is D: data-flow diagrams.
Let's break down why a feasibility document *doesn't* usually include data-flow diagrams:
* What is a feasibility document?
It's a report that assesses whether a proposed project is possible, practical, and worthwhile to undertake. Think of it as a preliminary investigation.
* What should be included in a feasibility document?
A feasibility study outlines the project's purpose, problems it addresses, and identifies potential solutions. It also includes a high-level assessment of available technologies and resources, costs, benefits, and a recommended solution.
* Why *not* data-flow diagrams (DFDs)?
DFDs are used to graphically represent the flow of data within a system. They are typically used during the design phase of a project, *after* the feasibility has been established.
The feasibility study happens early in the Software Development Lifecycle (SDLC). A feasibility document aims to determine if a proposed project is worth pursuing. While it *might* mention the high-level data requirements, it doesn't go into the detailed data-flow mapping that DFDs provide. DFDs are a design tool.
* Let's look at the other options:
* A: project name: Essential for identifying the project.
* B: problem descriptions: Clearly defines the issues the project aims to solve.
* C: feasible alternative: Presents possible solution approaches.
Therefore, a feasibility document should contain all of the listed elements except a data-flow diagram, which is a detailed design tool and is created after the project's feasibility is determined.
