ACTIVITY MANAGEMENT SYSTEM

Submitted to Bharathiar University in partial fulfilment of the

Requirements for the award of degree of

Bachelor of Science in Computer Technology

Submitted by

R.ANANDHAKUMAR

(Reg.No: 1426K0062)

Under the Guidance of

Mrs. D.Maheshwari, M.Sc., M.Phil., (Ph.D.),

Head of the Department

Department of Computer Technology

DEPARTMENT OF COMPUTER TECHNOLOGY

DR. N.G.P ARTS AND SCIENCE COLLEGE (AUTONOMOUS)

(Affiliated to Bharathiar University and NAAC Re- Accredited by ‘A’

Grade)COIMBATORE – 641 048

MARCH-2017

1
 DECLARATION

I, R.ANANDHAKUMAR, hereby declare that this study entitled “ACTIVITY

MANAGEMENT SYSTEM” submitted to Dr.N.G.P. ARTS AND SCIENCE
COLLEGE (Autonomous), COIMBATORE in partial fulfilment of the requirements
for the award of degree of Bachelor of Science in Computer Technology is a record of
original project work, under the supervision and guidance of Mrs.D.Maheshwari,
M.Sc., M.Phil., (Ph.D.), Head of the Department, Department of Computer
Technology, Dr.N.G.P. Arts and Science College(Autonomous), Coimbatore and it has
not formed the basis for the award of any Degree/Diploma/Associate Ship or
Fellowship or other similar title to any candidate of any University.

Place : Coimbatore R.ANANDHAKUMAR

Date : (Reg. No. : 1426K0062)

2
Dr. N.G.P ARTS AND SCIENCE COLLEGE(Autonomous)

(Approved by the Government of Tamil Nadu & Affiliated to Bharathiar University,

Coimbatore)

Re-accredited by NAAC with ‘A’ Grade

(An institute of Kovai Medical Centre Research & Educational Trust)

Dr. N.G.P –Kalapatti Road, Coimbatore – 641048, Tamil Nadu, INDIA

Ph : 0422 - 2369100, 2369253 Fax : 0422 – 2369206 Web : www.drngpasc.ac.in

Reg.No : ……………………………..

Certified Project Record work submitted for the Project Viva Voce held at Dr.N.G.P
Arts and Science College (Autonomous) for evaluation on _____________.

…………………… …………………....

Prof & HOD Guide in charge

EXAMINER

External .......................

Internal .......................

3
 ACKNOWLEDGEMENT

My deep sense of gratitude and thanks to our beloved chairman Dr. Nalla G
Palaniswami M.D.A.B (USA) and Thavamani D Palaniswami, Secretary, Dr.
N.G.P. Arts and Science College, Coimbatore for giving me an opportunity to undergo
my studies in this prestigious institution.

I wish to express my profound thanks to Dr.P.R.Muthuswamy, MA., MBA, FDPM.,

(IIM.A)., PGDMM., Ph.D., Principal, Dr. N.G.P. Arts and Science College for his
permission to undertake this study in this esteemed institution.

My heartfelt thanks to Dr. K. Durairaj, M.Com, M.Phil., Ph.D., Vice Principal, Dr.
N.G.P. Arts and Science College, Coimbatore for his inspiration and having permitted
me to make use of the infrastructure of this great institution of enduring excellence.

I express my sincere thanks to my guide Mrs.D.Maheshwari, M.Sc.,

M.Phil., (Ph.D.), Head of the Department, Department of Computer Technology,

Dr. N.G.P. Arts and Science College, Coimbatore for the successful completion and
submission of my project.

I extend my sincere thanks to all the staff members of the Department of the
Computer Technology for their support and guidance.

I wish to thank my Parents and Friends for their support and encouragement
throughout my study.

Success the destiny of hard work and pain is achieved only with the help of my most
gracious and ever loving Almighty without whose blessing, nothing would come to
pass. I dedicate to Him this humble endeavour of mine.

4
 ABSTRACT

The “ACTIVITY MANAGEMENT SYSTEM” project is a desktop

application for the department of computer technology. This desktop is fully developed
by VB.NET as front end and MS SQL as back end. The aim of project is to develop the
professional user interface for desktop. This project is used to displays the activities
and achievements of computer technology department.

This project implement the concept of social embedding. Via this social
embedding, the department can connect with the students of the department. This
project is also used to maintain the details of the department faculties. It helps to known
about the department features to the user.

