0% found this document useful (0 votes)
59 views147 pages

Chatify Final

Here are the key hardware and software requirements for developing and using the Chatify social media website: - Client side: - Hardware: Intel dual-core or Ryzen 3 processor, 2GB RAM, 32GB storage, Windows or Mac OS device - Software: Internet-enabled device and web browser, Windows 7 or Mac OS 10.12 and above - Development side: - Hardware: Intel Core i3 processor, 4GB RAM, 2GB storage plus 100GB hard disk storage - Software: PHP for front-end, MySQL for back-end, Visual Studio Code, Microsoft Office, E-draw Max, Windows 7 or above The requirements ensure the website is functional for clients and allows efficient development
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
59 views147 pages

Chatify Final

Here are the key hardware and software requirements for developing and using the Chatify social media website: - Client side: - Hardware: Intel dual-core or Ryzen 3 processor, 2GB RAM, 32GB storage, Windows or Mac OS device - Software: Internet-enabled device and web browser, Windows 7 or Mac OS 10.12 and above - Development side: - Hardware: Intel Core i3 processor, 4GB RAM, 2GB storage plus 100GB hard disk storage - Software: PHP for front-end, MySQL for back-end, Visual Studio Code, Microsoft Office, E-draw Max, Windows 7 or above The requirements ensure the website is functional for clients and allows efficient development
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 147

VIVEKANAND COLLEGE OF ADVANCED COMPUTER AND

INFORMATION SCIENCE

VEER NARMAD SOUTH GUJARAT UNIVERSITY, SURAT PROJECT


REPORT

ON

CHATIFY

AS A PARTIAL REQUIREMENT FOR THE DEGREE

OF

BACHELOR OF COMPUTER APPLICATION

(B.C.A.)

2021-2022

GUIDED BY: SUBMITTED BY:

Ms. Rini Cherian


Sasani Vivek [2019012363]

Shelar Deep [2019012376]

Thummar Ankit [2019012392]

Thummar Dip [2019012393]


ACKNOWLEDGEMENT

When we reach on completion of the project, giving credit becomes a


must, without the support of so many people’s help and guidance, this
project couldn’t be completed successfully.
First we would like to thank my parents with their great support We can
reach at the stage. Then our humble thanks to all professors and all staff
members of our college “Vivekanand College for BCA Advanced
Computer & Information Science”. For the Co-operation & keep
interest extended by them, throughout my degree course. It is a base that
they have built, which sustain such good jobs.
We would like to thank Mrs. Sumathi Shenoy, the campus director of
the Vivekanand College of advanced computer and Information science
and Mrs. Dipjaya Patel, I/C principal of Vivekanand college for
B.C.A.for granting us an opportunity to work on this Project. We would
also like to thank to our guide Ms. Rini Cherian for their valued guidance
and encouragement towards the completion of our project.

Last but not the least, our heartfelt appreciation goes to all those not named
here, but who have rendered their co-operation, little or more, directly or
indirectly involved in the development of this system.
Thanking All.

Sasani Vivek
Shelar Deep
Thummar Ankit
Thummar Dip
PREFACE

Before taking the project work for foundation, it is have an exact idea
the work “project”. The project consists of seven letters each letter
has its own significance as follows:-
 ‘P’:- Stands for PLANNING
Planning is the word this idea of work proposed to be done as a fact;
any work without planning is just like a ship without the radar and
compass.

 ‘R’:- Implies RESOURCE


Resources are the means which guide to promote the function of the
plant, without suitable resources, a project cannot work
satisfactorily. There must be necessary resources in order to maintain
good project work.
 ‘O’:- Denotes OPERATION
Operation is actually all the types of works which are promoted by
the worker to complete the project.

 ‘J’:- Stands for JOINT EFFORTS


Joint effort means that combine efforts of worker and other staff to
compete the work.
 ‘E’:- Denotes ENGINEERING FUNCTION
Both the bodies i.e. planning and engineering bodies work to gather
engineers through there techniques for good production. All
technical work is based on engineering function so it is very
important.

 ‘C’:-Signifies COMMUNICATION
For execution of plan, the communication is very necessary. The
material required for project work can be brought when proper
communication is available.
 ‘T’:- Symbolizes TASK OF WORKING
Task of working is co-operation of the working body and control
working body. As a matter of fact, the work “PROJECT” is used
specially for construction purpose.
A project is neither a physical objective nor it is the result. It has
something to do with going on between a project is a combination of
human and non human resources pooled to gather in temporary
organization to achieve the specific purpose.
Chance is an essence of life and this applies to information
technology for keeping in pace with the current market requirements
is the major challenge computer word is facing the need of the
business world is to organize the data.
AbsTRACT

