
If you think your talk is just a "remix" of existing talks tailored to your audience, you might have done a great job.
You may use and copy any source of information (but do not forget to cite it). How well you understood the topic has no direct influence on your grade, but only how well you presented the topic to the audience. You do not have to show how well you understood the topic for yourself. In a seminar you have to show that you are able to present some topic to other people. Well you achieved this goal will determine the grade of your talk. The possibility to learn something new about an interesting topic. With computer science in general, probably no experts in the topic) has The goal of your talk is that the audience (bachelor and master students, familiar. This invitation contains the abstracts of all talks. We will send an invitation for the seminar to all students and members of our chair. The abstract consists of one paragraph that summarizes what you present in the talk. which theorems are presented, which of them will be proven (why?), which proofs will be omitted (why?), will you use motivating examples in the proof?. which definitions are presented formally? (why?), which definitions are just mentioned informally? (why?). examples occurring in the talk (why these examples? Is there a running example that can be used for demonstration?). aspects of the topic that you present (why?) and ignore (why?).
short overview for the reviewers (the reviewers will probably not know your topic).The proposal should consist of around five pages in which you explain what you are going to present in your talk. You attend the talks of all other participants.You have a meeting with your supervisor in which you get feedback for your slides.You submit your slides via email to your supervisor (deadline: one week before your talk).You receive reviews for your proposal (deadline: two weeks before your talk).
Write two reviews about other participants' proposals and send them viaĮmail to the supervisor (deadline: one week after you received the
Your proposal is reviewed by your supervisor and two other participants. You submit your abstract and your proposal via email to your supervisor (deadline: three weeks before your talk). You write a proposal in which you explain what you are going to present in your talk, together with an abstract of your talk. You have a meeting with your supervisor in which we discuss relevant literature and develop a very coarse sketch of your talk (deadline: four weeks before your talk). You in a discussion with your supervisor. Yourself, pick one of the suggested topics, or find a topic suitable for #Finite state automata for software engineering free#
Feel free to hand in your favorite topic in advance.Ĭontact the instructors to obtain a topic. You participate in the kick-off meeting, where we present theĪvailable topics.Thu, October 22, 16:00 c.t., building 106, room 00-007Īdvanced Topics in Automata Theory (Seminar)