Você está na página 1de 76

Table Of Contents

Sr.No. 1 2 3 4 5 6 7 8 9 10 11 12 13 14

Particulars Acknowledgement Introduction To Project System Analysis Feasibility Study Hardware and Software Requirements Tools Used For Development Introduction To MS Access Introduction To SQL Server Data Flow Diagram Code Efficiency Implementation and Maintainence Screenshots Future Scope Bibliography

Page No. 2-2 3-3 4-6 7-9 10-10 10-9 13-14 15-17 18-18 19-22 22-26 27-41 42-42 43-43

Acknowledgement
It is indeed a privilege as well as pleasant duty to express my gratitude to all those who have made it possible for me to complete this training. It is my proud privilege to acknowledge with respectful gratitude the invaluable

guidance extended to me by my esteemed guide RAJESH BANSAL. I am thankful for his pains, taking supervision, timely suggestions and continuous constructive criticism during the course of this training. His ever-helping nature and limitless patience were constant source of inspiration during this work. I am grateful and obliged to Rajesh K. Bansal , for his guidance and suggestions rendered to me during the training period. I am sure that the time I have spent with him will be a constant source of inspiration for me in the days to come. I convey my deepest respect and appreciation to my Principal and H.O.D. in the Department of Computer Science for their continuous support. Itika Jindal

Introduction to Project
The University Management System acts as a database for storing the information regarding the student profile,
2

information regarding books and where they have been kept in the library. This project also deals with the onset of the date sheet assigned and also the subjects the students need to study in their curriculum. The project has been a boon for the complete management of the curriculum vitae of the students and is only accessible to the users. The provision for signing up under the university is also being provided and the students can easily check their job status and apply for the placement cell. In addition to managing data it also provide additional facility of usage of calculator and a calendar.

SYSTEM ANALYSIS
IDENTIFICATION OF NEED
One must know what the problem is before it can be solved. The basis for a candidate system is recognition of a need for improving an information system or a procedure. Ideas for change may come from within the organizationtop management, the user, and the analyst. As an organization changes its operations or faces advances in computers, some one with in the organization may feel the need to update the existing application or improve the procedures. In our Institute Management System it is the Administration who has decided to upgrade the existing manual system to advanced technology called computerized system. In Institute continuous efforts are going on to upgrade manual way of keeping of the records replacing it by computerized system. We already have an Institute Management System that is being run manually. Different persons are assigned for different jobs, as one person is to maintain the enquiry information, the other is busy with managing the details of library issue return and fine, the other is busy to maintain the fee information, the other is busy to maintain staff and their subjects and the other is to keep the information of internals. So the basic problem faced with this system is if

one wants to get admission for a course, one has to enquire for new entries in one file and their class information in the different files. Moreover, there is no proper security of files. Unauthorized user can access the files. There are more and more chances of error so the system should be able to check for the errors. Institute Management System needs automated enquiry of Courses, Staff, Attendance and Internals progress, generating the fee bill, Presently Institute Management System is done manually. The shopping requires web-based package for the following reasons: The packages available in the market are not customized to the needs of the organization. Data is not available randomly. It is scattered in different files at different places. So information regarding one order is searched within multiple files and hence the process is time consuming. The manual system is dependent on the person who is handling and not system dependent. Its mean That the person, who has created it, because it is created according to him, he can understand it skills and knowledge while in automated package anybody can handle it by having little knowledge about the software i.e. it is system dependent.

As human brain is prone to tiredness, the efficiency reduces as well as system is bounded to have more errors and does calculation mistakes. Proper analysis cannot be done and various management reports are not available quickly because of data being scattered among different places. The major drawback is illegal activities can be done by the members without having the clues. Redundancy is also one of the hindrances in manual system. As data is duplicated at many different places, modification at one places and not another will lead to an error. Large amount of paper work has to be managed and handled.

FEASIBILITY STUDY
6

Depending upon the results of the initial investigation, the survey is expanded to a more detailed feasibility study. A feasibility study is a test of a system proposal according to its workability, impact on the organization, ability to meet users needs and effective use of resources. It includes thee main questions: What are the users needs and how the candidate system does meet them? What resources are available for given candidate system? What are the likely impacts of the candidates system on the organization? Three key considerations are involved in the feasibility analysis, Economical, technical, and operational. All of these are discussed one by one in the following section.

TECHNICAL FEASIBILITY
Technical feasibility concerns around the existing computer system (hardware, software etc) and to what extent it supports the proposed addition. In our case we have 1 server networked with the Intranet. Here the administration requires minimum 1 computer with the Intranet connection to run this project. Here each department requires minimum 1 computer to make the department as computerized networked with the Intranet. So we can say that there is no considerable burden on the store to make this project functional. As the administration is planning to computerize

the entire enquiry, admission and accounts facilities already have been allocated to do the same. So here we have to simply utilize the Intranet to manage the institute. Now using this project can save large amount of money and time.

ECONOMICAL FEASIBILITY
Economic analysis is the most frequently used method for evaluating the effectiveness of the candidate system. More commonly known as cost/benefit analysis, the procedure is to determine the benefits and savings that are expected from a candidate system. And compare them with costs. Our project is economically feasible, as it does not put any extra burden on administration. Already Intranet terminals are available in the Office and all are networked together all are using MS-Access database. There are only initial expenditures and after which our system can expand to any extent. After the implementation of this project a huge amount of manpower can be saved causing conversion of this manpower for the effective use in purchase. In the above discussion we noticed that the benefits are more than the costs. So the project is also economically feasible.

OPERATIONAL FEASIBILITY
People are inherently resistant to change. And computers are known to facilitate change. An estimate should be made

of how strong reaction the user staff is likely to have towards the development of a computerized system. The system should be simple to operate so that layman can also under stand what the system is, and how he can be benefited from the system. The project is operationally feasible as every care has been taken to make it easy to operate and more over while conducting preliminary investigations there was a strong reaction to open this type of system from user side also.

HARDWARE AND SOFTWARE REQUIREMENTS


VB.Net and SQL-SERVER

Window-XP/ 2000 or Higher A VGA or SVGA Graphics Adapter A Serial Pointer Mouse and Keyboard 20 G.B. Hard Disk or more 256 MB RAM or more 1.44 Floppy/ CD-ROM Drive 15 Monitor Printer

TOOLS USED FOR DEVELOPMENT


. NET Framework (VB.NET) as Front-End . SQL Server as Back-End

Introduction to Technology
.NET Framework & Visual Studio .NET

10

