Object Oriented Analysis and Design using UML
Service Times: 9am and 10:30am
6399 North Wells Road, Bigtownville, CO 32748
  • Loading

Object Oriented Analysis and Design using UML

Email Print Export to ical format


Academy of Management & Science (AMS)
House # 89/E, Road # 13/C, Block # E, Banani, Dhaka 1213, Bangladesh
Telephone: +880 (2) 9891190, +880 (2) 8836875, Cell No: (88) 01680878839, (88) 01193070284

Who Can Attend

Software Architecture, design & Development professionals, Software QA Professionals, Software Engineer.


An exercise follows each topic to illustrate the concepts covered. An additional case study at the end ties the individual topics together and reinforces the learning.

Exercises are done in small groups, providing the chance to learn from each other and to fully explore the range and implications of each topic.

Pen and paper are used for the exercises, rather than a case tool. This ensures that the

Object Oriented Analysis and Design using UML


4 Days (32 Hours)

Course Objectives:

Abstraction and modularity are the best “tools” that we have to manage the complexity of the systems we develop. Object-orientation is the next step in the evolution of these tools. The SOLID principles are introduced to highlight good OO practices.

Course Details:


  • Software Engineering Concepts
  • Software development life-cycle
  • Major schools: application development methodologies

Object-oriented concepts

  • Object, class
  • Object behaviour and methods
  • Inheritance and aggregation
  • Polymorphism
  • Object model

The Unified Modelling Language

  • Use Cases and System Analysis
  • A Process for Modelling

Object and Class Workshop
Object Relationships

Associations and Links - Navigability and Naming - Multiplicity and Other Adornments - Association Classes and N-arys - Aggregation and Composition

Object Relationship Workshop
The Unified Process

  • The object-oriented software life cycle
  • Use case-driven and architecture-centric features
  • Iterative and incremental development
  • Performing requirements analysis

The UML is a formal means to represent a design. It is not a process to discover that design, merely a way to formally document it. The various diagram styles of the UML provide different views of the design.

B4 is a technique that helps identify requirements. Use cases and/or user stories focus requirements from a user's perspective without getting caught up with the internal system implementation.

UML Class Design

  • UML Class Notation
  • Attributes, operations and access visibility
  • Interfaces and stereotypes
  • Relationships, aggregation, composition, dependency
  • Designing with class diagrams

High-Level dynamic modeling
Activity diagrams are a powerful means to model the steps and behaviour of an implementation at a high level.

Low-level dynamic modeling
Sequence and communication diagrams model the internal behaviour in terms of interactions between objects. Applying the stereotypes of boundary, controller and entity aid this process.

Low-level structural modeling
Class diagrams model the static structure of the system. It is the primary input to the developer. This structure can be largely derived from the dynamic model.

State machines
State machine diagrams model how the behaviour of an individual object (based on its class) changes over its lifetime according to the “state” it is in. This model provides verification of the dynamic and structural models against the requirements while providing implementation information for the developer.

Database modeling
While class diagrams model the class/object structure in the computer's memory, entity-relationship (ER) diagrams model the structure of the database, the persistent repository of the information used by the objects. Relational databases have no basis in object-oriented concepts, so various techniques are required to map an object-oriented model to a relational database.

Every class needs to be specified in terms of its attributes and operations and also its relationships to other classes. Refactoring may also be required to ensure that the Single-Responsibility and Interface-Segregation principles are followed and to address various qualitative requirements.

Inheritance and polymorphism
These techniques provide a lot of power, particularly in the form of the Open-Closure and Dependency-Inversion principles. However, there are caveats to their use, such as the Liskov-Substitution principle.

High-level structural modeling
Larger systems require a higher-level structure that manages the low-level classes. Package diagrams provide a means to model that structure, but also impose constraints on the design.

Architecture, Components and Implementation Diagrams:
Larger systems are more susceptible to the problem of software entropy over the lifetime of the system. More up-front design is then needed to anticipate the sorts of issues that will be faced and ensure that the quality of the system is maintained. Multiple perspectives of the system are required in order to manage the complexity. This architectural work is not externally visible and has no obvious business value, yet neglecting this leads to technical debt that will need to be repaid in the future.

Packages and Dependencies - Stereotypes - Control Objects - Layered Architectures - Interfaces, Subsystems and Components - Task Modelling - Component Diagrams - Deployment Diagrams

System Architecture Workshop
Class Relationships and Inheritance
Class Similarities and Differences - Generalisation Syntax - Generalisation Hierarchies - Multiple Inheritance - Polymorphism - Generalisation Versus Interface - Class Dependency

Generalisation Workshop
Design Patterns
Reflexive Aggregate - Collection Class - Observer - State Machine - Meta-Model - Modelling Patterns

Design Patterns Workshop
Detailed Design
Subsystem Design - Architectural Mechanisms - Linking to Libraries and Frameworks - Visibility and Other Properties - Completing the Model - Incremental Development - Traceability and Review 

Detailed Design Workshop
Case Study & Tools

  • Case study using UML
  • Analysis View
  • Design View
  • UML Tools
  • Code Generation and Reverse Engineering

Training Calendar

<<  October  2017  >>
 S  M  T  W  T  F  S 
  1  2  3  4  5  6  7
  8  91011121314


AMS Campus Facilities

  • Two Air conditioned seminar halls with projector & audio system [Maximum Capacity up to 50 persons] including video recording capacity.
  • Two different PC Labs (Air conditioned)
  • Centralized server
  • Internet / WIFI facilities
  • Practice facilities in LABS
  • Online Exam Centre
  • Cafeteria & Own cook facility
  • Large lobby with natural surroundings
  • Huge Parking Space
  • Waiting Lounge
  • Distance education facilities
  • Printer, Scanner etc logistics facilities
  • Special Guest Room
  • Registration Booth Arrangement Space
  • 3 Star Accommodation arrangements for foreign guests on demand in walking distance from the center.
    ………and many more

Contact AMS

Academy of Management & Science (AMS)
House #450, Road # 31, New DOHS,Mohakhali, Dhaka-1206, Bangladesh
Cell No: (88) 01616004108
Email: This email address is being protected from spambots. You need JavaScript enabled to view it.

Academy Location