Better UML diagrams: 2015/06/01

Status report

Class diagram abstractions level : We constructed several abstraction level experiments based on grouping connections and related elements together. (See post)
Final report draft writing : We worked a lot on our final report draft and sent a version to our Chalmers supervisor and examiner (2015/06/15). We didn't get feedback yet as of 2015/06/22.
Neato and PlantUML : We began exploring PlantUML source code and studied the possibilities of switching PlantUML layout algorithm to Neato. In summary, switching the layout algorithm is easier said than done. The source code is quite complex. We mailed the PlantUML developers to get some tips and input on how it would be possible and even though they are really interested by this functionality (which was also on their to-do list), they warned us on the complexity to do it in the amount on time we have left. Therefore we decided to leave it on the side for now and focus on abstraction to collect feedback before everyone leaves on vacation. We will pick it back up later on.
Getting feedback : We presented our latest results (2015/06/12) to our Ericsson supervisor to get his and his team feedback. Awaiting for answer.

Getting feedback: It is critical that we get feedback before our supervisor and his team go on vacation so that we can develop the solution while they are away. We are awaiting for feedback on our abstraction propositions and on the rules making elements "relevant"/"not so relevant" to show on the diagrams.
Abstraction - statistical analysis: Our abstraction experiments so far focus on grouping and presenting element differently while preserving the original information. Another track we are exploring without knowledge of the system is to get statistics on components' names, number of interfaces and connections to see if it correlate to what our supervisor identifies as "important"/"not so important" component. This is based on Truong Ho Quang's work.
Continue on the final report writing