1. INTRODUCTION
1.1 ABOUT THE PROJECT
In present era, the scopes of information technology growing with a very fast .We do
not see any are untouched from this industry. The scope of information technology
has become wider includes: Business and industry. Household Business,
Communication, Education, Entertainment, Science, Medicine, Engineering, Distance
Learning, Weather Forecasting. Carrier Searching and so on.
My project named “Event Management System” is software that store and maintained
all events coordinated in college. It also helpful to print related reports. My project
will help to record the events coordinated by faculties with their Name, Event subject,
date & details in an efficient & effective ways.
In my system we have to make a system by which a user can record all events
coordinated by a particular faculty. In our proposed system some more featured are
added which differs it from the existing system such as security.
1.2
Objectives of the project
The important objectives if this project are following:
1) To provide a graphical user interface to add or delete the information.
2) To provide the same type of easy to feel type interface to update the records.
3) To provide an interface for feeding the suggestion.
4) To store those suggestions in the database.
5) To secure the data of records in very efficient way.
6) To allow the access of data and software to only the people who are
authenticated.
7) Improved processing speed.
8) Enhance capacity to process a greater amount of activity.
9) Providing ability to conducting complex search.
10) Faster retrieval of information.
1
11) Grater accuracy and consistency.
12) Reducing paper work.
13) Reducing cost.
14) Improved arrangement for event coordination.
MODULES
The proposed project will have its main page and will be mainly divided into partially
dependent and partially independent modules as:
1.
LOGIN FORM
2. MDI FORM
3. ENTRY FORM
4.
DISPLAY FORM
1. LOGIN MODULE
It is first form that is displayed on the display form if user wants to
edit information into the display form. Here the user has to give his login detail to the
system. It consists of one combo box and one text boxes. When the faculty wants to
edit information in the display form has to give his password. Password will be
hidden to the external viewer.
Along with then the form has two buttons, “OK” and “EXIT”. Clicking on “OK”, the
execution moves forward to the second form.
2. MDI FORM
MDI Form is the form in the execution line. All the other forms in project are linked
together by this from only. Pathways to all the other forms go through this module.
This form consists of two options buttons, that is labeled as “open” and “EXIT”.
Users first have to select one of the options that is desired by user. Clicking on any of
the button takes the user to form according to the option selected .Clicking on “Exit”
ends the execution.
2
3. ENTRY FORM
ENTRY form consists of one combo box, five text boxes in the form,
the users has to give the details of new records to be added. He can specify the
category by combo box and also fill up the text boxes provided under the heading of
software details and hardware details of a particular lab. For the purpose of adding
new record and removing record buttons” NEW”,“DELETE” and are provided.
Clicking on “PREVIOUS” or “NEXT” button in the form all entries in the database
are viewed on and “EXIT” clicking will be send back the user to main login form.
4. SEARCH MODULE
Display form contains a data grid to display the faculty’s even
records. Data Grid contains six records. It also contains two commands “edit” and
“exit”. By edit command we can edit information in the Entry form and by “exit”
clicking will be send back the user to main to MDI Form.
3
2.SYSTEM ANALYSIS
2.1 EXISTING SYSTEM
1. Problem of Reliability: Current system is not reliable. It seems to vary in quality
from one month to the next. Some times it gives good output, but some times the
output is worst.
2. Problem of Accuracy: There are too many mistakes in reports.
3. Problem of timeliness: In the current system the reports and output produced is
mostly late and in most of the cases it is useless because it is not on time.
4. Problem of Validity: The output and reports mostly contains misleading
information. The customer's information is sometimes not valid.
5. Problem of Economy: The current system is very costly. We have to spend lots of
money to keep the system up and going, but still not get the desired results.
6. Problem of Capacity: The current system is suffering from problem of capacity
also. The staff for organization is very less and the workload is too much. Few
peoples cannot handle all the work.
DRAWBACKS OF EXISTING SYSTEM

At present the system which is not effective and efficient way.

It does not has the security and authenticity. Any user can access that
system.

The existing system is not user friendly.

It does not have a menu based control which can make a system move
consistent and user friendly.

It requires on expend hand to work on.

If anyone wants to work on, then it requires a special training for this.
4

Unnecessary printing is too much costly.

There is no any file management technique used so it lacks it deserve high
speed data access.
No searching of records is too complex and time consuming.
2.2 PROPOSED SYSTEM
1.
Details: The new proposed system stores and maintains all the faculties
events, students, funds, expenses details.
2. Calculations: The new proposed system updates tables and other
information automatically and it is very fast and accurate.
3. Registers: There is no need of keeping and maintaining salary and
information manually. It remembers each and every record and we can get
any report at any time.
4. Speed: The new proposed system is very fast with 100% accuracy and saves
time.
5. Manpower: The new proposed system needs less manpower. Less people
can do the large work.
6. Efficiency: The new proposed systems complete the work of many people in
less time.
7. Past details: The new proposed system contains the details of every past
Event organized.
8. Reduces redundancy: The most important benefit of this system is that it
reduces the redundancy of data within the data.
9. Work load: Reduces the work load of the data store by helping in easy
updates of the products and providing them with the necessary details
together with financial transactions management.
5
10. Easy statements: Month-end and day-end statement easily taken out without
getting headaches on browsing through the day end statements.
I have designed the given proposed system in the Visual Basic to automate the process
of Event Management System. This project is useful for the authorities who keep
track of all the Event Management System.
The following steps that give the detailed information of the need of proposed system
are:

Performance: During past several decades, the records are supposed to be
manually handled for all activities. The manual handling of the record is time
consuming and highly prone to error. To improve the performance of the system,
the computerized system is to be undertaken. The computerized project is fully
computerized and user friendly even that any of the members can see the report
and status of their enquiries.

Efficiency: The basic need of this project is efficiency. The project should be
efficient so that whenever a new user submits his/her details the project is updated
automatically. This record will be useful for other users instantly.

Control: The complete control of the project is under the hands of authorized
person who has the password to access this project and illegal access is not
supposed to deal with. All the control is under the administrator and the other
members have the rights to just see the records not to change any transaction or
entry.

Security: Security is the main criteria for the proposed system. Since illegal
access may corrupt the database. So security has to be given in this project.
2.3 FEASIBILITY STUDY
The feasibility study is carried out to test whether the proposed system in
words is being implemented.
The feasibility study is based on three major factors
6
ECONOMICAL FEASIBILITY
Economical feasibility is the most recently used method for evaluating
effectiveness of the proposed system .It is obliquely known as cost benefit analysis.
This procedure determined the benefits and savings that are expected from the
proposed system and compared with the cost of the existing system.
In case of the existing system, the hardware in the company is sufficient for
system development and maintenance.
TECHNICAL FEASIBILITY
The hardware, the software and to what extent they can support the proposed
system are the keys for this study .The airways has all the required software
necessary development and maintenance. Taking into consideration of the above
criteria, the proposed system is technically feasible and further developments
could be accomplished easily.
BEHAVIOURAL FEASIBILITY
It is human resist changes in the beginning. Therefore the employees need to be
given training when a system is being implemented for the organization.
The proposed system is highly user interactive so it is easy for end user to
understand the system and use it.
7
3.SYSTEM SPECIFICATION
Visual programming tools are complete programming environments. It allows
programmers to build a GUI program using the various on-screen controls such as
buttons, text, menus, boxes etc. These controls are placed on a form and then the
processing details related with each control are filled.
In the business world, competitive strategies have become the order of the day to
improve quality, cut costs and provide a high response customer service base. Most
organizations today need to be market driven and do a lot of value addition to their
products and services. This naturally calls for rational decision making, which
requires information. Information Technology or IT provides that effective channel to
support and implement this strategy. Client/Server is the technology that empowers
the desktop, thus setting a trend for the way successful organizations will use
technology in the next decade.
3.1 HARDWARE SPECIFICATION
System
:
Pentium IV
RAM
:
128MB
Hard Disk
:
40 GB
Floppy Drive
:
1.44 MB
Monitor
:
14” Color Monitor
Printer
:
Text printer
Keyboard
:
SAMSUNG
Mouse
:
Logitech
3.2 SOFTWARE SPECIFICATION
Operating System
:
Windows XP
Front End
:
Visual Basic .Net 2005
Back End
:
Ms-Access
8
3.3 SOFTWARE DESCRIPTION
Introduction Of Visual Basic.Net
Visual Basic .NET is one of the languages that are directed towards meeting the
objectives of the .NET initiative of creating distributed applications.
Visual Basic .NET is a powerful object-oriented language that provides features such
as abstraction, encapsulation, inheritance, and polymorphism.
Features of Visual Basic .NET

