CHAPTER 01 INTRODUCTION

SIT ,COMPUTER ENGINEERING 2010-11

[PAGE No.1]

AIM:
To design a system where information regarding train status is relayed from one station to the next on the same line to avoid any type of collision.

PROBLEM STATEMENT:
To build application using RFID FOR RAILWAYS which sends the information gathered at one station to other stations using the RFID technology. A RFID Railway system is available from Secure Networks in a number of configurations designed to economically meet a full range of service requirements. Reader systems provide automated tracking of railcars via RFID tags, Readers and integrated Middleware, and make railcar and locomotive identification and location information available to railroads for asset management and other purposes.

NEED FOR PROJECT\SCOPE:Railways are one of the most important modes of travel all over the world. So, all their operational procedures have to be simplified for deriving the best results. A)One such technology employed for providing the best service by the railways is the RFID railway technology. It simplifies the process of the movement of the passengers without causing any problems. The biggest benefit of such a system is in simplification of the its implementation checking system this system is completely flawless and fool proof. Since the number of passengers going through the railways has enhanced to such a large extent, the operational difficulties faced the organizations has increased considerably B)with the employment of RFID, it can hope to get rid of its many problems like increasing capital expenditure and debt management. This technology can help such organizations like railways in consolidating their revenues while cutting costs through better operations and asset operation. C)The implementation of the RFID in the railways can provide knowledge about the exact location of a particular person or his luggage. The RFID systems operated by the railways help them in making accurate decisions about managing the transportation occurring through the railways. Every operation of railways like train marshalling, train dispatching and managing train throughput can become hassle-free after the introduction of such systems . D)It will become simpler and easier for Railways to control the system of freight billing with the help of this technology. Passengers will also discover and feel the benefits of such systems.

SIT ,COMPUTER ENGINEERING 2010-11

[PAGE No.2]

BRIEF HISTORY: About RFID:

In the last few years, radio frequency identification technology has gained a lot of importance and many innovative applications are being developed using this technology. RFID technology is going to revolutionize the businesses all over the world in coming years. RFID technology has immense potential in every market segment; it is not surprising what the market surveys indicate that it will be a US$ 10 billion industry by the year 2010. However, for RFID to penetrate the market on a large scale, the cost of the tag should be very low, about 5 cents per tag would be ideal. Though the cost of the tag is coming down, it is still on the higher side for a large scale penetration. Each and every product or item can be attached with an RFID tag. And, when the tag comes in the vicinity of the reader, the contents of the tag can be read by him and then processed/sent over a network. The power of the RFID technology comes in integrating this information with the corporate network or even the global internet. .S. Patent 3,713,148 of Mario Cardullo in 1973 was the first true ancestor of modern RFID; a passive radio transponder with memory. The initial device was passive, powered by the interrogating signal, and was demonstrated in 1971 to the New York Port Authority and other potential users and consisted of a transponder with 16 bit memory for use as a toll device. The basic Cardullo patent covers the use of RF, sound and light as transmission medium. The original business plan presented to investors in 1969 showed uses in transportation (automotive vehicle identification, automatic toll system, electronic license plate, electronic manifest, vehicle routing, vehicle performance monitoring), banking (electronic check book, electronic credit card), security (personnel identification, automatic gates, surveillance) and medical. RFID tags come in three general varieties: passive, active, or semi-passive (also known as battery-assisted). Passive tags require no internal power source, thus being pure passive devices (they are only active when a reader is nearby to power them), whereas semi-passive and active tags require a power source, usually a small battery.

SIT ,COMPUTER ENGINEERING 2010-11

[PAGE No.3]

LITERATURE SURVEY AND TECHNOLOGICAL SURVEY:

To come to a final decision about our B.E project we had to take into consideration a lot of aspects. Considering the time that is given to us to complete it is one year and hence keeping that in mind we need to make a project that is impressive enough to fetch us a high score.

We also wanted the project to incorporate a vast variety of fields of engineering such that we could maximize the learning from our project. But at the same time it had to be simple enough to be able to finish it completely in the one year that is given. Another aspect was that the group being composed of 4people, it was evident that we had to come to a consensus on a particular topic. So we looked for projects that satisfied all the aspects. We found this field interesting because of its tremendous scope for future development. Coupled with RFID we could really expand our scope. we thought about the new and upcoming field of Radio Frequency Identification (RFID).. Market survey is the overview of the available design technologies and it involves the manner in which we compare, convert and implement the potential of our concept of desired system. Performance is perhaps the most widely used metric in marketing. Cost along with performance was the most widely used metric in implementing of the project. A detailed study was undertaken for a comprehensive understanding of RF communication and its application in enabling RFID standards and of the various components involved in the RFID system.

SIT ,COMPUTER ENGINEERING 2010-11

[PAGE No.4]

Chapter: 2 LITERATURE SURVEY

SIT ,COMPUTER ENGINEERING 2010-11

[PAGE No.5]

RADIO FREQUENCY IDENTIFICATION (RFID): What is RFID?

RFID stands for Radio Frequency Identification. By means of radio signals, RFID can realize a contactless and unique identification of persons and products on a short range. To do this, RFID utilizes so-called transponders: electronic labels in which the unique information is saved digitally. This digital information can be read with a special reader unit. Contrary to optical recognition (i.e. barcodes), transponders can be read invisible with the aid of radio signals.

RFID tags
RFID tags consist of an integrated circuit (IC) attached to an antennatypically a small coil of wiresplus some protective packaging (like a plastic card) as determined by the application requirements. Tags also sometimes are called transponders, and sometimes they are called inlays, although technically an inlay is a tag mounted on a substrate that is ready to be converted into a smart label. RFID tags can come in many forms and sizes. Some can be as small as a grain of rice. Data is stored in the IC and transmitted through the antenna to a reader. RFID tags are either passive (no battery) or active (self-powered by a battery). Tags also can be read-only (stored data can be read but not changed), read/write (stored data can be altered or rewritten), or a combination, in which some data is permanently stored while other memory is left accessible for later encoding and updates.

RFID Reader or Interrogator

A reader (now more typically referred to as an RFID interrogator) is basically a radio frequency (RF) transmitter and receiver, controlled by a microprocessor or digital signal processor. The reader, using an attached antenna, captures data from tags, then passes the data to a computer for processing. As with tags, readers come in a wide range of sizes and offer different features. Readers can be affixed in a stationary position (for example, beside a conveyor belt in a factory or dock doors in a warehouse), portable (integrated into a mobile

SIT ,COMPUTER ENGINEERING 2010-11

[PAGE No.6]

computer that also might be used for scanning bar codes), or even embedded in electronic equipment such as print-on-demand label printers.

