Title:

Online Social Network

Introduction:

Online or virtual Social Network, allow people with common interests to meet, communicate and share
ideas and information, through a network like the web. While doing this, participants develop bonds with
each other and the community as a whole. Online Social Network have emerged as one of the most
potential levers of action the web. Such Social Network can be built around demographic groups -
students, parents, professional groups - doctors or programmers or who share a particular personal interest
- bikers or clock repairers.

Threaded by a common interest, community participants have a lot to share with each other. Once
established, online Social Network provides a new way for brands to reach customers with special interest
in their products. Online Social Network aims to achieve the following:

• Engage citizens in participating democracy, discuss their own issues etc.

• Encourage citizen-source journalism that complements and in some cases competes with local for-
profit news organizations

• Enable government officials to communicate with constituents more often, more easily and in a
more meaningful way

The target audience is anyone interested in local community issues/ any other issues.

How do online Social Network interact

Online Social Network interact by virtue of their shared passion. They can be found in a variety of web
destinations offering expression to interest-related activities. Like discussion forums, book sites, auction
sites, trading/exchange sites, blogs and so on. The tools used are generally message boards, blogging
applications, text chat.

The building blocks of an online community

Online virtual Social Network make use of a range of technologies that support person-to-person and
person-to-group communications. The enabling technologies facilitate two distinct types of
communication:

Real time (or synchronous) Communication: through text chat and instant messaging

Non-real time (or asynchronous) Communication: through message boards, mail lists, member and
community web pages, and surveys.

Additionally virtual Social Network also depend on a member database and may also include technologies
to support registration, electronic commerce, directories (of products, services, suppliers, etc.) and
searches (for searching member profiles, community documentation, reports, articles, transcripts,
archives,etc.).
PROJECT CATEGORY:
The category of this project is WEB APPLICATION

Tools to be used:

1. Language: PHP
2. Web Technology: PHP
3. Other tool: Wordpress
4. Web Server: Apache Server
5. IDE: Macromedia Dreamweaver
6. Database: My SQL

HARDWARE REQUIREMENTS FOR SERVER:

Processor :: INTEL P3 and above or AMD

RAM :: 512 MB and above
CACHE :: 512 KB and above
Input Device :: Mouse or Keyboard
Output Device :: VDU(minimum VGA,SVGA support) , Printer

SOFTWARE SPECIFICATION FOR SERVER:

Operating System :: Windows or Linux

Web Server :: Apache Server
Database :: Mysql 5
Language :: PHP

I am using XAMP (A software collection that has integrated Apache, Mysql and PHP) which is a
collection of all software we need in the server.

HARDWARE SPECIFICATION FOR CLIENT

Processor :: INTEL P2 and above or AMD or any processor

RAM :: 128 MB and above
CACHE :: 128 KB and above
Input Device :: Mouse or Keyboard
Output Device :: VDU(minimum VGA,SVGA support) , Printer

SOFTWARE SPECIFICATION FOR SERVER

Operating System :: Any

Web Browser :: Any

System Overview
The application that I will develop covers the following areas:
User’s Personal Details with Other Information:
o Entering Personal Professional and Social Details.
o Uploading personal image
o Storing images.
Friend search:
o Entering name or location.

Community search
o Entering name or owner.
Scrapbook:
o Select the user and write the message in his message box.
o View messages of various friend.
o Deleting Particular Departments Details.

Album
o User can store unlimited photos in his album
o User can also view others album also.

Communities
User can create community.
User can delete community
Messages can be interchanged.

Friend list
o This is the page where user can see all his joined communities.
o User can alsoremove coined communities from community list.
Chat
o User can chat with other online users.

Add friend
User can send /accept/reject friend to the desired user
Salient Features:
o A user is only allowed to enter the system through id and password. So
unauthorized access id controlled.
o A user can change his/her own password for his/her own security.
o This system provides high efficiency to manage different operation.
o It provides easy movement through the different screens.
o Multiple users can use this system after few modifications.
o Behaviour and look n’ feel of the tools can be controlled by comprehensive
administration parameters
o Web based administration for configuration, parameters, maintenance, and approval
activities
 o Web based content management and moderation tools. Moderators can approve,
