Diese aufeinander aufbauende Seminarreihe richtet sich an Engineering Manager, Teamleiter sowie System- und Prozessingenieure, die mehr über die modellbasierte Entwicklung erfahren wollen. Der erste Termin ist kostenlos, die anderen zwei Seminare sind kostenpflichtig. Die Veranstaltungen finden bei der ADV statt: Trattnerhof 2, 1010 Wien.

Die Termine sind:

Teil 1: 24. Juni 2013, 17:30 – 20:00 Uhr

Nähere Informationen und Anmeldung:   http://www.adv.at/veranstaltungen/20130624_ModellbasierteEntwicklung.htm

Teil 2: 9. September 2013, 09:00 – 17:00 Uhr

Nähere Informationen und Anmeldung: http://www.adv.at/veranstaltungen/20130909_ModellbasierteEntwicklung.htm

Teil 3: 18. Oktober 2013, 09:00 – 13:00 Uhr

Nähere Informationen und Anmeldung: http://www.adv.at/veranstaltungen/20131018_ModellbasierteEntwicklung.htm

If you intend implement Scrum in your team, you can not keep your existing organization, you need to change a lot, you need to change your mind. If you will try to combine existing structures with Scrum the achieved improvements will be far below your expectations if any at all.

Kanban is totally different, the challenge here is to understand how your process currently looks like, in what steps your process can be split, which internal artifacts, deliveries do you have. It’s about elimination of waste of resources. Small example: it’s a small consulting and training company, there are three steps in the productivity chain: customer acquisition, performance of training and writing of invoices. If the company will acquire more customers than trainer are able to perform – it’s waste of resources and ruin of company’s name, if trainers performs more trainings than the invoices will be written – the same. Basically Kanban is much more difficult than it sounds.

With other words Scrum is like a recipe for cooking apple-pie with all ingredients, steps to do etc. and Kanban presumes you already know how bake apple-pies, it defines how to bake them just-in-time without waste of time and resources. Not really comparable – isn’t it?

There are nice things about Scrum and there things which are not that nice. Let us discuss one unnice thing – issue of scalability. It is not that trivial and there is no common opinion regarding the issue. The majority believes the possibility of Scrum in big-scaled projects it could be the а question of maturity of the organization, but I don’t believe.

It happens when management tries to implement Scrum for large projects and multiple teams. That phenomenon has different names, e.g. Scrum-of-Scrum. Typically experts discuss how technically Scrum-of-Scrum can be realized and the sociological aspects are ignored. But what if the core reason of scrum success is the sociological one?

I have experience with Scrum under different conditions and with different results. On the one hand an example where Scrum leaded to a great success – there was a team responsible for a sub-system of a large-scaled system. The sub-system caused only problems for very long time until the team implemented Scrum as its development process. In couple of months the team made the delay good of last two years and finished their part of the project in-time. BUT the sub-system was a loosely-coupled from the rest of the system and the team managed Scrum independently from the rest of the project and other teams. On the other hand there are several examples I experienced when managers rolled out and forced Scrum-of-Scrum for multiple teams. They tried it for years but it won’t be a success despite all the consultants and trainings. In fact it wasn’t better then the old good V-process we had before, I believe it got worser.

But why? Why didn’t we have any success? Did we something wrong? Or probably it’s really a characteristic of Scrum?

I tried to understand it for years – and once I’ve noticed some parallels between the successful Scrum teams and those successful communes at the end of the 19th century which leaded to the belief the communism will be the most successful social order ever.

I grew up in the country where people tried to make it real – the communism – was supposed to bring the heaven on the earth. I also spent a lot of time trying to understand the reasons why it could never be a success.
Let us check:
We have a prove – the communes can work, people work together, help each other, spend their whole energy for the common goals and have fun. It does not work always and you can not implement it by force, but it definitely can work. And we have very similar situation regarding the Scrum teams, sometimes it works fabulous, sometimes it does not work. But in both cases: neither the communes-of-communes (communism) nor the Scrum-of-Scrum (common Scrum for multiples teams) works well. At least I do not know even one real success story.

