1. Project Meeting

2. Today’s process Roles: Desired Outcome: Facilitator(s): All
Scribe: Michel Atoudem Kana
Time Keeper: Uli Bauer
Minute Taker: Stefan Gersmann
Desired Outcome:
Open Issues
Work Breakdown Structure
Everybody knows what to work on
5/4/2019
ARENA Project Meeting

3. Project meeting outline
ODD status
Team status
Evaluation of project feedback
Schedule till Christmas
Hello SWORD application
Coding session
ARENA Christmas meeting
Another interesting issue with finding objects is to define which objects are inside the application domain and which ones are outside of it. Sometimes it helps you to get a clearer understanding of the overall system. Look at the figure in this slide. What does it show? A bunch of black and white dots? Given that I will tell you that it contains a system (that is an object model can be found) how would you start with looking for objects? Turn the slide around. Turn it upside down. Look at the “problem domain” from all angles. And suddenly you might experience what I would call the “gestalt experience”. You will see the application domain. Now there is no recipe for finding it. You might find a very low level object, such as an ear or you might find a high level object such as the shape of a dog. In fact, if you look carefully you will find a dalmatian dog. Once you understand that you are looking at a dog, a lot of the black and white pixels in the total figure are not part of your system and you can easily find the boundary of the system by trying to trace the outline of the Dalmatian.
However, don’t be lured into thinking that this is the system you have been looking for. Always be alert that the real system might be something totally different. For example, if you turn the dog upside down, you might be able to see an eagle taking off from a river, with a poor dead victim in its claws!
5/4/2019
ARENA Project Meeting

4. Project meeting outline
ODD status
Team status
Evaluation of project feedback
Schedule till Christmas
Hello SWORD application
Coding session
ARENA Christmas meeting
Another interesting issue with finding objects is to define which objects are inside the application domain and which ones are outside of it. Sometimes it helps you to get a clearer understanding of the overall system. Look at the figure in this slide. What does it show? A bunch of black and white dots? Given that I will tell you that it contains a system (that is an object model can be found) how would you start with looking for objects? Turn the slide around. Turn it upside down. Look at the “problem domain” from all angles. And suddenly you might experience what I would call the “gestalt experience”. You will see the application domain. Now there is no recipe for finding it. You might find a very low level object, such as an ear or you might find a high level object such as the shape of a dog. In fact, if you look carefully you will find a dalmatian dog. Once you understand that you are looking at a dog, a lot of the black and white pixels in the total figure are not part of your system and you can easily find the boundary of the system by trying to trace the outline of the Dalmatian.
However, don’t be lured into thinking that this is the system you have been looking for. Always be alert that the real system might be something totally different. For example, if you turn the dog upside down, you might be able to see an eagle taking off from a river, with a poor dead victim in its claws!
5/4/2019
ARENA Project Meeting

5. ODD Status How far are we? 3-6 class files per team html documentation
pdf documentation
problem: pre and postconditions not yet included
3-6 class files per team
5/4/2019
ARENA Project Meeting

6. ODD Status Compilation problems
Please try to compile before checking in.
Do you know ant?
Ant install and introduction session?
Is it important for Michael that sword compiles?
5/4/2019
ARENA Project Meeting

7. ODD Status
5/4/2019
ARENA Project Meeting

8. Project meeting outline
ODD status
Team status
Evaluation of project feedback
Schedule till Christmas
Hello SWORD application
Coding session
ARENA Christmas meeting
Another interesting issue with finding objects is to define which objects are inside the application domain and which ones are outside of it. Sometimes it helps you to get a clearer understanding of the overall system. Look at the figure in this slide. What does it show? A bunch of black and white dots? Given that I will tell you that it contains a system (that is an object model can be found) how would you start with looking for objects? Turn the slide around. Turn it upside down. Look at the “problem domain” from all angles. And suddenly you might experience what I would call the “gestalt experience”. You will see the application domain. Now there is no recipe for finding it. You might find a very low level object, such as an ear or you might find a high level object such as the shape of a dog. In fact, if you look carefully you will find a dalmatian dog. Once you understand that you are looking at a dog, a lot of the black and white pixels in the total figure are not part of your system and you can easily find the boundary of the system by trying to trace the outline of the Dalmatian.
However, don’t be lured into thinking that this is the system you have been looking for. Always be alert that the real system might be something totally different. For example, if you turn the dog upside down, you might be able to see an eagle taking off from a river, with a poor dead victim in its claws!
5/4/2019
ARENA Project Meeting

