Im Rahmen der Software Quality Days wird Horst Kargl am 18. Jänner (14.45 Uhr) unter dem Titel “Arbeiten Sie nicht planlos” über die Wichtigkeit der Planung in Software Entwicklungsprojekten sprechen.
Der Kongress bietet mit Keynotes, Fachvorträgen, Ausstellungsbereich, Tutorials und Workshops umfassende Möglichkeiten der Weiterbildung und des Networkings im Bereich Software.
Wenn Sie keine Zeit zum Besuch des Vortrags haben, finden Sie demnächst eine Zusammenfassung in diesem Blog bzw. auf unserer Homepage.
The idea for this was born out of a bet between Daniel Siegl from LieberLieber and the guys from the Merapi-Team from the Ostfalia University. The goal was, to create a somehow funny video, that explains the UML Statechart diagramm in under 10 minutes. Have fun!
UML Lifecycle
For the Credits idea: Alexander Horn, Kevin Barwich implementation: Kevin Barwich Music: Louis Armstrong, Pink Panther, Kevin Barwich
All the time the same issue: what window shall I use for typing code in the Enterprise Architect: the input window at the top named “Behavior” or the input window at the bottom named “Initial Code”??
To complete the confusion: the property tab also has been named “Behavior”
The property dialog has been changed between EA 8.0 and EA 9.0, the issue has remain. Summary If you want that EA considers your code during code generation please note:
for class operations use “Initial Code:” input window for manual coding
for class operations use “Behavior” window for linking it to a behavior only
for state operations use “Behavior” window only for everything
If you want to understand the reason behind that, see below for explanation:
By the way, the AMUSE 2.0 (coming soon) provides a number of really helpful validation rules, e.g. in that case AMUSE warns the user about the code will be ignored by the code generation
For the Electronics Fair Exhibition in the Hong Kong I prepared a presentation that explains how the toolkit we developed helps to manage the growing complexity in the embedded world. The solution is based on Sparx Systems Enterprise Architect, AMUSE and Willert Tools. Willert Software GmbH is one of the pioneers in that domain and provide Model Driven Development (MDD) solutions for embedded development for 10 Years (!). Last year LieberLieber and Willert companies decided to provide an affordable solution based on Enterprise Architect that I successfully present at the Electronics Fair Exhibition in the Hong Kong Exhibition and Convention Center. My colleagues from Sparx Systems Australia liked it, so I hope you’ll enjoy it also:
At that place I’d like to say a big thank you to Walter van der Heiden who allowed me to reuse some slides from his impressive presentation I enjoyed some times on the development conferences .
Please find here a video that demonstrates our solution for the Keil environment and ARM RTOS
Development of Real-Time Systems with Enterprise Architect and AMUSE.
Couple weeks ago we presented our solution for embedded development at the embedded world Conference 2011 for the first time . Today I’m at the Electronics Fair Exhibition in the Hong Kong Exhibition and Convention Center and present the solution in Asia market. The most of the local development companies need more time to realize the demand for Model Driven Design and Development (MDD) than the European companies, but there is mind change on the way, in particular in the embedded world. The embedded market is one of most competitive and the companies are under pressure to decrease time-to-market. The MDD one of the essential instruments for arriving that target and that what we present to our potential customers here.
How ever me and my colleagues from Sparx Systems Australia we created a new video that demonstrates the usage of the embedded tool kit including Enterpise Architect, AMUSE, Willert Tools and Keil IDE. I like it and would like to share it with you, please enjoy!
And here the same staff as flash video with higher quality:
If you are looking for inter state-machines communication using AMUSE, following example should help.
It’s a kind of “Hello World” for multiple machines, simplest possible example
Two state machines fires triggers to each other: Ping fires ping trigger and receives pong trigger and pong works another way around.
1. Download XMI 2. Create an empty Enterprise Architect project
3. Import XMI
4. Open ping and pong state machine diagrams
5. Add both to AMUSE simulation window
6. Start pong first then ping
7. if initial ping wasn’t caught, fire first trigger manually via trigger menu
8. watch the ping/pong counters
EA/AMUSE vs. Rhapsody Architect/Designer for Systems Engineers
Features
EA+AMUSE
Rhapsody
Designs and behavior using SysML or UML
UML 2.3 / SysML 1.1
UML 2.x / SysML 1.1
Simulate behavior to validate functionality
AM|USE supports simulation of state machines and activity diagrams as long as activity is set as behavior of a state or as affect of transition. The standalone activity diagrams will be supported in the next version coming middle of this year
yes
Capture requirements
EA provides full-blown solution for requirement engineering
yes but restricted by inflexible model storage and model structure
Capture structured scenarios
EA provides functionality for capturing scenarios as plain text but also in structured form with the option of automatic diagram generation (activity-, sequence- or state-diagrams )
no
Requirements analysis and traceability to design, implementation and test artifacts
Standard EA functionality
yes
Flexible Model Storage
Model can be stored as
- local single project file
- network shared single project file
- multiple XML files
- single or distributed DBMS supported: MSSQL Server, MySQL, Oracle, PostgreSQL, Progress OpenEdge, MSDE, Adaptive Server Anywhere
multiple storage files
Project development and task management incl. resources management