In this webinar, we'll demonstrate :
Don't miss this opportunity to learn more about Enterprise Architect
|Create Model Review:||create-review.mp4|
|WebEA Model Reviews:||review-discussions-webea.mp4|
|Time Aware Modeling:||time-aware.mp4|
It is due for release imminently. Currently, the beta version is available for download at: http://sparxsystems.com/ea135
Update: It was released on July 12th and can be downloaded from:
You'll simply download and run the installer from our Enterprise Architect release page. The installer will replace your existing Enterprise Architect installation.
Yes. See our response to a similar question from an earlier release of Enterprise Architect.
You can view past webinars from our Webinar Library.
Update: You can test Release 13.5 by downloading the free Trial Version and using it for a 30 day trial period.
The Beta version is now available for download from the registered users site. As usual, we will make the official release available for download from there as well. You can access the version 13.5 installers from the following web pages:
The two main requirements are a model repository that supports multiple users and the Enterprise Architect Corporate edition, which allows you to connect to such a repository with role-based (user) security enabled. For details, see the Help topic Team Support and its subtopics.
Packages and individual elements in Enterprise Architect have an Author field. In team-based modeling scenarios in which role-based security is used, the Author field is filled in automatically when a user creates a new element in the model.
We used a third-party cloud service to deploy the instance we demonstrated, but you can don't have to do this. Your own private cloud infrastructure or a third-party provider with an external cloud are both supported.
No, they can be edited and updated.
Currently, this is not supported.
You can access a read-only model on a Pro Cloud Server via the URL:
Model: EA Example
Only if the end user has HTTP access to the server that hosts your WebEA instance. The model content is shared via HTTP.
Yes. Firebird is one of numerous DBMS products that can be used as a model repository for both WebEA and Enterprise Architect. For a full list of supported DBMS products, see the Enterprise Architect System Requirements web page.
Sparx Systems has some demonstration Pro Cloud Server instances on servers residing in Australia, the UK and the USA, among others. We support and encourage you to run your own Pro Cloud Server instances within your own network to maximize the control and security of your data.
Much of it can be removed by disabling user security in the copied model. For details, see the Help topic Enable/Disable Security
All of the features that we demonstrated in this webinar presentation are available with on-premises (on-prem) installations of Enterprise Architect. Furthermore, with the exception of WebEA, all features we demonstrated are available in the Corporate and higher editions of Enterprise Architect; to use WebEA, you need a separate Pro Cloud Server license. You can then deploy a Pro Cloud Server instance within your own corporate cloud/server infrastructure, or it could be deployed within a third-party cloud offering.
Yes, the features we demonstrated are available when using DBMS server repositories, with the exception of the WebEA interface. WebEA is only available with the Pro Cloud Server. Also note: You typically wouldn't use an EAP file as a repository for multiple users to share simultaneously.
WebEA is part of the Pro Cloud Server. It is not included with stand alone installations of Enterprise Architect.
Yes, we intend to update the Cloud Server with bug and security fixes.
WebEA is separate. It comes with the Pro Cloud Server, which is a separately licensed server-based product for use with Enterprise Architect.
It is an additional product. It is not contained in the Ultimate edition license. For Pro Cloud Server pricing details, see the Special Offer web page.
No. The pricing for Pro Cloud Server is listed on a per-server basis. You may be interest in the special offer currently available for Pro Cloud Server. For details see the Special Offer web page.
No. Sparx Systems licenses Pro Cloud Server software (which includes WebEA), but does not provide hosting services. If you use a third-party hosting solution or cloud platform, that would be a separate cost that does not involve Sparx Systems. Obviously, if you deploy Pro Cloud Server within your own server infrastructure there is no additional fee beyond the Pro Cloud Server license, for hosting or storing models and reviews.
Yes, our Corporate and higher editions of Enterprise Architect support this.
The review does not create a copy of the element. If you are interested in this kind of functionality, you could use time aware modeling, and include a particular version of an element in the review.
Not at this time.
Currently, this is not supported.
You will probably need to record this information explicitly. If you use Resource Allocations, however, you could investigate the use of Charts in Enterprise Architect with a custom SQL query to extract the required information. For details, see the Help topic Charts.
Yes, you can use XMI to export and import packages that contain Review elements. Note: Even though our example model used a package named Model Reviews to contain Review elements, it is not required that you do the same; you can place Review elements anywhere in the model hierarchy.
You should also note that although you can use XMI to export and import packages that contain Review elements, there is not currently an export or import mechanism for the actual review data, such as topics, posts and replies.
Enterprise Architect treats Review information as metadata associated with the model itself; it is not owned by the elements that are being discussed. This allows you to discuss locked and version controlled elements effectively.
No. The link is implicit. Review elements are only linked to - that is they form a Review Set with - other model elements by virtue of those elements appearing on the child diagram of a Review element. For example, this image shows that the packages Application Design and Requirements and the element named Book Lending Application are all part of a Review Set. That Review Set belongs to the Review element named Book Lending Solution Design Review.
The Review element's child diagram determines which elements are part of the Review Set
When the review is completed, you would just leave that review element and the associated diagrams alone. You could lock them to prevent further changes. If you need to do a similar review in the future you would create a new review element.
The Review element with its associated Manage Reviews window and the Model Mail feature provide different and complementary functions. Whereas a message via Model Mail is great for communicating with a known set of recipients and alerting them to changes at a particular point in time, the Review element can be observed by different parties at any time. Team members can join and leave the discussion as appropriate, and any contribution they make to the discussions or reviews will be visible to a potentially large audience, indefinitely. This is obviously not possible with a Model Mail message, which requires a targeted unchanging audience, defined by the author at the time of composing the message.
Yes. There is no restriction on the types of models that you can view or comment on via WebEA.
Although the example we used involved the review of a specific solution for the Book Lending system, Enterprise Architect's Review elements can be applied at any level within the model repository. The Review could be, for example, on a business process, a top-level package that represents an entire enterprise architecture view, or a third-party industry reference model.
Regarding a report on how many reviews were conducted last week and their results, the Manage Reviews window provides a list of all reviews in the model, showing the start and end dates and review status among other fields. We will consider making these fields sortable in future as well. Because each Review is an element in the model, the results can be conveniently stored and displayed via the element's notes field or as part of a document that is stored with that element in the repository. This image shows an example of the Manage Reviews window providing a summary, and the Notes window displaying results that were entered into the Review element's Notes field.
Regarding standards: There are many ways to incorporate these into the model repository, depending on the nature of the standard. For example, there are numerous industry reference models that are already developed in Enterprise Architect (such as for power networks, geospatial data or telco), so you can directly include those reference models as part of your own corporate model repository. For internal corporate standards, you might use Enterprise Architect's built-in Document Artifacts to store them, or drop office documents directly into the repository.
Integration with Portfolio Management tools is not provided out-of-the-box, though you might use a third-party extension or add-in for Enterprise Architect to achieve this.
No. Once a post has been submitted, it cannot be edited - only deletion is possible.
At the moment, this has been limited to the set already provided, using one of the themes available.
Not at this time. The only images that can be used as icons for Navigation Cells are those listed in the Select Image dialog, which displays when you first create the Navigation Cell, or later when you invoke the context menu: Appearance | Select Navigation Image.
Not in an automated way. You would need to manually merge variants.
Not really. When you make a change to the nested element, that implicitly changes the parent element.
It depends on how your Requirements are connected. Currently, tagged values can be inherited using a generalization connector between elements. This allows the value to be displayed on all subtypes until overridden. This functionality, however, isn't available for other types of relationship. If you need something like this for other relationship types, it may be achievable via a custom add-in for Enterprise Architect.
At the bottom of the Insert Related Elements dialog, there is a check box labeled Layout Diagram when complete. You can enable that option prior to clicking OK.
There are no near-term plans for this. However we find that Enterprise Architect running via Wine or its commercial counterpart, CodeWeavers CrossOver, performs very well. For installation instructions, please see our web page on installing Enterprise Architect on Linux and Mac.
Not at the time of presenting this webinar.
You should contact our support team directly by raising a support ticket. You could do that from within Enterprise Architect via the Start Ribbon | Help | Explore Online Resources | Bug Report Page, which will invoke our registered users support page. Our support team would need some more details, such as the screen or controls you have tried and perhaps a small sample model to confirm or reproduce this issue.
There isn't a reporting mechanism from the Traceability window along the lines of what you suggested. It's purpose is primarily for exploring the model dynamically via connected elements, which can certainly be in the context of impact analysis, as you suggest. It is not intended as a documentation tool however. That said, we recommend using Enterprise Architect's reporting templates - not scripting - to do this kind of reporting on connected elements. It is true, this does require some detailed configuration, rather than a click-and-go kind of approach. You might like to review some of our previous webinars on reporting:
Regarding WebEA, we understand the concern about finding elements that don't exist on any diagram. There are various modeling scenarios where this situation occurs. Fortunately, in WebEA each package does provide links to its contained elements, regardless of whether those elements are in a diagram. There is in fact a simple way to navigate the model as a hierarchy in WebEA - it just doesn't provide the full tree view that you have in the desktop application. If you click the 'element branch' or 'hierarchy' icon on the top right of the screen in WebEA, you can drill down from the top-level package to lower level packages. If there is a child diagram for the selected package, it will display that diagram in the contents view on the left side.
There is another icon next to the 'hierarchy' button to toggle that display so that all child nodes of the package, such as diagrams, elements and sub-packages, are displayed. So navigating the model hierarchy without placing elements on a diagram is certainly possible in WebEA. It means using more simplistic controls than a fully-fledged tree view though. Especially for review purposes and convenient navigation for web/mobile users, the visual Navigation Cells serve a useful purpose here.