IT CAPSTONE WRITTEN PROJECT

IT CAPSTONE WRITTEN PROJECT
Competency 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.
________________________________________
Task 2: Formal Report
Introduction:
Candidates completing the Bachelor of Science in Information Technology or any of the emphasis area programs are required to complete a capstone project. The approach to executing the project and completing the capstone report should be discussed with your course mentor. The purpose of the capstone project is to demonstrate your skills in the integration and synthesis of competencies in all domains required for your degree. You will demonstrate this by designing and developing a project based on your chosen format (e.g., intellectual product/service, physical product/service, event or activity, system improvement or enhancement). The project will consist of a formal report in which you elaborate on the components of your proposal and explain the actual development of your project.
Work performed on contract for a third party or for an employer is their property. You must obtain their permission to include the work. Your work for task 2 will not be evaluated until the appropriate form(s) in task 1 have been submitted.
Requirements:
A.  Identify a topic for your project that aligns with your degree program.

B.  Create a formal report (suggested length of 25–50 pages) in which you elaborate on the components of your proposal and explain the actual development of your project by doing the following:
1.  Cover Sheet: Provide a cover sheet for your project that includes the following elements:
•   project name
•   your name
•   your degree program
•   your student mentor’s name
2.  Introduction: Provide a logical overview of the actual development of your project.
a.  Include a precise description of your project.
b.  Include a thorough discussion of your review of other third-party work done on your chosen topic.
c.  Include a thorough discussion of your rationale for the project.
d.  Include a thorough discussion of your systems analysis and methodology for the project.
3.  Project Goals and Objectives: Explain why you did or did not accomplish the goals and objectives set for your project.
a.  Include a list of the goals and objectives identified in your proposal (i.e., Task 2: Proposal).
4.  Project Timeline: Explain why you did or did not meet the timeframes set for your project.
5.  Project Development: Explain the development of your project and what your project actually accomplished by including some or all of the given points:
•   problems encountered and how they were solved
•   reasons for changes made to your original plan
•   unanticipated requirements or components that needed to be resolved
•   actual and potential effects of your project
•   conclusions about the success and effectiveness of your project
6.  Evidence of Project Deliverables: Include evidence (e.g., discussion, artifacts, and examples) of key project deliverables that will document and explain your project development. Possible deliverables are as follows:
•   code samples or screen shots
•   flowcharts, UML, or other process diagrams
•   charts, tables, and graphs
•   network diagrams (before and after)
•   training material
•   technical IT product itself

C.  When you use sources, include all in-text citations and references in APA format.

Note: For definitions of terms commonly used in the rubric, see the Rubric Terms web link included in the Evaluation Procedures section.
Note: When using sources to support ideas and elements in an assessment, the submission MUST include APA formatted in-text citations with a corresponding reference list for any direct quotes or paraphrasing. It is not necessary to list sources that were consulted if they have not been quoted or paraphrased in the text of the assessment.
Note: No more than a combined total of 30% of a submission can be directly quoted or closely paraphrased from outside sources, even if cited correctly. For tips on using APA style, please refer to the APA Handout web link included in the APA Guidelines section.

