PROJECT REPORT

ON
SOCIAL NETWORKING MANAGEMENT
SYSTEM

Session: 2010-11

Submitted To: Submitted By:

Lect. Mr. G. Mahesh Maninder Singh

Roll no: RA3002A04

Sec: A3002

Class: MCA (HONS.)

1
 ACKNOWLEDGEMENT

Our first experience of project has been successfully, thanks to the support
staff of many friends & colleagues with gratitude. We wish to acknowledge
all of them. However, we wish to make special mention of the following.

First of all we are thankful of our project guide Mr. G.Mahesh Sir
under whose guideline we were able to complete our project. We are
wholeheartedly thankful to him for giving us value able time & attention &
for providing us a systematic way for completing our project in time.

We must make special mention of Mr. G.Mahesh Sir our project in

charge for their co-operation & assistance in solving a technical problem.
We would thank to our H.O.D. Miss. Kuljeet Kaur & all lab maintenance
staff for proving us assistance in various h/w & s/w problem encountered
during course of our project.

2
 TABLE OF CONTENT

S. No. Contents Page Remarks

No.
1 Introduction 4
2 Preface 5

3 Process description 6-9

4 Existing system 10
5 Scope of project 11

6 ER-Diagram 12

7 Data Flow Diagram 13-14

8 Problem analysis 15-17

9 System design 18
10 Software Requirement Specification(SRS) 19
11 Testing 20-21
12 Implementation 22
13 Project Legacy 23

14 PSEUDO CODE 24-26

15 Output 27-36

16 Advantages 37
17 Bibliography 38

3
 INTRODUCTION

Social Networking Management System covers the entire concepts that are
required to setup a Social network, that can have one or more social sites
available for society use but here we will create only one site. Social sites
consist of a number of individuals or organizations known as “nodes”.

All nodes are connected to other nodes by specific relations or

interdependencies like friendship, common interest, knowledge, etc.

It also provides the facility of maintaining the Chat history, Mail history
of users in well organized manner so that it can be extracted and seen by user
easily.

4
 PREFACE

The journey of a thousand miles starts with a single step. This project is the
first milestone in the journey of our technical experience.

The information highway has brought an era where intricate problems are
being solved in a fraction of second. The present age is “The Age of
computers”. The computer technology has entered into every walk of life.
The increasing number of computers can be seen employed in offices,
hospitals, railways, banking and a lot more places. Computers not only
allows the enhancement in computation speed but also have bought in
considerable cost effectiveness.
It is important to develop a correlation between the practical and theoretical
aspects of the subject studied. It is more relevant in the field of computers.
Thus in order to test, implement and use the various techniques studied, this
project called “SOCIAL NETWORKING MANAGEMENT SYSTEM”
was taken up that has innumerable advantages over manual car service
centre.

Maninder Singh
REG. NO: - 11009884

5
 PROCESS DESCRIPTION

In this project I will divide the project in two modules listed as:

1. Database maintenance.

2. Communication.

In first module (Database Maintenance), I will divide this module into two
parts: -
1. Personal_Detail.
2. Address.

And

In second module (Communication). I will divide this module into two parts:-

1. Mail_History.
2. Chat_History.

1) First module(Database maintenance):-

I will construct database using ORACLE 10g that will contain the
complete information of the social site users. This will contain the
Personal _Details of the user like: - Name, User_Name and User_Password,
Age, DOB, Nationality in Personal_Detail table. Settings will be done in
such a manner that this information will be stored with privacy settings so
as to provide security to the personal information of users as well as to
avoid any damage to the information.

6
 Personal_Detail: -

Address of the user: - Name, City, State, Place, Phone_No, etc.

2) Second module (Communication): -

I will create and control communication between users like maintaining

Mail_History and Chat_History, etc. will be provided to the user. These
facilities can be seen by users having authorisation at any time in future.

For these purposes, every user will be provided with a different User_Name
and User_Password. This User_Name and User_Password will be used by
user to access the site.

7
Mail_History: - Name, Sent_Id, Receiver_Id, Sent_Date, Receiver_Date.

Chat_History: - Name, Sent_Id, Receiver_Id, Sent_Date, Receiver_Date.

The fields Name will be used in both the modules as it will be the only unique
identification of users.

In this project, we will use ORACLE 10g for storing a database as a backend
and Frontend is not implemented but in future it will be implemented.

