A PROJECT REPORT ON

TECHNICAL COMPARISON & PRACTICAL

IMPLEMENTATION OF VARIOUS LEADING
CRYPTOCURRENCY IN DIGITAL & COMMERCIAL CODE
Submitted by

Tatva Shah (141260107047)

Rudraksh Jani (141260107011)

Guided by

Asst. Prof. Kaushal Jani

Dr. Bankim Jani (Creative Solution International)

In fulfillment for the award of the degree

Of

BACHELOR OF ENGINEERING
In

COMPUTER ENGINEERING

2017-18

SAL ENGINEERING AND TECHNICAL INSTITUTE

Opp. Science City, Bhadaj Road, Ahmedabad

GUJARAT TECHNOLOGICAL INSTITUTE, AHMEDABAD

 TABLE OF CONTENTS
Acknowledgement I
College Certificate II
GTU PMMS Completion Certificate V
IDP Completion Certificate VIII
Abstract IX
Plagiarism Certificate XIII

Chapter : 1 Introduction 1
1.1 Introduction 2
1.2 Project Summary 2
1.3 Scope 2
1.4 Features 2
1.5 Technology Specification 3

Chapter : 2 Project Management 4

2.1 Project Planning 6
2.1.1 Project Development Approach and 6
Justification
2.1.2 Boehm’s Spiral Model 7
2.1.3 Project Plan 8
2.1.4 Milestone & Deliverables 9
2.1.5 Roles and Responsibility 11
2.2 Risk Management 11
2.2.1 Risk Identification 12
2.2.2 Risk Analysis 13
2.2.3 Risk Planning 14

Chapter : 3 System Requirement 15

3.1 User Characteristics 16
3.2 Client Side Requirements 17
3.3 Developer Side Requirements 18
3.4 Constraints 18
3.5 Assumption and Dependencies 18

Chapter : 4 System Analysis 20

4.1 Data Modeling 21
4.7.1 Class Diagram 22
4.2 Functional and Behavioral Modeling 25
4.8.1 Data Flow Diagram 27
4.8.2 Sequence Diagram 28
Chapter : 5 Input and Output Design 30
6.1 Home 30
6.2 Admin Layout 31
6.3 User Layout 32

Chapter : 6 Conclusion 33
References 33

Appendix : 1 Periodic Project Report 34

Appendix : 2 Business Model Canvas 39
Appendix : 3 Design Engineering Canvas 41
 Acknowledgement

We wish to express our sincere gratefulness to every one of the individuals who have
added to this extend, both unequivocally and verifiably, without the co-operation of
whom, it would not have been conceivable to finish this venture.

We would like to thank our H.O.D Dr. Kinjal Adhvaryu and Asst.Prof.Kaushal Jani
(Internal Guide) for continually directing and demonstrating to us the right way to reach
towards our favored objective. Additionally I express gratitude toward them for sharing
their experience, information and valuable time with me and demonstrating their worry
in my task to improve it.

I also thank all the other faculties who directly or indirectly supported me in making my
project successful by sharing their ideas and knowledge. Finally, I might want to thank
our folks and companions who have specifically or in a roundabout way helped us in
influencing the undertaking to work effective.

TATVA SHAH

RUDRAKSH JANI
 CERTIFICATE
Date:

This is to certify that the Project entitled “ TECHNICAL COMPARISON &

PRACTICAL IMPLEMENTATION OF VARIOUS LEADING
CRYPTOCURRENCY IN DIGITAL & COMMERCIAL CODE ” has been
carried out by TATVA SHAH under my guidance in fulfillment of the degree of
Bachelor of Engineering in COMPUTER ENGINEERING (8th Semester) of
Gujarat Technological University, Ahmedabad during the academic year 2017-
18.

Internal Guide:

Mr. Kaushal Jani

Assistant Professor of CE Department

Dr. Kinjal Adhvaryu

Head of Department

