Report Without Index

PROJECT-II T.R.O.J.4.N.
– Our Own Cryptocurrency
CHAPTER-1
INTRODUCTION
1.1 Introduction
Digital forms of money seek to be another type of cash and guarantee to keep up trust in the
soundness of their incentive using innovation. Blockchain, the innovation behind the Bitcoin
cryptographic money framework, offers a solid exchange of advanced information over the
system without the obstruction of any outsider element.
Bitcoin is the most prevalent model that is naturally attached to blockchain innovation. It is
likewise the most disputable one since it empowers a multibillion-dollar worldwide market of
unknown exchanges with no legislative control.
T.R.O.J.4.N will be another type of Cryptocurrency that will be made utilizing blockchain
innovation. A straightforward UI to deal with the cash will likewise be created.
1.2 Purpose
Cryptocurrency works on the theory of solving encryption algorithms to create unique hashes
that are finite in number. Combined with a network of computers verifying transactions, users
are able to exchange hashes as if exchanging physical currency.
T.R.0.J.4.N - Our Own Cryptocurrency will be created with the traditional methods using new
age concepts like blockchain and with the base language as python. The basic purpose of this
project is to gain in depth knowledge of Blockchain, Python.
The user interface can be easily operated by naive users. The building of UI will technologies
like HTML, CSS and JS. Since the blockchain will be on built on python, Flask will be used
to integrate designing with blockchain.
SAFFRONY INSTITUTE OF TECHNOLOGY Page 1

PROJECT-II T.R.O.J.4.N. – Our Own Cryptocurrency
1.3 Scope
 Reducing the burden of paperwork & counterfeit fake identities.
 Transparency and automation within the patient-to-hospital or patient-to-doctor
transactions.
 Streamline installments handling with high productivity, quick and secure exchanges.
 Forging the control of votes amid decisions.
 Purchase or pitch things without paying any commission to outsiders.
 The ability of IoT applications to contribute transactional data to blockchains.
 Expanded security with a move from brought together information security to a
decentralized system.
 Battle hacking with the changelessness of record.
1.4 Technology and Literature Review

 Our project is completely based on Blockchain, Networking, and Transaction
Processing.
 Coding will be done in python 3.7.
 Tools used are JetBrains PyCharm, Jupyter Notebook(optional), Anaconda.
 Libraries used are hashlib, datetime, pycryptodome and Flask packages.
 We will follow prototype model for this project.
Blockchain
 Blockchain goes about as a conveyed open record. It is a computerized record of

exchanges and proprietorship, that is recreated among the majority of the members of
a shared system.
 An agreement calculation guarantees that every hub possesses a similar duplicate of
the record as different hubs.
 Actually, it is a back-connected arranged rundown of squares, where each square
contains exchanges.
 Each time a transaction is made, it is broadcasted to the network.

 On the off chance that it is substantial, it gets added to a square. At the point when new
square is distributed to the system, all members (hubs) will run calculation to approve
the square.
 Majority of the nodes have to agree that the new block is valid and if so, it will be added
to the blockchain.
 When a square of information is recorded on the blockchain record, information turns
out to be progressively secure as the blockchain develops.
 There are two main types of blockchains: public and private. Bitcoin has a public ledger
i.e. a public blockchain, where anyone is allowed to contribute.
 There is no need for a third authority to grant permissions. Private blockchain is a
network where all the participants are known and trusted and the consensus process is
managed by a pre-selected set of participants.
 In our examination we consider both open and private blockchains along the
accompanying properties: –
 Platforms - we are considering implementations of the blockchain technology
that introduce different approaches to privacy and smart contracts.
 Actors - we need to know who the performing artists are and what jobs they
play in the given blockchain innovation.
 Services - what administrations are given by the blockchain stage? Who
cooperates with the administrations (business level)?
 Processes - what are the underlying processes to services? How do network,
transaction and mining/consensus processes work?
 Data models - what are the elements that hold data? What are the connections
between them?

1.5 Prior Art Search

1.5.1 Method and system for processing of a blockchain transaction in a
transaction processing network.
Inventors: Dennis M. Kennedy
Application no: US20170132626A1
Publication Date: 2015-11-05
Summary:
A method for validating blockchain transactions using a transaction processing network

