Data Modeling with PowerDesigner 12

Course Overview

In this course, you will first learn the basics of Object-Oriented programming, Systems Architectures, OOA&D approaches and UML. Many of these concepts are put into practice throughout the tool, thus making these fundamental concepts a pre-requisite for success in implementing the product.

You will then use the PowerDesigner IDE to create Object-Oriented models by using a case study through which you will work as a group with other students in your class - modeling a solution to a set of provided requirements. The class will take turns ?driving? the PowerDesigner product during the lab sessions in order to gain hands-on experience. There is no right-or-wrong answer for the labs, they will depend on class interaction and decisions. The instructor will be the consultant, the mentor, the tie-breaker. A possible solution will be provided by Sybase.

Explore how PowerDesigner implements the Unified Modeling Language (UML). The courseware will provide high-level design requirements to start, allowing you to experience a "real world" approach to Object Oriented Analysis and Design (OOAD). You and your class will be formulating the detailed requirements and designing the system in a team environment, including taking the design to its final stages where the model is forward engineered into live code.

You will either use PowerBuilder, C# or Java as the language of choice, once you enter into the concrete modeling phases. This is not a programming class. The main focus will be on modeling an application's Business Logic or Problem Domain. There will be no end-to-end solution created. There will be no testing of a "final" product, since OO modeling does not encompass GUI aspects.

Audience

This course is designed for individuals who are responsible for designing, implementing, and managing relational databases, including: Experienced data analysts, Object-oriented software developers and Object architects.

Skills Gained

Upon completion of this course, you will be able to:
• Approach object-oriented analysis and design from the appropriate perspective
• Use and interpret UML class model notation
• Collect information relevant to the development of class diagrams
• Create and interpret UML use-case and sequence diagrams
• Create and manage object-oriented models
• Generate: conceptual and physical data models, Java and PowerBuilder objects
• Reverse engineer Java and PowerBuilder code

Prerequisites

• Knowledge of basic object-oriented concepts and relational database concepts
• Exposure to entity relationship (ER) data modeling and data normalization
• Knowledge of object-oriented programming language (PowerBuilder, C#, Java, etc.) and methodologies

Course Outline

Basic Object-Oriented Concepts Explained

• Classes defined
• Attributes (Properties)
• Operations (Methods)
• Enums
• Exceptions
• Special types of classes
• Interfaces
• Packaging classes
• Classes versus Objects
• Object-Oriented Programming Defined
• Encapsulation
• Inheritance
• Polymorphism

Systems Architectures

• Two-tier development review
• N-tier (Distributed) development challenges
• Partitioning your applications
• Application Layers

Object-Oriented Analysis and Design (OOA&D)

• Analysis processes
• Design processes
• Iterations
• Methodologies
• Background
• Types of diagrams
• Key Notation (per diagram type)
• Stereotypes

Introduction to the PowerDesigner IDE

• Origins of the product
• Overall product capabilities
• Brief look at Physical Data Modeling
• Intro to Object Modeling
• Navigating the IDE

Test Case - Order Entry System

• Lay out facts of system requirements
• Create initial Domain Model from assigned Test Case (as a team)
• Identify classes making up the Problem Domain
• Very High Level

Use Cases (as a team)

• Introduction
• Define Actors (initiators and receivers)
• Define Use Cases
• Create Use Case Diagram
• Create Use Case Specification
• Relationships in Use Cases (Stereotypes)
• Refine domain model (2nd iteration)
• Creating new classes in the Use Case diagram

Sequence Diagrams (as a team)

• Introduction
• Components of a sequence diagram
• Create a sequence diagram
• Versus Activity Diagrams
• Outcome: refined Domain Model (3rd iteration)
• Class Diagrams (as a team)
• Basics

Advanced concepts

• Packages
• Accessing Frameworks
• Shortcuts
• Replicas
• Relationships
• Generalisation and Overriding operations (the process)
• Interfaces
• Stereotypes
• Abstract, Final
• Modeling Inner classes
• Some check models in here to achieve model accuracy
• Extended model definitions that stop some of the above?
• Outcome: refined Domain Model (5th iteration)

Generation options

• Generating code from the Model
• Reverse engineering of code into a Model
• Generating other models from the OOM

Reporting Options

• Provided templates
• Customising templates
• HTML or RFT output
• Repository
• Defined
• Use

Advanced PowerDesigner Topics

• Impact Analysis
• Comparing Models
• Merging Models
• Basic Extended Model Definitions
• Modeling Web Applications (ASP/JSP)
• Requirements Model

Miscellaneous Topics

• Creation of JavaDoc
• Integration with PowerBuilder, Visual Studio, Eclipse
• XML Modeling
• Web Service Modeling