15-819K: Logic ProgrammingProject ProposalTITLEAUTHORSNovember 10, 2006AbstractA short abstract summarizing the proposed project, 200 words orfewer. The proposal, excluding the references, must be at most 10pages and must conform to this format. If there is additional sup-porting material, say, more examples or a partial implementation,please provide a URL and sketch what is there. The firm deadlinefor handing in the proposal is Tuesday, November 21. Proposals willbe graded.1 IntroductionThe introduction should provide motivation, clear problem statemen t, andrevie w of the most relevant prior work with citations. The introductionshould be accessible to anyone in the class, including me, so do not expecttoo much backgroun d knowledge. This is especially true if the proposalapplies logic programming in your own area of research.2 Project DescriptionDescribe the proposed research. This may include additional background,examples of the problem and proposed solutions, and partial results ob-tained so far. Be explicit about how you plan to approach the problem andwhat is novel about it compared to prior work. If you have conjectures orplan to prove certain th eorems, s tate them as clearly as possible. If youPROJECT PROPOSAL NOVEMBER 10, 2006TITLE 2plan an implementation, sketch its functionality and justify your imple-mentation language. If you propose a language design, sket ch the prop-erties you expect t o hold (even if you do not plan to prove them) and thekind of programs you would like to exp ress. Examples are a useful devicein illustrating what y ou propose; use them liberally.3 Expected OutcomeDetail the expect outcome of the p roject. Summarize here any theoreticalresults, language designs, implementations, or other artifacts you intend toproduce. It is import ant to delineate the scope o f the proposed project, soyou should als o explicitly mention what you do not plan to address. Forexample, you might state that you wish to produce a design but not animplementation, or an implementation but not a correctness proof for it.You should also explain how yo u would assess the outcome of yourproject. For example, you might measure speed improvements in compiledcode, or consider the range of algorithms your language can express, or thekind of programs that your analysis can cer tify.A p roposal is n ot a binding contract, and research is unpredictable bynature, so this section s h ould represent your best guess. I f there are contin-gencies they should be spelled out to the exte n t you can anticipate them.A p roject report is a re q uired outcome for every group. If you believethat a paper might result from the work, give some potential publicationvenues.4 ConclusionSummarize the proposed project, now that its technical basis has been ex-plained, and point to some potential future work (even if you do not planon carrying it out yourself).5 ReferencesGive the references in the usual BibTeX format.PROJECT PROPOSAL NOVEMBER 10,