includes: storing one or more authentication rules configured to authenticate an electronic
transaction and one or more verification rules configured to verify a blockchain transaction;
receiving a transaction message including a message type indicator ad a plurality of data
elements including at least first data elements configured to store blockchain data and
additional data elements configured to store transaction data values; identifying an
authentication score based on application of at least one or more authentication rules to the
transaction data values; identifying a verification score based on application of one or more
verification rules to the blockchain data; generating a data message, the data message
including the blockchain data stored in the first data elements, the identified authentication
score, and the identified verification score; and electronically transmitting the generated data
message to a blockchain network.[1]

1.5.2 Blockchain-based identity and transaction platform
Inventors: Ashish Gadnis, Jeffrey A. Keiser, Michael Linton, Stanislav Natalenko
Summary:
Systems, methods, and computer media implementing blockchain-based identity and

transaction platforms are described herein. Identity information, such as a photo, for a person
can be encrypted and stored in a blockchain as part of enrolling the person as a user in a
blockchain-based identity and transaction platform. Trust relationships can be formed
between the user and other users, and records of the trust relationships can also be stored in
the blockchain. Transactions between the user and other users with whom the user has
formed a trust relationship can also be stored in the blockchain. The transactions can be
authorized, for example, through a multi-stage verification process that accesses information
stored on the blockchain. The transactions and identity information, along with other
information, contribute to an economic identity of the person. [2]

1.5.3 Systems and methods of blockchain transaction recordation
Inventors: Thomas Fay, Dominick Paniscotti
Application no: CA2981511C
Summary:
A computer system is provided that communicates with a distributed blockchain computing

system that includes multiple computing nodes. The exchange stores an order book and a
plurality of digital wallets associated with different clients. The computer system receives
new data transaction requests that are added to the order book. A match is identified between
data transaction requests and hashes associated with the digital wallets associated with the
respective data transaction requests are generated. The counterparties receive the hashes of
the other party along with information on the match and each party causes blockchain
transactions to be added to the blockchain of the blockchain computing system. The
computing system then monitors the blockchain to determine if both sides of the match has
been added to the blockchain. [3]

1.5.4 Use of Blockchain Based Distributed Consensus Control
Inventors: Lawrence Orsini, Yun Wei,Joseph Lubin
Summary:
Devices comprising, connected to or remotely operating an electric electrically powered

network may operate as a node in the network of devices which functions to
cryptographically-secure the operation of the network. The use of autonomous, self-
executing contracts may be hosted on the network may operate devices on the network while
simultaneously transacting the benefits, costs or value created by the device's operation
between nodes of the network. The results of autonomous, self-executing contracts may be
recorded on an immutable, append-only, public ledger which maintains a database of all
transactions that have taken place on the network. This database may be hosted on the
distributed network of devices. This ledger and database may be autonomous and
independent of control by any single node of the network. The network may ensure the
cryptographically secure, decentralized, autonomous and independent function of the public
ledger and self-executing contracts are maintained independent of the individual nodes that
make up the network. Access to the network is provided for the creation or execution of
autonomous, self-executing contracts which control the devices or transactions of claim. The
many different benefits, costs or value created by the system or network may be combined to
create a token that is representation of the many potential attributes of the benefits, costs or
value transacted on the network. This token is a representation of any form of value that
might be assigned by the participants of the network who may wish to transact the
characteristics of the devices. [4]

CHAPTER-2
SOFTWARE PROJECT MANAGEMENT
2.1 PROJECT PLANNING AND SCHEDULING
2.1.1 Project Plan

 Project planning is a piece of undertaking the executives, which identifies with the
utilization of timetables, for example, Gantt outlines to design and in this manner
report advance inside the task condition.
 Our cryptocurrency can be used for various types of transactions.
 It can be useful in banks.
 It can be useful in online transactions.
 Since it is just a prototype, we are planning for an advanced version, which is, a fully
functional UI for handling the cryptocurrency. It can be used for managing the
transactions, creation of the currency, etc.
2.1.2 Schedule Representation
Fig 2.1.2: Schedule Representation

2.2 Risk Management
2.2.1 Risk Identification

 We have used various kinds of libraries, the problem with these libraries are that they
get updated on monthly basis or sometimes even on weekly basis.
 In those updates, sometimes the names of different methods get changed which could
lead to system failure in many terms.
 So, we have to keep ourselves acquainted with those changes, so we can keep up with
some current world scenarios, technically speaking.
 Some libraries are compatible with only python 2.4 and some may only work with
python 3.6,so we have to keep that in mind as well.
 We are making a cryptocurrency, so there will be a problem of securing the