Today I came to believe the phenomena of commune and Scrum cannot scale just because of restrictions of the human nature. To be successful the participants of a commune or a Scrum team need to share a common goals between team players – the people you well know and trust and empathize. The problem is – humans are not able empathizing with hundreds of people, such feeling is restricted to couple of persons you really well know, people cannot share one goal across different teams, every team has it’s own goals, even if common meta-goal is known, members of other teams feel like competitors regarding the resources achievement of milestones, etc. – all in one – the human feelings does not scale – that’s the reason.

Summary
In my experience, a successful Scrum team – it is always a commune of comrades who share the goals and tasks, help each other and have fun of work. In that case the product owner is a person responsible for goal definition and the scrum master is responsible for the team spirit and for the conflict resolution. It’s a cool experience. What is not cool at all – if somebody tries to implement such approach by force and to apply it to big organizations, because the communism is a nice in dreams but horrible in reality.

However some of the Scrum attributes – like iterative development, backlogs, user stories may be used for large-scaled projects, why not, but not Scrum itself.

So as a tool maker – I thought there must be a possibility…

And I developed a VSTO Extension to PowerPoint. If you want to get it – contact us sales@lieberlieber.com

Here a screenshot:

I just wanted to show a result of a database query from an account-oriented datasource from the administration of Connecting Software – so i implemented a Search Script.

The result is as expected:

and here is the source code:

   1:  option explicit

   2:   

   3:  !INC Local Scripts.EAConstants-VBScript

   4:   

   5:  '

   6:  ' Script Name: SearchAccounts

   7:  ' Author: Peter Lieber

   8:  ' Purpose: Demonstration of database access to Connecting Software Administration

   9:  ' Date: 24-04-2013

  10:  '

  11:   

  12:  dim SEARCH_SPECIFICATION 

  13:  SEARCH_SPECIFICATION = "<ReportViewData>" &_

  14:                              "<Fields>" &_

  15:                                  "<Field name=""CLASSGUID""/>" &_

  16:                                  "<Field name=""CLASSTYPE"" />" &_

  17:                                  "<Field name=""ID"" />" &_

  18:                                  "<Field name=""AccountName"" />" &_

  19:                              "</Fields>" &_

  20:                              "<Rows/>" &_

  21:                          "</ReportViewData>"

  22:   

  23:  '

  24:  ' Search Script main function

  25:  ' 

  26:  sub OnSearchAccounts()

  27:   

  28:      ' Create a DOM object to represent the search tree

  29:      dim xmlDOM

  30:      set xmlDOM = CreateObject( "MSXML2.DOMDocument.4.0" )

  31:      xmlDOM.validateOnParse = false

  32:      xmlDOM.async = false

  33:      

  34:      

  35:      ' Load the search template

  36:      if xmlDOM.loadXML( SEARCH_SPECIFICATION ) = true then

  37:      

  38:          dim rowsNode

  39:          set rowsNode = xmlDOM.selectSingleNode( "//ReportViewData//Rows" )

  40:          

  41:          dim myConn

  42:          Set MyConn = CreateObject("ADODB.Connection") 

  43:          dim MdbFilePath

  44:          MdbFilePath = "c:\\temp\\test.mdb"

  45:          MyConn.Open "DRIVER={Media Gateway ODBC Driver};” &_

                  UID=administrator;ACC=ACCOUNT_ADMINISTRATION;” &_

                  IMPL=CORBA;PORT=8087;HOST=localhost;PWD=whatasecret;" 

  46:    

  47:      dim SQL_query

  48:      SQL_query = "select * from Accounts" 

  49:     

  50:      dim RS

  51:      Set RS = MyConn.Execute(SQL_query) 

  52:      WHILE NOT RS.EOF 

  53:      

  54:      AddRow xmlDOM, rowsNode, "", RS("ID"), _

  55:              RS("AccountName")

  56:      RS.MoveNext 

  57:      WEND 

  58:   

  59:          ' Fill the Model Search window with the results

  60:          Repository.RunModelSearch "", "", "", xmlDOM.xml

  61:          

  62:      else

  63:          Session.Prompt "Failed to load search xml", promptOK

  64:      end if

  65:  end sub    

  66:   

  67:  '

  71:  ' Adds an entry to the xml row node 'rowsNode'

  72:  '

  73:  sub AddRow( xmlDOM, rowsNode, elementGUID, elementName, comments )

  74:   

  75:      ' Create a Row node

  76:      dim row

  77:      set row = xmlDOM.createElement( "Row" )

  78:      

  79:      ' Add the Model Search row data to the DOM

  80:      AddField xmlDOM, row, "CLASSGUID", elementGUID

  81:      AddField xmlDOM, row, "CLASSTYPE", "Class"

  82:      AddField xmlDOM, row, "Name", elementName

  83:      AddField xmlDOM, row, "Comments", comments

  84:      

  85:      ' Append the newly created row node to the rows node

  86:      rowsNode.appendChild( row )

  87:   

  88:  end sub

  89:   

  90:  '

  91:  ' Adds an Element to the DOM called Field which makes up the Row data for the Model Search window.

  92:  ' <Field name "" value ""/>

  93:  '

  94:  sub AddField( xmlDOM, row, name, value )

  95:   

  96:      dim fieldNode

  97:      set fieldNode = xmlDOM.createElement( "Field" )

  98:      

  99:      ' Create first attribute for the name

 100:      dim nameAttribute

 101:      set nameAttribute = xmlDOM.createAttribute( "name" )

 102:      nameAttribute.value = name

 103:      fieldNode.attributes.setNamedItem( nameAttribute )

 104:      

 105:      ' Create second attribute for the value

 106:      dim valueAttribute 

 107:      set valueAttribute = xmlDOM.createAttribute( "value" )

 108:      valueAttribute.value = value

 109:      fieldNode.attributes.setNamedItem( valueAttribute )

 110:      

 111:      ' Append the fieldNode

 112:      row.appendChild( fieldNode )

 113:   

 114:  end sub

 115:   

 116:  OnSearchAccounts()

Lesen Sie den Bericht vom LieberLieber Device Day unter: http://futurezone.at/future/15235-einblicke-in-die-multitouch-zukunft.php

[SNIP]

const string ns = 

   "http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd";

XmlElement xmlUserToken = 

   XDoc.CreateElement("sec", "UsernameToken", ns);

XmlElement username = 

   XDoc.CreateElement("sec", "Username", ns);
username.InnerText = 

   soapUser;
xmlUserToken.AppendChild(username);

XmlElement password = 

   XDoc.CreateElement("sec", "Password", ns);
password.InnerText = 

   soapPwd;
xmlUserToken.AppendChild(password);

request.Headers.RemoveAt(0);
request.Headers.Insert(0, MessageHeader.CreateHeader("Security", ns, xmlUserToken));

[SNIP END]

Key features:

• Validate your models and diagrams
• Enable/Disable each validation rule
• Activate auto-correction for each rule
• Backup your models automatically

As depicted in the screenshot, we have defined different rules for demonstration purposes. For example, the total account of elements for each package or diagram is limited to a certain number. Furthermore, it is only allowed to use instances of classes within a sequence diagram. And each element has to realize at least one requirement or test case. Of course, these rules can be adopted and extended.

You can download this free plug-in here.

If you are interested in more rules for your modeling projects, do not hesitate to contact sales(at)lieberlieber(dot)com.