Department Of Computer Engg.

Sal Engineering and Technical Institute,

 Ahmedabad

CERTIFICATE
Date:

This is to certify that the Project entitled “ TECHNICAL COMPARISON &

PRACTICAL IMPLEMENTATION OF VARIOUS LEADING
CRYPTOCURRENCY IN DIGITAL & COMMERCIAL CODE ” has been
carried out by RUDRAKSH JANI under my guidance in fulfillment of the
degree of Bachelor of Engineering in COMPUTER ENGINEERING (8th
Semester) of Gujarat Technological University, Ahmedabad during the
academic year 2017-18.

Internal Guide:

Mr. Kaushal Jani

Assistant Professor of CE Department

Dr. Kinjal Adhvaryu

Head of Department

Department Of Computer Engg.

Sal Engineering and Technical Institute,

Ahmedabad
 Abstract
We are creating an application for displaying concept & algorithms of crypto
currencies, including changes in values & cost, advantages, disadvantages and
financial future of Cryptocurrency. Further there would be a better amount
efficient cloud security and distributed storage. This would even predict the value
of the virtual currency of upcoming Months and Years. Cryptocurrency is the
future for transferring money in an efficient manner and with the use of Block
Chain technology there won’t be any kind of fake money or duplicating the
currency which has already been used somewhere else. There have been a lot of
misconceptions about these virtual crypto currency and people are afraid to use it
while the Bitcoin was not even of 1 rupee and now it’s almost at 3 lakh rupees,
People invest in the market of Crypto currency. The implementation of virtual
currency and discuss about its daily basis application to military exchange of arms
and ammunition.

SETI (CE) Page VIII

 Plagiarism Certificate

SETI (CE) Page IX

 CHAPTER – 1
INTRODUCTION

SETI (CE) Page 10

1.1 Introduction
Virtual Currency is one of the most emerging topic around the world, Virtual currency is
basically used to exchange a commodity, It is extremely better than FIAT currency and
this gives an opportunity to even invest in the world of crypto currency.

These currencies do not have a fix value so there has to be a real time record and
updating the whole chart which would be compared amongst the leading crypto
currencies all over the world,

Virtual currency can be well-defined as a digital illustration of value that is issued and
controlled by its developers, and used and accepted among the members of a definite
(virtual) communal. Unlike FIAT currency, it depends on a system of conviction and not
issued by a central bank or other banking authority also these decentralized currencies
don’t even have a sever in the middle, this whole process works on PEER-PEER
connection which is quite risky and safe both at a same time.

1.2 Project Summary

This system creates awareness for those who don’t know about these virtual currencies
this would start making a change from level 0. For those who already are working on
these VC for them the system would manage the watch list and keep giving real time
updates about the interested VC.

For every individual these would make an initiative and for the miners and members of
the VC community, comparison, News and different valuation and prediction will be give
by the system.

1.3 Scope
The user interacts with the application designed by the system which would be showing
the leading crypto currency chart and real time updates of every currency. This process is
the basic process makes things look and feel good while the user is watching the charts
and predictions given by the algorithm based on old records of the market.

1.4 Features
The primary aim through this application is public awareness. People should have
information about CryptoMarket.

Rate details: Application is dynamic. So it fetches data from the CryptoMarket through
API and displays it to the user.

Currency Exchange: The Application also shows the exchange rates. For
example, exchance rate of Bitcoin with Ether.

SETI (CE) Page 11

Following are some other features of the project are like these -
• Easy to use
• Secure
• Accurate
• Reliable
• User friendly

1.5 Technology Specification

Programming Language JAVA, Android

Front End JAVA, CSS, JavaScript, HTML

Back End Blockchain, JAVA, MySQL Server

(Database Server)

Operating System Android

Supported By Kitkat, or above

Tools Android Studio

Table 1.5: Technology specification

SETI (CE) Page 12

 CHAPTER – 2
