INTRODUCTION

1.1 Introduction to the technology:

The technology basically extracts the IP address of the machine from which a breach is
being made into a users social account and sends the IP address as a text message to the user. It
also refines internet searches by making alias identification possible.

1.2 Statement of problem:

Prevention of unauthorized access of social accounts through web and mobile devices
and enabling the authorized users to find their friends by even giving the alias/nick names in the
query.

1.3 Objective of the project:

Preventing cyber crimes and theft, making social accounts safe and alias identification.

1.4 Methodology:
We make prevention of unauthorized access possible by extracting the IP address of the
machine from which the breach is being made and then delivering this IP address along with a
warning message to the user.

1.5 Limitations of the project:

If the user himself enters a wrong password multiple number of times he/she would get a
warning message.
Location of the machine from which the breach is being made is hard to extract only its
IP address can be obtained.

CHAPTER 2

LITERATURE SURVEY
2.1 Methods and Theories:
In our application the user is supposed to register and then he/she can login by giving the
appropriate username and password. After this the user can edit his friend list and other profile
information. At the time of incorrect login the user will get a message intimating about the
suspicious activity going on in his account. User can search his friends by giving their possible
known popular nick names by which search results are minimized and exact results are obtained.

2.2 Existing and Proposed Technology:

2.2.1 Existing System:

In the existing system of tracking the suspicious activity if intruder knows the username
and he/she starts guessing the password and these activities will not be known by the legal user.
In the social networking sites if a person is searching a friend with a particular known
name and if that user is registered by some other say alias name then he/she wont be traceable.
These are the some of the problems that are faced in present existing system.

2.2.2 Proposed System:

In our problem statement we are trying to solve the said above problem. At first about the
suspect tracking, we will be sending a text message to the authenticated users mobile about the
suspicious activity. Upon which he/she can take the protective measures.
In the second problem said above, as the user will be registering to our social networking
site he/she must provide theres popular nick/alias names so that they can be even found when
searched by their nick names.

2.3 Ideas of Design and Implementation:

Because of frequent reports of account breaches being made in social networking
accounts we came up with this idea to eradicate this problem to the maximum extent possible.
Our exhaustive work on this concept will surely help in reducing the number of such security
breaches.
Due to the suspicious activity and threats spread over WWW the continues call for
prevention of the security breaches. Here we have referred from many previous inventions that
have been done in order to prevent this insecurity.

CHAPTER 3
TECHNOLOGY USED
3.2.1 Php:
PHP is a scripting language originally designed for producing dynamic web pages. It has
evolved to include a command line interface capability and can be used in standalone
graphical applications.
It is a widely-used general-purpose scripting language that is especially suited for web
development and can be embedded into HTML.
PHP generally runs on a web server, taking PHP code as its input and creating web pages
as output. It can also be used for command-line scripting and client-side GUI
applications.
From PHP 4, the PHP parser compiles input to produce byte code for processing by the
Zend Engine, giving improved performance over its interpreter predecessor.

3.2.2 My Sql:
MySql is a multithreaded,multi-user SQL database management system (DBMS). The
basic program runs as a server providing multi-user access to a number of databases.
The data in MySql is stored in database objects called tables. A table is a collection of
related data entries and it consists of columns and rows. Databases are useful when
storing information categorically.
With MySql, we can query a database for specific information and have a record set
returned.
Before you can access data in a database, you must create a connection to the database. In
PHP, this is done with the mysql_connect() function.

CHAPTER 4
SOFTWARE REQUIREMENT SPECIFICATION

4.1 Introduction:
 The purpose of this document is to present detailed description of the project titled
preventing unauthorized access of social accounts through mobile devices. The intended users
can get the messages if any unauthorized access is made to their mail or social accounts. SRS is
intended for the users, developers and Project review committee. This application is known as
preventing unauthorized access for social accounts or mail accounts. It is a web based
application.
This application provides users to create account and if any suspicious activities in their
account will be intimated to them by a message using their mobile numbers. The main point of
the project is to search their friends with any nick name known and still the user will be able to
get the intended search.

