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, ducation, ntertainment, !cience, "edicine, ngineering, #istance $earning, Weather %orecasting. Carrier !earching and so on.
"y pro&ect named 'vent "anagement !ystem( is software that store and maintained all events coordinated in college. It also helpful to print related reports. "y pro&ect will help to record the events coordinated by faculties with their )ame, vent sub&ect, date * details in an efficient * effective ways.
In my system we have to ma+e 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 eisting system such as security.
1.2
Objectives of the project
The important ob&ectives if this pro&ect are following: - To provide a graphical user interface to add or delete the information. / To provide the same type of easy to feel type interface to update the records. 0 To provide an interface for feeding the suggestion. 1 To store those suggestions in the database. 2 To secure the data of records in very efficient way. 3 To allow the access of data and software to only the people who are authenticated. 4 Improved processing speed. 5 nhance capacity to process a greater amount of activity. 6 7roviding ability to conducting comple search. -8 %aster retrieval of information.
-
-- 9rater accuracy and consistency. -/ educing paper wor+. -0 educing cost. -1 Improved arrangement for event coordination.
MODULES The proposed pro&ect will have its main page and will be mainly divided into partially dependent and partially independent modules as: -.
LOGIN FORM
2. MDI FORM 3. ENTRY FORM 1.
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 bo and one tet boes. When the faculty wants to edit information in the display form has to give his password. 7assword will be hidden to the eternal viewer. ;long with then the form has two buttons, '<=( and '>IT(. Clic+ing on '<=(, the eecution moves forward to the second form. 2. MDI FORM
"#I %orm is the form in the eecution line. ;ll the other forms in pro&ect are lin+ed together by this from only. 7athways to all the other forms go through this module. This form consists of two options buttons, that is labeled as 'open( and '>IT(. ?sers first have to select one of the options that is desired by user. Clic+ing on any of the button ta+es the user to form according to the option selected .Clic+ing on 'it( ends the eecution.
/
3. ENTRY FORM
)T@ form consists of one combo bo, five tet boes in the form, the users has to give the details of new records to be added. He can specify the category by combo bo and also fill up the tet boes provided under the heading of software details and hardware details of a particular lab. %or the purpose of adding new record and removing record buttons( )W(,'#$T( and are provided. Clic+ing on '7AIT( button in the form all entries in the database are viewed on and '>IT( clic+ing will be send bac+ the user to main login form.
4. SEARCH MODULE
#isplay form contains a data grid to display the facultys even records. #ata 9rid contains si records. It also contains two commands 'edit( and 'eit(. By edit command we can edit information in the ntry form and by 'eit( clic+ing will be send bac+ the user to main to "#I %orm .
0
2.SYSTEM ANALYSIS
2.1 EXISTING SYSTEM
-. Probl! o" Rl#$b#l#%&' Current system is not reliable. It seems to vary in uality from one month to the net. !ome times it gives good output, but some times the output is worst.
/. Probl! o" A(()r$(&' There are too many mista+es in reports.
0. Probl! o" %#!l#*++' 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.
1. Probl! o" ,$l#-#%& : The output and reports mostly contains misleading information. The customerDs information is sometimes not valid.
2. Probl! o" E(o*o!&' The current system is very costly. We have to spend lots of money to +eep the system up and going, but still not get the desired results.
3. Probl! o" C$$(#%&' The current system is suffering from problem of capacity also. The staff for organiEation is very less and the wor+load is too much. %ew peoples cannot handle all the wor+.
DRA/BAC0S OF EXISTING SYSTEM •
;t present the system which is not effective and efficient way.
•
It does not has the security and authenticity. ;ny user can access that system.
•
•
The eisting system is not user friendly. It does not have a menu based control which can ma+e a system move consistent and user friendly.
•
It reuires on epend hand to wor+ on.
•
If anyone wants to wor+ on, then it reuires a special training for this.
1
•
?nnecessary printing is too much costly.
•
There is no any file management techniue used so it lac+s it deserve high speed data access. )o searching of records is too comple and time consuming.
2.2 PROPOSED SYSTEM -.
D%$#l+ ' The new proposed system stores and maintains all the faculties events, students, funds, epenses details.
/. C$l()l$%#o*+' The new proposed system updates tables and other information automatically and it is very fast and accurate. 0. R#+%r+' There is no need of +eeping and maintaining salary and information manually. It remembers each and every record and we can get any report at any time. 1. S-' The new proposed system is very fast with -88F accuracy and saves time. 2. M$*or' The new proposed system needs less manpower. $ess people can do the large wor+. 3. E""#(#*(&' The new proposed systems complete the wor+ of many people in less time. 4. P$+% -%$#l+' The new proposed system contains the details of every past vent organiEed. 5. R-)(+ r-)*-$*(&'The most important benefit of this system is that it reduces the redundancy of data within the data. 6. /or lo$-' educes the wor+ 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.
2
-8. E$+& +%$%!*%+' "onthGend and dayGend statement easily ta+en out without getting headaches on browsing through the day end statements.
I have designed the given proposed system in the Aisual Basic to automate the process of vent "anagement !ystem. This pro&ect is useful for the authorities who +eep trac+ of all the vent "anagement !ystem. The following steps that give the detailed information of the need of proposed system are: •
Pr"or!$*(' #uring 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 computeriEed system is to be underta+en. The computeriEed pro&ect is fully computeriEed and user friendly even that any of the members can see the report and status of their enuiries.
•
E""#(#*(&' The basic need of this pro&ect is efficiency. The pro&ect should be
efficient so that whenever a new user submits hisher details the pro&ect is updated automatically. This record will be useful for other users instantly.
•
Co*%rol' The complete control of the pro&ect is under the hands of authoriEed
person who has the password to access this pro&ect and illegal access is not supposed to deal with. ;ll the control is under the administrator and the other members have the rights to &ust see the records not to change any transaction or entry.
•
S()r#%&' !ecurity is the main criteria for the proposed system. !ince illegal
access may corrupt the database. !o security has to be given in this pro&ect.
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 ma&or factors
3
ECONOMICAL FEASIBILITY
conomical feasibility is the most recently used method for evaluating effectiveness of the proposed system .It is obliuely +nown as cost benefit analysis. This procedure determined the benefits and savings that are epected from the proposed system and compared with the cost of the eisting system. In case of the eisting system, the hardware in the company is sufficient for system development and maintenance.
TECHNICAL FEASIBILITY
The hardware, the software and to what etent they can support the proposed system are the +eys for this study .The airways has all the reuired software necessary development and maintenance. Ta+ing into consideration of the above criteria, the proposed system is technically feasible and further developments could be accomplished easily. BEHA,IOURAL 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 organiEation. The proposed system is highly user interactive so it is easy for end user to understand the system and use it.
4
3.SYSTEM SPECIFICATION
Aisual programming tools are complete programming environments. It allows programmers to build a 9?I program using the various onGscreen controls such as buttons, tet, menus, boes 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 uality, cut costs and provide a high response customer service base. "ost organiEations today need to be mar+et driven and do a lot of value addition to their products and services. This naturally calls for rational decision ma+ing, which reuires information. Information Technology or IT provides that effective channel to support and implement this strategy. Client!erver is the technology that empowers the des+top, thus setting a trend for the way successful organiEations will use technology in the net decade. 3.1 HARD/ARE SPECIFICATION !ystem
:
7entiumIA
;"
:
-/5"B
Hard#is+ %loppy#rive "onitor
: : :
189B -.11"B -1( Color "onitor
7rinter
:
Tetprinter
=eyboard
:
!;"!?)9
"ouse
:
$ogitech
3.2 SOFT/ARE SPECIFICATION
Operating System %rontnd
::
Bac+nd
:
5
Windows XP Aisual Basic.)et /882 "sG;ccess
3.3 SOFT/ARE DESCRIPTION I*%ro-)(%#o* O" ,#+)$l B$+#(.N% Aisual Basic .)T is one of the languages that are directed towards meeting the ob&ectives of the .)T initiative of creating distributed applications. Aisual Basic .)T is a powerful ob&ectGoriented language that provides features such as abstraction, encapsulation, inheritance, and polymorphism.
Features of Visual Basic .NET
•
!ome of the +ey features of Aisual Basic .)T are as follows: o Inheritance o Constructors and destructors o
Visual Studio .NET Integrated Development Environment
•
The Aisual !tudio .)T Integrated #evelopment nvironment I# provides you with a common interface for developing various +inds of pro&ects for the .)T %ramewor+.
•
In Aisual !tudio .)T, an application can be made up of one or more items, such as files and folders. To organiEe these items efficiently, Aisual !tudio .)T has provided two types of containers: o 7ro&ects o !olutions
•
The various components of the Aisual !tudio .)T I# are: o The !tart 7age o Windows %orms #esigner
6
o The !olution plorer Window o The 7roperties Window o Toolbo o The
)avigational %eatures in Aisual !tudio .)T I# o The Class Aiew Window o The Code and Tet ditor Window
•
The Aisual !tudio .)T I# also provides three navigational features: o #oc+ing o Tabbed navigation o ;uto 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 te .NET Framewor! •
!ome advantages of the .)T %ramewor+ are: o Consistent programming model o "ultiGplatform applications o "ultiGlanguage integration o ;utomatic resource management o ase of deployment
Securit" •
videnceGbased security authentication
•
Based on user identity and code identity
•
Configurable policies
•
Imperative and declarative interfaces
-8
I*%ro-)(%#o* O" Sl S%r)(%)r- 5)r& L$*)$ , is a computer language designed for the retrieval and
management of data in relational database management systems, database schema creation and modification, and database ob&ect access control management. !J$ has been standardiEed originally designed as a declarative uery and data manipulation language, variations of !J$ have been created by !J$ datab ase management system #B"! vendors that add procedural constructs, controlGofGflow statements, userGdefined data types, and various other language etensions. With the release of the !J$: -666 standard, many such etensions were formally adopted as part of the !J$ language via the !J$ 7ersistent !tored "odules !J$7!" portion of the standard. !J$ has come under criticism for its lac+ of crossGplatform portability between vendors, inappropriate handling of missing data , comple threeGvalued logic system, and its comple and occasionally ambiguous language grammar and semantics. ?sing !J$ one can create and maintain data manipulation ob&ects such as table, views, seuence etc. These data manipulation ob&ects will be created and stroed on the serverDs hard dis+ drive, in a tablespace, to wich the user has been assigned.
%irst, there are the standard #ata "anipulation $anguage #"$ elements. #"$ is the subset of the language used to add, update and delete data: •
INSERT is used to add rows formally tuples to an eisting table.
•
UPDATE is used to modify the values of a set of eisting table rows.
--
•
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 !J$:/880 standardK prior to that, some databases provided similar functionality via different synta, sometimes called an LupsertL.
•
DELETE removes Eero or more eisting rows from a table.
D$%$ (o*%rol
The third group of !J$ +eywords is the #ata Control $anguage #C$. #C$ handles the authoriEation aspects of data and permits the user to control who has access to see or manipulate data within the database. Its two main +eywords are: •
GRANT authoriEes one or more users to perform an operation or a set of operations on an ob&ect.
•
REVOKE removes or restricts the capability of a user to perform an operation or a set of operations.
ample: 9;)T !$CT, ?7#;T <) myMtable T< someMuser, anotherMuser
Data defnition
The second group of +eywords is the #ata #efinition $anguage ##$. ##$ allows the user to define new tables and associated elements. "ost commercial !J$ databases have proprietary etensions in their ##$, which allow control over nonstandard features of the database system. The most basic items of ##$ are the CREATE, ALTER, RENAME, TRUNCATE and DROP
•
statements:
CREATE causes an ob&ect a table, for eample to be created within the database.
•
DROP causes an eisting ob&ect within the database to be deleted, usually irretrievably.
•
TRUNCATE deletes all data from a table nonGstandard, but common !J$ statement.
-/
•
ALTER statement permits the user to modify an eisting ob&ect in various ways GG for eample, adding a column to an eisting table.
ample: C;T T;B$ myMtable "yMfield- I)T, "yMfield/ A;CH; 28, "yMfield0 #;T
)
7I";@ =@ myMfield-, myMfield/ K
In addition to the creationof data manipulation ob&ects, the actual manipulation of data within these ob&ects is done using !J$.
The !J$ sentences that are used to create these ob&ects are called ##$Ds or #ata #efination $anguage. The !J$ sentences used to manipulate data within these ob&ects are called #"$Ds or #ata "anipulation $anguage. The !J$ sentences, which are used to control the behavior of these ob&ects, are called #C$Ds or #ata Control $anguage.
Hence, once access to the !J$N7lus tool is available and !J$ synte is +nown, the creation of data stroage and the manipulation of data within the storage system, reuired by commercial applications, is possible.
-0
4 SYSTEM DESIGN
The design document that we will develop during this phase is the blueprint of the software. It describes how the solutio n to the customer prob lem is to be built. !ince solution to comple problems isnt usually found in the first try, iterations are most li+ely reuired. This is true for software design as well. %or this reason, any design strategy, design method, or design language must be fleible and must easily accommodate changes due to iterations in the design. ;ny techniue or design needs to support and guide the partitioning process in such a way that the resulting subG problems are as independent as possible from each other and can be combined easily for the solution to the overall problem. !ubGproblem independence and easy combination of their solutions reduces the compleity of the problem. This is the ob&ective of the partitioning process. 7artitioning or decomposition during design involves three types of decisions: G #efine the boundaries along which to brea+K #etermine into how money pieces to brea+K and Identify the proper level of detail when design should stop and implementation should start.
4.1 INPUT DESIGN $ogin "oduleG This is first module in the pro&ect used as authentication module. This module ta+es following inputG •
?ser )ame
•
7assword
•
Type
%aculty "oduleGThis module contains information of event coordinator faculties. It ta+es the following input.
-1
•
%aculty Id
•
%aculty )ame
•
;ddress
•
7hone )o
•
!ub&ect
vent "oduleGthis module contain complete information for coordinated event. It ta+es the following inputs. •
vent Id
•
vent )ame
•
vent !ub&ect
•
%aculty )ame
•
#ate
•
Time
4.2 OUTPUT DESIGN
$ogin "odule: nter username and password and get "#I form if valid. %aculty "odule: nter faculty Id and get complete information of faculty such as name, address, phone no. and sub&ect, if valid. vent "odule: nter event I# or vent name to get and complete information of coordinated event such as date, time, name and coordinator name.
Basic design princ iples that enable the software engineer to navigate the design process suggest a set of principles for software design, which have been adapted and etended in the following list:
-2
%ree from the suffer from Ltunnel vision.L ; good designer should consider alternative approaches, &udging each based on the reuirements of the problem, the resources available to do the &ob. The design should be traceable to the analysis model. Because a single element of the design model often traces to multiple reuirements, it is necessary to have a means for trac+ing how reuirements have been satisfied by the design model.
The design should not repeat the same thing. !ystems are constructed using a set of design patterns, many of which have li+ely been encountered before. These patterns should always be chosen as an alternative to reinvention. Time is short and resources are limitedO #esign time should be invested in representing truly new ideas and integrating those patterns that already eist.
The design should Lminimi Ee the intellectual distanceL between the software and the problem as it eists 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 ehibit uniformity and integration. ; design is uniform if it appears that one person developed the entire thing. ules of style and format should be defined for a design team before design wor+ begins. ; design is integrated if care is ta+en in defining interfaces between design components.
The design activity begins when the reuirements document for the software to be developed is available. This may be the !! for the complete system, as is the case if the waterfall model is being followed or the reuirements for the net LiterationL if the iterative enhancement is being followed or the reuirements for the prototype if the prototyping is being followed. While the reuirements specification activity is entirely in the problem domain, design is the first step in moving from the problem domain toward the solution domain. #esign is essentially the bridge between reuirements specification and the final solution for satisfying the reuirements.
-3
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 fied defined manner to produce some behavior or services for its environment. ; 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. ;t 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 topGlevel 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. #etailed design essentially epands 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 etension of system design, the system design controls the ma&or structural characteristics of the system. The system design has a ma&or impact on the testability and modifiability of a system, and it impacts its efficiency. "uch 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 topGlevel 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. easonable eit criteria for the phase could be that the design has been verified against the input specifications and has been evaluated and approved for uality.
; design can be ob&ectGoriented or functionGoriented. In functionGoriented design, the design consists of module definitions, with each module supporting a functional abstraction. In ob&ectGoriented design, the modules in the design represent data
-4
abstraction these abstractions are discussed in more detail later. In the functionG oriented methods for design and describe one particular methodology the structured design methodology in some detail. In a functionG 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 ma&or data structures in the system, all the ma&or modules of the system, and how the modules interact with each other.
-5
4.3 DATA BASE DESIGN
D$%$ !o-l#* -"#*+ r#!$r& -$%$ ob6(%+7 (o!o+#%#o* o" $(8 -$%$ ob6(%7 $*- $%%r#b)%+ o" %8 ob6(%7 rl$%#o*+8#+ b%* $(8 ob6(% $*- o%8r ob6(%+ $*- b%* ob6(%+ $*- %8 ro(+++.
L#+% o" T$bl+' A-!#* T$bl' To +%or $-!#* )+r*$! $*- $++or-. F#l-+ ?sername 7assword
T& Char08 Char08
Co*+%r$#*% )ot)ull )ot)ull
D+(r#%#o* ?sername P$++or-
U+r+ T$bl' To store users details. The users are managed by admin. F#l-+ ?sername 7assword mail
T& Char08 Char08 Char08
Co*+%r$#*% )ot)ull )ot)ull )ot)ull
D+(r#%#o* ?sername 7assword mailId
S%)-*%+' To store student details F#l-+ egno.
;ddress ContactMno eg.;mount
T& Char08 Char08 Char08 Char08 )umber
Co*+%r$#*% 7rimary=ey )ot)ull )ot)ull )ot)ull )ot)ull
Total%ee egMdate #escription
)umber2 #ate Char08
)ot)ull )ot)ull )ot)ull
)ame
D+(r#%#o* egistration)o. )ame ;ddress Contact)o egistration ;mount Total%ee egistration#ate #escription
F$()l%&' To store faculty details
F#l-+ I# )ame
;ddress City !tate !ub&ect !pecialiEation Jualification
T& Char08 Char08 Char08 Char08 Char08 Char08 Char08 Char08
Co*+%r$#*% 7rimary =ey )ot)ull )ot)ull )ot )ull )ot )ull )ot)ull )ot)ull )ot )ull
-6
D+(r#%#o* Id )ame ;ddress City !tate !ub&ect !pecialiEation Jualification
F)*-+' To store funds details. F#l-+ TransactionMId #onor
;mount #ateMofMdeps
T& Char08 Char28 )umber3 #ate
Co*+%r$#*% 7rimary=ey )ot)ull )ot)ull )ot)ull
D+(r#%#o* Transaction #onor ;mount #ate
E9*++' To store details of the epenses for event "anagement system. F#l-+ pensesMamount #ateMofMwithdrawl
#escription
T& )umber5 #ate Char/88
Co*+%r$#*% )ot)ull )ot)ull )ot)ull
D+(r#%#o* pensesamount #ateofwithdrawl #escription
E:*%' To store event #etails F#l-+
T&
Co*+%r$#*%
ventMId
!ub&ect %acultyMname
Char08 Char28 Char28 Char28
7rimary=ey )ot)ull )ot)ull )ot)ull
#ateMofMevent Time
#ate Char08
)ot)ull )ot )ull
ventM)ame
/8
D+(r#%#o*
ventI# vent)ame !ub&ect ;rranged %aculty #ateofevent Time
by
ENTITY RELATIONSHIP DIAGRAM ;ERD< E*%#%& = Rl$%#o*+8# D#$r$!' This depicts relationship between data ob&ects. The
attribute of each data ob&ects noted in the entityG relationship diagram can be described using a data ob&ect description. #ata flow diagram serves two purposes:
-. To provide an indication of how data are tran sformed as they mov e through the system. /. To depict the functions that transformation the data flow.
D$%$ Ob6(%+' ; data ob&ect 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. ; data ob&ect encapsulates data only there is no reference within a data ob&ect to operations that act on the data.
A%%r#b)%+' ;ttributes define the properties of a data ob&ect and ta+e on one of three
different characteristics. They can be used to: )ame an instance of data ob&ect. #escribe the instance. "a+e reference to another instance in other table.
Rl$%#o*+8#+' #ata ob&ects are connected to one another in a variety of different
ways. We can define a set of ob&ect relationship pairs that define the relevant relationships.
/-
4.4. DATA FLO/ DIAGRAM CONTEXT LE,EL DFD FOR E,ENT MANAGEMENT SYSTEM
/. !T?#)T -. ;#"I)
0. %;C?$T@
E,ENT MANAGEMENT SYSTEM
3. A)T !CH#?$
1. ;## A)T 2. B?#9T <% A)T
//
I+% L:l DFD "or A-!#*
-.;ccept the user name * 7assword
;#"I)
-./ Aalidate the ;dmin
E,ENT MANAGEMENT SYSTEM
;#"I)
/0
I+% L:l DFD For %8 +%)-*%+ /./ ;ccept the student
!T?#)T
details
/.1 update students
/./ Aalidate students
E,ENT MANAGEMENT SYSTEM
!T?#)T
/.1 ?pdate students
/.0 %aculty "anager s ven
%;C?$T@
A)T!
/1
I+% L:l DFD "or %8 F$()l%&
0.;ccept the
%;C?$T@
%aculty #etails
0./ Aalidate %aculty
E,ENT MANAGEMENT SYSTEM
%;C?$T@
0.0 %aculty manages the !tudent * vents
A)!
/2
I+% L:l DFD For :*% M$*$ !*%
1.;ccept the vent
;#"I)
euests
1.1 ;pproved Budget * penses
1./ Aalidate the vents
E,ENT MANAGEMENT SYSTEM
1.0 Coordinat e %aculty
vent
1.2 Coordina te !tudents
!tudents
%aculty!
/3
> SYSTEM TESTING
)o program or system design is perfectK 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 wor+ing order, but in reality, each piece wor+s independently. )ow is the time to put all the pieces into one system and test it to determine whether it meets the userDs reuirements. 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 li+ely variations to which it will be sub&ected and then push the system to its limits. If we implement the system without proper testing then it might cause the problems. -. Communication between the user and the designer. /. The programmerDs ability to generate a code that reflects eactly the system specification. 0. The time frame for the design.
Theoretically, a new designed system should have all the pieces in wor+ing order, but in reality, each piece wor+s indepen dently. )ow is the time to put all the pieces into one system and test it to determine whether it meets the reuirements of the user. The process of system testing and the steps ta+en to validate and prepare a system for final implementation are:
/4
1. UNIT TESTING' This is the smallest testable unit of a computer system and is normally tested using the white bo testin g. 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 chec+s 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 topGdown, bottomGup, or bigGbang. In this type of testing, some parts will be tested with white bo testing and some with blac+ bo testing techniues. This type of testing plays very important role in increasing the systems productivity. We have chec+ed our system by using the integration testing techniues.
3. SYSTEM TESTING' ; part from testing the system to validate the functionality of software against the reuirements, it is also necessary to test the nonGfunctional aspect of the system. !ome eamples of nonGfunctional tools include tests to chec+ performance, data security, usabilityuser friendliness, volume, loadstress that we have used in our pro&ect to test the various modules.
S&+%! %+%#* (o*+#+%+ o" %8 "ollo#* +%+' -. 7rograms testing. /. !tring testing. 0. !ystem testing. 1. !ystem documentation. 2. ?ser acceptance testing.
4. FIELD TESTING' This is a special type of testing that may be very important in some pro&ects. Here the system is tested in the actual operational surroundings. The
/5
interfaces with other systems and the real world are chec+ed. This type of testing is very rarely used. !o far our pro&ect is concernedK we havenDt tested our pro&ect using the field testing.
>. ACCEPTANCE TESTING' ;fter the developer has completed all rounds of testing and he is satisfied with the system, then the user ta+es over and reGtests the system from his point of view to &udge whether it is acceptable according to some previously identified criteria. This is almost always a tric+y situation in the pro&ect because of the inherent conflict between the developer and the user. In this pro&ect, it is the &ob of the boo+stores to chec+ the system that whether the made system fulfills the goals or not.
/6
?. SYSTEM IMPLEMENTATION
;s we +now, 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 tas+ of creating the pro&ect. %irst we have to implement the software on a small scale for removing the bugs and other errors in the pro&ect and after removing them we can implement the software on a large scale.
Before we thin+ in
terms of implementing the !oftware on a large basis, we must consider the Hardware reuirements.
Whenever we develop software or pro&ect a certain hardware and software is being used by the programmer for developing the pro&ect. The hardware and software to be used by the programmer for developing the pro&ect should be such that it would result in the development of a pro&ect, which would satisfy all the basic needs for which the pro&ect has been created by the programmer. The Hardware should be such that cost constraints of the Client should also be ta+en into account without affecting the performance.
08
@. SYSTEM MAINTENANCE AND SECURITY
So"%$r+ ,)l*r$b#l#%& %o A%%$(
!oftware development is not yet a science or a rigorous discipline, and the development process by and large is not controlled to minimiEe the vulnerabilities that attac+ers eploit. The security of software is threatened at various points throughout its life cycle, both by inadvertent and intentional choices and actions ta+en by 'insiders(Pindividuals closely affiliated with the organiEation that is producing, deploying, operating, or maintaining the software, and thus trusted by that organiEationPand by 'outsiders( who have no affiliation with the organiEation. The softwares security can be threatened. •
D)r#* #%+ -:lo!*%' ; developer may corrupt the software
intentionally or unintentionallyin ways that will compromise the softwares dependability and trustworthiness when it is operational. •
D)r#* #%+ -lo&!*% ;-#+%r#b)%#o* $*- #*+%$ll$%#o*<' 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. !imilarly, if the softwares installer fails to 'loc+ down( the host platform, or configures the software insecurely, the software is left vulnerable to access by attac+ers. •
D)r#* #%+ or$%#o*'
operational, vulnerabilities may be discovered and publiciEedK 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. )onGcommercial software and open source software
0-
stress the software in ways that were not anticipated and simulated during its testing. •
D)r#* #%+ +)+%$#*!*%' If those responsible for addressing discovered
vulnerabilities in released software fail to issue patches or updates in a timely manner, or fail to see+ 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. ;lso, the softwares maintainer may prove to be a malicious insider, and may embed malicious code, eploitable flaws, etc., in updated versions of the code.
T8 C8$ll* o" B)#l-#* S()r So"%$r' -.
D*-$b#l#%&' #ependable software eecutes predictably and operates
correctly under all conditions, including hostile conditions, including when the
/.
software comes under attac+ or runs on a malicious host. Tr)+%or%8#*++' Trustworthy software contains few if any vulnerabilities or wea+nesses that can be intentionally eploited to subvert or sabotage the softwares dependability. In addition, to be considered trustworthy, the software must contain no malicious logic that causes it to behave in a malicious manner.
S)r:#:$b#l#%& ;$l+o r"rr- %o $+ R+#l#*(<' !urvivablePor resilientPsoftware
is software that is resilient enough to - either resist i.e., protect itself against or tolerate i.e., continue operating dependably in spite of most +nown attac+s plus as many novel attac+s as possible, and / recover as uic+ly as possible, and with as little damage as possible, from those attac+s that it can neither resist nor tolerate
0/
8. SCOPE OF FT!E APP"ICATION The whole pro&ect as we have seen is totally based upon the database maintenance. This could be the most vital thing that the Indian industry as+s for these days. This phenomenon is not only confined to big industries, but amaEingly what that a common man deals with everyday in his life. This phenomenon starts from a common man to big industries li+e railways. )ot 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 ma&or role in upcoming of leading industries. #atabase accessing is what each firm will as+ for in the coming future. #atabase is what they reuired in each field. Therefore the database is the future of computer industry.
00
.CONCLUSION
This pro&ect is designed to meet the reuirements of vent "anagement in Colleges. It is developed in Aisual Basic.)et, +eeping in mind the specifications of the system.
%or designing the system we have used simple data flow diagrams.
?sing system analysis and design techniues li+e data flow diagram in designing the system.
?nderstanding the database handling and uery processing
01
1#. $I$"IO%!AP&Y
-. Aisual Basic
Qamew %oall
/. %undamentals
a&ib "all
0. !oftware ngineering
=.=.;ggarwal * @ogesh !ingh
1. Aisual Basic 7ro&ects
Tony "artin, #ominic !elly
2. Aisual Basic 7rofessional 7ro&ects
=ul&it =aur,7oo&a Bembey
3. ?sing !J$G!A /888, "icrosoft publication 4. !J$G!A /888 B7B publication
02
ANNEXURE
So'rce Co(e
"o)i* For+
Imports System.Data.SqlCliet P!"li# Class lo$i Dim DATATA%& 'atata"(& 'atata") As Ne* DataTa"le Pri+ate S!" o,-Cli#,%yVal se'er As System.O"/e#t& %yVal e As System.E+etAr$s0 1a'les o,.Cli#, Call start0 DA 2 Ne* SqlDataA'apter3SELECT 4 5ROM !sers *6ere !serame273 8 Te9t%o9(.Te9t 8 37 a' pass*or'273 8 Te9t%o9).Te9t 8 37 3& CN0 CM 2 Ne* SqlComma'%!il'erDA0 DA.5illDATATA%0 RO:NO 2 ; Dim s( As Stri$ 2 TrimDATATA%.Ro*sRO:NO0;0.ToStri$0 Dim s) As Stri$ 2 TrimDATATA%.Ro*sRO:NO0(0.ToStri$0
I< Te9t%o9(.Te9t 2 s( A' Te9t%o9).Te9t 2 s) T6e !ame 2 Te9t%o9(.Te9t !i' 2 Te9t%o9).Te9t Dim o"/ As Ne* me! o"/.S6o*0 Me.1i'e0 Else
03
Ms$%o93i+ali' Pass*or'30 Te9t%o9(.Te9t 2 33 Te9t%o9).Te9t 2 33 Te9t%o9(.5o#!s0 E' I< CN.Close0 E' S!"
Pri+ate S!" Te9t%o9)-Vali'ati$%yVal se'er As System.O"/e#t& %yVal e As System.CompoetMo'el.Ca#elE+etAr$s01a'les Te9t%o9).Vali'ati$ I< Te9t%o9).Te9t 2 33 T6e Ms$%o93Pass*or' S6o!l' ot "e "la,30 Te9t%o9).5o#!s0 E' I< I< LeTe9t%o9).Te9t0 = > T6e Ms$%o93Pass*or' s6o!l' "e o< ma9im!m > #6ara#ter30 Te9t%o9).Te9t 2 33 Te9t%o9).5o#!s0 E' I< E' S!" Pri+ate S!" Te9t%o9(-Vali'ati$(%yVal se'er As O"/e#t& %yVal e As System.CompoetMo'el.Ca#elE+etAr$s0 1a'les Te9t%o9(.Vali'ati$ I< Te9t%o9(.Te9t 2 33 T6e Ms$%o93UserName S6o!l' ot "e "la,30 Te9t%o9(.5o#!s0 E' I< I< LeTe9t%o9(.Te9t0 = > T6e Ms$%o93UserName s6o!l' "e o< ma9im!m > #6ara#ter30 Te9t%o9(.Te9t 2 33 Te9t%o9(.5o#!s0 E' I< E' S!" Pri+ate S!" Pael)-Pait%yVal se'er As System.O"/e#t& %yVal e As System.:i'o*s.5orms.PaitE+etAr$s0 1a'les Pael).Pait E' S!" Pri+ate S!" lo$i-Loa'%yVal se'er As System.O"/e#t& %yVal e As System.E+etAr$s0 1a'les My%ase.Loa' E' S!" E' Class
04
M,I For+
Imports System.:i'o*s.5orms P!"li# Class me!
Pri+ate S!" A'miToolStripMe!Item-Cli#,%yVal se'er As System.O"/e#t& %yVal e As System.E+etAr$s0 1a'les St!'et.Cli#, Dim o"/ As Ne* st!'et o"/.M'iParet 2 o"/.S6o*0 E' S!"
Me
Pri+ate S!" A"o!tCCMSToolStripMe!Item-Cli#,%yVal se'er As System.O"/e#t& %yVal e As System.E+etAr$s0 Dim o"/ As Ne*
Me
Pri+ate S!" me!-Loa'%yVal se'er As System.O"/e#t& %yVal e As System.E+etAr$s0 1a'les My%ase.Loa' E' S!"
Pri+ate S!" EterpriseRe#or'ToolStripMe!Item-Cli#, %yVal se'er As System.O"/e#t& %yVal e As System.E+etAr$s0 Dim o"/ As Ne* UPDATESTUDENT
05
o"/.M'iParet 2 o"/.S6o*0 E' S!"
Me
Pri+ate S!" Co!rses-Cli#,%yVal se'er As System.O"/e#t& %yVal e As System.E+etAr$s0 1a'les Co!rses.Cli#, Dim o"/ As Ne* DELSTUDENT o"/.M'iParet 2 Me o"/.S6o*0 E' S!" Pri+ate S!" A'miToolStripMe!Item-Cli#,-(%yVal se'er As System.O"/e#t& %yVal e As System.E+etAr$s0 1a'les A'miToolStripMe!Item.Cli#, Dim o"/ As Ne*
Me
Pri+ate S!" C6e#,Stat!sToolStripMe!Item-Cli#,%yVal se'er As System.O"/e#t& %yVal e As System.E+etAr$s0 1a'les C6e#,Stat!sToolStripMe!Item.Cli#, E' E' S!" Pri+ate S!" St!'etToolStripMe!Item-Cli#,%yVal se'er As System.O"/e#t& %yVal e As System.E+etAr$s0 1a'les St!'etToolStripMe!Item.Cli#, Dim o"/ As Ne* Eq!iry Type 2 3St!'et3 o"/.M'iParet 2 Me o"/.S6o*0 E' S!" Pri+ate S!" 5a#!ltyToolStripMe!Item-Cli#,%yVal se'er As System.O"/e#t& %yVal e As System.E+etAr$s0 Dim o"/ As Ne* Eq!iry type 2 35a#!lty3 o"/.M'iParet 2 Me o"/.S6o*0 E' S!" Pri+ate S!" Co
Pri+ate S!" St!'etsDetailsToolStripMe!Item-Cli#, %yVal se'er As System.O"/e#t& %yVal e As System.E+etAr$s0 1a'les St!'etsDetailsToolStripMe!Item.Cli#, Dim o"/ As Ne* STUDENT-REPO o"/.M'iParet 2
Me
06
o"/.S6o*0 E' S!"
Pri+ate S!" 5a#!ltyToolStripMe!Item(-Cli#,%yVal se'er As System.O"/e#t& %yVal e As System.E+etAr$s0 Dim o"/ As Ne*
Pri+ate S!" Eq!iryDetailsToolStripMe!Item-Cli#, %yVal se'er As System.O"/e#t& %yVal e As System.E+etAr$s0 1a'les Eq!iryDetailsToolStripMe!Item.Cli#, Dim o"/ As Ne*
o"/.M'iParet 2 o"/.S6o*0 E' S!"
Me
Pri+ate S!" UserMaa$erToolStripMe!Item-Cli#,%yVal se'er As System.O"/e#t& %yVal e As System.E+etAr$s0 1a'les UserMaa$erToolStripMe!Item.Cli#, E' S!"
18
Pri+ate S!" 5a#!ltyDetailsToolStripMe!Item-Cli#, %yVal se'er As System.O"/e#t& %yVal e As System.E+etAr$s0 1a'les 5a#!ltyDetailsToolStripMe!Item.Cli#, Dim o"/ As Ne* Eq!iry o"/.M'iParet 2 Me o"/.S6o*0 E' S!" Pri+ate S!" Co!rseDetailsToolStripMe!Item-Cli#, %yVal se'er As System.O"/e#t& %yVal e As System.E+etAr$s0 1a'les Co!rseDetailsToolStripMe!Item.Cli#, Dim o"/ As Ne* Eq!iry o"/.M'iParet 2 Me o"/.S6o*0 E' S!"
Pri+ate S!" A''ToolStripMe!Item-Cli#,%yVal se'er As System.O"/e#t& %yVal e As System.E+etAr$s0 1a'les A''ToolStripMe!Item.Cli#, Dim o"/ As Ne* 5!'s o"/.M'iParet 2 Me o"/.S6o*0 E' S!" Pri+ate S!" E9pesesDetailsToolStripMe!Item-Cli#, %yVal se'er As System.O"/e#t& %yVal e As System.E+etAr$s0 1a'les E9pesesDetailsToolStripMe!Item.Cli#, Dim o"/ As Ne* E9peses o"/.M'iParet 2 Me o"/.S6o*0 E' S!" Pri+ate S!" E9pesesToolStripMe!Item-Cli#,%yVal se'er As System.O"/e#t& %yVal e As System.E+etAr$s0 1a'les E9pesesToolStripMe!Item.Cli#, Dim o"/ As Ne* E9peses-repo o"/.M'iParet 2 Me o"/.S6o*0 E' S!" Pri+ate S!" 5!'Deposite'ToolStripMe!Item-Cli#, %yVal se'er As System.O"/e#t& %yVal e As System.E+etAr$s0 1a'les 5!'Deposite'ToolStripMe!Item.Cli#, Dim o"/ As Ne* 5!'s-repo o"/.M'iParet 2 Me o"/.S6o*0 E' S!" E' Class
1-
St'(e*t -(( (et-is
Imports System.Data.SqlCliet P!"li# Class st!'et Dim DATATA%& 'atata"(& 'atata") As Ne* DataTa"le
Pri+ate S!" st!'et-Loa'%yVal se'er As System.O"/e#t& %yVal e As System.E+etAr$s0 1a'les My%ase.Loa' start0 DA 2 Ne* SqlDataA'apter3sele#t 4
Te9t%o9(.Te9t 2
3E;;(3 ? DATATA%.Ro*s.Co!t 8 (
CN.Close0 RO:NO 2 ;
1/
E' S!"
Pri+ate S!" %!tto(-Cli#,%yVal se'er As System.O"/e#t& %yVal e As System.E+etAr$s0 1a'les %!tto(.Cli#, I< Messa$e%o9.S6o*3Do @o! *at to a'' t6is Re#or' i yo!r Data"ase3& 3ADD3& Messa$e%o9%!ttos.@esNo& Messa$e%o9I#o.E9#lamatio0 2 Dialo$Res!lt.@es0T6e I< Te9t%o9(;.Te9t 2 33 Or Te9t%o9.Te9t 2 33 Or Te9t%o9((.Te9t 2 33 Or Te9t%o9).Te9t 2 33 Or Te9t%o9B.Te9t 2 33 Or Te9t%o9.Te9t 2 33 Or Te9t%o9.Te9t 2 33 Or Te9t%o9.Te9t 2 33 T6e Ms$%o935IELD S1OULD NOT %E EMPT@30 Else Dim e*ro* As DataRo* 2 DATATA%.Ne*Ro* RO:NO 2 RO:NO 8 ( e*ro*;0 2 Te9t%o9(.Te9t e*ro*(0 2 Te9t%o9).Te9t e*ro*)0 2 Te9t%o9B.Te9t e*ro*B0 2 Te9t%o9.Te9t e*ro*0 2 Te9t%o9.Te9t e*ro*0 2 Te9t%o9.Te9t e*ro*0 2 Te9t%o9.Te9t e*ro*0 2 Com"o%o9(.Te9t e*ro*>0 2 Com"o%o9).Te9t e*ro*F0 2 Te9t%o9(;.Te9t e*ro*(;0 2 Te9t%o9((.Te9t
DATATA%.Ro*s.IsertAte*ro*0& RO:NO0 DA.Up'ateDATATA%0 Ms$%o93DATA INSERTED30 Te9t%o9(.Te9t 2 33 Te9t%o9).Te9t 2 33 Te9t%o9B.Te9t 2 33 Te9t%o9.Te9t 2 33 Te9t%o9.Te9t 2 33 Te9t%o9.Te9t 2 33 Te9t%o9.Te9t 2 33 7Te9t%o9>.Te9t 2 33 7Te9t%o9F.Te9t 2 33 Te9t%o9(;.Te9t 2 33 Te9t%o9((.Te9t 2 33
CN.Close0 DATATA%.Clear0 start0 DA 2 Ne* SqlDataA'apter3sele#t 4
10
E' I< E' I< E' S!" E' Class
,e st'(e*t
Imports System.Data.SqlCliet P!"li# Class DELSTUDENT Dim DATATA%& 'atata"(& 'atata") As Ne* DataTa"le Pri+ate S!" %!tto(-Cli#,%yVal se'er As System.O"/e#t& %yVal e As System.E+etAr$s0 1a'les %!tto(.Cli#, I< Messa$e%o9.S6o*3Do @o! *at to DELETE t6is Re#or'
E' Class
11
A(+i* "o)i*
Imports System.Data.SqlCliet
P!"li# Class
Pri+ate S!"
Pri+ate S!" Li,La"el(-Li,Cli#,e'%yVal se'er As System.O"/e#t& %yVal e As System.:i'o*s.5orms.Li,La"elLi,Cli#,e'E+etAr$s0 1a'les Li,La"el(.Li,Cli#,e' Dim o"/ As Ne* e*!sers o"/.S6o*0 E' S!" Pri+ate S!" %!tto(-Cli#,-(%yVal se'er As System.O"/e#t& %yVal e As System.E+etAr$s0 1a'les %!tto(.Cli#, DA 2Call start0 Ne* SqlDataA'apter3SELECT 4 5ROM a'mi *6ere !serame273 8 Te9t%o9(.Te9t 8 37 a' pass*or'273 8 Te9t%o9).Te9t 8 37 3& CN0 CM 2 Ne* SqlComma'%!il'erDA0 DA.5illDATATA%0
12
RO:NO 2 ; Dim s( As Stri$ 2 TrimDATATA%.Ro*sRO:NO0;0.ToStri$0 Dim s) As Stri$ 2 TrimDATATA%.Ro*sRO:NO0(0.ToStri$0
I< Te9t%o9(.Te9t 2 s( A' Te9t%o9).Te9t 2 s) T6e Pael(.Visi"le 2 5alse Pael).Visi"le 2 Tr!e Else Ms$%o93i+ali' Pass*or'30 Te9t%o9(.5o#!s0 E' I< CN.Close0 E' S!" Pri+ate S!" Li,La"el-Li,Cli#,e'%yVal se'er As System.O"/e#t& %yVal e As System.:i'o*s.5orms.Li,La"elLi,Cli#,e'E+etAr$s0 1a'les Li,La"el.Li,Cli#,e' Dim o"/ As Ne* #6a$epass o"/.S6o*0 E' S!"
E' Class
M-ster o)i*
Imports System.Data.SqlCliet
13
P!"li# Class
Pri+ate S!"
Pri+ate S!" Li,La"el(-Li,Cli#,e'%yVal se'er As System.O"/e#t& %yVal e As System.:i'o*s.5orms.Li,La"elLi,Cli#,e'E+etAr$s0 1a'les Li,La"el(.Li,Cli#,e' Dim o"/ As Ne* e*!sers o"/.S6o*0 E' S!" Pri+ate S!" %!tto(-Cli#,-(%yVal se'er As System.O"/e#t& %yVal e As System.E+etAr$s0 1a'les %!tto(.Cli#, Call start0 DA 2 Ne* SqlDataA'apter3SELECT 4 5ROM a'mi *6ere !serame273 8 Te9t%o9(.Te9t 8 37 a' pass*or'273 8 Te9t%o9).Te9t 8 37 3& CN0 CM 2 Ne* SqlComma'%!il'erDA0 DA.5illDATATA%0 RO:NO 2 ; Dim s( As Stri$ 2 TrimDATATA%.Ro*sRO:NO0;0.ToStri$0 Dim s) As Stri$ 2 TrimDATATA%.Ro*sRO:NO0(0.ToStri$0
I< Te9t%o9(.Te9t 2 s( A' Te9t%o9).Te9t 2 s) T6e Pael(.Visi"le 2 5alse Pael).Visi"le 2 Tr!e Else Ms$%o93i+ali' Pass*or'30 Te9t%o9(.5o#!s0 E' I< CN.Close0 E' S!" Pri+ate S!" Li,La"el-Li,Cli#,e'%yVal se'er As System.O"/e#t& %yVal e As System.:i'o*s.5orms.Li,La"elLi,Cli#,e'E+etAr$s0 1a'les Li,La"el.Li,Cli#,e' Dim o"/ As Ne* #6a$epass o"/.S6o*0 E' S!"
E' Class
14
Ne/ 'ser
Imports System.Data.SqlCliet P!"li# Class e*!sers Dim DATATA%& 'atata"(& 'atata") As Ne* DataTa"le Pri+ate S!" o,-Cli#,%yVal se'er As System.O"/e#t& %yVal e As System.E+etAr$s0 1a'les o,.Cli#, I< Messa$e%o9.S6o*3Do @o! *at to a'' t6is Re#or' i yo!r Data"ase3& 3ADD3& Messa$e%o9%!ttos.@esNo& Messa$e%o9I#o.E9#lamatio0 2 Dialo$Res!lt.@es0T6e I< Te9t%o9(.Te9t 2 33 Or Te9t%o9).Te9t 2 33 T6e Ms$%o935IELD S1OULD NOT %E EMPT@30 Else Dim e*ro* As DataRo* 2 DATATA%.Ne*Ro* RO:NO 2 RO:NO 8 ( e*ro*;0 2 Te9t%o9(.Te9t e*ro*(0 2 Te9t%o9).Te9t
DATATA%.Ro*s.IsertAte*ro*0& RO:NO0 DA.Up'ateDATATA%0 Ms$%o93DATA UPDATED30 CN.Close0 E' I< E' E' S!" I< Pri+ate S!" e*!sers-Loa'%yVal se'er As System.O"/e#t& %yVal e As System.E+etAr$s0 1a'les My%ase.Loa' start0 DA 2 Ne* SqlDataA'apter3sele#t 4
15
CM 2 Ne* SqlComma'%!il'erDA0 DA.5illDATATA%0 CN.Close0 RO:NO 2 ; E' S!" Pri+ate S!" S1O:CURRENTRECORD0 I< ro*o 2 'atata".Ro*s.Co!t T6e Te9t%o9(.Te9t 2 33 Te9t%o9).Te9t 2 33
Else Te9t%o9(.Te9t 2 DATATA%.Ro*sRO:NO0;0.ToStri$ Te9t%o9).Te9t 2 DATATA%.Ro*sRO:NO0(0.ToStri$ E' I< E' S!" E' Class
Change password
Imports System.Data.SqlCliet
P!"li# Class #6a$epass Pri+ate S!" #opass*or'-Cli#,%yVal se'er As System.O"/e#t& %yVal e As System.E+etAr$s0 1a'les #opass*or'.Cli#, Pael(.Visi"le 2 Tr!e Pael(.Lo#atio 2 Ne* System.Dra*i$.Poit>;& B)0 Pael).Visi"le 2 5alse E' S!" Pri+ate S!" #6a$e-Cli#,%yVal se'er As System.O"/e#t& %yVal e As System.E+etAr$s0 1a'les #6a$e.Cli#, start0 Dim !p As Ne* SqlComma'3!p'ate !sers set pass*or'273 ? Te9t%o9).Te9t ? 37 *6ere !serame273 ? Te9t%o9(.Te9t ? 373& CN0 DA.Up'ateComma' 2 !p DA.Up'ateComma'.E9e#!teNo!ery0
16
Ms$%o93PASS:ORD C1ANGED30 #opass*or'.Visi"le 2 Tr!e CN.Close0 E' S!" Pri+ate S!" o,-Cli#,%yVal se'er As System.O"/e#t& %yVal e As System.E+etAr$s0 1a'les o,.Cli#, start0 DA 2 Ne* SqlDataA'apter3SELECT 4 5ROM !sers *6ere pass*or'273 ? Te9t%o9.Te9t ? 37 a' !serame273 ? Te9t%o9B.Te9t ? 373& CN0 CM 2 Ne* sqlComma'%!il'erDA0 DA.5illDATATA%0 RO:NO 2 ; I< DATATA%.Ro*s.Co!t = ; T6e Me.1i'e0 Dim o"/ As Ne* me!
o"/.S6o*0 Else Ms$%o93i+ali' Pass*or'30 E' I< CN.Close0 E' S!" Pri+ate S!" #6a$epass-Loa'%yVal se'er As System.O"/e#t& %yVal e As System.E+etAr$s0 1a'les My%ase.Loa' start0 DA 2 Ne* SqlDataA'apter3SELECT 4 5ROM !sers3& CN0 CM 2 Ne* SqlComma'%!il'erDA0 DA.5illDATATA%0 CN.Close0 E' S!"
E' Class
28
Enquiry form
Imports System.Data.SqlCliet P!"li# Class Eq!iry Dim DATATA%& 'atata"(& 'atata") As Ne* DataTa"le Pri+ate S!" Eq!iry-Loa'%yVal se'er As System.O"/e#t& %yVal e As System.E+etAr$s0 1a'les My%ase.Loa' start0 DA 2 Ne* SqlDataA'apter3sele#t 4
Pri+ate S!" %!tto(-Cli#,%yVal se'er As System.O"/e#t& %yVal e As System.E+etAr$s0 1a'les %!tto(.Cli#, I< Messa$e%o9.S6o*3Do @o! *at to a'' t6is Re#or' i yo!r Data"ase3& 3ADD3& Messa$e%o9%!ttos.@esNo& Messa$e%o9I#o.E9#lamatio0 2 Dialo$Res!lt.@es0T6e I< Te9t%o9>.Te9t 2 33 Or Te9t%o9.Te9t 2 33 Or Te9t%o9).Te9t 2 33 Or Te9t%o9B.Te9t 2 33 Or Te9t%o9.Te9t 2 33 Or Te9t%o9.Te9t 2 33 Or Te9t%o9.Te9t 2 33 T6e Ms$%o935IELD S1OULD NOT %E EMPT@30 Else Dim e*ro* As DataRo* 2 DATATA%.Ne*Ro* RO:NO 2 RO:NO 8 ( e*ro*;0 2 Te9t%o9(.Te9t e*ro*(0 2 Te9t%o9).Te9t
2-
e*ro*)0 2 Te9t%o9B.Te9t e*ro*B0 2 Te9t%o9.Te9t e*ro*0 2 Te9t%o9.Te9t e*ro*0 2 Te9t%o9.Te9t e*ro*0 2 Te9t%o9.Te9t e*ro*0 2 Te9t%o9>.Te9t
DATATA%.Ro*s.IsertAte*ro*0& RO:NO0 DA.Up'ateDATATA%0 Ms$%o93DATA INSERTED30 Te9t%o9(.Te9t 2 33 Te9t%o9).Te9t 2 33 Te9t%o9B.Te9t 2 33 Te9t%o9.Te9t 2 33 Te9t%o9.Te9t 2 33 Te9t%o9.Te9t 2 33 Te9t%o9.Te9t 2 33 Te9t%o9>.Te9t 2 33 CN.Close0 start0 DATATA%.Clear0 DA 2 Ne* SqlDataA'apter3sele#t 4
2/
Pri+ate S!" La"el-Cli#,%yVal se'er As System.O"/e#t& %yVal e As System.E+etAr$s0 1a'les La"el.Cli#, E' S!" Pri+ate S!" La"el-Cli#,%yVal se'er As System.O"/e#t& %yVal e As System.E+etAr$s0 1a'les La"el.Cli#, E' S!" Pri+ate S!" La"el>-Cli#,%yVal se'er As System.O"/e#t& %yVal e As System.E+etAr$s0 1a'les La"el>.Cli#, E' S!" Pri+ate S!" La"elF-Cli#,%yVal se'er As System.O"/e#t& %yVal e As System.E+etAr$s0 1a'les La"elF.Cli#, E' S!" Pri+ate S!" Te9t%o9>-Te9tC6a$e'%yVal se'er As System.O"/e#t& %yVal e As System.E+etAr$s0 1a'les Te9t%o9>.Te9tC6a$e' E' S!" Pri+ate S!" Te9t%o9(-Te9tC6a$e'%yVal se'er As System.O"/e#t& %yVal e As System.E+etAr$s0 1a'les Te9t%o9(.Te9tC6a$e' E' S!" Pri+ate S!" Te9t%o9)-Te9tC6a$e'%yVal se'er As System.O"/e#t& %yVal e As System.E+etAr$s0 1a'les Te9t%o9).Te9tC6a$e' E' S!" Pri+ate S!" Te9t%o9B-Te9tC6a$e'%yVal se'er As System.O"/e#t& %yVal e As System.E+etAr$s0 1a'les Te9t%o9B.Te9tC6a$e' E' S!" Pri+ate S!" Te9t%o9-Te9tC6a$e'%yVal se'er As System.O"/e#t& %yVal e As System.E+etAr$s0 1a'les Te9t%o9.Te9tC6a$e' E' S!" Pri+ate S!" Te9t%o9-Te9tC6a$e'%yVal se'er As System.O"/e#t& %yVal e As System.E+etAr$s0 1a'les Te9t%o9.Te9tC6a$e' E' S!" Pri+ate S!" Te9t%o9-Te9tC6a$e'%yVal se'er As System.O"/e#t& %yVal e As System.E+etAr$s0 1a'les Te9t%o9.Te9tC6a$e' E' S!" Pri+ate S!" Te9t%o9-Te9tC6a$e'%yVal se'er As System.O"/e#t& %yVal e As System.E+etAr$s0 1a'les Te9t%o9.Te9tC6a$e' E' S!" E' Class
20
Events details
Imports System Imports System.Data.SqlCliet
P!"li# Class e+et'et Dim DATATA%& 'atata"(& 'atata") As Ne* DataTa"le
Pri+ate S!" %!tto(-Cli#,%yVal se'er As System.O"/e#t& %yVal e As System.E+etAr$s0 1a'les %!tto(.Cli#, Ms$%o9Com"o%o9(.Te9t ? Com"o%o9(.Sele#te'I'e90 Dim s As Stri$ 2 Com"o%o9(.Te9t Dim sql As Stri$ 2 33 Sele#t Case Com"o%o9(.Sele#te'I'e9 Case ; sql 2 3sele#t 4
3sele#t 4
Case B sql 2 Te9t%o9(.Te9t ? 373
3sele#t 4
21
E' Sele#t DATATA%.Clear0 start0 DA 2 Ne* SqlDataA'aptersql& CN0 CM 2 Ne* SqlComma'%!il'erDA0 DATATA%.Clear0 DA.5illDATATA%0 CN.Close0 RO:NO 2 ; Te9t%o9.Te9t Te9t%o9).Te9t Te9t%o9B.Te9t Te9t%o9.Te9t Te9t%o9.Te9t Te9t%o9.Te9t
2 2 2 2 2 2
DATATA%.Ro*sRO:NO0;0.ToStri$ DATATA%.Ro*sRO:NO0(0.ToStri$ DATATA%.Ro*sRO:NO0)0.ToStri$ DATATA%.Ro*sRO:NO0B0.ToStri$ DATATA%.Ro*sRO:NO00.ToStri$ DATATA%.Ro*sRO:NO00.ToStri$
E' S!"
E' Class
Add new events
Imports System.Data.SqlCliet P!"li# Class A''e+et Dim DATATA%& 'atata"(& 'atata") As Ne* DataTa"le Pri+ate S!" %!tto(-Cli#,%yVal se'er As System.O"/e#t& %yVal e As System.E+etAr$s0 1a'les %!tto(.Cli#,
22
I< Messa$e%o9.S6o*3Do @o! *at to a'' t6is Re#or' i yo!r Data"ase3& 3ADD3& Messa$e%o9%!ttos.@esNo& Messa$e%o9I#o.E9#lamatio0 2 Dialo$Res!lt.@es0T6e I< Te9t%o9).Te9t 2 33 Or Te9t%o9B.Te9t 2 33 Or Te9t%o9.Te9t 2 33 Or Te9t%o9.Te9t 2 33 T6e Ms$%o935IELD S1OULD NOT %E EMPT@30 Else Dim e*ro* As DataRo* 2 DATATA%.Ne*Ro* RO:NO 2 RO:NO 8 ( e*ro*;0 2 Te9t%o9(.Te9t e*ro*(0 2 Te9t%o9).Te9t e*ro*)0 2 Te9t%o9B.Te9t e*ro*B0 2 Te9t%o9.Te9t e*ro*0 2 Te9t%o9.Te9t e*ro*0 2 Te9t%o9.Te9t DATATA%.Ro*s.IsertAte*ro*0& RO:NO0 DA.Up'ateDATATA%0 Ms$%o93DATA INSERTED30 Te9t%o9(.Te9t 2 33 Te9t%o9).Te9t 2 33 Te9t%o9B.Te9t 2 33 Te9t%o9.Te9t 2 33 Te9t%o9.Te9t 2 33 Te9t%o9.Te9t 2 33
CN.Close0 E' I< E' I< E' S!" Pri+ate S!" A''e+et-Loa'%yVal se'er As System.O"/e#t& %yVal e As System.E+etAr$s0 1a'les My%ase.Loa' Te9t%o9(.Te9t 2 re$o start0 DA 2 Ne* SqlDataA'apter3sele#t 4
23
Pri+ate S!" La"el-Cli#,%yVal se'er As System.O"/e#t& %yVal e As System.E+etAr$s0 1a'les La"el.Cli#, E' S!" Pri+ate S!" La"el-Cli#,%yVal se'er As System.O"/e#t& %yVal e As System.E+etAr$s0 1a'les La"el.Cli#, E' S!" Pri+ate S!" La"elF-Cli#,%yVal se'er As System.O"/e#t& %yVal e As System.E+etAr$s0 1a'les La"elF.Cli#, E' S!" Pri+ate S!" Te9t%o9(-Te9tC6a$e'%yVal se'er As System.O"/e#t& %yVal e As System.E+etAr$s0 1a'les Te9t%o9(.Te9tC6a$e' E' S!" Pri+ate S!" Te9t%o9)-Te9tC6a$e'%yVal se'er As System.O"/e#t& %yVal e As System.E+etAr$s0 1a'les Te9t%o9).Te9tC6a$e' E' S!" Pri+ate S!" Te9t%o9B-Te9tC6a$e'%yVal se'er As System.O"/e#t& %yVal e As System.E+etAr$s0 1a'les Te9t%o9B.Te9tC6a$e' E' S!" Pri+ate S!" Te9t%o9-Te9tC6a$e'%yVal se'er As System.O"/e#t& %yVal e As System.E+etAr$s0 1a'les Te9t%o9.Te9tC6a$e' E' S!" Pri+ate S!" Te9t%o9-Te9tC6a$e'%yVal se'er As System.O"/e#t& %yVal e As System.E+etAr$s0 1a'les Te9t%o9.Te9tC6a$e' E' S!" Pri+ate S!" Te9t%o9-Te9tC6a$e'%yVal se'er As System.O"/e#t& %yVal e As System.E+etAr$s0 1a'les Te9t%o9.Te9tC6a$e' E' S!" Pri+ate S!" La"el-Cli#,%yVal se'er As System.O"/e#t& %yVal e As System.E+etAr$s0 1a'les La"el.Cli#, E' S!" Pri+ate S!" La"el>-Cli#,%yVal se'er As System.O"/e#t& %yVal e As System.E+etAr$s0 1a'les La"el>.Cli#, E' S!" E' Class
24
Delete update form
Imports System.Data.SqlCliet
P!"li# Class 'el!p'ate Dim DATATA%& 'atata"(& 'atata") As Ne* DataTa"le Pri+ate S!" %!tto)-Cli#,%yVal se'er As System.O"/e#t& %yVal e As System.E+etAr$s0 1a'les %!tto).Cli#,
I< Messa$e%o9%!ttos.@esNo& Messa$e%o9.S6o*3Do @o! Messa$e%o9I#o.E9#lamatio0 *at to !p'ate t6is Re#or'3& 3DELETE3& 2 Dialo$Res!lt.@es0 T6e start0 Dim CMD As SqlComma' 2 Ne* SqlComma'3!p'ate e+et set e+et-ame273 ? Te9t%o9).Te9t ? 37&e+et-s!"273 ? Te9t%o9B.Te9t ? 37&
E' S!" Pri+ate S!" %!ttoB-Cli#,%yVal se'er As System.O"/e#t& %yVal e As System.E+etAr$s0 1a'les %!ttoB.Cli#,
25
I< Messa$e%o9.S6o*3Do @o! *at to DELETE t6is Re#or'
3sele#t 4
Case B sql 2
3sele#t 4
Te9t%o9(.Te9t ? 373 E' Sele#t DATATA%.Clear0 start0 DA 2 Ne* SqlDataA'aptersql& CN0 CM 2 Ne* SqlComma'%!il'erDA0 DA.5illDATATA%0 CN.Close0 RO:NO 2 ; Te9t%o9.Te9t Te9t%o9).Te9t Te9t%o9B.Te9t Te9t%o9.Te9t Te9t%o9.Te9t Te9t%o9.Te9t
2 2 2 2 2 2
DATATA%.Ro*sRO:NO0;0.ToStri$ DATATA%.Ro*sRO:NO0(0.ToStri$ DATATA%.Ro*sRO:NO0)0.ToStri$ DATATA%.Ro*sRO:NO0B0.ToStri$ DATATA%.Ro*sRO:NO00.ToStri$ DATATA%.Ro*sRO:NO00.ToStri$
E' S!" E' Class
26
eports Student details
Imports System.Data.SqlCliet P!"li# Class STUDENT-REPO Dim DATATA%& 'atata"(& 'atata") As Ne* DataTa"le Pri+ate S!" STUDENT-REPO-Loa'%yVal se'er As System.O"/e#t& %yVal e As System.E+etAr$s0 1a'les My%ase.Loa' start0 DA 2 Ne* SqlDataA'apter3sele#t 4
!a"ulty details
38
Imports System.Data.SqlCliet P!"li# Class
Pri+ate S!"
E' S!" E' Class
3-
E#penses
Imports System.Data.SqlCliet P!"li# Class E9peses-repo Dim DATATA%& 'atata"(& 'atata") As Ne* DataTa"le Pri+ate S!" E9peses-repo-Loa'%yVal se'er As System.O"/e#t& %yVal e As System.E+etAr$s0 1a'les My%ase.Loa' start0 DA 2 Ne* SqlDataA'apter3sele#t 4
O%H.SetDataSo!r#eDATATA%0 CrystalReportVie*er(.ReportSo!r#e 2 O%H E' S!" E' Class
3/
!und details
Imports System.Data.SqlCliet
P!"li# Class 5!'s-repo Dim DATATA%& 'atata"(& 'atata") As Ne* DataTa"le Pri+ate S!" 5!'s-repo-Loa'%yVal se'er As System.O"/e#t& %yVal e As System.E+etAr$s0 1a'les My%ase.Loa' start0 DA 2 Ne* SqlDataA'apter3sele#t 4
E' S!" E' Class
30
Add fund details
Imports System.Data.SqlCliet
P!"li# Class 5!'s Pri+ate S!" %!tto(-Cli#,%yVal se'er As System.O"/e#t& %yVal e As System.E+etAr$s0 1a'les %!tto(.Cli#, I< Messa$e%o9.S6o*3Do @o! *at to a'' t6is Re#or' i yo!r Data"ase3& 3ADD3& Messa$e%o9%!ttos.@esNo& Messa$e%o9I#o.E9#lamatio0 2 Dialo$Res!lt.@es0T6e I<2Te9t%o9).Te9t 2 33 Or Te9t%o9B.Te9t 2 33 Or Te9t%o9.Te9t 33 T6e Ms$%o935IELD S1OULD NOT %E EMPT@30 Else Dim e*ro* As DataRo* 2 DATATA%.Ne*Ro* RO:NO 2 RO:NO 8 ( e*ro*;0 2 Te9t%o9(.Te9t e*ro*(0 2 Te9t%o9).Te9t e*ro*)0 2 Te9t%o9B.Te9t e*ro*B0 2 Te9t%o9.Te9t DATATA%.Ro*s.IsertAte*ro*0& RO:NO0 DA.Up'ateDATATA%0 Ms$%o93DATA INSERTED30 Te9t%o9(.Te9t 2 33 Te9t%o9).Te9t 2 33 Te9t%o9B.Te9t 2 33 Te9t%o9.Te9t 2 33 CN.Close0 E' I<
31
E' I< DATATA%.Clear0 DATATA%.Clear0 start0 DA 2 Ne* SqlDataA'apter3sele#t 4
32
Add e#penses details
Imports System.Data.SqlCliet P!"li# Class E9peses Pri+ate S!" E9peses-Loa'%yVal se'er As System.O"/e#t& %yVal e As System.E+etAr$s0 1a'les My%ase.Loa' DATATA%.Clear0 start0 DA 2 Ne* SqlDataA'apter3sele#t 4
E' S!" Pri+ate S!" %!tto(-Cli#,%yVal se'er As System.O"/e#t& %yVal e As System.E+etAr$s0 1a'les %!tto(.Cli#, I< Messa$e%o9.S6o*3Do @o! *at to a'' t6is Re#or' i yo!r Data"ase3& 3ADD3& Messa$e%o9%!ttos.@esNo& Messa$e%o9I#o.E9#lamatio0 2 Dialo$Res!lt.@es0T6e I< Te9t%o9).Te9t 2 33 Or Te9t%o9B.Te9t 2 33 T6e Ms$%o935IELD S1OULD NOT %E EMPT@30 Else Dim e*ro* As DataRo* 2 DATATA%.Ne*Ro* RO:NO 2 RO:NO 8 (
33
e*ro*;0 2 Te9t%o9(.Te9t e*ro*(0 2 Te9t%o9).Te9t e*ro*)0 2 Te9t%o9B.Te9t
DATATA%.Ro*s.IsertAte*ro*0& RO:NO0 DA.Up'ateDATATA%0 Ms$%o93DATA INSERTED30 Te9t%o9(.Te9t 2 33 Te9t%o9).Te9t 2 33 Te9t%o9B.Te9t 2 33
CN.Close0 E' I< E' I< E' S!" E' Class
34
