Project 3: Disaster in St. Himark!
- Project screenshot (a 1200 x 600 gif image of your visualization which should be named p1.<your_last_name1><your_last_name2><your_last_name3>.gif), demo link,
and github link are due at 11:59am Friday, May 10th to the nhat.le@ttu.edu
. Nhat will make an html table with your group projects.
- You can update your source code and project report uptill 4:30pm Friday, May 10th.
- This project is 30% of your final grade:
- 20% for design and implementation.
- 5% for in-class presentation.
- 5% for project report on Github.
- Each student needs to send a peer evaluation for other teammates by 11:59pm Saturday, May 11th to the nhat.le@ttu.edu . This peer evaluation is
significant to your individual project grade. One team member can get A but another can get D or Fail. The
peer evaluation contains:
- Teammate name.
- Rating from 0 to 5 (5 is best).
- Less than 3-sentence review.
Project Description:
- Project 3 is a group (3 or 4 students) project. A leader is also selected by the instructor.
- Students are provided 2 datasets:
- VAST Challenge 2019 with the Sample datasets: Each group will do one mini-Challenge
- Cybersecurity's Datasets
-
By 11:59pm Tuesday 4/16, you will need to select the topic for your Project 3 and send the nhat.le@ttu.edu (cc the instructor). You also need to send a group photo to show your group integrity. You loose 1% everyday for the delay.
-
At 3:30pm Thursday 4/25, groups present project planning and duties of each team member.
-
At 3:30pm Thursday 5/2, groups present on-going interface and the instructor will provide feedback and recommendation. Teams work on the same challenges can discuss.
Notes:
This project is a web-based application in javascript, html, and D3 (you can use other javascript libraries).
Your code should run on all browsers (Chrome, Safari, Firefox, Explorer,...). No refreshing: Every
refresh costs you 1%.
Your application should start out showing some data or an overview and then allow users to add more or request
details on demand. Do not start with an empty screen and do not overwhelm viewers by showing a lot of the data
right away.
Do not write the application at the last minute to avoid mistakes. Make sure that your code runs and that you
have enough time to design intuitive interfaces.
Make sure your code is well commented (this is a good practice since you will work in a team). Instructor may
inspect your source code.
Project report on Github (readme file):
Create a 3-minute video showing the use of your application with your voice over. That video should appear on
the top of your github readme file.
The video is a good way to show your interactive application in a short amount of time. If you submit a paper to
a visualization conference, a video is very useful. It can be also a backup during your presentation just in
case of something go wrong.
Add a link to your web-based application (right after the video). You can host it on your github or your ttu personal page.
Clearly explain the duties of each student in your group.
Discrible your application and highlight your findings by screenshots.
In-class presentation:
The presentation is 10 minutes per group (everyone needs to present). It is 8 minute talk and 2 minute for
questions. Make sure that you are ready to talk right after the group in front of you is done.
Please practice your talk. Show the basic functionality and emphasize on why your visualization is different.
Group Assigned
Team |
Members |
Topic Selection |
Screenshot |
Team Photo |
Dataset |
Demo Link |
Github |
Evaluation |
© Last revised: April 26, 2019