Welcome to Scribd. Sign in or start your free trial to enjoy unlimited e-books, audiobooks & documents.Find out more
Download
Standard view
Full view
of .
Look up keyword
Like this
4Activity
0 of .
Results for:
No results containing your search query
P. 1
Formal Specification Validation For SIDIF Using Theorem Proven

Formal Specification Validation For SIDIF Using Theorem Proven

Ratings: (0)|Views: 186|Likes:
Journal of Computing, ISSN 2151-9617, http://www.journalofcomputing.org/volume-3-issue-1-january-2011
Journal of Computing, ISSN 2151-9617, http://www.journalofcomputing.org/volume-3-issue-1-january-2011

More info:

Published by: Journal of Computing on Feb 10, 2011
Copyright:Attribution Non-commercial

Availability:

Read on Scribd mobile: iPhone, iPad and Android.
download as PDF, TXT or read online from Scribd
See more
See less

11/07/2012

pdf

text

original

 
JOURNAL OF COMPUTING, VOLUME 3, ISSUE 1, JANUARY 2011, ISSN 2151-9617HTTPS://SITES.GOOGLE.COM/SITE/JOURNALOFCOMPUTING/ WWW.JOURNALOFCOMPUTING.ORG 1
 
Formal Specification ValidationFor SIDIF Using Theorem Proven
Man. M, Jusoh. JA, Rahim. MMS, and Zakaria. MZ.
Abstract
 —This paper discusses the formal validation for Spatial Information Databases Integration Framework (SIDIF). A SIDIFdatabase is a large, organized body of persistent data, usually associated with computerized software designed to update,query, and retrieve components of the data stored within the system. One of the common difficulties faced by the developer is indesigning a robust database system. Even so, in order to solve this matter, developers have to focus their efforts on the formalspecifications. This is supposed to reduce the overall development time. Formal specifications can be use to provide anunambiguous and precise supplement to natural language descriptions. Besides, it can be rigorously validate, and verifiedleading to the early detection of specification errors. Consequently, to validate this problem formally, we specify the SIDIFdatabase framework using Z language and prove by using Z/EVES theorem proven tool. By using this kind of tools, it may helpsto reduce time, energy and mistake compared to manual theorem proving which can be error task and tedious.
Index Terms
 —
 
Software Engineering, Formal Specification, Z Specification Language, SIDIF Database Framework.
——————————
 
 
——————————
1 I
NTRODUCTION
 
ccording
 
to
 
[1],
 
software
 
engineering
 
is
 
in
 
engineer
ing
 
discipline
 
that
 
is
 
concerned
 
with
 
all
 
aspects
 
of
 
software
 
production
 
from
 
the
 
early
 
stages
 
of
 
system
 
specification
 
to
 
maintaining
 
the
 
system
 
after
 
it
 
has
 
gone
 
into
 
utilize.
 
In
 
engineering
 
discipline,
 
they
 
apply
 
theories,
 
methods
 
and
 
tools
 
where
 
these
 
are
 
appropriate.
 
Never
theless,
 
they
 
use
 
them
 
selectively
 
and
 
always
 
try
 
to
 
dis
cover
 
the
 
solutions
 
of
 
the
 
problems
 
even
 
when
 
there
 
are
 
no
 
applicable
 
theories
 
and
 
methods.
 
More
 
to
 
the
 
point,
 
software
 
engineering
 
is
 
not
 
 just
 
appre
hensive
 
with
 
the
 
technical
 
processes
 
of
 
software
 
devel
opment
 
 but
 
also
 
with
 
activities
 
such
 
as
 
software
 
project
 
management
 
and
 
with
 
the
 
development
 
of
 
tools,
 
methods
 
and
 
theories
 
to
 
support
 
software
 
production.
 
The
 
soft
ware
 
process
 
includes
 
all
 
of
 
the
 
activities
 
involved
 
in
 
a
 
software
 
development.
 
The
 
high
level
 
activities
 
of
 
soft
ware
 
specification,
 
development,
 
validation
 
and
 
evolution
 
are
 
part
 
of
 
all
 
software
 
process.
 
Software
 
specification
 
is
 
the
 
process
 
that
 
establishing
 
what
 
services
 