This project is one of the educational service. This desktop contains the softcopy
of computer technology department study materials. This project works with many
module interactions.

SCOPE OF THE PROJECT

The main scope of the project is promote the computer technology department
features, facilities, student’s achievements, staff achievements and activities. This
project contains the study materials. This is used to the students of the department. In
addition, the image and video gallery is used to show the details of the department.

5
 1. INTRODUCTION

1.1 OVERVIEW OF THE PROJECT

The title of the project is “ACTIVITY MANAGEMENT SYSTEM”. This

system used to display the activities and the achievements of the department. This
project contains more features that are advanced. This project is used to promote the
department features to other students.

“ACTIVITY MANAGEMENT SYSTEM” is very useful project for the

department of CT. Because the feature of the project is more. The image slider is used
to display the latest activities of the department. The virtual class desktop form is used
for study purpose. The desktop consist the two-navigation bar at top and middle level.

Now the most desktops are designed as flat UI interface by using the Photoshop
and the VB.Net coding. The effective use of flat user interface is looks more
professional.

This project contains two main features itself. The desktop desktop forms
embedded with the social pages. This is used to mingle with the student community. In
addition, the last main feature is virtual classroom. This is help for student study
purpose. This virtual class gives the live classroom experience for the department
students.

6
 2. SYSTEM SPECIFICATION

2.1 SOFTWARE SPECIFICATION

COMPONENTS REQUIRMENTS

OPERATING SYSTEM Windows 10

GRAPHICS Intel® HD Graphics

FRONT-END Visual Basic.NET 2010

BACK-END MS SQL Server Express

2.2 HARDWARE SPECIFICATION

COMPONENTS REQUIRMENTS

PROCESSOR Intel i3 Processor

RAM 15 MB

HARD DISK DRIVE 10 MB

2 MB
CACHE MEMORY

7
OVERVIEW OF THE FRONT – END

ABOUT VB.NET

Visual Basic .NET (VB.NET) is a multi-paradigm, high level programming language,

implemented on the .NET Framework. Microsoft launched VB.NET in 2002 as the
successor to its original Visual Basic language. Although the ".NET" portion was drop in
2005, this article uses "Visual Basic .NET" to refer to all Visual Basic languages releases
since 2002, in order to distinguish between them and the classic Visual Basic. Along with
Visual C#, it is one of the two main languages targeting the .NET framework.

Microsoft's integrated development environment (IDE) for developing in Visual Basic

.NET language is Visual Studio. Most of Visual Studio editions are commercial; the only
exceptions are Visual Studio Express and Visual Studio Community that are freeware. In
addition, .NET Framework SDK includes a freeware command-line compiler called
vbc.exe. Mono also includes a command-line VB.NET compiler.

VISUAL BASIC FEATURES

In April 2010, Microsoft released Visual Basic 2010. Microsoft had planned to use
Dynamic Language Runtime (DLR) for that release but shifted to a co-evolution strategy
between Visual Basic and sister language C# to bring both languages into closer parity with
one another. Visual Basic's innate ability to interact dynamically with CLR and COM
objects has been enhance to work with dynamic languages built on the DLR such as Iron
Python and Iron Ruby. The Visual Basic compiler was improve to infer line continuation in
a set of common contexts, in many cases removing the need for the "_" line continuation
character. In addition, existing support of inline Functions was complemented with support
for inline Subs as well as multi-line versions of both Sub and Function lambdas.

8
BACK END OVERVIEW

MS SQL SERVER

Microsoft SQL Server is a relational database management system developed by

Microsoft. A Database Server, it is a software product with the primary function of storing
and retrieving data as requested by other software applications - which may run either on
the same computer or on another computer across a network (including the Internet).

Microsoft markets at least a dozen different editions of Microsoft SQL Server, aimed
at different audiences and for workloads ranging from small single-machine applications to
large Internet-facing applications with many concurrent users.

SQL Server Express Edition is a scaled down, free edition of SQL Server, which
includes the core database engine. While there are no limitations on the number of databases
or users supported, it is limited to using one processor, 1 GB memory and 10 GB database
files (4 GB database files prior to SQL Server Express 2008 R2). It is intend as a replacement
for MSDE. Two additional editions provide a superset of features not in the original Express
Edition. The first is SQL Server Express with Tools, which includes SQL Server
Management Studio Basic. SQL Server Express with Advanced Services adds full-text
search capability and reporting services.

