Please enable JavaScript.

Coggle requires JavaScript to display documents.

4+1 View Model (Logical View (Class Diagrams (Purpose (Shows static…

- - - - Shows static structure of classifiers in a system
      - Helpful for developers and other team members too
      - Business Analysts can use class diagrams to model systems from business perspective.
    - - Class Operations
        
        (+) Public
        
        (-) Private
        
        (#) Protected
        
        (~) Package
      - Class Relationships Type
        
        Inheritance (or Generalization): Represents an "is-a" relationship.
        
        Simple Association: A structural link between two peer classes.
        
        Aggregation: A special type of association. It represents a "part of" relationship
        
        Composition: A special type of aggregation where parts are destroyed when the whole is destroyed.
        
        Dependency: Exists between two classes if changes to the definition of one may cause changes to the other.
      - Relationship - Roles
        
        A role is a directional purpose of an association.
        
        Roles are written at the ends of an association line and describe the purpose played by that class in the relationship.
  - - - During the analysis phase of a project, You might create a class diagram to describe the structure of a system and then create a set of object diagrams as test cases to verify the accuracy and completeness of the class diagram.
      - Before you create a class diagram, You might create an object diagram to discover facts about specific model elements and their links, or to illustrate specific examples of the classifiers that are required.
  - - - Show internal structure of a classifier - internal structure diagram,
      - Show classifier interactions with environment through ports
      - Show a behavior of a collaboration - collaboration use diagram
- - - - The top and the bottom of the rectangle are aligned with the initiation and the completion time respectively.
      - In communication diagram focus of control is explicit and thus, can be represented by the message nest numbering.
    - - Support the identification of objects (hence classes), and their attributes (parameters of message) and operations (messages) that participate in use cases
      - Model message passing between objects or roles that deliver the functionalities of use cases and operations
      - Model mechanisms within the architectural design of the system
      - Capture interactions that show the passed messages between objects and roles within the collaboration scenario
      - Model alternative scenarios within use cases or operations that involve the collaboration of different objects and interactions
  - - - Model high-level interaction between active objects in a system
      - Model the interaction between object instances within a collaboration that realizes a use case
      - Model the interaction between objects within a collaboration that realizes an operation
      - Either model generic interactions (showing all possible paths through the interaction) or specific instances of a interaction (showing just one path through the interaction)
    - - An actor does not necessarily represent a specific physical entity but merely a particular role of some entity
      - A person may play the role of several different actors and, conversely, a given actor may be played by multiple different person
- - - - You can describe those details in other UML diagram types and documents, and have them be linked from use cases.
      - Use cases represent only functional requirements of a system.
    - - Developed by analysts together with domain experts
      - Validate a systems architecture
      - Specify the a syscontext of tem
      - Capture the requirements of a system
      - Drive implementation and generate test cases
  - - - Avoid the appearance of false completeness and clarity
      - The simple and consistent format saves time when capturing and prioritizing requirements while remaining versatile enough to be used on large and small features alike.
      - Keep yourself expressing business value by delivering a product that the client really needs
      - Avoid introducing detail too early that would prevent design options and inappropriately lock developers into one solution.
      - Get to small enough chunks that invite negotiation and movement in the backlog
      - Leave the technical functions to the architect, developers, testers, and so on
    - - Who it is for?
      - What it expects from the system?
      - Why it is important (optional?)?
- - - - help to understand the structure of existing systems and then build new ones
      - it is used for component based system...which include constructed component that can be reused or replaced.