1 / 13

Logical view show classes and objects Process view models the executables Implementation view

Logical view show classes and objects Process view models the executables Implementation view Files, configuration and versions Deployment view Physical and computational nodes Use-case view Models the basic requirements 4+1 view. Architecture.

Télécharger la présentation

Logical view show classes and objects Process view models the executables Implementation view

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Logical view • show classes and objects • Process view • models the executables • Implementation view • Files, configuration and versions • Deployment view • Physical and computational nodes • Use-case view • Models the basic requirements • 4+1 view

  2. Architecture • Highest level concept of the system and its environment • Organizational structure of a system • Parts • Connectivity • Interaction • Mechanisms • Guiding principles

  3. UML • Program = Data + Algorithm • Software System = Objects + Messages • UML models the world as a system of interacting objects. • An object is a cohesive cluster of data and function. • UML is a visual language

  4. Object Model • Static Structure: Describes the important objects of the system and their relationships • Dynamic Behavior: Describes the lifecycles of the objects and how and when they collaborate to deliver the system functionality

  5. UML Structures • Things – modeling elements • Relationships – semantic relationship between the things • Diagrams – representing the ‘what’ and ‘how’ of the system.

  6. Things • Structural things - class, interface, collaboration, use case, active class, component, node, etc. • Behavioral things – interactions, sequence diagram, state machines • Grouping things – package • Annotations – notes, comments, etc.

  7. Relationships • Association • Dependency • Generalization • Realization (use-case)

  8. Diagrams • Class diagram • Component diagram • Deployment diagram • Object diagram • Use-case diagram • Sequence diagram • Collaboration diagram • State chart diagram • Activity diagram

  9. UML common mechanisms • Specifications – textual descriptions of the semantics of an element – Meat of the model • Without specs we just have blobs connected by lines • Specs evolve over time – and hence may be incomplete and/or inconsistent • Completeness and consistency test is applied periodically

  10. Adornments • Specs are hidden • Important details are added to model • Added only to highlight and add clarity

  11. Classifier • Abstract notion • Actor • role played by outside user • Class • description of similar objects • Classifier role • restricted classifier • Component • replaceable part of the system • Datatype

  12. Interface • collection of operations to specify a service offered by a class or a component • Node • physical, run-time element • Signal • an asynchronous message • Subsystem • grouping of elements • Use-case • sequence of actions performed to accomplish a task

  13. Instances are concrete things – taking part in the workings of the system • Interfaces – present the contract for a functionality • Various implementations can be made available to adhere to the interface. • Constraints can be added to elements • Stereotype is a tagged and/or constrained element

More Related