Chapter 3: Analysis

3.1 Structural Diagrams

23
Analysis modeling uses a combination of text and diagrammatic forms to depict requirements for
data, function, and behavior in a way that is relatively easy to understand, and more important,
straightforward to review for correctness, completeness and consistency. This section presents
resources for conventional and object-oriented analysis (A! methods as well as resources for
"#$.
%n order to achieve the highest understanding of the project next there will be illustrations
containing various cases of system.
&irst, the following diagram is the use case diagram of the system
&ig '.() "se *ase +iagram
Then, the following diagram is the activity diagram of the system)
24
&ig '.,) Activity +iagram
-ext up is the .wim lane +iagram)
25
&ig '.') .wim $ane +iagram
"se case diagram, .wim $ane diagram and activity diagram almost cover all the areas a client
needs to /now about. There is another diagram which is called *lass diagram)
26
&ig '.0) *lass +iagram
-ow the system states are clearer.
3.2 Data Types and Operation Signatures
(. 1roducts)
Attributes-
%d ) int
1roduct2name ) string
1roduct2image ) string
peration-
3 Add product(!
27
3 +elete 1roduct(!
3 .elect 1roduct(!
,. 1roducts2items)
Attributes-
%d ) int
name ) string
image ) string
peration-
3 Add product item(!
3 +elete 1roduct item(!
3 .elect 1roduct item(!
'. "sers)
Attributes-
sl ) int
email ) string
password ) string
peration-
- validated the credentials entered by the user
0. +atabasemanager)
peration-
28
3 storedata(! - stores the data4parameters in database.
3 updatedata(! - update the data4parameters in database.
3.3 Feasibility Matrix
Feasibility
Criteria
Trainee 1 Trainee 2
Operational
Feasibility
30% 65%
Technical
Feasibility
35% 50%
Economic
Feasibility
25% 40%
Ranking:
2nd 1st
3.4 Structural Diagrams
29
&ig '.5) .tructural +iagram
3.5 Detailed !D
The 6ntity 7elationship +iagram (67+! enables a software engineer to specify the data objects
that are input and output from a system, the attributes that define the properties of these objects
30
and their relationship. %t provides an excellent graphical representation of the data structures and
relationship. They provide a clear view of the logical structure of data within the boundary of
interest and allow the engineer to model the data without considering the physical form.
.ome of the basic terms used in 67+ described below)
6ntity) An entity is an object with physical existence or may be an object with conceptual
existence. &or example a car, a student, an employee, an applicant.
An entity represented by a rectangle.
7elationship) A relationship is a logical lin/age between two or more entities which
describes how the entities are associated with each other.
A relationship described by a diamond.
7elationship *ardinality
7elationship cardinality refers to the number of entity instances involved in the
relationship. The cardinality ratios are)
()( (ne to ne!
()- (ne to #any!
#)- (#any to #any!
Attribute) Attribute is a piece of information that describes a particular entity.
1rimary 8ey) A primary /ey is an attribute or collection of attributes that allow us to
identify an entity uniquely.
&oreign /ey) A foreign /ey is an attribute of a relation, which refers to an existing
attribute of another relationship.
9ere is the 67 +iagram of the system-
31
&ig '.:) 67+ +iagram
3." Detailed DFD
A data fow diagra is a graphi!al representation that depi!ts in"oration
fow and the trans"ors that are applied as data o#e "ro inp$t to o$tp$t%
&he '(' ay $sed to represent a syste or so"tware at any le#el o"
a)stra!tion% '(' ay partition into le#els that represent in!reasing
in"oration fow and "$n!tional detail% &here"ore* the '(' pro#ides a
e!hanis "or "$n!tional odeling as well as in"oration fow odeling%
A le#el 0 '('* whi!h is also +nown as "$ndaental syste odel or a
!onte,t odel* represents the entire so"tware or syste eleent into as a
single )$))le with inp$t and o$tp$t data indi!ated )y in!oing and o$tgoing
arrows respe!ti#ely% &hen )$))le o" !onte,t odel sho$ld de!opose into
se#eral le#els%
32
&ig '.;) $evel < +&+
&ig '.=) $evel ( +&+
33
&ig '.>) $evel , of process '
34
&ig '.(<) $evel , of process 0
&ig '.(() $evel ' of process '.(
35
&ig '.(,) $evel ' of process '.,
&ig '.(') $evel ' of process '.'
&ig '.(0) $evel ' of process '.0
36
&ig '.(5) $evel ' of process '.5
&ig '.(:) $evel ' of process '.:
37
&ig '.(;) $evel 0 of process 0.(
&ig '.(=) $evel 0 of process 0.,
&ig '.(>) $evel 0 of process 0.'
38
&ig '.,<) $evel 0 of process 0.'.(
&ig '.,() $evel 0 of process 0.0
&ig '.,,) $evel 0 of process 0.5
3.# $ard%are &on'iguration
39
.ite .erver
3.( )et%or* +rotocol
.-#1 .ervice
The .imple -etwor/ #anagement 1rotocol (.-#1! service is an optional feature that can be
installed after the T*14%1 protocol has been successfully configured.
The .-#1 service provides an .-#1 agent that allows remote, centrali?ed management of
computers running)
@indows AistaB
@indows .erverB ,<<=
#icrosoftB @indowsB C1
#icrosoft @indows ,<<<
@indows .erver ,<<' operating systems
The .-#1 agent also allows management of the following services)
@indows C1 or the @indows .erver ,<<' operating systems and #icrosoft
@indows ,<<<-based @%-.
@indows C1 or the @indows .erver ,<<' operating systems and @indows ,<<<-based
+9*1
40
@indows C1 or the @indows .erver ,<<' operating systems and @indows ,<<<-based
%nternet %nformation .ervices (%%.!
$A- #anager
41