Sparx Systems has released a major update to its Enterprise Architect modeling, visualization, and design platform based on the UML 2.4.1 standard. Version 9.3 is described as distinct from previous versions by virtue of its ability to work with multiple diagrams, tools, and views simultaneously.
Capable of accommodating a developer's chosen workspace, technologies, and menus in a domain-specific viewpoint, the new product also includes enhanced model-driven testing with codeless xUnit style Testpoints. There is also the ability to run simulations based on State tables; major updates to the ArcGIS geospatial profile, as well as ArchiMate 2.0 support — the latter feature clearly is a move in response to ArchiMate's existing alignment towards TOGAF (see below note).
NOTE: In related news from late January of this year, The Open Group announced the release of ArchiMate 2.0, the latest version of the organization's open and independent modeling language for Enterprise Architecture. Official statements specified that, "Developed by the ArchiMate Forum of The Open Group, the latest technical standard is now more aligned with the TOGAF Enterprise Architecture framework."
Sparx Systems says that Enterprise Architect 9.3 now offers developers the option to display multiple diagrams and model views on-screen; snap off diagrams and float or dock where desired; drag and drop between diagrams; run simulations showing all diagrams at once; and concurrently display diagrams, source code, reports, documents, relationship matrices, and scenarios.
According to Sparx Systems' website, "With complete traceability from mind mapping, through requirements to business and software design and deployment, Enterprise Architect 9.3 provides the kind of robust and efficient visualization and collaboration required in today's large and demanding modeling environments. A truly agile modeling solution, Enterprise Architect 9.3 provides a low installation overhead, sparkling performance, and an intuitive interface."
Features also include options to:
- Trim down menus to essential commands
- Apply per-configured menu sets or create your own
- Use Codeless xUnit testing driven from the model
- Define one or more invariants, pre- and post- conditions, and line conditions in the model
- Benefit from Testpoint constraints, which may be conditional on object state
- Use the debugger ,which applies and evaluates as code executes