5.

1 INTRODUCTION
Systems design

Introduction: Systems design is the process or art of defining the architecture,

components, modules, interfaces, and data for a system to satisfy specified requirements. One

could see it as the application of systems theory to product development. There is some

overlap and synergy with the disciplines of systems analysis, systems architecture and

systems engineering

5.2 DATA FLOW DIAGRAMS

Data Flow Diagrams

Admin

Online Administration
Scheduling Registration
Summary Scheduling

0
Searching For Searching Info
User Information’s without Idea Search
Endorsement
System
Search results
Level-1 (a)
(b)

Level-1

(a)
(b)

5.3 UML DIAGRAMS

Unified Modeling Language:

The Unified Modeling Language allows the software engineer to express an analysis model
using the modeling notation that is governed by a set of syntactic semantic and pragmatic
rules.

A UML system is represented using five different views that describe the system from distinctly
different perspective. Each view is defined by a set of diagram, which is as follows.
• User Model View
i. This view represents the system from the users perspective.
ii. The analysis representation describes a usage scenario from the end-
users perspective.
 • Structural model view
i. In this model the data and functionality are arrived from inside the system.
ii. This model view models the static structures.

• Behavioral Model View

It represents the dynamic of behavioral as parts of the system, depicting the
interactions of collection between various structural elements described in the
user model and structural model view.

• Implementation Model View

In this the structural and behavioral as parts of the system are represented as
they are to be built.

• Environmental Model View

In this the structural and behavioral aspects of the environment in which the
system is to be implemented are represented.

UML is specifically constructed through two different domains they are:

 UML Analysis modeling, this focuses on the user model and structural model views of
the system.
 UML design modeling, which focuses on the behavioral modeling, implementation
modeling and environmental model views.

Use case Diagrams represent the functionality of the system from a user’s point of view. Use
cases are used during requirements elicitation and analysis to represent the functionality of the
system. Use cases focus on the behavior of the system from external point of view.

Actors are external entities that interact with the system. Examples of actors include users like
administrator, bank customer …etc., or another system like central database.
 UML DIAGRAMS
UML Diagram

USE-Case Diagram:
Class Diagram:
Sequence Diagram for User:
Sequence Diagram for Administrator:
Activity Diagram for Administrator:
Activity Diagram for User:
5.4 E-R MODELING
5.5. NORMALIZATION

A Database is a collection of interrelated data stored with a minimum of redundancy to

serve many applications. The database design is used to group data into a number of
tables and minimizes the artificiality embedded in using separate files. The tables are
organized to:

• Reduced duplication of data.

• Simplify functions like adding, deleting, modifying data etc..,
• Retrieving data
• Clarity and ease of use
• More information at low cost

Normalization

Normalization is built around the concept of normal forms. A relation is said to be

in a particular normal form if it satisfies a certain specified set of constraints on the kind of
functional dependencies that could be associated with the relation. The normal forms are
used to ensure that various types of anomalies and inconsistencies are not introduced into
the database.

First Normal Form:

A relation R is in first normal form if and only if all underlying domains contained
atomic values only.

Second Normal Form:

A relation R is said to be in second normal form if and only if it is in first normal

form and every non-key attribute is fully dependent on the primary key.
 Third Normal Form:

A relation R is said to be in third normal form if and only if it is in second normal

form and every non key attribute is non transitively depend on the primary key.

5.6. DATA DICTI0NARY

create table admin(username varchar2(20),

password varchar2(20) ) ;

insert into admin values('admin','admin');

create table cart(itemname varchar2(15),

price number(5),film varchar2(20) );

create table creditcheck(cno number(5),

ctype varchar2(20),
amount number(5));

insert into creditcheck values(1100,'Visa Card',20000);

insert into creditcheck values(1101,'Master Card',20000);

create table forder(orno number,

ordes varchar2(200),
amount number(5),
date1 varchar2(20),
userid varchar2(25));

create table registration(

firstname varchar2(20) not null,
lastname varchar2(20) ,
username varchar2(20) primary key,
password varchar2(20) not null,
address varchar2(40),
pin number(10),
phone number(10),
email varchar2(30) ,
type char(1),
answer varchar2(25) );

create table search(itemno number,

itemname varchar2(20),
price number(5),
type varchar2(10),
category varchar2(20),
film varchar2(20),
singer varchar2(20));

create table user_inbox(

mid number primary key,
user_name varchar2(30),
msg_from varchar2(50),
msg_subject varchar2(50),
msg_data varchar2(500),
msg_date date);

create table admin_inbox(

mid number primary key,
user_name varchar2(30),
msg_from varchar2(50),
msg_subject varchar2(50),
msg_data varchar2(500),
msg_date date);