Foundations of Constraint Processing, Fall 2005 Aug 22, 2005Guidelines for reports1 Foundations of Constraint Processing CSCE421/821, Fall Berthe Y. Choueiry (Shu-we-ri) Avery Hall, 123B Tel: +1(402) Guidelines for Reports

Foundations of Constraint Processing, Fall 2005 Aug 22, 2005Guidelines for reports2 Outline Writing a critical summary Committing to a project Writing a progress report

Foundations of Constraint Processing, Fall 2005 Aug 22, 2005Guidelines for reports3 Writing a critical summary This generic template is provided as an aid but is not mandatory –PART I: your understanding of the paper –PART II: your opinion of the paper

Foundations of Constraint Processing, Fall 2005 Aug 22, 2005Guidelines for reports4 PART I: the paper What: Context of the paper –problem the authors claim to address (i.e., motivation) –assumptions they make –solution they claim to provide How: Short Description of proposed technique –basic algorithmic steps –optimizations, if any –evaluation: empirical/theoretical Impact: Comparison to previous techniques –if provided, how? –can you identify/propose some other? What next: Directions for future research

Foundations of Constraint Processing, Fall 2005 Aug 22, 2005Guidelines for reports5 PART II: your opinion Is the paper a ‘real’ advancement of the state of the art? Is it useful for the theory? for practice? Can you identify other uses of the proposed technique(s)? What are the shortcomings? Can you identify more? can you propose a fix? Any issues swept-under-the-carpet? Can you identify other directions for future research?

Foundations of Constraint Processing, Fall 2005 Aug 22, 2005Guidelines for reports6 Committing to a project By Thursday Oct 6 th, you must commit to a project Submit to handin a short report (up to 1 page) stating: –Project title, your name, & SSN –A justification for your choice –A clear work-plan listing main tasks, approximate dates, and expected outcomes –A bibliography, if applicable –Clearly state whether you are collaborating with colleagues and/or with a research assistant One proposal per team is sufficient. Teams are reminded that each member will have to provide a full evaluation of the performance of each other team member, listing both good and bad aspects. This is a requirement for collaboration.

Foundations of Constraint Processing, Fall 2005 Aug 22, 2005Guidelines for reports7 Progress report: format In your report, you discuss your progress on the work-plan you had set to yourself in the proposal you submitted. Be as concise as possible but do not be bothered by a limitation on the number of pages. Thus, there is no requirement concerning the number of pages (could take from 1 page to whatever is needed), shorter reports are welcome. If you have finished your project, this could be your draft for your final report.

Foundations of Constraint Processing, Fall 2005 Aug 22, 2005Guidelines for reports8 Progress report: content Document what you did so far Comment on what you accomplished with respect to what you promised you would State whether you are early/late and why Explain in case you have changed your plans and explain why Report any difficulties, breakthroughs Discuss anything else you feel is appropriate

Foundations of Constraint Processing, Fall 2005 Aug 22, 2005Guidelines for reports9 Progress report: spirit Imagine you are a professional hired to carry out some investigations for a client. The client is paying you for the number of hours and for the quality of service/result you are providing. It is time to re-evaluate the contract. You need to update your client on your progress. How would rate your performance? how much would you charge? are able to finish the task? –if so how and when? –if not, will you keep the contract? drop it (a penalty is involved)?