|
UML in Enterprise Architect (workshops)培训
|
|
班级规模及环境--热线:4008699035 手机:15921673576( 微信同号) |
每个班级的人数限3到5人,互动授课, 保障效果,小班授课。 |
上间和地点 |
上课地点:【上海】:同济大学(沪西)/新城金郡商务楼(11号线白银路站) 【深圳分部】:电影大厦(地铁一号线大剧院站)/深圳大学成教院 【北京分部】:北京中山学院/福鑫大楼 【南京分部】:金港大厦(和燕路) 【武汉分部】:佳源大厦(高新二路) 【成都分部】:领馆区1号(中和大道) 【沈阳分部】:沈阳理工大学/六宅臻品 【郑州分部】:郑州大学/锦华大厦 【石家庄分部】:河北科技大学/瑞景大厦 【广州分部】:广粮大厦 【西安分部】:协同大厦 最近开间(周末班/连续班/晚班):2018年3月18日 |
实验设备 |
◆小班教学,教学效果好 ☆注重质量☆边讲边练 ☆合格学员免费推荐工作 ★实验设备请点击这儿查看★ |
质量保障 |
1、培训过程中,如有部分内容理解不透或消化不好,可免费在以后培训班中重听; 2、课程完成后,授课老师留给学员手机和Email,保障培训效果,免费提供半年的技术支持。 3、培训合格学员可享受免费推荐就业机会。☆合格学员免费颁发相关工程师等资格证书,提升职业资质。专注高端技术培训15年,曙海学员的能力得到大家的认同,受到用人单位的广泛赞誉,曙海的证书受到广泛认可。 |
部份程大纲 |
|
- Create and configure EAP file
Create and save an Enterprise Architect project file
Types of views
Program interface: menus, toolbars, Toolbox, Project Browser and other windows
Docking and hiding windows
Working with a model, diagram
Predefined models
Packages (views) and diagrams
Adding elements to the model and diagram
Different ways of removing the items and their consequences
Saving diagrams
Requirements Management
Methods of requirements gathering
FURPS requirements categories
Requirements Diagram
Relationships between requirements
aggregation
dependency
How to improve the appearance of a diagram?
layout diagram
colour status requirements
enable / disable the package names
Create and manage a matrix relationship
Documenting requirements
HTML pages
printable version
Advanced requirement management
custom types of requirements
custom requirements status
tracking requirements
requirements documenting
Business process modeling, architecture
Activity Diagram
Compound activities
Control flows, object flows
Handling exceptions, interrupt flow
Partitions
Concurrent flows and decision-making
How to improve the appearance of a diagram?
different levels of detail
reducing the amount of detail
complexity of the process
Components and Deployment diagrams
The initial architecture of the system - logical and physical
nested components
delegation and assembly
port
interface
communication paths
Non-standard implementation of stereotypes in diagrams (OPTIONAL)
stereotypes graphic library
adding the library to the project
custom graphics stereotypes
Use Cases and their documentation
Functional requirements modeling
Scope of the system
Actors and the relationships between them
Identifying use cases
Association "actor - use case" and its properties
Relationship between use cases: include, extend, generalization
Auto numering
Use Case scenarios and activity diagrams generated based on them
Documentation generation
Document Templates
Analytical model
Class diagram on domain model level
class, method, attribute, abstract class, interface
association and its characteristics
other relationships: aggregation, composition, generalization, dependency, association class
class identyfication
Sequence Diagram
message types: asynchronous, synchronous, return
stereotypes: Boundary, Control and Entity
Static model
Class Diagram on design level
Source code generation and reverse engineering (OPTIONAL)
source code generating from the diagram
diagram generation from source code
source code and diagram synchronization
Object Diagrams
Dynamic Model
Static model verification
clarify the method signatures
verification of the class diagram
Dynamic modeling at the level of method calls (sequence diagram) based on use cases and static analysis model
How to improve the appearance of a diagram?
reducing the number of modeled scenarios
reducing the number of lifelines
avoiding complex nested blocks
hiding details
State Machine diagram (OPTIONAL)
states and sub-states
transitions between states - trigger, condition and action
internal actions (entry, do, exit)
Patterns and profiles (OPTIONAL)
"Gang of Four" patterns
Patterns defined in the project
User patterns
Importing profiles from XML files
MDA, source code (OPTIONAL)
Class Diagram to database schema transformation
SQL script generation based on class diagram
Source code generation - available options
Group work
Enterprise Architect package versioning
Differences in the versions of the project, documentation
Using a repository to store the model
Collaboration tools
|
|
|
|
|
|