4.2 The Overall Description:

4.2.1 Product perspective:

Fig 3.1 Product Perspective

Our product makes uses of normal mining and database concepts in order to maintain the
data. It makes use of pattern searching technology to give the intended result even when the nick
names are given for searching. There are no such products available that provides proper result
even on giving nick names. If unauthorized access is done to any other users account message
are sent to the legal user. Here it makes use of networking protocol in order to send the messages.
4.2.2 System Interface:
The application is going to be developed using wamp server and its packages. The
application will be developed in php language by making use of different packages.

4.2.3 Interfaces:
There is a GUI and no command line interface. The GUI is required for accepting the
users username and password. When there are some exceptions raising error like entering
invalid username and password, then error messages will be displayed prompting the users to re-
enter the details.

4.2.4 Hardware Interfaces:

The application can be built on any machine which supports 32 bit or 64 bit operating
system. As the suspect users details are sent as messages, it can work on any cell phones even
on a recent technology android but we are not implementing on android phones.

4.2.5 Software Interfaces:

The application makes use of wamp server 5.2. It is going to be built on php(hypertext
pre processor). In order to store the data, the application uses MySQL 13 database which is
supported by wamp server.

4.2.6 Memory Constraints:

No such memory constraints involved. Any computers having a normal 250 mb of
memory can be used to run the application. The mobiles having any operating systems with
minimum memory is sufficient to deploy the services.

4.2.7 Operations:
User: He/She is responsible for logging in.
Administrator: He will be responsible for authentication of user. Also responsible for extracting
the proper intended search result given the query using nick names. Also responsible for sending
messages to the authorized user if any suspicious activities are done in their account.
4.2.8 Site Adaptation Requirements:
The user must have social site account. We are not modifying any details of the user in
his account, but only extracting the required details from it.

4.2.9 Product Functions:

Register to the site.
Validate the user through his username and password.
Issue a query with known possible nick names.
The interface will interact with database and provide the appropriate result.
Send the result back to the user.
If unauthorized access made to any of the users account, detect the particular system.
Send the message to the authorized user about the suspicious activity.

4.2.10 User Characteristics:

Intended users must have basic knowledge of getting registered to the networking site.
The user must have his account in the social site created.

4.2.11 Constraint:
User must have an account in the social networking site created.
In order to get the information of hacking his account, user must possess a mobile device.
The user must provide his nick name during registration, so that given query for
searching a friend with nick name will be easy.
In case of unauthorized access, it is not possible to detect the person who is doing such
activity.

4.2.12 Assumptions and Dependencies:

In this application, it is assumed that a person in the social networking site keeps his
details updated such as his name and location etc.

4.2.13 Apportioning of Requirements:

Quality Requirements:
Correctness: The system should work correctly until the intended results are obtained. For
example until the user gets the specified person it must work correctly.
Reliability: The database must be updated and must work all the time unless in case of extreme
circumstances.
Efficiency: This depends on internet speed. The higher the speed better is the efficiency.
Integrity: The application uses the users username and password hence they need to be secured.
Usability: The application must be usable by most of the users who are familiar with social sites.
Flexibility: It is most important as the application must run on any browser provided. The
application has admin supervision and also users activities that can run on any platform.
Portability: since the suspicious activities are informed through message on cell phone, it will
support any cell phones and the social networking site is also capable of working in any
platform.
Reusability: The system source code can be extended to provide many more features that are
specific to a particular situation.

Safety Requirements: Since the users getting registered to the social networking site their
username and passwords are stored with high security measures.
Reliability Requirements: Reliability is the ability of the system to deliver services as specified.
The application is 100% reliable if the users friends maintain updated profiles.
Maintainability Requirements: The system source code should be updated as and when there
are changes made in the technology used.

4.3 Specific Requirements:

4.3.1 External Interfaces:

The system will display login page. End user provides login name and password to the
system. Take the login details from the user to authenticate the user
For invalid username and password appropriate error message will be displayed.
The output of the system will be the friends list to the end user.

