A

Project Report On
QRDROID
APPLICATION

10TH SEM OF 5TH

5 YEAR. MSC (CA&IT) (2017-2018
2018)

STUDENT NAME ROLL NO

N
Mauli M Sheth 5152

NAME OF COMPANY

Kings sky Technology Pvt. Ltd.

REPORT SUBMITTED TO

K.S. School of Business Management and Research

DATE OF SUBMISSION: 1st May, 2018.

Project Coordinator:
C Sajan Parekh

1|Page
 ACKNOWLEDGEMENT
It was a great experience working on the project of “QR Droid”. We express our gratitude
towards those who were constantly involved with us during our project. Kings sky, will
always occupies a special place in our heart, throughout our career, for both personal and
professional reasons.

The phenomenon remains same that no project ever can be executed proficiently and
efficiently without sharing the meticulous ideas, technical expertise and innovative thoughts
put forwarded by technical and non-technical veterans.

Whenever a technical project is developed, eventually it requires conductive technical

environment and technical guidance to get involved in the assigned project enthusiastically.
We also grateful to “Kings Sky” for being extremely friendly and co-operative during entire
course of our project. Their continuous help and support made the project much easy.

There is no exact word to express our regards and legitimate gratitude to one of our esteemed
techno personality, without him this project could not get an entrance towards the execution.
Our project manager is the pioneer who availed this magnificent option to us to move ahead.
He is always inspired and guided us for the right track to be followed for all the system
analysis section of this project.

From,

Mauli M Sheth

2|Page
 INDEX

NO Table Of Contents Page No

1 Introduction 3

1.1 Organization Profile

1.2 System Detail

1.2.1 Existing System

1.2.2 Proposed System

1.3 Scope of System

1.4 Objective

2 Proposed System Requirement Gathering

2.1 Stack holder of System

2.2 Requirement Gathering Technique

2.3 Project Definition

3 System Management And Planning

3.1 Feasibility Study

3.2 Hardware – Software Requirement

3.3 System Planning

3.3.1 Work Breakdown Structure

3.3.2 Grant Chart

3.4 Process Model

3|Page
4 System Analysis And Design

4.1 UML/DFD

4.2 System Flow Diagram

4.3 Data Dictionary

5 Input/output Design

6 Testing

7 Summary

7.1 Limitation

7.2 Future Scope

8 Bibliography

4|Page
 CHEAPTER INTRODUCTION
CHEAPTER-1

1.1 ORGANIZATION PROFILE:

PROFILE

1st Floor Parshwa Tower,

Above Kotak Mahindra Bank,
Pakwan Cross Road, S.G Highway,
Ahmadabad 380054

Website: www.kingsskytechnology.com
Phone: +079 - 7203057660

5|Page
Kings Sky

Kings Sky Technology Pvt. Ltd is an offshore software development and outsourcing
company specializing in the business of providing service to its client across the global. Our
clear value system and best business practises strengthened by our commitment for ‘Quality
of Time’ which makes us the trusted choice for many organizations-year after year we
strongly believe that every creation follows the strategically strong principle and the
innovative judgements. We deliver admirable results by incorporating the lessons from the
past projects and adventures. Our ability to work as an extension of your team is our
contribution.

We have the key capabilities in the fields of:

Web Development

Mobile Development

IOS Development

QA outsourcing

Responsive Web Design

We have enthusiastic team with long term steadiness which makes it possible to commit the
timely results. Our customers are completely involved in all the phases of product
development and hence we are able to maintain the clarity in our developments. For project
development we follow responsive development strategies the very beginning stage of
planning to development and hosting.

6|Page
1.2 SYSTEM DETAIL

1.2.1 Existing System:

In current system Barcode of the Book is to be scanned and provide information

related to that book. Save the history of scanned data. We can share the history of Barcode.

1.2.1 Proposed System:

Not only scan and save the barcode data but also provide editing option for the
scanned book. We can make shelf of the book according to our needs. Connecting application
with Good reads and Library Thing