Is RFID better than using Bar Codes?

RFID is not necessarily "better" than bar codes. The two are different technologies and have different applications, which sometimes overlap. The big difference between the two is bar codes are line-of-sight technology. That is, a scanner has to "see" the bar code to read it, which means people usually have to orient the bar code toward a scanner for it to be read. Radio frequency identification, by contrast, doesn't require line of sight. .Advantages of RFID 1. Transponders last a very long time. 2. Transponders are relatively cheap. 3. Transponders don't need batteries. 4. RFID Systems operate under extreme circumstances (cold / heat, pollution etc).

How does RFID work?

This is how RFID works, step by step (according to the diagram):

1. A processor controls the RFID sender / receiver controller; 2. An antenna sends high frequent energy with optional encoded information tot the transponder. 3. In the transponder, the high frequent energy is being converted to an electrical charge, which is saved; 4. This makes the transponder answer with its own, unique encoded information;
SIT ,COMPUTER ENGINEERING 2010-11 [PAGE No.7]

5. The reader unit receives the transponder's answer; this information can be processed depending on the application.

TYPES OF RFID TAGS:1. Passive tags:Passive tags refer to RFID tags which are powered solely by the RFID interrogator. The interrogator emits a radio frequency (RF), which powers the silicon chip on the tag when it is within range of the RF field. When the power to the silicon chip on the tag meets the minimum voltage threshold it require to turn on, the silcion chip can then send back information on the same RF wave. Range is usually limited to several meters.

2. Active
Active tags refer to RFID tags which have their own power source, so they can receive a weaker signal from the interrogator (i.e. be further away), and the power source on the tag boosts the return signal. These types can have ranges of many tens of meters and even hundreds of meters, but cost more because of their size and sophistication. Battery life can also limit the life of the tag.

3. Semi Passive
Semi Passive tags refer to tags with a power source (usually a laminar, flexible, low cost battery) which can be used for on tag sensing (e.g. temperature), but not to boost range. An RFID tag will be connected to each engine of the train. RFID readers will be placed at each platform. When the train arrives at platform the reader will read the information in the RFID tag and display the train Name and Number on LCD. This information will also be conveyed to successive stations by using a GSM Port (Mobile Handset) in the form of SMS. This system will consist of transmitter and receiver. At the Receiver on receiving the information, it announces that the train has reached the transmitting station. This information is then processed on the computer and the time
SIT ,COMPUTER ENGINEERING 2010-11 [PAGE No.8]

difference is calculated. This new information is then sent to all ticket holders via GSM, whose numbers are stored in the database on the computer.

Chapter :3 TECHNICAL RESEARCH

SIT ,COMPUTER ENGINEERING 2010-11

[PAGE No.9]

BRIEF ANALYSIS OF RFID:Radio-frequency identification (RFID) is an automatic identification method, relying on storing and remotely retrieving data using devices called RFID tags or transponders. The technology requires some extent of cooperation of an RFID reader and an RFID tag. An RFID tag is an object that can be applied to or incorporated into a product, animal, or person for the purpose of identification and tracking using radio waves. Some tags can be read from several meters away and beyond the line of sight of the reader. An RFID tag is an object that can be applied to or incorporated into a product, animal, or person for the purpose of identification and tracking using radio waves. Some tags can be read from several meters away and beyond the line of sight of the reader. What is RFID? A basic RFID system consists of three components: a) An antenna or coil b) A transceiver (with decoder) c) A transponder (RF tag) Electronically programmed with unique information. There are many different types of RFID systems out in the market. They are categorized according to there frequency ranges. Some of the most commonly used RFID kits are as follows: 1) Low-frequency (30 KHz to 500 KHz) 2) Mid-Frequency (900KHz to 1500MHz) 3) High Frequency (2.4GHz to 2.5GHz)

SIT ,COMPUTER ENGINEERING 2010-11

[PAGE No.10]

These frequency ranges mostly tell the RF ranges of the tags from low frequency tag ranging from 3m to 5m, mid-frequency ranging from 5m to 17m and high frequency ranging from 5ft to 90ft. The cost of the system is based according to there ranges with low-frequency system ranging from a few hundred dollars to a high-frequency system ranging somewhere near 5000 dollars.

How RFID Is Changing the Business Environment today

Radio frequency identification (RFID) technology has been in use for several decades to track and identify goods, assets and even living things. Recently, however, RFID has generated widespread corporate interest as a means to improve supply chain performance. Market activity has been exploding since Wal-Mart's June 2003 announcement that its top 100 suppliers must be RFID-compliant by January 2005. Mandates from Wal-Mart and the Department of Defense (DoD) are making many companies scramble to evaluate, select and implement solutions that will make them compliant with their customers' RFID requirements and additional retailers and other large supply chain channel masters are likely to follow suit.

COMPONENTS OF RFID:A basic RFID system consist of three components:

An antenna or coil A transceiver (with decoder) A transponder (RF tag) electronically programmed with unique information

These are described below:

1. ANTENNA
The antenna emits radio signals to activate the tag and read and write data to it. Antennas are the conduits between the tag and the transceiver, which controls the system's data acquisition and communication. Antennas are available in a variety of shapes and sizes; they can be built into a door frame to receive tag data from persons or things passing through the door, or mounted on an interstate tollbooth to monitor traffic passing by on a freeway. The
SIT ,COMPUTER ENGINEERING 2010-11 [PAGE No.11]

electromagnetic field produced by an antenna can be constantly present when multiple tags are expected continually. If constant interrogation is not required, a sensor device can activate the field. Often the antenna is packaged with the transceiver and decoder to become a reader (a.k.a. interrogator), which can be configured either as a handheld or a fixed-mount device. The reader emits radio waves in ranges of anywhere from one inch to 100 feet or more, depending upon its power output and the radio frequency used. When an RFID tag passes through the electromagnetic zone, it detects the reader's activation signal. The reader decodes the data encoded in the tag's integrated circuit (silicon chip) and the data is passed to the host computer for processing.

2. TAGS (Transponders) An RFID tag is comprised of a microchip containing identifying information and an antenna that transmits this data wirelessly to a reader. At its most basic, the chip will contain a serialized identifier, or license plate number, that uniquely identifies that item, similar to the way many bar codes are used today. A key difference, however is that RFID tags have a higher data capacity than their bar code counterparts. This increases the options for the type of information that can be encoded on the tag, including the manufacturer, batch or lot number, weight, ownership, destination and history (such as the temperature range to which an item has been exposed). In fact, an unlimited list of other types of information can be stored on RFID tags, depending on application needs. An RFID tag can be placed on
SIT ,COMPUTER ENGINEERING 2010-11 [PAGE No.12]