are
 
required
 
and
 
the
 
constraints
 
on
 
the
 
system’s
 
operation
 
and
 
devel
opment.
 
The
 
software
 
requirements
 
specification
 
(SRS)
 
is
 
the
 
offi
cial
 
statement
 
of
 
what
 
the
 
system
 
developers
 
should
 
im
plement.
 
It
 
should
 
include
 
 both
 
the
 
user
 
requirements
 
for
 
a
 
system
 
and
 
a
 
detailed
 
specification
 
of
 
the
 
system
 
re
quirements.
 
In
 
a
 
few
 
cases,
 
the
 
user
 
and
 
system
 
require
ments
 
may
 
 be
 
integrated
 
into
 
a
 
single
 
description.
 
In
 
oth
er
 
cases,
 
the
 
user
 
requirements
 
are
 
defined
 
in
 
an
 
introduc
tion
 
to
 
the
 
system
 
requirements
 
specification.
 
If
 
there
 
are
 
a
 
large
 
number
 
of
 
requirements,
 
the
 
detailed
 
system
 
re
quirements
 
may
 
 be
 
presented
 
in
 
a
 
separate
 
document.
 
Specification
 
and
 
design
 
are
 
inextricably
 
intermingled.
 
Architectural
 
design
 
is
 
essential
 
to
 
structure
 
a
 
specifica
tion
 
and
 
the
 
specification
 
process.
 
Formal
 
specifications
 
are
 
expressed
 
in
 
a
 
mathematical
 
notation
 
whose
 
vocabu
lary,
 
syntax
 
and
 
semantics
 
are
 
formally
 
defined
 
[1].
 
Usually
 
 both
 
the
 
system
 
requirements
 
and
 
the
 
system
 
design
 
are
 
expressed
 
in
 
detail
 
and
 
carefully
 
analyzed
 
and
 
checked
 
 before
 
implementation
 
 begins.
 
If
 
a
 
formal
 
specification
 
of
 
the
 
software
 
is
 
developed,
 
this
 
usually
 
comes
 
after
 
the
 
system
 
requirements
 
have
 
 been
 
specifying
 
 but
 
 before
 
the
 
detailed
 
system
 
design.
 
There
 
is
 
a
 
tight
 
response
 
loop
 
 between
 
the
 
detailed
 
requirements
 
specification
 
and
 
the
 
formal
 
specification.
 
One
 
of
 
the
 
main
 
 benefits
 
of
 
formal
 
specification
 
is
 
its
 
ability
 
to
 
un
cover
 
problems
 
and
 
ambiguities
 
in
 
the
 
system
 
require
ments.
 
A
 © 2011 Journal of ComputingPress, NY, USA, ISSN 2151-9617
http://sites.google.com/site/journalofcomputing/
 
————————————————
 
 
 Man. M.
 
Department
 
of 
 
Computer
 
Science,Faculty
 
of 
 
Science
 
and
 
Tech
nology,
 
Universiti
 
 Malaysia
 
Terengganu,
 
21030
 
Kuala
 
Terengganu,
 
Te
rengganu,
 
 Malaysia,
 
Tel:
 
09
6683307
 
 fax
 
:
 
609
6694660
 
 
 Jusoh
. JA. Department of Computer Science, Faculty of Computer Science and Information Technology, Univesiti Sultan Zainal Abidin,21030 Kuala Terengganu, Terengganu, Malaysia.
 
 Rahim. MMS.
Department
of 
 
Computer
 
Graphics
 
&
 
 Multimedia,
 
Facul
ty
 
of 
 
Computer
 
Science
 
and
 
Information
 
Systems,
 
Universiti
 
Teknologi Malaysia,
 
81310
 
UTM
 
Skudai,
 
 Johor
 
Bahru,
 
 Malaysia.
 
 
Zakaria, MZ.
 
Department
 
of 
 
Fisheries
 
Science,
 
Faculty
 
of 
 
 Agro
 
Tech
nology
 
and
 
Food
 
Science,
 
Universiti
 
 Malaysia
 
Terengganu,
 
21030
 
KualaTerengganu,
 
Terengganu,
 
 Malaysia.
 
Tel:
 
09
6683307
 
 fax
 
