A MINI PROJECT REPORT

On

COLLEGE PHONEBOOK

Submitted in partial fulfilment of the requirement for the award of

Degree of

BACHELOR OF TECHNOLOGY

IN

COMPUTER SCIENCE & ENGINEERING

BY

Vengala Siri chandana (15641A0558)

Pranay Reddy Parnem (15641A0507)

Oruganti Bala Ridhima Reddy (15641A0531)

Under the esteemed guidance of

Mr. Bandi Krishna

(Assistant Professor)

DEPARTMENT OF COMPUTER SCIENCE & ENGINEERING

VAAGDEVI COLLEGE OF ENGINEERING, WARANGAL

(Affiliated to Jawaharlal Nehru Technological University, Hyderabad, T.S)
(Accredited by National Board of Accreditation)
Bollikunta, Warangal (T.S) – 506005 (2015-2019)
 VAAGDEVI COLLEGE OF ENGINEERING, WARANGAL

Department of Computer Science and Engineering

(Affiliated to Jawaharlal Nehru Technological University, Hyderabad, T.S)

(Accredited by National Board of Accreditation)

Bollikunta, Warangal (T.S) – 506005

CERTIFICATE

This is to certify that project entitled as “COLLEGE PHONEBOOK “is prepared and submitted by
Vengala Siri chandana (15641A0558), Pranay Reddy Parnem (15641A0507), Oruganti Bala Ridhima
Reddy (15641A0531) and impartial fulfilment for the award of Bachelor of Technology in Computer
Science and Engineering is record work carried out by under the guidance and supervision.

Project Guide Head of the department

Mr. Bandi Krishna Dr .V. Janaki
 ACKNOWLEDGEMENT

We would like express our gratitude to all the people behind the screen who helped us to
transform an idea into a real application.

We would like to express our heart-felt gratitude to the principle, Mr. Dr. K. PRAKASH for his
extending support in initiating and establishing the industry interaction scenario which helped us in
successful completion of our project.

We profoundly thank Dr.V.JANAKI, Head of the department of Computer Science and

Engineering who has been an excellent guide and also a great source of inspiration to our work.

We also express our gratitude to all other lecturers and lab coordinators, non-teaching staff who
directly or indirectly helped us in completing project successfully and providing us with encouraging
guidance throughout.

Vengala Siri Chandana (15641A0558)

Pranay Reddy Parnem (15641A0507)

Oruganti Bala Ridhima Reddy (15641A0531)

 DECLARATION

We hereby declare that this project entitled “COLLEGE PHONEBOOK” is submitted in partial
fulfilment of requirements for the award of bachelor of technology at VAAGDEVI COLLEGE OF
ENGINEERING (AUTONOMOUS) affiliated to Jawaharlal Nehru Technology University. The report
has not been submitted either in part or full for degree earlier to this University.

Vengala siri chandana 15641A0558

Pranay reddy parnem 15641A0507

Oruganti bala ridhima reddy 15641A0531

 ABSTRACT

Project Description:

In every college there could be more than 4 to 5 departments and lot of faculty (Teaching and Non-
teaching). Apart from these teams we may have administration teams working in the college who will
take care of day to day college admin and infrastructure operations. It may be impossible to anyone in
the college to save the phone numbers of each and every person who is working in the college.
However, they may have a requirement to contact them some or the other occasion in the college. So
we would like to propose an application for Android Smart phones, by installing which we can have all
contacts in the mobile at once. However this has a provision to avoid including them in the Phone book.
The application will display not only contact number but also his qualification, email Id, Department,
experience, photo etc. User can modify the above details at any point of time in his phone. All the
contact numbers are segregated department wise so that it is easy to access.

Existing System:

User need to add all the contacts in the phone manually. They can also update and delete however it is
very tedious process. They don’t have provision to email from the contacts.

Proposed System:

In this application every one can maintain the details about all the employees in their mobile
sonly. So we can easily reach all the employees of the college. It consists of employee information like
qualification, phone number, email, designation and experience. From this application only we can call
and send a message to who we want to communicate.

Modules

The modules can be divided into different types.

 Gathering the contact info & Storing Information

 Modify Information.
 Making Communication (Call & Message)
 Branch wise division of information.
 1. INTRODUCTION

1.1 PURPOSE

The project College Phonebook is mainly designing for college staff. In college there are many
departments like CSE, ECE, MECH, CIVIL etc. All departments has the teaching and non-teaching
staff .To identify the details of the staff in our smart phone. The details consists of name of the
person, mobile number, his/her experience, qualification and e-mail id, date of birth, address,
gender, department.

1.2 DOCUMENT CONVENTIONS

We have used Times New Roman (text size of 12), Bold Font is used for Main Headings (text size
of 14), Bold, Underline and Italicized font is used for Modules (text size of 14).Underlining is done for
technically important words.

Font: Times New Roman

Font style: size: 10px
Main heading: Bold Font,14px
 1.3 INTENDED AUDIENCE & READING SUGGESTIONS