individual items, cases or pallets for identification purposes, as well as on fixed assets such as trailers, containers, totes, etc. Tags come in a variety of types, with a variety of capabilities. Key variables include: "Read-only" versus "read-write" There are three options in terms of how data can be encoded on tags: (1) Read-only tags contain data such as a serialized tracking number, which is pre-written onto them by the tag manufacturer or distributor. These are generally the least expensive tags because they cannot have any additional information included as they move throughout the supply chain. Any updates to that information would have to be maintained in the application software that tracks SKU movement and activity. (2) "Write once" tags enable a user to write data to the tag one time in production or distribution processes. Again, this may include a serial number, but perhaps other data such as a lot or batch number. (3) Full "read-write" tags allow new data to be written to the tag as neededand even written over the original data. Examples for the latter capability might include the time and date of ownership transfer or updating the repair history of a fixed asset. While these are the most costly of the three tag types and are not practical for tracking inexpensive items, future standards for electronic product codes (EPC) appear to be headed in this direction.

RFID TAGS Data capacity The amount of data storage on a tag can vary, ranging from 16 bits on the low end to as much as several thousand bits on the high end. Of course, the greater the storage capacity, the higher the price per tag.

SIT ,COMPUTER ENGINEERING 2010-11

[PAGE No.13]

Form factor The tag and antenna structure can come in a variety of physical form factors and can either be self-contained or embedded as part of a traditional label structure (i.e., the tag is inside what looks like a regular bar code labelthis is termed a 'Smart Label') companies must choose the appropriate form factors for the tag very carefully and should expect to use multiple form factors to suit the tagging needs of different physical products and units of measure. For example, a pallet may have an RFID tag fitted only to an area of protected placement on the pallet itself. On the other hand, cartons on the pallet have RFID tags inside bar code labels that also provide operators human-readable information and a back-up should the tag fail or pass through non RFID-capable supply chain links. Passive versus active Passive tags have no battery and "broadcast" their data only when energized by a reader. That means they must be actively polled to send information. "Active" tags are capable of broadcasting their data using their own battery power. In general, this means that the read ranges are much greater for active tags than they are for passive tagsperhaps a read range of 100 feet or more, versus 15 feet or less for most passive tags. The extra capability and read ranges of active tags, however, come with a cost; they are several times more expensive than passive tags. Today, active tags are much more likely to be used for high-value items or fixed assets such as trailers, where the cost is minimal compared to item value, and very long read ranges are required. Most traditional supply chain applications, such as the RFID-based tracking and compliance programs emerging in the consumer goods retail chain, will use the less expensive passive tags. Frequencies Like all wireless communications, there are a variety of frequencies or spectra through which RFID tags can communicate with readers. Again, there are trade-offs among cost,
SIT ,COMPUTER ENGINEERING 2010-11 [PAGE No.14]

performance and application requirements. For instance, low-frequency tags are cheaper than ultra high-frequency (UHF) tags, use less power and are better able to penetrate non-metallic substances. They are ideal for scanning objects with high water content, such as fruit, at close range. UHF frequencies typically offer better range and can transfer data faster. But they use more power and are less likely to pass through some materials. UHF tags are typically best suited for use with or near wood, paper, cardboard or clothing products. Compared to lowfrequency tags, UHF tags might be better for scanning boxes of goods as they pass through a bay door into a warehouse. While the tag requirements for compliance mandates may be narrowly defined, it is likely that a variety of tag types will be required to solve specific operational issues. You will want to work with a company that is very knowledgeable in tag and reader technology to appropriately identify the right mix of RFID technology for your environment and applications. RF Transceiver: The RF transceiver is the source of the RF energy used to activate and power the passive RFID tags. The RF transceiver may be enclosed in the same cabinet as the reader or it may be a separate piece of equipment. When provided as a separate piece of equipment, the transceiver is commonly referred to as an RF module. The RF transceiver controls and modulates the radio frequencies that the antenna transmits and receives. The transceiver filters and amplifies the backscatter signal from a passive RFID tag. Typical Applications for RFID:

Automatic Vehicle identification Inventory Management Work-in-Process Container/ Yard Management Document/ Jewellery tracking Patient Monitoring

SIT ,COMPUTER ENGINEERING 2010-11

[PAGE No.15]

MICROSOFT VISUAL C# 2005 Microsoft Visual C# 2005, pronounced C sharp, is a programming language designed for building a wide range of applications that run on the .NET Framework. C# is simple, powerful, type-safe, and object-oriented. With its many innovations, C# enables rapid application development while retaining the expressiveness and elegance of C-style languages. Visual Studio supports Visual C# with a full-featured Code Editor, project templates, designers, code wizards, a powerful and easy-to-use debugger, and other tools. The .NET Framework class library provides access to a wide range of operating system services and other useful, welldesigned classes that speed up the development cycle significantly. Extensions for component-oriented development Visual C# provides developers with a powerful component-oriented development language that includes support for properties, indexers, delegates, inheritance, versioning, and attributes, without the need for esoteric or rigid naming patterns and companion classes. Interactive XML Web services Visual C# allows developers to deploy and consume rich, interactive XML Web services that reduce development time by enabling software aggregation from any platform. Microsoft is famous for hiding the details from the developer: This is both good and bad. Leverage the .NET Framework Visual C# provides developers with access to the Microsoft .NET Framework--a robust, threadsafe library of collection classes, data access classes, networking functions, etc. Recently, however, various bridge software offer . Object-based type system Visual C# provides developers an object-based type system that eliminates the need for complex, verbose data marshalling code commonly required by Java applications.

SIT ,COMPUTER ENGINEERING 2010-11

[PAGE No.16]

Target any device Visual C# lets developers target desktop computers or a variety of handheld and wireless devices using identical tools and skills. True, but all the devices must be Windows based. XML comments Visual C# allows developers to use eXtensible Markup Language (XML) Comments to provide useful and customizable source code documentation. Of course, so does Java although Microsoft does add its own twists to it.

Chapter: 4

SOFTWARE REQUIREMENT SPECIFICATION

SIT ,COMPUTER ENGINEERING 2010-11

[PAGE No.17]

INTRODUCTION Scope and Purpose of Document

To present an overview of the software to be designed. A more detailed view of the project will follow which will include the development phases and the deliverables. (A)Software requirements specifications produced at the end of the analysis task (B)To present an analysis of the perceived problem from which a list of specific unambiguous requirements will be formulated from the users point of view. This list will include functional, external interface, performance and other requirements. (C)Design constraints and attributes leading to the finished product will be specified. (D)The function and refined performance allocated to software as part of system engineering are refined by establishing a complete information description, a detailed functional description, an indication of performance requirements and design constraints, appropriate validation criteria, and other data pertinent to requirements. (E)To discuss the approach adopted to carry the project through the development process to completion. This will include the analysis and design techniques used. (F) To provide an overview of the interaction between the user and the system, design of the visual appearance of the interface. A description of the interface between the user interface and the software will be included.

