Chatting Application

UCS 503
Software Engineering

Submitted By:

101783012 - Chahat Jindal

101610040 - Jahnavi Bhardwaj
101610043 - Jodh Singh

B.E Third Year, Computer Engineering

Submitted To:
Dr. Seema Bawa

Thapar Institute of Engineering and Technology

Nov 2018
UCS 503
Software Engineering, BE 3rd Year

1
 Table of Contents:

Sr. No. Description Page No.

1. Introduction 3

2. Analysis Phase 5

3. Design Phase 7

4. Testing Phase 14

5. Deployment Phase 17

2
 Introduction

There are numerous products available that allow for real time “chatting” over the Internet.

The purpose of this project is to implement a Java based chat application that
will allow users with an intranet connection to engage in private conversations.

The development of this project centered on the development of a message

protocol that would allow the application to properly log in users, send
messages, and performs system maintenance.

1.1 Scope Definition

Broadcasting Chat Server Application is going to be text communication

software; it will be able to communicate between two computers using point to
point communication.

The limitation of Live Chat is it does not support audio and video
conversations. To overcome this limitation we are concurrently working on
developing better technologies.

Companies would like to have communication software wherein they can

communicate instantly within their organization.

The fact that the software uses an internal network setup within the
organization makes it very secure from outside attacks.

1.2 Block Diagram of the Project

User1

Server

User2

3
1.3 Ishikawa diagram of problem formulated:

4
2. Analysis Phase

2.1 Use Case Diagrams based on Use Case Scenarios

5
2.2 Activity diagram to depict various procedural and algorithmic flows

6
2.3 Data flow diagram (DFD: Level 0,1,2) [It may become the part of design phase]

7
 2.4 Software Requirement Specifications (SRS) in IEEE format
1 Introduction
2.4.1.1 Document Purpose
There are numerous products available that allow for real time “chatting” over the Internet.
The purpose of this project is to implement a Java based chat application that will allow
users
with an intranet connection to engage in private conversations.
The development of this project centered on the development of a message protocol that
would
allow the application to properly log in users, send messages, and performs system
maintenance.

2.4.1.2 Product Scope

Broadcasting Chat Server Application is going to be text communication software; it will be
able
to communicate between two computers using point to point communication.
The limitation of Live Chat is it does not support audio and video conversations. To
overcome
this limitation we are concurrently working on developing better technologies.
Companies would like to have communication software wherein they can communicate
instantly within their organization.
The fact that the software uses an internal network setup within the organization makes it
very
secure from outside attacks.

2.4.1.3 Intended Audience and Document Overview

This system is useful for those who cannot afford to have an Internet connection. For
example:
schools, colleges, small companies, etc. It is Client-Server system with centralized database
server. All local clients are connected to the centralized server via LAN.

Overview:
This project is aimed at developing a chatting application which has the facilities to share
text messages and media. Media includes pictures, videos, documents and audio clips.
For security purpose of users, the messages sent over this chatting application are end to
end encrypted. Encryption means adding a key value to our data which will change the
information and decryption means removing that applied secret key.

2.4.1.4 Definitions, Acronyms and Abbreviations

1.2.1 Abbreviations:

LAN: Local Area Network

2.4.1.3 Definitions:

LAN: A local area network (LAN) is a computer network that interconnects computers within
a limited area such as a residence, school, laboratory, university campus or office building.
By contrast, a wide area network (WAN) not only covers a larger geographic distance, but
also generally involves leased telecommunication circuits.

Server: A server is a computer program or a device that provides functionality for

other programs or devices, called "clients". This architecture is called the client–
server model, and a single overall computation is distributed across multiple
processes or devices.

8
 1.5 Document Conventions
Font: Times New Roman font size 12 for normal text and 14 for headings throughout the
document for text.
Comments: Italics
Spacing: Document text is single spaced
Line Margins: 1” margins are used in this template.

4.1.1.6 References
www.stackoverflow.com
www.wikipedia.org
www.github.com
n
4.1.2.1 Product Overview
The system to be developed here is a Chat facility. It is a centralized system. It is Client-
Server system with centralized database server. All local clients are connected to the
centralized server via LAN.
There is a two way communication between different clients and server.
No Need of Internet Connection: Existing system requires Internet connection; whereas in
the proposed system only Intranet connection i.e. only a LAN connection is required. This
system is useful for those who cannot afford to have an Internet connection. For example:
schools, colleges, small companies, etc.

4.1.2.2 Product Functionality

There is a two way communication between different clients and server. Only logged in
users are allowed to chat. It allows to end to end encrypted communication.

4.1.2.3 Design and Implementation Constraints

General Constraints:
The application does not by any means open the web browser. If user wishes to open the
web browser he must open it externally. The system need to be permanent connected
with intranet.

4.1.2.4 Assumptions and Dependencies

There should be LAN connection. Clients should know each other. There can be multiple
clients.
3 Specific Requirements
4.1.3.1 External Interface Requirements
3.1.1 User Interfaces
This application interacts with the user through GUI. The interface is simple, easy to handle
and self-explanatory.
Once opened, user will easily come into the flow with the application and easily uses all
interfaces properly.
However the basic interface available in our application is
1. Title panel
2. Content panel
3. Admin panel.

