Although the background diagram is quite disordered and hard to follow, the overall presentation is well-organized and informative. The flow chart is properly and timely used to demonstrate application workflow. Main algorithm for detecting the size which is the digitization is described. And last but not least, the test is conducted to evaluate the work. I think this is a perfect pattern for research work. However, a little suggestion though, you might want to add your insight and opinion on the critical issues of your application and this problem so that the audience be aware of them.
Brilliant work and presentation! Absolutely, distributed programming is another good area to explore. The presentation is clear and well organized. You might consider using some kind of diagram to explain your system architecture and interaction instead of plain text in the third slide. However, you have pointed out some of the difficulties in developing this application. I think you are one of the two teams that mention this. This is a very important thing for the presentation apart from showing the result. I believe that presentation is not only to summarize your work but also to tell the story of your work. Good job.
Good job on the development and presentation. I'm sure that a lot of effort has been put in order to interface with propriety library from adobe acrobat. On your presentation, I would like to make some comments:
1) In your introduction, the open is very vague and distracting. I think, rather than mentioning general business need to create PDF, I think it is more important to show what value you can get from having the overtime sheet generated automatically in PDF format.
2) I still don't understand. Why you need to create PDF at the first place. I think you can represent this sheet in HTML dynamically based on your data. PDF just comes into play when you want to print the HTML out.
3) The system concept slide which explains the logic of the application is not quite clear. I think you might try to connect each element with appropriate arrows to show how interaction occurs and in which order. Or you can use UML interaction diagram for this.
4) Also, I don't know that your web site is for students and for guard until the very last slide for the demo. I think you should mention in the system conceptual diagram as well that who are the users of your system and what kind of roles or actions they have.
5) Just a small opinion, I think I would mention also the challenges and the problems that you faced in this project and how you overcome those. Then the audience can benefit from your experience.
I think your idea is close to page crawling for contents to download which is a good one. You have made your presentation short but informative. That is a very good and important thing. I have some comments:
1) Would you be able to explain how you crawl for the link? I think it's all in urlmon.dll but if you could share conceptually how this is possible, that would be perfect.
2) Security: downloading content naively could lead to opening your door to malicious contents. I think you should give some of your thoughts on this.
3) Good news: you guys are the only group that did mention and share your problems although you did not solve them. But this is a very important point. I really like that.
4) Instead of showing raw links, why don't you show thumbnails of the content from those links. If they are pictures, of course, you can show them. If they are audio or other kind of contents, you can just display it with some icons.
5) The way to filter contents to be downloaded is not quite effective. I think it makes more sense to let user be able to filter her download by content type such as audio, video, etc.
The application is of high quality and the presentation is concise and straight to the point. There is nothing much to comment apart from the fact that you can combine the screenshot explanation with the live demo because I think live demo is clear in itself anyway. Then you can save time to explain major issues in your work and how you overcome them which are very important compliments to your presentation. Again, well done.
The idea was very nice and quite challenging since sharing schedules or proposing schedules for a group of people is not trivial. The work is nicely done. Regarding the presentation, I quite like the style which you use a day in life scenario to walk audience through your presentation. The unfortunate thing is that you should not stop it only at your background. I would make this presentation as a day in life scenario play where all of the team members will be using the scheduler. Then I will be able to point out clearly how the program actually helps people share their schedule or propose schedule as you mentioned. About the demonstration details, I would like to make some comments:
1) I think the research background is nice. You talked about system architecture and software architecture which are important. But you didn't mention the most important point, i.e. under what logic this program works. If you have specific algorithm or flowchart, do show it since from your screenshot of each feature, I cannot get a grasp of how it actually works behind the scene. I propose that you extend your system architecture so that it accommodates this point.
2) Better than lengthy screenshots of your system, live demo is always better.
3) Just a small opinion, I think I would mention also the challenges and the problems that you faced in this project and how you overcome those. Then the audience can benefit from your experience.
4) I like your conclusion and your sense of humor. Please keep using them.
Well done for both content and presentation. The presentation is well organized and you have shown each point clearly. Also, the test with some benchmark to evaluate your software performance is necessary in your case and you have done it. Above all, you got a good result. I don't think I have much comment on your presentation except the following points:
1) SSDA Algorithm? When you introduced a name of something, it is good to shortly describe it either by a couple of sentences or a slide. I think it is one of the core algorithm in your work. Therefore, it deserves a separate slide for that.
2) Although your English is quite perfect, I think you sound a little nervous. So please be confident and take it easy.
3) Just a small opinion, I think I would mention also the challenges and the problems that you faced in this project and how you overcome those. Then the audience can benefit from your experience.
4) Screenshot was great. However, in your case, since you cannot do demo anyway. Then the alternative to bring LIVE to your presentation is to capture the experiment on your desktop as a video. There are some tools that you could use like camtasia. It is downloadable from
www.techsmith.com. You can use the trial version to create a video script for your presentation.
First of all, I am really impressed by your effort and improvement. I would say that the presentation is better organized than last time. The diagram and UML that help people to understand the logic of your work are an effective way to convey the idea. Here are some suggestions:
1) You should specify clearly what is the scope of your work and what is not. For example, in this work, you focus only extracting classes, structures and functions. This can be specified in your goal explicitly. Because without that, as an audience, I would tend to assume that you can extract everything from the code.
2) Following number 1), I'm not quite understand why you choose to focus only on structures, classes and functions. Is there any specific reasons?
3) In your demonstration, you show only the math class example. What if I change the class to be an arbitrary one? Would it still work? Or is there any specific limitations needed to impose on the input class?
4) Just a small opinion, I think I would mention also the challenges and the problems that you faced in this project and how you overcome those. Then the audience can benefit from your experience.
NOTE! Voice comment is available at http://modred.mit.edu:2323/documents/beta.wav.
Comments on Slides:
- I quite like the fact that you keep the slides simple but still narrative enough to cover all the details clearly. Good job.
- On the outline page, I think it is a very important slide that you show the description of your project. Since you are talking about something related to one specific area, i.e. measurement of displacement, which many people might not be familiar with or share the same background as yours. They will have a hard time understand what you try to say. What I propose is that you do some simple tabular format to compare measurement of large and small specimen and point out side by side what makes it hard for specimen to measure displacement on it. Of course, any pictures or illustrations that help depicting the point are highly recommended.
- Some misspells need to be corrected.
- I think image-based analysis for displacement is quite common out there. Then probably you need to state a bit more precise about what exactly you want to do. Implementing some existing algorithm or developing a new way to do so. Then, in your software development process, I am sure that you have a lot of behind stories that are worth to be mentioned and credit such as interfacing with digital camera, feeding in pictures, calibration, etc. At least, these should be mentioned along with associated problems to show that you have well deliberate through the problem and show how you tackle the problem to reach your ultimate goal.
- Be more precise when you mention about present status and future work. Time-line illustration is a simple and powerful tool to use. It is too vague to just mention your project name again.
- Also, mentioning about problems faced in the project is a very important thing and how you overcome them. This can be done in the summary of this intermediate presentation to show how far you have been through and how much you still have left on your journey.
Comment on the Presentation:
- Over all presentation was conducted pretty well with good fluency in English.
- However, when you try to emphasize the project problem or objective, I think it might be better to be clear and straight to the point. Maybe some language brush-up is required to make sure that what you say will clearly and effectively emphasize the problem and not to confuse the audience.
- The flow diagram is a good media to convey thoughts. You use it well. However, I would recommend that you carefully deliberate more about the logic of your diagram. Each block and arrow should be connected in a logical way.
- While putting on screenshot is a very good illustration, why not demo or short movie clip! I think that is much clearer.
NOTE! Voice comments are available at: http://modred.mit.edu:2323/documents/Alpha-1.wav and http://modred.mit.edu:2323/documents/Alpha-2.wav.
Comments on Slides:
- There is no agenda or outline presented to the audience to guide them through the content. This is an important ingredient for the presentation because it helps the audience understand the big picture of what you are going to present at a glance.
- Structure-wise, your presentation should include a clear goal (although whether you can accomplish it or not is a separate issue), but it’s hard for the audience to imagine this part out of background only. For example, I could see that the need is there for automatic reference generation, but I cannot see along the spectrum of possible solution, where exactly you envisage your project to position. Is the objective of your project is to develop an algorithm to automatically generate the documentation or to develop some kind of add-in module to an existing IDE in the market to help compiling the documentation from the written code?
- Following the previous point, although the algorithm is presented, I am afraid it is still hard for the audience to know how much progress you have made to reach your goal.
- The word ‘reference’ is ambiguously used here. I think the more appropriate word would be something like ‘C++ code reference documentation’.
- However, some small example is given to illustrate what you try to do is a very good thing.
- The present condition in your slide does not help much as your ultimate goal is not stated at the first place. Therefore, I cannot say anything much about this. However, I would propose something like a clear time-line with important milestones on it to illustrate your plan. Then I think it is clear that your project is currently in a good shape or it requires more adjustment in terms of, for example, time line, effort, methodology, etc.
Comment on the Presentation:
- In the part that you try to explain your background, I could see that you can shrink this down to a minute or so since the problem is already well-known to normal developers. You can give some examples in real-life such as java-code without documentation functionality in the old day. Then the point will become really clear. You can save two slides which try to say the same thing.
- As mentioned above, you should state your objective clearly and how you would like to achieve it, i.e. your methodology. Your objective could be “developing an algorithm that generates code documentation automatically” and then your corresponding methodology would be “looking at existing literatures and implement some of the existing algorithms or add some adjustment to the existing ones to obtain your original method”. In short, your objective should be solid and reflect some action that would be required in order to achieve.
- When you explain your algorithm, I think it is always good to have some small example to help the audience walk through your algorithm.
- Also, the quality of the presentation is mainly impeded by the lack of fluency in English. More practices and rehearsals are, of course, required. The number of points made in the presentation can be presented in half of the time if English proficiency is increased. And that means, you can add other important points in your presentation to support your argument as I have pointed out above.
- If the pictures or animations do not contribute to any of your points, try not to put them in as they tend to distract the audience.
Comments on the presentation:
It would be a good idea if the presenter has a copy of slides, instead of turning all the back to read the slides.
Lack of clarity 1) trying to read from paper 2) speak a bit louder
Comments on slides:
Slide 1: The heading Problem Definition is more suitable than Research background. Also, the problem definition is not well explained. Giving an instance of scheduling soccer is a good example to start with but the problem has to be emphasized at a larger perspective as well.
Slide 2: The heading Outline could be replaced by Functional Requirements/ Features. The fourth point is not very clear. The sentence could be rephrased as Interface to view the schedule for all members
Slide 3: Heading could be System Architecture. May be some textual comments along with the arrow would help to understand the figure better.
Slide 4: Heading could be Software Architecture.
Slide 5: Heading could have the form of GUI Graphical user interface. The figures could be complemented with arrows and textboxes for better explanation of the interface.
Slide 6: Future Project could be replaced by Future Work. Password protection is mentioned is slide 2 as well. So it would be a good idea to put it at one place depending on whether the feature was implemented or not.
NOTE!: Comments are also available in voice format for this team at http://modred.mit.edu:2323/Documents/feedback.wma
The comment per slide basis is available at
http://modred.mit.edu:2323/Documents/theta.ppt
Those comments are summarized in the following few paragraphs.
Slide 2:
What is the problem?
Why is the purpose of the pretty document?
What are other alternatives to PDF?
Who are PDFs competitors?
What are the technical, business, strategic advantages of the choices?
Slide 3:
What are the disadvantages?
Slide 4:
There are several open source project for PDF, which one are going to use?
If you are going to redo existing solutions, you should have good reasons.
There are now several large open source sites for .NET like www.gotdotnet.com, you may want to consider .NET as an alternative.
Slide 6:
You should consider moving to a service based architecture to make your architecture more open.
On the idea:
Downloading files by specifying URLS with wildcard characters seems potentially very useful.
On the presentation:
Slides:
Content was understandable but could have been conveyed better. There were grammatical errors that made understanding the content difficult at times.
(slide 2 is an example).
Audio Presentation:
The presentation was slow, clear and understandable. The content however was not different from the slides and the problems with the slide mentioned above were there for the presentation as well. Details regarding the execution of the project were not presented.
Presentation comments:-
-----------------------
The presentation would be much better if the student does not read from the slide directly. It would be much better if he looks at the audience directly and talks louder as well.
Comments on slides:-
--------------------
1. Overview slide looks fine.
2. Slide on "Functions" looks fine too. However, the last line could be changed to "browsing possible through the Web Browsers as well as Mobile Phones".
This point needs to be stressed out.
3. "Platform" slide title needs to change to "System Architecture".
4. Slide on Architecture can be deleted and content such as "Data stored in database" and "Object-Oriented Programming" can either be removed or included on previous page about platform/architecture. For instance, data stored in database is implicitly meant when the student says datastore is MySQL.
5. "Outline of System" slide looks good.
6. Slide on "Present Situation" can be changed from point listing to a flowchart or a box-like representation.
7. Slide on "Future Tasks" has Protected by User ID and Password deleted on the page. It need not be there at all.
1. The presentation and slides gave adequate information about team Gamma's project. The project is interesting.
2. It could be better to give an brief introduction about some background of the technology such as filter bank.
3. There were some grammar mistakes. Also, the word "soft" doesn't mean "software" in all context. This kind of short cut should be avoided.
4. Use passive voice instead of always speaking like "we have...." in presentation.
5. The speaker can greatly improve his presentation by frequent and direct eye contact with audience.