1.3 SCOPE OF SYSTEM

• Age Verification: For business that are age restrictive can use barcode on a
customer’s driving license which can be scanned to confirm a customer’s age and
avoid legal problems.

• Business Tracking: Barcode system reduces manual data entry to manage record by
providing automatic process of data entry machine.

• Tickets: You can eliminate the need for printed tickets by sending customer an
electronic ticket that can be scanned off a phone screen. This also reduces the
possibility of ticket fraud.

• Quality Measurement: Barcode presents on a product can be used to provide the

quality factor of it.

1.4 OBJECTIVES

• By taking advantage of built-in camera, which is available in most modern phones,

we were able to check library item availability by scanning ISBN of a book.

• Customers can use their phone to capture title, call number and location information
about the item being viewed.

• Prior to introducing QR code in the catalogue the library students had been using
Gmail messaging functionality as a method of transferring this same information to a
patron’s phone.

7|Page
 CHEAPTER-2 PRPOSED SYSTEM REQUIREMENT
GATHERING

2.1 STACKHOLDER OF THE SYSTEM:

• Customer
• Individuals
• End user
• Sponsor
• Upper management and executive
• Human resources
• Employees outside the project team
• Project manager
• Program
• Resource managers
• Development team
• Testing team
• Procurement
• Line managers
• Licensing entities
• Outside vendors or suppliers
• Third party collaborators including subcontracting firms, independent contractors
• Government entities

8|Page
2.2 REQUIREMENT GATHERING TECHNIQUE:

• A structured approach to requirements management resolves these problems

• Develop SMART objectives which nearly guarantees the success of project
• Scientific approach requires a constant description of all activities, objectives and
corrective measures to counter potential loopholes

o Apprenticing Technique
Observes the
Business users

Understands the day

To day activities

Capture/documents
The requirement

Get signoff from

Customer

9|Page
Techniques:

o Brainstorming Technique
• Idea generation
• Idea reduction and voting

o Mind mapping technique

• Use emphasis
• Use association
• Be clear
• Layout

o Use case workshop technique

• Most popular
• Collect requirement in step by step manner
• Helps understanding the details
• Easy to document and written in natural language

o Interviewing technique
• Fix up the time with business user
• Attend the session
• Note down the information in notebook

o Reusing requirement technique

• Multiple things are present for single purpose
• Two or more modules have same functionality
• Re-use the functionality and save the time

o Prototyping technique
• Screens mock ups-> visualize application
• Present to customer
• Make sure we and customer having same
understanding
• Data flow functionality overview

10 | P a g e
2.3 PROJECT DEFINITION:

QRDroid application that scan book barcode and provide information related to that book
also provide editing option about author, price and description. Connecting application with
Good reads and Library things. Application provides loan option for the book owner.

11 | P a g e
 CHEAPTER-3 SYSTEM MANAGEMENT AND PLANNING

3.1 FESIBILITY STUDY:

Is cancellation of project a bad news?

As per IBM report “31%” projects get cancelled before they are
completed. 53% over-runs their cost estimate by an average of 189% & for every 100
projects, there are 94 restarts.

How do we cancel a project with the least work?

CONDUCT A FESIBILITY STUDY

Technical feasibility:

• Is technically feasible to provide direct communication connectivity through space

from one location of globe to another location?

• Is it technically feasible to design a programming language using “Sanskrit”?

Feasibility depends upon non technical issues like:

• Are the project’s costs and schedule assumption realistic?

• Does the business model realistic?
• Is there any market for the product?

Purpose of feasibility study:

• Is the product concept viable?

• Will it be possible to develop a product that matches the project’s vision
statement?
• What are the current estimated cost and schedule for the project?

Focus of feasibility studies:

• Have users & developers been able to agree on a detailed user interface prototype?
If not, are the requirements really stable?
• Is the software development plan complete & adequate to support further
development work?

12 | P a g e
3.2 HARDWARE-SOFTWARE REQUIREMENT:

Android studio 2012

• Android Studio provides the fastest tools for building apps on every type of
Android device.

• World-class code editing, debugging, performance tooling, a flexible build

system, and an instant build/deploy system all allow you to focus on building
unique and high quality apps.

• Android Studio is Android's official IDE. It is purpose built for Android to

accelerate your development and help you build the highest-quality apps for
every Android device.

• It offers tools custom-tailored for Android developers, including rich code

editing, debugging, testing, and profiling tools.

Windows 8

• Windows 8 is a personal computer operating system developed

by Microsoft as part of the Windows NT family of operating systems.

• Windows 8 introduced major changes to the operating system's platform

and user interface to improve its user experience on tablets, where Windows
was now competing with mobile operating systems, including Android
and IOS.

• In particular, these changes included a touch-optimized Windows shell based

on Microsoft's Metro “design language, the Start screen, a new platform for
developing apps with an emphasis on touch screen input, integration with
online services, and Windows Store, an online store for downloading and
purchasing new software.

13 | P a g e
CLIENT SIDE TOOLS:

Processor PC with a Dual core processor or above Recommended

:2.20 GHz processor

RAM 512 MB or onwards Recommended.

Hard Disk 45 MB of available space required on system driver of

available or more.

Operating System Windows or open source 32 bit operating system, or later

versions.

Browser Mozilla Firefox 2.0 /Internet Explorer 8.0

SERVER SIDE TOOLS:

Processor PC with a Dual core processor or above

Recommended: 2.50 GHz processor.

RAM 4 GB or onwards Recommended

Hard Disk 25 GB.

Operating System Windows Service Pack 2, Windows Server 2003 Service

Pack 1, or later versions

Software Mysql, PHP, Apache server or Xammp server.

Browser Mozilla Firefox 2.0 /Internet Explorer 7.0 Onwards with

Player Plug-in 9.0 or onwards.

14 | P a g e
3.3 SYSTEM PLANNING:

Planning is a part of development and design planning your application.

• Pre-planning and research

The first phase is the most important one because it is during this phase
that you lay down the necessary ground work for what is to follow next.
During this step it is very important to do substantial research and
brainstorming before moving to the next phase. You need to do the
homework and have answers to questions like – What is the main aim of this
App? Who is the target audience? Which platform should you target first? Is
the App going to be free or paid?
Once you have the answer to all these questions then you clearly know
that how much time it will take for you to develop the App. Another thing
which is a must in this phase is the analysis of the competition. Do a detailed
study of your competitor’s App to see what features they are offering. Try to
figure out the features which are absent in their App so that you can include it
in your App, to make it stand out.

Once you have all this information then the next thing which you need to
do is to lay down the cost and the time for App development.

• Mental prototyping
Once you are done with the research and have laid down the costs
involved then the next phase involves preparing a detailed scope of work. You
need to do a mental prototyping of your App and draw your ideas in the form of
sketches on a whiteboard. This will be the first visual representation of the ideas
which you collected in Phase 1 and it will help you uncover usability issues.

Another thing which needs to done in this phase is to take the feedback
of relevant people to get a perspective of what they think about your idea.
Discussing it with them will help you figure out the loopholes and allow you to
look for a solution to tackle with them.

• Assessment of technical feasibility

Having an understanding of the visuals is not enough because you need

to analyze whether the back end systems will support the App’s functionality
or not. To understand if the idea of your App is technically feasible you need
to get access to public data by simply sourcing public APIs. You also need to
determine which platform you are building your App for, first. Building an
App shall have different requirements depending upon its platform
(Android/IOS) as well as its format (tablet/Smartphone).

15 | P a g e
 • Building a prototype

You cannot define the touch experience until and unless you actually
touch the App and see how it works and flows. In order for that to happen you must build a
prototype and get the experience of the App into the users hand as soon as possible. This will
help you see if things are going in the right direction. In this phase you can use rough and not
exhaustive wireframes. Including the stakeholders in this process and allowing them to touch
the prototype shall help you take their feedback and implement it into your work.

• Design and development of app

Before moving to coding you must design your App. A User Experience
designer can create the interaction architecture of the design elements while a User Interface
designer can create the look and feel of your App. This in itself is a multi-step process and
the end results is visual directions and blueprints which gives envision of the final product. It
also informs you on how an interaction should feel, move and flow.

• Building the app using agile methodologies

Once the design is ready then it is the time for you to build the App. Agile
methodology is the best approach for mobile application development as it allows you to make
changes, add new features and keep evolving with the changing trends.

• Testing the mobile app

Congratulations on building your Mobile App. For Phase 7 you need to
get some target users to help you test the App.

UAT Testing: For user experience testing you need to put your App in the
hands of the users which you are targeting and once it passes the UAT test you know that the
solution which you are providing actually works.

Beta Testing: Make your App available for the beta trial by allowing open
participation of people to test it. The feedback from these beta users will help you determine
if your App’s functions work well in the real world environment.

• The launch
Once Phase 7 is successful, your App is complete and is ready to be
submitted to the App stores for approval.

However, this is not the end as every App requires regular updates and
new features to be added to it during the mobile application development lifecycle. The
development cycle

16 | P a g e
3.3.1 WORK BREAK-DOWN STRUCTURE

QRDroid Online
Bookstore

1.3 1.4 1.5

1.1 1.2
Administration & Help Donate
MyBook AddBook
Preference

1.3.1 1.4.1 1.5.1

1.1.1 1.2.1
Synchronize with Send Information Amazon WishList
Sort & Style Scan Barcode
Goodreads

1.1.2 1.2.2 1.3.2

1.5.2
Expand All Enter ISBN Manage
Paypal
BookShelves

1.1.3 1.2.3 1.3.3

Collapse All Search Internet Manage
FieldVisibility

1.1.4 1.2.4 1.3.4

Search Books Add Manually BookList
Preference
1.1.5 1.3.5
Manage Book EditBookList
Shelves Preference

1.3.6
Edit BookList Style

1.3.7
Other Preference

1.3.8
Import/Export to
Archive

1.3.9
Import/Export CSV
File

1.3.10
Import/Export
Godreads

1.3.11
Reset Hints

1.3.12
Background Task

17 | P a g e
3.3.2 GANTT CHART

18 | P a g e
3.4 PROCESS MODEL

Project plan

Feasibility

Process model analysis

Product backlog

Work breakdown structure

Requirement
Use cases

SRS

SRS team effort

Design

Architecture

Class diagram

High level design document

Implementation

Coding and User testing

Testing

User acceptance test

19 | P a g e
 CHEAPTER-4 SYSTEM ANALYSIS AND DESIGN

UMLDiagram

20 | P a g e
UML:-
- Unified Modelling Language diagram is designed to let developers and
customers view a software system from a different perspective and in varying
degrees of abstraction.

- One reason UML has become a standard modeling language is that it is

programming-language independent.

- Since UML is not a methodology, it does not require any formal work
products.

21 | P a g e
 Use Case
Diagram

22 | P a g e
Introduction:

-A use case diagram describes how a system interacts with outside actors.

- It is a graphical representation of the interaction among the elements and

system.

- Each use case representation a piece of functionality that a system provides to

its user.

- Use case identifies the functionality of a system.

- Use case diagram allows for the specification of higher level user goals that
the system must carry out.

- These goals are not necessarily to tasks or actions, but can be more general
required functionality of the system.

- You can apply use case to capture the intended behaviour of the system you
are developing, without having to specify how that behaviour is implemented.

- A use case diagram at its simplest is a representation of a user's interaction

with the system and depicting the specifications of a use case.

- A use case diagram contains four components.

I) the boundary, which defines the system of interest in relation to the world
around it.

II) The actors, usually individuals involved with the system defined according
to their roles.