SIT ,COMPUTER ENGINEERING 2010-11

[PAGE No.18]

(G)SRS document is made to specify various acronyms, abbreviations and their meaning. This document will give overall description of Project in terms of product perspective, product functions, general constraints and assumptions. It will also specify specific requirements like external interface, functional requirements performance requirements and design constraints

Problem Statement:
To build application using RFID FOR RAILWAYS which sends the information gathered at one station to other stations using the RFID technology. A RFID Railway system is available from Secure Networks in a number of configurations designed to economically meet a full range of service requirements. Reader systems provide automated tracking of railcars via RFID tags, Readers and integrated Middleware, and make railcar and locomotive identification and location information available to railroads for asset management and other purposes.

Need For Project Scope:Railways are one of the most important modes of travel all over the world. So, all their operational procedures have to be simplified for deriving the best results. a)One such technology employed for providing the best service by the railways is the RFID railway technology. It simplifies the process of the movement of the passengers without causing any problems. The biggest benefit of such a system is in simplification of the its implementation checking system this system is completely flawless and fool proof. Since the number of passengers going through the railways has enhanced to such a large extent, the operational difficulties faced the organizations has increased considerably. b)with the employment of RFID, it can hope to get rid of its many problems like increasing capital expenditure and debt management. This technology can help such organizations like railways in consolidating their revenues while cutting costs through better operations and asset operation. c)The implementation of the RFID in the railways can provide knowledge about the exact location of a particular person or his luggage.

SIT ,COMPUTER ENGINEERING 2010-11

[PAGE No.19]

The RFID systems operated by the railways help them in making accurate decisions about managing the transportation occurring through the railways. Every operation of railways like train marshalling, train dispatching and managing train throughput can become hassle-free after the introduction of such systems. d)It will become simpler and easier for Railways to control the system of freight billing with the help of this technology. Passengers will also discover and feel the benefits of such systems.

Goals and objective The Objective of the project is to strengthen the present railway anti-collision systems by making them work collaboratively in the network. Reader systems provide automated tracking of railcars via RFID tags, Readers and integrated Middleware, and make railcar and locomotive identification and location information available to railroads for asset management and other purposes The main goals in the project are 1. Toimplement an anti-collision system using radiofrequency identifications. 2. To use the mechanism of rfid for applications like asset tracking etc.

SOFTWARE AND HARDWARE SPECIFICATION(s):

SIT ,COMPUTER ENGINEERING 2010-11

[PAGE No.20]

RFID Device CPU Memory Display Options Input Device Operating Systems Application Libraries Technologies / Software Pentium IV 512 MB RAM VGA Keyboard, Mouse Windows XP/Windows 2000 .Net Framework, ASP.Net, C# ASP.Net (Front End), IIS (Server) and SQLServer (Back End)

Run-Time Requirements: Required:

Microsoft Windows 98, Windows NT 4.0 (x86), or Windows 2000.,Windows XP, . A Pentium 100 MHz PC (or faster). At least 16 megabytes (MB) RAM. At least 1 MB free disk space for the core components. Atleast one rfid device,reader alongwith seprate group of tags.

FEATURES/BENEFITS :I)The System stores tag data including time, date, train direction and speed. II) It also responds to inquiries via modem and interfaces to scales, video systems and diagnostic and monitoring devices.

SIT ,COMPUTER ENGINEERING 2010-11

[PAGE No.21]

III)Timely data to increase capacity, speed, automation and operational flexibility IV)Arrival and departure data for signal and control operations

ASSUMPTIONS:-

I)The components/Modules will be developed in C#.Net and the front end will be ASP.Net and would comply to .NET framework specifications. II)Components may inherit from existing available Microsoft .NET components but may customize to suit the requirements. III)All the project team members have good knowledge of .NET framework basics, ASP.Net, C#.Net programming . IV)Some smaller dummy implementation applications would need to be developed to test & demonstrate the functionality provided by these components.

Chapter: 5
SIT ,COMPUTER ENGINEERING 2010-11 [PAGE No.22]

SOFTWARE PROJECT PLAN

Introduction
This section gives the specification of various tasks performed during the project-planning phase of RFID for railways. It highlights the project idea, relevance, objectives and resources along with the work structure proposed for the project. The RMMM plan and the SQA plan are also proposed after the risk analysis and the resource estimation for the project. 5.1Project Scope

Reliability
The System shall be self-monitoring. The System is not immune to changes under any abnormal conditions such as hardware failure or OS crash etc. The system can be run only on android platform.

Availability
The System is available all the time with just mobile GPRS active in.
SIT ,COMPUTER ENGINEERING 2010-11 [PAGE No.23]

Security
The security provided to the system is same as that provided by Google to the Gmail since entire data is going to be stored on the Gmail account of the user.

Maintainability
The system requires zero maintenance from the user side.

5.2 Feasibility Study:

A feasibility study is a preliminary study undertaken to determine and document a project's viability. The results of this study are used to make a decision whether to proceed with the project, or table it. If it indeed leads to a project being approved, it will - before the real work of the proposed project starts - be used to ascertain the likelihood of the project's success. It is an analysis of possible alternative solutions to a problem and a recommendation on the best alternative. It, for example, one can decide whether an order processing be carried out by a new system more efficiently than the previous one or not.

Technical Feasibility:
Technical feasibility is the study of the hardware and software requirement i.e. the technical requirement of the system in order to inform the management and user that for particular system designing this much technical resource are required. In order to know the user and management view regarding the technical resources, following are the technical resources required for developing the system.

Software Requirements :
Microsoft windows operating system Microsoft windows operating system is used as if it is widely available and fulfills all the requirements of our project Microsoft DotNet Framework 3.5 Net Framework is used for developing the project because it is very convenient for developing user interface as well as handling database connectivity.
SIT ,COMPUTER ENGINEERING 2010-11 [PAGE No.24]

Microsoft C# 2005 Vulguard will be interacting with a host of software during its execution. Primarily it interacts with SQL Server, .Net framework, XML parser, and all of their updates. Secondarily it will interact with Windows Firewall which at high security level might block the execution of our software; here it may be need user to enable execution by unblocking.

Hardware Requirements
Intel Core2Duo PC with 1GB Ram 1GB of Hard Disk Space 2.66 GHZ Processor speed No additional Hardware would be required other than normal

interface(monitor, keyboard, mouse , CPU unit as specified in hardware requirements)