This document is for better understanding of student’s project details and it is mainly intended
for HOD, Project Incharge, Internal Guide, Administrator and users. The details given below guide
every student about their project for better understanding. The sequence to follow is here purpose, scope,
features of the monitoring software, operating system requirements, modules present in the project,
advantages, references etc.

1.4 PROJECT SCOPE

The application will display not only contact details but also his qualification, email id,
Department, experience etc. User can modify the above details at any point of time in his phone. All the
contact numbers are segregated department wise for easy accessing.
 2. SOFTWARE REQUIREMENT ANALYSIS

2.1 EXISTING SYSTEM

User need to add all the contacts in the phone manually. They can also update and delete

however it is very tedious process. They don’t have provision to email from the contacts.

2.2 PROPOSED SYSTEM

In this application every one can have the details of employees in their mobile only. So we can
easily reach all the employees of the college. It consists of employee information like qualification,
phone number, email, designation and experience. From this application only we can call and send a
message to who we want to communicate.

2.3 PRODUCT FEATURES

 In this module we can store the particular details about employee who are working in their
college. We can store the details like qualification, phone number, email, designation and
experience.
 In this the person can make a call by using the call option and also send message using message
option.

2.4 OPERATING ENVIRONMENT

Software requirements used in this project are Eclipse technology, XML Language for Front
end , Back End Language SQLite database, Middleware Language is java. Hardware requirements used
in this project are i5 processor, 512 MB of main memory (RAM) and database memory.
2.5 MODULES
The modules can be divided into different types.

 Gathering the contact info & Storing Information.

 Modify Information.
 Branch wise division of information.
 Making Communication (Call &Message).

Storing Information:

In this module we can store the particular details about employee who are working in their
college. We can store the details like qualification, phone number, email, designation and experience
etc.

Modify Information:

In this module the person can edit the contacts and also can add the details about employee.

Branch wise division of information:

In this module the details of employees are segregated between the department wise and also
between the teaching staff and Non-teaching staff.

Making communication:

In this the person can make a call by using the call option and also send message using message
option.
 3. SOFTWARE DESIGN

3.1 Use Case Diagrams

3.1.1 Use case diagram for User

3.2 Class diagram
3.2.1 Class Diagram for User
3.3 Sequence Diagram

3.3.1 User
3.4 Object Diagram

3.4.1 Object Diagram for user

:
3.5 Activity Diagram

3.5.1 Activity Diagram for User

3.6 Deployment Diagram

3.6.1 Deployment Diagram for User

 4. HARDWARE AND SOFTWARE REQUIREMENTS

4.1 Hardware Requirements

Processor : I3 processor and above

RAM : 2 GB and above

Hard disk : 100 GB and above

4.2 Software Requirements

Frontend Technology : Eclipse

Frontend Language : XML

Middle Language : Java

Backend : SQLite Database

Android Technology : sdk 1.5 and above

Operating system : windows 7 and above

 5. SYSTEM DESIGN

System design is transition from a user oriented document to programmers or data base personal. The
design is a solution, how to approach to the creation of a new system. This is composed of several steps.
It provides the understanding and procedural necessary details for implementing the system
recommended in the feasibility study. Designing goes through logical and physical stages of
development, logical design reviews of the present physical system, prepared input and output
specifications, details of implementation of plan and prepared logical design walkthrough.

The database tables are designed by analyzing functions involved in the system and format
of the fields are also designed. The fields in the database tables should define their role in the system.
The
unnecessary fields should be avoided because it affects the storage areas of the system. Then in the input
and output screen design, the design should be made user friendly. The menu should be precise and
compact

SOFTWARE DESIGN
In designing the software following principles are followed:

1. Modularity and partitioning: software is designed such that, each system should consists of

hierarchy of modules and serve to partition into separate function.

2. Coupling: modules should have little dependence on other modules of a system.

3. Cohesion: modules should carry out in a single processing function.

4. Shared use: avoid duplication by allowing a single module is called by other that need the function it
provides.
 6.CODE
package com.vaagdevi.collegephonebook;

import android.app.Activity;
import android.content.Intent;
import android.database.Cursor;
import android.database.sqlite.SQLiteDatabase;
import android.os.Bundle;
import android.view.Menu;
import android.view.MenuItem;
import android.view.View;
import android.view.View.OnClickListener;
import android.widget.Button;
import android.widget.Toast;

