A PRELIMINARY PROJECT REPORT

ON

"Project Name"

Submitted to the Dr. Babasaheb Ambedkar technical university ,Lonere in the

partial fulfillment of the requirements for the award of degree

of

BACHLORE OF TECHNOLOGY

IN COMPUTER SCIENCE &ENGINEERING

BY

NAME 1 PRN No.:B120534340

NAME 2 PRN No.:B120534248
NAME 3 PRN No.:B120534314
NAME 4 PRN No.:B120534207

DEPARTMENT OF COMPUTER SCIENCE & ENGINEERING

JSPM | SBERCT’s
BHAGWANT INSTITUTE OF TECHNOLOGY, BARSHI

YEAR 2022-23
 JSPM | SBERCT’s
BHAGWANT INSTITUTE OF TECHNOLOGY, BARSHI

CERTIFICATE
This is to certify that the preliminary project report entitled

“Project Name”

Submitted by

NAME 1 PRN No.:B120534340

NAME 2 PRN No.:B120534248
NAME 3 PRN No.:B120534314
NAME 4 PRN No.:B120534207

is a bonafide work carried out and is approved for the partial fulfillment of the require-
ment of Dr. Babasaheb Ambedkar Technical University,Lonere for the award of the
Degree of Bachelor of technology in Computer science & Engineering This project work
has not been earlier submitted to any other Institute or University for the award of any
degree or diploma.

Place : Barshi
Date :

(Name) (Name) (Name)

Internal Guide Head Principal
Department of CSE Department of CSE BIT,Barshi
 ACKNOWLEDGEMENT

The satisfaction that accompanies the successful completion of this report would be in-
complete without mentioning of the people who made it possible, without whose constant
guidance and encouragement would have made efforts go in vain. I consider myself priv-
ileged to express gratitude and respect towards all those who guided me throughout the
completion of this seminar report.
Firstly, I would like to sincerely thank my guide (Guide name) for guiding me regarding
this project. My multiple discussions with her were extremely helpful for me. It is my
privilege to acknowledge the kind of guidance I received in preparation of this report. I
would not be able to prepare this report without her valuable cooperation.
I am grateful to (HOD name) , Head of the Department Computer Engineering for giving
me the support and encouragement that was necessary for the completion of this project.
I whole heartedly thank to record our sincere gratitude to Management of this college and
to my Principal, (principal name) , Principal, Bhagwant Institute of Technology ,Barshi
for his constant support and encouragement in preparation of this report and for making
available library and laboratory facilities needed to prepare this report.
Last but not the least, I wish to thank my parents for financing my studies in this college
as well as for constantly encouraging us to learn engineering. Their personal sacrifice in
providing this opportunity to learn engineering is gratefully acknowledged.

i
Contents

Acknowledgement i

Certificate ii

1 Synopsis 3
1.2 Project Title . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
1.4 Internal Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
1.5 Technical Keywords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
1.6 Problem Statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
1.7 Abstract . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
1.8 Goals And Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
1.9 Names of Conferences / Journals where papers can be published . . . . . 5
1.10 Review of Conference/Journal Papers supporting Project idea . . . . . . . 6
1.11 Plan of Project Execution . . . . . . . . . . . . . . . . . . . . . . . . . . 8

2 Technical Keywords 9
2.1 Area of Project.....................................................................................................10
2.2 Technical Keywords.............................................................................................10

3 Introduction 11
3.1 Introduction...........................................................................................................12
3.2 Project Idea And Motivation................................................................................12
3.3 Literature Survey..................................................................................................12

ii
4 Problem Definition and Scope 14
4.1 Problem Statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
4.2 Goals and Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
4.3 Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
4.4 Hardware And Software Resources Required .. . . . . . . . . . . . . . 15
4.4.1 Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
4.4.2 Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

5 Project Plan 16
5.1 Project Estimates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
5.2 Project Resource .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
5.3 RISK MANAGEMENTW.R.T. NP HARD ANALYSIS . . . . . . . . . . 20
5.3.1 Risk Identification . . . . . . . . . . . . . . . . . . . . . . . . . 20
5.3.2 Risk Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
5.3.3 Risk Impact Definition . . . . . . . . . . . . . . . . . . . . . . . 22
5.4 Overview of Risk Mitigation, Monitoring, Management . . . . . . . . . . 23
5.5 Project Schedule .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
5.5.1 Project task set . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
5.5.2 Task network . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
5.6 Timeline Chart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
5.6.1 TEAM ORGANIZATION . . . . . . . . . . . . . . . . . . . . . 26
5.6.2 Team Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

6 Software requirement specification 27

