System Design

4.1 UML diagrams

Each UML diagram is designed to let developers and customers view a software
system from a different perspective and in varying degrees of abstraction. UML diagrams
commonly created in visual modeling tools include:

Use Case Diagram displays the relationship among actors and use cases.

Class Diagram models class structure and contents using design elements such as classes,
packages and objects. It also displays relationships such as containment, inheritance,
associations and others.

Interaction Diagrams

 Sequence Diagram displays the time sequence of the objects participating in

the interaction. This consists of the vertical dimension (time) and horizontal
dimension (different objects).
 Collaboration Diagram displays an interaction organized around the objects
and their links to one another. Numbers are used to show the sequence of
messages.

State Diagram displays the sequences of states that an object of an interaction goes through
during its life in response to received stimuli, together with its responses and actions.

Activity Diagram displays a special state diagram where most of the states are action states
and most of the transitions are triggered by completion of the actions in the source states.
This diagram focuses on flows driven by internal processing.

A.I.E.T, Gunthapally 16
 System Design

UML DIAGRAMS

4.1.1 USE CASE DIAGRAM:

Set photo
User user
User
Get
photo
Get photo

Cropping

Image1

Image2

Image3

A.I.E.T, Gunthapally 17
 System Design

4.1.2 SEQUENCE DIAGRAM

File1
Face Client MainMenu Image Details Details1

Details of
Login
Store the image
details
Usernam
e Show
Password details
Back
Back

A.I.E.T, Gunthapally 18
 System Design

4.1.3. COLLABORATION DIAGRAM:

FaceWindow
submit

LoginWindow Login Window

submit
Mainmenu
Mainmenu Window
Window
Store details

Image Window segment ImageWindow

CropImage
CropImage Window
Window
submit
Mainmenu
Window Details2 Window
show

File1 Window
File1 Window
details

Details1 Window

A.I.E.T, Gunthapally 19
 System Design

4.1.4 ACTIVITY DIAGRAM:

ImageFiles Client

getPhoto Display photo

Store Croped
Crop Image
Images

Selected cropped Images

Embedded Image

Details

A.I.E.T, Gunthapally 20
 System Design

4.2. DATA FLOW DIAGRAMS

A graphical tool used to describe and analyze the moment of data through a system
manual or automated including the process, stores of data, and delays in the system. Data
Flow Diagrams are the central tool and the basis from which other components are
developed. The transformation of data from input to output, through processes, may be
described logically and independently of the physical components associated with the system.
The DFD is also know as a data flow graph or a bubble chart.

Types of data flow diagrams

DFD’s are of two types
(a) Physical DFD
(b) Logical DFD
4.2.1. Physical DFD
Structured analysis states that the current system should be first understand correctly.
The physical DFD is the model of the current system and is used to ensure that the current
system has been clearly understood. Physical DFDs shows actual devices, departments, and
people etc., involved in the current system.

4.2.2. Logical DFD

Logical DFD s is the model of the proposed system. They clearly should show the
requirements on which the new system should be built. Later during design activity this is
taken as the basis for drawing the system’s structure charts.

The Basic Notation used to create a DFD s is as follows:

Dataflow: Data move in a specific direction from an origin to a
Destination.

Process: People, procedures, or devices that use or produce

(Transform) Data. The physical component is not identified.

A.I.E.T, Gunthapally 21
 System Design

Source: External sources or destination of data, which may be

People, programs, organizations or other entities.

Data Store: Here data are stored or referenced by a process in the system.

DATAFLOW DIAGRAMS

Level 0:

Source Destination
Image Cropping
Image

A.I.E.T, Gunthapally 22
 System Design

Level 1:

External
Device

File1
File

File2
Source Cropping

File3

DB Store Details Verification

A.I.E.T, Gunthapally 23
 System Design

Level 2:

External
Device

File
File1
Source Cropping

File2

File3

DB Verification

Display details Merging Image 1

Image 2 Image 3
And image

4.2.1. Flow Chart

A.I.E.T, Gunthapally 24
 System Design

Start

No
Logi Access
n Denied
Yes
Source
Image

Cropping

Files Files Files

Merging

Display details
and image

End

4.3. Database Design

A.I.E.T, Gunthapally 25
 System Design

1) Table Name: User Login Information

Column Name Null? Data Type

Name Not Null Varchar2(15)
Password Varchar2(10)
Contact No Number(10)
Address Varchar2(20)
Email Varchar2(25)

2) Table Name: Criminals Information

Column Name Null? Data Type

No Not Null Number(5)
CName Varchar2(15)
Alias Varchar2(10)
Gender Varchar2(6)
Religion Varchar2(10)
Complexion Varchar2(10)
Main Crime Varchar2(20)
Address Varchar2(20)

A.I.E.T, Gunthapally 26