.NET is essentially a framework for software development. It is similar in nature to any other software development framework (J2EE etc) in that it provides a set of runtime containers/capabilities, and a rich set of pre-built functionality in the form of class libraries and APIs. The .NET Framework is an environment for building, deploying, and running Web Services and other applications. .Net is the Microsoft Web services strategy to connect information, people, systems, and devices through software. Integrated across the Microsoft platform, .NET technology provides the ability to quickly build, deploy, manage, and use connected, security-enhanced solutions with Web services. .Net-connected solutions enable businesses to integrate their systems more rapidly and in a more agile manner and help them realize the promise of information anytime, anywhere, on any device. The Microsoft platform includes everything a business needs to develop and deploy a Web service-connected IT architecture: servers to host Web services, development tools to create them, applications to use them, and a worldwide network of more than 35,000 Microsoft Certified Partner organizations to provide any help you need.

VB.Net
VB.Net is the successor of the Visual Basic 6 programming language. VB.Net has brought about a great number of architectural changes in the Visual Basic language that are not backward compatible. A number of core elements and concepts in VB6 have been modified or removed. A great many new features have been added to the VB.Net language. It will be right to say that VB.Net will change the
11

way Visual Basic programmers perceive their development. VB.Net has gained some credibility among serious programmers. Visual Basic has gained much favor amongst many developers. Currently, there are more VB programmers in the world than there are for any other programming language and there is more application development done in VB than in any other programming language. In the Microsoft .Net platform, VB.Net (along with C#.NET) is the language of choice. Its probable that most of the current VB6 programmers would like to switch to VB.Net when they decide to move to the .Net platform (which ultimately all Windows developers will have to; certainly the .Net platform is very much a part of LongHorn development).

VB.Net as a Programming Language


VB.Net is now a full-fledged object oriented programming language. It contains classes, objects, inheritance, polymorphism, abstract classes, interfaces, structures, enumerations, delegates and other common object oriented concepts. In VB.Net, the error handling mechanism has been modified and is now more structured. VB.Net uses the .Net standard garbage collector to release memory that is no more referenced by your apps. Probably the best thing about VB.Net is that it is a part of the .Net framework and is integrated in the .Net platform. It means that VB.Net programs can employ all the features and services exposed by the .Net framework. It can use the .Net framework class libraries, interact with program modules written in other .Net language and also use the old COM and ActiveX components. Previously, Visual Basic was mainly used for Windows applications and nothing else. Now VB.Net can be used to create console applications, Windows
12

applications, web applications, .Net components, .Net Form controls, .Net Web controls, windows services, web services, database applications, and more. Using the .Net framework libraries you can program new exciting features like reflection, attributes, marshalling, remoting, threads, streams and also data access with ADO.Net. Compared to using VB6, VB.Net will feel extremely powerful. The .NET Framework (pronounced dot net framework) defines the environment that you use to execute Visual Basic .NET applications and the services you can use within those applications. One of the main goals of this framework is to make it easier to develop applications that run over the Internet. However, this framework can also be used to develop traditional business applications that run on the Windows desktop. To develop a Visual Basic .NET application, you use a product called Visual Studio .NET (pronounced Visual Studio dot net). This is actually a suite of products that includes the three programming languages. Visual Studio also includes several other components that make it an outstanding development product. One of these is the Microsoft Development Environment, which youll be introduced to in a moment.. Another is the Microsoft SQL Server 2000 Desktop Engine (or MSDE). MSDE is a database engine that runs on your own PC so you can use Visual Studio for developing database applications that are compatible with Microsoft SQL Server. SQL Server in turn is a database management system that can be used to provide the data for large networks of users or for Internet applications. Programming languages supported by Visual Studio .NET Language Description Visual Basic .NET Designed for rapid

13

application development. Visual C# .NET A new language that combines the features of Java and C++ and is suitable for rapid application development. Visual C++ .NET Microsofts version of C++ that can be used for developing high-performance applications. The .NET Framework provides a common set of services that application programs written in a .NET language such as Visual Basic .NET can use to run on various operating systems and hardware platforms.

The .NET Framework is A component model for the internet The new approach to building large scale distributed systems for the Internet Provides the capability to integrate multiple devices. Built around the tools and protocols (XML, WSDL, SOAP, HTTP) that are becoming standard on the Internet. The .Net Framework Design Goals Component Development for the Internet Cross-Language Development Inheritance, Debugging, Exception handling Reliability and Security Simple Development and Deployment Device-agnostic

The .NET Framework components:

is

divided

into

two

main

The .NET Framework Class Library The Common Language Runtime

14

The .NET Framework Class Library consists of segments of pre-written code called classes that provide many of the functions that you need for developing .NET applications. For instance, the Windows Forms classes are used for developing Windows Forms applications. The ASP.NET classes are used for developing Web Forms applications. And other classes let you work with databases, manage security, access files, and perform many other functions. Although its not apparent in this figure, the classes in the .NET Framework Class Library are organized in a hierarchical structure. Within this structure, related classes are organized into groups called namespaces. Each namespace contains the classes used to support a particular function. For example, the System.Windows.Forms namespace contains the classes used to create forms and the System.Data namespace contains the classes you use to access data. The Common Language Runtime, or CLR, provides the services that are needed for executing any application thats developed with one of the .NET languages. This is possible because all of the .NET languages compile to a common intermediate language. The CLR also provides the Common Type System that defines the data types that are used by all the .NET languages. That way, you can use more than one of the .NET languages as you develop a single application without worrying about incompatible data types.

15

Description: .NET applications do not access the operating system or computer hardware directly. Instead, they use services of the .NET Framework, which in turn access the operating system and hardware. The .NET Framework consists of two main components: the .NET Framework Class Library and the Common Language Runtime. The .NET Framework Class Library provides pre-written code in the form of classes that are available to all of the .NET programming languages. This class library consists of hundreds of classes. The Common Language Runtime (CLR) is the foundation of the .NET Framework. It manages the execution of .NET programs by coordinating essential functions such as
16

memory management, code execution, security, and other services. Because .NET applications are managed by the CLR, they are called managed applications. The Common Type System (CTS) is a component of the CLR that ensures that all .NET applications use the same basic data types regardless of what programming languages were used to develop the applications. Two other components Component Description of Visual Studio .NET

Microsoft Development Environment:- The Integrated Development Environment (IDE) that you use for developing applications in any of the three languages. Microsoft SQL Server 2000 Desktop Engine:A database engine that runs on your own PC so you can use Visual Studio for developing database applications that are compatible with Microsoft SQL Server. Benefits of .Net Interoperability between languages and execution environments. Uniformity in schema or formats for Data Exchange using XML, XSL. Extend or use existing code that is valid. Programming complexity of environment is reduced. Platforms that can run Visual Studio .NET Windows 2000 and later releases of Windows Platforms that can run Visual Studio .NET applications Windows 98 and later releases of Windows, depending on which .NET components the application uses Visual Basic .NET Standard Edition
17

An inexpensive alternative to the complete Visual Studio .NET package that supports a limited version of Visual Basic .NET as its only programming language Description: The .NET Framework defines the environment that you use for executing Visual Basic .NET applications. Visual Studio .NET is a suite of products that includes all three of the programming languages listed above. These languages run within the .NET Framework. You can develop business applications using either Visual Basic .NET or Visual C# .NET. Both are integrated with the design environment, so the development techniques are similar although the language details vary. Besides the programming languages listed above, thirdparty vendors can develop languages for the .NET Framework. However, programs written in these languages cant be developed from within Visual Studio .NET.

18

Description: 1. The programmer uses Visual Studios Integrated Development Environment to create a project, which includes one or more Visual Basic source files. In some cases, a project may contain other types of files, such as graphic image files or sound files. A solution is a container that holds projects. Although a solution can contain more than one project, the solution for most simple applications contains just one project. So you can think of the solution and the project as essentially the same thing. 2. The Visual Basic compiler translates or builds the source code into Microsoft Intermediate Language (MSIL), or just Intermediate Language (IL). This language is stored on disk in an assembly that also contains references to the classes that the application requires. An assembly is simply an executable file that has an .exe or .dll extension.

19

3. The assembly is then run by the .NET Frameworks Common Language Runtime. The CLR manages all aspects of how the assembly is run, including converting the Intermediate Language to native code that can be run by the operating system, managing memory for the assembly, enforcing security. The Common Language Runtime (CLR) One of the major components of the .NET Framework is the Common Language Runtime, or CLR. The CLR provides a number of benefits to the developer, such as exception handling, security, debugging, and versioning, and these benefits are available to any language built for the CLR. This means that the CLR can host a variety of languages, and can offer a common set of tools across those languages. Microsoft has made VB, C++, and C# premier languages for the CLR, which means that these three languages fully support the CLR. In addition, other vendors have signed up to provide implementations of other languages, such as Perl, Python, and even COBOL. When a compiler compiles for the CLR, this code is said to be managed code. Managed code is simply code that takes advantage of the services offered by the CLR. For the runtime to work with managed code, that code must contain metadata. This metadata is created during the compilation process by compilers targeting the CLR. The metadata is stored with the compiled code and contains information about the types, members, and references in the code. Among other things, the CLR uses this metadata to Locate classes Load classes Generate native code Provide security

20

The runtime also handles object lifetimes. Just as COM/COM+ provided reference counting for objects, the CLR manages references to objects and removes them from memory when all the references are gone, through the process known as garbage collection. Although garbage collection actually gives you slightly less control than you had in VB, you gain some important benefits. For example, your errors should decrease because the number of objects that end up hanging around due to circular references should be reduced or completely eliminated. In addition, garbage collection ends up being much faster than the old way of destroying objects in VB. Instances of objects you create that are managed by the runtime are called managed data. You can interact with both managed and unmanaged data in the same application, although managed data gives you all the benefits of the runtime. The CLR defines a standard type system to be used by all CLR languages. This means that all CLR languages will have the same size integers and longs, and they will all have the same type of stringno more worrying about BStrs and CStrs! This standard type system opens up the door for some powerful language interoperability. For example, you can pass a reference of a class from one component to another, even if those components are written in different languages. You also can derive a class in C# from a base class written in VB.NET, or any other combination of languages targeted to the runtime. Dont forget that COM had a set of standard types as well, but they were binary standards. This meant that with COM, you had language interoperability at run time. With NETs type standard, you have language interoperability at design time. After it is compiled, managed code includes metadata, which contains information about the component itself, and the

21

components used to create the code. The runtime can check to make sure that resources on which you depend are available. The metadata removes the need to store component information in the registry. That means moving a component to a new machine does not require registration and removing components is as simple as deleting them. The Common Language Runtime provides a number of benefits that are not only new, but should enhance the experience of building applications. Other benefits that you will see in more detail include some of the new objectoriented features to VB.NET. Many of these new features are not so much additions to the language as they are features of the runtime that are simply being exposed to the VB.NET.

Assemblies One of the new structures you will create in VB.NET is the assembly. An assembly is a collection of one or more physical files. The files are most often code, such as the classes you build, but they could also be images, resource files, and other binary files associated with the code. Such assemblies are known as static assemblies because you create them and store them on disk. Dynamic assemblies are created at runtime and are not normally stored to disk (although they can be). An assembly represents the unit of deployment, version control, reuse, and security. If this sounds like the DLLs you have been creating in Visual Basic for the past six years, it is similar. Just as a standard COM DLL has a type library, the assembly has a manifest that contains the metadata for the assembly, such as the classes, types, and references contained in the IL. The assembly often contains one or more classes, just like a COM DLL. In .NET, applications are built
22

using assemblies; assemblies are not applications in their own rights. Perhaps the most important point of assemblies is this: All runtime applications must be made up of one or more assemblies.

The Common Type System The Common Type System specifies the types supported by the CLR. The types specified by the CLR include: ClassesThe definition of what will become an object; includes properties, methods, and events InterfacesThe definition of the functionality a class can implement, but does not contain any implementation code Value TypesUser-defined data types that are passed by value DelegatesSimilar to function pointers in C++, delegates are often used for event handling and callbacks. The type system sets out the rules that language compilers must follow to produce code that is cross-language compatible. By following the type system, vendors can produce code that is guaranteed to work with code from other languages and other compilers because all languages are consistent in their use of types.

23

MSIL (Microsoft Intermediate Language) Code When we compile our .Net Program using any .Net compliant language (like C#, VB.Net, C++.Net) it does not get converted into the executable binary code but to an intermediate code, called MSIL or IL, understandable by CLR. MSIL is OS and hardware independent code.

When the program needs to be executed, this MSIL, or intermediate code, is converted to binary executable code (native code). The presence of IL makes possible the Cross Language Relationship as all the .Net compliant languages produce similar, standard IL code. Just In Time Compilers (JITers) When our IL compiled code needs to be executed, CLR invokes the JIT compilers which compile the IL code to native executable code (.exe or .dll) that is designed for the specific machine and OS. JITers in many ways are different from traditional compilers as they compile the IL to native code only when desired; e.g., when a function is called, the IL of the function's body is converted to native code just in time. So, the part of code that is not used by that particular run is never converted to native code. If some IL code is converted to native code, then the next time it's needed, the CLR reuses the same (already compiled) copy without re24

compiling. So, if a program runs for sometime (assuming that all or most of the functions get called), then it won't have any just-in-time performance penalty. As JITers are aware of the specific processor and OS at runtime, they can optimize the code extremely efficiently resulting in very robust applications. Also, since a JIT compiler knows the exact current state of executable code, they can also optimize the code by in-lining small function calls (like replacing body of small function when its called in a loop, saving the function call time). Although Microsoft stated that C# and .Net are not competing with languages like C++ in efficiency and speed of execution, JITers can make your code even faster than C++ code in some cases when the program is run over an extended period of time (like web-servers). Framework Class Library (FCL) The .Net Framework provides a huge Framework (or Base) Class Library (FCL) for common, usual tasks. FCL contains thousands of classes to provide access to Windows API and common functions like String Manipulation, Common Data Structures, IO, Streams, Threads, Security, Network Programming, Windows Programming, Web Programming, Data Access, etc. It is simply the largest standard library ever shipped with any development environment or programming language. The best part of this library is they follow extremely efficient OO design (design patterns) making their access and use very simple and predictable. You can use the classes in FCL in your program just as you would use any other class. You can even apply inheritance and polymorphism to these classes.

Database
25

Databases are designed to offer an organized mechanism for storing, managing and retrieving information. They do so through the use of tables. If youre familiar with spreadsheets like Microsoft Excel, youre probably already accustomed to storing data in tabular form. Its not much of a stretch to make the leap from spreadsheets to databases. Database Tables Just like Excel tables, database tables consist of columns and rows. Each column contains a different type of attribute and each row corresponds to a single record. For example, imagine that we were building a database table that contained names and telephone numbers. Wed probably set up columns named First Name, Last Name and Telephone Number. Then wed simply start adding rows underneath those columns that contained the data were planning to store. If we were building a table of contact information for our business that has 50 employees, wed wind up with a table that contains 50 rows. Databases and Spreadsheets At this point, youre probably asking yourself an obvious question if a database is so much like a spreadsheet, why cant I just use a spreadsheet? Databases are actually much more powerful than spreadsheets in the way youre able to manipulate data. Here are just a few of the actions that you can perform on a database that would be difficult if not impossible to perform on a spreadsheet: Retrieve all records that match certain criteria. Update records in bulk. Cross-reference records in different tables.
26

Perform complex aggregate calculations.

Data Access in .Net using ADO.Net:Introducing ADO.NET Most of today's applications need to interact with database systems to persist, edit or view data. In .NET, data access services are provided through ADO.NET components. ADO.NET is an object oriented framework that allows you to interact with database systems. We usually interact with database systems through SQL queries or stored procedures. The best thing about ADO.NET is that it is extremely flexible and efficient. ADO.NET also introduces the concept of disconnected data architecture. In traditional data access components, you made a connection to the database system and then interacted with it through SQL queries using the connection. The application stays connected to the DB system even when it is not using DB services. This commonly wastes valuable and expensive database resources, as most of the time applications only query and view the persistent data. ADO.NET solves this problem by managing a local buffer of persistent data called a data set. Your application automatically connects to the database server when it needs to run a query and then disconnects immediately after getting the result back and storing it in the dataset. This design of ADO.NET is called disconnected data architecture and is very much similar to the connectionless services of HTTP on the internet. It should be noted that ADO.NET also provides connection oriented traditional data access services.

27

Traditional Data Access Architecture

ADO.NET Disconnected Data Access Architecture Another important aspect of disconnected architecture is that it maintains a local repository of data in the dataset object. The dataset object stores the tables, their relationships and their different constraints. The user can perform operations like update, insert and delete on this local dataset. The changes made to the dataset are applied to the actual database as a batch when needed. This greatly reduces network traffic and results in better performance. Different components of ADO.NET Before going into the details of implementing data access applications using ADO.NET, it is important to understand its different supporting components or classes. All of the generic classes for data access are contained in the System.Data namespace. Class DataSet Description The DataSet is a local buffer of tables or a
28

collection of disconnected recordsets A DataTable is used to contain data in tabular DataTable form using rows and columns. DataRow Represents a single record or row in a DataTable DataColumn Represents a column or field of a DataTable Represents the relationship between different DataRelation tables in a DataSet. Represents the constraints or limitations that Constraint apply to a particular field or column. ADO.NET also contains some database specific classes. This means that different database system providers may provide classes (or drivers) optimized for their particular database system. Microsoft itself has provided the specialized and optimized classes for their SQL server database system. The names of these classes start with 'Sql' and are contained in the System.Data.SqlClient namespace. Similarly, Oracle has also provides its classes (drivers) optimized for the Oracle DB System. Microsoft has also provided the general classes which can connect your application to any OLE supported database server. The name of these classes start with 'OleDb' and these are contained in the System.Data.OleDb namespace. In fact, you can use OleDb classes to connect to SQL server or Oracle database; using the database specific classes generally provides optimized performance however. Class SqlConnection, OleDbConnection SqlCommand, OleDbCommand SqlDataAdapter, OleDbDataAdapter Description Represents a connection database system Represents SQL a query A class database that connects to system, fetches the the

to

the

29

SqlDataReader, OleDbDataReader SqlParameter, OleDbParameter Microsoft Access

records and fills the DataSet A stream that reads data from the database in a connected design Represents a parameter to a stored procedure

Microsoft Access is a powerful relational database management system catering to high-end users with advanced needs. Along with Oracle, Microsoft Access is widely regarded as one of the two main full-featured database systems on the market today. The structured query language is an industry-standard language used for manipulation of data in a relational database. The major SQL commands of interest to database users are SELECT, INSERT, JOIN and UPDATE. Microsoft Access is a full-featured relational database management system (RDBMS) that offers a variety of administrative tools to ease the burdens of database development, maintenance and administration. SQL Most large-scale databases use the structured query language(SQL) to facilitate user and administrator interactions. This language offers a flexible interface for databases of all shapes and sizes. The first important point to make is that database transactions are made in SQL, whether you realize it or not. Nowadays, there are a large number of graphical user interfaces (GUIs) that simplify database administration tasks. If you're a SQL Server user, you may be familiar with tools like Enterprise Manager. There are also quite a few third-party applications that interact with different databases (in fact, many of these can

30

work with multiple database platforms simultaneously.) Did you ever wonder how these applications work? Thats right! They use SQL! The front-end translates your mouse clicks and text entries into SQL and then speaks to the database in the universal language of SQL.

A review of basic SQL queries Here we present a brief review of four basic SQL queries. SQL SELECT Statement This query is used to select certain columns of certain records from one or more database tables. SELECT * from emp selects all the fields of all the records from the table named 'emp' SELECT empno, ename from emp selects the fields empno and ename for all of the records from the table named 'emp' SELECT * from emp where empno < 100 selects all records from the table named 'emp' where the value of the field empno is less than 100 SELECT * from article, author where article.authorId = author.authorId

31

selects all records from the tables named 'article' and 'author' that have the same value of the field authorId SQL INSERT Statement This query is used to insert a record into a database table. INSERT INTO emp(empno, ename) values(101, 'John Guttag') inserts a record in to the emp table and sets its empno field to 101 and its ename field to 'John Guttag' SQL UPDATE Statement This query is used to modify existing records in a database table. UPDATE emp SET ename = 'Eric Gamma' WHERE empno = 101 updates the record whose empno field is 101 by setting its ename field to 'Eric Gamma' SQL DELETE Statement This query is used to delete existing record(s) from a database table. DELETE FROM emp WHERE empno = 101 deletes the record whose empno field is 101 from the emp table Note that its not good practice to allow users to actually delete records from your database. This is open to abuse an human error. A more safer method is to flag a field with an end date. I.e When a user "deletes" a record, what really happens is this. UPDATE emp SET enddate = GetNow(date) WHERE empno = 101 To remove this record from the users reach in future quieries.

32

Select * FROM emp WHERE enddate = Null Performing common data access tasks with ADO.NET Enough review and introduction! Let's start something practical. Now we will build an application to demonstrate how common data access tasks are performed using ADO.NET. We will use MS SQL server and MS Access database systems to perform the data access tasks. SQL Server is used because probably most of the time you will be using MS SQL server when developing .NET applications (And theres a free cut down version available from Microsoft). For SQL server, we will be using classes from the System.Data.SqlClient namespace. Access is used to demonstrate the OleDb databases. For Access we will be using classes from the System.Data.OleDb namespace. In fact, there is nothing different in these two approaches for developers and only two or three statements will be different in both cases. We will highlight the specific statements for these two using comments like: ' For SQL server Dim dataAdapter As New SqlDataAdapter(commandString, conn) ' For Access Dim dataAdapter As New OleDbDataAdapter(commandString, conn) For the example code, we will be using a database named 'ProgrammersHeaven'. The database will have a table named 'Article'. The fields of the table 'Article' are Field Name artId title Type (Primary Key)Integer String Description The unique identifier for an article The title of an article

33

topic authorId lines

String (Foreign Key)Integer Integer

Topic or Series name of the article like 'Multithreading in Java' or 'VB.NET School' Unique identity of author Number of lines in the article The date the article was published

dateOfPublishing Date

The 'ProgrammersHeaven' database also contains a table named 'Author' with the following fields: Field Name authorId name Type (Primary Key)Integer String Description The unique identity of the author Name of the author

Accessing Data using ADO.NET Data access using ADO.NET involves the following steps: Defining the connection string for the database server Defining the connection (SqlConnection or OleDbConnection) to the database using a connection string Defining the command (SqlCommand or OleDbCommand) or command string that contains the query Defining the Data Adapter (SqlDataAdapter or OleDbDataAdapter) using the command string and the connection object
34

Creating a new DataSet object If the SQL command is SELECT, filling the DataSet object with the results of the query through the Data Adapter Reading the records from the DataTables in the DataSets using the DataRow and DataColumn objects If the SQL command is UPDATE, INSERT or DELETE. The dataset will be updated through the data adapter Accepting to save the changes in the DataSet to the database Since we are demonstrating an application that uses both SQL Server and Access databases we need to include the following namespaces in our application: Imports System.DataImports System.Data.OleDb Access database Imports System.Data.SqlClient ' for SQL Server Defining the connection string The connection string defines which database server you are using, where it resides, your user name and password and optionally the database name. For SQL Server we have written the following connection string: ' for Sql Server Dim connectionString As String database=programmersheaven;" + _ "uid=phuser; pwd=nicecoding;" = "server=P-III; ' for

First of all we have defined the instance name of the server, which is "P-III" on our system. Next we defined the name of the database, the user id (uid) and the password (pwd). These days when you install Sql server the installation forces you to think of a password for the SA (System Administrator)
35

user . Its good practice for you to create another admin user and not use the SA user ever again. This will help stop intruders breaking in to your database. For Access, we have written the following connection string: ' for MS Access Dim connectionString As String "provider=Microsoft.Jet.OLEDB.4.0;" + _ "data source = c:\programmersheaven.mdb" =

We have defined the provider of the access database. Then we have defined the data source which is the location of the target database. Defining a Connection A connection is defined using the connection string. This object is used by the Data Adapter to connect to and disconnect from the database. For SQL Server, a connection is created like this: ' for Sql Server Dim conn As New SqlConnection(connectionString) And for Access, a connection is created like this: ' for MS Access Dim conn As New OleDbConnection(connectionString) Here we have passed the connection constructor of the connection string to object. the

Defining the command or command string The command contains the query to be passed to the database. We are using a command string. We will see the command object (SqlCommand or OleDbCommand) later in

36

the lesson. The command string we have used in our application is: Dim commandString As String = "SELECT " + _ "artId, title, topic, " + _ "article.authorId as authorId, " + _ "name, lines, dateOfPublishing " + _ "FROM " + _ "article, author " + _ "WHERE " + _ "author.authorId = article.authorId" We have passed a query to select all the articles along with the author's name. Of course you may want to use a simpler query, such as: Dim commandString As String = "SELECT * from article" Defining the Data Adapter We need to define the Data Adapter (SqlDataAdapter or OleDbDataAdapter). The Data Adapter stores your command (query) and connection. Using the connection and query the DaraAdapter connects to the database when asked, fetches the result of the query and stores it in a local dataset. For SQL Server, a Data Adapter is created like this: ' for Sql Server Dim dataAdapter As New SqlDataAdapter(commandString, conn) And for Access, a data adapter is created like this: ' for MS Access Dim dataAdapter As OleDbDataAdapter(commandString, conn) New

37

We have created a new instance of the Data Adapter and supplied it the command string and connection object in the constructor call. Creating and filling the DataSet Finally, we need to create an instance of the DataSet. As we mentioned earlier, a DataSet is a local and offline container of data. The DataSet object is created simply as: Dim ds As New DataSet() We need to fill the DataSet with the results from the query. We will use the DataAdapter object for this purpose and call its Fill() method. This is the step where the Data Adapter connects to the physical database and fetches the result of the query. dataAdapter.Fill(ds, "prog") We have called the Fill() method of dataAdapter object. We have supplied it the dataset to fill and the name of the table (DataTable) in which the result of query is filled. This is all we need to connect and fetch data from the database. Now the results of the query is stored in the dataset object in the prog table, which is an instance of the DataTable. We can get a reference to this table by using the indexer property of the DataSet object's Tables collection. Dim dataTable As DataTable = ds.Tables("prog") The indexer we have used takes the name of the table in the DataSet and returns the corresponding DataTable object. We can use the tables Rows and Columns collections to access the data in the table.

38

INTRODUCTION TO VISUALBASIC.NET Visual Studio .NET is a complete set of development tools for building ASP Web applications, XML Web services, desktop applications, and mobile applications. Visual Basic .NET, Visual C++ .NET, and Visual C# .NET all use the same integrated development environment (IDE), which allows them to share tools and facilitates in the creation of mixedlanguage solutions. In addition, these languages leverage the functionality of the .NET Framework, which provides access to key technologies that simplify the development of ASP Web applications and XML Web services. Visual Basic has been updated to include many new and improved language features that make it a powerful objectoriented programming language. These features include inheritance, interfaces, and overloading, among others. Visual Basic also now supports structured exception handling, and custom attributes. In addition, Visual Basic supports for multithreading. Multithreading is the ability to assign individual tasks to separate processing threads. Visual Basic .NET has many new and improved language features such as inheritance, interfaces, and overloading that make it a powerful object-oriented programming

39

language. As a Visual Basic developer, you can now create multithreaded, scalable applications using explicit multithreading. Other new language features in Visual Basic .NET include structured exception handling, custom attributes, compliance. The CLS is a set of rules that standardizes such things as data types and how objects are exposed and interoperate. Visual Basic .NET adds several features that Visual Basic .NET supports many new or improved objectoriented language features such as inheritance, overloading, the Overrides keyword, interfaces, shared members, and constructors. Also included structured exception handling, delegates, and several new data types. INHERITANCE Visual Basic .NET supports inheritance by allowing you to define classes that serve as the basis for derived classes. Derived classes inherit and can extend the properties and methods of the base class. They can also override inherited methods with new implementations. All classes created with Visual Basic .NET are inheritable by default. Because the forms you design are really classes, you can use inheritance to define new forms based on existing ones. For details, see Inheritance. EXCEPTION HANDLING and common language specification (CLS)

40

Visual Basic .NET supports structured exception handling, using an enhanced version of the Try...Catch...Finally syntax supported by other languages such as C++. Structured exception handling combines a modern control structure (similar to Select Case or While) with exceptions, protected blocks of code, and filters. Structured exception handling makes it easy to create and maintain programs with robust, comprehensive error handlers. For details, see Exception Handling. OVERLOADING Overloading is the ability to define properties, methods, or procedures that have the same name but use different data types. Overloaded procedures allow you to provide as many implementations as necessary to handle different kinds of data, while giving the appearance of a single, versatile procedure. For details, see Overloaded Properties and Methods. OVERRIDING PROPERTIES AND METHODS The Overrides keyword allows derived objects to override characteristics inherited from parent objects. Overridden members have the same arguments as the members inherited from the base class, but different implementations. A member's new implementation can call the original implementation in the parent class by preceding the member name with My Base. For details, see Overriding Properties and Methods. CONSTRUCTORS AND DESTRUCTORS

41

Constructors are procedures that control initialization of new instances of a class. Conversely, destructors are methods that free system resources when a class leaves scope or is set to Nothing. Visual Basic .NET supports constructors and destructors using the Sub New and Sub Finalize procedures. For details, see Object Lifetime: How Objects are Created and Destroyed. DATA TYPES Visual Basic .NET introduces three new data types. The Char data type is an unsigned 16-bit quantity used to store Unicode characters. It is equivalent to the .NET Framework System. Char data type. The Short data type, a signed 16-bit integer, was named Integer in earlier versions of Visual Basic. The Decimal data type is a 96-bit signed integer scaled by a variable power of 10. In earlier versions of Visual Basic, it was available only within a Variant. For details, see Data Types. INTERFACES Interfaces describe the properties and methods of classes, but unlike classes, do not provide implementations. The Interface statement allows you to declare interfaces, while the Implements statement lets you write code that puts the items described in the interface into practice. For details, see Interfaces in Visual Basic .NET. DELEGATES

42

Delegates objects that can call the methods of objects on your behalf are sometimes described as type-safe, objectoriented function pointers. You can use delegates to let procedures specify an event handler method that runs when an event occurs. You can also use delegates with multithreaded applications. For details, see Delegates and the Address Of Operator. SHARED MEMBERS Shared members are properties, procedures, and fields that are shared by all instances of a class. Shared data members are useful when multiple objects need to use information that is common to all. Shared class methods can be used without first creating an object from a class. For details, see Shared Members. REFERENCES References allow you to use objects defined in other assemblies. In Visual Basic .NET, references point to assemblies instead of type libraries. For details, see References and the Imports Statement. NAMESPACES Namespaces prevent naming conflicts by organizing classes, interfaces, and methods into hierarchies. For details, see Namespaces. ASSEMBLIES

43

Assemblies replace and extend the capabilities of type libraries by, describing all the required files for a particular component or application. An assembly can contain one or more namespaces. For details, see Assemblies. ATTRIBUTES Attributes enable you to provide additional information about program elements. For example, you can use an attribute to specify which methods in a class should be exposed when the class is used as a XML Web service. For details, see Attributes.

MULTITHREADING Visual Basic .NET allows you to write applications that can perform multiple tasks independently. A task that has the potential of holding up other tasks can execute on a separate thread, a process known as multithreading. By causing complicated tasks to run on threads that are separate from your user interface, multithreading makes your applications more responsive to user input. For details, see Multithreaded Applications.

44

INTRODUCTION TO MS-ACCESS DBMS that can be used to store and manipulate large amount of information and MS-ACCESS is a powerful multi user automate respective task. A collection of data and objects related to particular topic or purpose. Data in access is organized in the form of tables. Within a table records are arranged according to common to reference value known as Primary Key or Key Field. Access also manipulates index file or table. An index is external table of value that access maintain to store the order of records. Index object thus provide efficient access to data. Database indexes are just like books index. DATABASE OBJECTS TABLES A table is collection of data about a specific topic, such as product or supplier. Using a separate table for each topic means that you store data only once, which makes your database more efficient and reduces data-entry errors. QUERY You use queries to view, change and analyze in different ways. You can also use them as the source of records for forms, reports and data access pages. FORMS

45

You create the link between the form and its reports source by using graphical objects called controllers. The most common type of control used to display and enter data is a text box. Most of the information in a form come from and underlying source. Other information in the form is stored in form design. REPORT A report is an effective way to present your data in printed format because you have control over the size and appears of everything on report, you can display the information the way you want to see it. Most of information in a report comes from an underlying tables, or SQL statements, which is the source of reports data. Other information in report is stored in the reports design. FEATURES OF MS-ACCESS WINDOWS BASED APPLICATION Access is a windows based application an therefore has an interface similar to windows NT. You can cut, copy, paste from any windows application to and form access. LARGE DATA MANAGEMENT CAPACITY Access maintains a single disk for database and all associated objects. The maximum size of this can be of 1 G.B. Access allows a maximum of 32,768 tables and objects in the database. However, access can also supports 225 user at a a time BUILT-IN SECURITY

46

Single access is a multi-user database security features are built into the DBMS. You can enable database security at various levels. You can assign a password for loading access so that only authorized users can use it. You can encrypt a database to prevent un-authorized access.

CODE EFFICIENCY When we produce large programs, it often happens that extra code is left in the project. This extra code can be unused subs and functions, old variables, unnecessary constants, even Types and Enums. Extra code takes up disk space, slows down the program and it also makes it harder to read. Since this code is not needed, it is also called dead code. The opposite of dead code is live code. You can trace the dead code and then remove. One needs to detect questionable programming practices and code. Problem categories: Problems fall into 4 categories: Optimization. These problems adversely affect the speed and size of the resulting program. Style. These problems are related to the programming style. They don't necessarily lead to problems in the short run, but they often lead to confusion and further errors in the future.

47

Metrics is a sub-category of Style. You can set target values for different metrics and monitor to find out if some part of your program exceeds the limits. Read more about metrics in chapter 4. Functionality. These problems affect the run-time functionality of the program. The reason is often that somebody forgot to do something! One can create quick check filters and strict filters for giving code a final polish. The filters are:

Dead code Disable checking Functionality Optimizations Strict Style

Check deadness only Disable all problem checking Report problems affecting functionality only Report problems related to optimization only Report all problems Report problems related to style issues only

In this Project no dead code, variable, procedure, module is available. Problems were reported to the guide and with his help these all are solved. Coding is done by keeping in mind the future reusability of it. Complexity is tried to be in reduced number. Call trees are used here i.e. procedure / function call other procedure / function.

48

OPTIMIZATION OF CODE Development that are considered to improve the systems performance on the following areas :Physical I/O - data is read from and written into I/O devices. This can be a potential bottleneck. A well-configured system always runs 'I/O-bound' - the performance of the I/O dictates the overall performance. Memory consumption of the database resources e.g. Buffers, etc. CPU consumption on the database and application servers Network communication - not critical for little data volumes, becomes a bottleneck when large volumes are transferred.

CLASSIC GOOD 4GL PROGRAMMING CODE-PRACTICES GUIDELINES ARE -Avoid dead-code -Remove unnecessary code and redundant processing -Spend time documenting and adopt good change control practices -Spend adequate time analyzing business requirements, Process flows, data-structures and data-model -Quality assurance is key: plan and execute a good test plan and testing methodology -Experience counts

49

-These all points are kept in mind when the project was formulated. -In order to keep the amount of data which is relevant to the query the hit set small, always all known conditions in the WHERE clause is specified (wherever possible). The database system is also potentially made to use a database index (wherever possible) for greater efficiency resulting in fewer loads on the database server and considerably less load on the network traffic as well. Usage of "OR", "NOT", in Open SQL statements is checked appropriately. Wherever the maximum, minimum, sum and average value or the count of a database column is required, list with aggregate functions are used instead of computing the aggregates within the program. amount less. of data to the The RDBMS is responsible Overall Network, for aggregated computations instead of transferring large application. Application-server and Database load is also considerably

VALIDATION CHECKS Software validation is achieved through a series of black-box tests that demonstrate conformity with requirements. A test plan outlines the classes of tests to be conducted and a test procedure defines specific test cases that will be used to demonstrate conformity with requirements.

50

After each validation test case has been conducted, one of two possible conditions exists: (1) The function or performance characteristics conform to specification and are accepted or (2) a deviation from specification is uncovered and a deficiency list is created. CONFIGURATION REVIEW An important element of the validation process is a configuration review. The intent of the review is to ensure that all elements of the software configuration have been properly developed, are cataloged, and have the necessary detail to bolster the support phase of the software life cycle. The configuration review, sometimes called an audit. ALPHA AND BETA TESTING If software is developed as a product to be used by many customers, it is I impractical to perform formal acceptance test with each one. Most software product builders use a process called alpha and beta testing uncover errors that only the end-user seems able to find. A customer conducts the Alpha test at developers site. The software is used in a natural setting Alpha with the developer are looking in a over the shoulder of the user and recording errors and usage problems. tests conducted controlled environment. The Beta test is conducted at one or more customer sites by the end-user of the software. Unlike alpha testing, the developer is generally not present. Therefore, the beta test

51

is a live application of the software in an environment that cannot be controlled by the developer. The customer records all problems (real or imagined) that are encountered during beta tasting and reports these to the developer at regular intervals. As a result of problems reported during beta tests, software engineers make modifications and then prepare for release of the software product to the entire customer base. IMPLEMENTATION AND MAINTENANCE IMPLEMENTATION: A crucial phase in the system life cycle is the successful implementation of the new system designed. Implementation includes all those activities that take place to convert from the old system to the new one. The new system may be completely new, replacing an existing manual or automated system or it may be major modification to an existing system. In either case, proper implementation becomes necessary so that reliable system based on the requirements of the organization can be provided. Implementation includes: Training of personnel Conversion procedures Post-implementation review or evaluation TRAINING OF PERSONNEL:

52

The high quality training is an essential step in systems implementation. Hence to provide the training to personnel they have been provided user manuals. They are asked to read it carefully and same thing try practically on computer. If they dont understand any thing, can ask without any hesitation. They are asked to enter the data, which is more frequently entered, and print the reports are frequently printed. Users are told about those situations, which he must understand and he should able to handle it. CONVERSION METHOD: The direct conversion method is applied. This method converts from old to the new system abruptly. The old system is used till a planned conversion day. The organization relies fully on the new system. EVALUATION OR POST IMPLANTATION REVIEW: After the system is implemented and conversion is complete, a review is conducted to determine whether system is meeting expectations and where improvements are needed. A post implementation against how well review the measures the systems It to meet performance determines pre-determined system requirements.

continues

performance specifications. It also provides information to determine whether major re-design or modification is required. In evaluation system is checked against the predetermined requirements. All the requirements have been

53

fully attained. Where there was any mistake that had handled through system life cycle. Problem is solved and checked against the original facts. REVIEW PLAN: For review a team is planned. The Team shall prepare a formal plan around the objectives of the review. An overall plan covers the following areas:

ADMINISTRATOR PLAN: Review area objectives, operating costs, actual operating performance and benefits. PERSONNEL REQUIREMENTS PLAN: Review performance objectives and training performance to data. HARDWARE PLAN: Review performance specifications DOCUMENTATION REVIEW PLAN: Review the system development efforts. I. ADMINISTRATIVE PLAN

USER OBJECTIVE: This is an extremely crucial area since it may be possible that over a period of time the system does not meet the initial objectives of the user or objectives get changed as a

54

result

of

changes

in

the

overall

objectives

of

the

organization. The results of the evaluation are documented for future reference. OPERATING COSTS AND BENEFITS: Under the administration plan, current budget designed manipulate costs and savings of the system will closely reviewed. II. PERSONNEL REQUIREMENT PLAN Personnel old performance objectives will be compared with current performance levels. Training performance through testing, conducting interviews and other data gathering techniques. III. HARDWARE PLAN The hardware of the new system will also review. But as we are using existing hardware which full fill the requirement of project. Hence the cost of hardware is not increased. IV. DOCUMENTATION REVIEW PLAN: The reason for review plan is to evaluate the accuracy and completeness of the documentation compiled to date and to its conformity with documentation standards established earlier. SYSTEM MAINTENANCE: The last part of system development life cycle is system maintenance, which is actually the implementation of the post-implementation plan. Hence Programmers/ Analyst spend sufficient time for maintaining programs.

55

Hence maintenance will cover a wide range of activities including correcting coding and design errors, updating documentation and test data and upgrading user support. Many activities classified as maintenance actually fall under enhancements. Hence in maintenance of system enhancement also takes place. Therefore in maintenance addition, modification, re-developing of code will take place to support changes in specification. TESTING: No program or system design is perfect; the communication between the user and the designer is not always clear, and time is usually short. The result is errors and more errors. So before implementing the system it should be first tested. It is tedious but necessary step in system development. There are various testing techniques which are discussed below with the information that how they are applied to present system. The testing of software is done module wise. UNIT TESTING: It is technique for testing the changes made in an existing system. It is adopted to test the programs for errors. Errors found in coding and in logic are fixed. Errors between interactions of modules are removed.

INTEGRATION TESTING:

56

Integration testing is a systematic technique for constructing the program structure while at the same time conducting tests to uncover errors associated with interfacing. program structure that has been dictated by design. STRING TESTING: Programs are invariably related to one another and interact in total system. Each program is tested to see weather it confirms the related program in the system. Each part of the system is tested against the entire module with both test and live data before whole system is ready to be tested. SYSTEM TESTING: System testing is designed to uncover the weaknesses that were found in earlier tests. First the programs were tested against low volume of data. Now increasing the volume of data checks all the programs. This volume is increased until the maximum level for each transaction type is reached. USER ACCEPTANCE TESTING: An acceptance test has the objective of sealing the user on the validity and reliability of the system. It verifies that the systems procedures operate to system specifications and the integrity of vital data is obtained. Performance of this test is actually the users show. Users are allowed to operate the new system. And they are asked whether they are easy with new system as user acceptance is compulsory for a successful system. The screen are tried to make very easy if The objective is to take unit tested components and build a

57

user gives a good suggestion, which seems good. Screen is changed accordingly.

REPORT TESTING: In report testing old system reports are compared with new system. The entire calculated figures are checked carefully. Where there is error found is marked. And sent to programmer for correction. Once the problem is fixed, report is again sent to for checking. If it is found correct, then it is accepted else same step is repeated again. Old system reports are continued till all the new system reports are not checked and found correct. Once all the reports are O.K. The old system will be discontinued.

SYSTEM SECURITY MEASURES: The software is password protected. The user can enter to the admin part only via a password screen. And can exit only through same screen. The permission allows him more flexibility to keep his work secure for other user intervention. Unauthorized user get message. PASSWORD IS WRONG. Hence nobody other then authorized user can enter in application.

58

SREENSHOTS

59

This is the login form through which students can login to the university profiles by entering their USERID and PASSWORD.

Incase if the student has no account in the university site .He or she can signup i.e create new account by clicking SIGNUP button and then new form opens where the required

60

information is filled by the student to create his or her account.

If the student forgots his or her password ,he or she can click forgot button and then fill up the reqired information and then click on FIND button .the password will automatically be displayed to the student .

61

After logiging in the university ,student is able to access the profile and can check marks ,datesheet ,can change password etc. student can also use the various tools provided like notepad ,calculator etc .Student can also logout after accessing his or her account .

62

If the student wants to change his or her password so that it cant be hacked by somone else .he or she can go to tab and then click on my account and there is a option for changing password .

63

Students can also apply for part time job from their profiles and can fill the required information and then submit . This information can be checked out by the administration of the university.

64

Calender is also provided to the users for their reference .

65

Here students can also register for placements and submit the information regarding their experience .

66

Students are provided with the CALCULATOR for various calculations .

67

68

69

70

71

72

73

FUTURE SCOPE
As we mentioned above a module called Franchise, with help of this module we can expand our business by providing the franchisee to any person/firm interested at different locations. In this way we can cover a large area of the Globe. Pay mode: As mentioned above the customer can pay the order bill out of any three modes namely cash, Internet banking or credit card. In addition to it the other choice is also provided which will facilitate us to add a new mode if it is introduced in near future. 74

Also if a customer wants to pay through any other mode he/she will mention others giving details of that mode. Addition or deletion of new/old items:The administrator can add or delete any item at any stage in future if he/she wants to do so by entering his/her password. He/she can also update the website in accordance with the suggestions sent by the customers through suggestions module. After studying the complaints and suggestions made by the customers the administrator can give a new shape to this online shopping system which will facilitate all the customers to do shopping with more easiness and according to their choice.

75

BIBLIOGRAPHY
1. System Analysis and Design BY Elias M.Awad, Galgotia Publications. 2. Software Engineering By Roger S. Pressman, McGraw- Hill Publications. 3. MS-SQLSERVER ; BPB Publications. 4. 5. Mastering in VB.Net By BPB Publications. VisualBasic.Net Programming, Black Book.

76

Você também pode gostar