Project Report on:

SUBMITTED BY: ZEESHAN KHAN AJAZ AHMED MOHAMMED JAVED

GUIDED BY: Mr. TANVEER

A KNO!"EDGEMENT
It is great pleasure to acknowledge the guidance and support we have received in This project work on Institute Management. We are greatly overwhelmed with joy and guidance towards each and everyone, who have extended their valuable support and full co operation during the time of project. We are deeply indebted to !r. Tanveer our project guide, throughout our work. Work fails us to convery our deep sense of gratitude towards him. We would like to take opportunity to record our heartily thanks to the whole staff of "ll #aints$, for their co operation, precious suggestions, guidance and encouragement during the course of %&". We are also very much thankful to all colleagues for their co operation during our project.

ert#$#c%te o$ G&#'e

CERTIFICATE
This is to certify that this project entitled In(t#t&te M%n%)e*ent #ubmitted in partial fulfillment of the degree of %achelor of computer "pplication to the A++ S%#nt(, co++e)e o$ Sc#nce - o**erce done by Zee(.%n /.%n0 Aj%1 A.*e'0 Mo.%**e' J%2e' is an authentic work carried out by her at %hopal , under my 'uidance. The matter embodied in this project work has not been submitted earlier for award of any degree or diploma to the best of my knowledge and belief.

Signature of the student

Signature of the Guide

Mr Tanveer

CERTIFICATE
This is to certify that the Project Report Entitled I !TIT"TE MA A#EME T$% !u&mitted toAll Saints college of Science & Commerce$ has &een carried out &y the follo'ing student for the fulfillment of the re(uirement of )achelor of computer application *)CA+% is has &een su&mitted any 'here else for the a'ard of any e,amination or a'ard of any degree-

D%te : P+%ce

SYNOPSIS O3 THE PROJE T

Introduction
The Insitute uses Excel, and maintains various lists of students , staff etc , and prints the list when needed, however it is not possible them to share the data from multiple system in multi user environment, there is lot of duplicate work, and chance of mistake. When the product price are changed they need to update each and every excel file. There is no option to find and print previous saved invoice. There is no security; any body can access any report and sensitive data, also no reports to find out the important report. This system is used to overcome the entire problem which they are facing currently, and making complete atomi ation of institute management system

Objective
This section presents a conceptual overview of the solution, and then provides an introduction to its re!uirements.

"olution #oncept
The Institute $anagement "ystem consists of% Enquiry, Student,Course etc% &utomate the current manual system and maintain the searchable student, en!uiry system, admission system and database, maintain the data security, user rights. Re ort !eneration% & 'eport (eneration system will be developed for the user and management of Institute $anagement "ystem. This $I" system will have both details and summary type reports for analysis en!uiry, student reports, facilities reports ,salary reports etc.

It reduces the data entry implementation of the system.

work

and

!uick

3"O! HART

START

I*(+T ("## W,-.

(assword not found

If password

)es

Tr4 %)%#n

M%#n *en&

T.en

STOP
MAIN Men& o$ t.e Project

OUT"OOK FACULTY

FEE

LIBRARY MGT MGT NOC FACILITY E5IT

S&6 Men& o$ t.e Project

Enquiry Form

R%)#(tr%t#on 3or*

St%t&( O$ A'*#((#on

3%c&+t4 In$or*%t#on Per(on%+ In$or*%t#on S%+%r4 M%n%)e*ent 3%c&+t4 St%t&(

/00
3ee "o)#n 3or* 3ee Str&ct&re S&6*#((#on 3ee 3or*

"#6r%r4 M)t
"#6r%r4 In$o

Me*6er(.#p 3or*

I((&e Boo/ 3or*

Boo/ Stoc/ 3or*

St%t&( O$ I((&e Boo/(

St%t&( O$ Boo/ Stoc/

E7#t

E7#t

"#e follo$ing user ty es are e% ected for Institute &anagement System'

(ser #ounselor )ack office &ccountant $I" Executive

)rief *escri tion of (se Actions Enters all student en!uiry *ew admission record, course and all admission information will be maintained +iew and print student admission record (enerate reports, view and print facility , student and other reports

+eatures,+unctionality
The following sections summari e features and functionality described by use case. ,lease see Institute $anagement "ystem - 'e!uirements $anage "tudents. &naly e "tudent /ata $ust be able to analy e student data $ust be able to sort student record

Soft$are and -ard$are Requirement

!eneral Requirement for Server,Client'
"y e Work "tation0 *ode Soft$are 1. Windows 2, 3. +) 'un time 4. $" 5ffice -ard$are 1. ,.6 3. '&$ .378 $)

*evelo ment "ools and "ec#nologies 9ront End

1. +) /5T *ET .#y /)01E"2 +).*ET is built on the Windows "erver "ystem to take ma:or advantage of the 5" and which comes with a host of different servers which allows for building, deploying, managing and maintaining Windows )ased solutions. The Windows "erver "ystem is designed with performance as priority and it provides scalability, reliability. The advantage of +).*ET includes 'apid &pplication /evelopment ;'&/< "upport. ,owerful Windows.based &pplications "implified /eployment ,owerful, 9lexible, "implified /ata &ccess Improved #oding /irect &ccess to the 5" ,latform 5b:ect.5riented #onstructs #5$ Interoperability

)ac3 End
1. $" &ccess .#y &S Access2 $" &ccess is desktop '/$" support small application with all features like relational !uery, different data types, :oins, and !uery. Includes Easy to use and easy to deployment. Integration with Windows 5" "calability Import and Export of data in all ma:or database system. #entrali ed $anagement 'eliability

*ata )ase "ables

En8&#r4 Entr4
SNO
1 2 5 6 3 7 8 : ; 1< 11 12 15

3IE"D NAME
*ame /4name !4name /4occ "ddress !ob4mo .ob .oa &ourse (re4&lass (re4(er (re4&ol (re4+ni

DATA TYPE
Text Text Text Text Text *umber .ate9Time .ate9Time Text Text Text Text Text

SIZE
23 23 23 23 23 13 13 13 23 23 23 23 23

PTU SNO
1 2 5 6 3 7

3IE"D NAME
&ourse4&ode &ourse4*ame .uration !ax4dur 0ligibility /ee4plan

DATA TYPE
Text Text Text Text Text Text

SIZE
23 23 23 23 23 23

M U
SNO
1 2 5 6 3 7

3IE"D NAME
&ourse4&ode &ourse4*ame .uration !ax4dur 0ligibility /ee4plan A"MA

DATA TYPE
Text Text Text Text Text Text

SIZE
23 23 23 23 23 23

NO

3#e+' N%*e
1 2 5 6 &ourse4&ode &ourse4*ame .uration /ee4plan

D%t% t4pe
Text Text Text *umber

S#1e
23 23 23 1<

3A U"TY
NO

9 : = ; ? @ B C 9> 99 9: 9E 9= 9;

3#e+' N%*e N%*e 3<n%*e M<n%*e A)e Po(t A&%+# E7per#ence Do6 S%+%r4 Doj T#*e<'&r%t#on Enter<t#*e E7#t<t#*e St%t&(

D%t% t4pe Te7t Te7t Te7t Te7t Te7t Te7t Te7t D%teDt#*e Te7t D%teDt#*e Te7t Te7t Te7t Te7t

S#1e :; ; ;> 9> 9> 9> 9> 9> 9> 9> 9> B B

SA"ARY
NO

3#e+' N%*e 9 : E = ; N%*e Po(t S%+%r4 S%+%r4<'%te St%t&(

D%t% t4pe Te7t Te7t Te7t D%teDt#*e Te7t

S#1e :; :; :; 9> :;

"IBRARY
NO

9 : = ; ?

3#e+' N%*e Boo/<co'e Boo/<n%*e P&6<n%*e I((&e<'%te Re+#2#n)<'%te

D%t% t4pe A&toN&*6er Te7t Te7t D%teDt#*e D%teDt#*e

S#1e :; :; ;> 9> 9>

&E&)ERS-I4
NO

9 : E =

3#e+' N%*e D%t% t4pe N%*e Te7t o&r(e Te7t Do<*e*6er(.#p D%teDt#*e 3ee N&*6er

S#1e :; :; ;> 9>

ISS(E5)OO6
NO

9 : E = ; ? @

3#e+' N%*e D%t% t4pe N%*e Te7t o&r(e Te7t I((&e<'%te D%teDt#*e Ret&rn#n)<'%te D%teDt#*e Boo/<co'e Te7t Boo/<n%*e Te7t P&6<n%*e Te7t

S#1e :; :; 9> 9> :; :; :;

#T,&=

NO

9 : E = ; ?

3#e+' N%*e Ser#%+<no Boo/<co'e Boo/<n%*e P&6<n%*e Me'#&* No<cop#e(

D%t% t4pe A&toN&06er Te7t Te7t Te7t Te7t Te7t

S#1e :; :; 9> 9> :; :;

/00

NO

9 : = ; ? @ B C 9> 99 9: 9E 9= 9;

3#e+' N%*e En<no N%*e o&r(e A*o&nt B%+%nce Mo'e<P%4*ent Do' Tot%+<$ee

D%t% t4pe A&toN&*6er Te7t Te7t Te7t Te7t Te7t D%teDt#*e

S#1e :; :; :; :; :; :; 9>

OBJE TIVE - S OPE O3 THE PROJE T

This project is made for one of the institutes of %hopal, they have number of courses , lots of students and number of employees (resently they issue all records handwritten and they enter details in manual register. "nd maintain !# 0xcel file for employees, students and facilities etc. They want computeri>ation of their manual records

There is no security? any body can access any report and sensitive data, also no reports to find out the employee , student and other report. This Institute management system is used to overcome the entire problem which they are facing currently, and making complete atomi>ation of manual Institute management system

THEORETI A" BA K GROUND

-e@uirements #ummary The following preliminary lists are based on initial interviews %usiness -e@uirements The business goal for the application is to support an increase the productivity and complete automation of existing manual bill and invoice generation process. %usiness re@uirements are discussed in the #cope section, with the following additional detail. To enable them to accomplish this goal, they want to extract meaningful data that easily answers the following @uestions:

!.%t %re t.e e%r+4 F%rn#n) (#)n( o$ pro6+e*(G !.o %re *4 6e(t c&(to*er( %cro(( pro'&ct +#ne(G !#t. F.o* 'o I $oc&( *4 e$$ort( $or 6&#+'#n) % +on)Hter* re+%t#on(.#pG !.%t %re *4 c&(to*er(I #((&e( %( )ro&p(G Geo)r%p.#c%++40 F.ere %re *4 6e(t c&(to*er(G !.%t pro'&ct( %re *4 c&(to*er( 6&4#n) %n' %t F.%t r%teG U(er Re8&#re*ent( U(er re8&#re*ent( %re c%te)or#1e' 64 &(er t4pe. Accountant Up'%te recor'( 'et%#+(0 #nc+&'#n) co&r(e0 p.oto0 %n' 'e(cr#pt#on A''0 'e+ete0 %n' &p'%te (t&'ent recor' (pec#$#c%t#on( Gener%te report( %n' c.ec/ t.e %2%#+%6#+#t40 F.en nee'e'. MIS E7ec&t#2e Gener%te Report( %( per re8&#re*ent. S.%re t.e '%t%0 %n' con2ert report( to '#$$erent $or*%t +#/e Te7t0 SV.

Oper%t#on%+ Re8&#re*ent( T.e $o++oF#n) re8&#re*ent( pro2#'e % .#).H+e2e+ 2#eF o$ .oF t.e (4(te* F#++ r&n: Proce((or &(%)e (.o&+' not e7cee' B> percent '&r#n) conc&rrent &(e(. B%c/&p( F#++ occ&r #ncre*ent%++4 t.ro&).o&t t.e '%4. En(&re t.%t #n$or*%t#on #( e%(4 to %cce(( e#t.er0 %n' *e%n#n)$&+ $or t.e (%+e( repre(ent%t#2e %n' t.e co*p%n4. M#n#*#1e t.e tec.n#c%+ /noF+e')e t.%t (%+e( %n' *%r/et#n) (t%$$ nee' to %cce(( t.e '%t%0 )ener%te %' .oc 8&er#e(0 tr%c/ pro*ot#on(0 %n' 2#eF c&(to*er (e)*ent%t#on #n$or*%t#on. An4 c.%n)e to #n$or*%t#on *&(t 6e re$+ecte' #**e'#%te+40 %n' t.e c.%n)e( *&(t 6e prop%)%te' to t.e (e%rc. en)#ne (o t.%t e*p+o4ee( t.%t per$or* (e%rc.e( (ee t.#( neF #n$or*%t#on. T.e %pp+#c%t#on (.o&+' For/ F#t. t.e e7#(t#n) co**&n#c%t#on( %n' netFor/#n) #n$r%(tr&ct&re. T.e %pp+#c%t#on (.o&+' 'ep+o4 F#t. % *#n#*&* o$ %''#t#on%+ oper%t#on%+ proce((e(0 *%n&%+ or ot.erF#(e. S4(te* Re8&#re*ent( T.e(e %re %''#t#on%+ con(tr%#nt( $ro* % (4(te* per(pect#2e: Pre2#o&( '%t% o$ c&(to*er recor'( 'et%#+( *&(t 6e #*porte' #n t.e neF (4(te*. T.e %'*#n#(tr%tor *&(t 6e %6+e to *on#tor e2er4t.#n) $ro* t.e IT 'ep%rt*ent. T.e #n$or*%t#on *&(t 6e %cce((#6+e 64 e2er4one #n t.e co*p%n4 %( per t.e r#).t( (pec#$4. DE3INITION O3 PROB"EM

The problem was the control of all datas and records of the Institute. Aence it became necessary for complete automi>ation of the 0mployee, student and other records. In manual system , lots of redundant data is used , with lots of time wastage. It was also needed to safe guard the data. Aere our aim is to solve and update the records of the Insitute.

SYSTEM ANA"YSIS - DESIGN

Design Goals and Cons rain s Per$or*%nce *o more than a 3 percent degradation in average @uery response is allowed while all concurrent user are using the system. (rocessor utili>ation should not exceed :< percent during all concurrent users are using the system. A2%#+%6#+#t4 %ecause the system is accessed by sales representative to book the order and print the invoice, and their should not be any single point of failure. Re+#%6#+#t4 %ecause of the need no single point failure, automatic failover will be re@uired. In addition, existing disaster recovery and backup plans and procedures must be revised to incorporate the #ystem. Sc%+%6#+#t4 The #ystem an average load of 3< concurrent users after the system is fully operational, and expects that to grow by 3 percent each year for the next five years. Sec&r#t4 systems /or the sensitive customer and order data, all users will need to log on the system with their user id and password. 0very resource in the system are defined by the role and privileged. #ystem administrator assigned user role and privileged for their access rights.

Interoper%6#+#t4 In Bersion 1.< of the #ystem, there are no re@uirements for interoperability with other. "oc%t#on The #ystem are used in the company office only. Set&pDIn(t%++%t#on #etup and installation must not interrupt the sales staff$s daily tasks and work flow.

METHODO"OGY ADOPTED0 SYSTEM IMP"EMENTATION - DETAI"S O3 HARD!ARE SO3T!ARE USED

M#n#*&* (pec#$#c%t#on Pent#&* IV o*p&ter VGA B>>J?>> Me)% p#7e+ :;? MB RAM 3or F#n'oF,( DVDHROM. Opt#c%+ Mo&(e - M&+t#*e'#% Ke46o%r'. 3ree D#(/ Sp%ce Re8&#re*ent: H ;>> MB K$or ProjectL M#cro(o$t !#n'oF(H5P0 :>>>0 :>>; or +%ter.

SO3T!ARE USED MS O33I E 3OR DO UMENTATION VB. NET AS 3RONT END MS A ESS 3OR DATA BASE

9. ER DIAGRAM

#ala ry Tim e dura tion .ob

nam e

/4 nm

!4 nm

age .oj

/"&+CT)

(ost Dual i 0xp erie nce

#tatus

0xit Tim e

0nte r Tim e

Taken

(ost nam e #"C"-)

#tatus #alar y date

#alar y

0n no

*ame

&ours e /00 Tota l fee

.od

%alanc e

"mount

!od e pay

(ost name

#tatus (T+9!&+9"C!"

#alar y

#tatus

#alary date

(ub4n m

%4cod e Issue date

%4name (ub4n m -eliving date &ourse

Issue date -etur ning date

Cibrary

Issu e
name

Issue book

%4nam e %4code

PRINT OUT O3 THE ODE SHEET Cogin /orm1

"o)#n 3or*9 o'#n)

Public Class LoginForm1 Dim txtpassword As String Dim user As String Private Sub OK_Clic !"#$al sender As S#stem%Ob&ect' "#$al e As S#stem%(ventArgs) *andles OK%Clic +, -sername.ext"ox%.ext / 0intellicon0 And Password.ext"ox%.ext / 0mcu0 .1en 2D+Parent1%S1ow!) 2e%*ide!) (lse 2sg"ox!0+nvalid Password'Please .r# Again0' 2sg"oxSt#le%(xclamation' 0LO3+40) (nd +, (nd Sub Private Sub Cancel_Clic !"#$al sender As S#stem%Ob&ect' "#$al e As S#stem%(ventArgs) *andles Cancel%Clic 2e%Close!) (nd Sub (nd Class

MDI FORM

MDI FORM
+mports S#stem%5indows%Forms Public Class 2D+Parent1 Private Sub S1ow4ewForm!"#$al sender As Ob&ect' "#$al e As (ventArgs) *andles 4ew.oolStrip"utton%Clic 6 Create a new instance o, t1e c1ild ,orm% Dim C1ildForm As 4ew S#stem%5indows%Forms%Form 6 2a e it a c1ild o, t1is 2D+ ,orm be,ore s1owing it% C1ildForm%2diParent / 2e m_C1ildForm4umber 7/ 1 C1ildForm%.ext / 05indow 0 8 m_C1ildForm4umber C1ildForm%S1ow!) (nd Sub Private Sub OpenFile!"#$al sender As Ob&ect' "#$al e As (ventArgs) *andles Open.oolStrip"utton%Clic Dim OpenFileDialog As 4ew OpenFileDialog OpenFileDialog%+nitialDirector# / 2#%Computer%FileS#stem%SpecialDirectories%2#Documen ts OpenFileDialog%Filter / 0.ext Files !9%txt):9%txt:All Files !9%9):9%90 +, !OpenFileDialog%S1owDialog!2e) / S#stem%5indows%Forms%Dialog;esult%OK) .1en Dim File4ame As String / OpenFileDialog%File4ame 6 .ODO< Add code 1ere to open t1e ,ile% (nd +, (nd Sub

Private Sub SaveAs.oolStrip2enu+tem_Clic !"#$al sender As Ob&ect' "#$al e As (ventArgs) Dim SaveFileDialog As 4ew SaveFileDialog SaveFileDialog%+nitialDirector# / 2#%Computer%FileS#stem%SpecialDirectories%2#Documen ts SaveFileDialog%Filter / 0.ext Files !9%txt):9%txt:All Files !9%9):9%90 +, !SaveFileDialog%S1owDialog!2e) / S#stem%5indows%Forms%Dialog;esult%OK) .1en Dim File4ame As String / SaveFileDialog%File4ame 6 .ODO< Add code 1ere to save t1e current contents o, t1e ,orm to a ,ile% (nd +, (nd Sub Private Sub (xit.oolsStrip2enu+tem_Clic !"#$al sender As Ob&ect' "#$al e As (ventArgs) 3lobal%S#stem%5indows%Forms%Application%(xit!) (nd Sub Private Sub Cut.oolStrip2enu+tem_Clic !"#$al sender As Ob&ect' "#$al e As (ventArgs) 6 -se 2#%Computer%Clipboard to insert t1e selected text or images into t1e clipboard (nd Sub Private Sub Cop#.oolStrip2enu+tem_Clic !"#$al sender As Ob&ect' "#$al e As (ventArgs) 6 -se 2#%Computer%Clipboard to insert t1e selected text or images into t1e clipboard (nd Sub Private Sub Paste.oolStrip2enu+tem_Clic !"#$al sender As Ob&ect' "#$al e As (ventArgs) 6-se 2#%Computer%Clipboard%3et.ext!) or 2#%Computer%Clipboard%3etData to retrieve in,ormation ,rom t1e clipboard%

(nd Sub

Private Sub Cascade.oolStrip2enu+tem_Clic !"#$al sender As Ob&ect' "#$al e As (ventArgs) 2e%La#out2di!2diLa#out%Cascade) (nd Sub Private Sub .ile$erticle.oolStrip2enu+tem_Clic !"#$al sender As Ob&ect' "#$al e As (ventArgs) 2e%La#out2di!2diLa#out%.ile$ertical) (nd Sub Private Sub .ile*ori=ontal.oolStrip2enu+tem_Clic !"#$al sender As Ob&ect' "#$al e As (ventArgs) 2e%La#out2di!2diLa#out%.ile*ori=ontal) (nd Sub Private Sub Arrange+cons.oolStrip2enu+tem_Clic !"#$al sender As Ob&ect' "#$al e As (ventArgs) 2e%La#out2di!2diLa#out%Arrange+cons) (nd Sub Private Sub CloseAll.oolStrip2enu+tem_Clic !"#$al sender As Ob&ect' "#$al e As (ventArgs) 6 Close all c1ild ,orms o, t1e parent% For (ac1 C1ildForm As Form +n 2e%2diC1ildren C1ildForm%Close!) 4ext (nd Sub Private m_C1ildForm4umber As +nteger / > Private Sub 2enuStrip_+temClic ed!"#$al sender As S#stem%Ob&ect' "#$al e As

S#stem%5indows%Forms%.oolStrip+temClic ed(ventArgs) *andles 2enuStrip%+temClic ed (nd Sub Private Sub .oolStrip2enu+tem?_Clic !"#$al sender As S#stem%Ob&ect' "#$al e As S#stem%(ventArgs) *andles .oolStrip2enu+tem?%Clic 3eneral_in,o%2diParent / 2e 3eneral_in,o%S1ow!) (nd Sub Private Sub 2D+Parent1_Load!"#$al sender As S#stem%Ob&ect' "#$al e As S#stem%(ventArgs) *andles 2#"ase%Load (nd Sub Private Sub ;(3+S.A.+O4FO;2.oolStrip2enu+tem_Clic !"#$al sender As S#stem%Ob&ect' "#$al e As S#stem%(ventArgs) *andles ;(3+S.A.+O4FO;2.oolStrip2enu+tem%Clic (n@uir#%2diParent / 2e (n@uir#%S1ow!) (nd Sub Private Sub S.A.-SOFAD2+SS+O4.oolStrip2enu+tem_Clic !"#$al sender As S#stem%Ob&ect' "#$al e As S#stem%(ventArgs) *andles S.A.-SOFAD2+SS+O4.oolStrip2enu+tem%Clic status_add%2diParent / 2e status_add%S1ow!) (nd Sub Private Sub Librar.oolStrip2enu+tem_Clic !"#$al sender As S#stem%Ob&ect' "#$al e As S#stem%(ventArgs) *andles Librar.oolStrip2enu+tem%Clic Librar#%2diParent / 2e Librar#%S1ow!) (nd Sub

Private Sub 2embers1ip.oolStrip2enu+tem_Clic !"#$al sender As S#stem%Ob&ect' "#$al e As S#stem%(ventArgs) *andles 2embers1ip.oolStrip2enu+tem%Clic 2embers1ip%2diParent / 2e 2embers1ip%S1ow!) (nd Sub Private Sub +ssue"oo .oolStrip2enu+tem_Clic !"#$al sender As S#stem%Ob&ect' "#$al e As S#stem%(ventArgs) *andles +ssue"oo .oolStrip2enu+tem%Clic +ssue_(ntr#%2diParent / 2e +ssue_(ntr#%S1ow!) (nd Sub Private Sub "oo Stoc .oolStrip2enu+tem_Clic !"#$al sender As S#stem%Ob&ect' "#$al e As S#stem%(ventArgs) *andles "oo Stoc .oolStrip2enu+tem%Clic "oo _stoc %2diParent / 2e "oo _stoc %S1ow!) (nd Sub Private Sub .oolStrip2enu+temA_Clic !"#$al sender As S#stem%Ob&ect' "#$al e As S#stem%(ventArgs) *andles .oolStrip2enu+temA%Clic Application%(xit!) (nd Sub Private Sub Facult#+n,o.oolStrip2enu+tem_Clic !"#$al sender As S#stem%Ob&ect' "#$al e As S#stem%(ventArgs) *andles Facult#+n,o.oolStrip2enu+tem%Clic Facult#_login%2diParent / 2e Facult#_login%S1ow!) (nd Sub Private Sub Personal+n,ormation.oolStrip2enu+tem_Clic !"#$al

sender As S#stem%Ob&ect' "#$al e As S#stem%(ventArgs) *andles Personal+n,ormation.oolStrip2enu+tem%Clic Facult#%2diParent / 2e Facult#%S1ow!) (nd Sub Private Sub .oolStrip2enu+tem1_Clic !"#$al sender As S#stem%Ob&ect' "#$al e As S#stem%(ventArgs) *andles .oolStrip2enu+tem1%Clic (nd Sub Private Sub Salar#2anagement.oolStrip2enu+tem_Clic !"#$al sender As S#stem%Ob&ect' "#$al e As S#stem%(ventArgs) *andles Salar#2anagement.oolStrip2enu+tem%Clic Facult#_salar#%2diParent / 2e Facult#_salar#%S1ow!) (nd Sub Private Sub Facult#Status.oolStrip2enu+tem_Clic !"#$al sender As S#stem%Ob&ect' "#$al e As S#stem%(ventArgs) *andles Facult#Status.oolStrip2enu+tem%Clic Facult#_status%2diParent / 2e Facult#_status%S1ow!) (nd Sub Private Sub .oolStrip2enu+temB_Clic !"#$al sender As S#stem%Ob&ect' "#$al e As S#stem%(ventArgs) *andles .oolStrip2enu+temB%Clic (nd Sub Private Sub .oolStrip2enu+temC_Clic !"#$al sender As S#stem%Ob&ect' "#$al e As S#stem%(ventArgs) *andles .oolStrip2enu+temC%Clic (nd Sub

Private Sub FeeLoginForm.oolStrip2enu+tem_Clic !"#$al sender As S#stem%Ob&ect' "#$al e As S#stem%(ventArgs) *andles FeeLoginForm.oolStrip2enu+tem%Clic Fee_login%2diParent / 2e Fee_login%S1ow!) (nd Sub Private Sub FeeStatus.oolStrip2enu+tem_Clic !"#$al sender As S#stem%Ob&ect' "#$al e As S#stem%(ventArgs) *andles FeeStatus.oolStrip2enu+tem%Clic Fee_status%2diParent / 2e Fee_status%S1ow!)
(nd Sub

Private Sub FeeForm.oolStrip2enu+tem_Clic !"#$al sender As S#stem%Ob&ect' "#$al e As S#stem%(ventArgs) *andles FeeForm.oolStrip2enu+tem%Clic Fee_,orm%2diParent / 2e Fee_,orm%S1ow!) (nd Sub Private Sub
FeeStructure.oolStrip2enu+tem_Clic !"#$al

sender As S#stem%Ob&ect' "#$al e As S#stem%(ventArgs) *andles FeeStructure.oolStrip2enu+tem%Clic Fee_structure%2diParent / 2e Fee_structure%S1ow!) (nd Sub

Gener%+ En8&#r4 3or*

Gener%+ En8&#r4 3or* o'#n)

Public Class 3eneral_in,o Private Sub ;adio"utton1_C1ec edC1anged!"#$al sender As S#stem%Ob&ect' "#$al e As S#stem%(ventArgs) *andles ;adio"utton1%C1ec edC1anged +, ;adio"utton1%(nabled / .rue .1en Combo"ox1%+tems%Clear!) Combo"ox1%+tems%Add!02S OFF+C(0) Combo"ox1%+tems%Add!0C0) Combo"ox1%+tems%Add!0C770) Combo"ox1%+tems%Add!0DA$A0) Combo"ox1%+tems%Add!0%4(.0) Combo"ox1%+tems%Add!0.ALLE0) (nd +, (nd Sub Private Sub Combo"ox1_Selected+ndexC1anged!"#$al sender As S#stem%Ob&ect' "#$al e As S#stem%(ventArgs) *andles Combo"ox1%Selected+ndexC1anged x / Combo"ox1%Selected+tem Sub&ect%S1ow!) (nd Sub Private Sub ;adio"uttonB_C1ec edC1anged!"#$al sender As S#stem%Ob&ect' "#$al e As S#stem%(ventArgs) *andles ;adio"uttonB%C1ec edC1anged +, ;adio"uttonB%(nabled / .rue .1en Combo"ox1%+tems%Clear!) Combo"ox1%+tems%Add!0DCA0)

Combo"ox1%+tems%Add!0P3DCA0) (nd +, (nd Sub Private Sub ;adio"uttonC_C1ec edC1anged!"#$al sender As S#stem%Ob&ect' "#$al e As S#stem%(ventArgs) *andles ;adio"uttonC%C1ec edC1anged +, ;adio"uttonC%(nabled / .rue .1en Combo"ox1%+tems%Clear!) Combo"ox1%+tems%Add!0""A0) Combo"ox1%+tems%Add!0"CA0) (nd +, (nd Sub Private Sub ;adio"uttonF_C1ec edC1anged!"#$al sender As S#stem%Ob&ect' "#$al e As S#stem%(ventArgs) *andles ;adio"uttonF%C1ec edC1anged +, ;adio"uttonF%(nabled / .rue .1en Combo"ox1%+tems%Clear!) Combo"ox1%+tems%Add!02CA0) Combo"ox1%+tems%Add!02"A0) Combo"ox1%+tems%Add!02SC +.0) Combo"ox1%+tems%Add!02CAGL(0) Combo"ox1%+tems%Add!02"AGL(0) Combo"ox1%+tems%Add!02SC +.GL(0) (nd +, (nd Sub Private Sub 3eneral_in,o_Load!"#$al sender As S#stem%Ob&ect' "#$al e As S#stem%(ventArgs) *andles 2#"ase%Load (nd Sub

UNI!ER"ITY FORM

UNIVERSITY 3ORM
+mports S#stem%Data%oledb

ODING

Public Class universit# Dim ds As 4ew DataSet Dim st As String Private Sub universit#_Load!"#$al sender As Ob&ect' "#$al e As S#stem%(ventArgs) *andles 2e%Load Lin Label1%$isible / False Lin LabelB%$isible / False LabelB%$isible / False LabelC%$isible / False (nd Sub Private Sub Data3rid$iew1_CellContentClic !"#$al sender As S#stem%Ob&ect' "#$al e As S#stem%5indows%Forms%Data3rid$iewCell(ventArgs) *andles Data3rid$iew1%CellContentClic (nd Sub Private Sub "utton1_Clic !"#$al sender As S#stem%Ob&ect' "#$al e As S#stem%(ventArgs) *andles "utton1%Clic .ext"ox1%.ext / 02AK*A4LAL0 +, .ext"ox1%.ext / 02AK*A4LAL0 .1en Dim adp As 4ew OleDbDataAdapter!0select 9 ,rom mcu0' 0provider/microso,t%&et%oledb%F%>H data source / D<Igun&an%mdb 0) adp%Fill!ds' 0mcu0) Dim dv As 4ew Data$iew!ds%.ables!0mcu0)) Data3rid$iew1%DataSource / dv Lin Label1%$isible / .rue Lin LabelB%$isible / .rue LabelB%$isible / .rue LabelC%$isible / .rue

LabelB%.ext / 02C- .1e Fee installment o, t1e next semester 1as to be paid be,ore0 _ 7 0t1e start o, exam o, previous semester as per t1e dates communicated0 _ 7 0 b# t1e -niversit#%.1e ,irst installment 1as to be paid at 0 _ 7 0t1e time o, Admission%(xamination,ee o, ;sJJ>K per semester 1as to be paid to t1e learning0 _ 7 0 center separetel# at t1e time o, admissionIreadmission%0 LabelC%.ext / 0.1e semester ,ee as pere scribed in t1e prospectus 1as to be paid b# t1e student O4LE in s1ape o, a demanddra,t in t1e name o, ;(3+S.;A;'2AK*A4LAL -4+$(;S+.E'pa#able at t1e and t1e exam ,ee o, ;sJJ>KG can be paid b# cas1 at t1e learning center%0 Lin Label1%.ext / 0+nstructions For Pa#ment0 Lin LabelB%.ext / 02ode O, Pa#ment0 (nd +, (nd Sub Private Sub "uttonB_Clic !"#$al sender As S#stem%Ob&ect' "#$al e As S#stem%(ventArgs) *andles "uttonB%Clic .ext"ox1%.ext / 0AL2A0 Dim adp As 4ew OleDbDataAdapter!0select 9 ,rom alma0' 0provider/microso,t%&et%oledb%F%>Hdata source / D<Igun&an%mdb0) +, .ext"ox1%.ext / 0AL2A0 .1en st / 0select 9 ,rom alma0 adp%Fill!ds' 0alma0) Dim dv As 4ew Data$iew!ds%.ables!0alma0)) Data3rid$iew1%DataSource / dv Lin Label1%$isible / .rue Lin LabelB%$isible / .rue LabelB%$isible / .rue

LabelC%$isible / .rue LabelB%.ext / 0AL2A .1e Fee installment o, t1e next semester 1as to be paid be,ore _t1e start o, exam o, previous semester as per t1e dates _communicated b# t1e -niversit#%.1e ,irst installment 1as to be paid at t1e time o, Admission%(xamination,ee o, ;sJJ>K per semester 1as to be paid to t1e learning center separetel# at t1e time o, admissionIreadmission%0 LabelC%.ext / 0.1e semester ,ee as pere scribed in t1e prospectus 1as to be paid b# t1e student O4LE in s1ape o, a demanddra,t in t1e name o, ;(3+S.;A;'AL2A'pa#able and t1e exam ,ee o, ;sJJ>KG can be paid b# cas1 at t1e learning center%0 Lin Label1%.ext / 0+nstructions For Pa#ment0 Lin LabelB%.ext / 02ode O, Pa#ment0

(nd +, (nd Sub Private Sub "uttonC_Clic !"#$al sender As S#stem%Ob&ect' "#$al e As S#stem%(ventArgs) *andles "uttonC%Clic .ext"ox1%.ext / 0P.-0 Dim adp As 4ew OleDbDataAdapter!0select 9 ,rom ptu0' 0provider/microso,t%&et%oledb%F%>Hdata source /D<Igun&an%mdb0) +, .ext"ox1%.ext / 0P.-0 .1en st / 0select 9 ,rom ptu0 adp%Fill!ds' 0ptu0) Dim dv As 4ew Data$iew!ds%.ables!0ptu0)) Data3rid$iew1%DataSource / dv Lin Label1%$isible / .rue Lin LabelB%$isible / .rue LabelB%$isible / .rue LabelC%$isible / .rue

LabelB%.ext / 0P.- .1e Fee installment o, t1e next semester 1as to be paid be,ore _t1e start o, exam o, previous semester as per t1e dates _communicated b# t1e -niversit#%.1e ,irst installment 1as to be paid at t1e time o, Admission%(xamination,ee o, ;sJJ>K per semester 1as to be paid to t1e learning center separetel# at t1e time o, admissionIreadmission%0 LabelC%.ext / 0.1e semester ,ee as pere scribed in t1e prospectus 1as to be paid b# t1e student O4LE in s1ape o, a demanddra,t in t1e name o, ;(3+S.;A;'P-4DA" .(C*4+CAL -4+$(;S+.E'pa#able at t1e DALA4D*A; and t1e exam ,ee o, ;sJJ>KG can be paid b# cas1 at t1e learning center%0 Lin Label1%.ext / 0+nstructions For Pa#ment0 Lin LabelB%.ext / 02ode O, Pa#ment0 (nd +, (nd Sub Private Sub LabelB_Clic !"#$al sender As S#stem%Ob&ect' "#$al e As S#stem%(ventArgs) *andles LabelB%Clic (nd Sub Private Sub Lin Label1_Lin Clic ed!"#$al sender As S#stem%Ob&ect' "#$al e As S#stem%5indows%Forms%Lin LabelLin Clic ed(ventArgs) *andles Lin Label1%Lin Clic ed (nd Sub

METHODO"OGY USED 3OR TESTING

"ys em Tes #lan Introduction

This document describes the user acceptance test plan for the I*#TIT+T0 !"*"'0!0*T #ystem. The complete test strategy for the I*#TIT+T0 !"*"'0!0*T #ystem is to perform the following kinds of tests, in se@uenceE 1. o*ponent te(t#n) of each component that makes up the I*#TIT+T0 !"*"'0!0*T #ystem 2. Inte)r%t#on te(t#n) of the I*#TIT+T0 !"*"'0!0*T #ystem, to ensure the correct interworking of its components 5. V%+#'%t#on te(t#n) of the I*#TIT+T0 !"*"'0!0*T #ystem, to ensure that it works correctly in a pseudo live environment 6. U(er %ccept%nce te(t#n) of the I*#TIT+T0 !"*"'0!0*T #ystem, to ensure that its function is acceptable to its users "cceptance testing is the last set of tests to be performed before the application goes officially live.

Te(t Scope
The scope of the user acceptance testing coversE Bersion 1 of I*#TIT+T0 !"*"'0!0*T #ystem +ser facing functionality defined by a set of use cases "dministrator facing functionality defined by a set of use cases

The aim of the testing is to determine how well the application meets its functional re@uirements from the perspective of the user, and to identify any issues so they can be resolved. "lso, the testing serves to compile a set of test data and results that can be used during subse@uent test cycles, to test for non regression of the software in later releases or after the application is in maintenance. Working practices might vary from user to user and are considered outside the scope of the testing.

Te(t Str%te)4
The basis of user acceptance testing is that other tests were completed successfully, so the application and its re@uired infrastructure are considered to be stable and reliable. "cceptance testing concentrates on the application from the user$s perspective, that is, how the application is used and whether it meets the necessary @uality criteria. &hange re@uests will be sent to the development team as the actionable documentation. &hange criteria will be determined by the Test team and the .evelopment team prior to the beginning of testing. /or instance, criteria may include impact to desired functionality% amount of code impacted &y proposed change% and design re(uired &y proposed change. The tester will evaluate the criteria. The test lead will determine &hange -e@uired or not. ,nce a bug has been determined as &hange -e@uired, the bug report will be translated into a &hange -e@uest and passed on to development. The customer of the acceptance testing is the #ystem +sers, #upervisor and "dminstratorfor 0%illing and Invoice #ystem. The progress of the acceptance testing will be reported to the customer, together with any issues that are discovered and their planned resolutions. #ign off of the tests, and therefore the acceptance of the application, will be performed by the customer or a selected representative.

(reconditions
The following items are re@uired before testing can take placeE " complete and coherent functional specification of the I*#TIT+T0 !"*"'0!0*T #ystem expressed as use cases and usage scenarios " complete and validation tested release of the I*#TIT+T0 !"*"'0!0*T #ystem, delivered according to the delivery plan "n agreed upon procedure for dealing with any anomalies that are discovered during the testing process " set of test specifications describing how each functional area of the I*#TIT+T0 !"*"'0!0*T #ystem is to be acceptance tested "n implemented test environment for the testing #ufficient, suitable resources to carry out the testing "vailable standards for the acceptance testing

Test (riorities
.uring testing of the I*#TIT+T0 !"*"'0!0*T #ystem, the following @ualities will be tested in order of priorityE /unctionalityFwhether the re@uired functions are available and working as expected +sabilityFhow user friendly and intuitive the 0%illing and Invoice #ystem is #ecurityFhow well protected and guaranteed corporate and user data is (erformanceFwhether the response times are within acceptable limits &ustomi>ationFhow straightforward it is to use the application in new, unpredicted ways

+#0-9 ,(0-"TI,*"C !"*+"C #0&+-IT) "#(0&T#

INTRODUCTION Software is said to be secure if it can function properly despite of malicious attacks [3] . The security can not be bolted on the software by just spraying some security features on the later phases of software development life cycle, instead it must be the result of continuous effort throughout software development life cycle [ ]. !nly penetration testing ["] or penetrate and patch are not sufficient enough for the purpose of security. #s the malicious users do not create security holes in the system on their own, they just e$ploit the vulnerabilities already present in the system [%]. This means the e$istence of vulnerabilities in the software reflects that the software can be compromised at any point of time. The more vulnerability a software has the more attack prone it is. The presence of vulnerabilities was there in the root of many software failure reported to &'(T [%]. #n e$haustive review of the literature reveals that researchers and practitioners have made an e$tensive effort to minimi)e the effects of vulnerabilities*security releated flaws in the software under development. These efforts are applied in the software developement and are proven to be beneficial, but because of their adhoc application, they are not so popular. # security process proposed by +avid ,yres and -ahid Shahmehri is a continuous process and works at each phase of software development life cycle. Section of this paper briefly describes +avid.s security process. /n section 3, the bright side of the process is e$plored, whereas section 0 describes limitations of the process under study. Section 1 presents some suggestions in order to improve the process and a pictorial representation of the improved security process has been depicted and e$plained. II. THE SECURITY PROCESS # process for software security based on vulnerability cause graph has been proposed by +avid ,yres and -ahid Shahmehri. They developed adaptive formalism for modeling the causes of software vulnerabilities. Their aim is to evolve the software development process so that vulnerabilities are

prevented. The proposed process is fle$ible, straightforward and well adapted to the needs of most businesses. The process, shown in figure %, consists of mainly three steps including vulnerability modeling, vulnerability cause mitigation, and process component definition. These phases are described in the following section. Vulnerability Modeling #nalyses the vulnerability deeply and determines the direct and indirect causes to produce a structure called 2ulnerability &ause 3raph 42&35 [ , 0]. #n independent analyst validates vulnerability model at last. Vulnerability causes mitigation # security activity graph 4S#35 is generated for each of the vulnerability which shows how the activities in the software life cycle combine to prevent a cause or vulnerability. Process Component Definition #ctivities are selected from a set of security activity graph in order to prevent software vulnerabilities. The selection criterion depends upon development process, product and organi)ation. III. THE BRIGHT SIDE /t is an inevitable facts that various efforts have been made in order to get a security process for the development of software [3, 6, %7, %%, % ], but these are based on best practices and e$perience [ ]. -o doubt, these approaches are successful to some e$tent as they minimi)e the effect of the vulnerabilities but generally, these are infle$ible and provide little support for evolution. !n the other hand, the security process under review is integrated in software development life cycle and can be called in each phase of software development life cycle whenever vulnerability is found. The key benefits of the security process proposed by +avid ,yres and -ahid Shahmehriincludesthefollowings8

The process is fle$ible in nature and can be used in conjunction with any software development process. To encourage reuse, all information that is collected or generated during the process is stored in a shared repository called 2ulnerability #nalysis +atabase 42#+5 The process addresses the common de motivating factors across practitioners groups like cumbersome process, inertia, time

pressure, lack of resources, lack of evidence and imposition given by 9all and ,addooo [1]. The process is iterativein nature: it can be called any time in software life cycle so it reacts continuously to the new threats and vulnerability. The process support for evolution of the softwar

9aving the above benefits, the security process may be e$pected to be more successful and adaptive practically because of its nature of being independent of the development process.

IV. THE DARK SIDE #s almost everything has brighter as well as darker aspects so with this security process. +espite of having so many reasons favorable for the industrial adaptation of the process, there is a negative aspect also. Some pertinent ones are listed as follows8

The process is not diagnostic in nature i.e. it does not provide any guideline on how to detect the vulnerability. The process is only reactive in nature. /t only provides the mechanism to preventing the vulnerability known so far. The process proposed is nothing but the vaccination process. /t vaccinates for only known threats just like a doctor who neither diagnose*detect disease himself nor suggests any guideline for the detection of the disease. (ather suggests prescription for the diagnosed disease accordingly.

/t is apparent that, for already known vulnerability, the process works satisfactorily. ,ut the information about all the vulnerabilities can not be e$tracted from central repository like &'(T or some other sources as some vulnerabilities are very specific to the conte$t. Therefore, it is worthwhile to pose a ;uestion if the security process is waiting for the new vulnerability to react or mitigate, from where these vulnerabilities will come. !f course, vulnerabilities are detected either by some security personal or by some potential hackers, because these two are having interest in vulnerabilities. /f it is potential hacker*attacker who is going to detect it, the security process proposed will be very late to react on the newly discovered vulnerability. Therefore, it seems that the process does not discuss these issues, and hence there is a great demand for improvement in order to incorporate the issues described.

V. THEORETICAL BASIS There are different tools available including /TS0 [<], =law =inder [>], and (#TS [%3] for vulnerability detection. These tools are used to detect the vulnerabilities in source code, for e$ample, buffer overflows, format string problem, temporary file race condition etc in & and &?? functions. Splint [%0], and &;ual[%1] are used to perform static analysis of code to find vulnerability in code. The =@= finder [%<] assumes that those functions are likely to have security vulnerability which is near a source to input and this tool automatically detects the high risk functions, thus reduces the work for auditors. #s in many businesses non stop service is re;uired and even a single minute of stopping the software can cause much economic loss. Aeeping this in mind, Bhigiang @in has been developed a framework to dynamically immuni)ing software security vulnerabilities even when the software is running [%>]. /n /SS white paper [%"], it is shown that vulnerability driven research is far better than e$ploit driven research. #s in vulnerability driven research, addressing a particular vulnerability will keep system secure from all attacks*e$ploits which could take advantage of that vulnerability while in e$ploit driven approach each e$ploit is handled separately for a given vulnerability but since there is vulnerability any new e$ploit can be developed any time to compromise the system. The life cycle of a vulnerability is also defined [%", %6], and shown that a vulnerability during its life time may be in one of the five states namely introduce, discover, report, confirm and fi$, disclose and deploy [%6]. The -/#& has given a global vulnerability disclosure framework [ 7], which standardi)ed the comple$ issue as how, when and to whom to disclose vulnerability once it is discovered. VI. IMPROVED SECURITY PROCESS /n addition to the three phases of the security process, it is highly desirable to introduce another phase namely vulnerability detection, where a rigorous observation*analysis of each phase of software development life cycle can be done in order to detect new vulnerability. !ther than vulnerability modeling, vulnerability cause mitigation and process component definition, one responsibility of the security team should also be to detect vulnerability continuously even after the deployment so that the discovered vulnerability can be acted upon before its public disclosure. The improved security process, as shown in figure , consists of four phase including vulnerability modeling, vulnerability cause mitigation, process component definition, and vulnerability detection phase. The entire phases are same as described by +avid ,yres and -ahid Shahmehri, e$cept

2ulnerability +etection step, which is described in the following section. The process is integrated within the development life cycle so as to detect, analy)e and mitigate vulnerabilities in each phase. !bjective is to detect and fi$ vulnerability introduced in any phase of software development life cycle. This may avoid ha)ards caused by that particular vulnerability in a phase in future. The proposed security process is integrated within the life cycle model so as each phase of life cycle model is fed to the security process as an input. The security process, then after detects, analy)es and finds the way to mitigate the vulnerability, if any. The output from the security process will be sent to the corresponding phase as a feedback, and changes*modifications are made there accordingly. Vulnerability Detection !ne of the important steps of the process is to detect vulnerabilities in inputs received from each phase of software development life cycle. 2ulnerabilities may be detected either manually or by automated tools available. # few tools are available to detect the vulnerability in early phases of software development life cycle [ %]. Cethods including use*misuse cases [ ], attack trees [ 3] 4for re;uirement specification phase5, threat modeling [ 0] and attack trees [ 3] 4for architecture and design phase5 may be used while detecting vulnerabilities manually.

"**0G+-0E
9. BRIE3 BA KGROUND O3 THE ORGANISATION !HERE THE STUDENT HAS DEVE"OPED THE PROJE T !e H%2e 'e2e+ope' t.e project %t o&r In(t#t&te on+4 . T.e #n(t#t&te #( %$$#+#%te' to BARKATU""AH UNIVERSITY. T.ere %re % '#$$erent t4pe( o$ co&r(e( o$$ere'. :. DATA DI TIONARY

BIB"IOGRAPHY
!e6(#te(
httpE99www.google.com httpE99www.microsoft.com httpE99www.programmer2programmer.net httpE99www.codeproject.com httpE99www.msdn.com. httpE99www.vb125.com httpE99www.vbcode.com httpE99www.s@ltuner.com

Boo/( !astering Bisual %asic 7 H(aperbackI !astering Bisual %asic .*0T H(aperbackI %C"&= %,,= Bisual %asic %lack %ook H(aperbackI #DC %ible, 2nd 0dition H(aperbackI .atabase .evelopment in Bisual %asic

"#*#t%t#on:

1. This project is a very small project and has lots of bugs . 2. This project is not a commercial project. The logics and coding is very simple and does not include various situations and checks of Institute management. 5. The data base used is !# "ccess , the security is not good.

ON "USION
This project fulfills its entire re@uirement for which is developed. This project provided all the information that is related with an JInstitute !anagement process. It allows insertion, modification and deletion of JInstitute !anagement. %ut nothing is perfect in this world so this project. It has its own limitation. It can give you the raw information about stone but cannot give the source and JInstitute !anagement details of consumers. We have tried to make it as user friendly as possible and we have success up to certain extent.