SQL Server Management Studio is a GUI tool included with SQL Server 2005 and later
for configuring, managing, and administering all components within Microsoft SQL Server.
The tool includes both script editors and graphical tools that work with objects and features
of the server. SQL Server Management Studio replaces Enterprise Manager as the primary
management interface for Microsoft SQL Server since SQL Server 2005. A version of SQL
Server Management Studio is also available for SQL Server Express Edition, for which it is
known as SQL Server Management Studio Express (SSMSE).

A central feature of SQL Server Management Studio is the Object Explorer, which
allows the user to browse, select, and act upon any of the objects within the server. It can be
used to visually observe and analyze query plans and optimize the database performance,
among others. SQL Server Management Studio can also be used to create a new database,
alter any existing database schema by adding or modifying tables and indexes, or analyze
performance. It includes the query windows that provide a GUI based interface to write and
execute queries.

9
 3. SYSTEM ANALYSIS
System analysis is a process of gathering and interpreting facts, diagnosing problems
and the computer to recommend improvements on the system. It is a problem solving
activity that requires intensive communication between the system users and system
developers. System analysis or study is an important phase of any system development
process.

The system is studied to the minutest detail and analyzed. The system analyst plays the
role of the interrogator and dwells deep into the working of the present system. The system
is viewed as a whole and the input to the system are identified. The outputs from the
organizations are traced to the various processes.

System analysis is concerned with becoming aware of the problem, identifying the
relevant and decisional variables, analyzing and synthesizing the various factors and
determining an optimal or at least a satisfactory solution or program of action.

3.1 EXISTING SYSTEM DESCRIPTON

After analysing, the system studies, this existing system is has some features and
drawbacks. However, this project reduced the drawbacks and add some salient features.

DISADVANTAGES OF EXISTING SYSTEM

• The existing system desktop is not designed as flat user interface.

• The existing system does not consist the double navigation bar

• Module interaction not user friendly

The social embedding is not available in existing system

• The slider is not updated in existing system

• The virtual class is main disadvantage of existing system.

10
3.2 PROPOSED SYSTEM

These drawbacks are reduced in proposed system. The proposed system is not only
for reducing the existing system. It is also used for improve the system. In this proposed
system is also contain some addition features.

ADVANTEGES OF THE PROPOSED SYSTEM

• The proposed system desktop is designed as flat user interface.

• The proposed system consists the double navigation bar
• Module interaction is very user friendly
• The social embedding is available in proposed system
• The slider is always updated in proposed system
• The virtual class is main advantage of proposed system.

11
 4. SYSTEM DESIGN AND DEVELOPMENT
4.1 INPUT DESIGN
Input design is the process of converting user-originated inputs to a desktop-based format.
Input design is one of the most expensive phases of the operation of the major problem of a
system. Input facilities the entry of data into the computer system. Input design involves the
selection of the best strategy for getting data into the computer system at the right time and
as accurately as possible. This is because the most difficult aspect of input designs in
accuracy. The use of well- defined document can encourage used to record data accurately
without omission. Input design must capture all the data that the system needs, without
introducing any errors. Input errors can be greatly reduced when inputting directly by using
appropriate forms for data capture and well-designed computer screen layout. . The input
design is the part of overall system design, which requires very careful attention. If the data
going into the system is incorrect then the processing and output will magnify the errors.

The objectives considered during input design are:

• Nature of input processing.

• Flexibility and thoroughness of validation rules.
• Handling of properties within the input documents.
• Screen design to ensure accuracy and efficiency of the input relationship with files.
Careful design of the input also involves attention to error handling, in the project;
the input design is made in various window forms with various methods.
Company detail

4.2 OUTPUT DESIGN

Output design generally refers to the results and information that are generated by the
system for many end-users; output is the main reason for developing the system and the
basis on which they evaluate the usefulness of the application. In any system, the output
design determines the input to be given to the application. Output design is very important
concept in the computerized system, without reliable output his user may feel the entire
system is unnecessary and avoids using it. The proper output design is important in any
system and facilitates effective decision-making.

12
 Output design is the process, which involves designing necessary output, which helps the
user according to their requirement. Efficient output design should improve the system
relationship with the user and helps in decision-making. Since the management for taking
decision and to draw the conclusion directly requires the reports must be simple, descriptive
and clear to the user. Option for outputs and forms are given in the system menus.