4.3.2 Functions:
 Fig 3.2 Use Case diagram for user getting registered

The user has to get registered for our application.

Name of the use case- Register.
Description- User gets registered.
Normal Flow of Events:
Sign up for the site.
Login using username and password
Alternate Flow of Events: If user enters wrong user name or password, error messages
are displayed
Fig 3.3 Flow Chart for login process
Administrator:

Fig 3.4 Use Case diagram for administrator

Name of use case: Administrator

Description: It works in five stages.
Authentication: The user is authenticated.
Query with nick names: The user issues query to admin giving nick name.
Search possible details: The admin will analyze the data and search for possible
appropriate outcomes.
Send the final list: The final lists of suggested friend are sent to the user.
Unauthorized access: The suspicious activities are detected by the administrator.
Detect the system: The suspicious activity center is detected.
 Send the text message: The message is sent to the authenticated user about his accounts
suspicious activity.

4.3.3 Performance Requirements:

Have hours of operation that are 24 x 7 this is a web based application. The system will
work as long as the installed server is up. So the availability is 24 X 7.
The application must provide the list of friends if they have same nick names then all
possible answers must be given. If unauthorized access is detected from two or more places then
all those must be detected. If same suspected intruder is performing two suspicious things then
even that are must be detected.

4.3.4 Logical Database requirements:

The login details and all the nick names are held in the database during the time of
registration by the user to the social networking site.

Fig 3.5 Logical database diagram

4.3.5 Design Constraints:

4.3.5.1 Standards Compliance:

Not applicable. There are no such constraints imposed by regulating bodies that will
develop constraints for our application.

4.3.6 Software System Attributes:

 These are non-functional requirements that the system must have. These are not directly
concerned with the specific functions delivered by the system. These relate to the emergent
system properties. If the system fails to meet the non-functional requirements then its the failure
of the whole system. These can relate to three things Product requirements, Organizational
requirements and External requirements. Some of these related to our project are mentioned
below-

4.3.6.1 Reliability:
Reliability is the ability of the system to deliver services as specified. The application is
100% reliable if the users friends maintain updated profiles.

4.3.6.2 Availability:
Availability is the ability of the system to deliver services when requested. Since the
messages are sent to the cell phones about unauthorized access it must work any time to the user.

4.3.6.3 Security:
Security is the ability of the system to protect itself against accidental or deliberate
intrusion. Since we are maintaining login details the information are kept secured.

4.3.6.4 Maintainability:
Maintainability deals with the ability of the system which allows changes in the system
without affecting the existing components. World today has become competitive in everything.
As new requirements arrive from customer, we need to make changes in the system and add
functionalities. Since our system is built on object-oriented technology it supports the
maintainability to the great extent.

4.3.6.5 Portability:
Portability deals with the ability of the system being machine independent. The
application works on any computer that supports the installed servers. Hence it is portable
application.
 Table no: 4.1 Rating of software system attributes

ID Characteristic H/M/L 1 2 3 4 5 6 7 8 9 10 11 12

1 Correctness H

2 Efficiency H

3 Flexibility L

4 Integrity/Security M

5 Interoperability L

6 Maintainability M

7 Portability M

8 Reliability H

9 Reusability M

10 Testability L

11 Usability H

12 Availability H
4.3.7 Organizing the Specific Requirements:

4.3.7.1 System Mode:

There is only one mode of operation. The user needs to get registered to our social site.

4.3.7.2 User Class:

We have only one class. The user uses the application to fetch the friends list.

4.3.7.3 Objects:
The classes of objects in our system are User, Administrator, Application, our social
Website, Database, and Server. These Classes each have a single object and will be represented
along with their attributes and functions in a UML diagram in the design document.
4.3.7.4 Features:
In order to obtain friends list the user need to input his username and password that he
has provided at the time of registration.

4.3.7.5 Stimulus:
If a user inputs proper username and password of his account his friends list will be
displayed else a proper error message will be displayed.

4.4 Change Management Process:

