Beruflich Dokumente
Kultur Dokumente
BIS310: Week 4
Feasibility analysis
Feasibility is the measure of how beneficial or practical the development of an information system will be to an organization Feasibility analysis is the process by which feasibility is measured.
BIS310: Week 4
BIS310: Week 4
analysis)
BIS310: Week 4
Operational Feasibility
Is the problem worth solving, or will the solution to the problem work? How well would the candidate solution be received from management, system users, and organization perspective? (political) Is the solution compliant with laws and regulations? (legal)
BIS310: Week 4
Technical Feasibility
Is the proposed technology or solution practical? Do we currently possess the necessary technology? Do we possess the necessary technical expertise, and is the schedule reasonable?
BIS310: Week 4
Schedule Feasibility
Given our technical expertise, are the project deadlines reasonable?
BIS310: Week 4
Economic Feasibility
How Much Will the System Cost? What Benefits Will the System Provide?
Tangible benefits Intangible benefits
BIS310: Week 4
BIS310: Week 4
BIS310: Week 4
BIS310: Week 4
BIS310: Week 4
BIS310: Week 4
Select the one design strategy that is most likely to result in the desired information system Feasibility Matrix
BIS310: Week 4
A consolidation of all system models, discovery prototypes, and supporting documentation is sometimes called a requirements statement.
All elements of the requirements statement are stored in the repository, but most systems analysts find it useful to keep a printed copy of that documentation for reference and reporting.
BIS310: Week 4
BIS310: Week 4
BIS310: Week 4
BIS310: Week 4
Factual Format I. Introduction II. Methods and procedures III. Facts and details IV. Discussion and analysis of facts and details V. Recommendations VI. Conclusion
Administrative Format Introduction Conclusions and recommendations Summary and discussion of facts and details Methods and procedures
BIS310: Week 4 The abstract or executive summary is a one- or twopage summary of the entire report. The introduction should include four components: purpose of the report, statement of the problem, scope of the project, and a narrative explanation of the contents of the report. The methods and procedures section should briefly explain how the information contained in the report was developed for example, how the study was performed or how the new system will be designed. The bulk of the report will be in the facts section. This section should be named to describe the type of factual data to be presented (e.g., Existing Systems Description, Analysis of Alternative Solutions, or Design Specifications). The conclusion should briefly summarize the report, verifying the problem statement, findings, and recommendations.
BIS310: Week 4
BIS310: Week 4
Formal Presentations
In order to communicate information to the many different people involved in a systems development project, a systems analyst is frequently required to make a formal presentation.
Formal presentations are special meetings used to sell new ideas and gain approval for new systems. They may also be used for any of the purposes in the margin. In many cases, a formal presentation may set up or supplement a more detailed written report.
BIS310: Week 4
Step 2: Organize your presentation around the allotted time (usually 30 to 60 minutes).
BIS310: Week 4
BIS310: Week 4
Typical Outline and Time Allocation for an Oral Presentation I. Introduction (1/6) 1. Background 2. Problem Statement 3. Work completed to date
II. Body of Presentation (2/3) 1. Summary of existing systems and cause-effect analysis 2. Summary description of proposed systems 3. Feasibility study (analysis of alternatives) 4. Proposed schedule to complete project III. Conclusion (1/6) 1. Questions and concerns from the audience 2. Call to action (request for authority whatever you require to continue the systems development project)