Some of the key features of Visual Basic .NET are as follows:
o Inheritance
o Constructors and destructors
o Overloading
o Overriding
o Structured exception handling
o Multithreading
Visual Studio .NET Integrated Development Environment

The Visual Studio .NET Integrated Development Environment (IDE) provides
you with a common interface for developing various kinds of projects for
the .NET Framework.

In Visual Studio .NET, an application can be made up of one or more items,
such as files and folders. To organize these items efficiently, Visual Studio
.NET has provided two types of containers:
o Projects
o Solutions

The various components of the Visual Studio .NET IDE are:
o The Start Page
o Windows Forms Designer
9
o The Solution Explorer Window
o The Properties Window
o Toolbox
o The Output Window
o The Task List Window
o The Server Explorer Window
o The Dynamic Help Window

Navigational Features in Visual Studio .NET IDE
o The Class View Window
o The Code and Text Editor Window

The Visual Studio .NET IDE also provides three navigational features:
o Docking
o Tabbed navigation
o Auto hide
Windows Form

Is a representation of any window displayed in an application.

Is used to accept input from a user and display information.
Advantages of the .NET Framework

Some advantages of the .NET Framework are:
o Consistent programming model
o Multi-platform applications
o Multi-language integration
o Automatic resource management
o Ease of deployment
Security

Evidence-based security (authentication)

Based on user identity and code identity

Configurable policies

Imperative and declarative interfaces
10
Introduction Of Sql
Structured Query Language, is a computer language designed for the retrieval and
management of data in relational database management systems, database schema
creation and modification, and database object access control management.
SQL has been standardized originally designed as a declarative query and data
manipulation language, variations of SQL have been created by SQL database
management system (DBMS) vendors that add procedural constructs, control-of-flow
statements, user-defined data types, and various other language extensions. With the
release of the SQL: 1999 standard, many such extensions were formally adopted as
part of the SQL language via the SQL Persistent Stored Modules (SQL/PSM) portion
of the standard.
SQL has come under criticism for its lack of cross-platform portability between
vendors, inappropriate handling of missing data , complex three-valued logic system,
and its complex and occasionally ambiguous language grammar and semantics.
Using SQL one can create and maintain data manipulation objects such as table,
views, sequence etc. These data manipulation objects will be created and stroed on the
server's hard disk drive, in a tablespace, to wich the user has been assigned.
Once these data manipulation objects are created, they are used extensively in
commercial applications.
DML, DCL, DDL:
Data manipulation
First, there are the standard Data Manipulation Language (DML) elements. DML is
the subset of the language used to add, update and delete data:

INSERT is used to add rows (formally tuples) to an existing table.

UPDATE is used to modify the values of a set of existing table rows.
11

MERGE is used to combine the data of multiple tables. It is something of a
combination of the INSERT and UPDATE elements. It is defined in the SQL:2003
standard; prior to that, some databases provided similar functionality via different
syntax, sometimes called an "upsert".

DELETE removes zero or more existing rows from a table.
Data control
The third group of SQL keywords is the Data Control Language (DCL). DCL handles
the authorization aspects of data and permits the user to control who has access to see
or manipulate data within the database. Its two main keywords are:

GRANT authorizes one or more users to perform an operation or a set of
operations on an object.

REVOKE removes or restricts the capability of a user to perform an operation
or a set of operations.
Example:
GRANT SELECT, UPDATE ON my_table TO some_user, another_user
Data definition
The second group of keywords is the Data Definition Language (DDL). DDL allows
the user to define new tables and associated elements. Most commercial SQL
databases have proprietary extensions in their DDL, which allow control over
nonstandard features of the database system. The most basic items of DDL are the
CREATE, ALTER, RENAME, TRUNCATE

and DROP statements:
CREATE causes an object (a table, for example) to be created within the
database.

DROP causes an existing object within the database to be deleted, usually
irretrievably.

TRUNCATE deletes all data from a table (non-standard, but common SQL
statement).
12

ALTER statement permits the user to modify an existing object in various
ways -- for example, adding a column to an existing table.
Example:
CREATE TABLE my_table (
My_field1 INT,
My_field2 VARCHAR (50),
My_field3 DATE NOT NULL,
PRIMARY KEY (my_field1, my_field2)
);
In addition to the creationof data manipulation objects, the actual manipulation of data
within these objects is done using SQL.
The SQL sentences that are used to create these objects are called DDL's or Data
Defination Language. The SQL sentences used to manipulate data within these objects
are called DML's or Data Manipulation Language. The SQL sentences, which are
used to control the behavior of these objects, are called DCL's or Data Control
Language.
Hence, once access to the SQL*Plus tool is available and SQL syntex is known, the
creation of data stroage and the manipulation of data within the storage system,
required by commercial applications, is possible.
13
4 SYSTEM DESIGN
The design document that we will develop during this phase is the blueprint of the
software. It describes how the solution to the customer problem is to be built. Since
solution to complex problems isn’t usually found in the first try, iterations are most
likely required. This is true for software design as well. For this reason, any design
strategy, design method, or design language must be flexible and must easily
accommodate changes due to iterations in the design. Any technique or design needs
to support and guide the partitioning process in such a way that the resulting subproblems are as independent as possible from each other and can be combined easily
for the solution to the overall problem. Sub-problem independence and easy
combination of their solutions reduces the complexity of the problem. This is the
objective of the partitioning process. Partitioning or decomposition during design
involves three types of decisions: Define the boundaries along which to break;
Determine into how money pieces to break; and
Identify the proper level of detail when design should stop and implementation should
start.
4.1 INPUT DESIGN
Login Module- This is first module in the project used as authentication module. This
module takes following input
User Name

Password

Type
Faculty Module-This module contains information of event coordinator faculties. It
takes the following input.
14

Faculty Id

Faculty Name

Address

Phone No

Subject
Event Module-this module contain complete information for coordinated event. It
takes the following inputs.

Event Id

Event Name

Event Subject

Faculty Name

Date

