Outline of Enterprise Internal training course for UML Software Modeling Technology

Recently, Sunny gave a two-day internal training on UML software modeling technology to a large Chinese enterprise over the weekend. The following is the outline of this internal training course:

Outline of the UML Software Modeling Technology Course

Course description

Comprehensive learning of UML 2. X knowledge, learn to use UML to construct the system's Demand Model and implementation model, learn to analyze and design a software system from multiple perspectives, and construct a more complete system model, learn to read and draw 13 types of UML graphics and learn to write relevant documents.

 

Course objectives

(1) Learn to correctly read and draw UML diagrams;

(2) learn to use the use case diagram, status diagram, activity diagram, and sequence diagram (Communication diagram) to construct the system requirement model; learn to use class diagrams, package diagrams, sequence diagrams, component diagrams, and deployment diagrams to construct the system implementation model;

(3) familiar with the use of mainstream modeling tools powerdesigner, and explain how to apply UML to various stages of software engineering through a large number of examples;

(4) Write relevant analysis and design documents;

(5) learn to use UML correctly and effectively in actual project development.

 

Lesson schedule

This course lasts for 2 days, with 6 lessons per day and 60 minutes per lesson.

 

Teaching Method

This course includes 70% lectures + 30% discussions and case studies, and questions and documents.

 

Course features

(1) the combination of theory and practice provides certain exercises while explaining the knowledge;

(2) combined with a large number of real instances, directly hit the actual problems encountered during development;

(3) Pay attention to actual practices, and give a brief introduction to relevant knowledge based on the practical experience of lecturers.

 

Course object

Requirement analyst, system analyst, architecture designer, Development Engineer, etc.

 

Student Basics

Requires a certain degree of analysis, design or programming experience.

 

Course outline (including questions, discussions and exercises)

I. course introduction and lecturer Introduction

Ii. UML Overview

1. The Birth and Development of UML

2. UML structure Overview: describes four types of models, five views, and 13 types of diagrams in uml2.x to form an overall understanding of UML.

3. Characteristics of UML

Iii. UML core knowledge

1. Build a Demand Model

(1) Use Cases to express the functional requirements of the System

(2) correctly identifying executors and use cases in the system

(3) granularity of control cases

(4) business cases, concept cases, and system Cases

(5) Writing case documents (Use Case conventions)

(6) Check the use case model

(7) Use a status chart to capture and describe the object state (cross-Use Cases)

(8) use activity diagrams to describe business processes (cross-use cases) and use case paths

(9) Use a sequence chart to represent interactions between executors, use cases, and Business Objects

(10) Use powerdesigner to draw the use case diagram, state diagram, activity diagram, and Sequence Diagram for requirement modeling.

2. Build an implementation model

(1) Use a class chart to describe the static structure of the system

(2) understand the meaning, representation, and implementation of various relationships in the class graph

(3) concept layer class diagram, description layer class diagram, and Implementation Layer class diagram

(4) practical experience in class modeling

(5) boundary, control, and Entity

(6) Use a package chart to describe the relationship between element organizational structures

(7) Hierarchical Architecture Design Using class charts and package charts

(8) Use a sequence chart to represent interaction between object instances

(9) Use a component diagram to describe the component location of each function and the relationship between them.

(10) Use a deployment diagram to describe the hardware locations where each component of the software resides and the interaction between the hardware.

(11) using powerdesigner for forward engineering and Reverse Engineering

(12) Use powerdesigner to draw class diagrams, package diagrams, component diagrams, and deployment Diagrams

Iv. UML supplementary knowledge

1. Use an object graph to describe the relationship between class instances

2. Use a composite structure diagram to describe some class structures that contain complex members or internal classes

3. Use a communication diagram to describe the connections between objects and the messages sent and received between them.

4. accurately describe the order of messages using the timeline with a digital scale in the timing chart

5. Use the interaction overview diagram to refine some specific activities in the activity diagram.

6. How to Use communication graphs and class graphs to build Domain Models

7. Use powerdesigner to draw an object diagram, composite structure diagram, communication diagram, and interaction overview Diagram

8. Common UML extension mechanisms and Applications

V. Comprehensive instance analysis and UML Summary

1. Comprehensive instance analysis (defect Management System (BMS)

2. Exchange and discuss UML modeling experience

3. UML Summary

 

Assessment Method

Closed exam

 

13 types of UML diagrams

Graph name	Overview	Usage Frequency
Use case diagram	Describes how users interact with the system.	★★★★★
Class Diagram	Describes the features of a class and its relationships.	★★★★★
Package Diagram	Description class hierarchy	★★★★☆
Sequence Chart	Describes the interaction between objects, with emphasis on order	★★★★☆
Status chart	Describes how an event changes the object state.	★★★☆☆
Activity diagram	Describe process behavior and concurrent Behavior	★★★☆☆
Component Diagram	Describe component structure and Connection	★★★☆☆
Deployment Diagram	Describe the deployment of components on each node and the connection between nodes	★★★☆☆
Communication Diagram	Describes the interaction between objects, focusing on Connection	★★☆☆☆
Object Graph	A snapshot of each object in the system at a time point.	★★☆☆☆
Combination Structure Diagram	Describe the decomposition of the Class Structure	★☆☆☆☆
Interaction Overview	Mixing Sequence and activity Graphs	★☆☆☆☆
Timing chart	Describes the interaction between objects, focusing on timing	★☆☆☆☆

 

 

[Author: Liu Wei (Sunny) http://blog.csdn.net/lovelion]