6.1 Introduction...........................................................................................................28
6.1.1 Purpose and Scope of Document.............................................................28
6.1.2 Overview of Responsibilities of Developer.............................................28
6.2 To test the code USAGE SCENARIO..................................................................28
6.2.1 User profiles.............................................................................................28
6.2.2 Use-cases Diagram:.................................................................................28
6.2.3 Use Case View.........................................................................................29
6.3 Data Model and Description.................................................................................29
6.3.1 Data Description......................................................................................29
6.4 Functional Model and Description.......................................................................30
6.4.1 Data Flow Diagram..................................................................................30
 6.4.2 Description of functions..........................................................................30
6.4.3 Activity Diagram:....................................................................................32
6.4.4 Sequence Diagram:..................................................................................33
6.4.5 Non Functional Requirements:................................................................34
Interface Requirements:...........................................................................34
6.4.6 Hardware Interfaces.................................................................................34
6.4.7 Software Interfaces..................................................................................34
6.4.8 Communication Interfaces.......................................................................35
6.5 Performance Requirements:..................................................................................35
6.6 Software Interface Description.............................................................................35

7 SYSTEM DESIGN 36
7.1 Introduction...........................................................................................................37
7.1.1 Advantages for customers in shopping centers.......................................37
7.1.2 Advantages for mall operators.................................................................37
7.1.3 Advantages for shop owners....................................................................38
7.2 Architectural Design.............................................................................................39

8 CONCLUSION AND FUTURE SCOPE 40

8.1 Conclusion............................................................................................................41
8.2 Future Scope.........................................................................................................41

iv
List of Figures

5.1 Plan of execution..................................................................................................17

5.2 Risk Analysis........................................................................................................21
5.3 Risk Definition.....................................................................................................22
5.4 Risk Impact definitions........................................................................................23
5.5 Task network........................................................................................................25
5.6 Timeline Chart......................................................................................................26

6.1 Use case................................................................................................................29

6.2 Use case................................................................................................................30
6.3 Activity Diagram..................................................................................................32
6.4 Sequence Diagram...............................................................................................33
7.1 Architectural Design............................................................................................39

v
List of Tables

vi
Chapter 1

Synopsis
1.1 Project Title

1.2 Internal Guide

1.3 Technical Keywords

1.4 Problem Statement

1.5 Abstract

1.6 Goals And Objectives

1.7 Names of Conferences / Journals where papers can

be published

• ACM(Association for Computing Machinery)

• IEEE(Institute of Electrical and Electronics Engineers)

• IJARIIE(International Journal of Advanced Research and Innovative Ideas in Edu-

cation)

• IJIET(International Journal of Industrial Engineering Technology)

• IJET(International Journal of Engineering and Technology)

• IERJ(International Education and Research Journal)

• IJARIIT(International Journal of Advance Research,Ideas and Innovations In Tech-

nology)
1.8 Review of Conference/Journal Papers supporting
Project idea

M. Youssef and A. Agrawala, “The horus WLAN location determination system,” in Pro-
ceedings of the 3rd international conference on Mobile systems, applications, and services.
ACM, 2005, pp. 205–218.

L. Koski, R. Piche, V. Kaseva, S. Ali-L oytty, and M. H annik ainen, “Positioning with
coverage area estimates generated from location fingerprints,” in Proc. of the 7th Work-
shop on Positioning, Navigation and Communication. WPNC’10, Mar 2010, pp. 99–106

L. Koski, T. Peral a, and R. Pich e, “Indoor positioning using WLAN coverage area esti-
mates,” in Proc. Int. Conf. Indoor Positioning and Indoor Navigation, Sep 2010, pp. 1–7.

H. Nurminen, Position estimation using RSS measurements with unknown measurement

model parameters. MSc Thesis, Tampere University of Technology, 2012.

W. Storms, J. Shockley, and J. Raquet, “Magnetic field navigation in an indoor environ-

ment,” in Ubiquitous Positioning Indoor Navigation and Location Based Service (UPINLBS),
2010. IEEE, 2010, pp. 1–10

K. B. Anonsen and O. Hallingstad, “Terrain aided underwater navigation using point mass
and particle filters,” in Proceedings of the IEEE/ION Position Location and Navigation
Symposium, vol. 2006, 2006, pp. 1027–1035.
D. Dardari, P. Closas, and P. M. Djuric, “Indoor tracking: Theory, methods, and technolo-
gies,” Vehicular Technology, IEEE Transactions on, vol. 64, no. 4, pp. 1263–1278, 2015.

M. Arulampalam, S. Maskell, N. Gordon, and T. Clapp, “A tutorial on particle filters for