III) The use cases, which the specific roles are played by the actors within and
around the system.

IV) The relationships between and among the actors and the use cases.

23 | P a g e
Purpose:

- The main purpose of the use case diagram is to capture the dynamic aspect of
a system.

- Use case diagram shows, what software is suppose to do from user point of
view.

- It describes the behaviour of system from user’s point.

- It provides functional description of system and its major processes.

- Use case diagram defines the scope of the system you are building.

Use case Diagram Notations

Symbol Reference Name

Actor

Use Case

System

Relationships

24 | P a g e
4. DIAGRAMS

4.1 USE-CASE DIAGRAM

Search Book

Manage Book

Add Book

Update/Edit Book style

Manage Field Visibility

Book List Preference

Synchronize with Goodreads

Synchronize with LibraryThings

Backup to Archive

Import/Export Book

25 | P a g e
 Activity
Diagram

26 | P a g e
Introduction:

- An activity diagram is a type of flow chart with additional support for parallel
behaviour.

- This diagram explains overall flow of control.

- Activity diagram is another important diagram in UML to describe dynamic

aspects of the system.

- Activity diagram is basically a flow chart to represent the flow from one
activity to another activity

- The activity can be described as an operation of the system.

- The control flow is drawn from one operation to another. This flow can be
sequential, branched or concurrent. This distinction is important for a
distributed system.

- Activity diagrams deals with all type of flow control by using different
elements like fork, join etc.

Purpose:

- Contrary to use case diagrams, in activity diagrams it is obvious whether

actors can perform business use cases together or independently from one
another.

- Activity diagrams allow you to think functionally.

27 | P a g e
 Activity Diagram Notations

Symbol Reference Name

Initial state point

State

Fork

Join

Flow

Final state point

28 | P a g e
 Start

Binrization

Ffind Finder pattern Perform Image Matching

Location with QR-Image database

Find QR Image having the

largest similarity coefficient
Sucess the QR Code
detection

Exceed similarity
connection
Decoding

Sucess
Decodind?
Extract the original form Send the detection
matched image error

Send the detection Send the decode QR

error Code information

Check for
availability?

View Scanned Book Scan the ISBN No of

Book

29 | P a g e
 Provide Image &
Description of the Book

30 | P a g e
 Sequence
Diagram

31 | P a g e
Introduction
- Sequence diagrams model the dynamic aspects of a software system.

- The emphasis is on the “sequence” of messages rather than relationship

between objects.

- A sequence diagram maps the flow of logic or flow of control within a usage
scenario into a visual diagram enabling the software architect to both document
and validate the logic during the analysis and design stages.

- Sequence diagrams provide more detail and show the message exchanged
among a set of objects over time.

- Sequence diagrams are good for showing the behaviour sequences seen by
users of a diagram shows only the sequence of messages not their exact timing.

- Sequence diagrams can show concurrent signals.

Purpose
- The main purpose of this diagram is to represent how different business
objects interact.

- A sequence diagram shows object interactions arranged in time sequence.

- It depicts the objects and classes involved in the scenario and the sequence of
messages exchanged between the objects needed to carry out the functionality
of the scenario.

32 | P a g e
Sequence Diagram Notations

Symbol Reference Name

Activation

Objective Lifeline

Message

33 | P a g e
 User Application Database

Search Book Search from Database

Respond search Resopond to application

Save Book Save to Database

Save to Database

Update Book Update in Database

Respond to Update Update Application

Save Archive File Save to Database

Show file to User Import from Database

Manage Bookshelf

Collection of Book

Manage Field Visibility

Sorted List

Set Preferences

Respond to Preference

Share Book Search from Database

Respond to User Respond to Application

Share book to Goodread Save file to Database

View Book in Goodread Respond to Application

Import From Goodread Search in Database

View Book in Application Respond to Application

34 | P a g e
Class Diagram

35 | P a g e
Introduction
- The class diagram is a static diagram.

- A class model captures the static structure of a system by characterizing the