PROJECT MANAGEMENT

SETI (CE) Page 13

Project Management:

Project management is the application of knowledge, skills, tools, and techniques to

project activities to meet project requirements. Managing projects is not the same as
managing ongoing operations. This work that is unique and temporary requires different
management disciplines.

The term “project management” is sometimes used to describe an organizational

approach to the management of ongoing operations. This approach treats many aspects of
ongoing operations as projects to apply project management techniques to them. A
detailed discussion of the approach itself is outside the scope of this document.

Project management is accomplished through the use of the following 5 processes:

 Initiation

 Planning

 Execution

 Controlling

 Closure

The Managerial Process, 4th edition is distinguished by its balanced treatment of both the
technical and behavioral issues in project management as well as by its coverage of a
broad range of industries to which project management principles can be applied. It
focuses on how project management is integral to the organization as a whole. The 4th
edition reflects the latest changes found in the practice.

Advantages of proper project management:

 Planning provides the framework for decision making

 Planning reduces crisis management

 Planning provides for streamlined communications

 Planning allows you to set priorities

 Planning helps you eliminate fear of failure

SETI (CE) Page 14

2.1 Project Planning
The core of PLM (product lifecycle management) is in the creations and central
management of all product data and the technology used to across this information and
knowledge. PLM as a discipline emerged from tools such as CAD, CAM and PDM, but
can be viewed as the integration of these tools with methods, people and the processes
through all stages of a product’s life. It is not just about software technology but is also a
business strategy.

Project planning is part of project management, which relates to the use of schedules such
as Gantt charts to plan and subsequently report progress within the project environment.
Initially, the project scope is defined and the appropriate methods for completing the
project are determined. Following this step, the durations for the various tasks necessary
to complete the work are listed and grouped into a work breakdown structure.

The logical dependencies between tasks are defined using an activity network diagram
that enables identification of the critical path. Float or slack time in the schedule can be
calculated using project management software. Then the necessary resources can be
estimated and costs for each activity can be allocated to each resource, giving the total
project cost. At this stage, the project schedule may be optimized to achieve the
appropriate balance between resource usage and project duration to comply with the
project objectives.

Once established and agreed, the project schedule becomes what is known as the baseline
schedule. Progress will be measured against the baseline schedule throughout the life of
the project. Analyzing progress compared to the baseline schedule is known as earned
value management.

The inputs of the project planning phase include the project charter and the concept
proposal. The outputs of the project planning phase include the project requirements, the
project schedule, and the project management plan.

2.1.1 Project Development Approach & Justification

 There are two types of "Project Development Approach". They are like these -

1) PROJECT ADMINISTRATION

Focuses on finding solutions within given constraints (output, time, and budget);
characterized by an early design freeze that creates a stable target for the project;

SETI (CE) Page 15

effective when duration of the project - or the time required to innovate - is shorter than
the rate of change in the business environment.

2) BUSINESS SYNERGIES

Focuses on adding value to the organization and maximizing return on investment; does
not lock down design earlier than absolutely necessary not to miss a newly emerging
opportunity; effective for managing innovation projects in the rapidly changing business
environment.

Software process model are complex and involves very large number of activities. It
defines set of activities and associated results that produce a software process.

To manage all aspects of the application, I have to divide the whole management process
in different small modules and think the designing of it. This is best done with the model
- "Boehm’s Spiral Model".

2.1.2 Boehm’s Spiral Model

Fig 2.2.1: Boehm’s Spiral Model

SETI (CE) Page 16

Each loop in the spiral is split into four sectors:

• Objective Setting:
Specific objectives for that phase of the project are defined. Constraints on the process
and the product are identified and a detailed management plan is drawn up. Project risks
are identified. Alternative strategies, depending on these risks, may be planned.

• Risk Assessment and Reduction:

For each of the identified project risks, a detailed analysis is carried out. Steps are taken
to reduce the risk. For example, if there is a risk that the requirements are inappropriate, a
prototype system may be developed.

• Development and Validation:

After risk evaluation, a development model for the system is then chosen. For example, if
user interface risks are dominant, an appropriate development model might be
evolutionary prototyping.

If safety risks are the main consideration, development based on formal transformations
may be the most appropriate and so on. The waterfall model may be the most appropriate
development model if the main identified risk is sub-system integration.

• Planning:
The project is reviewed and a decision made whether to continue with a further loop of
the spiral. If it is decided to continue, plans are drawn up for the next phase of the project.

2.1.3 Project Plan

A Project Plan is: "...a formal, approved document used to guide both Project Execution
and Project Control. The primary uses of the project plan are to document planning
assumptions and decisions, facilitate communication among stakeholders and document
approved scope, cost, and schedule baselines.

SETI (CE) Page 17

A project plan may be summarized or detailed Project plan. The project plan must also
describe the execution, management and control of the project. This information can be
provided by referencing other documents that will be produced, such as a Procurement
Plan or Construction Plan, or it may be detailed in the project plan itself.

Project Plan (PP) is the process of creating development goals and objectives and using
these goals and objectives to improve productivity as well as development capabilities.
The purpose of this process is generally to ensure that each project will accomplish its
development goals and objectives. Projects can be differentiated into five types of
projects: breakthrough, platform, derivative, R&D, or partnered projects. This
differentiation determines a project's development goals and objectives as well as
resources allocated to that project.

An aggregate project plan provides management with a categorized list of projects, which
balances short and long term goals. This list assists management in making difficult
decisions such as when to start projects and which projects should be cannibalized.
Starting projects in a sequential manner according to the firm's strategy as well as
resources available will allow fewer projects to continue simultaneously and improve
productivity.

A project plan, according to the Project Management Body of Knowledge, is: "...a
formal, approved document used to guide both project execution and project control. The
primary uses of the project plan are to document planning assumptions and decisions,
facilitate communication among stakeholders, and document approved scope, cost, and
schedule baselines. A project plan may be summarized or detailed.

2.1.4 Milestone & Deliverables

MILESTONE :

Every task or group of tasks should be associated with project milestone. A milestone is
accomplished when one or more work products has been reviewed for quality and has
been approved. Project Milestones include completion of some defines tasks in defined
time limits.

The milestones associated with this project are shown below:

Study for Project:

First milestone includes study of project related coding languages and their techniques
and tools.

SETI (CE) Page 18

Project Planning & Scheduling:

Second milestone includes analysis of project and designing. Then we have started
coding to develop first prototype which includes homepage and some simple pages like
login, register etc. pages.

Development of Various Modules:

Third milestone includes developing services, Cryptocurrency details, Price

Comparison(Dynamically)as well as Exchange rates. Also these modules are debugged
and tested.

Fourth milestone includes developing framework to a complete application. This module

is again tested and reviewed.

Testing & Documentation:

Fifth milestone includes the integration testing and documentation.

2.2 Risk Management

Risk management is a series of steps whose objectives are to identify, address, and
eliminate software risk items before they become either threats to successful software
operation or a major source of expensive rework. The proactive management of risks
throughout the software development lifecycle is important for project success.

The risk management practice, which involves risk identification, analysis, prioritization,
planning, mitigation, monitoring, and communication Software development risks that
seem to reoccur in educational and industrial Projects risk-driven process for selecting a
software development model.

Risk in itself is not bad; risk is essential to progress, and failure is often a key part of
learning. But we must learn to balance the possible negative consequences of risk against
the potential benefits of its associated opportunity. A risk is a potential future harm that
may arise from some present action such as, a schedule slip or a cost overrun. The loss is
often considered in terms of direct financial loss, but also can be a loss in terms of
credibility, future business, and loss of property or life.

SETI (CE) Page 19

 Fig 2.3: Risk Management Cycle

