-
Notifications
You must be signed in to change notification settings - Fork 0
Progress updates
markfuge edited this page Nov 30, 2011
·
14 revisions
Weekly project goals, to be used in conjunction with our Pivotal Track Log:
Mark
- Review any code and help out where needed.
Christina
- Work with Matt on linking the graph and container.
Sahana
- Minor changes to HTML and styling.
- Finalize user testing doc for a test to be run in the latter half of dead week.
- Add Instructions to website HTML.
Matt
- Work with Christina on front and back end.
- Work on keeping favorites up to date on the front end
- Implement notifications for additional information etc.
Mark
- Review any code and help out where needed.
- Write degree computation code for Matt and commit to GitHub
Christina
- Finalize website design changes - Check. Sahana taking this over. Everything looks good so far. Minor changes will be complete next week.
- Work on Integration between front end and back end - Mostly done. Just need to link the graph and container, and debug.
Sahana
- Organize and e-mail out the process plan for another user test on the online prototype - Should include screen captures and audio recording. If possible, both Christina and Matt should observe, but you should run the entire test. - Check. Finalizing for next week.
- Take care of centering etc. for the front end + instructions - Check.
Matt
- Work on Styling for no remaining neighbors code, once Mark finishes his function for computing degrees. - In Progress
- Work with Christina on Front End and Back End integration (i.e. Saving and loading the graph). - Mostly done. Finalizing for next week.
- (optionally) working on the favorites. - Working on for next week.
Mark
- Review any code and help out where needed. - check
Christina
- Work with Sahana to fix up any HTML/design bugs that currently exist. - Check
- Add in the ability to add/edit nodes, as well as edit view titles (or at least give them a default name). - Check.
Sahana
- Finalize the site instructions and add in the HTML lines that display them on the site. - Just have to add to website code.
- Work with Christina on fixing any HTML/design bugs. - Check.
- Get Matt a list of user events that occur in the d3 app which result in changes in the front-end. - Check.
Matt
- Implement project saving on keyed actions, using the list that Sahana provides as a reference. - Almost done. Need to integrate with Christina's code.
- Try implementing a static CSS styling of the "no more information" notification on the application. - Check. Waiting for Mark to implement the
Mark
- Review Christina's Django code and help her out if she needs anything. - check
Christina
- Make static HTML files visually consistent and workable using the files on GitHub -check. Some minor HTML bugs will be addressed next week
- Read the Django tutorial and modify the HTML files to follow the template format that Django uses. The templates should use the models.py file that you made towards the beginning of the semester in order to populate the data fields in the template. - Check. Very nice work here getting everything working together.
- Make sure that the models.py file is complete so that Matt and Sahana can work from it. - Check. changes to the Node class will be necessary, in order to make views work, but that'll be worked on for next week.
- Get a rough version of the code working on the local SQLite database - Check. Well done on this, Christina.
Sahana
- Refine ideas for incorporating instructions into the website, developing a testable prototype, and work with Christina to make sure that the models.py file and HTML site is updated accordingly. - Check. Final fixes to be addressed by next week.
- Review the Django Tutorial - Check.
- Read through the current views.py file in the "similedb" directory and understand how each line is working. - Check
Matt
- Review the Django Tutorial - check.
- Read through the current views.py file in the "similedb" directory and understand how each line is working. - check.
- Work on the features and bugs in Pivotal tracker for this week. - didn't check.
- Ideas for keeping track of whether a node had info or not - Check. Going to implement some for next week, if enough time is available.
Mark
- Be available if anyone needs help on anything. - check
Christina
- Make static HTML files visually consistent and workable using the files on GitHub - Added to next week's deliverables
- Read the Django tutorial and modify the HTML files to follow the template format that Django uses. The templates should use the models.py file that you made towards the beginning of the semester in order to populate the data fields in the template. - Added to next week's deliverables
Sahana
- Design 2-3 ideas for incorporating instructions into the website, and bring them to the meeting. - Check. Presented 1 idea, will work on implementation for next week.
- Ensure that the results from the latest user test get incorporated into the website design. - Didn't check on this.
- Decide on which portions of the front-end vs visualization the instructions will live in, and coordinate with either Matt or Christina so that they have a heads up on what might need to be worked on. - Didn't check on this.
Matt
- Work on the features and bugs in Pivotal tracker for this week. - Check
Mark
- Arrange users for Christina and Sahana to test on - Check
- Put bugs found during workshop session into Pivotal Tracker - Check, though should have added them earlier.
Christina
- Conduct website user test with Sahana - Check
- Put bugs found during workshop session into Pivotal Tracker - Didn't check this
- Static HTML version of site complete. - Check, though the files didn't work in GitHub and were not visually consistent
Sahana
- Put bugs found during workshop session into Pivotal Tracker - Didn't check this
- Conduct website user test with Christina - Check. Hybrid test was well coordinated, though in the future more prep should be done prior to the test day to work out all of the kinks.
Matt
- Review backend Django code to become familiar with how everything works - Didn't check this
- Get started on bug fixes found during the workshop testing. - Sickness issues
- Consolidate new features and bugs for the graph visualization, based on our combined feedback from the workshop, that have been entered into Pivotal - Check
Mark
- Get BEST Server ready for Django deployment - check
- Get users to test graph interface for Matt and Sahana - check
Christina
- Figure out how to match the foreign keys to objects in Django -check
- Work with Sahana to make an appropriate Wizard of Oz prototype for testing on users (can be physical or electronic) - check
Sahana
- Run user test with Matt on the graph-based interactions - check
- Write up a summary of the insights gained from the user study on the graph interface - check
Matt
- Implement the node addition functionality and get the rough prototype working with the Django backend - check
- Work with Sahana to run a user study on the graph interface - check
Mark
- Upload a full version of the sqllite database to GitHub - Check
Christina
- Look over the Django Tutorial, paying specific attention to the "Models" section, which describes how Django stores and accesses data. - Check. Models look good.
- Code the models.py file for the interface design presented today (you don't have to worry about the graph part, but you do have to worry about the adjective list, etc.) - Check. Models look good.
Sahana
- Read over the entire Django tutorial (Parts 1-4),
- Read through Rubin's Ch. 2 in the Usability book
- Generate a few scripts of tasks for users to do to test the general website UI. Bring these in so we can review them. - Check, looks good.
- Generate a few scripts of tasks for users to do to test the graph layout code. Bring these in so we can review them. - Check.
Matt
- Implementing our node evaluation into D3.js as a rough prototype. We'll all review the progress at the group meeting. - Check. Nice work. Prototype looks good for a week's worth of work.
Mark
- Upload cleaned up code to GitHub so that people can makes the appropriate branches of it - Check
- Commit an updated sqllite that works with local drupal development settings. - Check, though only a reduced size database
Christina
- Set up GitHub and clone a version of code, create a branch for yourself off of the "dev" branch, and look over the Django code to get familar with how it handles models, views, and urls. - Didn't check this.
- Merge some of your initial concepts into two candidate final designs, working with Sahana to explore the space of ideas and experiment with the graphic design details. At the meeting, present detailed sketches of the two candidate final designs (can be in color or B/W, whichever is easiest for now). If a design has additional screens/menus (such as a separate login page or a non-traditional type of menu which pops out, etc.), use additional sheets of paper to display those elements. We should be able to roughly evaluate the full work-flow from the given sketches. Though both you and Sahana will be contributing to this, it is ultimately your call on the final design decisions. - Check. Some potential space issues were discussed.
Sahana
- Set up GitHub and clone a version of code, create a branch for yourself off of the "dev" branch. - Didn't check this
- Brainstorm with Christina on website graphic design and layout, based on your findings from the prototype sessions. You will be responsible for making sure that your user experience recommendations are reflected in the two final concept sketches produced for the meeting. - Check.
Matt
- Set up GitHub and clone a version of code, create a branch for yourself off of the "dev" branch, and commit any changes you may have made to Alex's JS Prototype - Didn't check on this
- Finish looking over any available web-based network graphing libraries and see if we can use them to simulate the current functionality of the prototype. Have a recommendation ready for next week's meeting about which library, if any, we should move forward with (knowing that our next move will be to implement something using that library). - Check. Decided to go with D3.js as a first pass, with initial tests due next week.
Mark
- Get GitHub/BitBucket up and running - Check, though without uploading code.
- Get Matt/Sahana Alex's Javascript prototype code - Check
Christina
- ~10 website wireframe ideas - Check. Ideas looked awesome. Very diverse set. Good work.
- Read over Django tutorial and try it out so that you'll be ready when Mark gives you the current code.
Sahana
- Read Jono's Metaphors in Design Paper
- Evaluating the following metaphor prototypes, noting note the good/bad and what each prototype offers that the others do not. - Check. Good insights from meta4acle and Design Simile tool. Interested to see what we can apply to new design.
- Paper prototype
- meta4acle.com
- Design Simile Website
- Alex's JS Prototype
Matt
- Brush up on JS and learn jQuery by making Alex's current JS prototype use the .data method, instead of tags - Check. Turns outtags comply with HTML 5 spec, so we'll keep that.
- Investigate alternative visualization libraries that could provide the current prototype abilities and make our future lives less work - Check. DataVis and some others explored. More rigorous work needed on assessing viability of those libraries as replacements for current JS code; pushed to next week.