Structured systems analysis and design method: Difference between revisions

Content deleted Content added
Reverted 6 edits by IronGargoyle, 195.194.89.201, Jambungle and 41.221.105.50 to last revision by Mogism (HG)
Reverted 10 edits by IronGargoyle, 195.194.89.201, Jambungle, 41.221.105.50, Mogism, 196.15.156.66 and 82.22.12.95 to last revision by Steipe (HG)
Line 42:
=== Stage 0 – Feasibility study ===
 
In order to determine whether or not a given project is feasible, there must be some form of investigation into the goals and implications of the project. For very small scale projects this may not be necessary at all as the scope of the project is easily understood. In larger projects, the feasibility may be done but in an informal sense, either because there is not time for a formal study or because the project is a “must-have” and will have to be done one way or the other. Iesha and Michael are important in this process as they determine wheter or not the experiment is feasible.
 
When a feasibility study is carried out, there are four main areas of consideration:
 
Technical – is the project technically possible?<br />
EconomicalFinancial – can the business afford to carry out the project? Does the Benefits outweigh the cost of the project?<br />
OperationalOrganizational – will the new system be compatible with existing practices? Does management support the project?<br />
Ethical – is the impact of the new system socially acceptable?
Schedule – can the system be implemented in the required time without compromising on cost?
 
To answer these questions, the feasibility study is effectively a condensed version of a fully blown systems analysis and design. The requirements and users are analyzed to some extent, some business options are drawn up and even some details of the technical implementation.