:
 
609
6694660
 
 
JOURNAL OF COMPUTING, VOLUME 3, ISSUE 1, JANUARY 2011, ISSN 2151-9617HTTPS://SITES.GOOGLE.COM/SITE/JOURNALOFCOMPUTING/ WWW.JOURNALOFCOMPUTING.ORG
6
2 F
ORMAL
S
PECIFICATION
 
The
 
principal
 
value
 
of
 
using
 
formal
 
methods
 
in
 
the
 
soft
ware
 
process
 
is
 
that
 
it
 
forces
 
an
 
analysis
 
of
 
the
 
system
 
requirements
 
at
 
an
 
early
 
stage.
 
Correcting
 
errors
 
at
 
this
 
stage
 
is
 
cheaper
 
than
 
modifying
 
a
 
delivered
 
system.
 
For
mal
 
methods
 
consist
 
of
 
formal
 
specification,
 
specification
 
analysis
 
and
 
proof,
 
transformational
 
development
 
and
 
program
 
verification.
 
Formal
 
specification
 
languages
 
comprise
 
VDM
 
(Jones,
 
1980),
 
Petri
 
Nets
 
(Carl
 
Adam
 
Petri,
 
1962),
 
CSP
 
(Hoare,
 
1985),
 
Z
 
(Spivey,
 
1992)
 
and
 
B
 
(WordSworth,
 
1996).
 
Formal
 
specification
 
techniques
 
are
 
most
 
cost
effective
 
in
 
the
 
development
 
of
 
critical
 
systems
 
where
 
safety,
 
reliability
 
and
 
security
 
are
 
particularly
 
im
portant.
 
Formal
 
proving
 
is
 
a
 
complete
 
argument
 
of
 
mathematical
 
representation
 
and
 
it
 
is
 
used
 
to
 
validate
 
statement
 
about
 
system
 
description.
 
Usually,
 
formal
 
proving
 
can
 
 be
 
done
 
manually.
 
Nowadays,
 
formal
 
proving
 
can
 
 be
 
done
 
with
 
the
 
support
 
of
 
formal
 
method
 
tools
 
such
 
as
 
theorem
 
proven
 
tools.
 
Theorem
 
proven
 
is
 
a
 
tool
 
that
 
implements
 
automatic
 
theorem
 
proving
 
need
 
of
 
user
 
support.
 
Regularly,
 
devel
opers
 
cover
 
a
 
long
 
times
 
and
 
looping
 
process,
 
so
 
there
 
might
 
 be
 
a
 
great
 
possibility
 
of
 
mistakes.
 
The
 
proofs
 
are
 
efficiently
 
when
 
it
 
 been
 
presented
 
in
 
a
 
user
friendly
 
ap
proach
 
and
 
it
 
should
 
not
 
 be
 
unreasonably
 
large.
 
Never
theless,
 
a
 
lot
 
of
 
the
 
proof
 
that
 
involved
 
in
 
software
 
valida
tion
 
is
 
naturally
 
detailed,
 
low
level
 
and
 
repetitious.
 
So
 
we
 
can
 
 briefly
 
state
 
that
 
it
 
is
 
unsuitable
 
for
 
human
 
checking.
 
Thus,
 
formal
 
proving
 
supported
 
 by
 
tool,
 
which
 
is
 
not
 
only
 
reduce
 
the
 
possibility
 
of
 
mistakes
 
 but
 
also
 
not
 
totally
 
removes
 
it
 
[2].
 
Hence,
 
the
 
use
 
of
 
support
 
tool
 
is
 
a
 
main
 
factor
 
that
 
can
 
affect
 
the
 
acceptance
 
of
 
formal
 
me
thod
 
practically
 
[3].
 
The
 
Z
 
specification
 
language
 
is
 
a
 
way
 
of
 
decomposing
 
a
 
specification
 
into
 
small
 
pieces
 
called
 
schemas
 
[4].
 
Each
 
piece
 
can
 
 be
 
linked
 
with
 
a
 
commentary
 
that
 
gives
 
explanation
 
informally
 
the
 
importance
 
of
 
the
 
formal
 
mathematics.
 
A
 
schema
 
is
 
essentially
 
the
 
formal
 
specification
 