8
 PROPOSED SYSTEM

Proposed System: Computerized database is much more efficient than

manual database.

a) Computer has large storage capacity. It can store thousands of records at

a time.

b) It provides high speed and accuracy.

c) Data can be stored in the computer in the form of files and records.

d) It provides the facility of searching a particular record and many other

types of searching.

e) It is very user-friendly.

f) It reduces the cost of designing.

9
 EXISTING SYSTEM

Existing System: Existing System is also known as Manual System. Manual

Database is the record keeping system in which we manages whole database
without any support of computer system. The main drawbacks of this system
are:

1. Duplication of data.

2. It is very difficult to maintain the whole database in the form of

records and files in paperwork.

3. There is no facility of searching a particular record, If we can search

any document, then we can search whole record.

4. Very time consuming process.

10
 SCOPE OF PROJECT

This project can widely be used as a backend for social site to store and
maintain the complex data of users in database in very simple manner.

It also provides the facility of maintaining the Chat history, Mail history
of users in well organized manner so that it can be extracted and seen by user
easily.

It also provide the facility of maintaining the Personal detail, Address of

users in well organized manner so that it can be extracted and seen by user
easily.

11
ER-DIAGRAM

12
 DATA FLOW DIAGRAM

A DFD, also known as “bubble chart” has the purpose of clarifying system
requirements and identifying major transformations that will become
programs in system design. So it is the starting point of the design phase that
functionally decomposes the requirements specifications down to the lowest
level of detail. A DFD consists of a series of bubbles joined by lines.

Data Flow: An arrow represents a data flow: it represents the path over which
data travels in the system. A data flow can move between processes, flow into
or out of data stores, to and from external entities.
Bubbles (Process): A circle or bubble represents that transforms data from
once from to another by performing some tasks with the data.
Data Store: A data store is a place where data is held temporarily from one
transaction to the next or is stored permanently.
External Entity: Which defines a source or destination of system data also
called an external entity.

13
14
 PROBLEM ANALYSIS

PROGRAM SPECIFICATION

After the broad stages or modules for a system have been define did this
necessary to move to preparation of detailed DATABASE specification. The
programs or modules are defined according to the functions they perform, not
by the size of the DATABASE. The breakdown of database into smaller
modules makes it easier to debug a system and modify it. Database
Specification must be developed for each module, which involve table name,
purpose for the tables, owner of the project and general information about the
project.

The project development process include three important stages namely

program design, program coding and program testing. All three stages
contribute to the production of high quality program. In this chapter the
techniques used for any designing any program coding testing has been
discussed.

Database design is the foundation for a good program and is therefore an

important part of the database development cycle. Before creating a database
should be well conceived and all aspects of the database design should be
consider in details.

 Problem Analysis

 Feasibility Analysis

15
 PROBLEM ANALYSIS

This process is adopted when management of the system development,

Personnel decide that the particular system needs improvement. The system
development life cycle is the set of activities, carried out by the analyst,
designers and users to develop and implement a system. The systems that are
present in the nature follow common life cycle pattern.

 Select ion and identification of the system to be studied.

 Preliminary study.

 Defining the system.

 Design and development of the system.

 Implementation of the system.

16
 FEASIBILITY ANALYSIS

Analysis and evaluation of a proposed project to determine if it (1) is

technically feasible, (2) is financial feasible. Feasibility analysis is almost
always conducted where large sums are at stake is also called Feasibility
Study.

1. FINANCIAL ANALYSIS

The objective of financial analysis is to ascertain whether the proposed

project will be financially viable in the sense of being able to meet the
burden of servicing debt and whether the proposed project will satisfy the
return expectations of those who provide the capital. While conducting a
financial appraisal certain aspects has to be looked into like:

- Investment outlay and cost of project

- Projected profitability
- Cash flows of the project
- Projected financial position

2. TECHNICAL ANALYSIS

The issues involved in the assessment of technical analysis of the proposed

project may be classified into those pertaining to inputs, throughputs.

1. Input Analysis: - Input analysis is mainly concerned with the

identification, quantification and evaluation of project inputs, that is,
machinery and materials. You have to ensure that the right kind and
quality of inputs would be available at the right time and cost
throughout the life of the project.
2. Throughput Analysis: - It refers to the production/operations that you
would perform on the inputs to add value. Usually, the inputs received
would undergo a process of transformation in several stages of
manufacture.

