Scribd Logo
Upload

Welcome to Scribd!

  • 3 views

    Final Report Instructions

    Uploaded by

    Eduardo Pereira Bártolo

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd

    Final Report Instructions

    Uploaded by

    Eduardo Pereira Bártolo
    3 views2 pages

    Original Title

    Final_Report_Instructions

    Copyright

    © © All Rights Reserved

    Available Formats

    PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Download as pdf or txt
    3 views2 pages

    Final Report Instructions

    Uploaded by

    Eduardo Pereira Bártolo

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Download as pdf or txt
    of 2

    InfoVis Final Report Instructions

    Objective
    For the final report of your InfoVis project, you should write a document using the provided template
    (SIGCHIPaperFormat.docx), with no fewer than 6 and no more than 8 pages long. You can adapt the
    sections to what is relevant for your project, but you should at the very least focus on the following
    things:

    1. Introduction
    Describe the problem domain you are going to address. Why is it relevant? What questions are
    unanswered? What is the motivation for addressing it? Don’t current tools already do what you need?
    What did you expect to gain from your approach? What questions do you propose to allow (from
    Checkpoint I)? New ones, even?

    IMPORTANT: explicitly list the questions you defined in Checkpoint I

    The intro should give someone who didn’t know your project enough background to understand it.

    Generic text about how nice this was, how it allowed you to overcome interesting challenges, etc. Fluff
    that I could transplant to any other such report is, most likely, not good. Be concrete. Here, and in the
    rest of the report!

    [NOTE: Part of this comes from what you decided in Checkpoint I]

    2. Related Work
    What similar works did you find to yours? Where did you get your inspiration? Scientific papers would
    be great, but at least online references should be here. You should be describing other works that
    visualize the same problem domain (or similar ones), and explain why they don’t really do what you
    need.

    [NOTE: be honest here. Mentioning something you already saw, even if it is similar to what you
    ended up implementing, is not considered a bad thing. You won’t get downgraded because you
    implemented a similar solution (only if you copied someone else’s code…)

    On the other hand, you WILL be downgraded if there is some obvious previous system (or it is just a
    google search away) and you neglect to mention it]
    3. The Data
    Where did you get your data from? What challenges did you face? Did you have to correlate sources?
    Did you have to clean it up? What data did you think you’d get and ended up not finding? Which
    compromises did you make? Also, be sure to mention scalability issues. Did you have to filter things
    out? Aggregate them? Derived measures? Go beyond Checkpoint II: after it, did you need to revisit the
    data and its format? Make changes? Describe them and why.

    [NOTE: We don’t need an exhaustive description such as the one in Checkpoint II. We want a
    narrative, a story of what you had to do and why, not lists of column names, etc. Copying and pasting
    the things from Checkpoint II here won’t work.]

    4. Visualization
    Be sure to profusely illustrate this section!

    4.1 Overall Description


    What is your solution? Start with an overview of the system (layout, etc.), how it works (how data can
    be filtered, selected, etc) and then move on to describing the different visualization techniques,
    showing how each works and gets the job done.

    4.2 Rationale
    Why did you think your techniques would work? What visual encodings did you use and why (and why
    not others)? What alternatives did you consider, even if they turned out not to work? Especially,
    discuss how you managed the complexity of real data, and matters of scalability. Also, include in your
    discussion the evolution of the prototype, from the initial sketches to the last version highlighting what
    you learned from version to version and how that influenced your design.

    4.3 Demonstrate the Potential


    Describe for at least a couple of cases (from the questions you promised you’d answer before) where,
    step by step (illustrated with screenshots), you find the answers you seek. In short, demonstrate the
    potential of your solution! Does your visualization provide insights on data that you were not expecting
    / that are not common knowledge? These are pure gold! Be sure to include them!

    5. Implementation Details
    What challenges did you find and overcome? How did you implement the links between the views
    (incl. brushing, etc.)? What algorithms did you use? What techniques did you adapt, or implement,
    from scratch? (instead of just copying & pasting them from the D3 examples page…)

    6. Conclusion & Future Work


    What did you learn? Were you able to address all the questions? If you were to start over, what would
    you have done differently? Also, if you now had 1 more month and €3000 do spend on this, what else
    would you do to enrich your solution?

    You might also like