You are on page 1of 53

@SakaHeroji

Object Oriented Analysis Design Behind The Truth


Saka Heroji You cant manage what you cant measure

@SakaHeroji Object Oriented Analysis Design Workflow

@SakaHeroji

An Example

BANKING APPLICATION

@SakaHeroji

1st Step

ESTABLISHED USE-CASE

@SakaHeroji

1st: Established Use Case


Analyze requirement and user relationship

@SakaHeroji

1st: Established Use Case

@SakaHeroji

2nd Step

USE CASE REALIZATION WITH ACTIVITY DIAGRAM, CONCEPTUAL CLASS & SEQUENCE DIAGRAM

2nd: Use case realization with Activity Diagram

@SakaHeroji

@SakaHeroji

2nd: Breaking Down Activity Diagram

@SakaHeroji

2nd: Construct Conceptual Class


Construct Object Name First!

@SakaHeroji

2nd: Construct Conceptual Class


Construct its attributes! Construct general method and setter getter!

@SakaHeroji

2nd: Construct Conceptual Class


Construct Class Relationship Types

@SakaHeroji

2nd Step Class Relationship

CLASS DIAGRAM RELATIONSHIP TYPE

@SakaHeroji

2nd: Association Relationship

Object Person using Object Car to access its function in Person function or the other hand

@SakaHeroji

2nd: Direct Association Relationship

Object Person using Object Car to access its function in Person function not the other hand

2nd: Composition / Aggregation Relationship

@SakaHeroji

2nd: A Core Conceptual Class Open Account Use Case

@SakaHeroji

@SakaHeroji

2nd Step

CONSTRUCT SEQUENCE DIAGRAM

@SakaHeroji

2nd: Before Sequence Diagram


Every use case has a CONTROLLER CLASS Its Function to Connect to Core Class Relationship between Core Class and Controller Class ALWAYS Directed Association

@SakaHeroji

2nd: Revise Conceptual Class

@SakaHeroji

2nd: Create Sequence Diagram


Process flow must based on Activity Diagram Object used: Actor, UI, Conceptual Class

@SakaHeroji

2nd: Create Sequence Diagram

@SakaHeroji

2nd: Create a Sequence Diagram

@SakaHeroji

2nd: Create a Sequence Diagram

@SakaHeroji

@SakaHeroji

2nd: Revise your Class Diagram

@SakaHeroji

2nd: Revise your class diagram

@SakaHeroji

3rd Step

CODE IMPLEMENTATION

@SakaHeroji

Rules Implementation
Code must be implement based on UML Implement to suitable Technology

@SakaHeroji

3rd: Implementation

@SakaHeroji

3rd: Implementation

@SakaHeroji

3rd: Implementation

@SakaHeroji

3rd: Implementation

@SakaHeroji

3rd: Implementation

@SakaHeroji

4th Step

EVALUATION

@SakaHeroji

Evaluation Types
Evaluation By Code Testing Evaluation By Performance Evaluation By IMK Questionnaire

@SakaHeroji

Code Testing: Cohesion and Coupling

@SakaHeroji

Code Testing: Cohesion & Coupling

@SakaHeroji

Metric Plugin for Java


Eclipse Metric Plugin CodePro Analitix from Google

@SakaHeroji

Eclipse Metric

@SakaHeroji

Eclipse Metric

@SakaHeroji

CodePro Analytix
Made from Google Integrated with Eclipse Plugin

@SakaHeroji

CodePro Analytix

@SakaHeroji

CodePro Analitix

@SakaHeroji

Code Pro Analitix

@SakaHeroji

Code Pro Analitix

@SakaHeroji

Evaluation By Performance
PageSpeed Yslow Embedded with Firebug

@SakaHeroji

PageSpeed

@SakaHeroji

PageSpeed

@SakaHeroji

YSlow

@SakaHeroji

YSlow

@SakaHeroji

YSlow

@SakaHeroji

Follow me @SakaHeroji

THANK YOU

You might also like