Economic Feasibility:
As it is an internal project the development cost of our project is minimal. The softwares and hardwares required are provided to us by our college. Thus, the expenditure of Software and Hardware is also minimal.

Resources: Human Resources:

The planner begins by evaluating scope and selecting the skills required to complete development. The number of people required for a software project can be determined only after an estimate of development effort is made. The project team members who will be engaged in development of the project are the very important human resources for the project.
SIT ,COMPUTER ENGINEERING 2010-11 [PAGE No.25]

5.3 Risk Management:

Everyone associated with the software has the responsibility of managing the risk. That is if everyone participated and paid close attention to all the details during the early phase of the software development many risk can be avoided. Software development can avoid having risk by double checking their Customer can help avoid risk by providing all necessary software information Software development team can avoid risk by getting all the details of the Client can avoid risk by making all necessary business change before initiating schedule, product size, estimates regarding costs of the development. during the early phase of the software development. equipment that are provided or are accessible to them. request for the software.

5.4

SQA Plan:

This document describes the Software Quality Assurance Plan for the Webbased Skills Tracking System. It mainly focuses on the construction phase of development. The analysis and design phases are also taken into consideration. Software Quality Assurance is an umbrella activity and will cover all major phases of the software development- requirements gathering, analysis, design, code development and testing. There will not be any special group to perform the SQA activities but the project team itself will be actively involved in ensuring the following: Conformance to explicitly state functional and functional and performance Explicitly documented development standards. Implicit characteristics that are expected of all professionally developed requirements.

software. Purpose of the Plan:

SIT ,COMPUTER ENGINEERING 2010-11 [PAGE No.26]

The SQA plan is made to describe all the software process activities that are covered by quality assurance. The whole purpose of this plan is to ensure that quality is maintained throughout the software project lifecycle.

SQA Activities:
SQA Task#1: The first SQA task will be development of the projects software process description. SQA Task#2: The second SQA task will be to conduct formal reviews of the software engineering activities to verify compliance with the defined software process. SQA Task#3: The third SQA task will be to audit designated software work products to verify compliance with those defined as part of the software process. SQA Task#4: The fourth SQA task will be to ensure that deviations in software work and work products are documented and handled according to a documented procedure. SQA Task#5: The final SQA task will be to record any noncompliance.

5.5 Documentation:
As a result of the above SQA activities, changes to the initial design were made in order to take into consideration, the exact requirements of the customer. The corresponding changes were also incorporated into the architectural design of the software. As a result of the above SQA activities, changes to the initial design were made in order to take into consideration, the exact requirements of the customer. The corresponding changes were also incorporated into the architectural design of the software. The work products produced as part of the software process are: Project plan. Data Flow Diagrams
SIT ,COMPUTER ENGINEERING 2010-11 [PAGE No.27]

 Technical Documents Software Requirement Specification. Test Plans User documents like help pages and Guide. Management: Organization: Help provides by guide. Tasks: Periodical checks of the work. Responsibilities: The responsibility lies on the project group. Problem Reporting and corrective action: The unforeseen problems which occur are reported to the guide during the periodical reviews. The corrective actions are taken as per the suggestions and advices given by them. Standardization: The document standards are all according to standard IEEE format and ISO Std

SIT ,COMPUTER ENGINEERING 2010-11

[PAGE No.28]

Problem Reporting and corrective action: The unforeseen problems which occur are reported to the guide during the periodical reviews. The corrective actions are taken as per the suggestions and advices given by them. Standardization: The document standards are all according to standard IEEE format and ISO Std. 5.6 Major software functions There are following major functions 5.6.1 Project Estimates We are following the Constructive Cost Model (COCOMO) for estimating the effort required in completing the project. The initial effort (Ei) in man months is calculated using the equation : Ei = a * (KLOC)^b where a and b are constants depending whether the project organic, semidetached, or embedded category. The values are as follows : System Organic Semidetached Embedded A 3.2 3.0 2.8 B 1.05 1.12 1.20

Our system belongs to semidetached category which falls between the organic and embedded systems. Organic projects are in an area in which the organization has considerable experience and whose requirements are less stringent. Embedded projects are those which have tight constraints, in which the organization has little experience and stringent requirements for aspects such as interfacing and reliability. Therefore a = 3.0 and b = 1.12 There are 15 cost drivers which may either increase or decrease the final effort depending upon the rating. The effort adjustment factor is calculated by multiplying the various cost driver multipliers. The final effort estimate, E, is obtained by multiplying the initial estimate by the EAF.
SIT ,COMPUTER ENGINEERING 2010-11 [PAGE No.29]

E = EAF * Ei

Cost Drivers Software Reliability Req. Data Base Size Product Complexity Execution Time Constraint Main Storage Constraint Virtual Machine Volatility Machine Turnaround Time Analyst Capability Application Experience Programmer Capability Programming Lang Exp. Modern Prog. Practice Use of SW tools Development Schedule

Rating High Low High Nominal Nominal Low Nominal High Nominal High High Nominal High Nominal

Multiplier 1.15 0.94 1.15 1.0 1.0 0.87 1.0 0.86 1.0 0.86 0.95 1.0 1.0 1.0

The table below gives the ratings and multipliers for the various cost drivers in the project. EAF = 1.15 * 0.94 * 1.15 * 1.0 * 1.0 * 0.87 * 1.0 * 0.86 * 1.0 * 0.86 * 0.9 *1.0* 1.0 * 1.0 EAF = 0.76

5.6.2Milestones of the project

1.Understanding requirements of the client. 2..Preparing the Software Requirement Specification. a.Study the standard required. b.Use the understanding of step 1 to prepare the document. 3.Prepare the design document a. Study the other design documents

SIT ,COMPUTER ENGINEERING 2010-11

[PAGE No.30]