online nonlinear/non-Gaussian Bayesian tracking,”

1.9 Plan of Project Execution

SDLC Processes regarding to the Project:-

Planning: - We started the plan for domain selection point. Found two Domains IOT and
Grid Android.

Requirement Gathering: Gathering of information for the two domains was successful.
Android was user based and easy implementation part of the system, while IOT had a great
aspect, but was difficult for the implementation process.

Scheduling:- The project we selected is related to Indoor Mapping using beacon. Beacon
uses Bluetooth connection as major part for the project to connect to the smartphones.
Hence we started scheduling the project in two teams.

Designing: - The designing of GUI and hardware parts was important, also completion of
project report and paper publishing was processed in this sector.

Implementation: - The first half was designed as Phase I Implementation (Module 1).
While the later consisted of Phase II and Final implementation process.

Testing: - Check whether beacon is giving the accurate range to user for navigating the
path

Deployment: - Creation of .exe file and publishing it is the main part of deployment
process.
Chapter 2

Technical

Keywords
2.1 Area of Project

2.2 Technical Keywords

Chapter 3

Introduction
3.1 Introduction

3.2 Project Idea And Motivation

3.3 Literature Survey

Topic Name-Indoor Positioning of Shoppers Using a Network of Bluetooth Low Energy

Beacons

Year-2016

Author - Patrick Dickinson, Gregorz Cielniak, Olivier Szymanezyk , Mike Mannion

Description - In this paper ,we present our work on the indoor positioning of users (shop-
pers), using a network of Bluetooth Low Energy (BLE) beacons deployed in a large whole-
sale shopping store. Our objective is to accurately determine which product sections a user
is adjacent to while traversing the store, using RSSI readings from multiple beacons, mea-
sured asynchronously on a standard commercial mobile device.

11
Topic Name -An Indoor Location-aware System for an IoT based Smart Museum .

Year – 2016

Author - S. Alletto, R. Cucchiara, G. Del Fiore, L. Mainetti, V. Mighali, L. Patrono, and

G. Serra

Description - The new technologies characterizing the Internet of Things allow realizing
real smart environments able to provide advanced services to the users. Recently, these
smart environments are also being exploited to renovate the users interest on the cultural
heritage

Topic Name - A location aware personalized smart control system

Year – 2014

Author - K.P. Subbu and N. Thomas

Description - The smart control system sense the identify the location of user in different
room. In this require active passive RFID and NFS system ,so it have lot of installation
and sensor data managing.

12
Chapter 4

Problem Definition and Scope

13
4.1 Problem Statement

4.2 Goals and Objectives

4.3 Application

4.4 Hardware And Software Resources Required

4.4.1 Hardware

4.4.2 Software

14
Chapter 5

Project Plan

15
In Order to produce high quality software SDLC process is followed by industry. SDLC
aims to produce a high quality software that meets or beats customer expectations, Reaches
completion within times and cost estimates. There are various Software development life
cycle models defined and designed which are followed During software development pro-
cess. For the first Phase of the project Waterfall Model is to be followed.

5.1 Project Estimates

Figure 5.1: Plan of execution

16
 • Requirement Gathering and analysis :
All possible requirements of the system to be developed are captured in this phase
and documented in a requirement specification document.

• System Design:
The requirement specifications from first phase are studied in this phase and the
system design is prepared. This system design helps in specifying hardware and
system requirements and helps in defining the overall system architecture.

• Implementation:
With inputs from the system design, the system is first developed in small programs
called units, which are integrated in the next phase. Each unit is developed and
tested for its functionality, which is referred to as Unit Testing.

• Integration and Testing:

All the units developed in the implementation phase are integrated into a system
after testing of each unit. Post integration the entire system is tested for any faults
and failures.

• Deployment of system :
Once the functional and non-functional testing is done; the product is deployed in
the customer environment or released into the market.

• Maintenance:
There are some issues which come up in the client environment. To fix those issues,
patches are released. Also to enhance the product some better versions are released.
Maintenance is done to deliver these changes in the customer environment.

5.2 Project Resource

Developers – 2
Testers -2
Eclipse Editor
At least 2 laptops with Windows OS
Internet connection
Java Debugging tools)
5.3 RISK MANAGEMENTW.R.T. NP HARD ANALYSIS
This section discusses Project risks and the approach to managing them.

5.3.1 Risk Identification

Impact values can be decided as

1. Domain knowledge

2. Technology will not Meet Expectations

3. Lack of Development Experience

4. Quality Documentation

5. Deviation from Software Engineering Standards

6. Poor Comments in Code

7. Changes in Requirements
5.3.2 Risk Analysis

