Course Outline

Best Practices

  • Software crisis
  • Best Practices in Software Development
    • Iterative development
    • Management requirements
    • Component-based architecture
    • Visual modeling
    • Verification of quality
    • Change management

RUP

  • Characteristics of RUP
  • Two dimensions of RUP
  • UML for RUP

Create an object model

  • UML 2 as a way to represent the model
    • The object model
    • Methods of describing the model
  • Practical analysis of the specification of the use cases
    • Actor
    • A use case
    • Association
    • Relations include, extend

Some object-oriented concepts in practice

  • Abstraction
  • Encapsulation
  • Generalization
  • Polymorphism

The system architecture

  • Mapping the structure and behavior of the system
    • Two categories of UML diagrams
    • Modeling the relationship between structure and behavior
    • Different levels of modeling behavior
  • Mapping class analytical design elements
    • Relations refine
    • Building strong relationships between the results of the analysis phase and the design phase
  • Modeling design classes
    • Class
    • Association
    • Enumeration
    • Forward/reverse engineering
  • Subsystem Design
    • Component
    • The relationship of the delegation
    • Connector Assembly
  • Description of the aspects of concurrency in the system architecture
    • Examples of activity diagrams, sequence and state machine
  • Description of the aspects of the architecture of the dispersion
  • The different perspectives of architecture description

Requirements

Basic knowledge of the commonly used UML diagrams (use case, class, sequence).

 21 Hours

Number of participants


Price per participant

Testimonials (5)

Related Categories