Scribd
Upload
14 views2 pages

End of Year Project

The End of Year Project for Computer Science involves groups creating a Python program of their choice and documenting their work for a portfolio. Students must submit a project outline for approval, maintain a burn-down list, and complete individual developer diaries. The project will be assessed based on scope, documentation, completion, reflections, and individual contributions.

Uploaded by

arya.santosh2007
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
14 views2 pages

End of Year Project

The End of Year Project for Computer Science involves groups creating a Python program of their choice and documenting their work for a portfolio. Students must submit a project outline for approval, maintain a burn-down list, and complete individual developer diaries. The project will be assessed based on scope, documentation, completion, reflections, and individual contributions.

Uploaded by

arya.santosh2007
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 2

End of Year Project – Computer Science

In groups of two or three, complete a Python program of your choosing, and create a portfolio piece representing your work.

You are free to choose what program you are going to create. When you have decided in your group what you would like to make, create an
outline document explaining your program, and submit this for approval. Make any revisions necessary from the feedback, and then begin to
create your program. The project is due by the last class before Finals week.

You can use any language we have used this year to create your project:

 Python
 Java
 AppInventor (note: we no longer have tablets, you will need to provide your own android device)

In addition to creating our program, we are going to complete documentation for our portfolios. We will need the following items:

 Project outline
o A paragraph explanation of your program and the tools that you will use to create it.
 Burn-down list
o A to-do list of code to be written – tackle small numbers of these at one time and ensure that they work before moving on.
 Project reflections (individual)

Modify your github websites to include these items.

Every day, you will individually complete developer diaries to state what you achieved, and what your next goal is. This will be in a Google Doc
that you share with me ([email protected]). An example developer diary entry:

5/12/15 – Dev Diary, Ian Edgeley

Today I set out to solve an issue with my game where it wouldn’t correctly keep track of how much health I had. I found that there was
an error within a while loop where I was decreasing the wrong variable. In addition, I created several methods for buying and selling
items within a store. Next time I will bug test these methods and integrate them within the game.
Objective Mastery Accomplished Developing Beginning
4 3 2 1
Project scope Challenging project that Challenging project that is Project scope includes Project scope is too narrow
required student research solved with knowledge some challenging aspects, to significantly challenge
30% and initiative to solve. learned in class. but is easily solved with in- students, not requiring in-
class material. depth analysis to solve.
Project outline and burn Documentation completed Documentation completed Documentation not Documentation missing or
down list before project start, with a before project start, with a finished before project not relevant to the project,
thorough analysis of the solid but incomplete start, but submitted before or submitted after
10% problems needed to be analysis of the problems completion. completion.
solved. faced.
Project Completion and Project completes the Project completes the Some work still required to Project does not execute in
efficiency entirety of the outline outline determined, with complete the project any form and cannot
determined at the start, some room for outline, or the code demonstrate progress
40% with care and thought improvement in the requires major towards the project
given to efficient efficiency of the code. improvements in efficiency. outline.
algorithms.
Reflections Student reflects insightfully Student reflects on the Student reflection is brief Student reflection is
on the process of project process of the project and requires more insight missing or not relevant to
20% completion, thoughts for completion, with some into how to improve upon the project, or offers no
improvement and insight thought given to how to the project, and how the real insight into the
into issues faced. improve the outcome. process was successful or process.
difficult.
Teacher assessment of Student contributed Student contributed in Student did not show Student had little or no
contribution significantly to the project some way to the project at initiative or make involvement in the creation
Separate Grade at all stages, through all stages, through research significant contributions to of the product.
research and development. and development. the development process.

You might also like