b. Prepare the design document 4.Enhancement of knowledge / skill set. a. Discuss the implementation issues to find out what additional skills are required b.Dedicate enough time so that these skills are acquired. 5.Implementation. a. Divide the modules to be done between the members. b.Do the implementation . 6.Delivering the first prototype. a. Integrate all the modules. b.Do deployment c.Give a demonstration of the working module. 7Delivering the advanced prototype a. Include additional features based on time remaining. b. Integrate and stabilize the software. c. Give a demonstration of this prototype. 5.7 Risk Management The RMMM plan prepared by us tackles risks through RISK Assessment and Risk Control. Risk Assessment involves Risk Identification, Risk Analysis and Risk Prioritization, while Risk Control involves Risk Management Planning, Risk Resolution and Risk Monitoring. 5.7.1 Project Risks 5.7.2 Risk Identification Our development team identified different potential risks to the project. These risks were analyzed and were classified into various categories depending upon the threat they posed to the project. Some of these risks were generic risks while others were product specific risks. A considerable amount of time was spent in analyzing the product specific risks. 5.7.3 Risk Analysis We analyzed all the risks individually and we came up with a classification of risks on the basis of their impact on project schedule. These risks were rated as follows : Catastrophic Critical Marginal
SIT ,COMPUTER ENGINEERING 2010-11 [PAGE No.31]

 Negligible These were then reviewed and a consensus on the impact was reached. 5.7.4 Risk Prioritization After analyzing the risks, the risks were prioritized based on the review and consensus among the developers. 3.2 Risk Table Sr.No. 1. 2. 3. 4. 5. 6. 7. 8. 9. 10 11. 12. 13. 14. 15. 16 17. 18. 19. Risk Stricter completion deadline Wrong estimate of size and effort Overly optimistic schedule Error prone modules require more testing and implementation work Lower use of code than expected Lack of sufficient research or development in field Developers work slower than expected Increase on workload on developers and hence divided attention on project Lack of hardware resources Developers assignments dont match their strength Lack of rapport amongst team members Change of technical guide Inexperience in project software environment Inexperience in programming language Lack of technical support on unforeseen environment Requirements have been finalized but continue to change Schedule omits necessary tasks Design neglects major issues Integrating new code with existing code may be difficult Category Business Project Project Project Technical Technical Personnel Personnel Project Personnel Personnel Personnel Technical Technical Technical Project Project Project Technical Probability 10% 40% 30% 30% 25% 30% 30% 50% 50% 30% 25% 75% 40% 10% 35% 45% 20% 20% 35% Impact Critical Critical Critical Critical Critical Critical Critical Marginal Critical Marginal Negligible Marginal Marginal Marginal Critical Critical Critical Critical Critical

Risk Management Software Risk management is a set of practices that enable software development projects to access overall project risk and identify, prioritize and manage specific risk.
SIT ,COMPUTER ENGINEERING 2010-11 [PAGE No.32]

Projects using risk management to manage their risks have realized benefits including: Prevention of schedule delays Reduce project cost More predictable schedules Better attainment of customer commitments

5.8 Project Risks Major risks for this software development are 1) Increase of workload on developers and hence divided attention on project. 2) Insufficient guidance in the fields of the project. 3) Inexperience in project software environment. 4) Requirements have been finalized but continue to change. 5) Overly optimistic schedules. 6) 5.8.1 Risk Table Risk 1 Increase of workload on developers and hence divided attention on project. 2 Insufficient guidance in the fields of the project 3 Inexperience in project software environment 4 Requirements have been finalized but continue to change 5 Overly optimistic schedules 6 Lack of sufficient research in the respective technologies 7 A wrong estimate on size and effort Category Probability Impact Personnel 25% Marginal Technical Technical Project Project Technical Project 10% 35% 30% 20% 20% 25% Critical Marginal Negligible Negligible Critical Marginal

Critical: Failure would degrade performance, mission success is questionable. Marginal: Failure would result in degradation of secondary mission. Negligible: Failure to meet would create inconvenience or slight impact. 5.8.3 Overview of Risk Mitigation, Monitoring, Management 5.8.4 Work Distribution chart
SIT ,COMPUTER ENGINEERING 2010-11 [PAGE No.33]

Task Drafting the problem statement Project synopsis Information gathering Study of existing systems Study of .NET Requirement Analysis Authorization main code Package Design Front end design Test plan Installation Testing Project report 5.9 Staff Organization 5.9.1Team structure

Parag Haide r

Harsh Sudhansh

5.9.2 Management reporting and communication There was a compulsory weekly meeting in addition to other meetings. Each group member would discuss the goals achieved as well as targets were set for the next week along with consultation with the internal guide. Meetings were conducted with internal guide on a regular basis along with constant consultation via e-mail.

5.10Project Resources People: four people involved. Hardware: 2 computers (1 GB RAM )

SIT ,COMPUTER ENGINEERING 2010-11

[PAGE No.34]

Software: Eclipse 3.2, Java Development Kit 1.5, Oracle 9i 5.11 Staff Organization 5.11.1 Team structure The team consists of four people. The sub-components are divided among them. 5.1.1 Roles and Responsibilities The roles and responsibilities of the group members are as follows:

Names Aviral Sharma Amit Hajare

Functions 1. Scope Definition 2. Technical Research : Key generation, Encryption Modules 3. Prototype Implementation 4. Analysis 5. Design 1. 2. 3. 4. 5. Scope Definition Technical Research : Decryption and SMS Modules Prototype Implementation Analysis Design

Abhishek khandelwal Mayur kothmire

5.11.2 Management reporting and communication For progress reporting and inter/intra team communication, we are using mechanisms like maintaining a log-book of all meetings with our internal and external guide.

SIT ,COMPUTER ENGINEERING 2010-11

[PAGE No.35]

Chapter: 6 DESIGN SPECIFICATION

SIT ,COMPUTER ENGINEERING 2010-11

[PAGE No.36]

ACTIVITY DIAGRAM

SIT ,COMPUTER ENGINEERING 2010-11

[PAGE No.37]

SIT ,COMPUTER ENGINEERING 2010-11

[PAGE No.38]

CLASS DIAGRAM

SIT ,COMPUTER ENGINEERING 2010-11

[PAGE No.39]

SEQUENCE DIAGRAM

SIT ,COMPUTER ENGINEERING 2010-11

[PAGE No.40]

COMPONENT DIAGRAM

SIT ,COMPUTER ENGINEERING 2010-11

[PAGE No.41]

DEPLOYMENT DIAGRAM

SIT ,COMPUTER ENGINEERING 2010-11

[PAGE No.42]

Chapter: 07 TESTING

SIT ,COMPUTER ENGINEERING 2010-11

[PAGE No.43]

TESTING 7.1 Introduction

Software testing is a critical element of software quality assurance and represents the ultimate review of specification, design and coding. The purpose of this document is to provide a complete list of test specifications for integrating the software Authorization Engine. These specifications are used to generate software verification test procedures. Testing is a process of executing a program with the intent of finding of an error. Testing demonstrates that software-functions appear to be working according to specification and that behaviors and performance requirement appear to have been met. The basic goal is to design a series of test cases that have a likelihood of finding errors. It is the role of test management to ensure that new or modified service products meet the business requirements for which they have been developed or enhanced. The purpose of test management is to ensure that a testing strategy is both devised and applied that is efficient, effective and economic. The testing strategy should define the objectives of all test stages and the techniques that apply. The testing strategy also forms the basis for the creation of a standardized documentation set, and facilitates communication of the test process and its implications outside of the test discipline. Any test support tools introduced should be aligned with, and in support of, the test strategy. Test management is also concerned with both test resource and test environment management.

