[csidc:2003] - Fw: Interim Report Guidelines[via LSMTP - see www.lsoft.com] by "Gvozden Marinkovic" <mgvozden@eunet.yu>

----- Original Message -----
From: <SSaul@COMPUTER.ORG>
To: <CSIDC2003@COMPUTER.ORG>
Sent: Thursday, February 27, 2003 9:20 PM
Subject: Interim Report Guidelines[via LSMTP - see www.lsoft.com]


> Interim Report Guidelines
>
> The purpose of the interim report is to provide feedback to the CSIDC
> organizers about the progress of the competition. This information will
> also be used to recruit the appropriate number of judges for the next stage
> in the evaluation process.
>
> Teams that are showing little or no progress will be eliminated at the
> interim report stage. However, the competition organizers would like to
> stress that all teams with a viable project that are making good progress
> will continue to the next stage of the competition (i.e., the submission of
> the final report on 28 April 2003).
>
> Once more, we state that only teams who have not really taken part in the
> competition and who have either not submitted an interim report or have
> submitted a very minimal interim report will be eliminated at this stage.
>
> We expect all teams that are working effectively on their project will
> proceed to the next stage. There is no limit on the number of teams that
> may continue to the next stage. If all interim reports are satisfactory,
> then all teams will be invited to submit a final report.
>
>
> Details of the Interim Report
>
> The report must be no more than four pages (either A4 or letter paper with
> 1 inch or 2.5 cm margins) long, plus a cover sheet. The cover sheet must
> provide only the name of the project and the information indicated in the
> appendix following this message. The cover sheet does not form part of the
> project page-count.
>
> The report may contain text, figures, or pictures.
>
> The report must be written in an 11pt or 12pt single-spaced font.
>
> The report must be submitted either as a Microsoft Word .doc file,  as an
> Adobe Acrobat .pdf file or as a text file.
>
> The report must be submitted by 24:00 hrs GMT 21 March 2003 via email to
> csidc@computer.org or via ftp to:
>
> basil.computer.org (or ip address: 20699235182)
> user id: csidc03
> password: addedvalue
>
> The report’s file name should be some form of  your university’s name, not
> your project’s name.
>
> Examples include:
> University of McMaster - McMaster.doc
> University of Virginia - UVA.doc
> Dwarkadas J Sanghvi College of Engineering - DJSanghvi.doc
> Indian Institute of Technology Roorkee - IITKRoorkee.doc
>
> The cover sheet of the report must contain the information given in the
> appendix to these guidelines. The information must be set out as shown (for
> ease of document handling). This information will also give the organizers
> a better idea of the teams. If you regard any of the information as
> personal (for example, your age or gender), it is not necessary to provide
> that information and you may ignore that question.
>
>
> Contents of the Interim Report
>
> This document is just a guide to the interim report. The purpose of the
> interim report is to ensure that teams are making satisfactory progress. We
> need to determine whether you have a viable project that falls within the
> scope of the competition and are making satisfactory progress towards the
> completion of the project.
>
> We need to know what your project is and what your system will achieve. We
> also need to know how your project will have a beneficial effect on society
> and what its social impact will be. We would like you to state what is new,
> innovative, or original about your project.
>
> We would like to know the structure of your system; that is, what hardware
> and software components does it use?
>
> How much do you intend to spend on your project? Remember the $400 limit!
> However, we are not interested in the cost of any “base system” such as a
> PC, or the cost of widely available software used in universities and
> colleges.
>
> Have you used software engineering principles or developed software tools
> that support the design of your project?
>
> What is the operating principle of your system and how is it expected to
> work?
>
> Teams are also expected to provide a short description on the way in which
> their team is organized. For example; you could describe the roles of each
> of the members of the teams and the way in which teams members communicate
> with each other and decisions are made.
>
> We suggest that your report be set out with the following headings
>
> INTRODUCTION: Brief description of the project
> BENEFITS OF PROJECT: How the project will benefit society
> INNOVATION: New, original and innovative aspects of the project
> SYSTEM ORGANIZATION: Structure of the system’s hardware and software
> PRINCIPLES OF OPERATION: How the system will work
> DESIGN STRATEGY: How the system is being designed (software engineering)
> COST: Anticipated amount of money spend on developing your system
> TEAM ORGANIZATION: Structure, planning and organization of your team
> OUTCOME: Brief description of what you expect to achieve by the end of the
> project.
>
>
> Alan Clements
> 25 February 2003
>
>
>
> Appendix – Interim Report Cover Sheet Outline
>
>
>
> CSIDC 2003
>
>
> Interim Report
>
>
> Team     Country    <my country>
>
> Team     University <my school/university/college>
>
> Team     District   <town or region of the university>
>
> Team     Number     <if your institution is entering multiple teams, please
>                     number the teams 1, 2, 3… so that we may evaluate each
>                     team individually>
>
> Team     Mentor     <mentor name>
>          Mentor     <contact email>
>          Mentor     <contact phone number>
>
> Project  Title      <title of project>
>
>
> Student 1           Name      <name>
>          Email      <contact email>
>          Course     <name of course being studied>
>          Age        <age of student>
>          Gender     <male|female>
>
> Student 2           Name      <name>
>          Email      <contact email>
>          Course     <name of course being studied>
>          Age        <age of student>
>          Gender     <male|female>
>
> Student 3           Name      <name>
>          Email      <contact email>
>          Course     <name of course being studied>
>          Age        <age of student>
>          Gender     <male|female>
>
> Student 4           Name      <name>
>          Email      <contact email>
>          Course     <name of course being studied>
>          Age        <age of student>
>          Gender     <male|female>
>
>
>
>
>
>
> IEEE Computer Society
> 1730 Massachusetts Avenue, NW
> Washington, DC  20036
> tel: +1-202-371-0101
> fax: +1-202-728-0884
> email:  ssaul@computer.org
>