This document is meant for describing all the features and procedures that
where followed while developing the system.
This document specially mentions the details of the project how it was
developed, the primary requirement, as well as various features and
functionalities of the project and procedures followed in achieving these
objectives.
The aim of this project was to design and create a Social media website that
gives easy interaction to the user. This website allows the user to interact with
each other.
Chatify – social media website is simple, user friendly and secured. The
solution is design to implement several database management techniques and
was primarily evaluated by its ability to transfer data speedily, maintaining
secure transaction and easy interaction. The final result is a website, which
provides facilities at an instance.
It has many technical elements and the rules are fairly simple. This simplicity
makes it a good platform. It covers a range of areas (data modelling, some
coding challenges, user interface etc.) but none too difficult.
INDEX
SR NO. CONTENTS PAGE NO

1 Introduction 01

1.1 Project Profile 02

1.2 Project Introduction 03

2 Environment Description 04

2.1 Hardware & Software 05


Requirement
2.2 Tools & Environment 08
Description
3 Proposed System 14

3.1 Scope 15

3.2 Aim & Objectives 17

3.3 Excepted Advantages 18

4 System Planning 19

4.1 Requirement Specification 20

4.2 Feasibility Study 21

4.3 Life Cycle Models 23


4.4 Effort Distribution Diagram 25

4.5 Task Dependency Diagram 26

4.6 Project Schedule Chart 28

5 UML Diagram 29

5.1 Use-Case Diagram 30

5.2 Activity Diagram 43

5.3 Sequence Diagram 61

6 System Design 63

6.1 Navigation Map 64

6.2 Database Table Structure 66

6.3 Screen Design 77

7 System Testing 123

7.1 Software Testing 124

7.2 Test Case 130

8 Limitation and System Enhancement 134

9 Reference 137
1
INTRODUCTION

1.1 Project Profile


1.2 Project Introduction

1
1.1 Project Profile

Title : Chatify

Duration : 3 Months

Team Members : 4

Front End Tools : PHP

Back End Tools : MySQL

Other Tools : Edraw, Microsoft office, Sublime text ,


Google chrome, command Prompt

Guided By : Ms.Rini Cherian

Submitted By : Sasani Vivek


Shelar Deep
Thummar Ankit
Thummar Dip

2
1.2 Project Introduction

 “Chatify” is a social web portal that will connect people with each other.
 Providing such a platform where people can share their posts, photos,videos
personal information & also like,comment their views.
 Users will be able to keep up with friends by using messaging services and
chatting Facilities.
 This will also help to make new friends around.
 Our main objective of making this web site is to create a social network of
people on web.
 To get in touch with the friends far away, to their share views to their friends.
To get people close to each other in this mechanical life.
 Make searching of friend easy and to connect with them.
 Share Photos, Personal information, Videos & also update their status.
 User can read books free of cost.

3
2
TOOLS & TECHNOLOGIES

2.1 Hardware & Software requirements


2.2 Tools & Technology

4
2.1 Hardware & Software requirements

Client Side :

 Hardware Requirements :

Processor : Intel duel core , Ryzen 3 or above

RAM : 2 GB or Above

Storage : 32 GB or Above

Device : Windows or Mac Os enabled

 Software Requirements :

Device : Internet Enabled De vice with Web-browser

Operating System : Windows 7 or above, Mac Os 10.12 or


above

5
Development side :

 Hardware Requirements :

Processor : Intel Core i3–350M dual-core processor (2.26 GHz,


3 MB Cache).

RAM : 4 GB or Above.

Storage : 2 GB of available disk space minimum, 4 GB


recommended (500 MB for IDE + 1.5 GB for Android SDK and
emulator system image). Minimum 100GB Hard disk Storage is
required.

 Software Requirements :

Front-End : PHP

Back-End : MySQL

Tools : Visual studio code, Microsoft office, E-draw max.

Operating System : Windows 7 or above, MacOS(64bit),


Linux, etc

6
Server Side

 Hardware Requirements :

Processor : Intel Core i3–350M dual-core processor (2.26 GHz,


3 MB Cache).

RAM : 4 GB or Above.

 Software Requirements :

Server : Wamp / Xampp, Android SDK, Flutter SDK


Operating System : Windows 7 or above,
MacOS(64bit), Linux, etc

7
2.2 Tools &Technology

Core technologies :

 PHP :
 PHP stands for PHP: Hypertext Pre-Processor.

 PHP is server-side scripting language, like ASP.

 PHP scripts are executed on the server.

 PHP is open source software.

 PHP is free to download and use.

 PHP is used to create dynamic websites this is a step up from HTML