9. Team status Algorithm Team SWORD Engine Team HCI Team FRAG Team
5/4/2019
ARENA Project Meeting

10. Project meeting outline
ODD status
Team status
Evaluation of project feedback
Schedule till Christmas
Hello SWORD application
Coding session
ARENA Christmas meeting
Another interesting issue with finding objects is to define which objects are inside the application domain and which ones are outside of it. Sometimes it helps you to get a clearer understanding of the overall system. Look at the figure in this slide. What does it show? A bunch of black and white dots? Given that I will tell you that it contains a system (that is an object model can be found) how would you start with looking for objects? Turn the slide around. Turn it upside down. Look at the “problem domain” from all angles. And suddenly you might experience what I would call the “gestalt experience”. You will see the application domain. Now there is no recipe for finding it. You might find a very low level object, such as an ear or you might find a high level object such as the shape of a dog. In fact, if you look carefully you will find a dalmatian dog. Once you understand that you are looking at a dog, a lot of the black and white pixels in the total figure are not part of your system and you can easily find the boundary of the system by trying to trace the outline of the Dalmatian.
However, don’t be lured into thinking that this is the system you have been looking for. Always be alert that the real system might be something totally different. For example, if you turn the dog upside down, you might be able to see an eagle taking off from a river, with a poor dead victim in its claws!
5/4/2019
ARENA Project Meeting

11. sucks communication and decision documentation (7)
inter-, but also intra-team
deadlines too short/unrealistic goals (6)
uneven efforts of members (5)
information about what to do and how (know the Bible) (4)
time requirements too high (4)
too much overhead (3)
tutorials were online too late and didn’t help (2)
too many tools to learn, use limited, usability (2)
unclear responsibilities (everybody should do everything) (2)
5/4/2019
ARENA Project Meeting

12. sucks, too uneven work distribution/motivation (also Coach/Team) (1)
wednesday meetings (attention) (1)
infrastructure (1)
adherence to standards (1)
visionary ideas are blocked (1)
Coaches are not moderating well (1)
5/4/2019
ARENA Project Meeting

13. rules topic (8) management (8) organization (team work) (7)
process (6)
members (5)
iBooks (4)
infrastructure (4)
technologies (4)
English (2)
tutorials (1)
social events (1)
5/4/2019
ARENA Project Meeting

14. Project meeting outline
ODD status
Team status
Evaluation of project feedback
Schedule till Christmas
Hello SWORD application
Coding session
ARENA Christmas meeting
Another interesting issue with finding objects is to define which objects are inside the application domain and which ones are outside of it. Sometimes it helps you to get a clearer understanding of the overall system. Look at the figure in this slide. What does it show? A bunch of black and white dots? Given that I will tell you that it contains a system (that is an object model can be found) how would you start with looking for objects? Turn the slide around. Turn it upside down. Look at the “problem domain” from all angles. And suddenly you might experience what I would call the “gestalt experience”. You will see the application domain. Now there is no recipe for finding it. You might find a very low level object, such as an ear or you might find a high level object such as the shape of a dog. In fact, if you look carefully you will find a dalmatian dog. Once you understand that you are looking at a dog, a lot of the black and white pixels in the total figure are not part of your system and you can easily find the boundary of the system by trying to trace the outline of the Dalmatian.
However, don’t be lured into thinking that this is the system you have been looking for. Always be alert that the real system might be something totally different. For example, if you turn the dog upside down, you might be able to see an eagle taking off from a river, with a poor dead victim in its claws!
5/4/2019
ARENA Project Meeting

15. Schedule till Christmas
Mon
Tue
Wed
Thu
Fri 9 10
today 12 13 16 17 18 19 20 23 24 25 26 27
Interface
session
coding
Coding
session
Christmas
demo
Coding
5/4/2019
ARENA Project Meeting

16. Schedule details Today By next Wednesday (Dec 18th)
Interfaces & interdependencies between different subsystems are discussed
Work distribution is discussed
By next Wednesday (Dec 18th)
Further coding of the development teams
Next Wednesday (Dec 18th, 14:00)
Coding session
Open end - including “Gluehwein” provided by the coaches ;-)
5/4/2019
ARENA Project Meeting

17. Schedule details Next Thursday (Dec 19th, 12:00)
Christmas demonstration
One simple run through SWORD, e.g.:
Two players start SWORD…
… can move their actors …
… through an algorithmically defined world …
… where they can see other items!
5/4/2019
ARENA Project Meeting