The change management process is as follows:
Customer forwards us a formal email specifying the change in the requirement
needed.
The email is received by the customer support cell and a developer meeting is
held.
The feasibility, financial effects, change in project schedule etc is taken into
account and a poll is taken by the developer team to decide whether to make the
change or not.
 Depending on the decision taken by the poll, the schedule is re-organized or work
is continued as per normal schedule.

CHAPTER 5

DESIGN PHASE

5.1 Architectural Design:

5.1.1 E.R Diagram:
In software engineering, an entity-relationship model (ER model for short) is an abstract
and conceptual representation of data. Entity-relationship modeling is a database
modeling method, used to produce a type of conceptual schema or semantic data model of a
system, often a relational database, and its requirements in a top-down fashion. Diagrams created
by this process are called entity-relationship diagram.
 Fig 5.1 E-R Diagram

5.2 System Design:

Most components described in the System design section will require a more detailed
discussion. Other lower-level components and subcomponents may need to be described as well.
Each subsection of this section will refer to or contain a detailed description of a system software
component. The design process for identifying the subsystems making up a system and the
framework for sub-system control and communication is architectural design. The output of this
design process is a description of the software architecture.

Wamp Server
Web
Admin or
Browser.
User
Internet

Database

Mysql

Fig 5.2 System design of the application

5.2.1 Sub System Design:
Here the sub system of the main application has been designed and the working of the
application has been described.

Fig 5.3 Subsystem design for admin

 Fig 5.4 Subsystem design for user

5.3 Data Flow Diagram:

A data flow diagram (DFD) is a graphical representation of the "flow" of data through
an information system, modeling its process aspects. Often they are a preliminary step used to
create an overview of the system which can later be elaborated. DFDs can also be used for
the visualization of data processing (structured design).
A DFD shows what kinds of data will be input to and output from the system, where the
data will come from and go to, and where the data will be stored. It does not show information
about the timing of processes, or information about whether processes will operate in sequence
or in parallel.
 Fig 5.5 Data flow diagram for application

5.4 Interface Diagram:

5.4.1 Client Server Model:
 Fig 5.6 Client server model

5.5 UML Diagrams:

Unified Modeling Language (UML) is a standardized general-purpose modeling
language in the field of object-oriented software engineering. The Unified Modeling Language
(UML) is used to specify, visualize, modify, construct and document the artifacts of an object-
oriented software-intensive system under development. UML combines techniques from data
modeling (entity relationship diagrams), business modeling (work flows), object modeling, and
component modeling. It can be used with all processes, throughout the software development life
cycle, and across different implementation technologies.

5.5.1 Class model:

 In software engineering, a class diagram in the Unified Modeling Language (UML) is a
type of static structure diagram that describes the structure of a system by showing the
system's classes, their attributes, operations (or methods), and the relationships among the
classes. The class diagram is the main building block of object oriented modeling. It is used both
for general conceptual modeling of the systematic of the application, and for detailed modeling
translating the models into programming code. Class diagrams can also be used for data
modeling.

Application

DBconnect +firstname
+lastname
+connection +contact_number
+database
1 Connects database to application * +edit_profile()
+open() +edit_group()
+close() +edit_friends()

Fig 5.7 Class diagram for overview of application

Maintains
+general_information()

profile
photos
+firstname
+lastname * +photo_id
*
+contact_number +photo_description

+edit_friendlist() +add_pic()
+edit_groups() +edit_Album()

Fig 5.8 Class diagram for profile

5.5.2 Advanced Class Diagram:

application
+profiles
+groups
DBconnect

+connection
+database
+dbconnect()
Alert message
+open()
+close()
+send_message()
+send_email()

Registered user
+firstname
+lastname Admin
+address
+email_id +username
+password
+add_friend()
+remove_Friend() +view_feedback()
+edit_profile() +block_user()
+edit_group() +unblock_user()

Profile
+first name
+employment information
+general info

friend_list

+find_friend() photos
+remove_friend()
+photo_id
+album_name
+add_photo()
+add_album()
+remove_photo()