17
 SYSTEM DESIGN

Then we began with the design phase of the system. System design is a
solution, a “HOW TO” approach to the creation of a new system. It translates
system requirements into ways by which they can be made operational. It is a
translational from a user oriented document to a document oriented
programmers. For that, it provides the understanding and procedural details
necessary for the implementation. Here we use Flowchart to supplement the
working of the new system. The system thus made should be reliable, durable
and above all should have least possible maintenance costs. It should overcome
all the drawbacks of the Old existing system and most important of all meet the
user requirements.

18
 SOFTWARE REQUIREMENT
SPECIFICATIONS

1) Hardware Requirements:

 Pentium III 500 MHz processor or compatible.

 128MB RAM (Minimum)/256MB RAM (Recommended).
 1GB Hard disk.
 Recommended: 1024 X 768, High Colour 16-bit.
 Keyboard.
 Mouse.

2) Software Requirements:

 Windows Operating System XP \ NT\ Windows Vista\Window 7, etc.

 SQL, PL/SQL, ORACLE 10g.

19
 TESTING

Testing is the major quality control measure employed during software

development. Testing is the process of executing a program with the intent of
finding an error. No piece of code is completely ready unless it has been fully
tested. This stage is very important as at this stage it is verified whether the
code developed meet the requirement specifications or not. Moreover, all
validations are also checked in the testing stage.

Need for Testing:

 Testing is vital to the success of the system. Testing makes a logical

assumption that if all parts of the system are Correct, the goal will be
successfully achieved. Inadequate testing or non-testing leads to errors
that may not appear until months later. A small system error can
conceivably explode into a much larger problem effective testing early
in the process translates directly into long-term cost saving from a
reduced number of errors.

 Second reason for testing is its utility as a user-oriented vehicle before

implementation.

 Finally, testing leads to software reliability. Identifying and removing

faults, during testing can make the software more reliable. This increases
user’s confidence in the system.

20
 The basic levels of testing are: -

1. Unit testing.
2. Integration testing.
3. System testing.
These different levels of testing attempt to detect different types of faults. The
relation of the faults introduced in different phases, and the different levels of
testing are shown: -

1) Unit Testing:
The first level of testing is unit testing. In this different modules are tested
against the specifications produced during design for the modules. Unit testing
is essential for verification of the code produced during the coding phase and
hence the goal is to test the internal logic of the modules.

2) Integration Testing:
The next level of testing is often called integration testing. In this many tested
modules are combined into sub-systems, which are then tested. The goal there
is to see if the modules can be integrated properly, the emphasis being on
testing interfaces between modules. This activity can be considered as testing
the design, and hence the emphasis on testing module interactions.

3) System Testing:
The next level of testing is system testing. Here the entire software system is
tested. The reference document for this process is requirement document, and
the goal is to see if the software meets its requirements. This is essentially a
validation exercise.

21
 IMPLEMENTATION

System implementation is the stage when the user has thoroughly tested the
system and approves all the features provided by the system. The various tests
are performed and the system is approved only after all the requirements are
met and the user is satisfied.
The new system may be totally new; replacing an existing manual or
automated system, or it may a major modification to an existing system. In the
either case, proper implementation is essential to provide a reliable system to
meet organization requirements .successful implementation may not guarantee
improvement in the organization using the new system (that is a design
question) ,but improper will prevent it.

22
 PROJECT LEGACY

Project legacy is followed by following two terms:

i) Current Status

ii) User Manual

i) Current Status:

The project is developed in environment of ORACLE 10g. The project is

tried to be completed. All entries are have been maintained properly in the
tables. Hence the project is ready to use by the user.

ii) User Manual:

The project has been developed in such a way that user can easily use it.
To use this project user has to follow following steps:

 Download ORACLE 10g on the system.

 Double click on installed package of ORACLE or SQL.

 Fill the Username and Password on the input page.

 Select ORACLE 10g command page.

 Enter the query with proper syntax.

 Run or Execute.

 Output will be on screen.

23
 PSEUDO CODE

Create Personal_Detail table:

create table Personal_Detail (Name char(20) Primary key,User_Name varchar(20),

User_Password varchar(20) NOT NULL, Nationality varchar(20),Dob date, Age
Varchar(20));

Insert into Personal_Detail table:

