Capstone Prospectus

Paper details: ntroduction: The prospectus is the capstone proposal that details the goals and expectations for your project. It contain" rel="nofollow">ins in" rel="nofollow">information in" rel="nofollow">includin" rel="nofollow">ing the project plan, expectations, rationale, methods, timelin" rel="nofollow">ines, and proposed outcomes. It is essential that the prospectus is approved prior to startin" rel="nofollow">ing the project itself. This protects you by providin" rel="nofollow">ing a common, agreed-upon goal. The IT Capstone Waiver-Release Form: Complete and submit with your Capstone work. The IT Capstone Employer Release Template: Complete this form to obtain" rel="nofollow">in authorization if your Capstone project is based upon or in" rel="nofollow">includes restricted in" rel="nofollow">information. Submit this form with your Capstone work. Task: Develop a prospectus for your project in" rel="nofollow">in which you complete the followin" rel="nofollow">ing: A. Summarize in" rel="nofollow">in an abstract the important prospectus poin" rel="nofollow">ints. Include the followin" rel="nofollow">ing poin" rel="nofollow">ints: 1. Busin" rel="nofollow">iness/IT problem under in" rel="nofollow">investigation 2. Plan 3. Research methodology 4. Implementation proposal 5. Proposed outcomes B. Summarize in" rel="nofollow">in an in" rel="nofollow">introduction the capstone’s highlights. Include the followin" rel="nofollow">ing: 1. The scope of the project 2. Your rationale for choosin" rel="nofollow">ing this project 3. A problem statement 4. The background of the problem 5. The need for this solution 6. Your reasons for the chosen approach 7. The organization of the prospectus C. Summarize in" rel="nofollow">in a busin" rel="nofollow">iness statement or an IT problem statement the components of the problem. Include the followin" rel="nofollow">ing: 1. Background in" rel="nofollow">information of the problem 2. Causes of the problem 3. Busin" rel="nofollow">iness impacts of the problem 4. Cost analysis Note: The cost analysis should deal with the costs of the implementation of the solution, not the costs in" rel="nofollow">incurred because of the problem. 5. Risk analysis Note: The risk analysis should deal with the risks of the implementation of the solution, not the risks in" rel="nofollow">incurred because of the problem. 6. Assumptions about the problem 7. Limitations of the problem 8. Technical terms used in" rel="nofollow">in the statement D. Explain" rel="nofollow">in why a technology solution is needed. 1. Discuss the busin" rel="nofollow">iness drivers (i.e., important and relevant busin" rel="nofollow">iness factors). a. Justify the importance of the busin" rel="nofollow">iness drivers. 2. Discuss what could happen if no technology solution were implemented. 3. Justify the technology solution within" rel="nofollow">in busin" rel="nofollow">iness priorities. E. When you use sources, in" rel="nofollow">include all in" rel="nofollow">in-text citations and references in" rel="nofollow">in APA format.