Transport Automation System
1.1 COMPANY PROFILE
Excel Technologies was established in the year 1998. It was formerly known as Lucent Consultancy Services, is an information technology centre in the field of Software Training, Technology Resourcing and Knowledge Consulting. It provides solutions through application of proven platforms and adaptation of emerging technologies. Core to its offering is a solution through well documented software engineering practices, project management mile stones and quality assurance parameters for each stage of software training and development lifecycles.
Excel Technologies. Is a committed
venture of I.T. services, by a team of dedicated professionals having distinct
experience in technical, management & functional domain both in domestic
and international business. Their long association with the industry has
equipped them with proven proficiency to lead the venture to its aspired goals.
The entire business process has been chalked out, by combining the strengths of
proven and potential technologies and experience of leading professionals of
the industry and consulting services. Utilization of resources is pledged to a
systematic and properly channeled business activity to ensure long-term
business development.
The aim of this project is to design, develop and
implement an on-line commercial application software package for "Transport Automation System".
Using Microsoft Visual Basic Technologies.
In
The
proposed software package includes various modules for :
Types of Driving Licenses in
•
Learner Driving License:
This is a
temporary license that is valid up to 6 months from the date of issue. It is basically issued to
learn driving of Motor Vehicles.
•
Permanent Driving License:
Permanent driving license is issued to those who become eligible for it after
thirty days (to apply within 180 days) from the date of issue of the learner
license. Person suppose to get permanent driving license should be conversant
about the vehicle systems, driving, traffic rules & regulations.
•
Duplicate Driving License:
In case of loss or theft, Duplicate License is issued.
The documents to be produced are FIR of the lost license,
challan clearance report from RTO Office and an application in Form LLR. The particulars are verified by the authority from the records. The duplicate license will have the valid period same as the previous license. If he license is lost and expired by more than 6 months it requires permission from Head Quarter of Transport Department
•
International Driving License:
The motor licensing authority also issues International Driving
License. The validity of this license is for one year. Apart from address proof and birth certificate, one has to produce a valid passport and valid visa while applying.
•
Motorcycle License or Two-wheeler License:
Two-wheeler license is issued by the Regional Transport Authority (RTO) to permit driving of only two-wheeler vehicles like bike, scooter and moped.
•
Light Motor Vehicle License (LMV):
Light Motor Vehicle License is issued to drive light vehicles like auto rickshaws, motor car, jeep, taxi, three-wheeler delivery vans, etc.
•
Heavy Motor Vehicle License (HMV):
Heavy Motor Vehicle License is issued to drive heavy vehicles like trucks, buses, tourist coaches, cranes, goods carriages, etc. A person with HMV license can drive light vehicles but Light Motor Vehicle License do not permit to drive heavy vehicles.
MODULES
•
Learners License :
The Learners License Module
basically holds details of the student for Learners Licence. This is a
temporary license that is valid up to 6 months from the date of issue. It is basically issued to learn driving of
Motor Vehicles.
•
License Issue :
This module basically stores
information of License Issue. The trainee who has completed 1 month training on
a vehicle can apply for License Issue within 6 months.
•
License
Renewal :
This Module maintains details about License Renewal. A person can apply for Licence Renewal only if the License is expired.
•
Accounts Information :
The Module basically holds
details of the accounts transaction, accounts holders name, bank, type of
account.
.
•
Interactive Reports :
This
module basically holds interactive reports.
2. SYSTEM
ANALYSIS
2.1 EXISTING SYSTEM
1)
Data Redundancy
2)
No Data Security
3)
No Sharing of Data
4)
Manual Work human effort
5)
Time
consuming
6)
Tedious
[difficult]
7)
Space requirement is more.
8)
Possibility
of information duplication
9)
One person
can access data at the same time
10)
Repetition of data
11) Requires
significant human thought and skill to be effective.
12) Accountability
for the process becomes muddled.
2.2 PROPOSED
SYSTEM
1. Faster and efficient in processing of information.
2.
Automatic generation of driving license.
3.
With the larger reductions in the cost of
hardware and software and availability
of user-friendly vehicle software package.
4.
More timely information can be
produced.
5.
No more manual processing of the
data-all automatically posted to the various ledgers / accounts and
6.
Many types of useful reports can be
generated for management to make decisions.
7.
Automated Process and data sharing.
2.3
Feasibility Analysis
The main objective of the
feasibility study is to test operational technical and economic feasibility of
the proposed system investigating existing system does this is a stage where
everyone will test the feasibility of the proposed system. The feasibility
assessment stage contains following factors to access.
TECHNICAL FEASIBILITY
Evaluating the technical feasibility is the tackiest part of a feasibility study. This is because at this point in time, not too many detailed designing of the system are present, making it difficult to access issues like performance, costs on (o n account of the kind of technology to be deployed ) etc. a number of issues have to be considered while doing a technical analysis .
Understand the different technologies
involved in the proposed:
Before commencing the project, we have to be very clear about what are the technologies that a4re to be required for the development of the new system. Find out whether the organization currently possesses the required technologies: Is the required technology available with the organization?
If so is the capacity sufficient?
OPERATIONAL FEASIBILITY
Proposed projects are beneficial only if they can be turned into information systems that will meet the organizations operating requirements. Simply stated, this test of feasibility asks if the system will work when it is developed and installed. Are there major barrowers to implementation? Here are questions that will help test the operational feasibility of a project:
Is this sufficient support for the project from management form users? If the current systemic well liked and used to the extent that persons will not be able to see reasons for change, there may be resistance.
Are the current business methods acceptable to the user? If they are not. Users may welcome a change that will bring about a more operation and useful systems.
Have the user been involved in the planning and development of the project? Early involvement reduces the chances of resistance to the system and in general and increases the likelihood of successful project.
ECONOMIC FEASIBILITY
Economic feasibility attempts two ways the costs of developing and implementing a new system, against the benefit that would accrue from giving the new system in place. This feasibility study gives the top management the economic justification for the new system. The project is not using any additional soft ware and there is no training required to operate the project so it is costing saving.
A simple economic analysis which gives the actual comparison of costs and benefits are much more meaningful in the case. In addition this proves to be a useful point of reference to compare actual costs as the project progress could be a various types of intangible benefits an account of automation. There could include increase customer satisfaction improvement in product quality better decision making, time lines of information expedition activities improved accuracy of operations better documentation and record keeping faster retrieval of information better employee morale.
3. SYSTEM IMPLEMENTATION
5.1 SOFTWARE DESCRIPTION
a) MICROSOFT VISUAL
BASIC.NET
Why VB.NET?
Introduction
Visual Basic... A name everybody knows for a rich, easy and
GUI based programming language, making each & every task easier and
improves programmer's productivity. VB has won the best RAD ( Rapid Application
Development ) Tool award for three times and still keeping itself at top.
Microsoft first started
Visual Basic in early 1990s and the project name was "Thunder". After
the launch of VB 5.0, it crosses all the boundaries and won the best RAD Tool
award by beating PowerBuilder in 1998. VB 5.0 came out with some great
enhancements but definitely this time VB.NET has come with revolutionary
changes to make it suitable for next generation of application development.
"Since Visual Basic's
inception, its community has grown to more than 3 million professional
developers worldwide. In fact, about half the world's developers now use Visual
Basic. The increasing power and richness of the PC provided the backbone for
this amazing growth."
Certainly this seems to be an
amazing thing to talk about these details in the world of Internet Programming
and when we know that Java has already taken place of most popular Internet
programming language, but this is hard truth. The only feature lacking in VB
was its Internet capabilities and when we are moving towards the third
generation of the Internet, it becomes important to have strong Internet
Programming capabilities for any programming language. The industry is focusing
on critical distributed computing with web services capabilities. At this
moment VB.NET is definitely a powerful tool to provide all these solutions in
integrated environment of .NET technology. Let us discuss the major problems
with VB 6.0, which has been creating troubles for VB developers for a long
time.
Problems with VB
6.0 are:
1. No capabilities for multithreading.
2. Lack of implementation inheritance and other object oriented features.
3. Poor error
handling capabilities.
4. Poor integration with other languages such as C++.
5. No effective user interface for Internet based applications.
In VB.NET all
these shortcomings have been eliminated.
Visual Basic .NET is a
major component of Microsoft Visual Studio .NET suite. The .NET version of
Visual Basic is a new improved version with more features and additions. After
these new additions, VB
qualify to become a full object-oriented language such as C++.
What
is VB.NET ?
VB.NET is the following
version of VB 6.0. Microsoft .NET is a new programming and operating framework
introduced by Microsoft. All .NET supported languages access a common .NET
library to develop applications and share common tools to execute applications.
Programming with Visual Basic using .NET is called VB.NET.
VB.NET, the following
version of VB 6.0 is an improved, stable, and full Object Oriented language. If
you remember, in VB 6.0 wasn’t a true object-oriented language because there
was no support for inheritance, overloading, and interfaces. VB.NET supports
inheritance, overloading, and interfaces. Multithreading and Exception handling
was two major weeks areas of VB 6.0. In VB.NET, you can develop multithreaded
applications as you do in C++ and C# and it also supports structured exception
handling.
Object Oriented
Programming language. Support of inheritance, overloading, interfaces, shared
members and constructors supports all CLS i.e. Common Language Runtime features
such as accessing and working with .NET classes, interaction with other .NET
languages, meta data support, common data types, and
delegates. Multithreading support. Structured exception
handling.
VB.NET: A Full
Object Oriented Language
Abstraction, Encapsulation, Polymorphism, and Inheritance are four basic
properties of an object-oriented language. VB 6.0 supports all of these
properties but Inheritance. Now VB.NET supports Inheritance. This brings VB.NET
in object-oriented languages category such as C++.
Inheritance
Inheritance is one of the most used techniques in an object-oriented language.
Inheritance provides you to reuse your work. Inheritance provides ability to
use existing classes functionality via it’s derived (inherited) class. VB.NET
supports inheritance, which wasn’t supported in VB 6.0 and it’s previous
versions. The good thing about inheritance is, you can use any classes either
developed by you or somebody else, derive your classes from those classes, and
use their class’s functionality via your classes.
Multithreading
Creating free-threaded applications was one of the lacking area of VB language.
In .NET framework, all languages share Common Runtime Library. That means you
can develop same applications using VB.NET as you can do with C# or other
.NET languages.
The System. Threading
namespace defines the threading classes. So we need to import System. Threading
name space before using any threading classes.
The System Threading Thread class represents a Thread object. You can create or
kill threads using the Thread class.
Structured
Exception Handling
Exception handling is
also called error handling. As a VB programmer, you must be familiar with On
Error Goto and On Error Resume Next statements we used to handler errors in VB
6.0. This exception handling in VB is called Unstructured Exception Handling.
In VB.NET, Microsoft introduces Structured Error Handling controls. Vb.NET
supports C++ like Try..Catch..Finally control.
Variable
Declarations Changes
In VB 6.0, there were
many limitations in variable declarations. One of them was can’t declare more
than one variables in same line. If you did, you had to define data type for
each variable or it defaults to Variant data type.
Dim a1, a2 As Integer
Dim a3 As Integer, a4 As
Integer
In first line, a1 is a variant type and a2 is an integer data type. In second
line, both variables are of type integer.
VB.NET supports multiple variable declarations in the same line. For
example,
Dim a1, a2, a3 As Integer
Variable initialization
was another problem. You can’t initialize variable in the same like it is
declared. VB.NET support this and now you can initialize variables as you do in
C++ or Java.
Dim name As
String = "Mahesh"
System.Console.Write(name)
Declaring Constants is straight forward.
Const DT_COUNT As Integer = 23
Arrays
There have been
significant changes in arrays in VB.NET.
Array Bounds. In VB.NET, first change you�ll
notice is array bound. In VB 6.0, default lower bound of an array is 0. At 0
lower bound, the number of elements in the array is equal to the upper bound
plus one. This statement has 11 elements in the array from A[0] ..A[10]
Dim A(10) As
Single
You use Option Base to change the lower bound of array to 1.
In VB.NET, Arrays are like C++, the lower bound of every array dimension is 0.
Option Base is not supported.
Arithmetic
Operators
VB.NET now supports C++ like shortcut operators. The following table shows tow
of them. You can use same shortcuts for any operator such as *, /, |, and
&.
Operation
Syntax Shortcut
Addition A = A+5 A
+=5
Subtraction A = A - 5 A -+ 5
Changes
in Control Flow Statements
There are following changes in the control flow statements in VB.NET.
1. GoSub is not supported.
2. Call, Function, and Sub statements can be used to call prodecures.
3. In VB.NET, On ... GoSub and On ... GoTo statements are not supported. You
can Select Case statement.
4. The While ... Wend statement has updated While - End While statement. Wend
keyword is not supported.
Some new
features of VB.NET
1. Full support for object oriented programming.
2. Structured error handling capabilities.
3. Access to .NET Framework.
4. Powerful unified Integrated Development Environment (IDE).
5. Inherent support for XML & Web Services.
6. Better windows applications with Windows Forms.
7. New Console capabilities of VB.NET.
8. New Web capabilities with Web Forms.
9. Immense power of tools & controls (including Server Controls).
10. Interoperatibility with other .NET complined languages.
11. Better database programming approach with ADO.NET.
... and many
more. The list is very long. Now we have to figure out that how important role
VB will play in future? The answer is there in the words of Bill Gates
once again -
"The
next 10 years will be an amazing time for software developers. The advancements
in the way we develop, deploy, and use applications will be as profound as the
architectural shift from DOS- to Windows-based programming. Visual Basic.NET
will provide the foundation for building the solutions that enable a new age of
truly distributed computing on the Internet.
Let us see how to write
simplest console based Hello World application in VB.NET.
This program
writes an output on the console saying Hello VB.NET World. The program looks
like Listing 1.1.
Listing 1.1: Hello VB.NET World Sample.
Imports System
Module Module1
Sub
Console.WriteLine("Hello
VB.NET World!")
End Sub
End Module
Key Changes in
VB.NET for VB 6.0 Developer
key changes
requiring redesign under VB.Net
compared to VB 6.0.
Using the .NET
Framework, Microsoft Visual Basic developers can build robust applications that
were very difficult to write in previous versions of Visual Basic.
First, VB.NET includes
a host of new features that enable developers to maximize their productivity.
In addition to a new unified IDE (integrated development environment), VB
developers can take
advantage of the new Server Explorer to easily integrate server-side components
into their apps, the shared Task List to help organize code, Dynamic Help for
instant access to pertinent information, and Macros to customize, extend, and
integrate the Visual Studio environment.
1. Add-In Model has Changed
2. Date and Time are renamed
In
VB.Net the Today function replaces the old Date function and TimeOfDay replaces
the Time function. The main difference between VB.Net and earlier versions is
that Date/Time values used to be stored as double-precision values and could be
manipulated directly. In VB.Net the internal format for dates and times has
been changed and is not directly accessible.
3. File I/O statements have changed
4. Controls have been redesigned with many
properties/methods removed
or
renamed.
5. DAO/RDO Data binding is not supported by the
new controls
Data
binding is directly supported by the VB.Net controls using
6.
Parameters are passed By Val by default.
7. Control Arrays are gone.
8. Fixed length strings are gone.
9. Gosub, On/Gosub, On/Goto are gone.
10. Names with leading underscores are not hidden.
11 .Null
is now DBNull.
12. Property syntax has changed.
13. No
more SET and limited default properties.
14. Static procedures are not supported.
15. Types are now Structures and LSET is gone.
16. Variant, Empty, Null, Missing, IsNull and IsMissing are missing.
17. WebClasses, ActiveX Documents and DHTML projects are now WebForms/ASP+.
18. While/Wend is now While/End While.
19. No more windowless controls.
20. API Calls need updating.
21. DIM As New is different.
22. Arrays are always base Zero.
23. VB.Net is not based on COM.
24. Integer and Long are redefined.
25. MsgBox defaults are different.
26. Currency data type is gone.
b) MICROSOFT SQL SERVER 2005
Microsoft
SQL Server 2005 is a comprehensive, integrated data management and analysis
software that enables organizations to reliably manage mission-critical
information and confidently run today’s increasingly complex business
applications. SQL Server 2005 allows companies to gain greater insight from
their business information and achieve faster results for a competitive
advantage.
SQL Server 2005 is the Data Platform leader:
- Microsoft is positioned in Leaders
Quadrant for Magic Quadrant for Data Warehouse Database Management
Systems, 2007
- SQL Server is the fastest growing Database
and Business Intelligence vendor
- SQL Server ships more units than Oracle
and IBM combined
- SQL Server is the #1 OLAP Server on the
market
- SQL Server is more secure than Oracle.
Since July 2003 more than 100 critical Oracle database security
vulnerabilities have been identified, compared to ZERO for SQL Server for
that period.
- SQL Server is best in price/performance
for TPC-H 1TB & 3TB (non-clustered).
- Microsoft SQL Server and Unisys are the
first to publish TPC-E benchmark results.
- Gartner 2006 worldwide RDBMS market share
reports highest growth rate in market share for Microsoft SQL Server. With
28% growth in market share, growth is almost twice the nearest competitor
at 14.8% growth.
- SQL Server still number 1 in databases.
74.7 percent of enterprises are using SQL Server, while 54.5 percent are
using Oracle databases.
Microsoft
SQL Server is a relational database management system (RDBMS) produced by
Microsoft. Its primary query language is Transact-SQL, an implementation of the
ANSI/ISO standard Structured Query Language (SQL) used by both Microsoft and
Sybase.
The
architecture of SQL Server : The architecture of Microsoft SQL Server is
broadly divided into three components:
- SQL Server Manages the World's Largest
Databases.
- Microsoft SQL Server recognized as Best
Seller and Top Growth Best Seller by CRN Magazine.
- SQLOS which implements the basic services
required by SQL Server, including thread scheduling, memory management and
I/O management
- Relational Engine, which implements the
relational database components including support for databases, tables,
queries and stored procedures as well as implementing the type system
- Protocol Layer which exposes the SQL Server
functionality.[1]
- Data storage The main unit of data storage
is a database, which is a collection of tables with typed columns. SQL
Server supports different data types, including primary types such as
Integer, Float, Decimal, Char (including character strings), Varchar
(variable length character strings), binary (for unstructured binary blob
of data), Text (for textual data) among others.
Microsoft
SQL Server is a relational database management system (RDBMS) produced by
Microsoft. Its primary query language is Transact-SQL, an implementation of the
ANSI/ISO standard Structured Query Language (SQL) used by both Microsoft and
Sybase.
ARCHITECTURE
The architecture of SQL
Server
The
architecture of Microsoft SQL Server is broadly divided into three components:
SQLOS which implements the basic services required by SQL Server, including
thread scheduling, memory management and I/O management; the Relational Engine,
which implements the relational database components including support for
databases, tables, queries and stored procedures as well as implementing the
type system; and the Protocol Layer which exposes the SQL Server functionality.
SQLOS
SQLOS
is the base component in the SQL Server architecture. It implements functions
normally associated with the Operating System - thread scheduling, memory
management, I/O management, buffer pool management, resource management,
synchronization primitives and locking, and deadlock detection. Because the
requirement of SQL Server is highly specialized,[1] SQL Server implements its
own memory and thread management system, rather than using the generic one
already implemented in the Operating System. It divides all the operations it
performs into a series of Tasks - both background maintenance jobs as well as
processing requests from clients.
Internally,
a pool of worker threads is maintained, onto which the tasks are scheduled. A
task is associated with the thread till it is completed, only after its
completion is the thread freed and returned to the pool. If there are no free
threads to assign the task to, the task is temporarily blocked. Each worker
thread is mapped onto either an Operating System thread or a fiber, which are
user mode threads, which is used to implement co-operative multitasking. Using
the latter, even though all the book-keeping jobs of thread management has to
be implemented in SQLOS (in addition to the native OS implementation), it can
optimize for the particular use. SQLOS also includes synchronization primitives
for locking as well as monitoring for the worker threads to detect if they have
entangled themselves into a deadlock and takes necessary measures to recover
from the situation.
SQLOS
handles the memory requirements of SQL Server as well. Reducing disc I/O is one
of the primary goals of specialized memory management in SQL Server. As such,
it maintains a buffer pool, handled by SQLOS, which is used to cache data pages
from the disc as well as to satisfy the memory requirements for other
components, including query processor, and other internal data structures.[1]
SQLOS also has to take care that the memory allocated is used efficiently, as
such it monitors all the memory allocated from the buffer pool, ensuring that
the components return unused memory to the pool, as well as shuffling data in
and out of the cache to make room for newer data. For changes that are made to
the data in buffer, SQLOS writes the data back to the disc lazily, that is when
the disc subsystem is either free, or there have significant number changes
made to the cache, while still serving requests from the cache. For this, it
implements a Lazy Writer, which handles the task of writing the data back to
persistent storage.
SQL
Server normally supports up to 2 GB memory on x86 hardware, though it can be
configured to use up to 64 GB if Address Windowing Extension is used on
supporting OS. For x64 hardware, it supports 8 TB of memory, and 7 TB for IA-64
systems. However, when running x86 versions of SQL Server on x64 hardware, it
can access 4 GB of memory without any special configuration.
Relational engine
The
Relational engine is the component, which implements the relational data store,
using the capabilities provided by SQLOS, which is exposed to this layer via
the private SQLOS API. It implements the type system, to define the types of
the data that can be stored in the tables, as well as the different types of
data items (such as tables, indexes, logs etc) that can be stored. It includes
the Storage Engine, which handles the way data is stored on persistent storage
devices, as well as implement methods for fast access to the data. The storage
engine implements log-based transaction so as to ensure that any changes to the
data are ACID compliant. It also includes the query processor, which is the
component that allows data to be retrieved. The specification of what
needs
to be retrieved is provided in the form of a SQL query, which it optimizes and
translates into the sequence of operations needed to retrieve the data. The
operations are then scheduled on to the worker threads, which are scheduled for
execution by SQLOS.[1]
Protocol layer
Protocol
layer implements the external interface to SQL Server. All operations that can
be invoked on SQL Server are communicated to it via a Microsoft-defined format,
called Tabular Data Stream (TDS). TDS packets can be encased in other physical
transport dependent protocols, including TCP/IP, Named pipes, and Shared
memory. Consequently, access to SQL Server is available over these protocols.
In addition, the SQL Server API is also exposed over web services.
Data storage
The
main unit of data storage is a database, which is a collection of tables with
typed columns. SQL Server supports different data types, including primary
types such as Integer, Float, Decimal, Char (including character strings),
Varchar (variable length character strings), binary (for unstructured binary
blob of data), Text (for textual data) among others. It also allows
user-defined composite types (UDTs) to be defined and used. SQL Server also
makes server statistics available as virtual tables and views (called Dynamic
Management Views or DMVs). A database can also contain other objects including
views, stored procedures, indexes and constraints, in addition to
tables,
along with a transaction log. An SQL Server database can contain a maximum of
231 objects, and can span multiple OS-level files with a maximum file size of
220 TB.[1] The data in the database are stored in primary data files with an extension
.mdf. Secondary data files, identified with an .ndf extension, are used to
store optional metadata. Log files are identified with the .ldf extension.[1]
Storage
space allocated to a database is divided into sequentially numbered pages, each
8 KB in size. A page is the basic unit of I/O for SQL Server operations. A page
is marked with a 96-byte header which stores metadata about the page including
the page number, page type, free space on
the
page and the ID of the object that owns it. Page type defines the data
contained in the page - data stored in the database, index, allocation map
which holds information about how pages are allocated to tables and indexes,
change map which holds information about the changes made to
other
pages since last backup or logging, or contain large data types such as image
or text. While page is the basic unit of an I/O operation, space is actually
managed in terms of an extent which consists of 8 pages. A database object can
either span all 8 pages in an extent ("uniform extent") or share an
extent with up to 7 more objects ("mixed extent"). A row in a
database table cannot span more than one page, so is limited to 8 KB in size.
However, if the data exceeds 8 KB and the row contains Varchar or Varbinary
data, the data in those columns are moved to a new page (or possible a sequence
of pages, called Allocation unit) and replaced with a pointer to the data.
For
physical storage of a table, its rows are divided into a series of partitions
(numbered 1 to n). The partition size is user defined; by default all rows are
in a single partition. A table is split into multiple partitions in order to
spread a database over a cluster. Rows in each partition are stored in either
B-tree or heap structure. If the table has an associated index to allow fast
retrieval of rows, the rows are stored in-order according to their index
values, with a B-tree providing the index. The data is in the leaf node of the
leaves, and other nodes storing the index values for the leaf data
reachable
from the respective nodes. If the index is non-clustered, the rows are not
sorted according to the index keys. An indexed view has the same storage
structure as an indexed table. A table without an index is stored in an
unordered heap structure. Both heaps and B-trees can span multiple allocation
units.
COMPETITIVE FEATURES
- Enhanced enterprise data management
- Security
- Business continuance.
- Manageability
- Advanced business intelligence
- Developer productivity
Enhanced enterprise data
management
SQL Server 2005 is ready for
the enterprise, offering exceptional data availability and manageability,
hardened security, and the ability to scale from handheld mobile devices to the
most demanding online transaction
processing (OLTP) systems and multi-terabyte data warehouses. This
release enhances DBA productivity by automating routine tasks and letting
administrators focus on high value activities. SQL Server 2005 also provides an
extensible framework for proactive health and performance monitoring. Here’s a
look at SQL Server 2005’s enterprise data-management features.
SQL Server 2005
boasts impressive component-level performance, from the relational engine to
business intelligence. The relational engine handles demanding OLTP workloads and multi-terabyte
data warehouses. SQL Server 2005 Integration Services (SSIS) is designed to
move millions of rows per second while performing in-memory transformations
with delivery to multiple destinations. Analysis Services offers unified access
to information, and is designed to provide subsecond query times, advanced
caching, and data mining with predictions for very large data sets.
SECURITY
Microsoft set a standard for security with its Trustworthy Computing initiative, which is designed to ensure a safe and reliable computing experience. SQL Server 2005 helps deliver on this from the design of the product through its final deployment: secure by design, secure by default, and secure in deployment. By default, SQL Server 2005 helps maximize security with a minimal surface area. A dedicated security-configuration interface called the Surface Area Configuration (SAC) consolidates access to configurable services and settings and gives you brief configuration descriptions to help you make informed decisions. SQL Server 2005 introduces fine-grain administration rights, which let you grant levels of development and administrative rights decoupled from the levels of data access rights in each platform subcomponent. SQL Server 2005 also gives you enhanced control over grantable permissions, password policy enforcement, and high levels of data encryption for storage and transmission. A secure evelopment environment also lets developers easily sign, verify, and manage code—including Common Language Runtime (CLR) assemblies that run in the database—and managed code uses Code Access Security (CAS) to prevent assemblies from performing certain operations, protecting the OS or database server from compromise
Business continuance.
For mission-critical applications, SQL Server 2005
enables 24/7 data availability, providing end users with consistent access to
information. Failover clustering and database mirroring technologies let you
deliver highly reliable, available applications to your employees, customers,
and partners with minimal downtime (see Figure 2). Features such as online
indexing, piecemeal backup and restore, partitioning, dynamic configuration,
and support for hot memory swapping minimize and help eliminate downtime,
enabling uninterrupted user access to enterprise data—even during disaster
recovery operations. SSIS offers distributed deployment and restartability,
promoting resilient (ETL) processes.
Manageability.
SQL Server 2005 gives you a single, unified management tool—SQL Server Management Studio—that lets you manage the SQL Server platform from one interface (see Figure 3). This integration boosts DBA productivity across the SQL Server implementations in your enterprise. The release also lets you easily identify, troubleshoot, and resolve performance problems. SQL Server Profiler benefits from enhanced trace capabilities that encompass core products in SQL Server, including SQL Server Database Services, Analysis Services, and project teams—to rapidly deliver robust enterprise database applications. Here’s how SQL Server 2005 helps your development team reduce time to market and collaborate to produce enhanced solutions.
Advanced business
intelligence
SQL Server 2005 provides
components and tools to help implement a comprehensive, end-to-end business
intelligence solution— whatever your analysis and reporting needs are. And
implementing the release’s entire integrated business intelligence feature set
can magnify the benefits enabled by a SQL Server 2005 upgrade.
Developer productivity
A SQL Server 2005 upgrade also presents a great opportunity to migrate applications to SQL Server. Features such as snapshot-related connection contexts, Read Committed Snapshot Isolation, and Snapshot Isolation let many Oracle-hosted applications behave on SQL Server 2005 just as they do on Oracle platforms. Impressive enhancements to the T-SQL query language accelerate SQL Server’s competitive lead. T-SQL now includes constructs such as EXCEPT and INTERSECT, PIVOT and UNPIVOT, RANK, and TOP N Sort in addition to common table expressions (CTEs), which enable advanced recursive queries. And the release adds error-handling capabilities with TRY…CATCH statements. You can also use Data Definition Language (DDL) triggers, a special kind of trigger that fires in response to DDL statements, to perform administrative tasks in the database, such as auditing and regulating database operations. Compared to previous SQL Server releases, SQL Server 2005 features a simplified licensing model (per processor or per server with client access licenses) for every feature a specific software edition offers. This enables SQL Server 2005 to play a central role in an organization where you can extend the value of an initial licensing investment by using additional features of the comprehensive platform at no incremental cost. For example, you can expand a SQL Server 2005 data-storage platform upgrade to also offer management, replication, analysis, and reporting functionality.
In addition, SQL Server 2005 can be an excellent solution for small and medium businesses. Microsoft has responded to the needs of small businesses with the introduction of two entry-level licensing options: the freely distributable SQL Server 2005 Express and the cost-effective SQL Server 2005 Workgroup Edition. Designed to scale from the large enterprises down to small business, SQL Server 2005 enables the same level of performance, security, reliability, and business value to all customers. Prepare to realize the benefits of upgrading to SQL Server 2005, which provides an enterprise data-management platform with advanced business intelligence functionality and impressive developer and administrator productivity features. Start digging into SQL Server 2005’s advantages today and begin your upgrade planning so that your DBAs, developers, and entire organization can reap the benefits that SQL Server 2005 brings.
Developer productivity
SQL Server 2005’s many development features and a comprehensive enterprise tool set empowers developers—whether on small or large multiple platforms, applications, and programming languages. Support for existing and emerging open standards such as HTTP, XML, Simple Object Access Protocol (SOAP), XQuery, and XML Schema Definition (XSD) facilitates communications across your extended enterprise systems. Native XML support in SQL Server 2005 runs deep: You will find XML storage in a dedicated XML data type that has its own index type, strong query capabilities via XQuery and XPath, and the ability to create XML code from relational data by using the XSD language.
5.2 CODING
Public Class Form5
Dim cn As New ADODB.Connection
Dim rs As New ADODB.Recordset
Private Sub
Form5_KeyDown(ByVal sender As Object, ByVal e As
System.Windows.Forms.KeyEventArgs) Handles Me.KeyDown
If e.KeyCode = Keys.Enter Then
SendKeys.Send("{tab}")
End If
End Sub
Private Sub
Form5_Load(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles
MyBase.Load
cn.ConnectionString = "Provider=SQLNCLI;integrated
security =SSPI;persist security info=false;initial catalog=Trans;user
id=sa;password=chetanp;data source=master"
cn.Open()
End Sub
Private Sub
cmdsave_Click(ByVal sender As System.Object, ByVal
e As System.EventArgs) Handles
cmdsave.Click
Dim res
res = MessageBox.Show("Do you want to
save this record?", "Alert",
MessageBoxButtons.YesNo, MessageBoxIcon.Question)
If res = vbYes Then
cn.Execute("insert into detail values(
" & t1.Text & ",'"
& t2.Text & "','" &
t3.Text & "','" & t4.Text
& "' )")
MessageBox.Show("Record saved
successfully.", "Alert",
MessageBoxButtons.OK, MessageBoxIcon.Information)
End If
End Sub
Private Sub
cmdclear_Click(ByVal sender As System.Object, ByVal
e As System.EventArgs) Handles
cmdclear.Click
Call clear()
End Sub
Sub clear()
t1.Clear()
t2.Clear()
t3.Clear()
t4.Clear()
t1.Focus()
End Sub
Private Sub
cmdfind_Click(ByVal sender As System.Object, ByVal
e As System.EventArgs) Handles
cmdfind.Click
Dim a As Integer
a
= InputBox("Enter slno : ", "Response", 0)
If rs.State Then
rs.Close()
End If
rs.Open("select * from detail where slno
=" & a & "",
cn, ADODB.CursorTypeEnum.adOpenStatic, ADODB.LockTypeEnum.adLockOptimistic)
If rs.RecordCount > 0 Then
t1.Text = rs.Fields(0).Value
t2.Text = rs.Fields(1).Value
t3.Text = rs.Fields(2).Value
t4.Text = rs.Fields(3).Value
Else
MessageBox.Show("Record not
found...", "Alert",
MessageBoxButtons.OK, MessageBoxIcon.Error)
End If
End Sub
Private Sub
cmdmodify_Click(ByVal sender As System.Object, ByVal
e As System.EventArgs) Handles
cmdmodify.Click
Dim res
res = MessageBox.Show("Do you want to
modify this record?", "Alert",
MessageBoxButtons.YesNo, MessageBoxIcon.Information)
If res = vbYes Then
cn.Execute("update detail set dat=
'" & t2.Text & "',narration='"
& t3.Text & "',amount='"
& t4.Text & "' where slno="
& t1.Text & "")
MessageBox.Show("Record modified
successfully.", "Alert",
MessageBoxButtons.OK, MessageBoxIcon.Information)
Call
clear()
End If
End Sub
Private Sub
cmddelete_Click(ByVal sender As System.Object, ByVal
e As System.EventArgs) Handles
cmddelete.Click
Dim res
res = MessageBox.Show("Do you want to
delete this record?", "Alert",
MessageBoxButtons.YesNo, MessageBoxIcon.Information)
If res = vbYes Then
cn.Execute("delete from detail where
slno=" & t1.Text & "")
MessageBox.Show("Record deleted
successfully.", "Alert",
MessageBoxButtons.OK, MessageBoxIcon.Information)
Call clear()
End If
End Sub
Private Sub
cmdexit_Click(ByVal sender As System.Object, ByVal
e As System.EventArgs) Handles
cmdexit.Click
Application.Exit()
End Sub
Private Sub
t1_KeyPress(ByVal sender As Object, ByVal e As
System.Windows.Forms.KeyPressEventArgs) Handles
t1.KeyPress
e.Handled = trapkey(Asc(e.KeyChar))
End Sub
Private Sub
t3_KeyPress(ByVal sender As Object, ByVal e As
System.Windows.Forms.KeyPressEventArgs) Handles
t3.KeyPress
e.Handled = Trapkey1(Asc(e.KeyChar))
If e.KeyChar = Chr(13) Then
t3.Text = StrConv(t3.Text, VbStrConv.ProperCase)
End If
End Sub
End Class
Implementation:
Implementation Planning. System implementation is a process of making newly designed system fully operational. The system is implemented after careful testing.
The following steps have been followed in he implementation of this system.
- System conversion.
- User training.
Implementation Planning:
A logical starting point for this type of planning involves knowledge of the following areas.
- Personal needs.
- Programming equipments selected.
- Physical requirements.
- Conversion activities.
Initially a primary implementation plan is prepared to schedule & manage many different activities that must be completed for a successful system implementation.
A complete implementation plan includes the following items:
- System training plan.
- System test plan.
- System conversion plan.
- Overall implementation plan.
l System
Conversion:
The system implementation could be done in the following methods.
l Direct conversion method.
l Parallel conversion method.
l Phase-in method.
The system is implemented by using the parallel conversion & fade-in method. Parallel conversion is in which both new & old system is run parallel for a particular period. In the phase-in method, the new system is implemented module by module
·
User training:-
The training should include everyone associated with the implementation, use, operation or maintenance of new system. The staff is comfortable with the system.
·
Software Testing:-
The aim of any software development is to create bug-free, reliable & secured system that provide solution to users requirements. The implementation of newly designed package is an important phase in adopting successful new system. The implementation of the package involves testing, user training, acceptance and change over.
Testing is an important & critical stage in software development. It accounts for the largest percentage of technical effort in the software development process. It plays a critical role in determining quality & reliability of an application. Testing phase in development life cycle validates the code against the functional specification. The feedback from test-stage will be incorporated which thereby ensures high reliability. To check the validity of the data MS-SQL 2000 validity checks & validity look-ups have been provided to ensure valid data entry.
The objective of testing is to discover errors. To fulfill this objective a series of test steps were planned & executed. The testing steps are:
·
Unit
testing
·
Integration
testing
·
Validation
testing
·
Output
testing
·
System
testing
·
User
acceptance testing.
Unit
testing:
In unit testing different module are tested against the specification produced during the design of the modules. Unit testing is essential for the verification of the code
Produced during coding phase, & hence the goal is to test the internal logic of the modules.
The testing is carried out during the programming itself. After designing & coding each form they are run to see whether there are any anomalies. Some of the various tests cases use to test the system are as follows:
l The test cases are given for testing against requirements of the unit being tested.
l If the unit modifies the database, test for the integrity of the database after the operation.
l Test cases for path or branch covering (use structures basic testing method).
l Test cases for database covering.
l Test bases cased on the experience (error guessing) such as testing for boundary conditions-minimum, maximum & off by one boundary.
l Testing of classes of bad data.
l Too little data or no data.
l Too much data.
l Working kind of data.
l Wrong size of data.
l Initialized data.
In unit testing, the program units that make up the system are tested individually. Unit testing focuses first on the modules, independent of one another to the logic within the module alone. This testing is also used to ensure the integrity of data store temporarily.
·
Integration Testing:
Integration testing is a systematic technique for constructing the program structure, while at the same time conducting tests to uncover errors associated with interfacing. That is the program is constructed & tested in small segments, which makes it easier to isolate & correct.
The following are common types of integration problems may be observed:
o
Version mistakes.
o
Data integrity violations.
o
Overlapping functions
- Resource problems especially in memory handling.
- Wrong type of parameters in function calls.
·
Validation Testing:
At the culmination or the integration testing, the software was completely assembled as a package, interfacing errors have been uncovered & corrected & final series of software validation testing began. Validation testing can define in many ways, but a simple definition is that validation succeeds when the software function in a manner that can be reasonably expected by the user or customer software validation is achieved through a series of black box test that demonstrate confirm with requirements. After validation test has been conducted, one of the two possible conditions exists.
The function or performance characteristics confirm to specification & are accepted.
A deviation from specification uncovered & deficiency list is created.
Deviation or error discovered at this step in this project is corrected prior to completion to this project with the help of user by negotiation to establish a method for resolving deficiencies. Thus, the proposed system under consideration has been tested by using validation testing & found to be working satisfactorily. After performing the validation testing the next step is the output testing of the proposed system. Since no system could be useful if it does not produce the required output in the specified format. Asking the user about the format required by them tests the output generated are displayed by the system under consideration. Here, the output format is considered in to two ways. One is on screen another is printed format. The user finds the output format on the screen to be correct as the format was designed in the system design phase according to the user needs. For the hard copy also the output comes out as the specified requirements. Hence, output testing does not result any correction in the system.
·
User acceptance testing:
User acceptance of a system is the key factor for the success of any system. The system under consideration was tested for user acceptance by constantly keeping in touch with the prospective system users at the time of developing & making changes whenever required, This is done in regard to the following points:
Input screen.
Output screen.
Online messages to guide the user.
Format of reports & other outputs.
System testing:
This is a series of tests whose primary purpose is to exercise the computer based system to verify that all system elements have been properly integrated & performed allocated function. Some of the consideration here is to see if the security mechanisms built into the systems would protect it from improper penetration. The primary concern is the compatibility of individual modules. Tests current specifications & system documentation.
7. FUTURE
ENHANCEMENT
The future enhancement of this project
is that it can be implemented on web applications by using Microsoft .Net
technologies. [Visual Basic .Net, C# and ASP.Net]
ASP : Active
Server Pages
C# : C
Sharp
8. CONCLUSION
CONCLUSION
Visual Basic.Net is the result of a
significant rebuild of Visual Basic for the Microsoft.Net Framework. There are
a number of changes that make visual Basic.NET easier to use, more powerful
than Visual Basic 6.0, and give it the kind of access to system resources that
in the past required the use of languages like C++. Rather than simply adding
some new features to Visual Basic 6.0. Microsoft has re-engineered the product
to make it easier than ever before to write distributed applications such as
web and enterprise n-tier systems.
The goals have been achieved by the
development of this project are:
- It simplifies the operation.
- The less processing time increases the
productivity.
- Avoids errors by minimizing human
intervention.
- User Friendly screens to enter the data
and require the data
- Tables
- Help message to operate the system.
- Reduce more manpower requirements.
- Reduce transaction processing time.
Comments
Post a Comment