Haha
A wise person once said, "All things are possible, but not all things are profitable."
Information systems development projects are subjected to at least three interrelated feasibility types—operational feasibility, technical feasibility, and economic feasibility.
Operational feasibility is the measure of how well particular information systems will work in a given environment. Just because XYZ Corporation's payroll clerks all have PCs that can display and allow editing of payroll data doesn't necessarily mean that ABC Corporation's payroll clerks can do the same thing. Part of the feasibility analysis study would be to assess the current capability of ABC Corporation's payroll clerks in order to determine the next best transition for them.
Technical feasibility A large part of determining resources has to do with assessing technical feasibility. It considers the technical requirements of the proposed project. The technical requirements are then compared to the technical capability of the organization. The systems project is considered technically feasible if the internal technical capability is sufficient to support the project requirements.
The analyst must find out whether current technical resources can be upgraded or added to in a manner that fulfills the request under consideration. This is where the expertise of system analysts is beneficial, since using their own experience and their contact with vendors they will be able to answer the question of technical feasibility.
Requirements determination is the general data-gathering activity done during analysis. It has four sub-activities—requirements anticipation, requirements elicitation, requirements assurance, and requirements specification. One of the earliest research articles to deal with understanding the requirements determination activity was presented by Naumann, Davis, and McKeen and later expanded by Vitalari's work. Together they have identified four sub-activities within the
Information systems development projects are subjected to at least three interrelated feasibility types—operational feasibility, technical feasibility, and economic feasibility.
Operational feasibility is the measure of how well particular information systems will work in a given environment. Just because XYZ Corporation's payroll clerks all have PCs that can display and allow editing of payroll data doesn't necessarily mean that ABC Corporation's payroll clerks can do the same thing. Part of the feasibility analysis study would be to assess the current capability of ABC Corporation's payroll clerks in order to determine the next best transition for them.
Technical feasibility A large part of determining resources has to do with assessing technical feasibility. It considers the technical requirements of the proposed project. The technical requirements are then compared to the technical capability of the organization. The systems project is considered technically feasible if the internal technical capability is sufficient to support the project requirements.
The analyst must find out whether current technical resources can be upgraded or added to in a manner that fulfills the request under consideration. This is where the expertise of system analysts is beneficial, since using their own experience and their contact with vendors they will be able to answer the question of technical feasibility.
Requirements determination is the general data-gathering activity done during analysis. It has four sub-activities—requirements anticipation, requirements elicitation, requirements assurance, and requirements specification. One of the earliest research articles to deal with understanding the requirements determination activity was presented by Naumann, Davis, and McKeen and later expanded by Vitalari's work. Together they have identified four sub-activities within the