moderate and maintain contents for all tools. It can be carried out online in real time for
tools like Room chat moderation, or Guest speaker chat
o Very flexible and generalized policy implementation for all tools. This policy
module controls access rights for visitors, members, respective owners of different tools
and moderators
o Active content technology, which enables any content of any tool to be pasted on
any page of the site or any other site. For example, content for a poll can be pasted in any
page within the your site, or any other site
o Very comprehensive user and usage statistics

Overall description

The Online Social Network encompasses numerous files and information from the User Database, as
well as files on the server system. This system will be completely web-based, linking to User Data
Base and the remote web server from a standard web browser. An Internet connection or as LAN
connection is necessary to access the system.

System environment

Figure 1: System Design

The Online Community Blogging web site will be operated from the web server. When an Admin
connects to the Web Server, the Web Server will pass the inform,ation to the database server . The Web
Server will then interact with the Database through BDE, which allows the Windows type program to
transfer data to and from a database.

Functional requirements definitions

Functional Requirements are those that refer to the functionality of the system, i.e., what services it
will provide to the user. Nonfunctional (supplementary) requirements pertain to other information needed
to produce the correct system and are detailed separately.

Use cases

User first log into the system if the user is registered member , otherwise the can register himself/herself
to the site, providing his/her user name , desired password and his/her every details that is required during
new user registration. If the user wants to be an unregistered member he can choose to be an unregistered
member of the site.
 During the registration a check must be made whether an user already, or duplicate user name exists, then
an error message is sent to the user.
After the registration process is over user can log into the system with his /her user id and password.
A check must be made, to verify the password of specified user against the database, otherwise an error
message is sent to the user.
After the user successfully logs in the system, he/she can update the profile, manage the community, post a
message, or even can retrieve a message.
(Note : An unregistered user cannot perform this operation. He/She can only view a message.).

Home Page

Figure 2: Home Page

Brief Description
The Web Server is waiting on an User to connect.

Initial step-by-step description

For this use case to be initiated, the User must be connected to the Internet/LAN and connected to
the Web Server.
1. The User connects to the Web Server.

2. The User selects the User link on the home page.

3. The Web Server passes the User to the User Home Page.

Log in
Figure 3: Login

Brief Description
The Web Server is waiting on an User to connect.

Initial step-by-step description

For this use case to be initiated, the User must be connected to the Internet and connected to the
Web Server.
• The User connects to the Web Server.

• The User selects the User link on the home page.

• The Web Server passes the User to the User Home Page.

• User id & password is given by the user.

• Admin checks both of them (Checking is generally done against the Database).

• If the information provided by the user is correct, it grants the access to the user otherwise
sent a error message to the user.

Add new entry

Figure 4: Add a new entry to Database

Brief Description:
The User chooses to create a new entry on the Entries page.

Initial step-by-step description.

For this use case to be initiated the User must be connected to the Internet and on the Entries page.
• The User selects the “Add a New User” link.

• The Web Server returns the “Add a New User Form.”

• The User fills in the form.

• The User can choose which fields to make public or private.

• The User clicks submit.

• The Web Server checks to see if all required fields contain data.

• If all required fields contain data the Web Server adds the data to the User Database.

• If a required filed is empty the Web Server returns the form to the User with a message.

• The Web Server returns the User to the User Home Page.

Update & Entry

Figure 5: Update & Entry

Brief Description:
The User chooses to update an existing entry in the User Database.

Initial step-by-step description:

For this use case to be initiated the User must be connected to the Internet and on the User Home
page.

• The User chooses the “Update User Information” option.

• The Web Server presents the User with a form.

• The Web Server searches the User Database for the User name and password.

• The Web Server returns the User’s data if the password matches.

• If the password does not match the Web Server returns an error message and
returns the User to the previous page.

• The User changes the appropriate fields and clicks submit.

• The Web Server replaces the old data with the new.

• The Web Server returns the User to the User Home Page.

Initialize Blog & Visit

Figure 6: Initializing Blog and Viewing

Brief description:
The User chooses to View or Post a message..

Initial step-by-step description:

For this use case to be initiated the User must be connected to the Internet and on the User Home
Page.

