Enterprise Architect version 14.0



My Profile

Social Media Channels

facebook google plus twitter youtube linkedin

White Papers

White Papers (83)

White papers provide in-depth technical discussion and best practice guidance on a wide range of modeling topics. The information presented by industry experts from the user community will help you learn new approaches to modeling and solving real-world problems using Enterprise Architect.

This White Paper looks at ways to create project documents that improve project quality, provide readers with relevant, easily navigated information, and give new insights. Using EA and eaDocX, approaches are described that can bring our project communications into the 21st Century. This White Paper looks at ways to transform our project documents, helping readers to find and use information that is relevant to them. In both Waterfall and Agile developments, excellent documents can improve project quality and give new insights. New document capabilities allow authors to create high quality, accurate and targeted documents, and allow readers to navigate their…
Future Networks and Policy at Scottish & Southern Energy Power Distribution are researching new systems and building foundations for Smart Grid Networks. This paper tells of a journey based on a vision to introduce more formal modelling methods using an IT practice to allow the company to deliver business-driven end-to-end solutions that meet business needs.
Enterprise Architect provides the facilities to create and edit models, to derive implementation code from models, and then to test and analyze the resulting software systems. This whitepaper shows how these activities can all be achieved within a single model driven development environment, and highlights the benefits of doing so. This paper covers Enterprise Architect's build, debug and testing features along with its Visual Execution Analysis tools. Together, these tools allow you to integrate your model with each and every phase of the software development lifecycle, thereby facilitating true Model Driven Development.
This paper considers the requirements for a robust project risk and issue management process and describes how Enterprise Architect and eaDocX can support this key project activity. Many projects use Enterprise Architect (EA) to store information about their projects: requirements, use cases, designs and other information. What is less common however is to use EA as the repository for ALL project information, replacing all the spreadsheets and reports which come along with a well-managed project. This document, one in a series on EA for Project Managers, looks at how risk and issue management and reporting can be automated, made more…
In our paper (full version available at http://www.es.tu-darmstadt.de/download/publications/anjorin/als2011.pdf) we describe the reasons and background for our decision to switch to EA as our frontend for our meta-CASE tool eMoflon (www.moflon.org/emoflon). MOFLON supports standard compliant metamodeling, code generation andmodel transformations. Development started in 2002 and it has since then been used successfully in a number of case studies for various applications. In recent years, the Eclipse Modeling Framework (EMF) has become a de facto standard, offering stableand well-tested components. In addition, numerous professional, industrial strength CASE tools have become increasingly affordable and open to extensions. We are convinced that it is…
Describes the value of combining the Service Oriented Architecture notation provided by SOMF with the BPMN process modeling notation.
Monday, 29 August 2011 00:00

Data Modeling with the UML

Written by
The UML is a popular modeling notation for programmers, but it is little used by database developers. Nevertheless, the UML is highly effective for high-level conceptual data modeling. The UML notation avoids confusing database details, making it easier for business experts to understand data models. The suppression of details promotes deep thinking about data models, such as the use of abstract patterns. This talk explains the UML notation by comparison to IDEF1X.
Monday, 22 August 2011 00:00

Data Modeling - From Conceptual Model to DBMS

Written by
Enterprise Architect supports comprehensive functionality for modeling database structures. This paper covers the core features for data modeling over the full lifecycle of an application. The initial development of a system typically involves numerous levels of abstraction. Database modeling traditionally includes a well established three tiered approach: Conceptual Model Logical Model Physical Model This paper covers creating these models, interconnecting models on these levels, using MDA transforms for generating the Physical model from the Logical model, along with generating schema scripts for loading to your DBMS. It also covers the features for remodeling legacy systems including Reverse Engineering an existing…
An important part of implementing Enterprise Architect, as an effective tool for agile analysis and design, is automating generation of project documentation. You need to be able to produce complex and stylised output and this has been a challenge for many. The first of a number of white papers, based on our Master Class training program, this paper looks at how to achieve complete project documents from within your Enterprise Architect models. Having now implemented EA as the tool for analysis and design, for over 11 organisations, I have found that a critical part of its adoption is the transition…
Friday, 22 July 2011 00:00

Design Driven Testing for Systems

Written by
Design Driven Testing (DDT) for software was first outlined in the book Use Case Driven Object Modeling with UML: Theory and Practice (by Doug Rosenberg and Matt Stephens), and then described in detail in Design Driven Testing: Test Smarter, Not Harder by the same authors. DDT is a highly methodical approach to testing, allowing you to know when you’ve finished – i.e. when you’ve written enough tests to cover the design and the requirements. It helps you to “zoom in” and write algorithmic tests to cover intensive or mission‐critical sections of code, and to know when it’s safe to “zoom…
Page 4 of 6