ENT1 Task 2 0215
value: 0.00     value: 1.00     value: 2.00     value: 3.00     value: 4.00     Score/Level
Articulation of Response (clarity, organization, mechanics)    The candidate provides unsatisfactory articulation of response.    The candidate provides weak articulation of response.    The candidate provides limited articulation of response.    The candidate provides adequate articulation of response.    The candidate provides substantial articulation of response.
A. Topic    The candidate does not identify a topic for the project that aligns with the candidate’s degree program.    Not applicable.    Not applicable.    Not applicable.    The candidate identifies a topic for the project that aligns with the candidate’s degree program.
B1. Cover Sheet    The candidate does not provide a cover sheet for the project that includes the given elements.    Not applicable.     Not applicable.    The candidate provides a cover sheet for the project that includes some of the given elements.    The candidate provides a cover sheet for the project that includes all of the given elements.
B2. Introduction
The candidate does not provide a logical overview of the actual development of the project.    The candidate provides a logical overview, with no detail, of the actual development of the project.    The candidate provides a logical overview, with limited detail, of the actual development of the project.    The candidate provides a logical overview, with adequate detail, of the actual development of the project.    The candidate provides a logical overview, with substantial detail, of the actual development of the project.
B2a. Description of Project    The candidate does not provide a precise description of the project.    The candidate provides a precise description of the project, with no detail.    The candidate provides a precise description of the project, with limited detail.    The candidate provides a precise description of the project, with adequate detail.    The candidate provides a precise description of the project, with substantial detail.
B2b. Review of Other Work    The candidate does not provide a thorough discussion of the review of other third-party work done on the chosen topic.    The candidate provides a thorough discussion, with no detail, of the review of other third-party work done on the chosen topic.    The candidate provides a thorough discussion, with limited detail, of the review of other third-party work done on the chosen topic.    The candidate provides a thorough discussion, with adequate detail, of the review of other third-party work done on the chosen topic.    The candidate provides a thorough discussion, with substantial detail, of the review of other third-party work done on the chosen topic.
B2c. Rationale    The candidate does not provide a thorough discussion of the rationale and systems analysis for the project.    The candidate provides a thorough discussion, with no detail, of the rationale and systems analysis for the project.    The candidate provides a thorough discussion, with limited detail, of the rationale and systems analysis for the project.    The candidate provides a thorough discussion, with adequate detail, of the rationale and systems analysis for the project.    The candidate provides a thorough discussion, with substantial detail, of the rationale and systems analysis for the project.
B2d. Systems Analysis and Methodology    The candidate does not provide a thorough discussion of the systems analysis and methodology for the project.    The candidate provides a thorough discussion, with no detail, of the systems analysis and methodology for the project.    The candidate provides a thorough discussion, with limited detail, of the systems analysis and methodology for the project.    The candidate provides a thorough discussion, with adequate detail, of the systems analysis and methodology for the project.    The candidate provides a thorough discussion, with substantial detail, of the systems analysis and methodology for the project.
B3. Project Goals and Objectives
The candidate does not provide a logical explanation of why some of the goals and objectives set for the project were accomplished and others were not.    The candidate provides a logical explanation, with no detail, of why some of the goals and objectives set for the project were accomplished and others were not.    The candidate provides a logical explanation, with limited detail, of why some of the goals and objectives set for the project were accomplished and others were not.    The candidate provides a logical explanation, with adequate detail, of why some of the goals and objectives set for the project were accomplished and others were not.    The candidate provides a logical explanation, with substantial detail, of why some of the goals and objectives set for the project were accomplished and others were not.
B3a. Goals and Objectives List    The candidate does not provide a list of the goals and objectives identified in the proposal.    Not applicable.    Not applicable.    Not applicable.    The candidate provides a list of the goals and objectives identified in the proposal.
B4. Project Timeline    The candidate does not provide a logical explanation of why the timeframes set for the project were either met or not met.    The candidate provides a logical explanation, with no detail, of why the timeframes set for the project were either met or not met.    The candidate provides a logical explanation, with limited detail, of why the timeframes set for the project were either met or not met.    The candidate provides a logical explanation, with adequate detail, of why the timeframes set for the project were either met or not met.    The candidate provides a logical explanation, with substantial detail, of why the timeframes set for the project were either met or not met.
B5. Project Development    The candidate does not provide a logical explanation of the development of the project and what it actually accomplished, including some or all of the given points.    The candidate provides a logical explanation, with no detail, of the development of the project and what it actually accomplished, including some or all of the given points.    The candidate provides a logical explanation, with limited detail, of the development of the project and what it actually accomplished, including some or all of the given points.    The candidate provides a logical explanation, with adequate detail, of the development of the project and what it actually accomplished, including some or all of the given points.    The candidate provides a logical explanation, with substantial detail, of the development of the project and what it actually accomplished, including some or all of the given points.
B6. Evidence of Project Deliverables    The candidate does not provide evidence of key project deliverables that will document and explain the project development.    Not applicable.    Not applicable.    Not applicable.    The candidate provides evidence of key project deliverables that will document and explain the project development.
C. Sources    When the candidate uses sources, the candidate does not provide in-text
citations and references.     When the candidate uses sources, the candidate provides only some in-text
citations and references.     When the candidate uses sources,
the candidate provides appropriate in-text citations and references with major deviations from APA style.     When the candidate uses sources,
the candidate provides appropriate in-text citations and references with minor deviations from APA style.     When the candidate uses sources, the candidate provides appropriate in-text citations and
references with no readily detectable deviations from APA style, OR the candidate does not use sources.