analogous
 
to
 
programming
 
language
 
sub
routines
 
that
 
are
 
used
 
to
 
structure
 
a
 
system,
 
where
 
the
 
schemas
 
are
 
used
 
to
 
structure
 
a
 
formal
 
specification.
 
The
 
Z
 
is
 
physically
 
powerful
 
on
 
sets
 
and
 
functions.
 
Generally,
 
Z
 
notation
 
is
 
use
 
for
 
sequential
 
situation.
 
We
 
interested
 
in
 
using
 
Z
 
notation
 
 because
 
it
 
is
 
a
 
mature
 
technique
 
for
 
model
 based
 
specification
 
[5].
 
It
 
combines
 
formal
 
and
 
informal
 
description
 
and
 
uses
 
graphical
 
highlighting
 
when
 
presenting
 
specifications.
 
In
 
this
 
research,
 
one
 
of
 
the
 
theorems
 
proving
 
tool
 
that
 
has
 
 been
 
choose
 
is
 
Z/EVES.
 
Z/EVES
 
can
 
 be
 
applied
 
in
 
most
 
process
 
and
 
need
 
only
 
a
 
minimum
 
 background
 
education
 
to
 
use
 
it.
 
It
 
can
 
 be
 
learned
 
in
 
a
 
few
 
months
 
depending
 
on
 
the
 
type
 
of
 
applications
 
and
 
can
 
 be
 
run
 
in.
 
3 SIDIF
 
D
ATABASE
F
RAMEWORK
 
Spatial
 
Information
 
Databases
 
Integration
 
Framework
 
or
 
SIDIF
 
is
 
a
 
design
 
database
 
integration
 
space
 
proposed
 
to
 
evaluate
 
development
 
effectiveness
 
artificial
 
reef.
 
This
 
method
 
is
 
was
 
one
 
method
 
regarded
 
as
 
a
 
new
 
idea
 
to
 
en
sure
 
effectiveness
 
of
 
artificial
 
reef
 
development
 
project
 
can
 
 be
 
valued
 
his
 
effectiveness.
 
As
 
evaluation
 
process
 
previously
 
require
 
fairly
 
high
 
cost
 
required
 
one
 
special
 
scuba
 
unit
 
to
 
assess
 
artificial
 
reef
 
levels
 
of
 
development
 
and
 
development
 
 by
 
diving
 
me
thod.
 
SIDIF
 
was
 
one
 
method
 
for
 
information
 
combination
 
of
 
two
 
or
 
more
 
database
 
which
 
possess
 
different
 
scheme
 
and
 
also
 
same.
 
In
 
this
 
study,
 
research
 
only
 
made
 
integra
tion
 
of
 
two
 
database
 
only
 
namely
 
artificial
 
reef
 
database
 
(ARPOS)
 
[6]
 
and
 
fish
 
landing
 
database
 
(WiFISH)
 
[7].
 
Be
fore
 
integration
 
process
 
 both
 
this
 
database
 
is
 
conducted,
 
various
 
issues
 
should
 
 be
 
identified
 
over
 
proceed.
 
A
 
few
 
process
 
or
 
move
 
need
 
to
 
 be
 
taken
 
 broken
 
up
 
into
 
4
 
levels
 
as
 
follows
 
[8]:
 
i.
 
Pre
integration
:
 
Process
 
to
 
assess
 
database
 
environ
ment
 
are
 
used
 
example
 
like
 
Oracle,
 
MYSQL,
 
MSSQL,
 
MS
 
ACESSS
 
and
 
form
 
other
 
database.
 ii.
 
Scheme
 
Comparison
:
 
Scheme
 
comparison
 
or
 
structure
 
for
 
each
 
this
 
database
 
is
 
needed
 
to
 
facilitate
 
integra
tion
 
process
 
conducted.
 
In
 
early,
 
this
 
process
 
is
 
made
 
manually.
 iii.
 
Intermediary
 
software
 
development
 
(middleware)
:
 
an
 
ap
plication
 
shall
 
 be
 
developed
 
for
 
integration
 
process
 
the
 
data
 
 base
 
workable.
 iv.
 
Post
Integration
:
 
Integration
 
process
 
assessment
 
