Top Community Contributors
For whom develops systems, a good and integrated toolset is fundamental: Herminio Lourenço
Written by sparxsystems
Managing a Student Project with Enterprise Architect – Part 2
Written by doug rosenberg
What's new with ArchiMate 3.0 & EA v.13?
Written by DT_Sam
Reader's Choice Award Recognizes Sparx Systems For Software Architecture
Written by sparxsystems
Managing a Student Project with Enterprise Architect – Part 3
Written by doug rosenberg
Fast access to each diagram in Enterprise Architect
Written by Dr. Konrad Wieland
EA TFS Connector a new add-in for the Bellekens EA Toolpack
Written by Geert Bellekens
New SysML Book for Enterprise Architect Users
Written by Dr. Konrad Wieland
Sparx Systems Enterprise Architect has been honored with a Silver medal for Software Architecture excellence in this year's Visual Studio Reader's Choice Award.
This follows on from winning a Bronze award in 2015 for outstanding solutions in the Software Design, Frameworks, and Modeling Tools category.
"For Sparx to place in the tight Software Architecture solutions category means readers are paying attention. It can only mean good things in the future for this builder of model-driven software development."
- Michael Domingo, Editor in Chief, Visual Studio Magazine
The Reader's Choice Award has been conducted by Visual Studio Magazine for 23 years, with winners selected from a pool of over 400 product and sevices within 36 categories.
A media announcement has been released by Sparx Systems, please visit the company News Room for more.
For more details about the Reader's Choice Award, please visit the Visual Studio Magazine website.
Above all else one of the most recurring questions Dunstan Thomas Consulting has encountered from clients over the years is "How do we use the Relationship Matrix?"
With that in mind we've got a short clip on how you can start effectively putting the Relationship Matrix into use for yourself...
Online Training, Marketing & Product Specialist
Dunstan Thomas Consulting
by Phil Chudley, Principal Consultant at Dunstan Thomas Consulting
The Open Group released the official specification of ArchiMate 3.0 in June 2016, and this new specification is supported in Enterprise Architect version 13. This article summarises the new features and changes within ArchiMate 3.0 and provides an example of how to migrate an existing ArchiMate 2.0 model to ArchiMate 3.0 model using Enterprise Architect v.13.
Summary of Changes
The following is a summary of the changes made within ArchiMate 3.0:
- Motivation Extension;
- New element for modelling Outcomes.
- New set of Strategy Elements, Resource, Capability, Course of Action.
- Business Layer;
- Representation of the Contract element modified so as to be different from the Business Object Element.
- Location element removed (although Enterprise Architect has re-located this element to the Technology Layer – Physical Extension).
- Application Layer;
- Two new elements added, Application Process and Application Event
- Technology layer;
- Elements called Infrastructure in ArchiMate 2.0 are now called Technology in ArchiMate 3.0.
- Four new elements added, Technology Process, Technology Interaction, Technology Event and Technology Collaboration.
- New set of Physical Elements, Equipment, Facility, Distribution Network and Material. These elements are known as the Physical Extension.
- Implementation and Migration Extension;
- One new element added, Implementation Event.
- Representation of Assignment modified to have a directional arrow.
- Bi-directional Access relationship added.
- Plus (positive) and Minus (negative) symbols added to Influence Relationship.
- New relationship, Serving.
Detail of Changes
The following tables provided an example of the changes for each of the sections listed in the Summary of Changes above.
|Outcome||An end result that has been achieved.|
|Resource||An asset owned or controlled by an individual or organisation.|
|Capability||An ability that an active structure element, such as an organisation, person, or system possesses.|
|Course of Action||An approach or plan for configuring some capabilities and resources of the enterprise, undertaken to achieve a goal.|
|Contract||A formal or informal specification of an agreement between a provided and consumer that specifies the rights and obligations associated with a product.|
|Application Process||A sequence of application behaviours that achieves a specific outcome.|
|Application Event||An application behaviour element that denotes a state change.|
|Technology Collaboration||An aggregate of two or more nodes that work together to perform collective technology behaviour.|
|Technology Process||A sequence of technology behaviours that achieves a specific outcome.|
|Technology Event||A technology behaviour element that denotes a state of change.|
|Technology Interaction||A unit of collective technology behaviour performed by (a collaboration of) two or more nodes.|
|Equipment||One or more physical machines, tools, or instruments that can create, use, store, move, or transform materials.|
|Facility||A physical structure or environment.|
|Distribution Network||A physical network used to transport materials or energy.|
|Material||Tangible physical matter or physical elements.|
Implementation & Migration Extension
|Implementation Event||A behaviour element that denotes a change of state related to an implementation or migration.|
|Assignment||Expresses the allocation of responsibility, performance of behaviour, or execution.|
|Serving||Models that an element provides its functionality to another element.|
|Access||Models the ability of behaviour and active structure elements to observe or act upon passive structure elements.|
|Influence||Models that an element affects the implementation or achievement of some motivation element.|
Implications to existing ArchiMate models
If an organisation has modelled their Enterprise Architecture using Enterprise Architect and ArchiMate 2, and are now using Version 13 of Enterprise Architect, they have two courses of action:
- Continue to model using ArchiMate 2.0. In this case no action is required either for Enterprise Architect or the model repository. An organisation would continue to model using ArchiMate 2.0 if they do not wish to make use of any of the new features in ArchiMate 3.0.
- Migrate their existing ArchiMate 2.0 model to ArchiMate 3.0, and then continue to model using ArchiMate 3.0. An organisation would continue to model using ArchiMate 2.0 if they wish to make use of any of the new features in ArchiMate 3.0.
My own personal opinion is that an organisation should consider moving to Enterprise Architect version 13 (mainly due its new feature of “Time Aware Modelling”) and ArchiMate 3.0. One of the main reasons, is due to inherent ambiguity (due to the lack of direction indication) in the assigns relationship in ArchiMate 2.0, which has been eliminated in ArchiMate 3.0 by making the assigns relationship directional.
Migrating an ArchiMate 2.0 model to ArchiMate 3.0
Enterprise Architect version 13 provides a migration script for this purpose. The following steps are used to perform the migration:
- Take a backup copy of the existing model repository.
- Using the Configure | Manage Technology ribbon, ensure that both ArchiMate 2.0 and ArchiMate 3.0 MDG technologies are enabled.
- Using the Code | Scripting ribbon, make the scripting window visible:
- Select the topmost package (or view) that contains the model to migrate:
- Select the script Migrate ArchiMate 2 to ArchiMate 3 in the scripting window.
- Right-click and select Run Script from the menu.
- The progress of the migration, together with any errors / warnings will be displayed in the system output window.
- Review the diagrams (you may have to tidy some of the relationships).
- Turn off the MDG ArchiMate 2.0 using the Configure | Manage Technology ribbon.
NOTE: It appears that composition relationships are NOT HIDDEN, when using nested structures in ArchiMate 3.0. I suspect this is an Enterprise Architect version 13 issue. This is likely to be fixed and should not deter migration, as these relationships can always be hidden using the Visible Relations function in Enterprise Architect. (Layout | Manage ribbon and select Show and Hide Relationships… from the menu).
Dunstan Thomas Consulting
You'll find lots of useful Enterprise Architect videos on our YouTube Channel.
Veteran Project Manager and user of Enterprise Architect in 100+ projects since 2001, Herminio Lourenço has recently published some illuminating articles regarding toolsets for systems development.
This article was orginally published on Mr. Lourenço's LinkedIn profile on November 22nd, reprinted on the Sparx Systems Community site with permission from the author.
Firstly, tool is something that enables, facilitates, gives bigger productivity to one or more activities. The tool works for us. We dedicate some effort and as a result we have a lot of work done. That said, I will suggest a set of tools to give productivity and quality to systems development.
A concept being introduced is the ALM: Application Lifecycle Management. According to Wikipedia, is the marriage between business management with software engineering, which became viable thanks to tools that facilitate and integrate processes such as requirements analysis, architectural modeling, code development, change management, test management and managing of versions of products accomplished. Each one of these processes is part of a stage of a software life cycle.
This can be achieved through a framework, as the Jazz from IBM or Microsoft TFS, among other options, which integrates specialized tools to manage: requirements; code repository; construction; architecture and coding; tests and quality, versions and components.
In that effort to implement multiple tools, the company may have to invest hundreds of thousands of dollars and dozens of months in software settings and in training.One of the options that brings fastest return in productivity and quality is the Enterprise Architect (EA) from Sparx Systems. With this tool you can manage and analyze requirements, with automatic control of traceability of the requirements until the code and vice versa, besides producing the models of analysis and design and code as much classes as databases.
Support for testing and integration with configuration and release managers practically complete the required skills. Furthermore, EA has tools like KANBAN and task planning that help you plan and control the progress of work.
Other tools like Jira and Subversion can help complete the spectrum.
Of course that the biggest suppliers will try to convince IT managers that this solution may not be as good and complete as their offers, but this solution has more than 300,000 users developers across the planet. Theirs might have a few hundred followers. I will not discuss what is the perfect solution because it doesn't exist.
The adoption of a good, solid and tested set of tools is crucial to obtain the desired productivity in systems development.
Save the Date: 21.2. – 22.2.2017
Enterprise Architect 13 is full of new functionalities that we would love to show and explain to you. So, for the first time ever, we will be presenting EA 13 as a combination of numerous Workshops in a two-day format. We're looking forward to seeing you there, and to showing you how to use the new EA 13 to your advantage!
This event caters primarily to German-speaking users; therefore, please be aware that all presentations will be delivered in German.
For more details, please visit the Sparx Systems Central Europe website: http://www.sparxsystems.de/ea-practice-days/
With the initial release of the Airline Industry Data Model (AIDM), and with an increasing number of airline industry standardization workgroups leveraging and adding to the data model, a training consortium of Sparx Systems’ Training Partners will support the data model with a global training program designed specifically for the airline industry.
This training will provide guidance and skills to individuals involved in the development of Airline Industry Data Exchange standards, as well as organizations or individuals wanting to use the models in the AIDM for development of their IT systems.
Public Training Schedule for 2017:
This webinar will show you how to make the most of Dynamic Documents to create simple, yet effective reports.The 'Dynamic Document' tab of the Document Window helps you to instantly generate a document on a selected element, using one of a range of templates. A style template consists of one or more command lines, each of which defines an element type (or all element types) and the document template to apply to the generated document.
In this LIVE webinar session, you will learn how to:
- Create your own style templates and document templates
- Understand how selectors and style templates work
- Use the Template editor to create rich and engaging document templates
We are trialling a new webinar technology based on YouTube Live streaming.
We’re attempting a “crowdsourced bad driver reporting system” this semester, and because we need to be really productive, we’re using Enterprise Architect to model the project, field-test the Resilient Agile process, and to coordinate all of the student homework. Students communicate with each other and with me using a shared EA model.
This semester I’m working with a group of 15 Masters students and an aggregate effective time budget of 80 student hours per week. We’ve got about 12 usable weeks of student time, so it works out to a time budget of roughly 1000 student hours (that’s about half-a-person-year at 40 hours a week) over a 3 month schedule.
Resilient Agile is a flexible process in that it can be employed with traditional Scrum/Kanban sprints and backlogs, or alternatively we can leverage parallelism, and each student can be assigned a use case and develop their use case independently.
I’ve been a big fan of leveraging parallelism in software development since I was a programmer at NASA/JPL way back in the 80s when I rescued a late project using a “divide-and-conquer” coding strategy, so we’re trying to see how far we can push the limits on massively parallel development with student projects at USC. Communication and well-defined interfaces are key when team members are working in parallel, so the shared EA model is critically important.
Parallel modeling and development has also been a theme of our ICONIX JumpStart classes for the last 20 years, where we go into industry and work a client’s real project by splitting the class up into “lab teams”. Typically in ICONIX JumpStart classes we put 3 or 4 students on a package of use cases, whereas on this project each student got a single use case.
If you’re going to leverage parallelism in development you have to do things a little bit differently. Here’s an overview of the process we’re following:
1. Plan for Parallelism (identify dependencies and architect for parallelism)
2. Build the Right System (discover requirements, prototype areas of technical risk, and agree on conceptual designs)
3. Build the System Right (carefully review detailed designs)
4. Integrate as often as necessary
Enterprise Architect is a key enabler of the above process. I would never attempt this approach without a good solid modeling tool at the heart of it. This article will show how we’ve used EA to accomplish the 4 steps above.
The final Enterprise Architect User Group event in Europe for 2016 will be held on November 11th at the Folksam, Bohusgatan 14, 106 60 Stockholm.
Tickets available now for the upcoming Swedish Enterprise Architect User Group, full schedule published with presentations based on separate User Story and Technical tracks
For just €75, join with other Enterprise Architect users for the last European User Group Event of 2016. Presentations will be in English and Swedish.
Meet other users, and share practical insights, advice, experience and inspiration.
Full event information, including directions to the venue, agenda and presentation abstracts, plus links to buy tickets are available now at www.eausergroup.com