 |
Object Oriented Analysis And Design with UML |
 |
| Syllabus for Object Oriented Analysis and Design part1 |
Module 1:UML and modeling Process
• Module 1.1: The Unified Modeling Language
• Module 1.2: Process and visual Modeling
• Module 1.3: Analysis & Design Key concepts
Module 2: Conceptof Object Orientation
• Module 2.1: Relationship
• Module 2.2: Class
• Module 2.3: Polymorphism
• Module 2.4: Interface
• Module 2.4.1: Provided
• Module 2.4.2: Required
• Module 2.5: Structured classesand ports.
Module 3: Architectural Analysis
• Module 3.1: Key Concepts
• Module 3.2:Define high-level organization of themodel.
• Module 3.3: Identify analysismechanism
• Module 3.4:Identify key abstractions
• Module 3.5:Create use-case realization.
Module 4: Use case Analysis
• Module 4.1: Supplement the Usecase Realization
• Module 4.2:For Each Use caserealization
• Module 4.2.1:Find Classes from Usecase Behavior
• Module 4.2.2:Distribute Use case behavior toclasses
• Module 4.3: For eachresulting analysis class
• Module 4.3.1: DescribeResponsibilities
• Module 4.3.2:Describe attributes and associations
• Module 4.3.3: Qualify Analysismechanisms
• Module 4.4:Unify analysisclasses.
|
| Object Oriented Analysis & Design Part 2 |
Module1.1: Persistent Data Base Cater
• Module1.1: Identify classes and Sub systems
• Module 1.2: Identify subsystems Interfaces
• Module 1.3 Update the organization of the Design Models
Module2: Identify Design Mechanism
• Module 2.1: Categorize clients of analysis mechanism
• Module2.2 Document architectural Mechanism
Module 3: Distribution
• Module 3.1: Define the network configuration
• Module 3.2: Allocate processes to node.
• Module 3.3: Define the Distribution mechanism
Module 4: Use case Design
• Module 4.1: Describe interaction among design objects
• Module 4.2: simplify sequence diagram using subsystems
• Module 4.3: Describe persistence-related behavior
• Module 4.4: Refine the flow of events description
• Module 4.5: Unify classes and subsystems
Module 5: Subsystem Design
• Module 5.1: Distribute subsystem behavior to subsystem elements.
• Module 5.2: document subsystem elements
• Module 5.3: Describe subsystem dependencies
Module 6: Class Design
• Module 6.1: Create Initial Design Classes
• Module 6.2: Define Operations
• Module 6.3: Define methods
• Module 6.4: Define States
• Module 6.5: Define Attributes
• Module 6.6: Define Dependencies
• Module 6.7: Define Associations
• Module 6.8: Define Internal Structure
• Module 6.9: Define Gene rationalizations s
• Module 6.10: Resolve use-Case Collisions
• Module 6.11: Handle Nonfunctional Requirements in General
|
|
|
|