transactions.
 We have to make our transactions secure for the user.
2.2.2 Risk Analysis

 As said, if we can’t keep the methods and functions updated of respective libraries,
then it could lead to some serious failure.
 A single function can annihilate the whole system.
 A method of a function can also annihilates the whole system.
 It is so because every line of code is somehow dependent to previous line of code.
 It could all become very messy and time consuming.
 If these things are not identified as soon as possible they can lead to system failure
 If the transactions are not secured, there can be currency theft.

2.2.3 Risk Planning

 We have to keep the system, libraries, packages all updated.
 We have to keep ourselves aware with updates of various libraries.
 Reading the documentation of respective libraries on a weekly basis can be helpful.
 If there is any update in those libraries then update the code as well.
 We have to keep the editor of corresponding language updated as well.
 At last, try to avoid conflict with previous version of libraries if you are installing the
libraries from a .whl (Wheel) file.

CHAPTER-3
SYSTEM REQUIREMENT STUDY
3.1 USER CHARACTERISTICS

 It describes the type of user, which deals with the applications. Basically, this
application has two types of users as given below:
1. Programmer
2. End User
1. Programmer
Programmer is a person who created the whole system by using some tools like editors
to keep everything in motion.
2. End User
End user is the person who uses the resultant software for their desired purpose. They
don’t know anything about the coding or how the program is made. Their scope is only
to use the software.
3.2 HARDWARE AND SOFTWARE REQUIREMENT
3.2.1 Hardware Requirements:

PC Computers with minimum capacity :
Processor 2 GHz processor
RAM 4GB
Disk 60GB
GPU 2GB
Operating System Windows 7 ultimate 64-bit or higher
Table 3.2.1: Hardware Requirements

3.2.2 Software Requirements:

Python compatible system
Web Browser (Mozilla Firefox or Google Chrome)
Table 3.2.2: Software Requirements
3.3 CONSTRAINTS
1. Time Constraints:
 There exist strict deadlines for each phase of the process, so the
constraint of meeting the deadlines is of utmost concern.
2. Tool Constraints:
 Using Graphics and AI Engines leads to limitations within the
corresponding domain according to the implementation of functionalities.
 While engines reduce the burden of low-level programming, they
introduce constraints to the capabilities of the project.
3. Personnel Constraints:
 The project is subject to balanced distribution of the limited workforce.

CHAPTER-4
SYSTEM ANALYSIS
4.1 Study of Current System

Current version of a typical blockchain can handle transactions but uses a lot of processing
power and resources to do it.. This can only happen in the presence of these resources. A
basic blockchain cannot function without powerful machines and a lot of resources.
4.2 Requirement of this System

We are developing this project because the resources are not available for an eternity. They
may become extinct at some point in time. So, our cryptocurrency will deal with this problem
by using a combination of algorithms and thoroughly analysing various techniques and
reducing the probability of malfunctioning as well as crashing which are common reasons of
excessive resource consumption. By scrutinizing our code we hope to build a system that
requires less processing and considerably less resources but performs the same functions as
the other cryptocurrencies.
4.2.1 Functional Requirement

Functional requirements manage what the framework ought to do or accommodate clients.
They incorporate a depiction of the required capacities, blueprints of related reports or online
questions, and subtleties of information to be held in the framework.
 User will be able to access his/her transaction history.
 User will be able to resolve problems with the transactions.
 User can mine coins.
 An easy to use User Interface.
 A trading engine.
 The user does not have to worry about security of transactions.
 For an advance version of this project user should have a highly configured system on

which this project can run even more efficiently.
4.2.2 Non-Functional Requirement

Non-functional requirements detail requirements, targets or control instruments for the new
framework. They portray how, how well or to what standard a capacity ought to be given:
1. Performance
 The amount of data being shared
 Number and location of peers
 Latency and throughput
 Batching characteristics
2. Security
 Type of data being shared, and with whom
 How is identity achieved
 Confidentiality of transaction queries
 Who verifies (endorses) transactions
3. Resiliency
 Resource failure
 Malicious activity
 Non-determinism

4.3 Feasibility of Study

 Feasibility is the proportion of how helpful the improvement of a data framework will
be to an association.
 The feasibility analysis is categorized under four different types.
1. Operational Feasibility 2. Technical Feasibility
3. Schedule Feasibility 4. Economic Feasibility
1. Operational Feasibility
 The System is to be produced for any client who needs to utilize it. We need our
framework easy to use and simple to utilize.
 The administrator likewise might be non-specialized, so the UI will be structured
so that it gets settled for non-specialized individual to work effectively.
2. Technical Feasibility
 It is an incomplete estimation of a particular specialized arrangement and the
accessibility of specialized hotels and ability.
 The expert must see if the present specialized assets, which are accessible in the
framework is fit for dealing with the activity.
On the off chance that not, at that point the examiner with the assistance of
designer ought to affirm whether the innovation is accessible and proficient or not.
Better Considering:
 Here we have to consider those tools, which are required for developing the
project.
 As far as basic knowledge concerned, we have studied basic of python,
blockchain, ML, DS, and DL.

3. Schedule Feasibility
 Schedule feasibility compares to whether the adequate time is accessible to
finish the task.
 Factor considered:
 Schedule of the project
 Time by which project has to be completed
 Reporting period
4. Economic feasibility
 Economic feasibility is a measure of cost effectiveness of a project or solution.
 For declaring that the system is economically feasible, the benefits from the
project should exceed or at least to the equal to the cost of development.
4.4 Requirement Validation

 Requirement validation examines this specification to ensure that all the system
requirements have been stated unambiguously.
 These inconsistent, error have been detected and corrected and the work products
confirmed to the standard.
 Source of the prerequisite are distinguished, the last Statement of necessity has been
analysed by the first source.
 Requirements identified with the principle necessities are established .
 Requirements are clarifying stated and are not misinterpreted.
 All sources of necessities are secured to get the most extreme prerequisite.
 All strategy for discovering prerequisites is connected.

4.5 Canvases
4.5.1 AEIOU CANVAS
Fig.4.5.1 AEIOU Canvas

4.5.2 PRODUCT DEVELOPMENT CANVAS
Fig.4.5.2 Product Development Canvas

4.5.3 BUSINESS MODEL CANVAS
Fig.4.5.3 Business Model Canvas

4.6 Function of the System

4.6.1 Use-Case
 In programming and frameworks designing, a use case is a rundown of steps,
commonly characterizing communications among on-screen character and a
framework, to accomplish an objective.
 The actor can be a human, an external system, or time.
 In systems engineering, use cases are used at a higher level than within software
engineering, often representing missions or stakeholder goals.
 The detailed requirements may then be captured in Systems Modelling Language or
as contractual statements.
 As an important requirement technique, use cases have been widely used in modern
software engineering over the last two decades.
 Use case driven development is a key characteristic of process models and
frameworks.
 With its iterative and evolutionary nature, use case is also a good fit for agile
development.
Fig 4.6.1: Use Case Diagram

4.7 Data Modelling
4.7.1 Class Diagram

 UML is the standard language for specifying, designing, and visualizing the artifacts
of software systems
 A class is a blueprint for an object
 A class diagram describes the types of objects in the system and the different kinds of
relationships which exist among them
 It allows analysis and design of the static view of a software application
 Class diagrams are most important UML diagrams used for software application
development
 Essential elements of UML class diagram are 1) Class 2) Attributes 3) Relationships
 Class Diagram provides an overview of how the application is structured before
studying the actual code. It certainly reduces the maintenance time.
Fig 4.7.1: Class Diagram

4.7.2 Block
 The block consists of three items the hash of the previous block, the index and the list
of transactions.
Fig 4.7.2: Block
4.7.3 Activity Diagram

In terms of UML, we can use activity diagram for the following purposes, for example:
 Model complex activities and business workflows in a high level activity diagram
 Identify candidate use cases and pre- and post-conditions for use cases through the
examination of business workflows
 How the events within a single use case relate to one another, and in particular, where
activities may overlap and require coordination among use cases
 How a collection of use cases coordinate to create a workflow for an organization
 Model workflows between/within use cases

Fig 4.7.3: Activity Diagram
4.7.4 Transaction Process

 The below diagram shows the process of a typical transaction in our blockchain.
 The process starts with the user creating a request for a transaction.
 If the transaction is valid, it is added to the open transactions.
 The transaction is added to the blockchain after someone mines the block.

Fig 4.7.4: Transaction Process
4.8 Functional & Behavioural Modelling
4.8.1 Security Layers

The diagram illustrates the three security layers of the blockchain.
Fig 4.8.1: Security Layers