Completing Your Capstone
Executing Your Proposal
In the Technical Writing course, you constructed a proposal for the capstone project. Now it is time to carry out your proposal. It is rare that projects go exactly according to plan. Keep an eye on the execution so you can make note of any departures; you can learn a great deal from what does not go as planned. Review the plan with any parties who have a stake in it; you may find a need to revise it.
Execute the plan you devised in the Technical Writing course.
1.    Obtain new permission to proceed with any part of the project related to your employment.
2.    Execute the plan, revised or original.
3.    Make explicit revisions to the plan.
4.    Keep accurate notes on the process:
• What changes were made to the plan, and why?
• What went better than planned?
• What was more difficult than expected?
• Was there anything that was not possible to complete?
5.    Justify departures from standard practice (e.g., If you could not construct a flowchart in its standard format, why not?).
6.    Keep your mentor and the course mentor apprised of anything that you consider significant in the execution of your plan.
________________________________________
Coallating Deliverables
Prepare the planned deliverables and documentation as they occur in the course of execution.
•    Obtain your employer’s permission to include any deliverables or documents that arise from your employment, even if the project itself does not.
•    Include project documentation for use by others (e.g., user manuals or software documentation). These may not need to adhere to APA format.
•    Use appropriate software to construct visuals.
•    Use appropriate software to construct documentation.
•    Properly label all visuals (exhibits, tables, figures, etc.).
________________________________________
Writing Phase
This phase could go quickly or take up to a month to complete; if a project imported from your employment only needs minor changes to align with capstone project requirements, you may only need a week or two for writing. You should not need more than four weeks for writing.
•    From Proposal to Capstone
Write Capstone Report Introduction
The capstone report introduction (suggested length of five to eight pages) is an overview of the project. Discuss the actual development, summarize the rationale, outline the systems analysis of your project, and review other work done in the same area (literature review). Some of this will represent a restatement of work that has already been done, but much of it will be new content, written to reflect the fact that your project is done.
The introduction should open with a description of your project, followed by a summary of the actual project development. To put your project into a larger context, you will restate the review of other work (literature review) from your capstone proposal with an expansion called for from the actual development of the project. Finally, the introduction closes with a discussion of the project’s rationale and the systems analysis you performed to arrive at the deliverables.
Review Capstone Project Goals and Objectives Section
Review the goals and objectives (suggested length of three to five pages), describing each in detail. Explain how you did or did not achieve them. Goals and objectives are not always technical in nature. Some of them will reflect the business or organizational unit goals.
Organize this section by individual goal and objective. For each goal and objective, explain how your project succeeded or failed. Your list of goals and objectives will come from your capstone proposal, although you may add to the list if your project identified unanticipated goals and objectives.
Discuss Capstone Project Plan and Timelines
Review your experience (suggested length of three to five pages) in using your project plan to develop the capstone project. You will provide a plausible explanation of why you did or did not meet stated timelines.
Organize this part in one of two ways: (1) list the milestones consecutively, and describe why they were or were not met; or (2) organize this section by deliverable, with a discussion of how each was or was not provided on time.
Discuss Project Development
Provide a credible and supported explanation (suggested length of three to five pages) of what the project accomplished. Discuss problems encountered, modifications made to the project plan, and reasons for those modifications. Also, address unanticipated requirements. Finally, discuss actual and potential effects of your project, developing a set of conclusions about the project’s success and effectiveness.
________________________________________
Project Assembly
Depending on the project, assembling your work into a presentable package should not take more than two weeks, even if you began from scratch. Add to that a week for evaluation, and you should be all done by week 18.
Coversheet
The cover sheet should contain the following information:
•    project name
•    your name
•    your degree program
•    your mentor’s name
The template that you used for your Technical Writing Assessment (Capstone Proposal) includes the coversheet template with the required fields to be filled in.
Additional Document Preparation
Prepare any other documents that are required (e.g., table of contents, bibliography, references, appendices) to complete your capstone report. You will likely have developed each section of your report as separate documents. However, other sections may need preparation before you can pull all of them together. Virtually all word-processing software will generate a table of contents if you have used named styles in your document.
Other sections that may need preparation include the bibliography of works cited in your capstone proposal and any appendices that your proposal requires.
________________________________________
Putting it all Together
•    At this point, your work is perhaps a collection of individual parts. Put all of your project parts together as the template indicates. List files from other programs as appendices to submit for grading.
•    Review all sections of the capstone report for language, APA format, etc.
•    Make sure that you have a backup of the final report, including all attachments.
•    Complie everything into a ZIP file and submit your Capstone Report task in TaskStream.
•    In the event that y

our capstone project is deficient, you will get it back with feedback for revision. Otherwise, your Degree Plan receives a “Pass.”