ASSIGNMENT 3
SUBJECT CODE : CS02414
SUBJECT NAME : Internet Programming – 5G
SEM / YEAR : IV / 2ND
TITLE : Student Chat Box
NAME : P. Muzakir
REG NO : 191711306
GRADING RUBRICS
S.No Components Marks(100) Marks Remarks
Scored
1. Results and Discussion 90
Environment/Test bed used (5)
Number of test samples taken (5)
Duration of running time for taking results (5)
Number of trails for taking results (5)
Accuracy (5)
Scalability (5)
Reliability (5)
Security (5)
Quality and quantity of input and output (5)
Performance Metrics (5)
Comparison Graph (4 graphs ) (4 x 5 = 20)
Applications (5 )
User friendly (5)
Installation guide (10)
2. Conclusion 5
3. References 5
Total 10
0
STUDENT CHAT BOX
ENVIRONMENT/TEST BED USED
A testing environment is a setup of software and hardware for the testing teams to execute test
cases. In other words, it supports test execution with hardware, software and network configured.
Test bed or test environment is configured as per the need of the Application Under Test. On a few
occasion, test bed could be the combination of the test environment and the test data it operates.
This project is tested under the following environment
Windows 10 ×64
Windows 10 ×32
Windows 8 ×64
Windows 8 ×32
Windows 7 ×64
Windows 10 ×32
Windows phone emulator
The system worked finely in all the above software.
NUMBER OF TEST SAMPLES TAKEN
The software is tested seven times based on the following
Firstly I created login form using html and tested it till it worked finely.
Test for user registration
Testing for logout
Test for chatting
DURATION OF RUNTIME FOR TAKING TESTS
Runtime is the period of time when a program is running. It begins when a program is opened and
ends with the program is quit or closed.
Runtime is a technical term, used most often in software development. It is commonly seen in the
context of a "runtime error," which is an error that occurs while a program is running. The term
"runtime error" is used to distinguish from other types of errors, such as syntax errors and
compilation errors, which occur before a program is run.
When a program is in the runtime phase, the application is loaded into RAM. This includes the
executable file and any libraries, frameworks, or other files referenced by the program. When the
program is quit, the runtime period ends and the memory used by the program is made available
for use by other programs.
Duration of runtime for login and inserting into database – 1.2sec
Duration of runtime for logout from a session – 0.567 sec
Duration of runtime for registering a new user – 1.386 sec
Duration of runtime for chatting – 1.375 sec
Duration of runtime for loading the chats – 2.879 sec
NUMBER OF TRAILS FOR TAKING RESULTS
Seven trails are done for taking the results. The snapshots of the trails are placed below
ACCURACY
The accuracy of a measurement is how close a result comes to the true value.
Systematic error or Inaccuracy is quantified by the average difference (bias) between a set of
measurements obtained with the test method with a reference value or values obtained with a
reference method.
In this system very good accuracy is maintained. No data errors are found while chatting and no
data is corrupted.
You can see in the following chat between 2 clients there are no errors in in sending and receiving
the data.
From the above snapshots we can see there is no data error and there is data accuracy.
SCALABILITY
Scalability Testing is defined as the ability of a network, system or a process to continue to function
well when changes are done in the size or volume of the system to meet a growing need. It is a
type of non-functional testing.
Scalability testing ensures that an application can handle the projected increase in user traffic, data
volume, transaction counts frequency, etc. It tests the system, processes, and databases ability to
meet a growing need.
It is also referred to as performance testing, as such, it is focused on the behavior of the application
when deployed to a larger system or tested under excess load.
In Software Engineering, Scalability Testing is to measure at what point the application stops
scaling and identify the reason behind it.
Scalability testing lets you determine how your application scales with increasing
workload.
Determine the user limit for the Web application.
Determine client-side degradation and end user experience under load.
Determine server-side robustness and degradation.
Here are few Scalability Testing Attributes:
Response Time
Screen transition
Throughput
Time (Session time, reboot time, printing time, transaction time, task execution time)
Performance measurement with a number of users
Request per seconds, Transaction per seconds, Hits per second
Performance measurement with a number of users
Network Usage
CPU / Memory Usage
Web Server
Performance measurement under load
RELIABILITY
Software reliability testing a testing technique that relates to testing a software's ability to function
given environmental conditions consistently that helps uncover issues in the software design and
functionality.
PARAMETERS INVOLVED IN RELIABILITY TESTING:
Dependent elements of reliability Testing
Probability of failure-free operation
Length of time of failure-free operation
The environment in which it is executed
Key Parameters that are measured as part of reliability are given below
MTTF: Mean Time To Failure
MTTR: Mean Time To Repair
MTBF: Mean Time Between Failures (= MTTF + MTTR)
SECURITY
Security Testing is a type of software testing that intends to uncover vulnerabilities of the system
and determine that its data and resources are protected from possible intruders.
FOCUS AREAS
There are four main focus areas to be considered in security testing
NETWORK SECURITY
This involves looking for vulnerabilities in the network infrastructure
SYSTEM SOFTWARE SECURITY
This involves assessing weaknesses in the various software the application depends on.
CLIENT-SIDE APPLICATION SECURITY
This deals with ensuring that the client cannot be manipulated.
SERVER-SIDE APPLICATION SECURITY
This involves making sure that the server code and its technologies are robust enough to fend off
any intrusion.
The system provides the security on both server side and client side. The application has login
page that will provide more security to the application. Once the user is logged in and leaved the
system the seesion will get expired and the user has to login again.
QUALITY AND QUANTITY OF INPUT AND OUTPUT
In this system the input and output are accurate and system will store the data into the database. In
the snapshot below the input given by the client and the output received by other client are same.
PERFORMANCE METRICS
Software metrics can be classified into three categories −
PRODUCT METRICS
Describes the characteristics of the product such as size, complexity, design features, performance,
and quality level.
PROCESS METRICS
These characteristics can be used to improve the development and maintenance activities of the
software.
PROJECT METRICS
This metrics describe the project characteristics and execution. Examples include the number of
software developers, the staffing pattern over the life cycle of the software, cost, schedule, and
productivity.
Some metrics belong to multiple categories. For example, the in-process quality metrics of a
project are both process metrics and project metrics.
Software quality metrics are a subset of software metrics that focus on the quality aspects of the
product, process, and project. These are more closely associated with process and product metrics
than with project metrics.
Software quality metrics can be further divided into three categories
Product quality metrics
In-process quality metrics
Maintenance quality metrics
Product Quality Metrics
This metrics include the following −
Mean Time to Failure
Defect Density
Customer Problems
Customer Satisfaction
Mean Time to Failure
It is the time between failures. This metric is mostly used with safety critical systems such as the
airline traffic control systems, avionics, and weapons.
DEFECT DENSITY
It measures the defects relative to the software size expressed as lines of code or function point,
etc. i.e., it measures code quality per unit. This metric is used in many commercial software
systems.
CUSTOMER PROBLEMS
It measures the problems that customers encounter when using the product. It contains the
customer’s perspective towards the problem space of the software, which includes the non-defect
oriented problems together with the defect problems.
COMPARISION GRAPH
CHAT TIMINGS
CHATTING BY GENDER
APPLICATIONS
This application is used for students to chat and to solve doubts
This is used to chat when there is no mobile network
This can be used for communicating between others
USER FRIENDLY
This application is very user friendly as the user interface is very friendly. You can see the
snapshots below.
CONCLUSION
The main objective of the project is to develop a Secure Chat Application. I had taken a wide range
of literature review in order to achieve all the tasks, where I came to know about some of the
products that are existing in the market. I made a detailed research in that path to cover the loop
holes that existing systems are facing and to eradicate them in our application. Using this system
we can chat with teachers and among the students and can solve the doubts.
REFERENCES
1. Mayur Jain,” Smart Home System Using Android Mobile Devices”, Journal of Computing
Technologies Vol 2, Issue 3 ISSN 2278 – 3814.
2. IEEE std. 802.15.4 - 2003: “Wireless Medium Access Control (MAC) and Physical Layer
(PHY) specifications for Low Rate Wireless Personal Area Networks (LRWPANs)”
3. KiumiAkingbehin,Akinsola Akingbehin.,“Alternativ es for Short Range Low PowerWireless
Communications,” IEEE.2005: 94 – 95
4. A.R.Al-Ali and M. AL-Rousan. “Java-Based Home Automation System”. IEEE Transaction on
Consumer Electronics, Vol.50, No. 2, May 2004.
5. N. Sriskanthan and Tan Karand. “Bluetooth Based Home Automation System”. Journal of
Microprocessors and Microsystems, Vol. 26, pp.281-289, 2002.
6. Y.R.Dhumal,” Green House Automation using Zig bee and Smart Phone”, International Journal
of Advanced Research in Computer Science and Software Engineering Research Paper, Volume
3, Issue 5, May 2013
7. Soyoung Hwang and Donghui Yu,” Remote Monitoring and Controlling System Based on Zig
Bee Networks”, International Journal of Software Engineering and Its Applications Vol. 6, No. 3,
July, 2012
8. Sweatha K N,” ADVANCE HOME AUTOMATION USING FPGA CONTROLLER,
International Journal of Advanced Research in Computer and Communication Engineering Vol.
2, Issue 7, July 2013.
9. Asim S,Daniel.S.Junichi.F and Neema M,”Sensay:A context-aware mobile phone,”
Proceedings,seventh IEEE International symposium on Wearable computers,pp.248249,2003.
10. Fan Jiang and Saoping Ku,”How to display the data from database by Listview on Android,”
second International workshop on Intelligent Systems and Applications(ISA),2010.
