Difference between revisions of "10 Thesen"
From OOEM
Jump to navigationJump to search
AndreasLeue (talk | contribs) |
AndreasLeue (talk | contribs) |
||
| (One intermediate revision by the same user not shown) | |||
| Line 1: | Line 1: | ||
{{T| | {{T| | ||
# Mythos: "Business vs. IT"-Kampf (sie haben keine Chance) | # Mythos: "Business vs. IT"-Kampf (sie haben keine Chance) | ||
# Mythos: Fachprozesse | # Mythos: Fachprozesse {{--}} BPM(N)/EPK {{--}} Wandschmuck | ||
# Mythos: IT | # Mythos: IT {{--}} UML {{--}} technisch {{--}} verkompliziert | ||
# Es gibt nur eine Wirklichkeit (und ein Single Source Modell ist sowieso besser) | # Es gibt nur eine Wirklichkeit (und ein Single Source Modell ist sowieso besser) | ||
# Zu einfach: Prozeß | # Zu einfach: Prozeß {{--}} Funktionshierarchie | ||
# Ablauf und Struktur gehören zusammen (Prozesse und Objekte) | # Ablauf und Struktur gehören zusammen (Prozesse und Objekte) | ||
# Abläufe nicht zementieren (Kontrollfluß so spät wie möglich codieren) | # Abläufe nicht zementieren (Kontrollfluß so spät wie möglich codieren) | ||
| Line 13: | Line 13: | ||
| | | | ||
# Myth: "Business vs. IT"-Infighting (they have no chance) | # Myth: "Business vs. IT"-Infighting (they have no chance) | ||
# Myth: Business Process | # Myth: Business Process {{--}} BPM(N)/EPC {{--}} Schrankware | ||
# Myth: IT | # Myth: IT {{--}} UML {{--}} technical {{--}} overly intricate | ||
# There's only one reality (and a Single Source Model is better, anyway) | # There's only one reality (and a Single Source Model is better, anyway) | ||
# Too simple: Process | # Too simple: Process {{--}} Funktion Hierarchy | ||
# Flow and Strcuture belong together (Processes and Objects) | # Flow and Strcuture belong together (Processes and Objects) | ||
# Do not hardcode flows (fix controllow as late as possible) | # Do not hardcode flows (fix controllow as late as possible) | ||
Latest revision as of 17:38, 14 July 2010
- Myth: "Business vs. IT"-Infighting (they have no chance)
- Myth: Business Process = BPM(N)/EPC = Schrankware
- Myth: IT = UML = technical = overly intricate
- There's only one reality (and a Single Source Model is better, anyway)
- Too simple: Process = Funktion Hierarchy
- Flow and Strcuture belong together (Processes and Objects)
- Do not hardcode flows (fix controllow as late as possible)
- Object Orientation? Object Orientation!
- It can't get any easier
- Look in the crytal ball: UML (but which version?)
Mit diesen Thesen befaßte sich der Vortrag am 8.12.2009. The speech at 8.12.2009 addressed these theses.
