Cloudy Models

Similarly to the Return Wrapped Object Pattern , this one involves reading the EA value for an enumerated attribute value and returning a corresponding object. get objectType() { return ObjectType.fromCode( this.wrappedObject.ObjectType ); } The code stored by the native attribute ObjectType is decoded by the ObjectType enumerated type, and the enumerated value object is returned.

Any time we have an EA object return another object we need to catch the operation and return an equivalent wrapper for the object returned.  To handle these cases we use the Return Wrapped Object Pattern , which is illustrated by the following example code. get element() { return this.elementFactory.newElementWrapper( this.wrappedObject.Element ); } That is a getter is defined for the wrapper class which calls a factory method to return the wrapped equivalent. A variation on the above is when an EA object refers to the ID or the GUID of a related object.  For these cases a variation on the previous pattern can be used to achieve the same result. get parent() { return this.repository.getElement( this.wrappedObject.ParentID ); } That is, a getter is defined for the wrapper class which calls the repository object (actually the RepositoryWrapper object) to retrieve the relevant ElementWrapper corresponding to the ID in question.   Note that getEle

 Chapter 5 - Integration of MDSE In Your Development Process MDSE Is process agnostic Does not define which models must be used. Integrating MDSE can be complex.  One code generator a MDSE integration does not make. 5.1 Introducing MDS In Your Software Development Process Technical and non-technical aspects should be taken into account. Major challenges The imbalanced distribution of efforts & rewards among team members. The lack of socio-technical congruence. 5.1.1 Pains & Gains Of Software Modeling If the pains of modeling are separated from the gains of modeling, in particular with respect to individual staff.  Those that are subjectively burdened with the pains may doubt that their effort is worthwhile. Therefore, when the work distribution among the members separates the pains and gains of modeling, we must adopt policies that recognize (and compensate for) those differences. 5.1.2 Socio-Technical Congruence Of The Development Process The introduction of MDSE can bring in

Previously published on 02/08/2020 for the  Model Based Engineering SIG  Meetup group Hi All, Welcome to the monthly newsletter for August 2020.  In this update we'll cover the following. Meetup Planning Sparx Systems Updates Cloudy Models Post Summary Feature Highlight - Connectors To Connectors Meetup Planning Our next meetup will be on the 5th of August at 6:30pm.  We will look to have the meetup done over Jitsi - To join us you can click on the following link on the day. struck from the record Sparx Systems Updates A reminder that the beta of Enterprise Architect 15.2 is out, and the beta of Pro Cloud Server 4.2 is out.  Users are encouraged to download and start testing.  There's a YouTube  video  from Tom O'Reilly providing an overview of what is in the release. Upcoming Webinars: 5th August -  Sparx Systems Architecture Platform New Videos: Using SysPhS and OpenModelica with Enterprise Architect Enterprise Architect for Business Analysis: Business Analysis Planning E