Sub:

CE
:
Softwar
e
Enginee
ring
•
Archite
ctural
design
metrics
•
Structu
ral
comple
xity
(based
on
modul
e
fanout)
•
Data
comple
xity
(based
on
modul
e
interfa
ce
inputs
and
output
s)
•
Syste
m
comple
xity
(sum
of
structu
ral and
data
comple
xity)
•
Morph
ology
(numb
er of
nodes
and
arcs in
progra
m
graph)
•
Design
structu
re
quality
index
(DSQI)
•
Compo
nent-
level
design
metrics
•
Cohesi
on
metrics
(data
slice,
data
tokens,
glue
tokens,
superg
lue
tokens,
stickin
ess)
•
Coupli
ng
metrics
(data
and
control
flow,
global,
enviro
nment
al)
•
Compl
exity
metrics
(e.g.
cyclom
atic
comple
xity)
•
Interfa
ce
design
metrics
(e.g.
layout
approp
riatene
ss)
Halste
ad’s
Softwa
re
Scienc
e
(Sourc
e Code
Metrics
)
•
Overall
progra
m
length
•
Potenti
al
minimu
m
algorit
hm
volume
•
Actual
algorit
hm
volume
(numb
er of
bits
used
to
specify
progra
m)
•
Progra
m level
(softwa
re
comple
xity)
•
Langu
age
level
(const
ant for
given
langua
ge)
Testin
g
Metrics
•
Metrics
that
predict
the
likely
numbe
r of
tests
require
d
during
various
testing
phases
•
Metrics
that
focus
on test
covera
ge for
a given
compo
nent
Mainte
nance
Metrics
•
Softwa
re
Maturit
y Index
(IEEE
Standa
rd
982.1-
1988)
•
SMI
approa
ches
1.0 as
produc
t
begins
to
stabiliz
e
Charotar
Institute
of
Technolo
gy-
Changa
Page 63
of 65
Sub:
CE
:
Softwar
e
Enginee
ring
Chapt
er 20
Object
-
Orient
ed
Conce
pts
and
Pricin
ples
Overvi
ew
This
chapte
r
provid
es an
introdu
ction to
object-
oriente
d
progra
mming
and
manag
ement
principl
es for
object-
oriente
d
project
s.
Object-
oriente
d
softwar
e
engine
ering
proces
s is
similar
to that
found
in the
rapid
prototy
ping or
spiral
paradi
gms.
Even
though
,
object-
oriente
d
softwar
e
engine
ering
follows
the
same
steps
as the
conven
tional
approa
ch
(analys
is,
design,
implem
entatio
n, and
testing
) it is
harder
to
separa
te
them
into
discret
e
activiti
es.
The
next 3
chapte
rs deal
with
the
topics
of
object-
oriente
d
analysi
s,
object-
oriente
d
design,
and
object-
oriente
d
testing.
Evoluti
onary
Object-
Orient
ed
Proces
s
Model
•
Custo
mer
comm
unicati
on
•
Planni
ng
•
Risk
analysi
s
•
Engine
ering
constr
uction
and
analysi
s
•
Identify
candid
ate
classe
s
•
Look-
up
classe
s in
library
•
Extract
classe
s if
availab
le
•
Engine
er
classe
s if not
availab
le
o
Object-
oriente
d
analysi
s
(OOA)
o
Object-
oriente
d
design
(OOD)
o
Object-
oriente
d
progra
mming
(OOP)
o
Object-
oriente
d
testing
(OOT)
•
Put
new
classe
s in
library
•
Constr
uct Nth
iteratio
n of
the
system
•
Custo
mer
evaluat
ion
Charotar
Institute
of
Technolo
gy-
Changa
Page 64
of 65
Sub:
CE
:
Softwar
e
Enginee
ring
Object-
Orient
ed
Conce
pts
•
Object
s-
encaps
ulates
both
data
(attribu
tes)
and
data
manip
ulation
functio
ns
(called
metho
ds,
operati
ons,
and
service
s)
•
Class -
genera
lized
descrip
tion
(templ
ate or
pattern
) that
describ
es a
collecti
on of
similar
objects
•
Superc
lass - a
collecti
on of
objects
•
Subcla
ss - an
instanc
e of a
class
•
Class
hierarc
hy -
attribut
es and
metho
ds of a
supercl
ass
are
inherit
ed by
its
subcla
sses
•
Messa
ges -
the
means
by
which
objects
exchan
ge
inform
ation
with
one
anothe
r
•
Inherit
ance -
provid
es a
means
for
allowin
g
subcla
sses to
reuse
existin
g
supercl
ass
data
and
proced
ures;
also
provid
es
mecha
nism
for
propag
ating
chang
es
•
Polym
orphis
m - a
mecha
nism
that
allows
several
objects
in an
class
hierarc
hy to
have
differe
nt
metho
ds with
thesa
me
name
(instan
ces of
each
subcla
ss will
be free
to
respon
d to
messa
ges by
calling
their
own
version
of
themet
hod)
Advant
ages
of
Object-
Orient
ed
Archite
ctures
•
Imple
mentat
ion
details
of data
and
proced
ures
and
hidden
from
the
outside
world
(reduc
es the
propag
ation
of side
effects
when
chang
es are
made).
•
Data
structu
res
and
operat
ors are
merge
d in
single
entity
or
class
(this
facilitat
es
reuse)
•
Interfa
ces
among
encaps
ulated
objects
are
simplifi
ed
(syste
m
couplin
g is
reduce
d since
object
needs
not be
concer
ned
about
the
details
of
interna
l data
structu
res)
Class
Constr
uction
Option
s
•
Build
new
class
from
scratch
without
using
inherit
ance
•
Use
inherit
ance
to
create
new
class
from
existin
g class
contain
s most
of the
desire
d
attribut
es and
operati
ons
•
Restru
cture
the
class
hierarc
hy so
that
the
require
d
attribut
es and
operati
ons
can be
inherit
ed by
the
newly
create
d
class
•

Overri
de
some
attribut
es or
operati
ons in
an
existin
g class
and
use
inherit
ance
to
create
a new
class
with
(specia
lized)
private
version
s of
these
attribut
es and
operati
ons.
Charotar
Institute
of
Technolo
gy-
Changa
Page 65
of 65