The second webinar was recorded by Oliver Alt from LieberLieber. He talks about “Enterprise Architect, AUTOSAR and ISO26262” and gives an overview about the possibilities of using Sparx Systems Enterprise Architect in development of automotive systems and software. Furthermore the webinar shows the available extensions and solutions form LieberLieber.

Take a few minutes and have a look: http://www.iccmedia-vcon.com/conference/software-development-rtos

Just right-click a diagram and select [Extensions –> EnAr Power Tools –> EnAr Connection Style Wizard] as depicted in the following screenshot.

You can apply different layout styles for all diagram links at the same time – a feature which will save a lot of time when creating models. In addition, you can also select a color to apply on your connectors.

If you only want to apply a style type for a specific diagram link, you can easily select a connector type e.g, association in a class diagram, in a drop-down box.

If you like EnAr Power Tools and want to purchase it, please visit our homepage: http://www.lieberlieber.com/model-engineering/enar-power-tools/

Wer sich für Open Data bzw. Open Government Data interessiert, hat sich vielleicht schon die “OGD Austria Suche-“ App angesehen, die einem aktuelle Neuigkeiten aus dem OGD-Umfeld serviert. Der “Open Data Browser” geht einen großen Schritt weiter und versucht all diese Daten auch gleich darzustellen.

Der Entwickler Roman Ranzmaier schreibt: “Ziel war es für jeden Datensatz zumindest eine Visualisierung anzubieten. Das ist mir zwar nicht ganz gelungen da einige Datensätze einfach nicht darstellbar sind aber im Großen und Ganzen kann man mit dem Ergebnis sehr zufrieden sein.”.

WindowsBlog | Windows 8 App: Open Data Browser Austria

The event being held in Central London is the best multi-track day in Europe to meet and interact with other EA users on all levels and abilities with a registration fee of £50.00 per person + Vat.

The event tracks are:

• Track 1: Setting up projects for success with EA
• Track 2: Project Delivery with EA
• Track 3: Implementation & lessons learnt

Agenda; Wednesday 15th May 2013

The agenda for the day will be as follows:

09:00 – 09:45

• Exhibition, Coffee & Welcome

09:45 – 10:30

• Keynote – Modelling Software Intensive Systems with Doug Rosenberg. (see his Interactive Map here)

10:30 – 10:45

• Refreshments

10:45 – 11:30

• Track 1 - Writing Use Cases in EA with Ian Mitchell.
• Track 2 - BPMN 2.0 with Phil Chudley.
• Track 3 - User Story: EA usage at ACV with Geert Bellekens.

11:45 – 12:30

• Track 1 - MDG Profiles & Toolboxes with Phil Chudley.
• Track 2 – SysML with Roman Bretz.
• Track 3 - User Story: EA usage at Evry with Knut Paulsen.

12:30 – 13:30

• Lunch & Exhibition

13:30 – 14:15

• Track 1 – Fifty Enterprise Architect tricks with Peter Doomen.
• Track 2 – Analyser Workbench with Daniel Siegl.
• Track 3 – How to do less work, have more fun and become (a bit) more famous doing it with Ian Mitchell

14:30 – 15:15

• Track 1 – Modelling with Enterprise Architect – What’s in it for the PM? With Jackie Mitchell.
• Track 2 – EA Navigator with Geert Bellekens .
• Track 3 – Open Session 2: Collaborative use of EA – Chair Simon Beck

15:15 – 16:30

• Refreshments, Exhibition and Q&A with speakers & organisers.

A summary of the last user group event can be found here: http://blog.lieberlieber.com/2012/10/18/first-european-enterprise-architect-in-london/

Our contribution “ISO 26262 kann man nur modellbasiert überleben!” was accepted for presentation at the german conference Forum Funktionale Sicherheit, 9./10. July 2013 in Munich, Germany.

Visit our presentation and learn how model-based development and model-based systems engineering helps you to fulfill the requirements of functional safety management (FSM) and ISO26262.

www.funktionale-sicherheit-forum.de