4.3 DATABASE DESIGN

A Database is an organized mechanism that has the capability of storing information

through which a user can retrieve stored information in an effective and efficient manner.
The Database design is a two level process. In the first step, user requirements are gathered
together and a database is designed which will meet these requirements as clearly as
possible. This step is called Information Level Design and it is taken independent of any
individual DBMS. In the second step, this Information level design is transferred into a
design for the specific DBMS that will be used to implement the system in question. A
database design runs parallel with the system design. The organization of the data in the
database is aimed to achieve the following two major objectives.

• DATA INTEGRITY & DATA INDEPENDENCE

DATABASE NORMALIZATION

Normalization is the process of decomposing the attributes in an application, which

results in a set of tables with very simple structure. The purpose of normalization is to make
tables as simple as possible. Normalization is carried out in this system for the following
reasons.

• To structure the data so that there is no repetition of data

• To permit simple retrieval of data in response to query and report
request.

Normalization

Normalization is a important step in database design, particularly for relational DBMS.

Normalization is the process of simplifying the relationship between data elements in a record.

13
 Through normalization a collection of data in a record structure is replaced by
successive records structure and make data simpler and more predictable and therefore more
manageable.

Normalization is carried out for the following reasons:

• To structure the data so that perfect relationship between entities can be represented.

To permit is simple retrieval of data in response query and report request.

• To reduce the need to restructure or reorganize data when new application

requirements arise.

Normalization consists of various levels as follows

First Normal Form

First Normal Form decomposes all data groups into two-dimensional records. It is
achieved when all repeating groups are removed so that a record is of the fixed length. A
relation scheme R is said to be in 1NF, if values in the domain of each attributes of the relation
are atomic.

Second Normal Form

Second Normal Form eliminates any relationship in which data elements do not fully
depend on the primary key of the record. Second Normal Form is achieved when a record is
first Normal Form and each item in the record is fully dependent on the primary key for
identification in storage or retrieval.

A relation R said to be 2NF, if it is in 1NF and if the entire nonprime attributes ate fully
functionally dependent on the relational keys. A database scheme is said to be in 2NF if all the
relations in the database are in 2NF.

14
Third Normal Form

Third Normal Form eliminates any relationship that contains transitive dependencies.

A relation R is said to be in 3NF if whenever a functional dependencies, X->A hold in

R and A is not in X, then either X is super key for R or A is prime (i.e. A is a subset is a subset
of the candidate key).

Keys

• A Super Key is set of one or more attributes whose combined value uniquely identifies
the entity in the entity set.

• A Candidates Key is the minimal super key that is a super key, which does not have
proper subset, which also a super key.

• A primary key is a candidate key that is chosen by the database designer as a principal
mean of uniquely identifying entities with an entity set

• A foreign key is a reference key that is chosen by the database designer as a reference
to other tables for an entity .

4.4 SYSTEM DEVELOPMENT

4.4.1 MODULE AND DESCRIPTION

LOGIN MODULE
The main use of module is login into the system with admin privilege. The admin have
a username and the password for login. After login, the admin can modify the system
design. Like picture adding, video embedding and more.

ACADEMIC MODULE
This academic module is used to manage the details of the about us, contact us and
other academic details in the desktop forms.

15
PLACEMENT MODULE
This placement is important module of the desktop. The student’s gets the live
updating about the placement and it is used to helps for placement preparation.

ASSOCIATION EVENTS

The department of the computer technology is started an association. This association

is used to conduct the seminars, workshop and symposium in college.

These kind of the images, computer and videos will updated in the module

STAFF DETAILS
The staff details module is manage the details of the staff. The basic staff details
of the name, age, qualification, specialization and achievements are displays in the
desktop form.

MENTOR SYSTEM
The mentor is guide of the few students. The mentor and the mentor’s student’s details
are display in the desktop forms.

EXTENSION ACTIVITIES
This is used to display the report of the department extension activities and the images
and videos gallery.

16
 5. SYSTEM TESTING AND IMPLEMENTATION

SOFTWARE TESTING STRATERGIES

Any software has to be tested with replanted strategies. To carry out the testing
in an efficient manner certain amount of strategic planning has to be done. Any testing
strategy must incorporate test planning, test case design, test execution and the resultant
data collection and evaluation.