as it allows you to do much more than creating static websites. Using
a language such as PHP also gives you access to using databases with
your website such as MySQLI.

 PHP runs on different platforms. [Windows, Linux, UNIX, etc.] PHP


is easy to learn and runs efficiently on the server side.

8
 MYSQL:

 MySQL is a database system used for developing web-based software


applications.

 MySQL used for both small and large applications.

 MySQL is a relational database management system (RDBMS).

 MySQL is fast, reliable, and flexible and easy to use.

 MySQL supports standard SQL (Structured Query Language).

 MySQL is free to download and use.

 MySQL was developed by Michael Widenius and David Axmark in


1994.

 MySQL is presently developed, distributed, and supported by Oracle.

 MySQL Written in C, C++.

 MySQL server design is multi-layered with independent modules.

 MySQL is fully multithreaded by using kernel threads. It can handle


multiple CPUs if they are available.

 MySQL provides transactional and non-transactional storage engines.

 MySQL has a high-speed thread-based memory allocation system.

 MySQL supports in-memory heap table.

9
Document Tools :

 E Draw Max(7.2) :

EDRAW Max is an extremely powerful all-in-one diagramming tool that can


serve all of your purposes. Whether you need to draw flowcharts, fishbone
diagrams, UML diagrams or design floor plans, office layouts, you can find
what you want in Edraw Max. Importantly, it is quite affordable.

• Massive Templates & Symbols


• Robust File Compatibility
• More Powerful than Visio
• Easy to Get Started
• Visualize your Ideas in the Impressive Way
• Share your Designs Anytime, Anywhere
• Cross-Platform Visual Communication Tool

 MsWord(2013) :

Microsoft Word or MS-WORD is a Graphical word processing program that users


can type with. It is made by the computer company Microsoft. Its purpose is to allow
users to type and save documents.

• Spelling & grammar checker, word count

10
• Speech recognition
• Inserts pictures in documents
• Choice of typefaces
• Special codes
• Web pages, graphs, etc.
• Tables
• Displays synonyms of words and can readout the text
• Prints in different ways

 MsPowerPoint(2013) :

Microsoft PowerPoint is a powerful presentation software developed by


Microsoft. It is a standard component of the company’s Microsoft Office suite
software, and is bundled together with Word, Excel and other Office productivity
tools. The program uses slides to convey information rich in multimedia. The
term “slide” refers to the slide projector, which this software effectively replaces.

Benefits of PowerPoint

• It is widely used, and considered the “standard” for presentation software.


If you create a PowerPoint presentation, it’s more likely it will be easier
for others to open and view.

• It includes many optional presentation features, including slide transitions,


animations, layout, templates, and more.

11
• It offers the option to export its slides to alternative file formats, including
GIF and JPG images, MPEG-4 video, PDF, RTF(rich text format),
WMV(Windows Media Video), and PowerPoint XML.

12
Devlopment Tools :

 Xampp Server(3.2.4) :
XAMPP is a software distribution which provides the Apache web server, MySQL
database (actually MariaDB), Php and Perl (as command-line executables and
Apache modules) all in one package. It is available for Windows, MAC and Linux
systems. No configuration is necessary to integrate Php with MySQL. XP, SP3, or
Windows Server 2003.

 Sublineme :
sublineme a text source code editor for use with Microsoft Windows. It supports
tabbed editing, which allows working with multiple open files in a single window.
The project’s name comes from the C increment operator. Vscode is distributed as
free software. Vscode save the extraction is PHP and more than one file can be
opened.

13
3
PROPOSED SYSTEM

3.1 Scope
3.2 Aim & Objective
3.3 Expected Advantage

14
3.1 Scope

 The scope of the application “Chatify“ is global i.e. it should be


accessed from anywhere and any time through internet.
 “Chatify“ is online social media web-site which a user can
communicate with their friends and families.
 The main advantage of “Chatify“ is that User can be active
anytime a day.
 There are two sections in our application :

15
 Admin

 Admin can perform following operations :

 Admin Can Login, Signout, Change password.


 Admin Can Delete Images.
 Admin Can Suspend User
 Admin Can Manage the feedback from users
 Admin Sorts Users Complaints.
 Admin can manage books.
 Admin can logout from admin panel

 User

 User can perform following operations :

 User Can Register, login and change password.


 User can upload profile picture, photo, video and
text.
 User can delete post.
 User Can Send a message.
 User can read a book.
 User can edit their profile.
 User can report post and user.
 User Can Complaint to Admin.
 User Can give Feedback.
 User Can Block a User.
 User can contact to admin.
 User can deactive their account.
 User can logout from website.