The risks for the Project can be analyzed within the constraints of time
and quality

Figure 5.3: Risk Analysis

20
5.3.3 Risk Impact Definition

Figure 5.4: Risk Definition

5.4 Overview of Risk Mitigation, Monitoring,
Management

Following are the details for each risk.

Figure 5.5: Risk Impact definitions

Solution 1

When working on the product or documentation, the staff member should always be aware
of the stability of the computing environment there working in. Any changes in the stabil-
ity of the environment should be recognized and taken seriously.

Solution 2

The schedule will be followed closely during all development stages. Steps have been
taken to ensure a timely delivery by gauging the scope of project based on the delivery
deadline.

Solution 3
The meetings with the customer should ensure that the customer and our organization
understand each other and the requirements for the product. Should the development team
come to the realization that their idea of the product specifications differs from those of
the customer, the customer should be immediately notified and whatever steps necessary
to rectify this problem should be done.

Solution 4

In order to prevent this from happening, the software will be developed with the end user
in mind. The user-interface will be designed in a way to make use of the program
convenient and pleasurable.

Solution 5

In order to prevent this from happening, meetings (formal and informal) will be held with
the customer on a routine business. This insures that the product we are producing and the
requirements of the customer are equivalent.

Solution 6

In Poor code commenting can be minimized if commenting standards are better expressed.
While standards have been discussed informally, no formal standard yet exists. A formal
written standard must be established to ensure quality of comments in all code.

5.5 Project Schedule

5.5.1 Project task set

Major Tasks in the Project stages are:

1. Major Tasks in the Project stages are:

2. Task 1:Communication.

3. Task 2:Planning.

4. Task 3:Risk Management.

5. Task 4:Modelling
5.5.2 Task network

Here are the project tasks and their dependencies in this diagrammatic form

Figure 5.6: Task network

T1: Communication Software development process starts with the communication be-
tween customer and developer. According to need of project, we gathered the require-
ments related to project.

T2: Planning It includes complete estimation and scheduling.

T3:Risk Management It includes identifying the risks during project development and
managing the risks which are affecting the project development.

T4:Modelling It includes detailed requirement analysis and project design.

24
5.6 Timeline Chart

5.6.1 TEAM ORGANIZATION

The manner in which staffs are organized and the mechanisms for reporting is given
below:

Figure 5.7: Timeline Chart

5.6.2 Team Structure

The team structure for the project is identified. Roles are defined. Management reporting
and communication Mechanisms for progress reporting and inter/intra team communica-
tion are identified as per assessment sheet and lab time table.
Chapter 6

Software requirement specification

26
6.1 Introduction

6.1.1 Purpose and Scope of Document

The SRS is used for developer and testers of this system who wanted to build and test the
system of carpooling.

6.1.2 Overview of Responsibilities of Developer

Developers will be having the following responsibility:

• To design this system

• To develop this system

• To do modular unit testing of this system

• To provide the details documentation of system

• To write the code and do bug fixing.

• To test the system

6.2 To test the code USAGE SCENARIO

This section provides various usage scenarios for the system to be developed.

6.2.1 User profiles

This system will be having two user actor.

6.2.2 Use-cases Diagram:

Use case diagram for satisfying above conditions is constructed. Refer given Diagram
which gives thorough explanation of use cases in this project.

27
6.2.3 Use Case View

Use Case Diagram. Example is given below

Figure 6.1: Use case

6.3 Data Model and Description

6.3.1 Data Description

We will be using MySQL database to save users credentials. Here we are not using any
files to save any data. Only database will be used for saving all types of data.

• Hence we will require 2-3 tables to save above listed data.

1. Garbage info table

2. User info table Data objects and Relationships

28
6.4 Functional Model and Description

Figure 6.2: Use case

6.4.1 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. A DFD is often used as a preliminary
step to create an overview of the system, which can later be elaborated.

6.4.2 Description of functions

6.4.3 Activity Diagram:

The Activity diagram represents the steps taken:

Figure 6.3: Activity Diagram

6.4.4 Sequence Diagram:

Figure 6.4: Sequence Diagram

6.4.5 Non Functional Requirements:

Interface Requirements:

User Interfaces

Client Side:

6.4.6 Hardware Interfaces

6.4.7 Software Interfaces

6.4.8 Communication Interfaces

6.5 Performance Requirements:

Chapter 7

SYSTEM DESIGN
 7.1 Introduction
7.2 Architectural Design

Figure 7.2: Architectural Design

Chapter 8

CONCLUSION AND FUTURE SCOPE

8.1 Conclusion

Conclusion:

8.2 Future Scope

Future Scope: