Samenvatting system design diagrams

System
12-202


design
4

, U.m.l = unified language
model
Model → requirements → developers can create a
system. Iron triangle of project
Why use
models? management:
Schedul
• understand the e
system
• Communicate with
users
• Accurate description of tree required Qualit
system y
• iron triangle of project
Scop Budge
management Ik e t

What is a
model?
A simplified representation of a part of the word from a particular view

• Simplified → what do we discard,what do we represent?

• Representations → which notation is to be
used?
• View → with particular aspect is
modelled?

U.m.l • Use Case diagram → describes the system's
diagrams: functionality at the highest level → actor uses function of
Activit • the system
Activity diagram → describes process that take place in the
Requirements
y
list Real world → not al interact with the system




&
• State machine → describes changes within the

• systemdiagram → models the data that are stored
Class
State
machine Use case inside the system → use cases correspond to actions
on objects
Behaviou Functionalit
r Dat Iynteractio
a n

Sequenc
Clas e
s

System
boundary


Design = the creation of a plan or convention for the construction of an object or a
system.
Waterfall
model:




Ik