318 The UMAP Journal 24.3(2003) Make sure that your conclusions and results are clearly stated. Any mission directives or additional questions need to be addressed Restate the problem in your words. At theend, ask yourselves the question, "Does our answer make intuitive . "Executive"Summary(Abstract)of Results The summary is the first piece of information read by a judge. It should be well written and contain the bottom-line answer or result It should motivate the judge to read your paper to see how you ob tained your results. The judges place considerable weight on the summary, and winning papers are sometimes distinguished from other papers based on the quality of the summary. To write a good summary, imagine that a reader may choose whether or not to read the body of the paper based on your summary. Thus, a summary should clearly describe your approach to the problem and, most prominently, your most important conclusions Summaries that are mere restatements of the contest problem or are cut-and-pasted boil erplate from the Introduction are generally considered weak Put the"bottom line results and managerial recommendations" in the Be succinct: do not include a discussion of methods used and do not just list a description or historical narrative of what you did Clarity and Style Use a clear style and do not ramble Do not list every possible model or method that could be used in a roblem a table of contents is elpful to the judg Pictures, tables, and graphs are helpful; but you must explain them Donot include a picture, table, or graph that is extraneous to your model Do not be overly verbose, since judges have only 10-30 min to read and our paper. Include a graphic flowchart or an algorithmic flow chart for computer Develop your model-do notjust provide a laundry list of possible mod- els even if explained318 The UMAP Journal 24.3 (2003) – Make sure that your conclusions and results are clearly stated. Any mission directives or additional questions need to be addressed. – Restate the problem in your words. – At the end, ask yourselves the question, “Does our answer make intuitive and/or common sense?” • “Executive” Summary (Abstract) of Results The summary is the first piece of information read by a judge. It should be well written and contain the bottom-line answer or result. It should motivate the judge to read your paper to see how you ob￾tained your results. The judges place considerable weight on the summary, and winning papers are sometimes distinguished from other papers based on the quality of the summary. To write a good summary, imagine that a reader may choose whether or not to read the body of the paper based on your summary. Thus, a summary should clearly describe your approach to the problem and, most prominently, your most important conclusions. Summaries that are mere restatements of the contest problem or are cut-and-pasted boil￾erplate from the Introduction are generally considered weak. – Put the “bottom line results and managerial recommendations” in the summary. – Be succinct; do not include a discussion of methods used, and do not just list a description or historical narrative of what you did. • Clarity and Style – Use a clear style and do not ramble. – Do not list every possible model or method that could be used in a problem. – A table of contents is very helpful to the judges. – Pictures, tables, and graphs are helpful; but you must explain them clearly. – Do not include a picture, table, or graph that is extraneous to your model or analysis. – Do not be overly verbose, since judges have only 10–30 min to read and evaluate your paper. – Include a graphic flowchart or an algorithmic flow chart for computer programs used/developed. • The Model – Develop your model—do not just provide a laundry list of possible mod￾els even if explained