Mis Final Review

10

* Things- The primary element of the UML (unified modeling language)

* Relationships- Glue that holds the things together

* Structural diagrams- Used to describe the relationship between classes

* Class

* Shows class relationships, static features only, no processing

* Classes-represented by a rectangle on the diagram

* Types of Classes

* Entity- represents real world items like people or things

* Interface-means for user to work with the system

* Abstract- linked to concrete classes in a generalization/specialization relationship

* Control-used to control the flow of activities. Example (log on process)

* Object

* Component

* Deployment

* Behavior diagrams- Used to describe the interaction between people and a use actors

* Use Case

* Describe how a system is used, doesn’t explain how the system does it

* Starting point for uml modeling

* Sequence

* Shows the sequence of Activities

* Communication Diagrams- used to show the interactions of two or more than any one of the things can do alone

* Three Layers

* Presentation Layer- what the user sees

* Business Layer-Containing the Unique rules for this application

* Persistence layer- obtaining and storing data

* Collaboration

* Statechart

* Shows the state transitions

* Activity

* Illustrates the overall flow of activities

* Usually created for one use case and may show the different possible scenarios

* Has Swimlanes- useful to show how the data must be transmitted or converted between system components

* Associations- the simplest type of relationship

* Used to break up a many-to-many association between classes

* An object in a class may have a relationship to other objects in the same class

* Whole Part...