Time
4.2 OUTPUT DESIGN
Login Module: Enter username and password and get MDI form if valid.
Faculty Module: Enter faculty Id and get complete information of faculty such as
name, address, phone no. and subject, if valid.
Event Module: Enter event ID or Event name to get and complete information of
coordinated event such as date, time, name and coordinator name.
Basic design principles that enable the software engineer to navigate the design
process suggest a set of principles for software design, which have been adapted and
extended in the following list:
15
Free from the suffer from "tunnel vision." A good designer should consider alternative
approaches, judging each based on the requirements of the problem, the resources
available to do the job.
The design should be traceable to the analysis model. Because a single element of the
design model often traces to multiple requirements, it is necessary to have a means for
tracking how requirements have been satisfied by the design model.
The design should not repeat the same thing. Systems are constructed using a set of
design patterns, many of which have likely been encountered before. These patterns
should always be chosen as an alternative to reinvention. Time is short and resources
are limited! Design time should be invested in representing truly new ideas and
integrating those patterns that already exist.
The design should "minimize the intellectual distance" between the software and the
problem as it exists in the real world. That is, the structure of the software design
should (whenever possible) mimic the structure of the problem domain.
The design should exhibit uniformity and integration. A design is uniform if it appears
that one person developed the entire thing. Rules of style and format should be
defined for a design team before design work begins. A design is integrated if care is
taken in defining interfaces between design components.
The design activity begins when the requirements document for the software to be
developed is available. This may be the SRS for the complete system, as is the case if
the waterfall model is being followed or the requirements for the next "iteration" if the
iterative enhancement is being followed or the requirements for the prototype if the
prototyping is being followed. While the requirements specification activity is entirely
in the problem domain, design is the first step in moving from the problem domain
toward the solution domain. Design is essentially the bridge between requirements
specification and the final solution for satisfying the requirements.
16
The design of a system is essentially a blueprint or a plan for a solution for the
system. We consider a system to be a set of components with clearly defined behavior
that interacts with each other in a fixed defined manner to produce some behavior or
services for its environment. A component of a system can be considered a system,
with its own components. In a software system, a component is a software module.
The design process for software systems, often, has two levels. At the first level, the
focus is on deciding which modules are needed for the system, the specifications of
these modules, and how the modules should be interconnected. This is what is called
the system design or top-level design. In the second level, the internal design of the
modules, or how the specifications of the module can be satisfied, is decided. This
design level is often called detailed design or logic design. Detailed design essentially
expands the system design to contain a more detailed description of the processing
logic and data structures so that the design is sufficiently complete for coding.
Because the detailed design is an extension of system design, the system design
controls the major structural characteristics of the system. The system design has a
major impact on the testability and modifiability of a system, and it impacts its
efficiency. Much of the design effort for designing software is spent creating the
system design.
The input to the design phase is the specifications for the system to be designed.
Hence, reasonable entry criteria can be that the specifications are stable and have been
approved, hoping that the approval mechanism will ensure that the specifications are
complete, consistent, unambiguous, etc. The output of the top-level design phase is
the architectural design or the system design for the software system to be built. This
can be produced with or without using a design methodology. Reasonable exit criteria
for the phase could be that the design has been verified against the input specifications
and has been evaluated and approved for quality.
A design can be object-oriented or function-oriented. In function-oriented design, the
design consists of module definitions, with each module supporting a functional
abstraction. In object-oriented design, the modules in the design represent data
17
abstraction (these abstractions are discussed in more detail later). In the functionoriented methods for design and describe one particular methodology the structured
design methodology in some detail. In a function- oriented design approach, a system
is viewed as a transformation function, transforming the inputs to the desired outputs.
The purpose of the design phase is to specify the components for this transformation
function, so that each component is also a transformation function. Hence, the basic
output of the system design phase, when a function oriented design approach is being
followed, is the definition of all the major data structures in the system, all the major
modules of the system, and how the modules interact with each other.
Once the designer is satisfied with the design he has produced, the design is to be
precisely specified in the form of a document. To specify the design, specification
languages are used. Producing the design specification is the ultimate objective of the
design phase. The purpose of this design document is quite different from that of the
design notation. Whereas a design represented using the design notation is largely to
be used by the designer, a design specification has to be so precise and complete that
it can be used as a basis of further development by other programmers. Generally,
design specification uses textual structures, with design notation helping in
understanding
18
4.3 DATA BASE DESIGN
Data modeling defines primary data objects, composition of each data object,
and attributes of the object, relationships between each object and other objects
and between objects and the processes.
List of Tables:
Admin Table: To store admin username and password.
Fields
Username
Password
Type
Char(30)
Char(30)
Constraint
Not Null
Not Null
Description
Username
Password
Users Table: To store users details. The users are managed by admin.
Fields
Username
Constraint
Not Null
Not Null
Not Null
Description
Username
Password
Email Id
Address
Contact_no
Reg.Amount
Type
Char(30)
Char(30)
Char(30)
Char(30)
Number
Constraint
Primary Key
Not Null
Not Null
Not Null
Not Null
Total Fee
Reg_date
Description
Number(5)
Date
Char(30)
Not Null
Not Null
Not Null
Description
Registration No.
Name
Address
Contact No
Registration
Amount
Total Fee
Registration Date
Description
Constraint
Primary Key
Not Null
Not Null
Not Null
Not Null
Not Null
Not Null
Not Null
Description
Id
Name
Address
City
State
Subject
Specialization
Qualification
Password
Email
Type
Char(30)
Char(30)
Char(30)
Students: To store student details
Fields
Reg no.
Name
Faculty: To store faculty details
Fields
ID
Name
Address
City
State
Subject
Specialization
Qualification
Type
Char(30)
Char(30)
Char(30)
Char(30)
Char(30)
Char(30)
Char(30)
Char(30)
19
Funds: To store funds details.
Fields
Transaction_Id
Donor
Amount
Date_of_deps
Type
Char(30)
Char(50)
Number(6)
Date
Constraint
Primary Key
Not Null
Not Null
Not Null
Description
Transaction
Donor
Amount
Date
Expenses: To store details of the expenses for event Management system.
Fields
Expenses_amount
Constraint
Not Null
Not Null
Not Null
Description
Expenses amount
Date of withdrawl
Description
Subject
Faculty_name
Type
Char(30)
Char(50)
Char(50)
Char(50)
Constraint
Primary Key
Not Null
Not Null
Not Null
Date_of_event
Time
Date
Char(30)
Not Null
Not Null
Description
Event ID
Event Name
Subject
Arranged
Faculty
Date of event
Time
Date_of_withdrawl
Description
Type
Number(8)
Date
Char(200)
Event: To store event Details
Fields
Event_Id
Event_Name
20
by
ENTITY RELATIONSHIP DIAGRAM (ERD)
Entity – Relationship Diagram: This depicts relationship between data objects. The
attribute of each data objects noted in the entity- relationship diagram can be
described using a data object description. Data flow diagram serves two purposes:
1. To provide an indication of how data are transformed as they move through the
system.
2. To depict the functions that transformation the data flow.
Data Objects: A data object is a representation of almost any composite information
that must be understood by the software. By composite information, we mean
something that has a number of different properties or attributes. A data object
encapsulates data only there is no reference within a data object to operations that act
on the data.
Attributes: Attributes define the properties of a data object and take on one of three
different characteristics. They can be used to:
Name an instance of data object.
Describe the instance.
Make reference to another instance in other table.
Relationships: Data objects are connected to one another in a variety of different
ways. We can define a set of object relationship pairs that define the relevant
relationships.
21
4.4. DATA FLOW DIAGRAM
CONTEXT LEVEL DFD FOR EVENT MANAGEMENT SYSTEM
1.
ADMIN
2.
STUDENT
3.
FACULTY
EVENT
MANAGEMENT
SYSTEM
6.
EVENT
SCHEDULER
4.
ADD EVENT
5.
BUDGET OF
EVENT
22
Ist Level DFD for Admin
1.1
Accept
the user
name &
Password
ADMIN
1.2
Validate
the
Admin
EVENT
MANAGEMENT
SYSTEM
ADMIN
23
Ist Level DFD For the students
2.2
Accept
the
student
details
STUDENT
2.4
update
students
2.2
Validate
students
EVENT
MANAGEMENT
SYSTEM
STUDENT
2.4
Update
students
2.3
Faculty
Manager
s Even
FACULTY
EVENTS
24
Ist Level DFD for the Faculty
3.1
Accept
the
Faculty
Details
FACULTY
3.2
Validate
Faculty
EVENT
MANAGEMENT
SYSTEM
FACULTY
3.3
Faculty
manages
the
Student &
Events
EVENS
25
Ist Level DFD For event Management
4.1
Accept
the Event
Requests
ADMIN
4.4
Approved
Budget &
Expenses
4.2
Validate
the
Events
EVENT
MANAGEMENT
SYSTEM
4.3
Coordinat
e Faculty
Event
4.5
Coordina
te
Students
Students
FacultyS
26
5 SYSTEM TESTING
One of the purposes of the testing is to validate and verify the system. Verification
means checking the system to ensure that it is doing what the function is supposed to
do and Validation means checking to ensure that system is doing what the user wants
it to do.
No program or system design is perfect; communication between the user and the
designer is not always complete or clear, and time is usually short. The result is errors
and more errors. Theoretically, a newly designed system should have all the pieces in
working order, but in reality, each piece works independently. Now is the time to put
all the pieces into one system and test it to determine whether it meets the user's
requirements. This is the best chance to detect and correct errors before the system is
implemented. The purpose of system testing is to consider all the likely variations to
which it will be subjected and then push the system to its limits. If we implement the
system without proper testing then it might cause the problems.
1. Communication between the user and the designer.
2. The programmer's ability to generate a code that reflects
exactly the system specification.
3. The time frame for the design.
Theoretically, a new designed system should have all the pieces in working order, but
in reality, each piece works independently. Now is the time to put all the pieces into
one system and test it to determine whether it meets the requirements of the user. The
process of system testing and the steps taken to validate and prepare a system for final
implementation are:
27
1. UNIT TESTING:
This is the smallest testable unit of a computer system and is
normally tested using the white box testing. The author of the programs
usually carries out unit tests.
2. INTEGRATION TESTING:
In integration testing, the different units of the system are integrated
together to form the complete system and this type of testing checks the system as
whole to ensure that it is doing what is supposed to do. The testing of an integrated
system can be carried out top-down, bottom-up, or big-bang. In this type of testing,
some parts will be tested with white box testing and some with black box testing
techniques. This type of testing plays very important role in increasing the systems
productivity. We have checked our system by using the integration testing techniques.
3. SYSTEM TESTING:
A part from testing the system to validate the functionality of
software against the requirements, it is also necessary to test the non-functional aspect
of the system. Some examples of non-functional tools include tests to check
performance, data security, usability/user friendliness, volume, load/stress that we
have used in our project to test the various modules.
System testing consists of the following steps:
1. Program(s) testing.
2. String testing.
3. System testing.
4. System documentation.
5. User acceptance testing.
4. FIELD TESTING:
This is a special type of testing that may be very important in some
projects. Here the system is tested in the actual operational surroundings. The
28
interfaces with other systems and the real world are checked. This type of testing is
very rarely used. So far our project is concerned; we haven't tested our project using
the field testing.
5. ACCEPTANCE TESTING:
After the developer has completed all rounds of testing and he is
satisfied with the system, then the user takes over and re-tests the system from his
point of view to judge whether it is acceptable according to some previously
identified criteria. This is almost always a tricky situation in the project because of the
inherent conflict between the developer and the user. In this project, it is the job of the
bookstores to check the system that whether the made system fulfills the goals or not.
29
6. SYSTEM IMPLEMENTATION
As we know, creating software is one thing and the implementation of the created
software is another. The process of implementing software is much difficult as
compared to the task of creating the project. First we have to implement the software
on a small scale for removing the bugs and other errors in the project and after
removing them we can implement the software on a large scale. Before we think in
terms of implementing the Software on a large basis, we must consider the Hardware
requirements.
Whenever we develop software or project a certain hardware and software is being
used by the programmer for developing the project. The hardware and software to be
used by the programmer for developing the project should be such that it would result
in the development of a project, which would satisfy all the basic needs for which the
project has been created by the programmer. The Hardware should be such that cost
constraints of the Client should also be taken into account without affecting the
performance.
30
7. SYSTEM MAINTENANCE AND SECURITY
Software’s Vulnerability to Attack
Software development is not yet a science or a rigorous discipline, and the
development process by and large is not controlled to minimize the vulnerabilities that
attackers exploit.
The security of software is threatened at various points throughout its life cycle, both
by inadvertent and intentional choices and actions taken by “insiders”—individuals
closely affiliated with the organization that is producing, deploying, operating, or
maintaining the software, and thus trusted by that organization—and by “outsiders”
who have no affiliation with the organization. The software’s security can be
threatened.

During its development: A developer may corrupt the software—
intentionally or unintentionally—in ways that will compromise the software’s
dependability and trustworthiness when it is operational.

During its deployment (distribution and installation): If those responsible
for distributing the software fail to tamperproof the software before shipping
or uploading, or transmit it over easily intercepted communications channels,
they leave the software vulnerable to intentional or unintentional corruption.
Similarly, if the software’s installer fails to “lock down” the host platform, or
configures the software insecurely, the software is left vulnerable to access by
attackers.

During its operation: Once COTS and open source software has gone
operational, vulnerabilities may be discovered and publicized; unless security
patches and updates are applied and newer supported versions (from which the
root causes of vulnerabilities have been eliminated) are adopted, such software
will become increasingly vulnerable. Non-commercial software and open
source software (OSS) may also be vulnerable, especially as it may manifest
untrustworthy behaviors over time due to changes in its environment that
31
stress the software in ways that were not anticipated and simulated during its
testing.

During its sustainment: If those responsible for addressing discovered
vulnerabilities in released software fail to issue patches or updates in a timely
manner, or fail to seek out and eliminate the root causes of the vulnerabilities
to prevent their perpetuation in future releases of the software, the software
will become increasingly vulnerable to threats over time. Also, the software’s
maintainer may prove to be a malicious insider, and may embed malicious
code, exploitable flaws, etc., in updated versions of the code.
The Challenge of Building Secure Software:1.
Dependability: Dependable software executes predictably and operates
correctly under all conditions, including hostile conditions, including when the
software comes under attack or runs on a malicious host.
2.
Trustworthiness: Trustworthy software contains few if any vulnerabilities or
weaknesses that can be intentionally exploited to subvert or sabotage the
software’s dependability. In addition, to be considered trustworthy, the
software must contain no malicious logic that causes it to behave in a
malicious manner.
Survivability (also referred to as “Resilience”): Survivable—or resilient—software
is software that is resilient enough to (1) either resist (i.e., protect itself against) or
tolerate (i.e., continue operating dependably in spite of) most known attacks plus as
many novel attacks as possible, and (2) recover as quickly as possible, and with as
little damage as possible, from those attacks that it can neither resist nor tolerate
32
8. SCOPE OF FUTURE APPLICATION
The whole project as we have seen is totally based upon the database maintenance.
This could be the most vital thing that the Indian industry asks for these days. This
phenomenon is not only confined to big industries, but amazingly what that a
common man deals with everyday in his life. This phenomenon starts from a common
man to big industries like railways. Not only has their database had to upgraded very
often. There is no denying the fact that one can say that the company’ progress solely
depends on how fast the database accessing goes on.
Certainly database accessing has given boon to the companies if Indian industries and
will have major role in upcoming of leading industries. Database accessing is what
each firm will ask for in the coming future. Database is what they required in each
field.
Therefore the database is the future of computer industry.
33
9.CONCLUSION
This project is designed to meet the requirements of Event Management in Colleges.
It is developed in Visual Basic.Net, keeping in mind the specifications of the system.
For designing the system we have used simple data flow diagrams.
Overall the project teaches us the essential skills like:

Using system analysis and design techniques like data flow diagram in designing
the system.

