Final Project Guidelines
Updated : 24 Sep 2007
Project compliance and deliverables checklist.
1. Membership on http://groups.google.com/group/PIMSAT-project
Use a gmail or yahoo account. Other domains that work are acceptable.
MSN and hotmail accounts are not to be used for any project work.
2. Get openoffice.org for creating documentation.
This can be used for creating presentations (ODP), PDF files, HTML and
ODT files.
3. Make a project website. For space check
http://www.thefreesite.com/Free_Web_Space/
4. A copy of the work done in the day needs to be sent to the group.
This includes :
Summary of work done
Timing report. Log of time spent.
Detailed results of work done
Raw material used to get work done.
Make sure a copy reaches the same day group by looking at the group
website.
5. Format of created documents.
Allowed formats for email are plain text and HTML.
Allowed formats for created project docuementation are :
Plain text, HTML, PDF and openoffice.org
For PDF and openoffice.org documents, no DRM or passwords are allowed.
6. Make a detailed proposal which includes what problem you are
solving.
7. Make a detailed plan of what you plan to do by the end of the
semester.
Deadlines :
This is week 3
By week 4 you should have an accepted proposal and detailed plan.
By week 8 You should be working on the project
By week 12 you should be planning to finish
By week 15 you need to be finished, implemented, presented, and published.
A google discussion group has been created in which all
students are required to discuss all their projects. Subscribe your
email address to it and read all of the discussions so you can learn
from the other
projects.
http://groups.google.com/group/PIMSAT-project
CC
all email to PIMSAT-project@googlegroups.com
Send a detailed plan of what you plan for each week from today up to the end of April 2007 so I know what you are going to do.
If all goes well inshallah, the results shall be finalized on an ongoing basis and there shall be no delay in the results.
Any work done without proof of work (timing reports) shall be awarded zero points.
One copy of the TR needs to be on the pimsat-project group and submitted on the same day as the work was done.
Excuses like : I have trouble becoming a member of the group shall not be accepted.
Serious work is defined as 10 - 15 hours per week for 15 weeks
with a detailed TR.
The semester is of 15 weeks but to avoid clashing project work
with preparations of finals the project is limited to the first 10
weeks.
Total serious time that you should work on your project is approximately from 100 to 200 and an expected class average average of 150 hours.
Since you have 15 weeks to Start, Think, Propose, Get approval, Plan, Do, Present, and Finish. This translates to approximately 10 hours per week on the average if you work all 15 weeks of the semester. That is like 1.5 hours per day.
This does not include the class discussion time. You can and are expected to discuss on the group during the week.
Plagiarism
Guidelines
First
proposal. Read this for details on how to fix your first
proposal.
Second
Proposal. Read this to learn how not to learn about serious software
proposals.
At least 1 proposal is due before the 20th of
Feb 2006. 
Proposal
writing Guide.
Basic Project Plan for the semester projects.
How to write a Literature Review
advisor_evaluation_11_aug_2005.pdf
course_project_11_aug_2005.pdf
example_project_specification.pdf
peer_evaluation_form_11_aug_2005.pdf
project_planning_document_11_aug_2005.pdf
sample_timing_report_11_aug_2005.pdf
student_accomplishment_sheet_11_aug_2005.pdf
student_grading_sheet_11_aug_2005.pdf
time_management_11_aug_2005.pdf
student_project_guidelines_11_aug_2005.pdf
website_evalution_11_aug_2005.pdf
How to write a research report.
Check list for project queries and deliverables.
Format for sending emails related to project to
khawar@pimsat-khi.edu.pk cc to PIMSAT-project@googlegroups.com
Full name <email address>
Subject : Your Name
: Project Title : Date : Time
Example : Khawaja Salman : ICT Security : 24 Sep 2007 : 4:01
In the body of the message write your roll number
Message body example :
Roll Number : 1234-567-007
What you want to discuss.
Then Attachments.
Make attachments in HTML if formatting is required.
If you do not need special formatting. Please send a simple text email with no attachments.
Send all timing reports as simple text emails. There is no need for formatting them.
If you need to send complete HTML pages with inline
images or other files then you may use the .zip format.
However
for open standardization .tgz is preferred.
All rough draft and final documentation needs to be done in HTML Format. All presentations are to be in Open Office Impress Format.
Emails not in the correct format shall be ignored.
Make sure no
email is greater than 1 MB in size.
If you need to send data more
than 1 MB in size, then break it up into separate emails.
If you
cannot break it into smaller parts, then send it on a CD on my desk
with.
Make sure to label the following information :
1. Your Full
Name
2. Project Title or proposal
3. Student Number
4.
Contents of the CD.
In case your mail bounces, then resend the
original to atrc.support@gmail.com
You also need to send a second
mail with the bounced message with complete headers so I can figure
out what
happened.
--------------------------------------------------------------------------------------
Read a page.
Understand it.
Write your own notes (Read how to write a report information provided).
Update your timing report. (Sample provided).
.Zip the html file to send.
and MOVE ON.
----------------------------------------------------------------------------
For all articles or documents which you are referencing in your final report mark their difficulty level as follows :
|
Difficulty Levels of Documents. |
|
Newspaper article. No scientific knowledge required. |
|
Science Magazine Article. Some subject knowledge will be helpful. |
|
Review article. Undergraduate level knowledge assumed. |
|
Research article. Familiarity with the essentials of the field assumed. |