4.8.2 Consensus
 New transactions are broadcasted to all nodes.
 Each node binds new transactions into a block.
 Each node works on finding a difficult proof-of-work number for its block.
 When a node finds a proof-of-work, it broadcasts the block to all nodes.
 Nodes accept the block only if all transactions in it are valid and not already spent.
 Nodes express their acknowledgment of the square by taking a shot at making the following
square in the chain, utilizing the hash of the acknowledged square as the past hash.
 Nodes always consider the longest chain to be the correct one and will keep working on
extending it.
Fig 4.8.2: Consensus
4.8.3 Proof of Work (PoW)

 Proof-of-Work, or PoW, is the original consensus algorithm in a Blockchain network.
 In Blockchain, this algorithm is used to confirm transactions and produce new blocks
to the chain.
 With PoW, miners compete against each other to bind transactions to a block on the
network and get rewarded.

Fig 4.8.3: Proof of Work
4.8.4 Purpose of PoW

The main benefits are the anti-DoS attacks defence and low impact of stake on mining
possibilities.
Fig 4.8.4: Purpose of PoW

4.9 Main Modules of New System

 The main modules involved in this system are:
1. Block Creation
2. Adding valid Blocks in Blockchain
3. Validity check of blockchain
4. User interaction
5. Managing Funds, blockchain and transactions
 Module Wise Description
1. Block Creation
 A typical block in our project includes the address of previous block,
index of the block and the transactions.
 Every block is created only after it satisfies certain security conditions
 So this going to be an add-on in this project.
2. Adding valid Blocks in Blockchain
 After the block is created it is added to the blockchain.
 Also we wanted to store the result separately in a file on the system of
user’s choice of format, currently we can store it in a text file or a binary
file.
 Our goal is to keep the valid blockchain separately on the disk in a .txt
file or in a binary format.
3. Validity check of blockchain
 The blockchain cannot be created with a special algorithm created by us
known as ‘Consensus’.
 Consensus means that the blockchain of a new node will be valid only
after the majority(i.e. 51%) of nodes agree on the fact that the chain is
valid.
4. User interaction
 The UI is very simple, anyone even a person with a non-technical
background can easily use this software, which makes it easy to use.

5. Managing Funds, blockchain and transactions

 Using the UI, the user can create transactions, check the current contents
of the blockchain, mine blocks, check wallet balance, and many more
useful stuff.
4.10 Selection of Hardware & Software and Justification

Python is best open source programming language to develop any kind of applications for
small and large enterprise with portable implementation.
 Flask is also a great open source library for web development.

 We have also used a library for cryptographic operations i.e. pycryptodome to add an
extra layer of security by using hashes to validate blocks, signatures to timestamp and
RSA algorithm to generate public and private keys which are used for transactions.
 Other libraries used are binascii, json, functools, and hashlib.
 And most importantly requests to handle HTTP requests from the web server
efficiently.
 Combination of both will give a great application as output.

CHAPTER-5
SYSTEM DESIGN
Systems design is the way toward characterizing the engineering, parts, modules, interfaces,
and information for a framework to fulfil indicated necessities. The System Design Description
report provides summary or detailed information about a system design represented by
a model. Systems design is, along these lines, the way toward characterizing and creating
frameworks to fulfil indicated necessities of the client.
5.1 System Procedural design
5.1.1 Designing Pseudo Code or Algorithm for Method or Operations

Step 1: open the command prompt.
Step 2: Load the .py file onto the command prompt with the port number on which you want
to run the project.
Step 3: Open a browser and search for localhost:port_no
Step 3: A UI will open in which you can manage the blockchain.

5.1.2 Flow Chart
Fig 5.1.2: Flow Chart

5.2 Screenshots
Fig 5.2 (a): User Interface
Fig 5.2 (b): Wallet Creation/Loading

Fig 5.2 (c): Adding node to the network
Fig 5.2 (d): Transaction to other node

Fig 5.2 (e): Balance check of other node
Fig 5.2 (f): Blockchain

CHAPTER-6
CONCLUSION
Blockchain, the technology behind the Bitcoin cryptocurrency system, offers reliable transfer
of digital data over the network without the interference of any third party entity. We
developed T.R.O.J.4.N - Our own cryptocurrency based on the emerging concepts of
blockchain. The working model has been crafted using python. The UI has been built using
Flask. The UI helps us to manage the cryptocurrency providing an oversight over the number
of nodes present in the network, number of blocks in the chain, records of successful
transactions.

CHAPTER-7
APPENDIX
7.1 Periodic Progress Report (PPR)

7.1.1 PPR-1
Fig.7.1.1 PPR-1

7.1.2 PPR-2
Fig.7.1.2 PPR-2

7.1.3 PPR-3
Fig.7.1.3 PPR-3

7.1.4 PPR-4
Fig.7.1.4 PPR-4

7.2 Patent Drafting Exercise (PDE)

7.2.1 PDE Form 1
Fig.7.2.1 PDE Form 1

7.2.2 PDE Form 2

7.2.3 PDE Form 3

8. BIBLIOGRAPHY
[1] https://patents.google.com/patent/US20170132626A1/en?oq=US20170132626A1
[3] https://patents.google.com/patent/CA2981511C/en?oq=CA2981511C
[5] https://www.python.org/doc/
[6] http://flask.pocoo.org/
[7] https://pycryptodome.readthedocs.io
[8] https://cointelegraph.com/explained/proof-of-work-explained

Report Without Index

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Report Without Index

Загружено:

Авторское право:

Доступные форматы

PROJECT-II T.R.O.J.4.N.

– Our Own Cryptocurrency

SAFFRONY INSTITUTE OF TECHNOLOGY Page 1

1.4 Technology and Literature Review

 Blockchain goes about as a conveyed open record. It is a computerized record of

SAFFRONY INSTITUTE OF TECHNOLOGY Page 2

SAFFRONY INSTITUTE OF TECHNOLOGY Page 3

1.5 Prior Art Search

Inventors: Dennis M. Kennedy

Application no: US20170132626A1

Publication Date: 2015-11-05

A method for validating blockchain transactions using a transaction processing network

SAFFRONY INSTITUTE OF TECHNOLOGY Page 4

1.5.2 Blockchain-based identity and transaction platform

Inventors: Ashish Gadnis, Jeffrey A. Keiser, Michael Linton, Stanislav Natalenko

Application no: US20180285879A1

Publication Date: 2015-10-17

Systems, methods, and computer media implementing blockchain-based identity and

SAFFRONY INSTITUTE OF TECHNOLOGY Page 5

1.5.3 Systems and methods of blockchain transaction recordation

Inventors: Thomas Fay, Dominick Paniscotti

Application no: CA2981511C

Publication Date: 2015-03-31

A computer system is provided that communicates with a distributed blockchain computing

SAFFRONY INSTITUTE OF TECHNOLOGY Page 6

1.5.4 Use of Blockchain Based Distributed Consensus Control

Inventors: Lawrence Orsini, Yun Wei,Joseph Lubin

Application no: US20170103468A1

Publication Date: 2015-10-13

Devices comprising, connected to or remotely operating an electric electrically powered

SAFFRONY INSTITUTE OF TECHNOLOGY Page 7

2.1 PROJECT PLANNING AND SCHEDULING

2.1.1 Project Plan

2.1.2 Schedule Representation

Fig 2.1.2: Schedule Representation

SAFFRONY INSTITUTE OF TECHNOLOGY Page 8

2.2 Risk Management

2.2.1 Risk Identification

2.2.2 Risk Analysis

SAFFRONY INSTITUTE OF TECHNOLOGY Page 9

2.2.3 Risk Planning

SAFFRONY INSTITUTE OF TECHNOLOGY Page 10

3.1 USER CHARACTERISTICS

3.2 HARDWARE AND SOFTWARE REQUIREMENT

3.2.1 Hardware Requirements:

Processor 2 GHz processor

Operating System Windows 7 ultimate 64-bit or higher

Table 3.2.1: Hardware Requirements

SAFFRONY INSTITUTE OF TECHNOLOGY Page 11

3.2.2 Software Requirements:

Web Browser (Mozilla Firefox or Google Chrome)

Table 3.2.2: Software Requirements

SAFFRONY INSTITUTE OF TECHNOLOGY Page 12

4.1 Study of Current System

4.2 Requirement of this System

4.2.1 Functional Requirement

SAFFRONY INSTITUTE OF TECHNOLOGY Page 13

which this project can run even more efficiently.

4.2.2 Non-Functional Requirement

SAFFRONY INSTITUTE OF TECHNOLOGY Page 14

4.3 Feasibility of Study

SAFFRONY INSTITUTE OF TECHNOLOGY Page 15

4.4 Requirement Validation