Understanding the database handling and query processing
34
10. BIBLIOGRAPHY
1. Visual Basic
Jamew Foxall
2. Fundamentals Of Software Engineering
Rajib Mall
3. Software Engineering
K.K.Aggarwal & Yogesh Singh
4. Visual Basic Projects
Tony Martin, Dominic Selly
5. Visual Basic Professional Projects
Kuljit Kaur,Pooja Bembey
6. Using SQL-SERVER 2000, Microsoft publication
7. SQL-SERVER 2000 BPB publication
35
ANNEXURE
Source Code
Login Form
Imports System.Data.SqlClient
Public Class login
Dim DATATAB, datatab1, datatab2 As New DataTable
Private Sub ok_Click(ByVal sender As System.Object, ByVal e As
System.EventArgs) Handles ok.Click
Call start()
DA = New SqlDataAdapter("SELECT * FROM users where
username='" + TextBox1.Text + "' and password='" + TextBox2.Text + "'
", CN)
CM = New SqlCommandBuilder(DA)
DA.Fill(DATATAB)
ROWNO = 0
Dim s1 As String = Trim(DATATAB.Rows(ROWNO)(0).ToString)
Dim s2 As String = Trim(DATATAB.Rows(ROWNO)(1).ToString)
If TextBox1.Text = s1 And TextBox2.Text = s2 Then
uname = TextBox1.Text
uid = TextBox2.Text
Dim obj As New menu
obj.Show()
Me.Hide()
Else
36
MsgBox("invalid Password")
TextBox1.Text = ""
TextBox2.Text = ""
TextBox1.Focus()
End If
CN.Close()
End Sub
Private Sub TextBox2_Validating(ByVal sender As System.Object,
ByVal e As System.ComponentModel.CancelEventArgs) Handles
TextBox2.Validating
If TextBox2.Text = "" Then
MsgBox("Password Should not be blank")
TextBox2.Focus()
End If
If Len(TextBox2.Text) > 8 Then
MsgBox("Password should be of maximum 8 character")
TextBox2.Text = ""
TextBox2.Focus()
End If
End Sub
Private Sub TextBox1_Validating1(ByVal sender As Object, ByVal e
As System.ComponentModel.CancelEventArgs) Handles TextBox1.Validating
If TextBox1.Text = "" Then
MsgBox("UserName Should not be blank")
TextBox1.Focus()
End If
If Len(TextBox1.Text) > 8 Then
MsgBox("UserName should be of maximum 8 character")
TextBox1.Text = ""
TextBox1.Focus()
End If
End Sub
Private Sub Panel2_Paint(ByVal sender As System.Object, ByVal e
As System.Windows.Forms.PaintEventArgs) Handles Panel2.Paint
End Sub
Private Sub login_Load(ByVal sender As System.Object, ByVal e As
System.EventArgs) Handles MyBase.Load
End Sub
End Class
37
MDI Form
Imports System.Windows.Forms
Public Class menu
Private Sub AdminToolStripMenuItem_Click(ByVal sender As
System.Object, ByVal e As System.EventArgs) Handles Student.Click
Dim obj As New student
obj.MdiParent = Me
obj.Show()
End Sub
Private Sub AboutCCMSToolStripMenuItem_Click(ByVal sender As
System.Object, ByVal e As System.EventArgs)
Dim obj As New frmAboutus
obj.MdiParent = Me
obj.Show()
End Sub
Private Sub menu_Load(ByVal sender As System.Object, ByVal e As
System.EventArgs) Handles MyBase.Load
End Sub
Private Sub EnterpriseRecordToolStripMenuItem_Click(ByVal sender
As System.Object, ByVal e As System.EventArgs)
Dim obj As New UPDATESTUDENT
38
obj.MdiParent = Me
obj.Show()
End Sub
Private Sub Courses_Click(ByVal sender As System.Object, ByVal e
As System.EventArgs) Handles Courses.Click
Dim obj As New DELSTUDENT
obj.MdiParent = Me
obj.Show()
End Sub
Private Sub AdminToolStripMenuItem_Click_1(ByVal sender As
System.Object, ByVal e As System.EventArgs) Handles
AdminToolStripMenuItem.Click
Dim obj As New frmmaster
obj.MdiParent = Me
obj.Show()
End Sub
Private Sub CheckStatusToolStripMenuItem_Click(ByVal sender As
System.Object, ByVal e As System.EventArgs) Handles
CheckStatusToolStripMenuItem.Click
End
End Sub
Private Sub StudentToolStripMenuItem_Click(ByVal sender As
System.Object, ByVal e As System.EventArgs) Handles
StudentToolStripMenuItem.Click
Dim obj As New Enquiry
Type = "Student"
obj.MdiParent = Me
obj.Show()
End Sub
Private Sub FacultyToolStripMenuItem_Click(ByVal sender As
System.Object, ByVal e As System.EventArgs)
Dim obj As New Enquiry
type = "Faculty"
obj.MdiParent = Me
obj.Show()
End Sub
Private Sub ConfirmAddmissionToolStripMenuItem_Click(ByVal sender
As System.Object, ByVal e As System.EventArgs) Handles
ConfirmAddmissionToolStripMenuItem.Click
Dim obj As New eventdet
obj.MdiParent = Me
obj.Show()
End Sub
Private Sub StudentsDetailsToolStripMenuItem_Click(ByVal sender
As System.Object, ByVal e As System.EventArgs) Handles
StudentsDetailsToolStripMenuItem.Click
Dim obj As New STUDENT_REPO
obj.MdiParent = Me
39
obj.Show()
End Sub
Private Sub FacultyToolStripMenuItem1_Click(ByVal sender As
System.Object, ByVal e As System.EventArgs)
Dim obj As New faculty_repo
obj.MdiParent = Me
obj.Show()
End Sub
Private Sub GroupsDetailsToolStripMenuItem_Click(ByVal sender As
System.Object, ByVal e As System.EventArgs)
Dim obj As New GROUP_REPO
obj.MdiParent = Me
obj.Show()
End Sub
Private Sub AddDetailsToolStripMenuItem_Click(ByVal sender As
System.Object, ByVal e As System.EventArgs) Handles
AddDetailsToolStripMenuItem.Click
End Sub
Private Sub ADDNewEventsToolStripMenuItem_Click(ByVal sender As
System.Object, ByVal e As System.EventArgs) Handles
ADDNewEventsToolStripMenuItem.Click
Dim obj As New Addevent
obj.MdiParent = Me
obj.Show()
End Sub
Private Sub UpdateDeleteEventsToolStripMenuItem_Click(ByVal
sender As System.Object, ByVal e As System.EventArgs) Handles
UpdateDeleteEventsToolStripMenuItem.Click
Dim obj As New delupdate
obj.MdiParent = Me
obj.Show()
End Sub
Private Sub EnquiryDetailsToolStripMenuItem_Click(ByVal sender As
System.Object, ByVal e As System.EventArgs) Handles
EnquiryDetailsToolStripMenuItem.Click
Dim obj As New faculty_repo
obj.MdiParent = Me
obj.Show()
End Sub
Private Sub UserManagerToolStripMenuItem_Click(ByVal sender As
System.Object, ByVal e As System.EventArgs) Handles
UserManagerToolStripMenuItem.Click
End Sub
40
Private Sub FacultyDetailsToolStripMenuItem_Click(ByVal sender As
System.Object, ByVal e As System.EventArgs) Handles
FacultyDetailsToolStripMenuItem.Click
Dim obj As New Enquiry
obj.MdiParent = Me
obj.Show()
End Sub
Private Sub CourseDetailsToolStripMenuItem_Click(ByVal sender As
System.Object, ByVal e As System.EventArgs) Handles
CourseDetailsToolStripMenuItem.Click
Dim obj As New Enquiry
obj.MdiParent = Me
obj.Show()
End Sub
Private Sub AddToolStripMenuItem_Click(ByVal sender As
System.Object, ByVal e As System.EventArgs) Handles
AddToolStripMenuItem.Click
Dim obj As New Funds
obj.MdiParent = Me
obj.Show()
End Sub
Private Sub ExpensesDetailsToolStripMenuItem_Click(ByVal sender
As System.Object, ByVal e As System.EventArgs) Handles
ExpensesDetailsToolStripMenuItem.Click
Dim obj As New Expenses
obj.MdiParent = Me
obj.Show()
End Sub
Private Sub ExpensesToolStripMenuItem_Click(ByVal sender As
System.Object, ByVal e As System.EventArgs) Handles
ExpensesToolStripMenuItem.Click
Dim obj As New Expenses_repo
obj.MdiParent = Me
obj.Show()
End Sub
Private Sub FundDepositedToolStripMenuItem_Click(ByVal sender As
System.Object, ByVal e As System.EventArgs) Handles
FundDepositedToolStripMenuItem.Click
Dim obj As New Funds_repo
obj.MdiParent = Me
obj.Show()
End Sub
End Class
41
Student add details
Imports System.Data.SqlClient
Public Class student
Dim DATATAB, datatab1, datatab2 As New DataTable
Private Sub student_Load(ByVal sender As System.Object, ByVal e
As System.EventArgs) Handles MyBase.Load
start()
DA = New SqlDataAdapter("select * from STUDENT", CN)
CM = New SqlCommandBuilder(DA)
DA.Fill(DATATAB)
da1 = New SqlDataAdapter("select * from course", CN)
cm1 = New SqlCommandBuilder(da1)
da1.Fill(datatab1)
combobox1.datasource = datatab1
ComboBox1.DisplayMember = "course_id"
da2 = New SqlDataAdapter("select * from groupi", CN)
cm2 = New SqlCommandBuilder(da2)
da2.Fill(datatab2)
ComboBox2.DataSource = datatab2
ComboBox2.DisplayMember = "group_id"
TextBox1.Text = "E001" & DATATAB.Rows.Count + 1
CN.Close()
ROWNO = 0
42
End Sub
Private Sub Button1_Click(ByVal sender As System.Object, ByVal e
As System.EventArgs) Handles Button1.Click
If (MessageBox.Show("Do You want to add this Record in your
Database", "ADD", MessageBoxButtons.YesNo,
MessageBoxIcon.Exclamation) = DialogResult.Yes) Then
If TextBox10.Text = "" Or TextBox7.Text = "" Or
TextBox11.Text = "" Or TextBox2.Text = "" Or TextBox3.Text = "" Or
TextBox4.Text = "" Or TextBox5.Text = "" Or TextBox6.Text = "" Then
MsgBox("FIELD SHOULD NOT BE EMPTY")
Else
Dim newrow As DataRow = DATATAB.NewRow
ROWNO = ROWNO + 1
newrow(0) = TextBox1.Text
newrow(1) = TextBox2.Text
newrow(2) = TextBox3.Text
newrow(3) = TextBox4.Text
newrow(4) = TextBox5.Text
newrow(5) = TextBox6.Text
newrow(6) = TextBox7.Text
newrow(7) = ComboBox1.Text
newrow(8) = ComboBox2.Text
newrow(9) = TextBox10.Text
newrow(10) = TextBox11.Text
DATATAB.Rows.InsertAt((newrow), ROWNO)
DA.Update(DATATAB)
MsgBox("DATA INSERTED")
TextBox1.Text = ""
TextBox2.Text = ""
TextBox3.Text = ""
TextBox4.Text = ""
TextBox5.Text = ""
TextBox6.Text = ""
TextBox7.Text = ""
'TextBox8.Text = ""
'TextBox9.Text = ""
TextBox10.Text = ""
TextBox11.Text = ""
CN.Close()
DATATAB.Clear()
start()
DA = New SqlDataAdapter("select * from STUDENT", CN)
CM = New SqlCommandBuilder(DA)
DA.Fill(DATATAB)
TextBox1.Text = "E001" & DATATAB.Rows.Count + 1
CN.Close()
ROWNO = 0
43
End If
End If
End Sub
End Class
Del student
Imports System.Data.SqlClient
Public Class DELSTUDENT
Dim DATATAB, datatab1, datatab2 As New DataTable
Private Sub Button1_Click(ByVal sender As System.Object, ByVal e
As System.EventArgs) Handles Button1.Click
If (MessageBox.Show("Do You want to DELETE this Record from
your Database", "DELETE", MessageBoxButtons.YesNo,
MessageBoxIcon.Exclamation) = DialogResult.Yes) Then
start()
Dim CMD As SqlCommand = New SqlCommand("DELETE FROM
STUDENT WHERE REG_NO='" & TextBox1.Text & "'", CN)
CMD.ExecuteNonQuery()
CN.Close()
MsgBox("Record Deleted")
TextBox1.Text = ""
End If
End Sub
End Class
44
Admin Login
Imports System.Data.SqlClient
Public Class frmmaster
Dim DATATAB, datatab1, datatab2 As New DataTable
Private Sub frmmaster_Load(ByVal sender As System.Object, ByVal e
As System.EventArgs) Handles MyBase.Load
End Sub
Private Sub LinkLabel1_LinkClicked(ByVal sender As System.Object,
ByVal e As System.Windows.Forms.LinkLabelLinkClickedEventArgs)
Handles LinkLabel1.LinkClicked
Dim obj As New newusers
obj.Show()
End Sub
Private Sub Button1_Click_1(ByVal sender As System.Object, ByVal
e As System.EventArgs) Handles Button1.Click
Call start()
DA = New SqlDataAdapter("SELECT * FROM admin where
username='" + TextBox1.Text + "' and password='" + TextBox2.Text + "'
", CN)
CM = New SqlCommandBuilder(DA)
DA.Fill(DATATAB)
45
ROWNO = 0
Dim s1 As String = Trim(DATATAB.Rows(ROWNO)(0).ToString)
Dim s2 As String = Trim(DATATAB.Rows(ROWNO)(1).ToString)
If TextBox1.Text = s1 And TextBox2.Text = s2 Then
Panel1.Visible = False
Panel2.Visible = True
Else
MsgBox("invalid Password")
TextBox1.Focus()
End If
CN.Close()
End Sub
Private Sub LinkLabel4_LinkClicked(ByVal sender As System.Object,
ByVal e As System.Windows.Forms.LinkLabelLinkClickedEventArgs)
Handles LinkLabel4.LinkClicked
Dim obj As New changepass
obj.Show()
End Sub
End Class
Master login
Imports System.Data.SqlClient
46
Public Class frmmaster
Dim DATATAB, datatab1, datatab2 As New DataTable
Private Sub frmmaster_Load(ByVal sender As System.Object, ByVal e
As System.EventArgs) Handles MyBase.Load
End Sub
Private Sub LinkLabel1_LinkClicked(ByVal sender As System.Object,
ByVal e As System.Windows.Forms.LinkLabelLinkClickedEventArgs)
Handles LinkLabel1.LinkClicked
Dim obj As New newusers
obj.Show()
End Sub
Private Sub Button1_Click_1(ByVal sender As System.Object, ByVal
e As System.EventArgs) Handles Button1.Click
Call start()
DA = New SqlDataAdapter("SELECT * FROM admin where
username='" + TextBox1.Text + "' and password='" + TextBox2.Text + "'
", CN)
CM = New SqlCommandBuilder(DA)
DA.Fill(DATATAB)
ROWNO = 0
Dim s1 As String = Trim(DATATAB.Rows(ROWNO)(0).ToString)
Dim s2 As String = Trim(DATATAB.Rows(ROWNO)(1).ToString)
If TextBox1.Text = s1 And TextBox2.Text = s2 Then
Panel1.Visible = False
Panel2.Visible = True
Else
MsgBox("invalid Password")
TextBox1.Focus()
End If
CN.Close()
End Sub
Private Sub LinkLabel4_LinkClicked(ByVal sender As System.Object,
ByVal e As System.Windows.Forms.LinkLabelLinkClickedEventArgs)
Handles LinkLabel4.LinkClicked
Dim obj As New changepass
obj.Show()
End Sub
End Class
47
New user
Imports System.Data.SqlClient
Public Class newusers
Dim DATATAB, datatab1, datatab2 As New DataTable
Private Sub ok_Click(ByVal sender As System.Object, ByVal e As
System.EventArgs) Handles ok.Click
If (MessageBox.Show("Do You want to add this Record in your
Database", "ADD", MessageBoxButtons.YesNo,
MessageBoxIcon.Exclamation) = DialogResult.Yes) Then
If TextBox1.Text = "" Or TextBox2.Text = "" Then
MsgBox("FIELD SHOULD NOT BE EMPTY")
Else
Dim newrow As DataRow = DATATAB.NewRow
ROWNO = ROWNO + 1
newrow(0) = TextBox1.Text
newrow(1) = TextBox2.Text
DATATAB.Rows.InsertAt((newrow), ROWNO)
DA.Update(DATATAB)
MsgBox("DATA UPDATED")
CN.Close()
End If
End If
End Sub
Private Sub newusers_Load(ByVal sender As System.Object, ByVal e
As System.EventArgs) Handles MyBase.Load
start()
DA = New SqlDataAdapter("select * from users", CN)
48
CM = New SqlCommandBuilder(DA)
DA.Fill(DATATAB)
CN.Close()
ROWNO = 0
End Sub
Private Sub SHOWCURRENTRECORD()
If rowno = datatab.Rows.Count Then
TextBox1.Text = ""
TextBox2.Text = ""
Else
TextBox1.Text = DATATAB.Rows(ROWNO)(0).ToString
TextBox2.Text = DATATAB.Rows(ROWNO)(1).ToString
End If
End Sub
End Class
Change password
Imports System.Data.SqlClient
Public Class changepass
Private Sub conpassword_Click(ByVal sender As System.Object,
ByVal e As System.EventArgs) Handles conpassword.Click
Panel1.Visible = True
Panel1.Location = New System.Drawing.Point(80, 32)
Panel2.Visible = False
End Sub
Private Sub change_Click(ByVal sender As System.Object, ByVal e
As System.EventArgs) Handles change.Click
start()
Dim up As New SqlCommand("update users set password='" &
TextBox2.Text & "' where username='" & TextBox1.Text & "'", CN)
DA.UpdateCommand = up
DA.UpdateCommand.ExecuteNonQuery()
49
MsgBox("PASSWORD CHANGED")
conpassword.Visible = True
CN.Close()
End Sub
Private Sub ok_Click(ByVal sender As System.Object, ByVal e As
System.EventArgs) Handles ok.Click
start()
DA = New SqlDataAdapter("SELECT * FROM users where
password='" & TextBox4.Text & "' and username='" & TextBox3.Text &
"'", CN)
CM = New sqlCommandBuilder(DA)
DA.Fill(DATATAB)
ROWNO = 0
If DATATAB.Rows.Count > 0 Then
Me.Hide()
Dim obj As New menu
obj.Show()
Else
MsgBox("invalid Password")
End If
CN.Close()
End Sub
Private Sub changepass_Load(ByVal sender As System.Object, ByVal
e As System.EventArgs) Handles MyBase.Load
start()
DA = New SqlDataAdapter("SELECT * FROM users", CN)
CM = New SqlCommandBuilder(DA)
DA.Fill(DATATAB)
CN.Close()
End Sub
End Class
50
Enquiry form
Imports System.Data.SqlClient
Public Class Enquiry
Dim DATATAB, datatab1, datatab2 As New DataTable
Private Sub Enquiry_Load(ByVal sender As System.Object, ByVal e
As System.EventArgs) Handles MyBase.Load
start()
DA = New SqlDataAdapter("select * from faculty", CN)
CM = New SqlCommandBuilder(DA)
DA.Fill(DATATAB)
TextBox1.Text = "E001" & DATATAB.Rows.Count + 1
CN.Close()
ROWNO = 0
End Sub
Private Sub Button1_Click(ByVal sender As System.Object, ByVal e
As System.EventArgs) Handles Button1.Click
If (MessageBox.Show("Do You want to add this Record in your
Database", "ADD", MessageBoxButtons.YesNo,
MessageBoxIcon.Exclamation) = DialogResult.Yes) Then
If TextBox8.Text = "" Or TextBox7.Text = "" Or
TextBox2.Text = "" Or TextBox3.Text = "" Or TextBox4.Text = "" Or
TextBox5.Text = "" Or TextBox6.Text = "" Then
MsgBox("FIELD SHOULD NOT BE EMPTY")
Else
Dim newrow As DataRow = DATATAB.NewRow
ROWNO = ROWNO + 1
newrow(0) = TextBox1.Text
newrow(1) = TextBox2.Text
51
newrow(2) = TextBox3.Text
newrow(3) = TextBox4.Text
newrow(4) = TextBox5.Text
newrow(5) = TextBox6.Text
newrow(6) = TextBox7.Text
newrow(7) = TextBox8.Text
DATATAB.Rows.InsertAt((newrow), ROWNO)
DA.Update(DATATAB)
MsgBox("DATA INSERTED")
TextBox1.Text = ""
TextBox2.Text = ""
TextBox3.Text = ""
TextBox4.Text = ""
TextBox5.Text = ""
TextBox6.Text = ""
TextBox7.Text = ""
TextBox8.Text = ""
CN.Close()
start()
DATATAB.Clear()
DA = New SqlDataAdapter("select * from ENQUIRY", CN)
CM = New SqlCommandBuilder(DA)
DA.Fill(DATATAB)
TextBox1.Text = "E001" & DATATAB.Rows.Count + 1
CN.Close()
ROWNO = 0
End If
End If
End Sub
Private Sub Label1_Click(ByVal sender As System.Object, ByVal e
As System.EventArgs) Handles Label1.Click
End Sub
Private Sub Label2_Click(ByVal sender As System.Object, ByVal e
As System.EventArgs) Handles Label2.Click
End Sub
Private Sub Label3_Click(ByVal sender As System.Object, ByVal e
As System.EventArgs) Handles Label3.Click
End Sub
Private Sub Label4_Click(ByVal sender As System.Object, ByVal e
As System.EventArgs) Handles Label4.Click
End Sub
Private Sub Label5_Click(ByVal sender As System.Object, ByVal e
As System.EventArgs) Handles Label5.Click
End Sub
52
Private Sub Label6_Click(ByVal sender As System.Object, ByVal e
As System.EventArgs) Handles Label6.Click
End Sub
Private Sub Label7_Click(ByVal sender As System.Object, ByVal e
As System.EventArgs) Handles Label7.Click
End Sub
Private Sub Label8_Click(ByVal sender As System.Object, ByVal e
As System.EventArgs) Handles Label8.Click
End Sub
Private Sub Label9_Click(ByVal sender As System.Object, ByVal e
As System.EventArgs) Handles Label9.Click
End Sub
Private Sub TextBox8_TextChanged(ByVal sender As System.Object,
ByVal e As System.EventArgs) Handles TextBox8.TextChanged
End Sub
Private Sub TextBox1_TextChanged(ByVal sender As System.Object,
ByVal e As System.EventArgs) Handles TextBox1.TextChanged
End Sub
Private Sub TextBox2_TextChanged(ByVal sender As System.Object,
ByVal e As System.EventArgs) Handles TextBox2.TextChanged
End Sub
Private Sub TextBox3_TextChanged(ByVal sender As System.Object,
ByVal e As System.EventArgs) Handles TextBox3.TextChanged
End Sub
Private Sub TextBox4_TextChanged(ByVal sender As System.Object,
ByVal e As System.EventArgs) Handles TextBox4.TextChanged
End Sub
Private Sub TextBox5_TextChanged(ByVal sender As System.Object,
ByVal e As System.EventArgs) Handles TextBox5.TextChanged
End Sub
Private Sub TextBox6_TextChanged(ByVal sender As System.Object,
ByVal e As System.EventArgs) Handles TextBox6.TextChanged
End Sub
Private Sub TextBox7_TextChanged(ByVal sender As System.Object,
ByVal e As System.EventArgs) Handles TextBox7.TextChanged
End Sub
End Class
53
Events details
Imports System
Imports System.Data.SqlClient
Public Class eventdet
Dim DATATAB, datatab1, datatab2 As New DataTable
Private Sub Button1_Click(ByVal sender As System.Object, ByVal e
As System.EventArgs) Handles Button1.Click
MsgBox(ComboBox1.Text & ComboBox1.SelectedIndex)
Dim s As String = ComboBox1.Text
Dim sql As String = ""
Select Case ComboBox1.SelectedIndex
Case 0
sql = "select * from event where event_id='" &
TextBox1.Text & "'"
Case 1
sql = "select * from event where event_name='" &
TextBox1.Text & "'"
Case 2
sql = "select * from event where event_sub='" &
TextBox1.Text & "'"
Case 3
sql = "select * from event where dat='" &
TextBox1.Text & "'"
54
End Select
DATATAB.Clear()
start()
DA = New SqlDataAdapter(sql, CN)
CM = New SqlCommandBuilder(DA)
DATATAB.Clear()
DA.Fill(DATATAB)
CN.Close()
ROWNO = 0
TextBox7.Text
TextBox2.Text
TextBox3.Text
TextBox4.Text
TextBox5.Text
TextBox6.Text
=
=
=
=
=
=
DATATAB.Rows(ROWNO)(0).ToString
DATATAB.Rows(ROWNO)(1).ToString
DATATAB.Rows(ROWNO)(2).ToString
DATATAB.Rows(ROWNO)(3).ToString
DATATAB.Rows(ROWNO)(4).ToString
DATATAB.Rows(ROWNO)(5).ToString
End Sub
End Class
Add new events
Imports System.Data.SqlClient
Public Class Addevent
Dim DATATAB, datatab1, datatab2 As New DataTable
Private Sub Button1_Click(ByVal sender As System.Object, ByVal e
As System.EventArgs) Handles Button1.Click
55
If (MessageBox.Show("Do You want to add this Record in your
Database", "ADD", MessageBoxButtons.YesNo,
MessageBoxIcon.Exclamation) = DialogResult.Yes) Then
If TextBox2.Text = "" Or TextBox3.Text = "" Or
TextBox4.Text = "" Or TextBox5.Text = "" Then
MsgBox("FIELD SHOULD NOT BE EMPTY")
Else
Dim newrow As DataRow = DATATAB.NewRow
ROWNO = ROWNO + 1
newrow(0) = TextBox1.Text
newrow(1) = TextBox2.Text
newrow(2) = TextBox3.Text
newrow(3) = TextBox4.Text
newrow(4) = TextBox5.Text
newrow(5) = TextBox6.Text
DATATAB.Rows.InsertAt((newrow), ROWNO)
DA.Update(DATATAB)
MsgBox("DATA INSERTED")
TextBox1.Text = ""
TextBox2.Text = ""
TextBox3.Text = ""
TextBox4.Text = ""
TextBox5.Text = ""
TextBox6.Text = ""
CN.Close()
End If
End If
End Sub
Private Sub Addevent_Load(ByVal sender As System.Object, ByVal e
As System.EventArgs) Handles MyBase.Load
TextBox1.Text = regno
start()
DA = New SqlDataAdapter("select * from event", CN)
CM = New SqlCommandBuilder(DA)
DA.Fill(DATATAB)
CN.Close()
ROWNO = 0
End Sub
Private Sub Label1_Click(ByVal sender As System.Object, ByVal e
As System.EventArgs) Handles Label1.Click
End Sub
Private Sub Label2_Click(ByVal sender As System.Object, ByVal e
As System.EventArgs) Handles Label2.Click
End Sub
Private Sub Label3_Click(ByVal sender As System.Object, ByVal e
As System.EventArgs) Handles Label3.Click
End Sub
56
Private Sub Label4_Click(ByVal sender As System.Object, ByVal e
As System.EventArgs) Handles Label4.Click
End Sub
Private Sub Label5_Click(ByVal sender As System.Object, ByVal e
As System.EventArgs) Handles Label5.Click
End Sub
Private Sub Label9_Click(ByVal sender As System.Object, ByVal e
As System.EventArgs) Handles Label9.Click
End Sub
Private Sub TextBox1_TextChanged(ByVal sender As System.Object,
ByVal e As System.EventArgs) Handles TextBox1.TextChanged
End Sub
Private Sub TextBox2_TextChanged(ByVal sender As System.Object,
ByVal e As System.EventArgs) Handles TextBox2.TextChanged
End Sub
Private Sub TextBox3_TextChanged(ByVal sender As System.Object,
ByVal e As System.EventArgs) Handles TextBox3.TextChanged
End Sub
Private Sub TextBox4_TextChanged(ByVal sender As System.Object,
ByVal e As System.EventArgs) Handles TextBox4.TextChanged
End Sub
Private Sub TextBox5_TextChanged(ByVal sender As System.Object,
ByVal e As System.EventArgs) Handles TextBox5.TextChanged
End Sub
Private Sub TextBox6_TextChanged(ByVal sender As System.Object,
ByVal e As System.EventArgs) Handles TextBox6.TextChanged
End Sub
Private Sub Label7_Click(ByVal sender As System.Object, ByVal e
As System.EventArgs) Handles Label7.Click
End Sub
Private Sub Label8_Click(ByVal sender As System.Object, ByVal e
As System.EventArgs) Handles Label8.Click
End Sub
End Class
57
Delete update form
Imports System.Data.SqlClient
Public Class delupdate
Dim DATATAB, datatab1, datatab2 As New DataTable
Private Sub Button2_Click(ByVal sender As System.Object, ByVal e
As System.EventArgs) Handles Button2.Click
If (MessageBox.Show("Do You want to update this Record",
"DELETE", MessageBoxButtons.YesNo, MessageBoxIcon.Exclamation) =
DialogResult.Yes) Then
start()
Dim CMD As SqlCommand = New SqlCommand("update event set
event_name='" & TextBox2.Text & "',event_sub='" & TextBox3.Text &
"',fac_name='" & TextBox4.Text & "',dat='" & TextBox5.Text &
"',tim='" & TextBox6.Text & "' WHERE event_id='" & TextBox1.Text &
"'", CN)
CMD.ExecuteNonQuery()
CN.Close()
MsgBox("Record Deleted")
TextBox1.Text = ""
End If
End Sub
Private Sub Button3_Click(ByVal sender As System.Object, ByVal e
As System.EventArgs) Handles Button3.Click
58
If (MessageBox.Show("Do You want to DELETE this Record from
your Database", "DELETE", MessageBoxButtons.YesNo,
MessageBoxIcon.Exclamation) = DialogResult.Yes) Then
start()
Dim CMD As SqlCommand = New SqlCommand("DELETE FROM event
WHERE event_id='" & TextBox1.Text & "'", CN)
CMD.ExecuteNonQuery()
CN.Close()
MsgBox("Record Deleted")
TextBox1.Text = ""
End If
End Sub
Private Sub delupdate_Load(ByVal sender As System.Object, ByVal e
As System.EventArgs) Handles MyBase.Load
End Sub
Private Sub Button1_Click(ByVal sender As System.Object, ByVal e
As System.EventArgs) Handles Button1.Click
MsgBox(ComboBox1.Text & ComboBox1.SelectedIndex)
Dim s As String = ComboBox1.Text
Dim sql As String = ""
Select Case ComboBox1.SelectedIndex
Case 0
sql = "select * from event where event_id='" &
TextBox1.Text & "'"
Case 1
sql = "select * from event where event_name='" &
TextBox1.Text & "'"
Case 2
sql = "select * from event where event_sub='" &
TextBox1.Text & "'"
Case 3
sql = "select * from event where dat='" &
TextBox1.Text & "'"
End Select
DATATAB.Clear()
start()
DA = New SqlDataAdapter(sql, CN)
CM = New SqlCommandBuilder(DA)
DA.Fill(DATATAB)
CN.Close()
ROWNO = 0
TextBox7.Text
TextBox2.Text
TextBox3.Text
TextBox4.Text
TextBox5.Text
TextBox6.Text
=
=
=
=
=
=
DATATAB.Rows(ROWNO)(0).ToString
DATATAB.Rows(ROWNO)(1).ToString
DATATAB.Rows(ROWNO)(2).ToString
DATATAB.Rows(ROWNO)(3).ToString
DATATAB.Rows(ROWNO)(4).ToString
DATATAB.Rows(ROWNO)(5).ToString
End Sub
End Class
59
Reports
Student details
Imports System.Data.SqlClient
Public Class STUDENT_REPO
Dim DATATAB, datatab1, datatab2 As New DataTable
Private Sub STUDENT_REPO_Load(ByVal sender As System.Object,
ByVal e As System.EventArgs) Handles MyBase.Load
start()
DA = New SqlDataAdapter("select * from student", CN)
CM = New SqlCommandBuilder(DA)
DA.Fill(DATATAB)
CN.Close()
ROWNO = 0
Dim OBJ As New CrystalReport2
OBJ.SetDataSource(DATATAB)
CrystalReportViewer1.ReportSource = OBJ
End Sub
End Class
Faculty details
60
Imports System.Data.SqlClient
Public Class faculty_repo
Dim DATATAB, datatab1, datatab2 As New DataTable
Private Sub faculty_repo_Load(ByVal sender As System.Object,
ByVal e As System.EventArgs) Handles MyBase.Load
start()
DA = New SqlDataAdapter("select * from faculty", CN)
CM = New SqlCommandBuilder(DA)
DA.Fill(DATATAB)
CN.Close()
ROWNO = 0
Dim OBJ As New facu
OBJ.SetDataSource(DATATAB)
CrystalReportViewer1.ReportSource = OBJ
End Sub
End Class
61
Expenses
Imports System.Data.SqlClient
Public Class Expenses_repo
Dim DATATAB, datatab1, datatab2 As New DataTable
Private Sub Expenses_repo_Load(ByVal sender As System.Object,
ByVal e As System.EventArgs) Handles MyBase.Load
start()
DA = New SqlDataAdapter("select * from expenses", CN)
CM = New SqlCommandBuilder(DA)
DA.Fill(DATATAB)
CN.Close()
ROWNO = 0
Dim OBJ As New EXPENSE
OBJ.SetDataSource(DATATAB)
CrystalReportViewer1.ReportSource = OBJ
End Sub
End Class
62
Fund details
Imports System.Data.SqlClient
Public Class Funds_repo
Dim DATATAB, datatab1, datatab2 As New DataTable
Private Sub Funds_repo_Load(ByVal sender As System.Object, ByVal
e As System.EventArgs) Handles MyBase.Load
start()
DA = New SqlDataAdapter("select * from funds", CN)
CM = New SqlCommandBuilder(DA)
DA.Fill(DATATAB)
CN.Close()
ROWNO = 0
Dim OBJ As New fund
OBJ.SetDataSource(DATATAB)
CrystalReportViewer1.ReportSource = OBJ
End Sub
End Class
63
Add fund details
Imports System.Data.SqlClient
Public Class Funds
Private Sub Button1_Click(ByVal sender As System.Object, ByVal e
As System.EventArgs) Handles Button1.Click
If (MessageBox.Show("Do You want to add this Record in your
Database", "ADD", MessageBoxButtons.YesNo,
MessageBoxIcon.Exclamation) = DialogResult.Yes) Then
If TextBox2.Text = "" Or TextBox3.Text = "" Or
TextBox4.Text = "" Then
MsgBox("FIELD SHOULD NOT BE EMPTY")
Else
Dim newrow As DataRow = DATATAB.NewRow
ROWNO = ROWNO + 1
newrow(0) = TextBox1.Text
newrow(1) = TextBox2.Text
newrow(2) = TextBox3.Text
newrow(3) = TextBox4.Text
DATATAB.Rows.InsertAt((newrow), ROWNO)
DA.Update(DATATAB)
MsgBox("DATA INSERTED")
TextBox1.Text = ""
TextBox2.Text = ""
TextBox3.Text = ""
TextBox4.Text = ""
CN.Close()
End If
64
End If
DATATAB.Clear()
DATATAB.Clear()
start()
DA = New SqlDataAdapter("select * from funds", CN)
CM = New SqlCommandBuilder(DA)
DA.Fill(DATATAB)
TextBox1.Text = "T001" & DATATAB.Rows.Count + 1
CN.Close()
ROWNO = 0
DA = New SqlDataAdapter("select * from funds", CN)
CM = New SqlCommandBuilder(DA)
DA.Fill(DATATAB)
TextBox1.Text = "T001" & DATATAB.Rows.Count + 1
CN.Close()
ROWNO = 0
End Sub
Private Sub Funds_Load(ByVal sender As System.Object, ByVal e As
System.EventArgs) Handles MyBase.Load
DATATAB.Clear()
start()
DA = New SqlDataAdapter("select * from funds", CN)
CM = New SqlCommandBuilder(DA)
DA.Fill(DATATAB)
TextBox1.Text = "T001" & DATATAB.Rows.Count + 1
CN.Close()
ROWNO = 0
End Sub
End Class
65
Add expenses details
Imports System.Data.SqlClient
Public Class Expenses
Private Sub Expenses_Load(ByVal sender As System.Object, ByVal e
As System.EventArgs) Handles MyBase.Load
DATATAB.Clear()
start()
DA = New SqlDataAdapter("select * from expenses", CN)
CM = New SqlCommandBuilder(DA)
DA.Fill(DATATAB)
CN.Close()
ROWNO = 0
End Sub
Private Sub Button1_Click(ByVal sender As System.Object, ByVal e
As System.EventArgs) Handles Button1.Click
If (MessageBox.Show("Do You want to add this Record in your
Database", "ADD", MessageBoxButtons.YesNo,
MessageBoxIcon.Exclamation) = DialogResult.Yes) Then
If TextBox2.Text = "" Or TextBox3.Text = "" Then
MsgBox("FIELD SHOULD NOT BE EMPTY")
Else
Dim newrow As DataRow = DATATAB.NewRow
ROWNO = ROWNO + 1
66
newrow(0) = TextBox1.Text
newrow(1) = TextBox2.Text
newrow(2) = TextBox3.Text
DATATAB.Rows.InsertAt((newrow), ROWNO)
DA.Update(DATATAB)
MsgBox("DATA INSERTED")
TextBox1.Text = ""
TextBox2.Text = ""
TextBox3.Text = ""
CN.Close()
End If
End If
End Sub
End Class
67