Aus über 500 Bewerbungen wurde AMUSE 2.1 in der Kategorie „IT- & Softwarelösungen für die Industrie“ unter die drei Nominierten gewählt. Der Industriepreis wird seit 2006 jährlich vom Huber Verlag für Neue Medien in 14 Kategorien auf der Hannover Messe verliehen . Eine 30-köpfige Experten-Jury aus Professoren und Fachjournalisten wählte aus den heuer besonders zahlreich eingegangenen Bewerbungen die Nominierten und Sieger. Die offizielle Preisverleihung fand am Montag, den 23. April auf der Hannover Messe in Halle 2 auf dem Stand des Verein Deutscher Ingenieure (VDI) statt. Wir gratulieren den Siegern und freuen uns mit ihnen über unsere Nominierung…
LieberLieber Software CEO Daniel Siegl explains in this webinar how to suceed in your UML software project by using the latest releases of Enterprise Architect (Sparx System) and AMUSE (LieberLieber Software). Enjoy the show..
A little story to explain our company name “LieberLieber”
LieberLieber was found by our owner Mr. Peter Lieber.
To write Peter Lieber a letter (old form of a mail, but you can also write mails) in English in a personal, but not to formally way, you can start with “Dear Mr. Lieber” similar to that in German would be: “Lieber Herr Lieber” and some funny guys wrote sometimes: “Lieber Lieber”.
So what’s the story behind the company’s name? Is it: “Lieber and son”? No Is it: “two Brothers”? No – indeed it is because of another meaning of the word “Lieber” – it means also “prefer” or “better”. So it could mean “prefer to go to Mr. Lieber”.
But the true story is: There was a friend of Peter called “Johannes Leopold Zeitlberger” and in old Austria “Leopold” was “Leupold” and he wanted to have a company “Leupold&Leupold” – and so I thought that this sounds like a good idea to get an unique domain name: www.lieberlieber.com was born.
Developing State Machines and drawing GUI sketches is not a new feature, but opening both and working on both at the same time it’s definitely something new in the EA 9.3 
Execution of State Machine is nothing new for AMUSE, but generating GUIs from UI sketch drawn in the EA and control them using a state machine is definitely something new in the AMUSE 2.5 coming soon:
Important for everybody who needs to extend EA by new functionality.
The picture shall provide roughly overview of Enterprise Architect layer architecture. Most important message: The EA itself is built of building blocks and it can be flexibly extended more or less in the same way (like AMUSE it does). The only difference between self made MDG Technologies / Add-Ins and EA original functionality – there are some APIs reserved for EA internal usage.
MDG technologies shall be used for extension of already available technologies like UML or SysML by providing new tool boxes, stereotypes, tagged values etc.
Add-Ins shall be used for providing completely new functionality like new UIs, diagram types, reports, supporting of user workflows etc.
Some of us always had a feeling – model based development saves time and money, others of us had reasonable doubts, most of us had endless discussions about it. Good news for all Enterprise Architect and AMUSE users – finally we got proved numbers! The following dissertation shows why it’s true why the benefits definitely overweighs the costs and why MBSE (Model Based System Engineering) is the approach of the future development.
The only question keeps open – how to use Enterprise Architect and AMUSE to get maximum benefit of these tools, e.g.
- can I build functional architecture from customer requirements using Enterprise Architect??
- or can I combine EA and Matlab/Simulink in a reasonable way??
The answer is – yes you can! But it’s a stuff for one of the next articles 
Summary of the dissertation “Model Based Development of Embedded Software Systems in the Automotive – Costs and Benefits” Author: Sascha Kirstan; Academic Advisor: Prof. Dr. Dr. h.c. Manfred Broy; Technical University Munich (Software & Systems Engineering).
Hardcover Edition: http://www.amazon.de/gp/product/384390121X/
The dissertation defined and verified following 26 hypotheses – enjoy!
|
Hypothesis 1 |
Usage of MBSE saves at least 30% of time during development lifecycle |
Fully confirmed |
|
Hypothesis 2 |
Usage of MBSE leads to productivity improvement |
Fully confirmed
|
The screenshot shows a scenario, when the Validation rule detects a validation rule violation.
The diagram specifies that the state “Ready” shall be the sub-state of the composite state “Working”, but the project browser shows the real facts. Both states are on the same level in the model. Validation dialog informs the user about the issue and ask if auto-correction rule shall be executed to repair the problem.
AMUSE 2.0 provides over 20 validation rules. They ensure UML-correctness of customer models, their internal consistence as well as the consistence between model and diagrams. As far as possible we provide also corresponding auto-correction rules that help the user to repair the model.