public class BranchActivity extends Activity {

SQLiteDatabase db4;

@Override
protected void onCreate(Bundle savedInstanceState) {
super.onCreate(savedInstanceState);
setContentView(R.layout.activity_branch);
final Button cse=(Button)findViewById(R.id.button1);
final Button ece=(Button)findViewById(R.id.button2);
final Button eee=(Button)findViewById(R.id.button3);
final Button mech=(Button)findViewById(R.id.button4);
final Button civil=(Button)findViewById(R.id.button5);
final Button it=(Button)findViewById(R.id.button6);
db4=openOrCreateDatabase("vaagdevi", MODE_PRIVATE, null);
cse.setOnClickListener(new OnClickListener() {

@Override
public void onClick(View arg0) {
// TODO Auto-generated method stub
String s=cse.getText().toString();
Intent it=new Intent(BranchActivity.this,TechniActivity.class);
it.putExtra("data", s);
startActivity(it);
}
});

ece.setOnClickListener(new OnClickListener() {

@Override
public void onClick(View arg0) {
// TODO Auto-generated method stub
 String s1=ece.getText().toString();
Intent it1=new Intent(BranchActivity.this,TechniActivity.class);
it1.putExtra("data", s1);
startActivity(it1);
}
});
eee.setOnClickListener(new OnClickListener() {

@Override
public void onClick(View arg0) {
// TODO Auto-generated method stub
String s2=eee.getText().toString();
Intent it2=new Intent(BranchActivity.this,TechniActivity.class);
it2.putExtra("data", s2);
startActivity(it2);
}
});
mech.setOnClickListener(new OnClickListener() {

@Override
public void onClick(View arg0) {
// TODO Auto-generated method stub

String s3=mech.getText().toString();
Intent it3=new Intent(BranchActivity.this,TechniActivity.class);
it3.putExtra("data", s3);
startActivity(it3);
}
});
civil.setOnClickListener(new OnClickListener() {

@Override
public void onClick(View arg0) {
// TODO Auto-generated method stub
String s4=civil.getText().toString();
Intent it4=new Intent(BranchActivity.this,TechniActivity.class);
it4.putExtra("data", s4);
startActivity(it4);
}
});
it.setOnClickListener(new OnClickListener() {

@Override
public void onClick(View arg0) {
// TODO Auto-generated method stub
String s5=it.getText().toString();
Intent it5=new Intent(BranchActivity.this,TechniActivity.class);
it5.putExtra("data", s5);
startActivity(it5);
 }
});

}
}
 7. SOFTWARE TESTING

Testing

Software testing is a critical element of software quality assurance and represents the
ultimate review of specification, design and code generation.

7.1 TESTING OBJECTIVES

 To ensure that during operation the system will perform as per specification.
 To make sure that system meets the user requirements during operation
 To make sure that during the operation, incorrect input, processing and output will be
detected
 To see that when correct inputs are fed to the system the outputs are correct
 To verify that the controls incorporated in the same system as intended
 Testing is a process of executing a program with the intent of finding an error
 A good test case is one that has a high probability of finding an as yet undiscovered
error

The software developed has been tested successfully using the following testing strategies and
any errors that are encountered are corrected and again the part of the program or the procedure or
function is put to testing until all the errors are removed. A successful test is one that uncovers an as
yet undiscovered error.

Note that the result of the system testing will prove that the system is working correctly. It will
give confidence to system designer, users of the system, prevent frustration during implementation
process etc.
7.2 TEST CASE DESIGN

7.2.1 White box testing

White box testing is a testing case design method that uses the control structure of the
procedure design to derive test cases. All independents path in a module are exercised at least once,
all logical decisions are exercised at once, execute all loops at boundaries and within their operational
bounds exercise internal data structure to ensure their validity. Here the customer is given three
chances to enter a valid choice out of the given menu. After which the control exits the current menu.

7.2.2 Black Box Testing

Black Box Testing attempts to find errors in following areas or categories, incorrect or missing
functions, interface error, errors in data structures, performance error and initialization and
termination error. Here all the input data must match the data type to become a valid entry.The
following are the different tests at various levels:

7.2.3 Unit Testing

Unit testing is essentially for the verification of the code produced during the coding
phase and the goal is test the internal logic of the module/program. In the Generic code project,
the unit testing is done during coding phase of data entry forms whether the functions are
working properly or not. In this phase all the drivers are tested they are rightly connected or not.

7.2.4 Integration Testing

All the tested modules are combined into sub systems, which are then tested. The goal is
to see if the modules are properly integrated, and the emphasis being on the testing interfaces
between the modules. In the generic code integration testing is done mainly on table creation
module and insertion module.
7.2.5 Validation Testing

This testing concentrates on confirming that the software is error-free in all respects. All the
specified validations are verified and the software is subjected to hard-core testing. It also aims at
determining the degree of deviation that exists in the software designed from the specification; they
are listed out and are corrected.

7.2.6 System Testing

This testing is a series of different tests whose primary goal is to fully exercise the computer-based
system. This involves:
 Implementing the system in a stimulated production environment and testing it.
 Introducing errors and testing for error handling.

7.3 Test case 1

Test case for name in Registration form

When a user enters only name in the form then it displays a toast message to enter the “FULL NAME”.

7.4 Test case 2

Test case for phone number in Registration form

When the user enters the wrong no of digits then it displays a toast message to enter a “VALID
MOBILE NUMBER”.

7.5 Test case 3

Test case for Email id in registration form

When the user does not enter correct email id according to the validation then a toast message is
displayed that “ PLEASE ENTER THE CORRECT EMAIL ID”.
8. OUTPUT SCREENS
 9. CONCLUSION

The college phonebook project has been successfully completed. The goal of the project is
achieved and the problems are solved. This project is developed in a manner that is user friendly and
required help is provided at different levels.
Here our application will be simple and user friendly which will simplify user work easily.