2.2.1 Risk Identification

In the risk identification step, the team systematically enumerates as many project risks as
possible to make them explicit before they become problems. There are several ways to
look at the kinds of software project risks.

It is helpful to understand the different types of risk so that a team can explore the
possibilities of each of them. Each of these types of risk is described below.

• BUSINESS RISKS
Business risks are those that threaten the viability of the software, such as building an
excellent product no one wants or building a product that no longer fits into the overall
business strategy of the company.

There are some specific factors to consider when examining project, product, and
business risks. Some examples of these factors are listed here, although this list is meant
to stimulate you thinking rather than to be an all-inclusive list.

People risks are associated with the availability, skill level, and retention of the people on
the development team. Size risks are associated with the magnitude of the product and
the product team. Larger products are generally more complex with more interactions.
Larger teams are harder to coordinate.

The risk identification process should stop short of assessing or analyzing risks so that it
does not inhibit the identification of "minor" risks. The process should promote creative
thinking and leverage team experience and knowledge.

2.2.2 Risk Analysis

Project risk analysis is concerned with the assessment of the risks and uncertainties that
threaten a project. Project risk analysis has a broad range of applications, just as the

SETI (CE) Page 20

definition of a project is broad. Project is any set of inter-related tasks designed to
achieve a certain goal or set of goals, with a limited set of resources, to a particular
quality standard and within a particular budget and time frame.

• COST RISK ANALYSIS

Cost Risk Analysis consists of looking at the various costs associated with a project, their
uncertainties and any risks or opportunities that may affect these costs. Risks and
opportunities are defined as discrete possible events that will increase and decrease the
project costs respectively.

They are both characterized by estimates of their probability of occurrence and the
magnitude of their impact. The distributions of cost are then added up in a risk analysis to
determine the uncertainty in the total cost of the project.

• SCHEDULE RISK ANALYSIS

Schedule risk analysis looks at the time required to complete the various tasks associated
with a project, and the interrelationship between these tasks.

Risks and opportunities are identified for each task and an analysis is performed to
determine the total duration of the project and, usually, the durations until specific
milestones within the project are achieved.

A schedule risk analysis is generally more complex to perform than a cost risk analysis
because the logical connections between the tasks have to be modeled in order to
determine the critical path.

2.2.3 Risk Planning

Risk planning involves the thoughtful development, implementation, and monitoring of
appropriate risk response strategies. Risk Management Plan is a critical step in any
project, as it helps you to reduce the likelihood of risk from occurring.

The Engineering and Construction Management defines risk planning as the detailed
formulation of a plan of action for the management of risk. Risk planning is iterative and
includes describing and scheduling the activities and processes to assess, mitigate,
monitor, and document the risk associated with a project. Large projects or projects with
a high degree of uncertainty, the result should be a formal risk management plan.

Risk plan should be documented, but the level of detail will vary with the unique
attributes of each project. Risk management plans that record all aspects of risk.

SETI (CE) Page 21

 CHAPTER – 3
SYSTEM REQUIREMENT

SETI (CE) Page 22

The study is to assist the management in evolving right strategies in implementation of a
proper system for an activity. A thorough study and gap analysis with the best of
practices ensures the right design of system. A System Requirements Study is a
structured collection of information that embodies the requirements of a system.

A System Requirements Study (SRS) is a document or set of documentation that

describes the features and behavior of a system or software application. It includes a
variety of elements (see below) that attempts to define the intended functionality required
by the customer to satisfy their different users. In addition to specifying how the system
should behave, the specification also defines at a high-level the main business processes
that will be supported, what simplifying assumptions have been made and what key
performance parameters will need to be met by the system.

