UML

Oregon Health & Science University
Beaverton, Oregon, United States

Course Format: Classroom | E-learning | Virtual Class | Online | On-site | Blended | Self-paced

Course Description:

'' This course provides engineers, programmers, software developers and testers with basic, practical knowledge that will enable them to identify and prepare meaningful views of their system using the Unified Modeling Language (UML) diagrams and notation. We’ll use the last version, UML 2.0, which includes some powerful and expressive additions.

After a brief introduction to a basic development process we’ll walk through the most common UML diagrams and show how together they can represent a design model of a software system. We’ll explore how UML can be effectively used for rough sketches as part of design discussions as well part of more permanent documentation or presentations. This course is focused on the practical application of UML to effectively communicate design ideas.

Training Philosophy

Students learn by doing. There is enough class-time to explore concepts and techniques and develop basic skills. Class is roughly 80% lecture and 20% exercises followed by review.

Each learning cycle lasts between one and two hours, and consists of:

an interactive lecture which illustrates and motivates each diagram and presents effective techniques for representing design ideas

a review of some finer points on how it is best used

quick exercises to reinforce new skills and/or short discussions
Although we will mention various open source, shareware and commercial UML modeling tools, this is a pencil-and-paper based class which will focus on effective diagramming techniques instead of tool usage.

Who Should Attend:

This course is suited for developers, sw designers, testers, sw architects and those who need to understand what they produce (analysts and/or managers), and anyone wanting to know about the latest UML 2.0 features.

Course Outline

I. A brief overview of a design process

Defining system behavior at a high level with use cases and/or activity diagrams

Designing the system and representing its structure and operation

Presenting relevant views of a system’s architecture and design
II. An Introduction to UML

What it is

What is it good for and what are its limitations

The difference between a design and an implementation view of a system
III. Common UML diagrams

Activity diagrams

Sequence diagrams

Class diagrams

Component diagrams

State diagrams

Other UML diagrams: communication, use case, deployment
At the end of the course, students should be able to:

Draw an activity diagram to represent processing steps and actions. Skills include:

Use of swimlanes to show the division of activities among elements, actors and/or subsystems

Representing optional actions, branching, and decisions

Layout options
Draw a sequence diagram that represents an interaction among design elements. Skills include the ability to:

Represent objects that are instances of particular classes and components

Effectively arrange the elements of a diagram

Represent and label return values

Show optional, conditional, and repeated actions

Show object creation and destruction

Break a complex action down into one or more diagrams, and

Link one diagram to another
Create and interpret class diagrams. Skills include knowing how to:

Read and interpret class diagrams

Represent abstract and concrete classes, and interfaces

Represent attributes and operations and access rights

Indicate relationships between classes, cardinality, and visibility between classes

Show/hide details
Draw a component diagram representing major system elements and their relationships. Skills include:

Basic conventions for drawing components

Labeling and showing key properties using stereotypes, tags, and notes

Showing component dependencies and interactions
State diagrams representing complex processing. Skills include:

Creating basic elements of a state diagram: initial and ending conditions, states, transitions and guards

Apply several cross-checks to verify that UML diagrams are in synch and convey what was intended

Prerequisites

Students must be familiar will object technology and some modeling, but this does not require prior working experience. It is suited for developers, sw designers, testers, sw architects and those who need to understand what they produce (analysts and/or managers).
...''

Phone:(503) 748-1121

School Address:

Center for Professional Development
OGI School of Science & Engineering
20000 NW Walker Road
Beaverton, OR 97006 USA

Jobs & Resumes: Beaverton
Houses & Roommates: Beaverton

Programming with Microsoft .NET Framework (C# .NET)
Optimizing Oracle SQL, Intensive
Agile Project Planning with Scrum
AJAX Development with .NET
.NET Debugging
Developing Web Applications with ASP.NET 2.0
Perl
Engineering Software Quality
Developing Web Service Clients with Java

Notice: The course description on this page was captured from the Internet as historical reference or submitted by visitors. It was archived statically and not updated from day to day.
 

Tips: Schools can use this unlimited free web marketing service by submitting their course descriptions and school introductions. Two outbound links will be granted to each posting.