Case 1:
♣ User chooses to enter as a registered User.
♣ User can post a message.
♣ User can modify existing ones
♣ User can send a reply message to the post of other user.
♣ User cannot send a reply to its own post.

Case 2:
• User chooses to Enter as a unregistered User.
• User can view the message.
• User cannot modify the post
• User cannot send a reply message unless he/she is a registered user.

Search
Figure 7: Search a Community

Brief description:
The User chooses to Search Community.

Initial step-by-step description:

For this use case to be initiated the User must be connected to the Internet and on the User OCB
Home Page.

• The User chooses “Search.”

• .The User fills in the form and clicks submit.

• The Web Server queries the User Database for the requested information.

• The Web Server returns all related results

• The User chooses a particular result

• If the User requested is not in the User Database, if there is no related for the requested User, the
Web Server will return a message that the requested “Result can not be found”

• The Departmental Server will return a message containing either a result of execution or
“Result can not be found”.

System Analysis:

Systems development can generally be thought of as having two major components, in which one such
component is Systems Analysis. Systems analysis is the process of gathering and interpreting facts,
diagnosing problems and using the information to recommend improvement to the system. Analysis is a
detailed study of the various operations performed by a system and their relationship within and outside of
the system. One aspect of analysis is defining the boundaries of the system and determining whether or
not a candidate system should consider other related systems. During analysis, data are collected on the
available files, decision points, and transactions handled by the present system. Data flow diagrams,
interviews, on-site observations and questionnaires are commonly used tools in analysis. We can say that
analysis specifies what the system should do. System analysis is the management technique, which helps
us in designing a new system, improving an existing system or solving a system problem.

There are key strategies for eliciting information regarding the user’s requirements:-
(i)Asking, (ii) getting information from the existing information system, and, (iii) prototyping.
Asking:
This strategy obtains information from users by simply asking them about the requirements. It
assumes a stable system where users are well informed and can overcome in defining the problem. There
are three key asking methods ,-
(i) Question may be open-ended or closed? An open ended question allows the respondent to
formulate a response. It is used feeling or opinions are important.
A close question requests are answer from a specific set of responses. It is used when
factual responses are known.
(ii) Brainstorming is a technique used for generating new ideas and obtaining general
information requirements.
(iii) Group consensus asks participants for their expectations regarding specific variables.

GETTING INFORMATION FROM THE EXISTING INFORMATION SYSTEM

Determining information from an existing application has been called the data analysis approach. It
simply asks the user what information is currently received and what other information is required. It
relies heavily on the user to articulate information needs. The analyst examines all reports, discusses
with the user each piece of information examined, and determines unfulfilled information needs by
interviewing the user. The analyst is primarily involved in improving the existing flow of data to the
user.

PROTOTYPING
The third strategies for determining user information requirements are used when the user can’t

establish information needs accurately before the information system to build. The reason could be the

lack of an existing model on which to have requirements or a difficulty in visualizing candidate systems.

PLANNING THE DEVELOPMENT PROCESS:

The development of the software has been done by the following the steps of Software Development Life
Cycle. Development of the software was deemed essential and the particular solution has been adopted
after devising the alternative solutions of the problem and conducting feasibility tests on all of them.

First, the Software Requirements Specification has been done. The preliminary requirements
determination, followed by the requirements specification, data flow design, functional requirements
determination has been conducted.

The next step is System Design. The Data Flow Diagram (DFD) and Entity– Relationship (ER)
diagram are to be created in this phase. While the former identifies the major transformations and clarifies
system requirements, the latter provides us with representation of the schemas. In this phase, the
organization of forms and reports and a detailed description of the activities of the system have been
provided.
REQUIREMENTS SPECIFICATION:

Requirements Specification involves the basic requirements that the system to be developed
should posses. These can be broadly classified into two types.
1. Performance Requirements.
2. Functional Requirements.

Understanding the requirements specification is critical for the projects success otherwise the system does
not get developed according to the customer’s wishes.

Functional Requirements:

Home Page

Use Case Name: Access Home Page

