Tag Archives: conference

Speaking at Brussels JUG: User Experience for Business Process Applications

I’m glad to inform that I will speak at the next Brussels JUG‘s event about user experience thinking and design for business process applications. The event will take place at Hogeschool-Universiteit Brussel, Building Hermes, on Thursday, 30th of May, at 6:30 pm. Visit Brussels JUG website for more information: http://www.brussels-jug.be.

You won’t find a lot of information about this subject on this blog, but I have been doing research about it in parallel since 2006, in collaboration with Kênia Sousa, who would be happy to share the stage, but she had to decline due to family duties. You may find more information on the page Publications of this blog.

If you were assigned to design and implement a business process based application, You may find this session interesting. User interface design is the most time consuming task in a software development process. It is highly subjective and under heavy criticism by end-users. This presentation will help you better deal with this problem, exploring strategies to represent business processes in a way that end-users can easily understand what they see based on their business knowledge. We will discuss about a different approach for Business-IT traceability based on UX, an architecture and a methodology to support constant process changes, navigation approaches and the right widgets for the right actions.

See you there!

Freedom of Thinking and Speech at Devoxx 2012

I have been attending Devoxx in a row since it was called JavaPolis and then they had to change the name to Devoxx due to copyright issues with Sun Microsystems at the time. I have the privilege to live close (in terms of world, but far in terms of Belgium) to the hosting city, Antwerp, and I’m used to be passionate and engaged with the Java international community. However, the main reason I’m successively attending this conference is because they excel every edition, making the next one unmissable. This year it wasn’t different.

Stephen Janssen trying to find 200 available places in that crowded geek audience.

Devoxx is probably the only conference in the world that manages to put Oracle and Google face to face without conflicts. This is such a great achievement that I would recommend Devoxx’s team to the United Nations in order to address the conflict in Gaza and finally put an effective peace process in place between Israel and Palestine 😉

By the way, I should say something about the way Oracle leads their keynote speeches. Last year Oracle made a pretty boring presentation, but it was ok after all. This year they exceeded themselves making a pretty boring + chaotic presentation. First, Nandini Ramani, vice president of engineering, Java client, and mobile platforms at Oracle, was clearly nervous on the stage. At some point, she called Stephen Chin to join her and he didn’t show up. Ups! She decided to jump to the next presentation, which was clever, but right in the middle she was interrupted by the sound of a motorcycle, causing a pretty awkward moment. What?! 😀 Yep! We initially thought that the staff accidentally opened a door, bringing noise from the traffic, but in fact Stephen Chin suddenly came out with the motorcycle used in his Night Hacking Project. That was actually pretty cool except by the fact that Nandini was completely taken by surprise. She couldn’t handle that unforeseen situation and she just handed over to Stephen, leaving the presentation halfway. Still, we had a lot of fun watching the situation. 😀

On the other hand, Google made a great tech show! Wow²! They know how to hold the audience’s breath. The only issue (at least for those urging to visit the toilet) was their inability to manage time. The presentation took longer than expected, but every second was pretty well spent on exciting demos! Cool!

So, what do I learn from that? From my perspective, I see Devoxx as a great independent conference where it’s possible to closely compare leading competitors and make realistic decisions about the technologies we are going to chose for the coming years. Devoxx is definitively the best alternative to avoid brainwashing conferences such as JavaOne (It wasn’t like that in the past). This is to say the least, because they managed to overcome our expectations by adding a special track named Future<Devoxx>, focused on the programming of tiny devices, such as TinkerForge, Arduino, Raspberry Pi, and others. Curiously, there wasn’t a single mention to the classic SunSpot, which is probably one of many nice projects killed by Oracle after acquiring SUN. That track added a world of possibilities to all those entrepreneurial minds. Well done!

Is that all?! Not yet. Mother Devoxx is going to have a new baby next year! After Devoxx France, they announced Devoxx UK. Yeah, attending Devoxx became a touristic problem now, based on the city you wanna visit 😉 Last, but not least, Devoxx4Kids is definitively a great initiative! I actually wanted to attend it, but I have to wait for my little boy, who is only 11 months old now. I’m giving him twice more milk to watch him grow up faster 😛

Writing Scientific Papers

When I was a young researcher nobody taught me how to write a paper. Maybe, it is a sort of a test: if we prove we can write one, without any guidance, just taking into consideration other papers, we are ready to face the research world. In fact, many young researchers don’t even know what a paper is useful for. Their lack of understanding and absence of instructions bring them fear and low self-esteem to write one.

Recently, I received some papers to review and I could see a lot of evidences that novice researchers still make the same mistakes that I used to at the time of my debut. I have contributed in publishing 17 papers so far, and it gave me some experience to share with you about paper writing. My intention is to be clear and honest, so there is no rigor in this text and I don’t try to magnify the academic world with nice words.

A paper is a written report of what is going on during a scientific research. That’s why it is so boring to read. This report should be published somewhere. If we do not publish it nobody will actually know that we are active in research, thus we are not considered as researchers. If we publish, good! It means that other researchers have read and evaluated our text, identifying some innovation there. There are many kinds of publications. We can publish our work in conferences, workshops, journals, etc. Some of them are more accessible, others are more challenging. “Challenging” means that the researchers that will review our paper might be top specialists on the field, and if we are good too, they are our competitors. It usually happens when we submit to a journal. “Accessible” means most conferences and workshops. Renowned conferences work like journals, but a lot of conferences are not so rigorous and our papers might be reviewed by specialists, but not necessarily in our field, which will lead them to observe other aspects, like scientific methodology, text quality, structure and some logic in our words. The formula of a good conference is  = tradition (several years) + strong reputation (stars in the program committee and hosted by renowned institutions) + blind reviewing process + strong sponsors (i.e. ACM, IEEE) + no submission extensions (important dates are like mountains: they don’t move).

