|
The final project presentations in the course Software Engineering 2 in autumn 2020
will be held on Friday, December 4 in lecture hall 303A/45, and on Monday, December 14
in room 322.205 (according to the choices of the groups). All group members must be
present at the final presentation of their group.
You will find the schedule for these presentations below.
Please contact Ekkart Kindler right away, if this
schedule does not work for you.
Friday, December 4 in lecture hall 303A/45:
- 1300: Group D
- 1345: Group B
- 1430: Group E
In lecture hall 303A/45, your have two independent projectors
available, as well as a blackboard.
Monday, December 14 in room 322.205:
- 1000: Group C
- 1045: Group A
In room 322.205, your have one projector (actually a large screen) available with two white boards
on the side.
Below, you will find some information on this presentation and what is expected from it.
The group's presentation should be 25-30 minutes long, including the demo of the tool (see below);
after the group's presentation, there will be time for some questions (10-15 minutes).
Please, remember that you need to make sure that every group member must have been an
active part of at least one of the three presentations.
The talk should cover the following things (not necessarily in that order):
- There should be a presentation of the functionality of the tool from the
different end-users' point of views. This could cover the sales perspective (benefits,
selling points, ease of use, long-term perspectives, but do
not overdo this) and must cover the end-users perspective. This part would be from the "WHY" and "WHAT" perspective.
- 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 details
(but do not dwell on that), and you do not need to explain "standard programming stuff".
- There should be a demonstration of the software.
You should show that the functionality (see 1.) is working and
demonstrate the tool and its features from its best angle. This would also mean that
you have an example configuration and different users for that purpose.
- If the presented software is still lacking some features, which you are planning
to implement in the final version, these should be named in the talk
(e.g. with a slide summarizing these planning changes and issues).
Note that all parts of that presentation except the demo would typically be done with
some powerpoint slides. The demo needs careful preparation (it needs to be "choreographed"),
so that you present the capabilities of the tool in a concise and convicing way.
As audience, you should expect a manager (e.g. CEO) who is more interested in what he, his company, and
his customers will get and how they will benefit from using your product than in its technical details.
But, you should also expect an IT expert (e.g. CTO) who will have a critical eye on the technical
aspects, and whether the architecture and design (and the way they are presented) make sense.
The manager might not be able to follow the details of this part — that is why he brings an IT expert,
whom he will ask whether the technical part makes sense.
The questions will be asked from the non-technical (manager and end-user) as well as from
the technical (IT experts) point of view.
|