The system “MOBILE SHOP AUTOMATION SYSTEJM” was tested with the help of
the following software testing strategies.

BLACK BOX TESTING

1. By the use of these techniques the missing functions are identified and
placed in their positions.
2. The errors in the interfaces were identified and corrected.

3. This technique was also used to identify the initialization and termination
errors and correct them.

UNIT TESTING

In Unit testing, we have to test the programs making up the system. The
software units in a system are called modules and routines that are assembled and
integrated to perform a specific function. Unit testing focuses first on the modules,
independently of one another, to locate errors.

This enables to detect errors in coding and logic that are contained within the
module. In the lines of this strategy all, the individual functions and modules were put
to the test independently. This method was applied in combination with white and
black box testing techniques to find the errors in each module.

17
INTEGRATED TESTING

Again, this software testing strategy has two different approaches namely the
top down approach in which the integration is carried out from the top-level module to
the bottom and the bottom-up approach in which the integration is carried out from
the low-level modules to the top.

The module was tested using the bottom up approach by introducing stubs for
the top level functions. This test was used to identify the errors in the interfaces, the
errors in passing the parameters between the functions and to correct them.

VALIDATION TESTING

Software validation is achieved through a series of black box test that

demonstrate conformity with requirements. Both plan and procedure are designed to
ensure that all functional required area achieved.

Using validation testing we have tested this project. The user should not leave
any input area blank and it is not allowed to enter improper data. Many validations are
needed for every file in the form like textbox validations.

SYSTEM TESTING

The software and hardware are integrated and a full range of system tests is
conducted in an attempt to uncover error at the software and hardware interface.
Before the system is released to user, testing is the sole duty of the developer to see
that the system is free from all kinds of bugs.

The main purpose of testing an information system is to find out errors and
correct them. Testing was done in two phases

1. Foreground testing
2. Background testing

18
 The Foreground testing includes the testing of all kinds of bugs that would be
visible to the user on the screen.

1. Testing for validity of inputs.

2. Testing whether the help message is displayed properly.
3. Testing for the proper flow of sequence.
4. Testing whether the system is user friendly.

The background testing includes, whether the database is updated as required.

A message such as “Record Stored Successfully” on the monitor may ensure that data
has really been updated in the required tables.

Table updating and Data Validation test.

1. Date Retrieval, Calculation and Report generation test.

2. Date and Form Security test.

IMPLEMENTATION

System Implementation is the stage of the project when the theoretical design
is tuned into working system. If the implementation system stages is not carefully
controlled and planned, it can cause chaos.

Thus, it can be considered the most critical stage in achieving a successful new
system and in giving the user a confidence that the system will work and be effective.

After the management has given the approval of the design phase, report for this
project, further the development activities are preceded.
The major activities done in this project are

1. The most important development activity is prepared to computer program

needed for the system. The system flowcharts, Input charts, Output charts
are transferred into program.

2. In each stage of preparation, the programs have been tested and errors are
corrected if any. All necessary measures are also falls into account while
testing the program.

19
3. The changeover method is the process where the existing system is to be
replaced by the new computerized system.

4. Change over plan has to be made carefully so as to minimize the problem

that may arise from human errors.

5. The activities to be performed during the changeover plan have to be

identified and the responsibilities should be assigned to individuals in the
organization.

20
 6. CONCLUSION AND FUTURE ENHANCEMENT

The project report entitled "Activity Management system" has come to its final
stage. The system has been developed with much care that it is free of errors and at the
same time, it is efficient and less time consuming. The important thing is that the system
is robust. I have tried our level best to make the site as dynamic as possible. The entire
system is documented and can be easily understood by the end users. The desktop
developed has been designed and run to satisfy the requirements and needs of the
organization as well as the end users. In addition, provision is provided for future
developments in the system. The entire system is secured. This online system will be
approve and implemented soon.

In future, the “ACTIVITY MANAGEMENT SYSTEM” displays the student’s

exam results visually. Through this desktop, E- Learning for students can be
implemented lively.

21
 BIBLIOGRAPHY

BOOKS REFERENCES

1. Adm Trachtenberg - “VB.NET Cook Book”, Orreilly & Associates Publication,

First Edition, 2003.

2. Dongosselin - “New VB.NET Program with MS SQL”, Course Technology

Publication, 2008.

3. Kevin Yank – “Build your own Database Driven Desktop using VB.NET & MS
SQL”.

4. Peter Moulding - “VB.NET Black Book”, Coriolis Group Publication, Fifth Edition,
2005.

5. Robin Nikson - “Learning VB.NET, MS SQL”, Orreilly & Associates Publication,

Third Edition, 2009.

DESKTOP REFERENCES

1. www.VB.Net.net/manual/en/tutorial.VB.Net

2. www.youtube.com

3. www.tutorialspoint.com/VB.Net/

4. www.codeacademy.com/en/tracks/VB.Net

22
 APPENDICES

A. DATA FLOW DIAGRAM

A data-flow diagram (DFD) is a graphical representation of the "flow" of data through

an computer system. DFDs can also be used for the visualization of data processing
(structured design).On a DFD, data items flow from an external data source or an internal
data store to an internal data store or an external data sink, via an internal process. The
purpose of a DFD is:

 To show the scope and boundaries of a system

 To show that the whole system has been considered
 May be used as a communications tool between a systems analyst and any person
who plays a part in the system

 To act as the starting point for redesigning a system

The representations used in order to frame a data flow diagram are:

The circle represents the process. It shows the pair of the

Process that transforms input to output.

The arrow
represents the
graphical flow into
or out of a process

The store is used to model a collection of data packets at rest.

The terminator represents external entities with system

Communication

23
 LEVEL 0 DFD LEVE 1 DFD

Login Activity
Admin Management Database

Activity
Faculty Managem Students
ent
Query quest Query Response

Query Response Query quest

Query response/request

Administrator

24
 LEVEL 2 DFD ACTIVITY FOR USER

Tutorial
Video
Student Details
Report

Job
provider
Faculty Details
Report Activity Management

Job
seeker
Registration
Details Report

Interview
Fees Details
Report

Report

B.TABLE STRUCTURE
Table design is the process of the producing a detailed data model of a database.
This logical data model contains all the needed logical and physical design choices and
physical storage parameters needed to generate a design in a data definition language, which
can then be used to create a database fully attributed data model contains detailed attributes
for each. The term database design can be used to describe many different parts of the design
of an overall database system. Principally, and most correctly, it can be thought of as the
logical design of the vase data structure used to store the data. In the relation model these

25
are the table and views. In an object database the entities and relationship map directly to
object classes and named relationships.

TABLE NAME: REGISTRATION

Primary key:User_id

COLUMN DATA SIZE CONSTRAINTS DESCRIPTION

NAMES TYPE

User_id Varchar 15 Primary Key User ID

Password Char 32 Not Null For login security

and authorization

New_Password Char 32 Not Null

Used for password
reset

Conform_Password Chat 32 Not Null

Used for password
reset

26
TABLE NAME: STUDENT
Foreign key:Dept_id

COLUMN DATA SIZE CONSTRAINTS DESCRIPTION

NAMES TYPE

Reg_no Varchar 20 Not Null Students register

number

Dept_id Varchar 20 Foreign key Link with

department table

(Dept_id)
Stud_name Varchar 25 Not Null Students name

Father_name Varchar 25 Not Null

Student’s father
name

Course Varchar 25 Not Null Course details

Batch_year Year 15 Not Null Academic year

Timing Varchar 10 Not Null Part / Full time

DOB Date 15 Not Null Date of Birth

Address Varchar 25 Not Null

Address of the
students

Email_id Char 25 Not Null

Student’s email id

Bloog_gp Char 5 Not Null Student’s Blood

Group

Identity Varchar 30 Not Null Emergency details

27
TABLE NAME: FACULTY
Primary key: Faculty_id
Foreign key: Dept_id

COLUMN DATA SIZE CONSTRAINTS DESCRIPTION

NAMES TYPE

Faculty_id Varchar 20 Primary key Faculty id number

Faculty_name Varchar 25 Not Null Faculty name

Dept_id Varchar 20 Foreign key Link with

department table

(Dept_id)
Designation Varchar 25 Not Null Faculties Posting

Specialist Varchar 20 Not Null Well – Known

Subject

DOJ Date 20 Not Null Date of joining

Timing Varchar 10 Not Null Part / Full time

Staff_Type Varchar 15 Not Null Teaching / Non –

Teaching

DOB Date 15 Not Null Date of Birth

Address Varchar 25 Not Null Address of the

students

Email_id Char 25 Not Null

Student’s email id