In cases of going in for standard 'off the shelf' system solutions, quite often, the business
processes of an enterprise and those imbibed in ready-made product, differ widely. While
the 'off the shelf' packages ensure standardization and incorporation of the best, a blind
adoption of the same results in unmanageable change management issues which makes
the project unsuccessful. On the other hand, too much of customization defeats the very
purpose of going for a standard product apart from project cost escalations. Requirements
analysis is critical to the success of a systems or software project. The requirements
should be documented, actionable, measurable, testable, traceable, related to identified
business needs or opportunities, and defined to a level of detail sufficient for system.

Requirements analysis in systems engineering and software engineering, encompasses

those tasks that go into determining the needs or conditions to meet for a new or altered
product, taking account of the possibly conflicting requirements of the various
stakeholders, analysing, documenting, validating and managing software or system
requirements..

3.1 User Characteristics

The application operators are being categorized into three main categories:

• Registered users
• Admin

SETI (CE) Page 23

Registered users:

• Can log in
• Enter CryptoMarket
• View different categories of Cryptocurrency
• View Rates of different websites
• Know the exchange rates
• Get the basic Information
• logout

Admin:

• Can Log in
• Maintain database
• Search API’s
• View Details
• Logout

SETI (CE) Page 24

 CHAPTER – 4
SYSTEM ANALYSIS

SETI (CE) Page 25

4.7 Data Modeling
Data modeling is the formalization and documentation of existing processes and events
that occur during application software design and development. Data modeling
techniques and tools capture and translate complex system designs into easily understood
representations of the data flows and processes, creating a blueprint for construction
and/or re-engineering.

A data model can be thought of as a diagram or flowchart that illustrates the relationships
between data. Although capturing all the possible relationships in a data model can be
very time-intensive, it's an important step and shouldn't be rushed. Well-documented
models allow stake-holders to identify errors and make changes before any programming
code has been written.

Data modelers often use multiple models to view the same data and ensure that all
processes, entities, relationships and data flows have been identified. There are several
different approaches to data modeling, including:

Conceptual Data Modeling:

Identifies the highest-level relationships between different entities.

Enterprise Data Modeling:

Similar to conceptual data modeling, but addresses the unique requirements of a specific
business.

Logical Data Modeling:

Illustrates the specific entities, attributes and relationships involved in a business

function. Serves as the basis for the creation of the physical data model.

Physical Data Modeling:

Represents an application and database-specific implementation of a logical data model.

Representation of a real world situation about which data is to be collected and stored in a
database. A data model depicts the dataflow and logical interrelationships among
different data elements.

SETI (CE) Page 26

4.7.1 Class Diagram

Fig 4.7.1: Class Diagram

SETI (CE) Page 27

4.8 Functional and Behavioral Modeling

4.8.1 Sequence Diagram

Admin:

Fig 4.8.2.1: Admin Sequence Diagram

4.8.3 ER Diagram

SETI (CE) Page 28

SETI (CE) Page 29
 CHAPTER – 5
INPUT& OUTPUT DESIGN

5.1 Home page:

SETI (CE) Page 30

 Fig 5.1: Home page

5.2 User Layout:

Fig 5.2: Multiple CryptoCurrency

SETI (CE) Page 31

 Fig 5.3 Different Website Rates

SETI (CE) Page 32

 CONCLUSION

 To conclude, the entire details and specifications about the

concepts,theories,practical implementation and the technologies used
behind activities related to cryptocurrency is explained thoroughly.

 The application leads people towards a better perspective and

understanding of cryptocurrencies. The application gives wide details
about the cryptocurrencies, makes transactions reliable,easy and
secured.

 Virtual Currency is the new gold which is lighter in weight but more
profitable cause this new gold basically gives high returns. This
currency is again not centralized and therefore the currency does not
gets banned or something as the currency is not controlled by the bank
or federal authorities.

REFERENCES

[1] Market Analysis:- coinmarketcap.com

[2] Source Of Cryptocurrency:-

en.wikipedia.org/wiki/Cryptocurrency

SETI (CE) Page 33

[3] Application development:- Android Studio.

SETI (CE) Page 34