Priority Essential
Trigger Menu selection
Precondition Admin is connected to the Internet and on
the home page
Basic Path End User sends request to the admin.
The Web Server presents the Admin with
home Page.
Alternate Path N/A
Postcondition The Admin allow access to the user
Exception Path If there is a connection failure the Web
Server returns to the wait state

Login

Use Case Name: Log in

Priority Essential
Trigger Selects
Precondition The User is connected to the Internet and
on the Home Page
Basic Path • The Web Server presents the user
with a form.
• The user fills in the form and click
submit
• The Web Server checks to see if
all required fields are correct by
checking with the database.
• If the required fields are correct,
the web server welcome the user .
• If any of the required fields are
 not correct, the Web Server
returns a message and returns the
Admin to the Survey form.
Alternate Path N/A
Postcondition The can interact with all communities
Exception Path • If the connection is
terminated before the
form is submitted, the
fields are all cleared
and the Web Server
is returned to the wait
state.

Add a new entry

Use Case Name: Create a new entry

Priority Essential
Trigger Menu selection
Precondition The User must be connected to the
Internet and on this new registration page.
Basic Path • The User click on
add a new entry.
• The Web Server
returns a form.
• The user fills in the
form and clicks
submit.
• The Web Server
checks to see if any
required field is
empty.
• If any required field
is empty the Web
Server will send a
message and return
the new entry form
page.
• If no required field is
empty the Web
Server will create a
new record in the
Admin Table in the
Admin Database,
and return the User to
the Home Page.
Alternate Path N/A
Postcondition A record is created in the Admin Table of
 the Admin Database.
Exception Path  If the connection is terminated before
the form is submitted, the fields are
cleared and the Web Server is
returned to the wait state.
 If the connection is terminated after
the form is submitted, but before the
Admin is returned to the Home Page,
the record is created in the Admin
Table of the Admin Database.

Update an Entry

Use Case Name: Update an Entry

Priority Essential
Trigger Menu selection
Precondition The User must be connected to the Internet
and on the edit profile Page.
Basic Path o The User clicks on update an entry
link.
o The Web Server returns a form.
o The User enters his/her profile details.
o The Web Server queries the Admin
Database and returns a table.
o The Web Server returns a form with
the data for that user in it and a message
to update the data they wish and click
submit.
o The Web Server with replaces the old
data with the new data and returns the
User Home Page.
Alternate Path New Data will be available.
Post condition The record in the Admin Table of the Admin
Database has been updated and the Admin is
returned to the Home Page.
Exception Path • If the connection is
terminated before the
form is submitted,
the fields are cleared
and the Web Server
is returned to the wait
state.
• If the connection is
terminated after the
form is submitted,
but before the Admin
is returned to the
 Home Page, the
record in the Admin
Table of the Admin
Database is updated
and the Web Server
is returned to the wait
state

Initialize and visit

Use Case Name: Search for a community

Priority If user wants.
Trigger Menu selection
Precondition The User is connected to the Internet and on
the Home Page
Basic Path Case 1:
♣ User chooses to enter as a registered
User.
♣ User can post a message.
♣ User can modify existing ones
♣ User can send a reply message to the
post of other user.
♣ User cannot send a reply to its own
post.

Case 2:
• User chooses to Enter
as a unregistered User.
• User can view the
message.
• User cannot modify
the post
• User cannot send a
reply message unless he/she is a
registered user.
Alternate Path N/A
Postcondition The user writes it down, what ever he/she
wants to write in the blog. And his/her
comments can be shown by all others
viewers.
Exception Path o If the connection is
terminated before the
comments is
submitted, the fields
are cleared and the
Web Server is returned
 to the wait state.
o If the connection is
terminated after the
comments is
submitted, but before
the Admin is returned
to the Home Page, the
record is created in the
Admin Table of the
Admin Database.

Search for a community

Use Case Name: Search for a community

