Mnnsoura OnfversUy

F11culty of Computers nnd Infonnation

Deporrnient or lnformntlon Technology
Fh~t Srmcstcr- 2020-2021

IIT326P) Human Computer Interaction

Grode: TTIJRD YEAR
Eng. Kboloud Aml'I'
OUTLINE

,,.. Requirement Analysis

-,, System Modeling
,. Interaction Models
,, Use Case Diagram
,. Sequence Diagram
,., Structure Model
, Class Diagram
 REQUIREMENT ANALYSIS

❖ Once the requirements are gathered, we document the requirements in a r,-v~;- rP(fl:""1""'""11~rn
r c-i, c i H1 t :; , document. use cases or as User Stories. which are shared with the stakeholders for
approval.
•·· Re qulrert'le nt anaJyals

•·· helps organizations to determine the actual needs of stakeholders

❖ it enables the development team to communicate with srnkeholders in " language they understand
❖ like system models. flow-charts instead of pages of text.
SYSTEM MODELING

, is the process of developing abstr.lct models of a system. W1th each model presenting a different view or
perspective of that system
, It 1s :1bout representing :t system using some kind of graphic31 notation based on notitions in d,e Unified
Modelin1 Language (UML).
,.. Mod<!ls help the 3nalyst co understand the function:illty of the systc_m

, It helps the cunomer to communic:ire with the system.

SYSTEM MODELING

Cxtcrnal

Bch;wior:il
lntcracoon

Structural
INTERACTION MODELING

, Modeling user interaction is important as it helps to identify user requirements.

;,,. Modeling system-to-system interaction.
,. Modeling component interaction.
, Use case diagrams and sequence diagrams are used for interaction modeling
USE CASE MODELING

Medical Receptionist Patient record system

Requirements Roquirements

- Transfer Data -Transfer data

• Register patient

Medical receptionist Patient record system

USE CASE MODELING

• Use cases were developed originally to support requirements elicitation and now
incorporated into the UML.
• Each use case represents a discrete task that involves external interaction with a
system.
• Actors in a use case may be people or other systems.
USE CASE RELATIONS

Gene r aJ iu tio n Ext e nd << exte nd> > Include

.. - --- --~ -<<include>>
- --- - - ·

•extend• © .... ... ...

•lndudo•

1'"91•
16gn4n
Registration - - - -

( optional) use case can be inserted

Withdraw
Cash -
The indude relationship is analogous
Between use-cases
into the behavior defined in the to a subroutine call.
extended use case.
USE CASE -CASE STUDY

/
.,c:--- --......
I .,,gin_ __ ,) ..

0 / ~:- _ <_ i._u~uu~~~) .. '-•Vo lidntc '• \

j ~- '"'·-.... . c-ocpo~i;- .:_') ( ucuuun~ ...-
\.!U~to m ""'-, • : : . . - - --."
\
"\

~
, ,., u r1t1 1JrJ\\ j
"' n -

b~;k ba~
- _,,- ••••

~)
'

•I• •

...
'<-
..... "(lp<lutc: --)
___ -
. . .nccount_ ,
{,
""
X
DutuhJS\;

---- :>
Trnn~fcr
-
A il tlq111."1"kttc). •~ h,1i,,u~ip•~ ••c "r ')'I~ ,· inchwk- · ·
SEQUENCE DIAGRAMS

• Sequence diagrams arc part of the UML and arc used to model the interactions between the actors and the
objects within a system.
• A sequence d1agr.im shows the sequence of mt.e ractrons that ~kc pince dunng a pi1rt1cular use case or use case
instance.
• The objects and act.o rs involved arc listed along the top of the diagrnm. with a dotted line drnwn vertically from
these.
• Interactions bctwC<?n objccu are indicated by annotated arrows.
SEQUENCE DIAGRAM FOR VIEW PATIENT INFORMATION

M @dlcal R eceptio nist

P : Pallentlnf o
7 r D : MHCPMS-D"'a'J
I
r AS : Authorlziltlon j
I
V iavvlnfo (PID) J r eport (Info. PIO,
I I
UIO)
- I
nuthorize (Info.
UID)
I
I
I

••t J
- !_U!_h~ri!a~o!~ J ]
•
I
(.:iiut h o rlz.:iit lon OKI

-1l - - - - - . -- - -- -- - -- -- - -- ·- -
Pcllicnl I nfo

- - - -
I
-•· -
I

--
( authonz.4tlon fdll) Error (no acccs,) I
y - - - - - - - ,.
I ,- I
STRUCTURAL MODELS

❖ Structural models of software display the organization of a system in terms of the

components that make up that system and their relationships.

❖ You create structural models of a system when you are discussing and designing the
system architecture.

❖ C lass diagrams are used for Structural modeling.

CLASS DIAGRAMS

, Class diagrams are used when developing an object oriented system

model to show the classes in a system and the a.ssociations between
these classes.
► An association is a link between classes that indicates that there is some
relationship between these classes.
 CLASS DIAGRAMS

leng&h: ~ • The illustration uses the following UML TM conventions:

Wtdth: double
Gal .... . Point• ( 10. 10)
1. Static members are underlined. Instance members are
• dniplay() "Old not.
+ ~ YOld
+ ,et'Wldth(~tcfth) : YOk:f 2. The operations follow this form :
• NtLenQd'l(newLengtt,) ¥Ok:f <ace••• modifier> <name> ( <parameter Hat>) : <return type>
• lletP~Uonu,c» Polnt) · ¥Old
1. A ccess Modifiers a re :
Student • publlc : (+) s ig n
-name: String • Prlvato: (- ) sign
~ :Int • Protected: (#) s ign.
• Package/Internal: (-) sign
:tmo•$1ude otc1tot
llgetlD()lnt 4 . Access modifiers appear i n front of each member.
+getN am e(): Str•ng 5 . Th• paramet.r ll&t &how& each parameter type pr.ced~
-gctE maH"""1:JdloO'G() String
by a colon.
CLASSES AND ASSOCIATIONS

Cu,tome, 5Y1t•m Order

• 10 ; fnl c-K(: r
t Mcnu urd \
M P.lJ)WOfd c-ncryptcd
• RM t.,u1:1nt U~t
•cu1tome 1 let & P,wd
• lojlln • p.-ym ~ optk>n
• 1elc<I • ~ l ~ 11• nl
• flbc:o o rdff from menu c ord
• p.,.,,nent

Cu,tomer S.tcct
P.lvmetll Oplton
0.llve,v Of 01de1

Ae,tau1cnl P~nl

• 01NI( lho OfC!cf •Amount

• Odtvc-, NJ II><• UHfn •P.11men1 e>oaon