PROJECT DESCRIPTION
This project involves the development of web-based application to support the “E-Land Handling” newly started and suitable to all over tamilnadu.
This project contains very useful modules to support the operations of buying and selling as well as trading purposes.
By using this project, any property or landholders can register their property information and with photos of all information. After registration the registered information will be displayed in the corresponding pages and it becomes ready to sales.
This web application contains all modules to record the each and every information done towards houses, plots, buildings and agricultural or wet lands and provides facilities to buyers to easily purchase the property or lands over net without manual effort and problems.
ANALYSIS OF THE EXISTING SYSTEM
Internet playing the vital role in all aspect of the human life. So one web-based application is very much essential to carry out the above-mentioned processes in fast manner.
ANALYSIS OF THE PROPOSED SYSTEM
The main objective of the proposed system is developing a new web based applications in order to support all the buying and selling activities of lands in time.
The web based application development for land buying and selling or property buying and selling surely will increase the speed of operations in “Eland Handling”.
Any individual buy or sell their property over Internet without any troubles and problems. The proposed system tested with some sample data college all around Dindigul District But capable to establish all over tamilnadu.
SYSTEM REQUIREMENT
Hardware Requirements
Each computer must have the following minimum configuration. All hardware should be on the Microsoft Windows 2000 Hardware Compatibility List.
Pentium II class processor, 450 megahertz (MHz).
160 MB physical memory, 256 MB recommended.
CD-ROM or DVD drive, 12x or faster recommended.
NOTE A DVD drive is required to install the Visual Studio .NET Professional Evaluation Edition software
gigabytes (GB) on installation drive, which includes 500 megabytes (MB) on system drive.
Super VGA (800 x 600) or higher-resolution monitor with 256 colors.
Microsoft Mouse or compatible pointing device.
Software Requirements
The following software is required to complete the procedures in this course.
Microsoft Windows 2000 or Microsoft Windows XP
Microsoft Visual Studio .NET, Professional Edition, Enterprise Developer Edition, or Enterprise Architect Edition
Microsoft Access 2000 with the Jet 4.0 data engine or Sql.Server 2000
SYSTEM DESIGN
System Design means the translation of analyzed requirements in to ways of meeting them. The design will determine the success of the proposed system. Based on the proposed system objectives of major modules are identified and the operations to be carried out are determinates.
INPUT OUTPUT DESIGN
The input design is the link that ties information system in to the world of its users, input design consists of developing specific procedures for data preparation, steps necessary to put the transaction of data in the form that is usable for computer processing.
This web application system contains the following input form modules and its input entries.
Plots Registration
Registering plot details by seller such as total are in sq. feet or in cent, location of plot with photo.
Houses Registration
Registering house details by seller such as total are in sq. feet or in cent, location of house with photo of house and surrounding area of house.
Lands Registration
Registering lands details by seller such as total Acres or Cents, location of lands and village sketch with photo and surrounding area…
Buildings Registration
Registering Buildings details by seller such as total are in sq. feet or in cent, location of Buildings with photo includes layout approval, Building approval plans.
Plots Listing
Listing of all plots details to buyer such as total are in square feet or in cent, location of plot with photo of layout and other things.
Houses Listing
Listing of all houses details to buyer such as total are in square feet or in cent, location of house with photo and with photos of surrounding area.
Lands Listing
Listing of all lands details to seller such as total are in sq. feet or in cent, location of house with photo and surrounding area…
Buildings Registration
Listing of all buildings details to buyer such as total are in sq. feet or in cent, location of house with photo of buildings and with photos surrounding area…
Buyer Preferences
Module used to specify the buyer's preference about the property such as his need (land, building or house) and preferences such as total are in sq. feet or in cent, location of house with photo and with photos surrounding area
Contact Seller
This module used to buyer to contact seller in buying process
Contact Buyer
This module used to seller to contact buyer in selling process
Remove Entry
This Module used to remove the details of property or land from website after selling it other person or buyer
Contact Organization
This module used to buyer and seller to contact website organization in buying and selling process
TABLE DESIGN
Table Plots
Field
Data Type
Regno
Number
SellerName
Text
PhoneNumber
Text
Location
Text
Village
Text
Panchayat
Text
Town
Text
District
Text
PlotNumber
Number
Square Feet
Number
Layout Fle
Text
Expected Sales Value
Number
Table Houses
Field
Data Type
Regno
Number
Seller Name
Text
Location
Text
Village
Text
Panchayat
Text
Town
Text
District
Text
Phone Number
Text
Square Feet
Number
Plan File
Text
Layout File
Text
View File1
Text
View File2
Text
Sales Value
Number
Table Buildings
Field
Data Type
Regno
Number
Seller Name
Text
Location
Text
Village
Text
Panchayat
Text
Town
Text
District
Text
Phone Number
Text
Square Feet
Number
Plan File
Text
Layout File
Text
View File1
Text
View File2
Text
Sales Value
Number
Table Lands
Field
Data Type
Regno
Number
Seller Name
Text
Location
Text
Village
Text
Panchayat
Text
Town
Text
District
Text
Phone Number
Text
Acre
Number
Land Sketch
Text
Detailed Sketch
Text
Land Description
Text
Sales Value
Text
Table Preferences
Field
Data Type
Name
Text
Customer Need
Text
District
Text
Town
Text
District
Text
Phone Number
Text
Acre
Number
Land Sketch
Text
Detailed Sketch
Text
Land Description
Text
Sales Value
Text
DATA FLOW DIAGRAM
Plot Registration
Houses Registration
Buildings
Registration
Lands
Registration
Plot
Listing
Houses
Listing
Buildings
Listing
Lands
Listing
Centralized
Data Base
Entering into Home Page
Buyer Preferences
Buyer Details
Seller Details
Remove Entry
VISUAL BASIC.NET
The .NET Framework and the Common Language Runtime
The Microsoft .NET Framework is an integrated and managed environment for the development and execution of your code. This lesson is an introduction to the .NET Framework, the philosophy behind it, and how it works.
Overview of the .NET Framework
The .NET Framework is a managed, type-safe environment for application development and execution. The framework manages all aspects of the execution of your program: it allocates memory for the storage of data and instructions, grants or denies the appropriate permissions to your application, initiates and manages application execution, and manages the reallocation of memory for resources that are no longer needed. The .NET Framework consists of two main components: the common language runtime and the .NET Framework class library.
The common language runtime can be thought of as the environment that manages code execution. It provides core services, such as code compilation, memory allocation, thread management, and garbage collection. Through the common type system (CTS), it enforces strict type safety, and it ensures that code is executed in a safe environment by enforcing code access security. The .NET Framework class library provides a collection of useful and reusable types that are designed to integrate with the common language runtime. The types provided by the .NET Framework are object-oriented and fully extensible, and allow you to seamlessly integrate your applications with the .NET Framework.
Languages and the .NET Framework
The .NET Framework is designed for cross-language compatibility. Simply put, this means that .NET components can interact with each other no matter what language they were originally written in. So, an application written in Microsoft Visual Basic .NET might reference a DLL file written in Microsoft C#, which in turn might access a resource written in managed Microsoft C++ or any other .NET language. This language interoperability extends to full object-oriented inheritance. A Visual Basic .NET class might be derived from a C# class, for example, or vice versa.
The Structure of a .NET Application
To understand how the common language run time manages the execution of code, you must examine the structure of a .NET application. The primary unit of a .NET application is the assembly. An assembly is a self-describing collection of code, resources, and metadata. The assembly manifest contains information about what is contained within the assembly. The assembly manifest provides
· Identity information, such as the name and version number of the assembly.
· A list of all types exposed by the assembly.
· A list of other assemblies required by the assembly.
· A list of code access security instructions for the assembly. This includes a list of permissions required by the assembly and permissions to be denied the assembly.
Each assembly has one and only one assembly manifest, and it contains all the description information for the assembly. The assembly manifest can be contained in its own separate file, or it can be contained within one of the assembly's modules. An assembly also contains one or more modules. A module contains the code that makes up your application or library, and metadata that describes that code. When you compile a project into an assembly, your code is converted from high-level code to IL. Because all managed code is first converted to IL code, applications written in different languages can easily interact. For example, one developer might write an application in Visual C# that accesses a DLL in Visual Basic .NET. Both resources will be converted to IL modules before being executed, thus avoiding any language incompatibility issues
The .NET Data Types
The .NET data types are the types you use to store your data. They are value types and can be broken down into subcategories: Integer types, Floating-point types, the Boolean type, and the Char type. Two built-in reference types that are an integral part of your application will also be discussed: the String type and the Object type.
Implementing Properties
Properties are members of classes that expose member variables or objects. Properties have similarities to both fields and methods. Values are set and retrieved using the same syntax as fields: getting a value from a property or setting a value with a property actually calls a specialized method that carries out these functions. Properties can contain code that validates values before setting them or carries out any other function that is required by the application.
Read-Only and Write-Only Properties
Sometimes you will need to implement a property that can return a value to the client but cannot be changed once the class is initialized. Very infrequently, you might need to create a property that can be changed but not read. These properties are called read-only and write-only properties, respectively.
Parameterized Properties
Most of the properties you create will return a single value or object. In Visual Basic .NET, you can create properties that accept parameters when accessed. These properties usually expose a range, or array of values. For example, a single Engine object might have several Cylinders. Rather than expose each one individually, you could create a Cylinder property that returned or set each cylinder based on a supplied parameter.
Object-Oriented Programming in .NET Frame work
Programming in the .NET Framework environment is done with objects. Objects are programmatic constructs that represent packages of related data and functionality. Objects are self-contained and expose specific functionality to the rest of the application environment without detailing the inner workings of the object itself. Objects are created from a template called a class. The .NET base class library provides a set of classes from which you can create objects in your applications. You can also use the Visual Studio programming environment to create your own classes to use in your programs. This lesson will introduce you to the concepts associated with object-oriented programming.
Objects, Members, and Abstraction
An object is a programmatic construct that represents something. In the real world, we think of objects like cars, bicycles, laptop computers, and so on. Each of these items exposes specific functionality and has specific properties. In your application, an object might be a form, a control such as a button, a database connection, or any of a number of other constructs. Each object is a complete functional unit, and contains all of the data and exposes all of the functionality required to fulfill its purpose. The ability of programmatic objects to represent real-world objects is called abstraction.
Classes Are Templates for Objects
Classes were discussed in Chapter 1 and represent user-defined reference types. Classes can be thought of as blueprints for objects. They define all of the members of an object, define the behavior of an object, and set initial values for data when appropriate. When a class is instantiated, an in-memory instance of that class is created.
Overview Of ADO.NET
Most applications require some kind of data access. Desktop applications need to integrate with central databases, Extensible Markup Language (XML) data stores, or local desktop databases. ADO.NET data access technology allows simple, powerful data access while maximizing system resource usage.
Disconnected Database Access
Previous versions of data access technologies have provided continuously connected data access by default. In such a model, an application creates a connection to a database and keeps it open for the life of the application or at least for the amount of time that data is required. As applications become more complex and databases begin to serve more and more clients, a connected data access technology becomes impractical for a variety of reasons.
ADO.NET Data Architecture
Data access in ADO.NET relies on two components: the DataSet, which stores data on the local machine, and the Data Provider, which mediates interaction between the program and the database.
The DataSet
The DataSet is a disconnected, in-memory representation of data. It can be thought of as a local copy of the relevant portions of the database. Data can be loaded into a DataSet from any valid data source, such as a Microsoft SQL Server database, a Microsoft Access database, or an XML file. The DataSet is persisted in memory, and the data therein can be manipulated and updated independent of the database. When appropriate, the DataSet can then act as a template for updating the central database.
The Data Provider
The link to the database is created and maintained by the Data Provider. A Data Provider is not actually a single component, but a set of related components that work together to provide data in an efficient, performance-driven manner. The Microsoft .NET Framework currently ships with two data providers: the SQL Server .NET Data Provider, which is designed specifically to work with Microsoft SQL Server 7.0 or later, and the OleDb .NET Data Provider, which connects with other types of databases. Each Data Provider consists of similar versions of the following generic component classes:
The Connection object provides the connection to the database.
The Command object is used to execute a command against a data source. It can execute either non-query commands, such as INSERT, UPDATE, or DELETE, or return a DataReader with the results of a SELECT command.
The DataReader object provides a forward-only, read-only, connected recordset.
The DataAdapter object populates a disconnected DataSet or DataTable with data and performs updates.
No comments:
Post a Comment