In general, a paper has the same structure of how research is conducted. However, we don’t have to write this exactly sequence neither use them as our section’s titles. You can be original, but please, preserve the essence. This structure is as follows:

  • Abstract: Considering our incredible summarization power, we have to write a few lines about the paper’s contribution in order to convince the reader to consider the work. People who are looking for references for their state of the art definitively appreciate well written abstracts.
  • Introduction: We introduce the document explaining the context where the research is inserted, which problem of this context the work is going to explore, a summary of the solution and the consequences of solving the problem, concluding with a reading map of the rest of the document. The introduction does not give details about the research, but it should invite the reader to continue through the rest of the content.
  • State of the art: Depending on the maximum size of the document, the introduction can also contain the state of the art in case of small papers (up to 6 pages), but it is so boring to read that it’s better to put it in a separate section, giving the option to the reader to jump it. But only when we have more space to write (over 6 pages). The state of the art describes recent advances that have been developed elsewhere. These advances are cited to a) justify our decisions; b) show a gap that our work is going to fulfill, or c) show a similar work with a different approach to solve the same problem we are exploring. The content of our work is supposed to be new, built on top of the state of the art and the rest of the paper is to prove that. It’s important to mention that some authors prefer to write the state of the art after the contributions, but it is just a style of writing.
  • Contribution details: The most important part of the paper is where we describe the work we have done so far, and it should contain something new over the presented state of the art. This new “thing” should be described into details in order to allow reviewers to fairly evaluate our work, and give us a constructive feedback. The more distinguished is our contribution from the state of the art the more chances we have to get our paper accepted. That’s why it is called contribution. Contribution to the science.
  • Validation: Ok, we have done a nice contribution, described it into details already, but how can we prove that it is actually realistic and useful? So, we have to describe how we could validate our research, showing the procedures, the execution and the results. Validation might be the hardest part in a research because the contribution is just an idea and the validation is the implementation of this idea. The same way we cannot trust a software that was not tested, we cannot trust a research that was not validated.
  • Discussion of Results: The results obtained during the validation deserves additional attention. We can use them to compare with other papers’ results, analyze possible implications and so on.
  • Conclusion: Some people make a summary of the whole paper in the conclusion, but we have to summarize only our contributions, validation and obtained results. Introductory discussions and state of the art are irrelevant here. The conclusion also considers future works, which is actually what we didn’t have time to do, and probably will never have. Who knows? But at least, reviewers will not complain about those future works because they are out of scope.

Depending on the reader profile they will read our paper in different ways. Of course, we will be the first to read 100% of our paper, maybe many times, and the last one too. Nobody else would be so patient to do such a thing. The reviewers don’t have time to lose because they have 10 more papers to read, besides other several duties. So, after the abstract, they will jump to the conclusion, see the contributions, go through the results, and finally write the review. Conference’s attendees will read only the abstract. After being published, only young researchers and people out of the research community will read the paper’s introduction. For experienced researchers, our abstract should be enough because they know too much about the field and they don’t have time for bla, bla, bla. In summary, each part of our paper has a particular audience and we should consider them in the writing process. The only exception are journals and renowned conference reviewers, who will read 100% of the paper like we did, and that’s all.

To be honest, I don’t like to write papers, but sometimes we have to do what we don’t like to get what we want. During the PhD, publishing a certain number of papers is mandatory. The better is the journal or conference, the easier will be the PhD defense, because the jury is aware that they don’t have to be so rigorous if other researchers in the academic world already have. After getting the PhD, the number of references to our work becomes more relevant (other papers referencing our paper in the state of the art) than the number of publications we have. Seeing these as indicators, the number of publications shows our research activity and the number of references shows the relevance of our work.

Besides that, I also have problems to conciliate formal language, readability and deadlines. That’s why I love so much my blog, a place where I can express myself through my soul.

    Usi4Biz Presentation at Devoxx Available on parleys.com

    The presentation of the Usi4Biz Platform at Devoxx’09 was fully published on parleys.com. When we say “fully” we mean 100% of the content published, which includes a video of the speaker, synchronized with the slides and also with the demo of the Usi4Biz Platform.

    Click here to see a preview of the presentation. To watch all 132 Devoxx sessions, including our own session, you can register on parleys.com for only 49 Euros. A very good deal, considering the high quality of all conference’s talks available on demand.

    Presentation published on Parleys

    ICMI’09 Video

    In addition to the experience reported at “ICMI-MLMI 2009 at MIT” and “Discussion about Context during the UCVP Workshop“, I’m publishing a video showing the visual experience of the ICMI’09 at MIT Media Lab.

    Publishing this video, I wish to motivate myself, my colleagues and thank UCL/TELE Lab for this opportunity. It is supposed to be just one more conference, one more place, one more line in my CV, but it is more than all of that. As a simple person, of course, I add an enormous value to this experience and this is a way I found to share what inspired me there.