Bloog_gp Char 5 Not Null Student’s Blood

Group

28
TABLE NAME: FEES

Foreign Key: Roll_no

COLUMN DATA SIZE CONSTRAINTS DESCRIPTION

NAMES TYPE

Roll_no Varchar 15 Foreign Key

Roll Number of
Students

Dept_id Varchar 20 Foreign Key

Student’s
Department ID

Date Date 15 Not Null Date of Bill Paying

Fees_id Varchar 15 Not Null Fees ID

Amount Number 10 Not Null Amount of Fees

Type Varchar 10 Not Null Type of Bill Payment

29
C.SAMPLE SOURCE CODE

Public Class Form2

Private Sub Button1_Click(ByVal sender As System.Object, ByVal e As

System.EventArgs) Handles Button1.Click
Me.Hide()
Form3.Show()
End Sub

Private Sub Button2_Click(ByVal sender As System.Object, ByVal e As

System.EventArgs) Handles Button2.Click
Me.Hide()
Form4.Show()
End Sub

Private Sub Button3_Click(ByVal sender As System.Object, ByVal e As

System.EventArgs) Handles Button3.Click
Me.Hide()
Form5.Show()
End Sub

Private Sub Button4_Click(ByVal sender As System.Object, ByVal e As

System.EventArgs) Handles Button4.Click
Me.Hide()
Form6.Show()
End Sub

30
Private Sub Button5_Click(ByVal sender As System.Object, ByVal e As
System.EventArgs) Handles Button5.Click
End
End Sub
End

Public Class Form3

Private Sub ActivityBindingNavigatorSaveItem_Click(ByVal sender As

System.Object, ByVal e As System.EventArgs) Handles
ActivityBindingNavigatorSaveItem.Click
Me.Validate()
Me.ActivityBindingSource.EndEdit()
Me.TableAdapterManager.UpdateAll(Me.ActivityDataSet)

End Sub

Private Sub Form3_Load(ByVal sender As System.Object, ByVal e As

System.EventArgs) Handles MyBase.Load

'TODO: This line of code loads data into the 'ActivityDataSet.Activity' table.
You can move, or remove it, as needed.

Me.ActivityTableAdapter.Fill(Me.ActivityDataSet.Activity)

End Sub

Private Sub Button1_Click(ByVal sender As System.Object, ByVal e As

System.EventArgs) Handles Button1.Click
Me.Hide()
Form2.Show()
31
End Sub
End Class

Public Class Form4

Private Sub DepartmentBindingNavigatorSaveItem_Click(ByVal sender As

System.Object, ByVal e As System.EventArgs) Handles
DepartmentBindingNavigatorSaveItem.Click
Me.Validate()
Me.DepartmentBindingSource.EndEdit()
Me.TableAdapterManager.UpdateAll(Me.ActivityDataSet)

End Sub

Private Sub Form4_Load(ByVal sender As System.Object, ByVal e As

System.EventArgs) Handles MyBase.Load

'TODO: This line of code loads data into the 'ActivityDataSet.Department' table.
You can move, or remove it, as needed.
Me.DepartmentTableAdapter.Fill(Me.ActivityDataSet.Department)

End Sub

Private Sub Button1_Click(ByVal sender As System.Object, ByVal e As

System.EventArgs) Handles Button1.Click
Me.Hide()
Form2.Show()
End Sub
End Class

32
Public Class Form5

Private Sub HallBindingNavigatorSaveItem_Click(ByVal sender As

System.Object, ByVal e As System.EventArgs) Handles

HallBindingNavigatorSaveItem.Click
Me.Validate()
Me.HallBindingSource.EndEdit()
Me.TableAdapterManager.UpdateAll(Me.ActivityDataSet)

End Sub

Private Sub Form5_Load(ByVal sender As System.Object, ByVal e As

System.EventArgs) Handles MyBase.Load

'TODO: This line of code loads data into the 'ActivityDataSet.Hall' table. You
can move, or remove it, as needed.

Me.HallTableAdapter.Fill(Me.ActivityDataSet.Hall)

End Sub
Private Sub Button1_Click(ByVal sender As System.Object, ByVal e As
System.EventArgs) Handles Button1.Click
Me.Hide()
Form2.Show()
End Sub
End Class

33
D.SCREENSHOT

Login Page

Dashboard

34
Activity

Department

35
Hall Booking

Result

36