Introduction to the use of EA drawing tools

The previous blog post describes the EA vs Rose modeling tool, which will now introduce the use of EA drawing tools.

First, Enterprise architect introduction

1.EA (Enterprisearchitect) is a case software (Computer aided Software Engineering) that has excellent support for software system development. Unlike ordinary UML drawing tools such as Visio, EA will support the whole process of system development. In the requirements analysis phase, the system analysis and design phase, system development and deployment have strong support, coupled with the 10 programming languages of the pros and cons of the project, project management, document generation, data modeling and so on. Allows for the best development efficiencies for each role in system development.

2. Life cycle Software Design--enterprise Architect is a goal-oriented software system. It covers the entire cycle of system development, in addition to developing class models, including transaction process analysis, use case requirements, dynamic models, components and layouts, system Management, non-functional requirements, user interface design, testing, and maintenance.

3.EA Features: Fast, stable, high performance

4. Includes:

Structure chart: Class, Object, synthesis element, package, component, layout;
Behavior Chart: Use case, communication, sequence, interaction overview, behavior, status, timing;
Extensions: Profiling (simple behavior), customization (requirements, changes, and UI design).

Second, create new projects 1. After installing the EA, start the software. Click "Create new Project" To open the Create New Project dialog box.

"Figure 1" 2. Create Project:

Click file->new project-> named Save-> Select the type you want to create in select model (Figure 1)-> Click OK to confirm the interface as shown in Figure 2

                                                    

 

"Figure 2"

                  

Business Process	Business Process
Requirements	Demand Analysis
use case	Use Cases
Domain Model	Domain Model
Class	class Design
Database	Database Design
Component	Component
Deployment	Deploy
Testing	Test
Maintenance	Maintain
Project Management	Project Management
User Interface	user Interface

table -1 3. Create a "Class" model

 

"Figure 3"

 

Class Elements
Package	Package
Class	class
Interface	Interface
Enumeration	Enumeration
Table	Table
Signal	description of the object communication signal
Association	Associated
Class Relationships
Associate	Implement
generalize	Generalization
Compose	composition
Associate Class	Association Class
Assembly	Assembly
realize	Implement
Nesting	Nesting
Package Merge	Merge of Packages
Package Import	Import of Packages
Common
Note	Notes
Constraint	constraint conditions
Document	Documents: Attaching document Attachments
Artifact	Artificial: Any piece of information that represents any system
Requirement	Requirements Description
Issue	Problem Description
Change	Description of Change
Boundary	Dividing line
Dependency	Dependency Relationships
realize	Implement
Trace	Tracking
Information Flow	Data Flow
Note Link	Comment Links

table -2 4.EA Software Configuration

we found that the name shown by default "Class" is test, but if we need to display the alias, we need to set the following:

"Figure 4"


"Figure 5"
After generating the class, we can add some variables (right "variables" on the class component), and the variables will basically hold some of the data of the class itself, just like the sex, age and other data characteristics of the person. For example, we register the class, there are data link variables (it needs to know which database they are dealing with), but also may have the number of per-day registration limit of data variables and so on.

"Figure 6"

classes also need to add methods (right-click on the class component "method"), for example, in the registration class, you need to check the input of the verification code, the need for data manipulation, the need to check the number of day registration and so on. In the class method, we can also set parameters for each method, parameter types, and comments on parameters, which will be generated directly into the code file as an annotation of the parameters and methods within the code engineering.                                                

                          "Figure 7"

                              "Figure 8"
Third, use of other graphics

"Figure 9"
Object graph, which is a supplement to the class diagram, is primarily a demonstration of the different things that the classes in the system do after they are instantiated in different scenarios.
Interaction diagrams (interaction), collaboration Diagrams (communication), and sequence Diagrams (Timing), which embody the interactions between some entities in the system. Collaboration diagram is to focus on interaction with the expression entities, in the new version of UML, collaboration diagram is also called communication map, more can reflect the entity is the communication between the principle of collaboration. And the sequence diagram emphasizes the sequence of the interaction of each entity part. For example, sending a prompt for a successful registration occurs after the registration class verifies the input data, not before.
In addition, there are other graphics, such as status Diagram (state), deployment Diagram (Deployment), Component Diagram (component), activity diagram (activities), please refer to the relevant documentation. At the same time, EA supports a lot of graphics, where the mind map (which expresses and assists in thinking processes), and the Web Model diagram (which shows the model structure deployed on the site) is only available in recent versions.
Vi. Data Modeling
In the data Model Diagram (modeling), EA supports 13 different models of database modeling, generates SQL statements directly, and also imports existing data table structures through ODBC.

"Figure 10"
The following example sets up a data table of student dormitory personnel, which uses SQL. The first is to create a data table component and then set its properties.

"Figure 11"

Add field (right-click variable on table symbol), set field data type, length, set as primary key, etc. Here you can use Chinese as the field name, in the "Alias" to write the English section name, in the generation of SQL, select "Use available aliases" can be generated in English name field names.

"Figure 12"

Generate the table SQL, click on the parent package of the data model and select "Project" – "Data Modeling" – "Generate SQL code" to open the dialog box that generates SQL.

"Figure 13"
Once set up, click Build, you can generate a complete SQL table statement.

 

The following are the effects of code generation.

-
CREATE DATABASE Newssystem
-Create a Category table
CREATE TABLE Register
(
ID int identity (1,1) Primary  key,
name varchar () NOT NULL
)

The above is the use of EA modeling tools, such as discrepancies, please forgive me.