Fig 5.9 Advanced class modeling

5.5.3 Use Case Models:
In software and systems engineering, a use case is a list of steps, typically defining
interactions between a role (known in UML as an actor) and a system, to achieve a goal. The
actor can be a human or an external system. In systems engineering, use cases are used at a
higher level than within software engineering, often representing missions or stakeholder goals.

System
login

view/edit profile

edit photos

edit groups

user

edit friend list

send/recieve messages

Fig 5.10 Use case diagram for administration

5.5.3.1 Advanced use case model:

<<include>>
login

database confimation
<<include>> view/edit profile

edit photo send message/email

user

edit groups
Admin

<<extend>>
edit friend

block/unblock user

recieve message/email

Fig 5.11 Advanced use case for entire application

5.5.4 Sequence model:
 register homepage
user login_verify database profile message address_book groups pics friends

1 : site()

3 : register() 2 : store info()

4
5 : login()

6 : verify()

7 : goto homepage()

8 : edit()

9
10 : send/recieve msgs()

11
12 : edit and view contacts()

13
14 : create and edit groups()

15
16 : upload and view pics()

17
18 : add and search friends with nick name()

19

20

21

22

23

24

Fi
g 5.12 Sequence diagram for entire application
 register homepage
user login_verify database profile message address_book groups pics friends

1 : site()

3 : register() 2 : store info()

4
5 : login()

6 : verify()

7 : goto homepage()

8 : edit()

9
10 : send/recieve msgs()

11
12 : edit and view contacts()

13
14 : create and edit groups()

15
16 : upload and view pics()

17
18 : add and search friends with nick name()

19

20

21

22

23

24

Fig 5.13 Sequence model for updating profile information

5.5.5 State Model:
A state diagram is a type of diagram used in computer science and related fields to
describe the behavior of systems. State diagrams require that the system described is composed
of a finite number of states sometimes; this is indeed the case, while at other times this is a
reasonable abstraction. Many forms of state diagrams exist, which differ slightly and have
different semantics.

LOGIN

false

Verify

true

User Home Page

ADDRESS FRIENDS COMMUNITY

PROFILE MESSAGES PICS
BOOK

EDIT SEND RECEIVE ADD and ADD and View SEARCH and Create Topic
INVITE and
PROFILE MSG MSG VIEW PICS Contacts JOIN and post Reply
ACCEPT

LOGOUT
 Fig 5.14 State diagram for application

5.5.6 Concurrency Model:

Concurrency is widely used in many new applications because of the usefulness of
parallel processing. Examples of concurrency can be found in preemptive multitasking systems,
multiple processor computers, and special networks of computers that work together to run a
single program.

Fig 5.15 Concurrency model

5.5.7 Activity Model:
Activity diagrams are graphical representations of workflows of stepwise activities and
actions with support for choice, iteration and concurrency. In the Unified Modeling Language,
activity diagrams can be used to describe the business and operational step-by-step workflows of
components in a system. An activity diagram shows the overall flow of control.
 Login

Messages Pics Friends and

Profile Address Community
book

Edit Profile Send Receive Add Pics View Pics Add View Search and
Message Message Contact Contact add Friend

Logout

Fig 5.16 Activity diagram for application

5.5.8 Swimlane Diagram:

A swim lane (or swimlane) is a visual element used in process flow diagrams, or
flowcharts that visually distinguishes responsibilities for sub-processes of a business process.
Swim lanes may be arranged either horizontally or vertically. In the accompanying example, the
swimlanes are named Customer, Sales, Contracts, Legal, and Fulfillment, and are arranged
vertically.

Authentication HOME PAGE Activities END SESSION

PROFILE EDIT
PROFILE

SEND
MESSAGE

MESSAGES
RECIEVE
MESSAGE

ADD PICS

LOGIN HOME PAGE PICS Logout

VIEW
PICS

CREATE
COMMUNITY

COMMIUNITY
JOIN
COMMUNITY

FRIENDS SEARCH AND

ADD FRIENDS

Fig 5.17 Swimlane diagram for application