project plan with milestones and deliverables

[laughedelic]

No description provided.

[laughedelic]

Meeting conclusions for myself:

• JSON format:
  • more detailed description
  • example (comes from the model-service)
• Model-service:
  • example for GO
  • usage documentation

[carmen-tm]

Work Plan based on my GSoC Submitted Proposal initial work plan reviewed.

I'm much more comfortable on the design/proposal side than on the coding-work plan one... don't know how to approach it and if it makes sense, I think not yet. I've just distributed all elements appearing on the proposed Representation structure #5 along the Phase1 - MODULE TEST PHASE weeks. Any feedback about usual coding processes/this particular project is more than welcome. I'll keep on researching a bit on Internet to complete it along the weekend.

Phase0. Self-learning period.

From 2nd week March – 2nd week May
/2 months, partial dedication/

• D3 basics self-learning period through on-line resources.
• Familiarization with Github platform, MarkDown... as usual tools to be used during the work period.
• Familiarization with Linux new environment.
• Small research about existing things done with d3 & graphs/networks. Compilation of example codes from bl.ocks.org
  TO DO: moving and organizing the examples compiled into a el-grafo branch, and keep on reviewing them or adding stuff.
• Small representation experiments with Force layout based on the above examples, in order to understand their code, using a JSON test example file.
• Collaboration on defining the GraphSON representation of the data model.

Phase1. Module TEST Phase

From 19 May – 27 June.
/6 weeks, full dedication/

Week 1: May >> Pre-coding phase extension

• Main browser/representation structure design definition. Basic appearance, features and user interactions draft.
• Design/representation aspects doubts
• Getting an example file of the module schema to start working with the graph > GO Module.

Week 2: May >> Working with graph-data example

• Working with graphlib to test some of their functions and graph algorithms (will be used for contextual menu actions when exploring the network)
• Working with dagre lib lib to test how it lay outs the model.
• Revision with mentors of main functionalities achieved, issues, etc.
• Possible new requirements on the .json structure will be required afterwards.
  Deliverables -> html tests done.

Week 3: June >> Zoomed Network View

• Network aspects/restrictions rendered with SVG objects
• Threshold implementation to control the fragment size loaded.
• In/Out break of the network feature based on previous graphlib/dagre tests.
• Contextual Menu features based on previous graphlib/dagre tests.
• Revision with mentors

Week 4: June >> Full Network View

• Integration of the GO Module as full network visualization: election between d3 force layout/cola.js alternative or dagre layout.
• Path drawing feature
• Text Search element feature to find a certain node/edge label
• Minimap for guidance
• Revision with mentors

Week 5: June >> Route Map View

• d3 tree layout integration
• Contextual menu features: exit selection for undo steps.
• Properties and Indexes labels integration on the scheme, with "copy route" element.
• Revision with mentors

Week 6: 23-27 June >> Mid-term evaluations period.

• Resume of the project state and Test outcomes will be uploaded to the GSoC platform.

Phase2. Complete Database Integration Phase

From 4th week June – 3rd week August.
/8 weeks, full dedication/

Week 7: June-July >> Integration of the whole Database Graph
Week 8: July
Week 9: July
Week 10: July

Week 11: July >> Optional ....
Week 12: August
Week 13: August
Week 14: 18-22 August >> Final evaluations period.

• Final outcomes will be uploaded to the GSoC platform.
• Revision of the project state and possible implementations list.
• Optional-1: Alternative new layout. Design and coding.
• Optional-2: creation of a new d3 component for working with graphSON data.

[eparejatobes]

@carmen-ooo sorry I couldn't take a look at this until now. I'll review everything, and schedule a meeting for maybe tomorrow. I'll write something this afternoon/evening US EST

[eparejatobes]

At last I could do this. It looks reasonable in general. I will read #5 and #7 first and then I'll come back here

[carmen-tm]

hola, estoy probando cosas