7.1.1 Goals and objectives

To test the software for performance degradation under stress. To uncover bugs in the system to set aright any flaws in logic that may be present. To check logical flow from one module to another within system.

SIT ,COMPUTER ENGINEERING 2010-11

[PAGE No.44]

7.1.2 Statement of scope This application is developed for the main Authorization algorithm, to make sure that the values returned are in tune with the existing rules and user qualifications. For various functions that can be performed by the administrator complex queries fetch data from the databases, all these queries need to be tested. The most important element to be tested is the time that a particular transaction takes, coming up with associated figures and attempt to engineer constantly to improve the results.

7.2 Test Plan

The overall testing strategy and the project management issues that are required to properly execute effective tests have been mentioned. Creating inputs such as test data, test cases Here the test data such as different messages for different domains are created. Different test cases such as null results, blank fields, invalid entries etc. are created. Here the procedure had been created to identify how the system will be tested after getting test data. Carry out testing according to test procedures Here the actual testing is carried out according to test procedures and using different test data and test cases. The modules in the project were checked on the basis of the following details: All details about every activity to be done (what is to be done, when, how etc.). Data and other input to be given, if any. Behavior expected of the system. Evaluation procedure, for interpreting the results.

Creation of test procedure

SIT ,COMPUTER ENGINEERING 2010-11

[PAGE No.45]

Control decisions: When to start, end, suspend, resume, and return the test, actions to be taken in case of exceptional situations (for e.g. if the network gets lost during the backup period).

7.3Testing strategy
The overall strategy for software testing is described. 7.3.1Unit testing (White Box Testing) The system consists of several components that work together. Unit testing focuses verification effort on the smallest unit of software design-the software component or module. The unit test is white box oriented and can be conducted in parallel for multiple components. Following are the steps taken for unit testing: A functional module was created by the respective programmer and tested if it works properly for the expected inputs. If error occurs for certain conditions or boundary cases, they were rectified. It is made sure that the system doesnt crash for any input. It is made sure that necessary Error Messages are displayed to users. Maintaining the authenticity of the administrator and the users.

SIT ,COMPUTER ENGINEERING 2010-11

[PAGE No.46]

The diagram above outlines the Test Process approach that will be followed. a. b. Organize Project involves creating a System Test Plan, Schedule & Test Approach, and requesting/assigning resources. Design/Build System Test involves identifying Test Cycles, Test Cases, Entrance & Exit Criteria, Expected Results, etc. In general, test conditions/expected results will be identified by the Test Team in conjunction with the Project Business Analyst or Business Expert. The Test Team will then identify Test Cases and the Data required. The Test conditions are derived from the Business Design and the c. Transaction Requirements Documents Design/Build Test Procedures includes setting up procedures such as Error Management systems and Status reporting, and setting up the data tables for the d. e. f. g. Automated Testing Tool. Build Test Environment includes requesting/building hardware, software and data set-ups. Execute Project Integration Test - Test Phases & Cycles Execute Operations Acceptance Test - Test Phases & Cycles Signoff - Signoff happens when all pre-defined exit criteria have been achieved.

7.3.2 Integration testing

This phase tested the integration of all the modules. The phase concentrated on various interface mismatch problems that arose between the subsystems when integration of various modules of the system was done. Integration testing is a systematic technique for constructing the program structure while at the same time conducting test to uncover errors associative with interfacing. The objective is to take unit tested component and build the program structure that has been designed. Following are the steps taken for integration testing are: Merge the required individual functional components created. Test if they produce the correct results for all the inputs Check if there is no interface problem between the individual components.

7.3.3 Validation Testing

SIT ,COMPUTER ENGINEERING 2010-11

[PAGE No.47]

Software validation is achieved through a series of black block tests that demonstrates conformity with requirements. Validation succeeds when software functions in manner that can be reasonably expected by customer.

Alpha Testing: This test is conducted at developers site by customer. The software is
used in a natural setting with the developer looking over the shoulder of the user and recording errors and usage problems.

Beta Testing: This test is conducted by one or more customer sites by end user of the
software. This test is a live application of the software in an environment that cannot be controlled by the developer.

7.3.4. System Testing

Pressman believes that system testing fails outside the scope of the software engineering process as it is not conducted solely by the software developer. He does define the system testing through as,... a series of different tests whose primary purpose is to fully exercise the computer-bases system. A system testing is actually a series of different tests whose primary purpose is to fully exercise the computer-based system. The final integrated system has undergone a series of tests, thus inspecting its stability and performance.

7.4Testing tools and environment

Operating System: Windows XP Software: . Net Framework, ASP. Net, C# ASP. Net (Front End), IIS (Server) & MS ASCESS(Back End) Hardware: RFID device, tags & readers

SIT ,COMPUTER ENGINEERING 2010-11

[PAGE No.48]

7.5Test schedule A detailed schedule for unit, integration, and validation testing as well as high order tests is described. Task No of people Unit Testing involved 3 Man hrs required 15 3 21 Feb 2007 Integration Testing 3 20 6 4 March 2007 Stress and 3 15 3 14 Mar 2007 23 Feb -2007 9 Mar 2007 16 Mar 2007 No. of days Start date End date

Validation Testing.

Purpose of the test cases: Test cases help us in building confidence in our code. Test cases should be plotted in such a manner, that they exercise different parts of the code. By testing the code as per the plotted cases, we can easily check out the system functionality. We also get to know the scenarios for which the system fails. The corresponding code can then be examined and corrected. Thus, a good set of test cases not only ensures correct system functionality but also aids in error detection and correction.

SIT ,COMPUTER ENGINEERING 2010-11

[PAGE No.49]

Unit Testing: RFID FOR RAILWAYS

Sr.n o 1 Functionality Working of rfid Objectives To allow Steps and data Expected result Select appropriate connectivity IRFID device,tag, anteena should communicate properly else error should be Select one of the database and press Yes. displayed. After pressing Yes list of maintainance types within that database will be displayed, AlternateResult If communication doesnt established than appropriate, error messages should be displayed. If Yes is pressed without selecting database then error message will be displayed Pass Remark Pass

device,anteena,tag reliable Track inspection system,Wagon 2 Yard Maintainance tracking Effective error handling

communication database

SIT ,COMPUTER ENGINEERING 2010-11

[PAGE No.50]

Chapter:08 APPLICATIONS & FUTURE WORK

8.1 Applications:
SIT ,COMPUTER ENGINEERING 2010-11 [PAGE No.51]

