Certificate Authentication

Software Development  Engineering With UML-Ben

 

Has over fourteen years’ experience of Automotive E/E system and software development

with

• Strong experience of software development for hybrid powertrain system, chassis system

and ADAS product.

• Experienced system and architect competency with a demonstrated history of working

for advanced safety products development of the automotive industry.

• Expertise skilled automotive Software design and development process, software

quality management and software function safety of ISO26262.

• Expertise skilled in Embedded Software, Motor Control, Embedded C, Java and AUTOSAR

OS.

• Expertise skilled Model-Based Software Development methodology, process and

toolchain-building, such as Matlab/Simulink/Stateflow, UML/SysML for system development

language.

• Strong experience of automotive prototype/productive control system development

for hybrid powertrain and advanced assistance driving system.

• Strong knowledge of ADAS system architectures and control strategies for single sensors

and multiple sensors.

• Strong knowledge of system requirements engineering and toolchain of development

(Polarion, Doors, Plastic, Integrity PTC).

Software Engineering with UML

On basis of model-based software design and development engineering for embedded system

with foundation, and senior level, provided by personal and company dedicated On- line/site

Consulting Services.

The training will be following topics:

November 18th, 2021

UML - Overview

• Goals of UML

• A Conceptual of Model of UML

• OO(Object-Oriented) Analysis and Design

• Role of UML in OO Design

UML- Basic Notations

• Class Notation

• Object Notation

• Interface Notation

• Collaboration Notation

• Use Case Notation• Actor Notation

• Initial State Notation

• Final State Notation

• Active Class Notation

• Component Notation

• Note Notation

• Interaction Notation

• State Machine Notation

• Package Notation

• Note Notation

• Dependency Notation

• Generalization Notation

• Extensibility Notation

User-Case Diagram

• Purpose of User Case Diagram

• How to Draw a User Case Diagram

• Where to Use User Case Diagrams

• Case Study:

UML – Standard Diagram

• Structure Diagrams

• Behavior Diagrams

UML – Class Diagram

• Purpose of Class Diagram

• How to Draw a Class Diagram

• Where to Use Class Diagrams

• Case Study

UML – Object Diagram

• Purpose of Object Diagrams

• How to Draw an Object Diagram

• Where to Use Object Diagrams

• Case Study

November 19th, 2021

UML – Component Diagram

• Purpose of Component Diagrams

• How to Draw a Component Diagram

• Where to Use Component Diagrams

• Case Study

UML – Interaction Diagram

• Purpose of Interaction Diagrams

• How to Draw a Interaction Diagram

• Where to Use Interaction Diagrams

• Case Study

UML – State-chart Diagram

• Purpose of State-chart Diagrams

• How to Draw a State-chart Diagram

• Where to Use State-chart Diagrams

• Case Study

UML – Activity Diagram

• Purpose of Activity Diagrams

• How to Draw a Activity Diagram

• Where to Use Activity Diagrams• Case Study

UML – Package Diagram

• Purpose of Package Diagrams

• How to Draw a Package Diagram

• Where to Use Package Diagrams

• Case Study

Conclusion

 Steps of the system analysis and design processes by UML modeling language

Patterns for ensuring traceability between requirements and the software code

Testing requirements on the system modeling architecture

Notice: The above training-mentoring sessions are conducted interactively using Requirement

Engineering and Modeling tools in order to ensure good level of traceability between

requirements and underlying solutions. Concepts are explained first using basic examples and

are then followed by solution drafts to your own issues. After this session, we can accompany

you by reviewing and validating your solutions depending on your needs.