Enterprise Architect

Enterprise Architect1

1

1.4

1.1.EA6

1.2.6

2.8

2.1.8

2.1.1.8

2.1.2.8

2.2.9

2.2.1.ODBC10

2.2.2.EA12

2.2.3.13

2.2.4.15

2.3.17

2.3.1.TortoiseSVN17

2.3.2.EASVN17

2.4.20

2.4.1.20

2.4.2.21

2.4.3.22

2.4.4.22

2.4.5.23

2.4.6.23

2.4.7.24

2.4.8.24

2.4.9.25

2.4.10.26

2.5.26

2.6.Class27

2.6.1.Class27

2.6.2.Class29

2.7.31

2.7.1.C31

2.7.2.C32

2.8.33

2.8.1.Text33

2.8.2.Html34

2.9.XML34

Enterprise Architect

Business Process

Requirements

Use Case

Domain Model

Class

Database

Component

Deployment

Testing

Maintenance

Project Management

User Interface

EApowerdesign

EA13 UML 2.0EA13 UML 2.0

UI

EACVSSCCexplorer

EA

EAC++, C#, Java, Delphi, VB.Net, Visual BasicPHPCORBAPythonEAEclipseVisual Studio.NetSparx SystemsIDEEA

EAJava.jar.Net

EAMDADDL, C#, Java, EJB XSDPSMPIMPSM

UML

MS Word

DDLODBC

Professional Corporate Edition

Professional Corporate EditionJava, C#, C++, VB.Net, Delphi, Visual Basic PHP

XML/

EA

a) UML 2.0

EAUML 2.0

b)

Enterprise ArchitectUML Windows

c)

EA

d)

Enterprise ArchitectQA

e) UML 2.0

UMLEAUMLOMGUML2.0

Enterprise ArchitectUML 2.0UML Profileextensions for BPMN Eriksson-Penker profile

RTFEA RTFRTF

a) AccuRevPerforce

b) XMI

c) MDAEAMDAMDAPIMPSM

d) DiffXMIEA XMIEA XMI

EAJava Archive (.jar), . NET PE Files* (.exe, .dll)Intermediate Language (.il)

e) EA Professional CorporateUMLMDAnUnit jUnitEA IDEUML///

f) MOFMOF 1.31.4XMIMOFMOFMOF 1.31.4 XMI

g)

h) WebW3C WebWSDLWSDL

i) XMLXSDW3C XMLWSDLXML

j) The Corporate EditionDesktop ProfessionalSQLMySQL, Oracle9i, PostgreSQL, MSDEAdaptive Server Anywhere MS Access backendsMDG

k) The Professional EditionActiveXEAXMI/ SQL Server, MySQL, Oracle9iMDG

l) The Desktop EditionUMLDLL/ Active-X

1.1

2.1

Tool->Options-Source Code Engineering->Default Language For Code Generation->JAVA3

-3

Close

Tool->Options- Code Editors->Default Database->ORALE

4

-4

Figure 2 provides a high-level schematic of the relationship between Enterprise Architect and the external version control system. Note that versions are stored and retrieved as XMI files. XMI is used to serialize Package information to create a point-in-time snapshot. Enterprise Architect enforces that only a single user edits a given Package at once. This approach represents a Lock-Modify-Unlock solution, which helps to avoid revision conflicts especially useful as XMI files are considered binary artifacts that cannot be merged directly via the Version Control System.

EAXMIXMIEAVSSXMI

: EADBMS

EAUMLRDBMSEA(SVN)

ODBC

ODBC for MySQL

a) ODBC)

b) ODBC

c)

TestConnection successful

EA

a) EA

b) EA

Project-->Model inport/export-->Export package to XMI

c) VCC

d) EA

Project-->Model inport/export-->Inport package from XMI

a) ToolsData ManagementProject Transfer

b)

a) ToolsData ManagementProject Transfer

Subversion

Subversion