was
 
 being
 
conducted
 
from
 
credibility
 
process
 
aspect
 
and
 
interoperability
”.
 
The
 
evaluation
 
results
 
of
 
the
 
two
 
databases
 
are
 
found
 
that
 
the
 
location
 
(position)
 
of
 
artificial
 
reef
 
can
 
 be
 
equal
 
with
 
the
 
location
 
of
 
fish
 
catches
 
conducted.
 
Due
 
to
 
this,
 
the
 
location
 
 based
 
technique
 
is
 
a
 
core
 
and
 
a
 
fundamental
 
to
 
determine
 
the
 
effectiveness
 
development
 
level
 
of
 
the
 
ar
tificial
 
reef
 
project
 
development
 
at
 
a
 
certain
 
location
 
and
 
also
 
within
 
the
 
timeline.
 
An
 
equivalent
 
assumption
 
can
 
 be
 
formed
 
as
 
follows:
 
Catch
 
location
 
(CL)
 
is
 
equivalent
 
with
 
artificial
 
reefs
 
de
velopment
 
(AR).
 
 Assessment
 
 factor
 
is
 
dependent
 
on
 
catch
 
 yield
 
number
 
(CT)
 
 for
 
each
 
type
 
of 
 
 fish
 
(FT)
 
and
 
compari
son
 
with
 
artificial
 
reef 
 
type
 
(RT)
 
which
 
included.
 
 A
 
 for
mula
 
can
 
be
 
set
 
up
 
here.
 
CL
 AR
 
where
 
if 
 
 found
 
CT 
FT 
 
is
 
high
 
then
 
 AR
 
is
 
effective
 
which
 
depending
 
on
 
catch
 
date
 
(DT)
 
made.
 
Vice
 
versa
 
if 
 
CT 
 
low,
 
then
 
 AR
 
to
 
be
 
inef 
 fective.
 
Based
 
on
 
that
 
assumption
 
formula,
 
a
 
newly
 
developed
 
algorithm
 
called
 
location
 
 based
 
technique
 
can
 
assess
 
the
 
effectiveness
 
level
 
of
 
artificial
 
reef
 
development
 
project.
 
 
JOURNAL OF COMPUTING, VOLUME 3, ISSUE 1, JANUARY 2011, ISSN 2151-9617HTTPS://SITES.GOOGLE.COM/SITE/JOURNALOFCOMPUTING/ WWW.JOURNALOFCOMPUTING.ORG
3
The
 
integration
 
of
 
location
 
 based
 
process
 
and
 
scheme
 
comparison
 
would
 
 be
 
made
 
 by
 
intermediary
 
software
 
(middleware)
 
which
 
shall
 
 be
 
developed
 
refer
 
to
 
Fig.
 
3
 
 by
 
using
 
3
tier
 
architecture
 
as
 
shows
 
in
 
Fig.
 
4.
 
Fig.
 
3
 
SIDIF
 
architecture
 
Fig.
 
4
 
The
 
3
tier
 
Architecture
 
Since
 
those
 
data
 
in
 
the
 
three
 
different
 
databases
 
are
 
at
 
different
 
location
 
and
 
in
 
different
 
formats,
 
then
 
interme
diary
 
software
 
(middleware)
 
is
 
very
 
much
 
needed
 
for
 
integration
 
purposes
 
[9].
 
Table
 
1
 
to
 
table
 
5
 
 below
 
shown
 
the
 
information
 
about
 
the
 
data
 
that
 
covert
 
to
 
specific
 
da
tabase
 
type
 
in
 
different
 
environment
 
[10].
 
4 Z
 
S
PECIFICATION
V
ALIDATION
F
OR
SIDIF
Based
 
on
 
the
 
information
 
in
 
table
 
1
 
to
 
table
 
4
 
 below,
 
for
mal
 
specification
 
was
 
generated
 
using
 
Z
eves
 
tools
 
for
 
formalizing
 
the
 
software
 
specification
 
for
 
all
 
the
 
informa
tion.
 
Fig.
 
5
 
to
 
Fig.
 
7
 
 below
 
has
 
shown
 
the
 
schema
 
for
 
all
 
the
 
information
 
with
 
different
 
type
 
of
 
database
 
