A. EA Self Introduction
EA (Enterprise Architect) life cycle software design, Enterprise Architect is a full-featured, UML-based visual
Case tool, a goal-oriented software system that covers the entire cycle of system development, in addition to the development of class models, also includes the process of
Analysis, use case requirements, dynamic models, components and layouts, system management, non-functional requirements, user interface design, testing and maintenance.
Rational Rose is a standard, and the EA is characterized by fast drawing, documentation, high performance, and good flexibility. Unified Modeling language can be built in a consistent manner
Robust and traceable software system model, while the EA provides an easy-to-use and fast-flexible working environment for the build process.
The EA includes:
1. Structure chart: Class, object, composition element, package, component, layout;
2. Behavior Chart: Use case, communication, sequence, interaction overview, behavior, status, timing;
3. Expansion: Analysis (simple behavior), customization (requirements, changes, and UI design). Establish engineering
two. Engineering Establishment
1. Engineering Establishment
You can-à "new project" in "File"
Or in the "Manage Project"-create a new Projet
2.UML Build
After the new project is saved to the local disk, the "Select Model" pops up and the selection model is divided into three categories----common,simple,unifledprocess when I
When building a UML diagram, you can choose the type in simple.
Business Process |
Business process |
Requirements |
Demand analysis |
Use case |
Case |
Domain Model |
Domain model |
Class |
Class design |
Database |
Database design |
Component |
Component |
Deployment |
Deployment |
Testing |
Test |
Maintenance |
Maintenance |
Project Management |
Project Management |
User Interface |
User interface |
After you select Use Case view, a use Case view appears below the model package in the project browser.
Class Model:
Class Elements |
Package |
Package |
Class |
Class |
Interface |
Interface |
Enumeration |
Enumeration |
Table |
Table |
Signal |
Description of the object communication signal |
Association |
Association |
Class Relationships |
Associate |
Realize |
Generalize |
Generalization |
Compose |
Composition |
Associate Class |
Association classes |
Assembly |
Assembly |
Realize |
Realize |
Nesting |
Nesting |
Package Merge |
Consolidation of Packages |
Package Import |
Import of packages |
Common |
Note |
Comments |
Constraint |
Constraint conditions |
Document |
Documents: Attaching document Attachments |
Artifact |
Manual: Any block of information representing arbitrary systems |
Requirement |
Requirements Description |
Issue |
Problem description |
Change |
Change description |
Boundary |
Boundary |
Dependency |
Dependent relationships |
Realize |
Realize |
Trace |
Tracking |
Information Flow |
Data flow |
Note Link |
Comment Link |
Class diagram, time series diagram, activity diagram ... Are created in the same way that is not introduced here.
3. Settings
(1) Role property settings
(2) Use Case property settings
(3) property settings for class diagrams:
(4) method settings for Class
(5) Variable setting
(6) Property settings
4. Common buttons in the project browser
(1.) re-select the model
(2.) New Package
(3.) New Component
(4.) Create a new chart