16
3.2 Aim & Objective

 The scope of the website “Chatify“ is global i.e. it should be


accessed from anywhere and any time through internet.
 You’re always logged in so you don’t miss social. No more
confusion about whether you are logged in or not.
 Our aim is to make the application as easy as possible to use.
 Our website is optimized to operate in the most constrained
environment possible.
 Our aim is to change habit of social media user that’s why we
introduce book section in our website. User can easily access and
read book on our site free of cost anytime.
 We are looking for eliminate fack and bot account from social
media for that reason user have to make account on our website
with their mobile number and they have to verify mobile number
with otp.

17
3.3 Expected Advantages

 Users can use their existing phone numbers to register in chatify.


 Through this website you can freely send messages and post photo and
video.

 You can interact with your friends and family through this social
media platform.

 User can read thousend of books free of cost on chatify, so they can
utilities their time.

18
4
SYSTEM PLANNING

4.1 Requirement Specification


4.2 Feasibility Study
4.3 Life Cycle Models
4.4 Effort Distribution Diagram
4.5 Task Dependency Diagram
4.6 Project Schedule Chart

19
4.1 Requirement Specification
 Admin
 Admin Can Login, Change and Forget password.
 Admin Can Delete Images.
 Admin Can Suspend User
 Admin Can Manage the feedback from users
 Admin Sorts Users Complaints.
 Admin can manage books.
 Admin can logout from admin panel

 User

 User Can Register, login and change password,


forget password.
 User can upload profile picture, photo, video and
text.
 User can delete post.
 User Can Send a message.
 User can read a book.
 User can edit their profile.
 User can report post and user.
 User Can Complaint to Admin.
 User Can give Feedback.
 User Can Block a User.
 User can contact to admin.
 User can deactive their account.
 User can logout from website.

20
4.2 Feasibility Study

Feasibility study plays very important role in the development of any system,
but when it is the case of development of any software then its importance
increases much more because in the case one should be very clear about
availability of the time and resources. Before starting the development of the
software one should give considerable amount of time for feasibility study
because the successful completion of project depends upon feasibility. The
feasibility of our project has been judged on the basis of time, technology,
resources available and project length.

 Time:
This project takes at least 3 month to be completed if we take help of reused
components otherwise it will take 6 months to be complete. We will not make
use of components and therefor will be complete the project in 4 months. Thus
according to time the feasibility is not that right.

 Technology:
The necessary technology, front-end development tool, back-end database
technology and various other tools namely installation tools, etc. for developing
the system, are already available within the organization. So this problem is
feasible.

 Resources:
We need good knowledge software engineers and practitioners. We need net
connection. We have all the resources in the desired amount.

21
 Project Size:
The Project size might be above 1500 LOC. This is just the rough assumption
because we don’t have any basis of the past projects. Thus the project overall
feasibility is normal and therefore we have undertaken this project.

22
4.3 Life Cycle Models

23
 Increment Model:
