Modeling and UML

Modeling

model is an abstraction of the system
modeling is a way to deal with complexity by ignoring irrelevant details
model is useful when sharing idea and the results of system analysis and design among clients, system analysts and programers
UML is the standard for modeling

1990s: method wars of objected-oriented paradigm
- OOAD, OMT, OOSE, Fusion, OOA/ OOD....
- each of the methods had its own notation, process and tools
Unified Method 0.8 was designed in 1995
- OOAD + OMT + OOSE ...
currently UML 2.0(2005), UML 2.5(2015) are widely used

jimin-kiim commented 1 year ago

Structure Diagrams: what things must be in the system
Behavior Diagram: what must happen in the system
Interaction Diagrams( subset of behavior diagrams): the flow of control and data among the things

class diagram and object diagram
- describe the static structure of the system
- objects, attributes and associations
component diagram
composite diagram
deployment diagram
package diagram

activity diagram
- step-by-step workflows
- shows overall flow of control ( flowchart)
state diagram (state chart diagram)
- describe the dynamic behavior of an individual object as a finite state machine
- initial state, states, event, transition, final state
use case diagram
- shows the functions provided by a system in terms of actors, their goals represented as use cases and dependencies between those use cases
- actor, package, use case
interaction diagrams
- communication diagram
- interaction overview diagram
- sequence diagram
- describe the dynamic behavior between actors&the system and the objects of the system
- object, activation, message
- timing diagram

jimin-kiim commented 1 year ago