CS473 Practicum in Artificial IntelligenceStatus Reports and Code ReviewsGeneral Suggestions for Completing the Project. To encourage thatyou write your code in stages rather than waiting until the end of thesemester, you’ll have to turn in a status report and copies of your code forreview twice before the final project is due. A portion of your final gradeis based on these intermediate project reviews. The format of the status re-ports is included below, but I’ll preface that with some general suggestionsfor how to go about constructing your CS473 systems.• First, think about the major modules that your project requires andthe knowledge/data structures (e.g., rules, state descriptions, boardrepresentations, graphs, networks) that you’ll need. If at all possi-ble, implement the modules as “stubs,” i.e., functions that have nosubstantive code, but that specify all of the necessary parameters andthat make calls to the appropriate module stubs. Ideally, these shouldbe completed for code review 1.• Write the code to implement your knowledge/data structures. Thiscode normally takes the form of a set of abstract data types with allof the appropriate constructor and accessor functions. Again, ideallythese should be completed for code review 1.• Get the system running from beginning to end as soon as possible —just on a simple example. This will invariably require making manysimplifying assumptions for major chunks of the system. Hopefully,you’ll have this running for code review 2.• Once you have the basics running, design and implement any infer-ence engine or control strategies needed for your system, e.g., specificsearch strategies, a rule interpreter, move generator, learning algo-rithm.• Finally, incrementally remove the simplifying assumptions by addingthe necessary code. Evaluate the system as set forth in your projectproposal.1What to turn in for the status reports. Only one status report per projectshould be turned in. It does not need to be long. (One or at most two pagesshould suffice.) It should contain the following sections:1. A short (one or two sentence) summary of the project goal/topic.(This is just to remind us what you’re working on.)2. A list of the major components of the system as well as the currentstatus of each (e.g. designed, implemented, tested, finished, almostfinished with coding). For the pieces not yet finished, indicate tenta-tive completion dates. The schedule doesn’t have to be incredibly de-tailed, but it should include entries for all substantial modules/sub-modules of your system.3. A list of the major steps in your planned evaluation of the systemand the status of each. For some projects it may be easier to mergethis list with the component/module status list above.4. Optional: an informal log your efforts. If you’ve been keeping noteson your progress, feel free to turn these in as well. These might in-clude: (1) notes on what aspect of the project you worked on andwhen, (2) what was accomplished in each “session”, (3) design ques-tions, (4) implementation questions, (5) descriptions of experimentsand results, (6) problems that arose, (7) anything else that you thinkis relevant to the project.5. Also upload to CMS a copy of your code. We only need to see thecode that you’re writing for the project, NOT any of the code thatyou’re making use of but did not write as part of the CS473 project.6. Call the report file something obvious like report.txt or report.doc.Include it as part of the zip file uploaded to CMS (along with yourcode).The grade for the status report will be based on: (1) progress made; (2)clarity of the report; (3) algorithm design; procedural and data abstraction;(4) readability, style, documentation of the