System Summary Due: Tues Jan 30 by 11:59 pm (late Tuesday night)
all content added to your moodle system wiki page must be complete.
This week you will spend work with your Assigned Group for Paper 1 group to together investigate your assigned parallel or distributed system, and to prepare and deliver a 15 minute presentation on your system during your Monday lab section next week. You will also add a page to the moodle wiki about your system that includes a short summary about your system and links to to useful information about the system that you discovered in preparing your presentation.
With your Paper1 Group you will:
Here are the group assignments and the Assigned Systems for each group:
Paper 1 Groups and Assigned Systems.
Your group is assigned a specific type of system, and may pick one particular system of this type for your prensentation. Try to pick a particular system of your assigned type early based on how much information seems to be available on it, and then focus your effort on presenting information about that particular system. It is also valuable to include in your presentation some general characteristics about the type of system it is, but the details should be about your particular example system.
You must create slides for presentation. You may use any any software you would like for editing your presentation slides as long as you can generate a PDF version of your slides for submission from the software you use (google docs, powerpoint, office libreoffice, are some suggestions). You will upload a .pdf of your talk slide to the class wiki prior to class, and give your presentation using this .pdf version of your slides. The .pdf of your presentation slides must be uploaded to moodle by noon on Monday Jan 29.
Your presentation should address each of the items listed below. For some systems, discussing certain ones of these will take more time than for other systems. For example, for some systems the details of the architecture may be the most interesting, for others, it may be how the system is used. Part of your job is to determine which are the most important things to focus on.
This is also not an exhaustive list of what to cover. Part of your job is to determine what is interesting about your particular system.
How much to prepare and at what level: As you present parts of your system, do so in a top-down way: start with a high-level overview and then refine some parts in more detail. You only have 15 minutes, so you are going to have to pick one or two things to discuss in more detail, and leave much of the system to present at a high-level (and skip even discussing some parts of the system). Think big-picture definition of this system, and some detail about one (or two) things that are most unique or interesting about it. You do not need to know everything about the system you present, but you should be able to present both a high-level overview, some detail about an interesting part, and address the points above in your presentation.
I also encourage you to give a practice talk to at least one other group (and be a practice talk audience for them). I suggest picking the group in the other lab section who is presenting a similar system to yours.
As you give your practice talk, do not stop and make changes as you go. It should be a timed dry run of your in-class presentation (12 minutes of presentation and 3 minutes for questions). You should have talked through your slides at least once prior to your practice talk.
Audience members should provide feedback to each person, to help them improve slide content, and phrasing and content of their part of the oral presentation. Write down your comments during other group member's parts of your presentation, and the end of your presentation, go back over feedback for all slides and all presenters together. Every audience member should provide two pieces of feedback to every presenter: