02341: Model-based Software Engineering (f16)

The final presentations of the project in the course Model-based Software Engineering (f16) will be held on Monday, May 30 and Tuesday, May 31, 2016 in room 303B.136 (Matematikum). This room has a big screen and a white board available for the presentation.

You will find the schedule for the presentations of the different groups blow. If your group is not mentioned, or if your group could not do the presentation at the given slot, please, contact Ekkart Kindler right away. This also applies, if you should not be a member of a group yet.

Schedule, Monday, May 30:

•   8¹⁵: Group B
•   8⁴⁵: Group C
•   9¹⁵: Group D
•   9⁴⁵: Group E
• 10¹⁵: Group F
• 10⁴⁵: Group H
• 11¹⁵: Group X

   

• 13⁰⁰: Group K
• 13³⁰: Group L
• 14⁰⁰: Group M
• 14³⁰: Group N
• 15⁰⁰: Group O
• 15³⁰: Group Q
• 16⁰⁰: Group R
• 16³⁰: Group W

•   8¹⁵: Group A
•   8⁴⁵: Group G
•   9¹⁵: Group I
•   9⁴⁵: Group P
• 10¹⁵: Group S
• 10⁴⁵: Group T
• 11¹⁵: Group U
• 11⁴⁵: Group V
  

The talk should be about 15-20 minutes, including a demo (see below); after the talk, there will be some questions (5-10 minutes). Please, remember that you need to make sure that every group member must have given a part of the presentation.

The talk should cover the following things (not necessarily in that order):

1. There should be a presentation of the functionality of the tool from the users' point of view. This could be a bit from the sales perspective (benefits, selling points, ease of use, long-term perspectives); but do not overdo this. This part would be from the "WHY" and "WHAT" perspective.
2. There should be a part that is more technical ("HOW" perspective); this part should talk about the architecture and design of the tool (of course on a higher level of abstraction); if you want (and time allows), you could also mention some interesting implementation detail (but do not dwell on that), and do not explain "standard stuff" of Java programming.
3. There should be a demonstration of the tool. You should show that the main functionality (see 1.) is working and demonstrate the tool from its best angle. This would also mean that you have an example prepared for that purpose.

Note that all parts of that presentation except the tool demo would typically be done wit some powerpoint slides. The tool demo needs careful preparation (it needs to be "choreographed"), so that you present the capabilities of the tool in a concise and convincing way.

As audience, you should expect a manager who is more interested in what he, his company, and his customers will get or benefit from using your product than in its technical details. But, you should also expect an IT expert who will have a critical eye on the technical aspects, and whether the architecture and design make sense. The manager might not be able to follow that part — that is why he brings an IT expert, whom he will ask whether the technical part makes sense.

Please, also bring a runnig version of Eclipse with your projects in the workspace, so that we could have a look into the source code and the models of your Eclipse projects, if need should be.