Two important things are explained:

• Instances vs. Classes
• Methods vs. Operations

Full read: http://geertbellekens.wordpress.com/2011/05/27/uml-best-practice-one-operation-one-sequence-diagram/

Why to use state-machines at all?

UML supports state charts for really long time, but only a small part of UML community uses state-machines on a regular basis.
My experience confirms that – it isn’t easy to start using them. The question is – why?

In my opinion, the reason is – the way how the people do thinking – in functions and activities (actually straight forward ). Therefore most of us likes sequence and activity charts better.
Everybody begins programming by writing functions – first, you have an idea of desired result in your mind and next, to get that result – you program a… function. Other way around – nobody will start thinking about classes, instances, states, interaction between objects, etc. if you just want e.g. to parse some strings.

But one day you want to (or you have to ) develop code in a more structured way. At that point machines can help
- Why? Because they get the object oriented methodology to the heart of the matter – it’s all about objects and their states. But as already mentioned above, at the beginning, state-machines seem to be non-trivial
– So what to do?

How to get the state-machine right?

Wouldn’t be great if an UML tool could interact with you and give you feedback while modeling to show if you are still on the right track?
– It’s exactly what AMUSE does. It extends Enterprise Architect to an interactive UML tool.

My first lesson learned with AMUSE

1. First, install the tool – very easy
2. Cause I developed state machines before AMUSE, the next step was also easy going – created a model, a view, a package, added an state diagram and drew a trivial state chart
3. Next, I wanted of course to know if it’s executable – the first thing I had to learn was to add every state-machine into simulation window manually. Actually it’s annoying, hope we change that in the next version
4. But already at the fourth step I learned a really important thing – every state machine belongs to a class. First, I thought it is also nonsense, but then I’ve got it

Basically it is easy and exactly the right way to think:

- So, you want a state chart? First question you have to answer – state of what? And the answer is – state of class you have to design.

Answering that question is the first step in the right direction of good design!

Bottom line

To cut a long story short:

• State machines are cool, because they guide you to a good design
• AMUSE is cool, because it guides you to a good state machine
  - e.g. it creates automatically a class and a state machine that belongs to a state diagram if you forgot

meanwhile i came to the conclusion:
- Usage of state machines is probably most suitable way to enter into object oriented design, but they are also excellent helpers for experts.

Next time more …

If you can handle Japanese have a nice read!

Offizieller Start: LieberLieber AMUSE 1.5 für Sparx Systems Enterprise Architect – pressetext.austria

It’s always existing to see how a press release is being picked up.

Register now:
To register you interest for this webinar please email us with your name, company, telephone number and email address along with the title of the webinar you wish to register for. We’ll then send you login details for the webinar on the week prior to the event. Register your interest here.

Unavailable on the day?
As before for those of you unable to attend any of our webinars, don’t worry, all of our webinars are available for download from the Dunstan Thomas site.

.

Currently implemented new Features:

• smaller and faster Setup
• Single Step Simulation
• Sub and extended Diagrams will be opened on simulation
• Simulation stops if user switches Diagram
• improved external Reference feature (easier for .net implementations)
• Possibility to update Referenced (easier for .net implementations)
• Testcases can  be defined via contraints and are taken into account during simulation
• AMUSE Addin Window in Enterprise Architect 8.0 is now dockable
• Toolbar gives for better usability than the previous context menus

Play Video

It can also be downloaded.

We are still working on other new Features like the possibility to simulate Activity Diagrams – and a HTTP Bridge to connect Embedded Hardware….

Other than that we are working on a showcase for Windows CE and Lego Mindstorms….

Christian hat mir heute einen Link auf sehr cooles Youtube Video geschickt. – Mehr das zu findet ihr hier: X3D-UML – X3D-UML

So here is the standard answer:

1. MS .NET Framework 2.0
2. Enterprise Architect 7.5.840 (System Engineer, Ultimate)
3. A valid license (at least for a trial period)

GEBRAUCHSINFORMATION

Durch die MPG-Novelle werden zusätzliche Anforderungen an Ihr Projektmanagement und Ihre Hard- Softwareentwicklung gestellt. Ist Ihr Software Code bereits dokumentiert? Verwenden Sie ein Anforderungs- und Testmanagement?

Qualitätssicherung setzt umfassende Dokumentation voraus.