insert into Personal_Detail values('Maninder Singh',

'[email protected]','123a','Indian','12-dec-2010','21');

Create Address table:

create table Address(Name char(20) REFERENCES Personal_Detail(Name),City

varchar(20),State varchar(20),Place varchar(20),Phone_No number(20));

Insert into Address table:

insert into Address values('Maninder Singh','Pathankot','Punjab','Mamun

Cantt','9876748928');

Create Mail_History table:

create table Mail_History

(Name char(20) REFERENCES Personal_Detail(Name),Sent_Id varchar(20),Receiver_Id
varchar(20),Sent_Date date,Receiver_Date date);

Create Chat_History table:

create table Chat_History

(Name char(20) REFERENCES Personal_Detail(Name),Sent_Id varchar(20),Receiver_Id
varchar(20),Sent_Date date,Receiver_Date date);

24
Create view fullPersonal_detail:

create view fullPersonal_detail as select

User_Name,User_Password,Nationality,Dob,Age,City,State,Place,Phone_No from
Personal_Detail,Address where Personal_Detail.Name=Address.Name;

Implementation of Cursor for Personal_Detail:

declare cursor c1 is
select Name,User_Name from Personal_detail where User_Password='123a';
rec c1% rowtype;
begin
open c1;
loop
fetch c1 into rec;
exit when c1%notfound;
if c1%found then
dbms_output.put_line('P_Name'||' '||rec.Name);
dbms_output.put_line('U_Name'||' '||rec.User_Name);
end if;
end loop;
close c1;
end;

Implementation of Cursor for fullPersonal_Detail:

declare cursor c3 is
select User_Name,Age,State,City from fullPersonal_detail where User_Password='saa';
rec3 c3% rowtype;
begin
open c3;
loop
fetch c3 into rec3;
exit when c3%notfound;
if c3%found then
dbms_output.put_line('P_Name:'||' '||rec3.User_Name);
dbms_output.put_line('P_Age:'||' '||rec3.Age);
dbms_output.put_line('P_State:'||' '||rec3.State);
dbms_output.put_line('P_City:'||' '||rec3.City);
end if;
end loop;

25
close c3;
end;

Implementation of Full outer join for Personal_Detail and Address:

select * from(Personal_Detail Full outer join Address on

Personal_Detail.Name=Address.Name);

Implementation of Left outer join for Personal_Detail and Mail_History:

select * from(Personal_Detail Left outer join Mail_History on

Personal_Detail.Name=Mail_History.Name);

Implementation of Trigger for Personal_Detail:

CREATE OR REPLACE TRIGGER CUS

BEFORE UPDATE
OF Name,User_Password
ON Personal_Detail
FOR EACH ROW
BEGIN
:NEW.Name := UPPER (:NEW.Name);
:NEW.User_Password := UPPER (:NEW.User_Password);
END;

26
 OUTPUT

OUTPUT FOR PERSONAL_DETAIL TABLE:

27
OUTPUT FOR ADDRESS TABLE:

28
OUTPUT FOR MAIL_HISTORY TABLE:

29
OUTPUT FOR CHAT_HISTORY TABLE:

30
OUTPUT FOR VIEW FULLPERSONAL_DETAIL:

31
OUTPUT OF CURSOR C1 FOR PERSONAL_DETAIL:

32
OUTPUT OF CURSOR C3 FOR PERSONAL_DETAIL:

33
OUTPUT OF TRIGGER CUS FOR PERSONAL_DETAIL:

34
OUTPUT OF FULL OUTER JOINS FOR PERSONAL_DETAIL &
ADDRESS:

35
OUTPUT OF LEFT OUTER JOINS FOR PERSONAL_DETAIL &
MAIL_HISTORY:

36
 ADVANTAGES:-

 This project is very useful for Social network sites.

 Gives a better service.

 This project can widely be used as a backend for social site to store and
maintain the complex data of users in database in very simple manner.

 It also provides the facility of maintaining the Chat history, Mail history,
Personal detail of users in well organized manner so that it can be
extracted and seen by user easily.

 It also provides the facility of security.

37
 BIBLIOGRAPHY

BOOKS:

 Author: H. F. Korth, & S. SudarshanA. Silverschatz, Title:

Database System Concepts, Publishers: Tata McGraw Hill.
 Lyan Bayross, SQL, PL/SQL .The Programming Language of
Oracle, BPB Publication.

38