You may copy/paste it here, or add it in as an attachment (For example, write “See Attachment A” here and put an Attachment A line in your table of contents.)
Deviations from Original Proposal & Justifications
Explain anything you changed from your original proposal. This includes features you added in and those you removed or altered in some way. Here is one way to do this as an example, but you may tell us this in any way consistent with your project.
- Layout change to something that was more consistent with the Bootstrap framework. The layout included in the proposal was more suggestive than a strict guideline – the size of the required graphs was an important factor which could only be truly understood when implemented.
- Separated bar charts to one variable only. In the proposal and the outlined layout, I had grouped the bar graphs for certain variables, such as product + sub-product, and issue + sub-issue, together. But closer analysis of the data made it clear that they should be visualized separately rather than together. The d3.js libraries were also more suited to create visualizations in an independent form rather than a combined form.
- Note: There were two boxes in the bottom right corner of the layout image in the proposal for company response and name of the company. But I decided to leave those two variables out even in the technical details as I had realized that they do not add much value relatively and could also result in cognitive overload for the user.
You may copy/paste any user feedback, user manuals, etc., here or you may add them as an attachment. You can also explain anything about the reports here. See below for one example.
Attached with this document as Attachment B. The timeline was not completely running by the third checkpoint so I ran the user tests again after the timeline was working.
You may copy/paste your code here or add it as an attachment, or put it on a flash drive / CD / DVD, or upload it somewhere like Dropbox or Google Drive with a link to share it with the department. If it fits you can also upload it to Moodle. Explain any rationale here as well. See below for one example.
The ata could not be uploaded on Moodle as the file size was too large, even when compressed. I have included the link to download the data in the references.
Tell about your experience with your project – anything important you learned and the conclusion of your project. What went well? What didn’t go so well? What problems did you encounter that you did not foresee? What are you proud of for accomplishing? See below for one example. This section will vary based on your own experience with your project.
The most important aspect of a data visualization is the data and its characteristics. This is one aspect I did not consider in depth when starting the project. Since this project is mostly exploratory rather than driven by a message, I was more interested in being surprised and finding more about the dataset. The biggest problem was the different unique fields in three variables made it impossible to graph them without further analysis. That part of data mining was unplanned but crucial. For future projects, that is going to be the first order of business. Do quick analysis and visualizations in R and then proceed based on what picture the data paints.
本网站支持淘宝 支付宝 微信支付 paypal等等交易。如果不放心可以用淘宝交易！
E-mail: email@example.com 微信:itcsdx