Was nicht gleich dokumentiert wird, wird nie dokumentiert. Projektabdeckende Traceability – von der Erstellung der Anforderungen über die Implementierung bis zu den Testfällen – ist die grundlegende Voraussetzung für besichertes und nachvollziehbares Validieren und Verifizieren. Gemeinsam im Team durchgeführte Projektschritte werden zugleich automatisch zur Dokumentation: Analyse, Design, Implementierung, Testen und Roll-out. Machen Sie alle Projektphasen auch im Nachhinein noch validier- und verifizierbar.

Alle diese Anforderungen lassen sich durch unser UML Werkzeug Enterprise Architect von SparxSystems abdecken. UML, die bildhafte Sprache für Techniker und Nicht-Techniker.

• UML 2.1 Notation
• Alle 13 UML-Diagramme Security
• Versioning, Locking
• Zusammenarbeit im Team
• Traceability
• Hohe Integrationsfähigkeit in ihre bestehende
• Toollandschaft durch Automation Interface
• Automatische und flexible Dokumentation – Export (HTML, RTF)
• Live Code Support für C++, Java, C#, VB, VB.Net, Delphi
• UML Profiles
• Benutzerdefinierte Patterns  · Automatisiertes Erzeugen von HTML und RTF Dokumentation· XMI 2.1 Export/Import inkl. Sonderformate
• Data Modelling und Database Engineering
• Projekt-Aufwandsschätzung mit Hilfe von Use Case Metrics
• Testing, issues, changes, glossary, resourcing
• Replikationsfunktionalität (.EAP Files)
• Grafikunterstützung über Stereotypes/Metafiles und importierte Bildformate
• CSV Export/Import
• Integration in Visual Studio und Eclipse
• WYSIWYG Report Writer

Über 220.000 Kunden arbeiten bereits mit Enterprise Architect. Unsere Referenzen im Medizinbereich sind: Siemens AG – Healthcare Sector, Cardinal Health Germany, Viasys Healthcare GmbH, SHL Solutions for Healthcare and LifeSciences, Philips Medizinsysteme GmbH, Disetronic Medical Systems AG, MeVis Medical Solutions AG, u.v.a
WIRKSTOFF: UML
GEGENANZEIGEN: keine bekannt
PACKUNGSGRÖSSE: Named User, Concurrent User
VERWENDUNGSART: Entwickler, Projektmanager, Analyst täglich verwenden
LAGERUNG: Sofortige Installation und Anwendung empfohlen
Enterprise Architect kann gleichzeitig mit anderen Tools verwendet werden. Gebrauchsinformationen und fachliche Beratung unter sales@sparxsystems.at einholen.

Dieses Addin bietet die Möglichkeit MSBuild Dateien in EA zu importieren und mit Hilfe der dazugehörigen MDG Technology, dessen Konfigurationen graphisch darzustellen. Als weiteres Feature wurde ein “Element type choose” Dialog eingebaut, mit dem man einfach aus einer Liste z.B.: MSBuild Task Types auswählen kann (Copy, Delete,…).  Auch werden alle “required attributes” automatisch angefügt und mit Hilfe des “Attribute” Features können weitere “optional attributes” ausgewählt werden.
Natürlich gibt es auch eine Export funktion, um wieder ein MSBuild File erstellen zu können.
(Alle MSBuild Types und Attribute werden aus der MSBuild Schemadatei ausgelesen)

Und nun zur MSBuild Demo bzw. zum Download …. MSBuild Integration

English:

As announced in a previous entry I developed a MSBuild Integration for EA.

This addin gives you the possibility of importing MSBuid files into EA and with the appendant MDG Technology EA can visualize the MSBuild configurations. As an additional feature I implemented an “Element type choose” dialog, so you can easily choose from a list of e.g. MSBuild Task Types (copy, delete,…). Also all “required attributes are automatically added and with the “Attribute” feature you even can choose “optional attributes”.
Of course there is an export function, to get your MSBuild file again.
(All MSBuild types and attributes are taken from the MSBuild schema file.)

And now for the MSBuild Demo and respectively the Download …. MSBuild Integration

Darum die Idee!! Wir machen ein UML Profil, sowie Import und Export Funktion für MSBuild in Enterprise Architect.
Derzeitiger stand: Testen des Profils!
Soblad es etwas zum online stellen gibt geben wir bescheid.

EnglishEverytime the same things,… change to productiv systems (customer system settings), raise version number, copy additional files you need for the Setup and then maybe a test and a productive version for the customer.
So you get the idea of using MSBuild, but as a developer we are all lazy buggers and try to copy/paste our way around or find an IDE where we can click and drag our solution.

Thats where I got the idea!! We just design an UML Profile, as well as an Import/Export funktion for MS Build in Enterprise Architect.
Current status: Testing the profile
As soon as we have something we can release I’ll come back to you.