TortoiseSVN

C:\svnfile"SVN Checkout""Checkout"" URL""svn://localhost:3690/ch14_test_repo"

admin/admin

EASVNEASubversion

EAMySQLEA"Project-->Version Control-->Version Control Setting"Subversion

Subversion

EA(Package)

"Package Control""Check In""Check Out"

Every element, including a requirement element, that is part of a model has properties or attributes. Enterprise Architect has built-in requirements attributes such as status, difficulty, priority, and type.

It is common that there are a series of requirement attributes specific to any project. You can enter any number of additional attributes such as stability, cost, and lateness penalty through the use of tagged values.

Tagged value data for an element is available as a separate window, which is accessed using Ctrl+Shift+6 (or from the main menu View | Tagged Values).

To set this mode for a specific diagram, right-click on the diagram, and in the context menu, select: Properties | Elements | Show Compartments | [] Tags.

Select a Package in the Project Browser

Right-click and from the context menu select: turn on Level Numbering

Select a Package in the Project Browser

Right-click and from the context menu select: List View:

Open the Traceability window (View | Traceability or Ctrl+Shift+4).

Select an element to display its relationships.

The Audit feature enables you to record model changes in Enterprise Architect. It records details of who changed an element, when and what was changed, along with the prior state of the model. This can be particularly useful for recording a history of changes to requirements models.

1. From the main menu select: Project | Audit View, which opens the following view:

2. Select the Audit Settings button.

3. This will bring up the Audit Settings window:

4. In the Audit Settings window set: [] Enable Auditing on as shown above.

Enterprise Architect supports logging of Change-requests against Requirements. This can be defined using two different methods:

a) Using the Maintenance View to list Changes, Defects, Issues and Tasks against each element.

b) Using custom elements of type Issue and Change linked to the External Requirements being altered.

The Maintenance View can be accessed from the main menu using: View | Other Element Tools | Maintenance or (Alt+4). Figure 10 is an example of a set of changes listed for an element:

Enterprise Architects maintenance elements include Elements of type: Issue and Change. These are accessible from: Toolbox | Maintenance or Toolbox | Custom.

Enterprise Architect allows you to enter requirements at the level of an individual UML element. At this level these requirements can best be thought of as the responsibility of the element.

Internal requirements can be externalized (see the [Move External] button above). This will create a new external requirement element with a realization relationship back to the original element (in this scenario a use case element).

External requirements may be color coded to enable quick visual cues indicating the status of a requirement. To enable color coded external requirements take the following steps:

1. From the menu, select Tools | Options to open the local options window.

2. From the hierarchical tree select Objects.

3. Check the Show Status colors on diagrams checkbox.

Mode-->Use Case Model "Use Case Diagram"""

ClassClass

File->New Project->->Select modelClass-5

-5

6

-6

Class Elements

Package

Class

Interface

Enumeration

Table

Signal

Association

Class Relationships

Associate

Generalize

Compose

Associate Class

Assembly

Realize

Nesting

Package Merge

Package Import

Common

Note

Constraint

Document

Artifact

Requirement

Issue

Change

Boundary

Dependency

Realize

Trace

Information Flow

Note Link

-2

Class

7

-7

NameClass TestAlias

ClassTest

Testclass diagramPropreties8

-8

Diagram9

-9

Use Alias if Available

C

Project->Source Code Engineering->Generate Package Source Code10

-10

11

-11

GenerateC

C

CClassGenerate CodeF1112

-12

12C3Generate

Text

Project->Documentation->Rich Text Format(RTF) Report19F8

-19

Output to fileText

Html

Project->Documentation->HTML Report16Shift+F820

-20

Generate

XML

Project->XML Schema->Import XML Schema21

-21

FilenameXMLImport

uc Business Rules Model

class class

- kb: String

+ calculateRate(Boolean) : Integer

+ calculateRate(Boolean) : Integer

1

1

11