Get Started. It's Free
or sign up with your email address
Rocket clouds
OOAD by Mind Map: OOAD

1. Complexity

1.1. Simple

1.2. complex

1.2.1. why ?

1.2.1.1. Complexity of problem domain

1.2.1.1.1. Contradictory/competing requirements

1.2.1.1.2. impedance mismatch

1.2.1.1.3. often requirement changing

1.2.1.2. difficulties in managing SDLC

1.2.1.3. Flexibility through Software

1.2.1.4. problems in characterizing behavior of discrete systems

1.2.2. Consequences of Unrestrained complexity (Software Crisis)

1.2.2.1. Delay

1.2.2.2. Over-budget

1.2.2.3. deficient in their stated requirements

1.2.3. Structure of Complex System

1.2.3.1. Attributes

1.2.3.1.1. Hierarchic structure

1.2.3.1.2. relative Premitives

1.2.3.1.3. Separation of Concern

1.2.3.1.4. Common patterns

1.2.3.1.5. stable intermediate forms

1.2.4. Simplifying the complexity

1.2.4.1. System Analysis & Design

1.2.4.1.1. Decomposition

1.2.4.1.2. Abstraction

1.2.4.1.3. Hierarchy

2. OO Paradigm(model)

2.1. Programming Paradigm

2.1.1. Procedural Paradigm

2.1.2. OO Paradigm

3. Principal of Object Orientation

3.1. why ?

3.1.1. Modularization

3.1.2. Abstraction

3.1.3. Hierarchy

3.1.4. Encapsulation & Information Hiding

3.1.4.1. Encapsulation

3.1.4.2. information hiding

3.1.5. improved maintainability

3.2. relationship

3.2.1. class

3.2.2. object

3.2.2.1. state

3.2.2.2. behavior

3.2.2.3. identiy

3.3. Advantage

4. UML Diagrams

4.1. Structural diagram

4.1.1. Deployment diagram

4.1.2. package diagram

4.1.3. component diagram

4.1.4. class diagram

4.1.5. object diagram

4.1.6. composite structure diagram

4.2. Behavior diagram

4.2.1. Use-case diagram

4.2.1.1. Actor

4.2.1.2. use-case

4.2.1.3. interaction

4.2.1.3.1. association

4.2.1.3.2. inclusion

4.2.1.3.3. extension

4.2.1.4. System boundary

4.2.1.5. <<furtherDetails>>

4.2.1.5.1. Analyze & Design

4.2.1.5.2. specification

4.2.2. Activity diagram

4.2.2.1. Action nodes

4.2.2.2. control nodes

4.2.2.2.1. initial node

4.2.2.2.2. final node

4.2.2.2.3. decision & merge

4.2.2.2.4. fork and join

4.2.2.3. object nodes

4.2.3. State machine diagram

4.2.3.1. state

4.2.3.2. transition

4.2.4. interaction diagram

4.2.4.1. sequence diagram

4.2.4.2. interaction over-view diagram

4.2.4.3. Timing diagram

4.2.4.4. communication diagram

5. Phases in delivering a S/W

5.1. initiation

5.2. requirement gathering

5.3. specification

5.4. design

5.5. implementation

5.6. testing & integration

5.7. maintainance