3.1.2 Hardware Interfaces

Minimum requirements will be as follows:
1. 1 GB RAM required.
2. Processor with speed of 500 MHz
3. Intranet or LAN connection.
4. MOUSE: 2 or 3 button mouse
5. KEYBOARD: 101 key Keyboard

9
3.1.3 Software Interfaces
1. NetBeans 8.2
2. Windows 7,8,10

3.2 Functional Requirements

1. There is a two way communication between different clients and server.
2. Only logged in users are allowed to chat.
3. It allows to end to end encrypted communication.

3.3 Use Case Model

TO DO: Provide a use case diagram that will encapsulate the entire system and all actors.

3.3.1 Use Case #1 (use case name and unique identifier – e.g. U1)

Author – Identify team member who wrote this use case

Purpose - What is the basic objective of the use-case? What is it trying to achieve?

Requirements Traceability – Identify all requirements traced to this use case

Priority - What is the priority? Low, Medium, High. Importance of this use case being
completed and functioning properly when system is deployed

Preconditions - Any condition that must be satisfied before the use case begins

Post conditions - The conditions that will be satisfied after the use case successfully
completes

Actors – Actors (human, system, devices, etc.) that trigger the use case to execute or provide
input to the use case

Extends – If this is an extension use case, identify which use case(s) it extends

Flow of Events
1. Basic Flow - flow of events normally executed in the use-case
2. Alternative Flow - a secondary flow of events due to infrequent conditions
3. Exceptions - Exceptions that may happen during the execution of the use case
Includes (other use case IDs)
Notes/Issues - Any relevant notes or issues that need to be resolved

4O

10
4.1 Performance Requirements
1. When user sends the data it will reach server firstly and server will send the data to
receiver.
2. The server verifies for which device the message was intended and sends it to that device.
3. If data format is not supported by the chatting application, then server will immediately send
warning to the sender.

4.2 Safety and Security Requirements

1. The user needs to verify its identity before operating the application
2. If user enters the password wrong for consecutively 5 times then the account will be locked
for 1 hour.
3. It has end to end encryption for the security of the messages
4. If the media transferred is not received by the receiver then the media is lost and can’t be
recovered.

4.3 Software Quality Attributes

1. Adaptability: This application is platform independent means this application can be run
on any OS.
2. Availability: This application is easily available.
3. Reliability: This application has end to end encryption and user data is secured.
4. Usability: Communication among people at organizational level privately.
5. Portability: This application is only portable in that area which is covered by the intranet
connection of the organization.

3. Design Phase
3.1 Class diagram showcasing Logical structure

11
3.2 Collaboration Diagram

12
3.3 Sequence Diagrams

13
 3.4 State Chart Diagrams

4. Testing Phase

4.1 Test Plan

 Identify which feature of the system will be tested
 Define the pass/fail criteria for each failure to be tested
 Specify the testing approach that will be used during tested
 Identify the deliverables of the testing process

4.2 Test Cases for various test strategies (Scenario, Boundary value analysis and
Equivalence class testing

4.2.1 Login Test Case

Sr. Test Case Test case Prerequisite Steps/Procedures Expected

No ID Objective & Data Result

1 TC_login_01 To check Application 1 Enter valid Valid

functionality of valid should be username in username
“username” in installed on username field. and
username field and system. 2 Enter valid password
valid “password” in password in should be
password field with password field. accepted and
minimum 6 3 Click on “login” Home Page
characters. button. should be
displayed.

14
2 TC_login_02 To check Launch the 1 Enter invalid Invalid
functionality of application. “username” in username
invalid “username” Login into the username field shouldn’t be
and valid system. 2 Enter valid accepted and
“password” in “password” in error
password field. password field. message
3 Click on “login” window
button. should be
displayed
with error
message
“Enter valid
username”.

3 TC_login_03 To check Launch the 1 Enter valid Invalid

functionality of valid application. “username” in password
“username” invalid Login into the username field shouldn’t be
“password” in system. 2 Enter invalid accepted and
password field. “password” in error
password field. message
3 Click on “login” window
button. should be
displayed
with error
message
“Enter valid
password”.

4 TC_login_04 To check Launch the 1 Enter invalid Invalid

functionality of application. “username” in password
invalid “username” Login into the username field shouldn’t be
invalid “password” system. 2 Enter invalid accepted and
in password field. “password” in error
password field. message
3 Click on “login” window
button. should be
displayed
with error
message
“Enter valid
username &
password”.

5 TC_login_05 To check Launch the 1 Enter valid Home page

functionality of application. username in should be
“Login” Button Login into the username field. displayed on
system. 2 Enter valid the screen
password in
password field.
3 Click on “login”
button.

15
4.2.2 Navigation Test Case

Sr. Test Case Test case Prerequisite Steps/Procedures & Expected

No ID Objective Data Result

1 TC_nav_01 To check Application should 1 After successful Valid

functionality of be installed on the login, redirect to home username &
navigation from system & the first page. password
home page to page that users will 2 Through the home should be
other menu access should be page navigate to accepted and
links. home page other menu like “ride home page
now”. should be
3 When transaction is displayed.
done, click on “logout” Click on other
button. menu for other
functions.

16
5. Deployment Phase
5.1 Component Diagram

5.2 Deployment Diagram

17