CIT Dept @ UPES | Sept 2013 | Unified Modeling Language - UML.

23
CIT Dept @ UPES | Sept 2013 | Unified Modeling Language - UML

Transcript of CIT Dept @ UPES | Sept 2013 | Unified Modeling Language - UML.

CIT Dept @ UPES | Sept 2013 |

Unified Modeling Language - UML

CIT Dept @ UPES | Sept 2013 |

For UML Logo website. http://uml.web.id/wp-content/uploads/2011/12/UML_logo.gif

CIT Dept @ UPES | Sept 2013 |

Unified Modeling Language - UML

• Unified Modeling Language (UML) is a standardized, general-purpose modeling language in the field of software engineering.

• UML includes a set of graphic notation techniques to create visual models of object-oriented software-intensive systems

• It was developed by Grady Booch, Ivar Jacobson and James Rumbaugh at Rational Software in the 1990s.

CIT Dept @ UPES | Sept 2013 |

Unified Modeling Language - UML

• It was adopted by the Object Management Group (OMG) in 1997, and has been managed by this organization ever since.

• In 2000 the Unified Modeling Language was accepted by the International Organization for Standardization (ISO) as industry standard for modeling software-intensive systems.

CIT Dept @ UPES | Sept 2013 |

Unified Modeling Language - UML

• Unified Modeling Language (UML) combines techniques from data modeling (entity relationship diagrams), business modeling (work flows), object modeling, and component modeling.

• It can be used with all processes, throughout the software development life cycle, and across different implementation technologies.

CIT Dept @ UPES | Sept 2013 |

• The Unified Modeling Language (UML) offers a standard way to visualize a system's architectural blueprints, including elements such as:

activities actors business processes database schemas (logical) components algorithms reusable software components.

Unified Modeling Language - UML

CIT Dept @ UPES | Sept 2013 |

Object Modeling Techniques (OMT)

CIT Dept @ UPES | Sept 2013 |

Object Modeling Techniques (OMT)

• OMT was developed by Rumbaugh in 1991 and it as an approach to software development. The purposes of modeling are:

testing physical entities before building them (simulation),

communication with customers, visualization (alternative presentation of information),

and reduction of complexity.

CIT Dept @ UPES | Sept 2013 |

OMT Models• Object Model• Dynamic Model• Functional Model

CIT Dept @ UPES | Sept 2013 |

OMT- Object Model• The object model represents the static and most

stable phenomena in the modeled domain.• Main concepts are classes and associations with

attributes and operations. • Aggregation and generalization (with multiple

inheritance) are predefined relationships.

CIT Dept @ UPES | Sept 2013 |

OMT- Dynamic Model• The dynamic model represents a state/transition

view on the model. • Main concepts are states, transitions between

states, and events to trigger transitions. • Actions can be modeled as occurring within

states. • Generalization and aggregation (concurrency)

are predefined relationships.

CIT Dept @ UPES | Sept 2013 |

OMT- Functional Model• The functional model handles the process

perspective of the model, corresponding roughly to data flow diagrams.

• Main concepts are process, data store, data flow, and actors

CIT Dept @ UPES | Sept 2013 |

Difference between the UML model and the set of diagrams of a system

CIT Dept @ UPES | Sept 2013 |

UML Model <vs> Other Diagrams

• It is important to distinguish between the UML model and the set of diagrams of a system.

• A diagram is a partial graphic representation of a system's model.

• The model also contains documentation that drives the model elements and diagrams (such as written use cases).

CIT Dept @ UPES | Sept 2013 |

UML Model• Unified Modeling Language (UML) Models

represent systems at different levels of detail. Some models describe a system from a higher, more abstract level, while other models provide greater detail.

• UML models contain model elements, such as actors, use cases, classes, and packages, and one or more diagrams that show a specific perspective of a system.

CIT Dept @ UPES | Sept 2013 |

UML Model• A model can also contain other, more

detailed models.

CIT Dept @ UPES | Sept 2013 |

UML Model• You can use modeling diagrams to capture

system use cases in a use-case model during the requirements gathering phase.

• you define the application domain in an analysis model during the system analysis phase, and you refine the application model in a design model during the detailed design phase.

CIT Dept @ UPES | Sept 2013 |

• There are three important type of UML modelings:– Structural Modeling– Behavioral Modeling– Architectural Modeling

CIT Dept @ UPES | Sept 2013 |

Structural Modeling• Structural modeling captures the static

features of a system..• It consists of..

₪Classes diagrams₪Objects diagrams₪Deployment diagrams₪Package diagrams₪Composite structure diagram₪Component diagram

CIT Dept @ UPES | Sept 2013 |

Behavioral Modeling• Behavioral model describes the interaction

in the system.• It represents the interaction among the

structural diagrams.• Behavioral modeling shows the dynamic

nature of the system.

CIT Dept @ UPES | Sept 2013 |

Behavioral Modeling• It consist of the following:

Activity diagramsInteraction diagramsUse case diagrams

CIT Dept @ UPES | Sept 2013 |

Architectural Modeling• Architectural model represents the overall

framework of the system. • It contains both structural and behavioral

elements of the system. • Architectural model can be defined as the

blue print of the entire system. • Package diagram comes under

architectural modeling.

CIT Dept @ UPES | Sept 2013 |

Reference Web Link www.safaribooksonline.com

• http://my.safaribooksonline.com/book/software-engineering-and-development/9780750661232/front-cover/cover