objects in the system, the relationship between the objects, and the attributes
and operations for each class of objects.

- The class diagram can be mapped directly with object oriented languages.

- The class model is the most important among the three models.

- Class diagram provide a graphical notation for modeling classes and their
relationship.

- They are concise, easy to understand, and work well in practice.

- Class diagrams are the backbone of almost every object-oriented method

including UML.

- They describe the static structure of a system.

Purpose
- Analysis and design of the static view of an application.

- Describe responsibilities of a system.

- Base for component and deployment diagrams

36 | P a g e
 Author

Name
Book Published Book
ISBN String
Add()
Name String
Update()
Subject String
Delete()
Overview String
Publisher String 0*
PublicationDate Date
0* Wrote
Language String
Image Blob
Title String
Author String

Search

Use
0* User

Name
Catalogue
Emailid

Add()
0* Update()
Use Delete()
Manage 1.1
Makes

0*
Loan
BookOnShelf
Checkout dateTimeOut
copyNumber
0* ScannedId
1.1
dateDue
1.* dateReturned

Catalogue

Title
1.1 Represents
PublishDate
Publiaher
ISBN

37 | P a g e
 System
Flow

38 | P a g e
39 | P a g e
 Data
Dictionary

40 | P a g e
 BOOK-DETAILS

Fields Data type size Constraint Description

Id Integer 10 Auto To store user ID

Increment
ISBN Integer 15 Not null Book ISBN No

Name Varchar 20 Not null Name of Book

Subject String 20 Not null Subject of Book

Overview String 50 Not null Description of

Book
Publisher String 20 Not null Publisher name

Published Date Date 10 Not null Publish date

Image Long Binary Not null Image of Book

Title String 20 Not null Title of Book

Author String 20 Not null Author of Book

LOAN-DETAILS

Fields Data type Size Constraint Description

Cust_name String 15 Not null Name of Customer

Phone_No Integer 10 Not null Phone No of Cust

Scanner_ID Integer 12 Not null ID of Book

41 | P a g e
 Date due Date 10 Not null Date of Book Given

Date Returned Date 10 Not null Date of Book

returned

42 | P a g e
Input-Output
Design
(Screen Shots)

43 | P a g e
44 | P a g e
45 | P a g e
46 | P a g e
47 | P a g e
48 | P a g e
49 | P a g e
50 | P a g e
51 | P a g e
52 | P a g e
53 | P a g e
54 | P a g e
55 | P a g e
56 | P a g e
57 | P a g e
58 | P a g e
59 | P a g e
60 | P a g e
61 | P a g e
62 | P a g e
63 | P a g e
64 | P a g e
65 | P a g e
66 | P a g e
67 | P a g e
68 | P a g e
69 | P a g e
70 | P a g e
71 | P a g e
72 | P a g e
73 | P a g e
74 | P a g e
75 | P a g e
Conclusion
(Future
Scope,
Limitations)
76 | P a g e
Future Scope:
• Authentication with Good Reads.

• More option regarding Loan option

• Import/Export in Library Things.

• Bill Generation of Book purchase.

77 | P a g e
 Conclusion

78 | P a g e
Any Work may not always be perfect

There may be some defects or errors. We have taken enough care to make the

project user friendly and more interactive. Major focus is to generate paper

dynamically without leaking of paper.

Any suggestion to make this project more useful is Always

most welcome.

79 | P a g e
 Th a n k Y o u

80 | P a g e
 Bibliography

81 | P a g e
During this whole Application development we referred books and Web-sites.

The books and Web-site are referred as below:

BOOKS:-

• Professional Android 4 Application Development by Reto Meier

• Android Application Development For Dummies by Donn Felker

WEB-SITE:-

• http://android-developers.blogspot.in/

• http://android-pro.blogspot.in/

• http://www.androidhive.info

• https://developer.android.com/design/index.html

82 | P a g e
83 | P a g e
84 | P a g e
85 | P a g e
86 | P a g e