|
|
|
bgcolor="#FFFFFF" width="840" height="1660" border="0" cellpadding="0" cellspacing="0" valign="top" align="left"> |
 CHECKLIST FOR PREPARING THE PROJECT
- AGREE WITH THE TEACHER (prof. Roberto Giorgi) A POSSIBLE PROJECT or suggest one (some proposals THEMES for projects are available by clicking on this link.
OUTPUT OF THIS STEP: write half a page of project specification to indicate the methods to achieve the objectives (this specification will then be refined with the teacher) and the names of the participants.
- DEVELOPMENT OF PROJECT!
- MAKING A SHORT FINAL REPORT TO COLLECT THE CONCLUSION OF THE PROJECT (ALL SOFTWARE USED AND PRODUCED TO BE PROVIDED IN ELECTRONIC FORM)
If it's a program, the report should not be particularly fancy, but just a collection and a short discussion of the obtained results.
If you rely on existing material: please clearly highlights the sources (plagiarism will be severely marked).
- DO NOT FORGET TO HIGHLIGHT REFERENCES: the last page of the project typically contains the references of your project.
- Note: experimental projects will be evaluated more.
|
|
| |
GENERAL INFORMATION ON THE MODALITY TO DEVELOP THE PROJECT
- The project allows students to put into practice what
learned in this course, and to develop the ability to present their work.
- The project should be done in small groups (max 3 people) .
- The project can be done individually, but in exceptional cases, since one of the educationl purposes of the group project is to learn how to interact with more colleagues to achieve a common goal, thus simulating a very common work situation.
|
|
SOME RECOMMANDATIONS
- Do not go outside topic: the project is about COMPUTER ARCHITECTURE
- Relate the project content with what you have learned during this course
- The teacher is not interested in verifying the ability of the student to program or
to solve problems of various kinds, learned in other courses:
the teacher is interested to see if the student
followed productively COMPUTER ARCHITECTURE and (possibly) if he/she is capable
to apply the knowledge learned in other courses (e.g.
programming , as well as the benchmarks and simulators, are seen as tools NOT INTENDED AS THE FINAL GOAL OF LEARNING).
Clearly the knowledge learned in other courses, especially preliminary courses, is taken for acquired.
- Hence, the purpose of the project is to understand (and demonstrate your understanding) on how the architecture of a computer works. You must show that you have followed productively the course of COMPUTER ARCHITECTURE.
|
|
PROJECT EVALUATION CRITERIA
Each project will be assessed taking into account the following criteria:
- Difficulty of the project (10/40): The chosen project was trivial or ambitious? What are the challenages that project is dealing with? What was the ability to fix yourself any encountered problem?
- Correctness of the project (10/40): Were the objectives reached? How well?
- Originality and committment (10/40): The project contains hints of originality or recopy existing solutions? How much effort has been spent to solve the various problems?
- Presentation quality (10/40): What is the quality of the presentation (written and/or verbal)?
|
|
|
|
|