in
 
single
 
server.
 
5 R
ESULT AND
C
ONCLUSIONS
 
In
 
this
 
paper,
 
we
 
demonstrate
 
a
 
validation
 
on
 
Z
 
formal
 
specification
 
of
 
a
 
case
 
study
 
in
 
fisheries
 
industry
 
databas
es
 
using
 
theorem
 
proving
 
technique.
 
According
 
to
 
our
 
experience,
 
many
 
theorems
 
have
 
 been
 
through
 
a
 
long
 
and
 
repetitious
 
proving
 
process.
 
If
 
the
 
proving
 
is
 
done
 
ma
nually
 
 by
 
humans,
 
the
 
possibility
 
a
 
mistake
 
may
 
 be
 
made
 
is
 
high.
 
Using
 
Z/EVES,
 
not
 
only
 
this
 
possibility
 
can
 
 be
 
reduced,
 
the
 
proving
 
can
 
 be
 
done
 
fast
 
and
 
reliable.
 
One
 
of
 
our
 
future
 
works
 
shall
 
deal
 
with
 
complete
 
and
 
precise
 
specification
 
and
 
validation
 
for
 
multiple
 
databases
 
in
 
dis
tributed
 
database
 
systems
 
environment.
 
After
 
a
 
formal
 
specification
 
and
 
validation
 
in
 
successful.
 
Coding
 
process
 
was
 
done
 
using
 
.net
 
programming
 
lan
guage
 
for
 
developing
 
a
 
middleware
 
application.
 
Below
 
is
 
one
 
module
 
of
 
coding
 
for
 
two
 
databases
 
integration
 
that
 
was
 
included
 
in
 
SIDIF
 
framework.
 
//combining
 
the
 
data
 
from
 
two
 
different
 
databases
 
DataTable
 
combine
 
=
 
new
 
DataTable();
 
combine.Columns.Add(
ʺ
TARIKHTANGKAPAN
ʺ
 ,
 
typeof(string
 
));
 
combine.Columns.Add(
ʺ
 JENISIKAN
ʺ
 ,
 
typeof(string));
 
combine.Columns.Add(
ʺ
 JUMLAHHASILTANGKAPAN
ʺ
 ,
 
type
of(string));
 
combine.Columns.Add(
ʺ
KAWASANTANGKAPAN
ʺ
 ,
 
typeof(string));
 
combine.Columns.Add(
ʺ
 JENISTUKUN
ʺ
 ,
 
typeof(string));
 
for
 
(int
 
i
 
=
 
0;
 
i
 
<
 
dt1.Rows.Count;
 
i++)
 
{
 
for
 
(int
 
 j
 
=
 
0;
 
 j
 
<
 
dt2.Rows.Count;
 
 j++)
 
{
 
if
 
(dt1.Rows[i][
ʺ
TAPAKUNJAM
ʺ
].ToString()
 
==
 
dt2.Rows[j][
ʺ
KAWASANTANGKAPAN
ʺ
].ToString
 
())
 
{
 
com
 bine.Rows.Add(dt2.Rows[j][
ʺ
TARIKHPENDARATAN
ʺ
].ToString(),
 
dt2.Rows[j][
ʺ
 JENISIKAN
ʺ
].ToString(),
 
dt2.Rows[j][
ʺ
 JUMLAHHASILTANGKAPAN
ʺ
].ToString(),
 
dt1.Rows[i][
ʺ
TAPAKUNJAM
ʺ
],
 
dt1.Rows[i][
ʺ
 JENISTUKUN
ʺ
]);
 
}
 
}
 
}
 
GridView3.DataSource=
 
combine
 
;
 
GridView3.DataBind();
 
}
 
Database Layer
 Database Server 
ARPOSDatabase
 
WiFISHDatabase
Server Application Layer
Web Server 
Client LayerInternet
Client 

Activity (4)

You've already reviewed this. Edit your review.
1 thousand reads
1 hundred reads
Lily Aida Jusoh liked this
Imsai Arasan liked this

You're Reading a Free Preview

Download
scribd
/*********** DO NOT ALTER ANYTHING BELOW THIS LINE ! ************/ var s_code=s.t();if(s_code)document.write(s_code)//-->