The system can be used by administrator for having the current location of the train railyard information managegment,Track inspection system,maintainance etc Better equipment distribution and management RFID tags are assign a particular tag no,tag index,tag id to avoid any confusion Database is used to keep the details as a reference for future enhancement 8.2 Future Enhancements: I) In future the system can be accommodated using google API(application programming interface) technology a) It enhance the rate of perfection along with precision. b)Service provided by google II) The project can be enhanced by using GSM technology. Using GSM technology admin will be able to receive information about current location of the train,next stop at the arrival of current stop,wagon tracking m and it will also provide information about various routes available

III).Active RFID technology can be used for larger scale or for commercial purposes as it
has larger communication range. IV)latest compatible rfid readers,anteenas along with appropriate tags with as much fields of information as possible. Cost of the project is the important aspect of its implementation steps should be taken to reduce the cost as much as possible by implementing latest compatible rfid readers,anteenas Along with appropriate tags with as much fields of information as possible. V)Effective and large scale database to enlarge the area of working of our project

VI ) limited functionality can be created with lot of more functionality providing developer with more functions implemented in class.

8.3 Limitations: The system can only generate classes of c# language these classes doesnt support another language. Cost of RFID readers,tags & device is major aspect to deal with
SIT ,COMPUTER ENGINEERING 2010-11 [PAGE No.52]

Accuracy The System should be 100 % accurate ideally. It should not suffer from any bug. Our system is not providing any authority to user for updating database. So it is very accurate. Timing Describe the timing requirements to be imposed on the system, such as: Response time between input data and system availability should be least as possible keeping correct results in mind. Response time of queries should be fast Capacity Limits There is no capacity limit only there should have space on hard disk to store the generated classes.

SIT ,COMPUTER ENGINEERING 2010-11

[PAGE No.53]

Chapter:09 SUMMARY & CONCLUSION

Summary:

SIT ,COMPUTER ENGINEERING 2010-11

[PAGE No.54]

Problem definition was thoroughly understood and scope of project was determined. Requirement analysis was done for gathering requirements and determining functionality of tool. Proper design was done as per given requirement and modules to be developed were determined. Total architecture of system was finalized.

Conclusion:
In the end we like to conclude that the potential for the project is very high. A totally new business model can be evolved from this project. This tool can be used effectively used on various database applications and also its cost effectiveness is very high. Various data losses due to vulnerable procedures can now be overcome with the help of this system. The efficient data storage and then backing up the lost data that is in the form of various formats which gives this system an edge as compared to the other system present in the market. The use software engineering principles in the end helped in keeping the project focus and completing the project on time. It helped to clear many design issues and provide clarity of thoughts. Software Testing helped us to recognize various flaws present in the system which were unrecognized during the implementation process. Thus we would like to conclude that in the end the project was properly implemented and above all very good learning experience. The second and the more important side is what we as engineering students learned in the course of this project academically and professionally.

SIT ,COMPUTER ENGINEERING 2010-11

[PAGE No.55]

Chapter:10 SCREEN SHOTS

SCREEN SHOT No.(01) HOME PAGE

SIT ,COMPUTER ENGINEERING 2010-11

[PAGE No.56]

SCREEN SHOT No.(02) ADMIN HOME

SIT ,COMPUTER ENGINEERING 2010-11

[PAGE No.57]

SCREEN SHOT No.(03) REPLACE RFID TAGS

SIT ,COMPUTER ENGINEERING 2010-11

[PAGE No.58]

SCREEN SHOT No.(04) REGISTER RFID TAG ON WAGON

SIT ,COMPUTER ENGINEERING 2010-11

[PAGE No.59]

SCREEN SHOT No.(05) REGISTER RFID TAGS

SIT ,COMPUTER ENGINEERING 2010-11 [PAGE No.60]

SIT ,COMPUTER ENGINEERING 2010-11

[PAGE No.61]

SCREEN SHOT No.(06) YARD INFORMATION

SCREEN SHOT No.(07) MAP

SIT ,COMPUTER ENGINEERING 2010-11 [PAGE No.62]

SCREEN SHOT No.(08) MAINTANANCE REPORT

SIT ,COMPUTER ENGINEERING 2010-11 [PAGE No.63]

SCREEN SHOT No.(09) ADMIN HOME

SIT ,COMPUTER ENGINEERING 2010-11 [PAGE No.64]

SIT ,COMPUTER ENGINEERING 2010-11

[PAGE No.65]

Chapter: 11 LIST OF FIGURES & TABLES

List of Tables

SIT ,COMPUTER ENGINEERING 2010-11

[PAGE No.66]

1. SOFTWARE & HARDWARE SPECIFICATION 2. PROJECT ESTIMATES 3. RISK PRI0RITISATION 4. WORK DISTRIBUTION 5. ROLES & RESPONSIBILITIES 6. TEST SCHEDULE 7. TEST CASES

16 29 31 32 34 48 49

List of Figures & Diagrams 1. RFID TAG 2. 3. 4. RFID WORKING DIAGRAM TYPES OF RFID TAGS RFID ANTEENA INTERNAL LAYOUT 5. TESTING STRATEGY WORKIKG IMPLEMENTATION 6. USE CASE DAIGRAM 7. ACTIVITY DIAGRAM 8. CLASS DIAGRAM 9. SEQUENCE DIAGRAM 10. COMPONENT DUAGRAM 11. DEPLOYMENT DIAGRAM 06 07 08 12 45 36 37 38 39 40 41

SIT ,COMPUTER ENGINEERING 2010-11

[PAGE No.67]

Chapter: 12 REFERENCES

REFERENCES:[1] The Complete Reference C#.NET 2008, Herbert Schildt, Tata McGraw-Hill Edition [2] Black Book of C#.Net TMH- Second Edition
SIT ,COMPUTER ENGINEERING 2010-11 [PAGE No.68]

[3] Professional C# 2008,Nagel,Evjen,Glynn,Watson,Skinner ; WROX-Wiley India Pvt Ltd. [4] Steve Hodges & Mark Harrison, White Paper-Demystifying RFID: Principles & Practicalities, Auto-ID Centre Institute For Manufacturing, University of Cambridge, Mill Lane, Cambridge, United Kingdom, Jan 2004. [5] Klaus Finkenzeller. RFID Handbook : Fundamentals and Applications of RFID, Chichester : John Wiley, Leipzig, Dritte Edition, 2003. . [6] Software Engineering-A practitioners approach by Roger Pressman [7] The Unified Modeling Language User Guide by Grady Booch, James Ram Baugh & Ivar Jacobson [8]S. Sarma, D. Brock, and D. Engels, Radio Frequency Identification and the Electronic Product Code, IEEE Micro, v.21 no 6, p. 50-54, November 2001.

SIT ,COMPUTER ENGINEERING 2010-11

[PAGE No.69]