Priority If user wants.
Trigger Menu selection
Precondition The User is connected to the Internet and on
the Home Page
Basic Path a) The User chooses “Search.”
b) .The User fills in the form and
clicks submit.
c) The Web Server queries the User
Database for the requested information.
d) The Web Server returns all related
results
e) The User chooses a particular
result
f) If the User requested is not in the
User Database, if there is no related for
the requested User, the Web Server will
return a message that the requested
“Result can not be found”
g) The Departmental Server will
return a message containing either a result
of execution or “Result can not be
found”.
Alternate Path N/A
Postcondition The Admin receives the information on the
requested community, returns the requested
result , If not found show a message
Exception Path o .If the connection is
terminated before the
form is submitted, the
fields are cleared and
the Web Server is
returned to the wait
state.
o If the connection is
terminated after the
form is submitted, but
before the Admin is
returned to the Home
Page, the record is
created in the Admin
Table of the Admin
Database.
Class Diagram:

Administrator
name:String
designation:String
NEW USER
insert()
delete()
update() newUsername:Stri
validateLogin() ng
newPassword:Stri
USER ng

createId()
username:String createPassword()
password:String
ONLINE
passwordValidati COMMUNITY
on()
registrationReque date:Date
st() time:Int
month:String
day:String
year:String
communiity:String
username:String GUEST
userPreference:String

getValue()
putInformation() Register()

SITE
DETAILS FRIEND NEW
COMMUNITY SEARCH BLOG
details:Strin username:Stri
ng username:String blog:String username:Stri
g username:Stri ng
ng time:Int
viewDetails() addFreind()
ignoreUser() createCommunit searchBlog() createBlog()
y() searchFriend() viewBlog()
createBlog()
viewBlog()
Sequence Diagram:

Design

login Usr database search

user Info database

Request to login
Checks validity

Access granted

Search for specific information

If available

supplied
info displayed

Administrator Sequence Diagram

Administrator User Database Administrator Database Blog DataBase

checking if user

grant or deny

checking if
administrator

grant or deny

insert/update/delete
USECASE Diagram:

Registration

Query

Grant

User Administrator

View

Modify
CONCLUSION

The need of the project is to keep the information of Patient, Doctor Details in database or how the
whole thing can be atomized. The administrator of the agency is given a facility to access information
about Patient, Doctor Details within a short period of time.

The objective of the System is to automate the process of Hospital. The objectives are:

o To enable correct information about Patient, Doctor, Discharge.

o To provide accurate and timely information at various levels to assist
administrator in effective decision-making
o To provide user-friendly system with GUI.

The system was tested by running it on different computers. The system has a high degree of
accuracy and user friendliness. A few changes were suggested which is to be incorporated into the system.

The system is a user-friendly system and further changes can be incorporated into the system
easily.

Doing this project has made me learn not only a new technology but also it has made me more
knowledgeable in the software engineering activities, which are carried out in the organization. It was a
great learning experience.
BIBLIOGRAPHY
0-Level Context

Send Request

0.1
USE Communit
R y
Send Request

Detailed 0.1(Level 1)
 0.1.5

User DB
Registry
0.1.3
0.1.4
User 0.1.2 Verif
y Post
Scrap
Login
0.1.5

0.1.12 View
Scrap DB
Scrap
Add
Friends 0.1.6
Delet
0.1.13 e
Friend DB Delete Scrap
Friends 0.1.7

0.1.14 Update
Profile
Profile DB
View
Friend List 0.1.8
View
0.1.15 Profil
Scrap DB e
View
Friends 0.1.9
Scrap Create
Communit
0.1.16 y
View 0.1.10 Community DB
Friends Delete
Album Communit
y
Album DB
0.1.17 0.1.11
Creat
e/Vie Join/Leave
w Communit
Albu y
m

Detailed 0.1.5(Level 1)
 0.1.5.1 0.1.5.2

Registry
Verify
USER

0.1.5.3

Create User DB
Social
Profile

0.1.5.4

User_Prof DB Create
Professional
Profile

0.1.5.5 0.1.5.6

Create
Personal User
User_Pers DB Home
Profile
ERD
education un
school F_un
Frnd_

college
User_prof m have
accepted
has sender
un
1
fname
1 1 lname m receiver
occupation have
1 scrap
un user
Scr_tm
1 msg
un city
1
has
Scr_dt
User_per
Favourite state
movie

about
Favourite
book Ph no

img
Favourite
novel
hobbies email

1 m

hav owner
e
C_type
hav
e
m

un community
m

C_name
album C_img

img