Bi-weekly Progress status
Upate the instructor and the class of your team's progress. Informal
presentation (<5minutes) with the below information.
- Design decisions,
- The target audience for the project (who the users are), personas, user stories if any
- What is the overall design? What are the core features?
- How does the requirements/design satisfy the needs of your users?
- What tools/technologies will you use and why?
- What is the overall design? What are the core
features?
- How does the UI/UX satisfy the needs of your users?
- Screen shots of the user interface or a prototype (in
your intial progress reports).
- Data Models (ER, Use Cases, Class Diagrams, HTA, Sequence Diagrams) - optional
- System architecture and implementation details (if any) - optional
- Current Status
- What is the current status of the implementation?
- What is left to do?
- Who is doing what?
- Status of the Final Report (submitted to Piazza thread as a link to overleaf document)
Final Report (Overleaf)
The project reports must be in the IEEE Information Reuse and Integration for Data Science (IRI 2022) conference
full paper paper format (see below link for Overleaf template): concise
and focussing on what you did. What is important is the submission,
your project grade doesn't rely on the outcome of this submission
(whether your paper accepted for publications). The
project report should be checked for spelling and grammar. Work with
instructor before your submission to review/trim the paper to
approprate format.
- Here's few sample papers, paper 1 , paper 2, and paper 3.
- Full papers must be in English of up to 6 pages (using the IEEE two-column, Overleaf template instructions).
- Write the abstract LAST, since it is easier this way.
- Introduction (1 page)
- Why your topic is important (convince us!)
- Where is it used? Applications
- What you will talk about/do
- What are the main contributions of your project
- Overview of the rest of your paper (section 2 covers...section 3 presents...)
- Background (1page)
- What other people had to say on this topic(s) (be sure to cite your references, and quote as appropriate)
- You
are expected to discuss the books and papers that you include in your
references. You must also cite them. If nothing else, include a brief
rationale explaining why you thought it was useful.
- What other people did on this topic (or related topics)
- Problems and shortcomings of their work
- How your work is different and better
- Methdology (3-4 pages)
- Your approach to the problem
- What you did
- Design
- what you already had (and where it came from)
- what you added/changed
- for parts, include close-up drawings (e.g. Magic screenshots)
- What did/didn't work?
- Include graphs, equations, pictures, etc. as appropriate
- Provide any specific code segments and explanations (non-trivial), this may include in pseudo-code.
- Provide
as much graphics as
you can—not only UI components, but any kind of diagrams and
illustrations that
will make it easier for us to understand and evaluate your effort.
Graphics are
always helpful, you have probably heard the saying “a
picture is worth a thousand words!"
- Do
not just show the diagrams—for all figures, tables, and diagrams
provide some narrative
discussion! Unfortunately, diagrams, particularly technical
diagrams, are rarely if ever self-explanatory. You should document the
alternative solutions that you considered as well as the arguments for
the
final choice. Diagrams only represent your final solution, but do not
explain
why you decided on this solutions and what alternatives were
considered. Hence, all diagrams must be accompanied
with
explanation
and discussion of alternatives and tradeoffs. Anything that could lead
to
ambiguity or misunderstanding on the reviewer’s part, should be clearly
explained. Explanations should be written in prose and key arguments
highlighted in bullet points.
- Results (1-2 pages)
- Your
evaluation (or evaluation strategy)
- What
are the characteristics of users that you would invite to evaluate this
system?
- What
kind of tasks will you ask them to perform?
- What
metrics will you use to evaluate the success of your system?
- Comparison
with existing applications (which)?
- Performance
measures (how will you measure them)?
- Other
criteria?
- Include
relevant observations, measurements, and statistics. For example, for
the VLSI Class: Include statistics such as timing information if
available by simulation, or if not, your own analysis about critical
path, delays, and clock cycles. Be sure to include size information:
the total size of the circuit measured (X lambda by Y lambda), and the
transistor count.
- Discussion (0.5 pages)
- Try to draw together the intro, background, and project sections.
- How do they all relate together? (They may appear to be disjoint sections to an unfamiliar reader).
- Restate important results
- Conclusions (0.5 pages)
- What was accomplished / learned
- What you would have done differently
- You should
also include your conclusions from the study and point out how your
work can be
further extended (i.e., future work).
- References (0.5-1page)
- You should include a number of books and papers that were useful. About 10-20 citations
- Webpages do not count toward this minimum number. Wikipedia is not appropriate, and you will be penalized if you include it.
- Cite the papers/books that you used
- Anything you found useful (check with me if you are not sure)
- References should
list ALL sources that you used for your project. It
is
recommended that you list your references in the IEEE Square numbered style. All team members must be involved in preparing this
section, and provide a list of URL's, books, or other sources that they
used
for the project.
Final
project presentations / demos
- The project schedule and sign up available at Piazza
- Time 15 mintues per each team + 5 mintues question/answer.
- When
your 15 minutes are up, I will stop you and we will move to the Q/A
time. During those 5 minutes, the next team should begin to setup. We
will start the next presentation exactly 5 minutes later. If you have
trouble setting up, you will lose time for your presentation. As a
result, I highly recommend that all teams do a walkthrough of their
presentation before Thursday, just to make sure that whatever
resources you need are available.
- In terms of content, you will
have to make hard decisions about what to include in your presentation
(and what to cut). Do not feel like you have to jam every technical
component into your talk; indeed, presentations that sacrifice clarity
for overstuffing inevitably fare poorly. Remember that you have the
project report as an avenue for communicating all of the details of
your approach, so you are free to use the presentation as a
higher-level opportunity to motivate your part of the project, give clear insight
into your approach, and give us a flavor of your overall development and
results. Manage your time carefully.
- Specifically, you should probably use fairly large fonts
and clear figures.
- All team members must participate!
- As we assess your presentation, here are some of the points we will consider:
- Preparation
and poise.
Did you speak to the audience rather than look at the slides? Did you
expand on what was on the slides rather than read them word-by-word?
Did you speak at a reasonable pace rather than too fast or too slow?
Did you appear to be spontaneous and fluid, avoiding the use of
distracting mannerisms and colloquialisms?
- Use of
allotted time.
Was there a good balance between inspirational material and technical
content? Did you complete your presentation in time? Did you have to
skip some important material (e.g., conclusions) in order to complete
your presentation in time?
- Use of
visual aids.
Did you use pictures/diagrams to explain your ideas? Did you have
graphs of experimental results? Did the slides contain short, clear
bullets rather than long sentences and/or cryptic equations?
- Presentation
is visually appealing and strongly effective presentation. Easy to read
slides, utllized creativity in use of graphics, headings, colors, and
white space to provide sequential information from introduction to
conclusion.
- Presenters are confident and professional
with eye contact and clearly conveyed problem, methods, techniques,
conclusions. Answer questions well.