1. Provide an overview of the proposed system, including costs and benefits, with an explanation of the various cost-benefit types and categories.
2. Develop an economic feasibility analysis, using payback analysis, ROI, and present value (assume a discount rate of 10%).
3. Prepare a context diagram and diagram 0 for the new system.
4. Provide a brief explanation of the various alternatives that should be investigated if development continues, including in-house development and any other possible strategies.

Based on your earlier recommendations, New Century decided to continue the systems development process for a new information system. Now, at the end of the systems analysis phase, you are ready to prepare a system requirements document and give a presentation to the New Century associates. Many of the proposed system’s advantages were described during the fact-finding process. Those include smoother operation, better efficiency, and more user-friendly procedures for patients and New Century staff.
You also must examine tangible costs and benefits to determine the economic feasibility of several alternatives. If New Century decides to go ahead with the development process, the main options are to develop the system in-house or purchase a vertical package and configure it to meet New Century’s needs. You have studied those choices and put together some preliminary figures. You know that New Century’s current workload requires six hours of office staff overtime per week at a base rate of $15 per hour. In addition, based on current projections, New Century will need to add another full-time clerical position in about six months. Neither the overtime nor the additional job will be needed if New Century implements the new system. The current manual system also causes an average of three errors per day, and each error takes about 20 minutes to correct. The new system should eliminate those errors.

You estimate that by working full-time you could complete the project in about 12 weeks. Your consulting rate, which New Century agreed to, is $35 per hour. If you design the new system as a database application, you can expect to spend about $2,500 for a networked commercial package. After the system is operational and the staff is trained, New Century should be able to handle routine maintenance tasks without your assistance. As an alternative to in-house development, a vertical software package is available for about $12,000. The vendor offers a lease-purchase package of $4,000 down, followed by two annual installments of $4,000 each. If New Century buys the package, it would take you about four weeks to install, configure, and test it, working full-time. The vendor provides free support during the first year of operation, but then New Century must sign a technical support agreement at an annual cost of $600. Although the package contains many of the features that New Century wants, most of the reports are pre-designed and it would be difficult to modify their layouts. No matter which approach is selected, New Century probably will need you to provide about 10 hours of initial training and support each week for the first three months of operation. After the new system is operational, it will need routine maintenance, file backups, and updating. These tasks will require about four hours per week and can be performed by a clinic staff member. In both cases, the necessary hardware and network installation will cost about $12,500. In your view, the useful life of the system will be about five years, including the year in which the system becomes operational. You are scheduled to deliver a presentation to New Century next week, and you will submit a system requirements document at that time. To prepare yourself, you reviewed the skills described in Part A of the Systems Analyst’s Toolkit, and you listed tips to remember, as follows:

Presentation Tips

• Use suitable visual aids.
• Use presentation software, if possible.
• Distribute handouts before, during, or after the presentation.
• Follow the guidelines in Part A of the Systems Analyst’s Toolkit.
• Keep your presentation to 30 minutes, including 5 minutes for questions.

System Requirements Document Tips

• Follow the guidelines in Part A of the Systems Analyst’s Toolkit.
• Include charts, graphs, or other helpful visual information in the document. Also include other material to help the audience understand the new system and decide on the next step.
• Spell check and carefully proofread the entire document.
• For readability, try to keep the Flesch Reading Ease score above 60, and aim for a Flesch- Kincaid Grade Level of 8.0 to 9.0.