Capstone Prospectus
I’m studying for my Computer Science class and need an explanation.
COMPETENCIES
981.1.1 : Capstone
The graduate integrates and synthesizes competencies from across the degree program and thereby demonstrates the ability to participate in and contribute value to the chosen professional field.
INTRODUCTION
The prospectus is the capstone proposal that details the goals and expectations for your project. It contains information including the project plan, expectations, rationale, methods, timelines, and proposed outcomes. It is essential that the prospectus is approved prior to starting the project itself. This protects you by providing a common, agreed-upon goal.
Before starting this task, ensure that task 1 has a passing score. If task 1 is not yet passed, your Prospectus will be returned without evaluation.
REQUIREMENTS
Your submission must be your original work. No more than a combined total of 30% of the submission and no more than a 10% match to any one individual source can be directly quoted or closely paraphrased from sources, even if cited correctly. An originality report is provided when you submit your task that can be used as a guide.
You must use the rubric to direct the creation of your submission because it provides detailed criteria that will be used to evaluate your work. Each requirement below may be evaluated by more than one rubric aspect. The rubric aspect titles may contain hyperlinks to relevant portions of the course.
Develop a prospectus for your project in which you complete the following:
A. Summarize in an abstract (suggested length of 200 words) the important prospectus points. Include the following points:
1. Business/IT problem under investigation
2. Plan
3. Research methodology
4. Implementation proposal
5. Proposed outcomes
B. Summarize in an introduction (suggested length of 6–9 pages) the capstone’s highlights. Include the following:
1. The scope of the project
2. Your rationale for choosing 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 a business statement or an IT problem statement (suggested length of 3–5 pages) the components of the problem. Include the following:
1. Background information of the problem
2. Causes of the problem
3. Business 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 incurred because of the problem, and should indicate the outside sources used to estimate the cost factors.
5. Risk analysis
Note: The risk analysis should deal with the risks of the implementation of the solution, not the risks incurred because of the problem.
6. Assumptions about the problem
7. Limitations of the problem
8. Technical terms used in the statement
Note: The sources used to compose the definitions of the technical terms should be indicated.
D. Summarize the technology solution that addresses the problem (suggested length of 4-6 pages). Include the following:
1. Explain the technology solution.
2. Identify the business drivers of the technology solution (e.g., important and relevant business factors).
a. Justify the importance of the business drivers.
3. Discuss what could happen if no technology solution were implemented.
4. Justify the technology solution within business priorities.
E. Acknowledge sources, using in-text citations and references, for content that is quoted, paraphrased, or summarized.
F. Demonstrate professional communication in the content and presentation of your submission.
File Restrictions
File name may contain only letters, numbers, spaces, and these symbols: ! – _ . * ‘ ( )
File size limit: 200 MB
File types allowed: doc, docx, rtf, xls, xlsx, ppt, pptx, odt, pdf, txt, qt, mov, mpg, avi, mp3, wav, mp4, wma, flv, asf, mpeg, wmv, m4v, svg, tif, tiff, jpeg, jpg, gif, png, zip, rar, tar, 7z
RUBRIC
A1: PROBLEM
:
NOT EVIDENT The candidate does not provide in the abstract a logical summary of the business/IT problem under investigation.
|
APPROACHING COMPETENCE The candidate provides in the abstract a logical summary, with limited detail, of the business/IT problem under investigation.
|
COMPETENT The candidate provides in the abstract a logical summary, with adequate detail, of the business/IT problem under investigation.
|
A2: PLAN:
NOT EVIDENT The candidate does not provide in the abstract a logical summary of the plan.
|
APPROACHING COMPETENCE The candidate provides in the abstract a logical summary, with limited detail, of the plan.
|
COMPETENT The candidate provides in the abstract a logical summary, with adequate detail, of the plan.
|
A3: METHODOLOGY:
NOT EVIDENT The candidate does not provide in the abstract a logical summary of the research methodology.
|
APPROACHING COMPETENCE The candidate provides in the abstract a logical summary, with limited detail, of the research methodology.
|
COMPETENT The candidate provides in the abstract a logical summary, with adequate detail, of the research methodology.
|
A4: IMPLEMENTATION PROPOSAL:
NOT EVIDENT The candidate does not provide in the abstract a logical summary of the implementation proposal.
|
APPROACHING COMPETENCE The candidate provides in the abstract a logical summary, with limited detail, of the implementation proposal.
|
COMPETENT The candidate provides in the abstract a logical summary, with adequate detail, of the implementation proposal.
|
A5: OUTCOMES:
NOT EVIDENT The candidate does not provide in the abstract a logical summary of the proposed outcomes.
|
APPROACHING COMPETENCE The candidate provides in the abstract a logical summary, with limited detail, of the proposed outcomes.
|
COMPETENT The candidate provides in the abstract a logical summary, with adequate detail, of the proposed outcomes.
|
B1: PROJECT SCOPE:
NOT EVIDENT The candidate does not provide in the introduction a logical summary of the scope of the project.
|
APPROACHING COMPETENCE The candidate provides in the introduction a logical summary, with limited detail, of the scope of the project.
|
COMPETENT The candidate provides in the introduction a logical summary, with adequate detail, of the scope of the project.
|
B2: PROJECT RATIONALE:
NOT EVIDENT The candidate does not provide in the introduction a logical summary of the rationale for choosing the project.
|
APPROACHING COMPETENCE The candidate provides in the introduction a logical summary, with limited detail, of the rationale for choosing the project.
|
COMPETENT The candidate provides in the introduction a logical summary, with adequate detail, of the rationale for choosing the project.
|
B3: PROBLEM SUMMARY:
NOT EVIDENT The candidate does not provide in the introduction a logical summary of the problem statement.
|
APPROACHING COMPETENCE The candidate provides in the introduction a logical summary, with limited detail, of the problem statement.
|
COMPETENT The candidate provides in the introduction a logical summary, with adequate detail, of the problem statement.
|
B4: PROBLEM BACKGROUND:
NOT EVIDENT The candidate does not provide in the introduction a logical summary of the background of the problem.
|
APPROACHING COMPETENCE The candidate provides in the introduction a logical summary, with limited detail, of the background of the problem.
|
COMPETENT The candidate provides in the introduction a logical summary, with adequate detail, of the background of the problem.
|
B5: NEED FOR THE SOLUTION:
NOT EVIDENT The candidate does not provide in the introduction a logical summary of the need for the solution.
|
APPROACHING COMPETENCE The candidate provides in the introduction a logical summary, with limited detail, of the need for the solution.
|
COMPETENT The candidate provides in the introduction a logical summary, with adequate detail, of the need for the solution.
|
B6: REASON FOR APPROACH:
NOT EVIDENT The candidate does not provide in the introduction a logical summary of the reasons for the chosen approach.
|
APPROACHING COMPETENCE The candidate provides in the introduction a logical summary, with limited detail, of the reasons for the chosen approach.
|
COMPETENT The candidate provides in the introduction a logical summary, with adequate detail, of the reasons for the chosen approach.
|
B7: PROSPECTUS ORGANIZATION:
NOT EVIDENT The candidate does not provide in the introduction a logical summary of the organization of the prospectus.
|
APPROACHING COMPETENCE The candidate provides in the introduction a logical summary, with limited detail, of the organization of the prospectus.
|
COMPETENT The candidate provides in the introduction a logical summary, with adequate detail, of the organization of the prospectus.
|
C1: BACKGROUND INFORMATION:
NOT EVIDENT The candidate does not provide in a business statement or an IT problem statement a logical summary of the background information of the problem.
|
APPROACHING COMPETENCE The candidate provides in a business statement or an IT problem statement a logical summary, with limited detail, of the background information of the problem.
|
COMPETENT The candidate provides in a business statement or an IT problem statement a logical summary, with adequate detail, of the background information of the problem.
|
C2: CAUSES:
NOT EVIDENT The candidate does not provide in a business statement or an IT problem statement a logical summary of the causes of the problem.
|
APPROACHING COMPETENCE The candidate provides in a business statement or an IT problem statement a logical summary, with limited detail, of the causes of the problem.
|
COMPETENT The candidate provides in a business statement or an IT problem statement a logical summary, with adequate detail, of the causes of the problem.
|
C3: BUSINESS IMPACTS:
NOT EVIDENT The candidate does not provide in a business statement or an IT problem statement a logical summary of the business impacts of the problem.
|
APPROACHING COMPETENCE The candidate provides in a business statement or an IT problem statement a logical summary, with limited detail, of the business impacts of the problem.
|
COMPETENT The candidate provides in a business statement or an IT problem statement a logical summary, with adequate detail, of the business impacts of the problem.
|
C4: COST ANALYSIS:
NOT EVIDENT The candidate does not provide in a business statement or an IT problem statement a logical summary of the cost analysis.
|
APPROACHING COMPETENCE The candidate provides in a business statement or an IT problem statement a logical summary, with limited detail, of the cost analysis.
|
COMPETENT The candidate provides in a business statement or an IT problem statement a logical summary, with adequate detail, of the cost analysis.
|
C5 : RISK ANALYSIS:
NOT EVIDENT The candidate does not provide in a business statement or an IT problem statement a logical summary of the risk analysis.
|
APPROACHING COMPETENCE The candidate provides in a business statement or an IT problem statement a logical summary, with limited detail, of the risk analysis.
|
COMPETENT The candidate provides in a business statement or an IT problem statement a logical summary, with adequate detail, of the risk analysis.
|
C6: ASSUMPTIONS:
NOT EVIDENT The candidate does not provide in a business statement or an IT problem statement a logical summary of the assumptions about the problem.
|
APPROACHING COMPETENCE The candidate provides in a business statement or an IT problem statement a logical summary, with limited detail, of the assumptions about the problem.
|
COMPETENT The candidate provides in a business statement or an IT problem statement a logical summary, with adequate detail, of the assumptions about the problem.
|
C7: LIMITATIONS:
NOT EVIDENT The candidate does not provide in a business statement or an IT problem statement a logical summary of the limitations of the problem.
|
APPROACHING COMPETENCE The candidate provides in a business statement or an IT problem statement a logical summary, with limited detail, of the limitations of the problem.
|
COMPETENT The candidate provides in a business statement or an IT problem statement a logical summary, with adequate detail, of the limitations of the problem.
|
C8: TERMS:
NOT EVIDENT The candidate does not provide in a business statement or an IT problem statement a logical summary of the technical terms used in the statement.
|
APPROACHING COMPETENCE The candidate provides in a business statement or an IT problem statement a logical summary, with limited detail, of the technical terms used in the statement.
|
COMPETENT The candidate provides in a business statement or an IT problem statement a logical summary, with adequate detail, of the technical terms used in the statement.
|
D1: EXPLANATION FOR TECHNOLOGY SOLUTION:
NOT EVIDENT The candidate does not provide a logical explanation of the technology solution.
|
APPROACHING COMPETENCE The candidate provides a logical explanation, with limited support, of the technology solution.
|
COMPETENT The candidate provides a logical explanation, with adequate support, of the technology solution.
|
D2: BUSINESS DRIVERS:
NOT EVIDENT The candidate does not identify business drivers.
|
APPROACHING COMPETENCE The candidate identifies, with limited detail, the business drivers of the technology solution.
|
COMPETENT The candidate identifies, with adequate detail, the business drivers of the technology solution..
|
D2A: JUSTIFICATION:
NOT EVIDENT The candidate does not provide a logical justification of the importance of the business drivers.
|
APPROACHING COMPETENCE The candidate provides a logical justification, with limited support, of the importance of the business drivers.
|
COMPETENT The candidate provides a logical justification, with adequate support, of the importance of the business drivers.
|
D3: NO SOLUTION:
NOT EVIDENT The candidate does not provide a logical discussion of what could happen if no technology solution were implemented.
|
APPROACHING COMPETENCE The candidate provides a logical discussion, with limited support, of what could happen if no technology solution were implemented.
|
COMPETENT The candidate provides a logical discussion, with adequate support, of what could happen if no technology solution were implemented.
|
D4: SOLUTION:
NOT EVIDENT The candidate does not provide a logical justification of the technology solution within business priorities.
|
APPROACHING COMPETENCE The candidate provides a logical justification, with limited support, of the technology solution within business priorities.
|
COMPETENT The candidate provides a logical justification, with adequate support, of the technology solution within business priorities.
|
E:SOURCES
NOT EVIDENT The submission does not include both in-text citations and a reference list for sources that are quoted, paraphrased, or summarized.
|
APPROACHING COMPETENCE The submission includes in-text citations for sources that are quoted, paraphrased, or summarized and a reference list; however, the citations or reference list is incomplete or inaccurate.
|
COMPETENT The submission includes in-text citations for sources that are properly quoted, paraphrased, or summarized and a reference list that accurately identifies the author, date, title, and source location as available.
|
NOT EVIDENT Content is unstructured, is disjointed, or contains pervasive errors in mechanics, usage, or grammar. Vocabulary or tone is unprofessional or distracts from the topic.
|
APPROACHING COMPETENCE Content is poorly organized, is difficult to follow, or contains errors in mechanics, usage, or grammar that cause confusion. Terminology is misused or ineffective.
|
COMPETENT Content reflects attention to detail, is organized, and focuses on the main ideas as prescribed in the task or chosen by the candidate. Terminology is pertinent, is used correctly, and effectively conveys the intended meaning. Mechanics, usage, and grammar promote accurate interpretation and understanding.
|
Need your ASSIGNMENT done? Use our paper writing service to score good grades and meet your deadlines.
Order a Similar Paper Order a Different Paper