Please enable JavaScript.
Coggle requires JavaScript to display documents.
SYSTEM MODELING (5.2)
The process of developing abstract models of a…
SYSTEM MODELING (5.2)
The process of developing abstract models of a system.
It helps analysts understand the functionality of the system and models are used to better communicate with customers.
MODELS OF EXISTING SYSTEMS
- Used during requirements engineering.
- Lead to requirements for the new system
MODELS OF NEW SYSTEMS
- Used during requirements engineering to help explain the proposed requirements to other system stakeholders.
- Used to discuss design proposals
SYSTEM PERSPECTIVES
-
-
-
BEHAVIORAL PERSPECTIVE
dynamic behaviour of the system and how it responds
ACTIVITY DIAGRAM
STATECHART DIAGRAM
UML DIAGRAM TYPES
ACTIVITY DIAGRAMS
show the activities involved in a process or in data processing.
helps to visualize a certain use case at a more detailed level
describes dynamic aspects of the system
-
SEQUENCE DIAGRAMS
show interactions between system, actors, and its components
SHOWS DIFFERENT PARTS OF A SYSTEM WORK IN SEQUENCE TO GET SOMETHING DONE
-
-
ACTORS AND OBJECTS ARE LISTED ALONG THE TOP OF THE DIAGRAM, WITH DOTTED LINE DRAWN VERTICALLY
-
OBJECTS ARRANGED IN X AXIS, AND MESSAGES IN INCREASING TIME ALONG THE Y AXIS
-
ACTIVATION
represented by a thin rectangle representing the period during which an element is performing an operation
-
MESSAGES
-
RETURN MESSAGE
comm. between lifelines of an interaction, represents the passing of info back to the caller
-
SYNCHRONOUS MESSAGE
sender waits for the receiver to process the message before carrying out with another mess. SOLID HEAD ARROW
ASYNCHRONOUS MESSAGE
when sender does not wait for the receiver to reply before sending another message
LINE HEAD ARROW
-
ALTERNATIVES
describe a mutually exclusive choise
drawn using a frame
word alt is place inside the frame
operands are seperated by a dashed line
each operand is given a guard, place on top of the operand
STATE DIAGRAMS
also referred to (STATECHART DIAGRAMS)
show how the system reacts to internal and external events
used to model dynamic behavior of a class in response to time and external stimuli
used to model events responsible for change from a state
CLASS DIAGRAM
visualizing, describing, documenting different aspects of a system, constructing exuctable code of the software
overview by displaying classes, attributes, operations, and relationships
-
-
ESSENTIAL ELEMENTS
-
ATTRIBUTES
VISIBILITIES describe the accessibility of an attribute of a class
( +, -, #, OR ~ )
-
RELATIONSHIPS
-
-
ASSOCIATIONS: static relationship between classes, named using a verb
COMPOSITIONS: strong ownership between two classes
CHILD WILL NEVER EXIST INDEPENDENTLY
two-way association
if composite is deleted, all other parts associated are deleted
STRAIGHT LINE WITH FILLED BLACK DIAMOND
AGGREGATION: weak relationship
CHILD CAN EXIST SEPERATELY
models a whole-part between aggregate and its parts
part object remains, even when the whole object is destroyed.
STRAIGHT LINE WITH EMPTY DIAMOND
MULTIPLICITY
- zero to one (0..1)
- one to one (1..1)
- zero to many (0..6)
- one to many (1..*)