18. Project meeting outline
ODD status
Team status
Evaluation of project feedback
Schedule till Christmas
Hello SWORD application
Coding session
ARENA Christmas meeting
Another interesting issue with finding objects is to define which objects are inside the application domain and which ones are outside of it. Sometimes it helps you to get a clearer understanding of the overall system. Look at the figure in this slide. What does it show? A bunch of black and white dots? Given that I will tell you that it contains a system (that is an object model can be found) how would you start with looking for objects? Turn the slide around. Turn it upside down. Look at the “problem domain” from all angles. And suddenly you might experience what I would call the “gestalt experience”. You will see the application domain. Now there is no recipe for finding it. You might find a very low level object, such as an ear or you might find a high level object such as the shape of a dog. In fact, if you look carefully you will find a dalmatian dog. Once you understand that you are looking at a dog, a lot of the black and white pixels in the total figure are not part of your system and you can easily find the boundary of the system by trying to trace the outline of the Dalmatian.
However, don’t be lured into thinking that this is the system you have been looking for. Always be alert that the real system might be something totally different. For example, if you turn the dog upside down, you might be able to see an eagle taking off from a river, with a poor dead victim in its claws!
5/4/2019
ARENA Project Meeting

19. Hello SWORD Interfaces between different subsystems
Interdependencies between different teams
Work distribution
Open questions regarding FRAG
5/4/2019
ARENA Project Meeting

20. Project meeting outline
ODD status
Team status
Evaluation of project feedback
Schedule till Christmas
Hello SWORD application
Coding session
ARENA Christmas meeting
Another interesting issue with finding objects is to define which objects are inside the application domain and which ones are outside of it. Sometimes it helps you to get a clearer understanding of the overall system. Look at the figure in this slide. What does it show? A bunch of black and white dots? Given that I will tell you that it contains a system (that is an object model can be found) how would you start with looking for objects? Turn the slide around. Turn it upside down. Look at the “problem domain” from all angles. And suddenly you might experience what I would call the “gestalt experience”. You will see the application domain. Now there is no recipe for finding it. You might find a very low level object, such as an ear or you might find a high level object such as the shape of a dog. In fact, if you look carefully you will find a dalmatian dog. Once you understand that you are looking at a dog, a lot of the black and white pixels in the total figure are not part of your system and you can easily find the boundary of the system by trying to trace the outline of the Dalmatian.
However, don’t be lured into thinking that this is the system you have been looking for. Always be alert that the real system might be something totally different. For example, if you turn the dog upside down, you might be able to see an eagle taking off from a river, with a poor dead victim in its claws!
5/4/2019
ARENA Project Meeting

21. Coding session Process: Preparation: pair programming (XP)
all developers in one room
pairs are formed based on open tasks
continuous integration
Preparation:
open questions & issues
5/4/2019
ARENA Project Meeting

22. Project meeting outline
ODD status
Team status
Evaluation of project feedback
Schedule till Christmas
Hello SWORD application
Coding session
ARENA Christmas meeting
Another interesting issue with finding objects is to define which objects are inside the application domain and which ones are outside of it. Sometimes it helps you to get a clearer understanding of the overall system. Look at the figure in this slide. What does it show? A bunch of black and white dots? Given that I will tell you that it contains a system (that is an object model can be found) how would you start with looking for objects? Turn the slide around. Turn it upside down. Look at the “problem domain” from all angles. And suddenly you might experience what I would call the “gestalt experience”. You will see the application domain. Now there is no recipe for finding it. You might find a very low level object, such as an ear or you might find a high level object such as the shape of a dog. In fact, if you look carefully you will find a dalmatian dog. Once you understand that you are looking at a dog, a lot of the black and white pixels in the total figure are not part of your system and you can easily find the boundary of the system by trying to trace the outline of the Dalmatian.
However, don’t be lured into thinking that this is the system you have been looking for. Always be alert that the real system might be something totally different. For example, if you turn the dog upside down, you might be able to see an eagle taking off from a river, with a poor dead victim in its claws!
5/4/2019
ARENA Project Meeting

23. ARENA Christmas meeting
… will take place after or during our next project meeting
… everyone can bring some gingerbread and cookies
… Gluehwein will be provided by the coaches ;-)
5/4/2019
ARENA Project Meeting

24. Thanks for your attention & Happy coding ;-)
5/4/2019
ARENA Project Meeting