The incremental Model is an evolution of the waterfall Model, where the waterfall
Model is incrementally applied.
The series of releases is referred to as “increments”, with each increment providing
more functionality to the customers. After the first increment, a core pr3pp [product
is delivered, which can already be used by the customer. Based on customer
feedback, a plan is developed for the next increments, and modifications are made
accordingly. This process continues, with increments being delivered until the
complete product is delivered. The incremental philosophy is also used in the agile
process model.

 Advantages:
After every iteration any faulty piece software can be identified easily as very few
changes are done after every iteration.
It is easier to test and debug as testing and debugging can be performed after each
iteration.
This model does not affect anyone's business values because they provide core of
the software which customer needs, which will indeed help that person to keep run
his business.
After establishing an overall architecture, system is developed and delivered in
increments.

 Disadvantages:
If the requirements initially were thought to be stable but at later stages are realized
to be unstable then the increments have to be withdrawn and have to be reworked.
Resulting cost may exceed the cost of the organization. Problems may arise related
to system architecture.

24
4.4 Effort Distribution Diagram

Analysis & Desgin : 20-30 %

Testing & Debugging : 20-30 %

Design : 40-50%

25
4.5 Task Dependency Diagram

Requirement
Gathering

Requirement
Analysis

Requirement Determine Scope


of the System
Gathering

Requirement
Gathering

Designing

Coding & Integrating


Module

Testing

26
Work breakdown Structure:
1. Scope & Planning:
In this particular phase of the project we have explained the problem
definition along with its requirements in detail. All the research work and
background study prior the project initialization has been conducted in this
phase. The work breakdown structure and scheduling chart is prepared after
conducting the feasibility study and risk analysis.

2. Requirement Analysis:
Here we have tried to gather all the requirements pertaining program code, user
interface and database design. The detailed flow of data in the system is
depicted. We have shown the relationships between the entities of data through
entities relationship diagrams. This particular phase leads milestone Software
Requirement Specication.

3. User Interface Designing:


Depending on the inputs and outputs of the system i.e. the interaction between
the user and the system we have designed the interface. We have made it simple
and attractive which makes it more users friendly.

4. Implementation and Testing:


Depending upon the requirement specified in scope, we have implemented the
system using latest PHP technology.

5. Other Peripheral Activities For Quality Assurance:


Continuously meetings were held for project tracking and analyzing the higher
risks. Their degree of rigor was always tested and properly documented. These
activities were conducted considering our budget constraints and required
accuracy. It helped us to be focused and built a quality product.

27
4.6 Project Schedule Chart

28
5
SYSTEM MODEL ARCHITECHTURE

5.1 Use Case Diagram


5.2 Activity Diagram
5.3 Sequence Diagram

29
5.1 Use case diagram

 The Unified Modelling Language (UML) is a standard language for


Specifying, visualizing, constructing, and documenting the artefacts of
Software systems, as well as for business modelling and other non-software
Systems.

 The UML is a very important part of developing objects oriented software and
the software development process.

 Using the UML helps project teams communicate, explore potential designs,
and validate the architectural design of the software.

 The primary goals in the design of the UML were:

 Provide users with a ready-to-use, expressive visual modelling language so


they can develop and exchange meaningful models.

 Provide extensibility and specialization mechanisms to extend the core


concepts.

 Integrate best practices

Why Use UML?

In particular, they recognize the need to solve recurring architectural problems, such
as Physical distribution, concurrency, replication, security, load balancing and fault
tolerance. Additionally, the development for the World Wide Web, while making
some things simpler, has exacerbated these architectural problems. The Unified
Modelling Language (UML) was designed to respond to these needs.

30
Types of UML Diagrams

 Use case Diagram


 Activity Diagram

Use Case Diagram:

A use case diagram in the UML is a type of behavioural diagram defined by


and created from a Use-case analysis....

A use case diagram is a UML diagram that provides a high-level graphical view of
the functionality (use cases) supported by the system and shows which roles (actors)
can invoke each use case.

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.

Types of Actors:

 Admin
 User

31
Admin use case:

Login

Suspend
Post

Manage
Books

Manage
feedback

Manage
User
Admin
Analysis
site data

Suspend
user

Logout

32
Admin sub use case:

 Suspend user: View about


suspend

Valid/
Suspend invalid
user

Admin Suspend
user

 Books:
View
Book

<<Extend>> Valid/
Books
invalid
user

Admin Upload
book

33
View
 Complaint: complaint

Valid/
invalid

Complaint
Reply
user complaint

Admin

Fixed issue

 Suspend user post:


View user
post

Suspend
user
<<Extend>> Valid/
post invalid

Admin Suspend
User post

34
User use case:

Login

Manage Post

Manage friend

Manage
profile

Read
Books
User
Send report

Block user

Send message

Send Feedback

Change password

35 Logout
User sub use case:

 Manage Post:
Add post

Like/Unlike

Manage
post
Delete post
user
User

Comment
post

36
 Manage friend:

View
friend

Search
friend

Add
Manage friend
friend
Block
User friend

Report
friend

Report
Friend

37
 Manage profile:
Change
name

Manage <<Extend>> Change


profile profile

User Change
password

 Read Books:
View
Book

Read <<Extend>> Valid/


Books invalid

User Upload
book

38
 Send Report:
View
Post

Send
<<Extend>>
Report View user
user

User Send
report

 Send message:
View
friend

Send
message

User
Text friend

39
 Block user:
View
User profile

Block
user

User
Block user

 Send feedback:
View
website

Send
feedback

User Give
feedback

40
 View user:

View
info

View
post

Save
View post
user
Like/
User comment

View
friend

Report
post

41
 Send complaint :
Mark
issue

Send <<Extend>> Choose


complaint type

User Write
problem

42
5.2 Activity diagram

o Activity diagrams are graphical representations of workflows of


stepwise activities and actions with support for choice, iteration and
concurrency.

o An activity diagram is a UML diagram that is used to model a process.


It models the actions (or behaviours) performed by the components of
a business process or IT system, the order in which the actions take
place, and the conditions that coordinate the actions in a specific order.

Basic Activity Diagram Symbols and Notations :

o Action States :

Action states represent the no interruptible actions of objects. You can draw
an action state in Smart Draw using a rectangle with rounded corners.

o Action Flow:

Action flow arrows illustrate the relationships among action states.


.

43
o Object Flow :

Object flow refers to the creation and modification of objects by activities. An


object flow arrow from an action to an object means that the action creates or
influences the object. An object flow arrow from an object to an action
indicates that the action state uses the object.

o Initial State :

A filled circle followed by an arrow represents the initial action


State.

44
o Final State

An arrow pointing to a filled circle nested inside another circle represents


the final action state.

o Branching

A diamond represents a decision with alternate paths. The outgoing


alternates should be labelled with a condition or guard expression. You can
also label one of the paths "else."

o Synchronization :

A synchronization bar helps illustrate parallel transitions.


Synchronization is also called for king and joining.

45
Activity diagram of Admin:

46
Sub activity diagram of admin:

Manage User :

47
Manage books :

48
Manage Complaints :

49
Suspend post:

50
Suspend User:

51
Activity diagram of User:

52
Sub activity diagram of User:

Registration :

53
Login :

54
Manage Post :

55
Manage friend :

56
Read Books :

57
Send report :

58
Send message :

59
Send feedback :

60
5.3 Sequence Diagram

Sequance Diagram of Admin:

Obj : Chatify Obj : Database

61
Sequance Diagram of Admin

Obj : Chatify Obj : Database

62
6
SYSTEM DESIGN

6.1 Navigation Map


6.2 Database Table Structure
6.3 Screen Layout

63
6.1 Navigation Map

Nevigation map of Admin

64
Nevigation map of Users

65
6.2 Database Table Structure
Table name: users

Discription: It is used to store information about new user


who register and make account on website.

66
Table name: admin

Discription: It is used to store information that help in admin


login.

Table name: friend_requests

Discription: It is used to store information of friend request


sent by one user to another.

67
Table name: message

Discription: It is used to store the conversation between the


users it also stores chatting Information.

Table name: otp

Discription: It is used to store in unique phone number the


unique otp.

68
Table name: notification

Discription: it is used to store information of Notification


section.

69
Table name: book

Discription: it store information about book which are stored


in e-library.

70
Table name: posts

Discription: It is used to store all the detail of all the post that
are posted by the user.

71
Table name: reports_post

Discription: It is used to store information of post which is


reported by some user.

Table name: likes

Discription: It is used to store likes by numbers of user on any


particular post posted by any user.

72
Table name: comment

Discription: It is used to store comments of the user that are


posted on another user’s Post ( post/photo/video).

Table name: bookmark

Discription: it is used to store information of bookmarked


Post.

73
Table name: report_user

Discription: It is used to store information of user who


reported by another user.

Table name: suspend

Discription: it is used to store information of user who are


suspended.

74
Table name: feedback

Discription: it is used to store information of feedback that


user want to give to admin.

Table name: complaint

Discription: it is used to store user complaints.

75
Table name: temp_user

Discription: it is used to store information which user can not


fully sign up.

76
6.3 Screen Layout

Admin panel :

Admin Login:

77
78
Dashboard :

79
Dashboard in Dark-mode:

80
Tables:

81
82
Chart :

83
Books :

84
Upload book:

Book details:

85
Edit book:

Report post :

86
Report user:

Suspend user:

87
Feedback:

Complaint:

88
Complaint information:

Reset password:

89
90
Forget password:

91
User panel :

Sign up :

Step 1:

92
93
Step 2:

94
95
Step 3:

96
Step 4:

97
Step 5:

98
Welcome mail for new user:

99
Sign in:

100
101
Home page:

Home page in Dark-mode:

102
Multi-languages:

Text post:

103
Photo post:

Video post:

104
Advertisement:

Payment:

105
106
Upload Advertise:

Monetize advertise:

107
Search:

Other user profile:

108
Friend profile:

Friend Requests:

109
Like/comment on post:

Chatting with friend:

110
Search friend:

Books:

111
View book:

112
Book in pdf:

Settings:

113
Update Details:

Change profile:

114
User profile:

Save post:

115
Report post:

Report user:

116
Feedback:

Complaints:

117
Complaint reply from admin:

118
FAQ:

Contact on what’s app:

119
Terms & conditions :

Delete account:

120
Forget password with otp :

Enter new password:

121
122
7
SYSTEM TESTING

7.1 Testing Introduction


7.2 Test Case

123
7.1 Testing Introduction
 Testing is the process of examining an application to ensure it fulfills the
requirements for which it was designed and meets quality expectations. In
short, Testing is software quality assurance activity.
 The main objective of testing is to find yet an undiscovered error and at the
same time checking the quality and reliability of system. More importantly,
testing ensure that the application meet customers’ expectations.
 Testing accomplished a variety of things, but most importantly it measures
the quality of websites you are developing.
 This view presupposes there are defect in your website waiting to be
discovered and this view is rarely disproved or even disputed.
 System testing makes logical assumptions that if all the part of the system is
correct so that the goal will be successfully achieved. The system should be
checked logically.
 Validations and cross checks should be implemented, avoiding duplications
of records, which cause redundancy of data.

124
Types Of Testing :

 Unit Testing :
 The primary goal of unit testing is to take the smallest piece of testable web
site in the application, isolate it from the remainder of the code, and determine
whether it behaves exactly as you expect.
 Each unit was tested separately before integrating them into modules to test
the interfaces between modules for that prepare case.
 It allows automation of the testing process, reduces difficulties of discovering
error contained in more complex pieces of the application, and test coverage
is often enhanced because attention is given to each unit.

of In the web based application smallest testable unit is web page itself. So the web
Pages the site are to be unit tested. Each web page contains content, navigational
links, and processing elements (script, event handlers, etc.). The testing will be
driven by the content processing, and links contained in the site.

 Validation Testing :

 After integration testing, web site is completely assembled as a package,


interfacing error has been uncovered and corrected and the final series of the
web site is tested. The validation succeeds when the web site functions in a
manner that can be reasonably accepted by the client.

 Validation tests provide assurance that the web site as written meets all the
requirements.

 In validation testing, requirement established as part of software requirements


analysis are validated against the software that has been constructed.

125
 All validation criteria are tested. Validation testing provides the final
assurance that software meets all functional, behavioral and performance
requirements.
 In date entry user can not insert incorrect date format, if user enter wrong date
then it will display the error message.
 In numeric field only enter numeric data otherwise display error message.
In text field only enter text data otherwise display error message.

 Integration Testing :

We have used top down testing strategy for integrating web pages
.The separately generated web pages will be integrated and for
checking that they work properly after their integration , tests will be
conducted to ensure their proper functionality.
Using dummy web pages it is checked that weather output of page
will redirect to specific webpage After that regression testing strategy
help us to ensure that changes do not introduce unintended behavior
or additional .

 White Box Testing :

While box testing is testing case design method that uses the control
structure of the procedural design testcases. Using white box testing
methods, One can devices that cases that –
 Grantees that all independent paths within a module have been
exercised at least once.
 Exercise all logical decision on their true and false sides.
 Exercise all loops at their boundaries and within their operational
bounds.
 Exercises internal data structure to ensure their validity

126
 Black Box Testing :

Black box s the method of software testing that tests the factuality of applications
appeased to it internal structure or workings. Specific knowledge of application’s
code /internal structure & programming knowledge in general is not require Test
cases are built around specification & requirement , i.e. what application suppose to
do.it uses external description of the software , including specification , requirements
and design to derive test cases .This cases can be functional or non-functional
through usually function. The test designers select valid and invalid inputs and
determine the correct output. There is no knowledge of the test object’s internal
structure testing.

 Alpha Testing :

Alpha testing makes use of prototypes to test the software in its beta
stage. However, You cannot expect the software to possess complete
functionality for which it is designed especially at this stage . This is
because alpha testing is usually conducted to ensure that the software
that is being developed provides all necessary core function and that
accepts all inputs and gives expected output.
Alpha test are conducted in the software developers offices or on any
designated systems so that they can monitor the test and list out any
errors or bugs that may be present. Thus, some of the most complex
codes are developed during alpha testing stage. Furthermore, the
project manager who is handling the testing process will need to talk
to the software developer on the possibilities of integrating the results
procured from alpha testing process with the future software design
plans so that all potential future problem can be avoided.

127
 Beta Testing :

In software development, beta test is the second phase of software


testing in which a sampling of intended audience tries the product
out. Originally, the term alpha test meant the first phase of testing in
a software development process. The first phase includes unit testing,
component testing and system testing. Beta testing can be considered
“pre-release testing “. Beta test versions of software are now
distributed to a wide audience on the web partly to give the program
a “Real World “test and partly to provide a preview of the next
release.
Beta testing comes after alpha testing and can be
consider as a form of extremer user acceptance testing. Version of
the software , known as beta versions , is released to a limited
audience outside of the programming team .The software is released
to group of people so that further testing can ensure the products have
few faults or bugs. Sometimes, Beta version are made available to
the open public to increase the feedback field to a maximal number
of the future users.

 System Testing :

The uncovered weakness that were not found in earlier tests are
removed In System testing. The system is corrected such away that
it does not affect the forced system failure. The testing is done with
the low volume of transaction based on live data. Finally the total
system is also tested to ensure that no data are lost.
Following testing on the completed system will be performed in order
to find the errors before they become defects and correct them.

 In order to eliminate navigational errors the site will be


reviewed and tested. The use cases scenarios that we have

128
developed in the same document while requirement analysis activity
will be considered to uncover errors in the navigational links.
 Web pages of the site will be unit tested. For the web pages
sometimes the smallest testable unit is the single web page itself.
Each web page contains content, Navigational links, and processing
elements (Scripts, event handlers etc.). The testing will be driven by
the content processing and links contained in the site.
 The separately generated web pages will be integrated and for
checking that they work properly after their integration, tests will be
conducted to ensure their proper functionality.
 The functionality of the site will be checked with the different
versions of the Internet Explorer , Netscape Navigator etc. and
wherever necessary it will be attempted to change the
implementation of the not working for some browsers fir some case
and of course without loosing the purpose of the functionality if
possible .

129
7.2 Test case

Admin login :

No. Field Input Data Valid / Validation


Invalid

1 User Blank Invalid User name can‘t


name be blank
Admin1 Valid Redirect the next
fild.

2 Password Blank Invalid Password is


invalid

admin Valid Redirect towards


the Admin pannel

130
User Registration:

No. Field Input Data Valid / Validation


Invalid
1 Username Blank Invalid Username can’t be
blank.
Ak26 Invalid Username already
exist.
Shelar11 Valid Redirect towards the
page

2 Phone no Blank Invalid Phone no can ‘t be


blank
Character Invalid Phone must contain
number.
$$$ Invalid Phone must be
proper.
9510573911 Valid Redirect towards the
page .

3 OTP Blank Invalid Password is invalid


123456 Invalid Otp is wrong
5654 Valid Redirect towards the
page.

4 Personal Blank Invalid Personal details is


detalis invalid
First 011 Invalid First name is must be
name in character

131
Deep Valid Redirected in next
fild.
Last 001 Invalid last name is must be
name in character
Shelar Valid Redirected in next
fild.
Email $$$ Invalid e-mail must be
proper. It must
contain @.
[email protected] Valid Redirected in next
fild.
DOB Character Invalid DOB must be in
numbers.
25-09-2021 Invalid Age must be above 8
year.
11-04-2002 Valid Redirected in next
fild
Passwd abcd Invalid Length must be 8.
abcdefgh Invalid Strong password
required.
Deep@1234 Valid Redirected in next
fild

5 Profile Blank valid Profile pic default.


Pic
Deep.png valid Redirect home page.

132
User login :

No. Field Input Data Valid / Validation


Invalid

1 User Blank Invalid User name can‘t


name be blank
Shelar11 Valid Redirect the next
fild.

2 Password Blank Invalid Password is


invalid

admin Valid Redirect towards


the home page

133
8
SYSTEM LIMITATIONS AND FUTURE
ENHANCEMENT

8.1 System Limitations


8.2 Future Enhancement

134
8.1 System Limitations

 The project report entitled "Chatify" is to be developed as


a part of curriculum & to be submitted within a period of 3
months.

 User can not tag another user in post.

135
8.2 Future Enhancement

Once the s/w is developed, tested and independently used by the


users then the focus is laid on the changes associated with error
correction, adaptation required as the software environment evolves
and changes that will occur due to enhancement brought by changing
requirement.

• As software is used, the user will recognize additional functions that


will provide benefits, perfective maintenance extends the software
beyond its original functional requirements.
• At same time, the requirements as shown in this project report may
also change to provide user’s need or per software enhancement
requirements.
• The duration of three months was insufficient for the complete
development of the project. Hence in the future enhancement, the
project can be extended to provide additional facilities.
• Another enhancement that is possible in future is to provide the
sharing of multimedia to other social media platforms.

136
9
REFERENCES

9.1 Bibliography
9.2 Webography

137
9.1 Bibliography

All the needed information related to my project “JUST FINDER” was


being clumped from the following sources:

Reference Book
 PHP & Mysql novice to ninja
 PHP in action: Objects, Design, Agility
 Learning Php, Mysql, JavaScript & CSS

138
9.2 Webography

All the needed information related to my project


“Chatify” was being clumped from the following
sources :

 www.Stackoverflow.com
 www.Youtube.com
 www.facebook.com
 www.instagram.com

139
140

You might also like