College Management System

college management system

A Project Report on

“COLLEGE MANAGEMENT SYSYEM"Submitted To

PUNJAB TECHNICAL UNIVERSITYJALANDHAR

In partial fulfillment of the requirement for the Award of degree of

“MASTERS OF SCIENCE (INFORMATION TECHNOLOGY)”

Submitted to: SUBMITTED BY: Mrs Pallavi Vyas Rajni Devi(1166605) Assistant Professor Navjot Kaur (1166603) ( Department of Computer Applications)

1


ACKNOWLEDGMENT

I am short of words to express my thankfulness to all the distinguished people who

during the course of my project work gave their unflinching support and valuable

guidance, which helped me to make my endeavor a success .The accomplishment of

this project would have not been possible individually, without the encouragement,

assistance and valuable support from various sources. Thus my whole hearted thanks

to the Almighty.

My heartfelt gratitude to Dr. Manoj Kumar Group Director CT Group of Institutes,

Jalandhar for providing various facilities needed for successful completion of our

project.

I extend my profound thanks to Mr. Sangram Singh , Head Department of

Computer Applications, for his constant encouragement and support. I also like to

thank my project guide MRS. PALLAVI VYAS , Department of Computer

Applications, without whose guidance and cooperation my project would have not

been completed. I am also very thankful to all other faculty members of computer

department for giving their full cooperation.

2


INDEX

Sr.No Contents Page No

Remarks

1. About The Project 1-42. Objectives 53. System Analysis 64. Feasibility Study 7-95. E-R Diagram 10-116 Introduction to ms-access 127. Introduction to Java 138. System design 14-169. Part-I DFD 17-1810. Part-II FORMS 19-2411. DATABASE DESIGN 25-2712. Test Plan 28-3213. Implementation 33-3414. Conclusion 35

15. Bibliography 36

3


ABOUT THE PROJECT

This project is based on College Management.College is a place where we can get educationin different courses. College is a vast source of knowledge.Education prepares us to have morality,self-purification, responsibility,boldness,knowledge,self-reliance and self –restraint.This project includes the following parts:-Forms, coding and data reports.1st form is LOGIN form which contained user name & password.2nd. form is MDI form which includes all the information about the Institute Management likeAdmission,fee record ,teacher record record.PART-I contains all the DFD’S of this project.PART-II contains all forms which are as follows:-

1.Admission Report2.Teacher ReportPART- includes the database design.

4


OBJECTIVES

The new computerized system has the basic of being efficient and user friendly .Following are the objectives of the new system :

1. To make the job less complex one.

2. To ease data management and storage information .

3. To quicken the entry process.

4. To reduce the amount of errors creeping into system.

5. Reduction of the manpower needed to do the job.

6. To make the system user friendly.

7. To provide for storing of data in a meaningful order.

8. The retrival process has to be made easy and time complex.

9. To provide a new management methodology for college managers

to improve their management skills.

10. To contribute and support the implementation in service,training

methods and practices for college managers.

11. To highlight and disseminate examples of best practices in college

management and project’s result as well.

12. To improve and enrich the syllabus.

.

13. To ensure minimum levels of learning.

14. To impart refresher training to teachers.

.

5


SYSTEM ANALYSIS

During this, the developer focuses on three tasks:-

Defining the problem and deciding whether to proceed.

Analyzing the current system in depth and developing possible solution to the

problem.

Selecting the best solution and defining its function.

Identification of needs is done in order to understand the problem the software system

is to solve. The problem could be automating an existing manual process, developing

a new automated system, or a combination of the two. For large systems that have

many features, and that need to perform many different tasks, understanding the

requirements of the system is a major task. The emphasis in requirements analysis is

on identifying what is needed from the system, not how the system will achieve its

goals. This task is complicated by the fact that there are often at least two parties

involved in software development- a client and a developer. The developer has to

develop the system to satisfy the client’s needs. The developer usually does not

understand the client’s problem domain, and the client does not understand the issues

involved in the software systems. In most software projects, the need ends with a

document describing all the requirements. In other words, the goal of the requirements

specification is to produce the software requirements specification. The person

responsible for requirements needed is often called the analyst. The knowledge

gathered regarding the current system is documented in several different ways. Some

analysts use data flow diagrams, which show the flow of data

6


FEASIBILITY STUDY

For all new systems, the requirements engineering process starts with feasibility study.

The input to the feasibility study is an outline description of the system and how it

will be used within an organization. The result of the feasibility study should be a

report which recommends whether or not it is worth carrying on with the requirements

engineering and system development process.

A feasibility study is a short, focused study which aims to answer a number or

questions:

1. Does the system contribute to the overall objectives of the organization?

2. Can the system be implemented using current technology and within cost and

schedule constraints?

3. Can the system be integrated with other systems that are already in place?

7


The Requirement Engineering Process:

Based on these requirements we have carried out a feasibility study from three

perspectives wiz. Economic, Technical and Social Feasibility. The following pages

describe these studies.

1 Economic Feasibility

One of the aims of developing the college Management System project was to

provide such an alternative to the current system, which is highly productive while

remaining economically feasible.

College management System is an economically feasible alternative to the current

system.

College management System can perform all the tasks of management at Products in

an efficient manner.

It is true that a significant amount of investment is needed to setup the automated

system. This cost includes the computer hardware and software expense. The college

management System may even require a trained person to operate the system. This

cost withstanding college management System can make up for the expense in a short

period of time.

The old system required for manual maintenance of registers.college management

System does away with the need for these registers. Thus a significant amount of

money can be saved in the form of reduced stationary cost. Thus this can give a boost

to their environment friendly image.

college management System with its fast and accurate transaction handling can

significantly improve the productivity of the School management System. The manual

8


system is prone to human errors which can cost the Items loss in terms of money and

goodwill.

Thus we can conclude that college management System is an economically feasible

alternative to the present system.

2 Technical Feasibility

With the use of the tools and resources which were available with us, it was highly

feasible to develop college management System.

We did a detailed study of the various requirement of the system and on in-depth

analysis concluded that it was possible to technically develop the project..

All the requirements of the college management System are satisfied by Manager. It is

able to efficiently mimic the present system with many added features and

productivity tools. Thus we can conclude that college management System project is

technically feasible to develop and implement.

3 Social Feasibility

For any proposed system to be successful, it has to be accepted by the people who

work on that system. A system which is readily accepted by its users as a credible and

workable environment is a successful system.

One of our very basic aims when setting out to develop this project was to gain user

acceptance. With the present system being in use for eternal time, it is difficult to

convince the Inventory Control System to leave the present system and move on to a

computerized system. This problem is not so prominent in case of new Stock being

9


setup. We have tried to add all such features to Stock manager which make it easier

form the management to migrate to Stock Manager.

One of the basic necessities was to provide a simple and attractive user interface.Stock

Manager is successful in doing so. The other aim was to make the working as simple

and straight forward as possible. Stock Manager is successful in meeting this

requirement also.

The inclusion of such features has made Stock Manager highly user friendly, thus

making it possible for the user to easily adapt with the new system. Thus we

conclude Stock Manager is a socially feasible project which can be readily accepted

by the users.

10


E-R DIAGRAM

Entity Relationship Diagrams are a major data-modeling tool and help organize the

data in the project into entities and define the relationships between the entities. This

process has proved to enable the analyst to produce a good database structure so that

the data can be stored and retrieved in a most efficient manner. An entity-relationship

(ER) diagram is a specialized graphic that illustrates the interrelationships between

entities in a database. ER diagrams often use symbols to represent three different

types of information. Boxes are commonly used to represent entities. Diamonds are

normally used to represent relationships and ovals are used to represent attributes.

BASIC ELEMENTS IN E-R MODEL

There are three basic elements in ER modeling. These are:

Entity- A data entity is anything real or abstract about which we want to

store data. Entity types fall into five classes: roles, events, locations,

tangible things or concepts. E.g. employee, payment, campus, book. Specific

examples of an entity are called instances. Entities are the principal data

object about which information is to be collected.

Relationship- A data relationship is a natural association that exists

between one or more entities. E.g. Employees process payments.

Relationships are classified in terms of degree, connectivity, cardinality and

existence.

11


Attribute- Attributes describe the properties of the entity of which they are

associated. A data attribute is a characteristic common to all or most

instances of a particular entity. An attribute or combination of attributes

that uniquely identifies one and only one instance of an entity is called a

primary key or identifier. E.g. Employee Number is a primary key for

Employee.

12


INTRODUCTION TO MICROSOFT ACCESS

MS Access is a Relational Database Management System (RDBMS) used to

store and manipulate large collection of information of any kind. Here RDBMS refers

to the organization of data in, a series of rows and columns in such a manner that any

specific piece of information available with a click of a mouse and a few key strokes.

MS Access has tools which are easy to use and provide powerful development

environment, making it an appropriate choice for novices as well as professionals.

MS ACCESS is a RDBMS(RELATIONAL DATABASE MANAGEMENT SYSTEM) which is based on Edger Ford codd’s rules. A database is RDBMS if it implements atleast 6 rules out of 12 rules explained by Edger Ford codd’s rules.

MSACCESS is a Microsoft product which came with Microsoft Office Package. You can easily create database and tables in database by using MSACCESS because it is very easy to work in it. It also provides security where username and password can be given to the database. It can be used with any kind of front end application like VISUAL BASIC SCRIPT, C#, C, C++,JAVA etc.

This article explains how to use the JDBC ODBC bridge to access an MS-Access database from Java applications. Instead of elaborating on the basics of the database, let's get down to the subject.

ODBC driver

In Java, we require a driver to be loaded at runtime to connect to any data source. The same is the case for ODBC data sources too. The driver is implemented as a class that is located and loaded at runtime. The ODBC driver for JDBC connections is named sun.java.odbc.JdbcOdbcDriver.

13


INTRODUCTION TO JAVA

Java is an object-oriented programming language with a built-in application programming interface (API) that can handle graphics and user interfaces and that can be used to create applications or applets. Because of its rich set of API's, similar to Macintosh and Windows, and its platform independence, Java can also be thought of as a platform in itself. Java also has standard libraries for doing mathematics.

Much of the syntax of Java is the same as C and C++. One major difference is that Java does not have pointers. However, the biggest difference is that you must write object oriented code in Java. Procedural pieces of code can only be embedded in objects. In the following we assume that the reader has some familiarity with a programming language. In particular, some familiarity with the syntax of C/C++ is useful.

In Java we distinguish between applications, which are programs that perform the same functions as those written in other programming languages, and applets, which are programs that can be embedded in a Web page and accessed over the Internet. Our initial focus will be on writing applications. When a program is compiled, a byte code is produced that can be read and executed by any platform that can run Java.

14


SYSTEM DESIGN

System design is the first step in moving from the problem domain to solution

domain. In other words, starting with what is needed, design takes us toward how to

satisfy the needs, the design of a system is perhaps the most critical factor affecting

the quality of software; it has major impact on the later phase, particularly Testing and

maintenance. The output of this phase is design document. The design of a system is

essentially a blueprint or a plan for a solution for the system. Here, we consider a

system to be set of components with clearly defined behavior that interacts with each

other in a fixed defined manner to produce some behavior or services for its

environment. A component of a system can considered a system, with its own

component. In a software system, a component is software module.The design process

for software systems often has two levels. At the first level the focus is on the

deciding which modules are needed for the system, the specification of these modules,

and how the modules should be interconnected? This is what is called the system

design or top-level design.

In the second level, the internal design of the modules, or how the

specification of the modules can be satisfied, is decided. This design is often called

detailed design or logic design. A design methodology is a systematic approach to

creating a design by applying of set of techniques and guidelines. Most design

methodologies focus on the system design. Most current design methodologies

essentially offer a set of guidelines that can be used by the developer to design a

15


system. These techniques are not formalized and do not reduce the design activity to

sequence of steps that can follow by the designer.

Logical design

The logical design of a system pertains to an abstract representation of the data flows,

inputs and outputs of the system. This is often conducted via modelling, which

involves a simplistic (and sometimes graphical) representation of an actual system. In

the context of systems design, modelling can undertake the following forms,

including:

* Data flow diagrams

* Entity Life Histories

Physical design

The physical design relates to the actual input and output processes of the system.

This is laid down in terms of how data is inputted into a system, how it is

verified/authenticated, how it is processed, and how it is displayed as output.

Physical design, in this context, does not refer to the tangible physical design of an information system. To use an analogy, a personal computer's physical design involves input via a keyboard, processing within the CPU, and output via a monitor, printer, etc. It would not concern the actual layout of the tangible hardware, which for a PC would be a monitor, CPU, motherboard, hard drive, modems, video/graphics cards, USB slots, etc.

16


DFD

17


Data flow diagram’s is commonly used during problem analysis. Data flow diagram’s

are quite general and are not limited to problem analysis for software requirements

specifications. They were in use long before the software engineering discipline begin.

DFD’S are very useful in understanding a system and can be effectively used in

analysis.

A DFD’S shows the flow of data through a system. It views a system as a function

that transforms the inputs into a desire outputs.

DFD Symbols:

18


Rectangle - It represents an entity.

Arrow - An arrow identify the data flow i.e. Data in motion. It is a pipeline

through which information flows.

Circle - A circle or a bubble represents a process that transforms incoming

data flow into outgoing data flow.

Open Rectangle - An Open Rectangle is a data store i.e. Data at rest or

temporary, repository of data.

19


LOGIN FORM

NAME OF FORM:-LOGIN FORM

20


PURPOSE:-

This form is used for logging in.Through this form user can perform his tasks in the

application.

21


MDI FORM

NAME OF FORM:- MDI FORM

PURPOSE:-

User can see all the forms in this form by simply selecting the form from menu bar.Menu bar consists of headings which further contain pop-up menu by which we can open forms.

22


ADMISSION FORM

NAME OF FORM:- ADMISSION FORM

PURPOSE:-

This form contains all the information which is required for admission of the student.Admin can search any student record by this form. This form stores all the basic information of a student.

23


TEACHER RECORD

NAME OF FORM:- TEACHER RECORD FORM

PURPOSE:-

All the information of teachers are stored through this form. Admin can get any information regarding any teacher by simply giving its TEACH_ID.

24


EXIT RECORD

NAME OF FORM:- EXIT RECORD FORM

PURPOSE:-

This form is used for exit.

25


ADMISSION TABLE

NAME OF TABLE:- ADMISSION

26


PURPOSE:-

This table contains all the information which is required for admission of the student.Admin can search any student record from this table. This table stores all the basic information of a student.

TEACHER TABLE

27


NAME OF TABLE:- TEACHER RECORD

PURPOSE:-

All the information of teachers are stored in this table. Admin can get any information regarding any teacher through this table.

TEST PLAN

28


A test plan documents the strategy that will be used to verify and ensure that a product or system meets its design specifications and other requirements. A test plan is usually prepared by or with significant input from Test Engineers.

Depending on the product and the responsibility of the organization to which the test plan applies, a test plan may include one or more of the following:

* Design Verification or Compliance test - to be performed during the development or approval stages of the product, typically on a small sample of units. * Manufacturing or Production test - to be performed during preparation or assembly of the product in an ongoing manner for purposes of performance verification and quality control. * Acceptance or Commissioning test - to be performed at the time of delivery or installation of the product. * Service and Repair test - to be performed as required over the service life of the product. * Regression test - to be performed on an existing operational product, to verify that existing functionality didn't get broken when other aspects of the environment are changed (e.g., upgrading the platform on which an existing application runs).

A complex system may have a high level test plan to address the overall requirements and supporting test plans to address the design details of subsystems and components.

Test plan document formats can be as varied as the products and organizations to which they apply. There are three major elements that should be described in the test plan: Test Coverage, Test Methods, and Test Responsibilities. These are also used in a formal test strategy.

Test coverage in the test plan states what requirements will be verified during what stages of the product life. Test Coverage is derived from design specifications and other requirements, such as safety standards or regulatory codes, where each requirement or specification of the design ideally will have one or more corresponding means of verification. Test coverage for different product life stages may overlap, but will not necessarily be exactly the same for all stages. For example, some requirements may be verified during Design Verification test, but not repeated during Acceptance test. Test coverage also feeds back into the design process, since the product may have to be designed to allow test access. Test methods in the test plan state how test coverage will be implemented. Test methods may be determined by standards, regulatory agencies, or contractual agreement, or may have to be created

29


new. Test methods also specify test equipment to be used in the performance of the tests and establish pass/fail criteria. Test methods used to verify hardware design requirements can range from very simple steps, such as visual inspection, to elaborate test procedures that are documented separately. This test plan is a basic guideline for future testing . It mainly focuses on two problems: What will test and how we will test.

FEATURES TO BE TESTED

1) Interface Test:Pass criteria: System should provide a GUI for end user to interface with the backend inventory control System.

2) Database Test:Pass criteria: Result of all basic and advanced operations stated below are normal.

2.1) Basic Operations: ADD/UPDATE/ Query Records in each table2.2)Advanced Operations:Start or stop the database

3) Basic Function Test3.1) Add a Customer Information

Pass criteria: The information is added in all the records are updated in the respective fields of the databases. The data entered satisfies all the specified integrity constraints.

3.2) Update Customer Information

Pass criteria: The record to be modified should be successfully retrieved and the modification in any field is updated in the database.The modification of internally generated fields is not allowed.

3.3) Search For a Customer Record

Pass criteria:The project allows the user to search for particular records Of customer based on the customer_id

30


The search result would produce list of records that match the specified search parameter.

The display shall provide a means to select one or more rows to aUser list and would display details about a selected record from search operation.

3.4) Bill Calculation

Pass criteria: This project allows the user to make appropriate bills of the customer according to the quantity of item purchased by him/her and according to the market price of the gold.

The bill details can be of the customer or it can be about the purchasing of the items by the owner from the wholesalers.

The existing system was not reliable in terms of bill calculations .Sometimes due to some human errors the sale tax of the item were not added successfully in the bill details or the wrong entries were added by the employees so I use a critical test plan which automatically gave the messages to the user about his wrong or forgotten entry

3.5) Price Updation

Pass criteria: This project allows the user to daily update the price of the item according to the supplier price from which we purchase the item .

TYPES OF TESTING:-

31


Unit testing - Testing of individual software components or modules. Typically done by the programmer and not by testers, as it requires detailed knowledge of the internal program design and code. may require developing test driver modules or test harnesses.

Incremental integration testing - Bottom up approach for testing i.e continuous testing of an application as new functionality is added; Application functionality and modules should be independent enough to test separately. done by programmers or by testers.

Integration testing - Testing of integrated modules to verify combined functionality after integration. Modules are typically code modules, individual applications, client and server applications on a network, etc. This type of testing is especially relevant to client/server and distributed systems.

Functional testing - This type of testing ignores the internal parts and focus on the output is as per requirement or not. Black-box type testing geared to functional requirements of an application.

System testing - Entire system is tested as per the requirements. Black-box type testing that is based on overall requirements specifications, covers all combined parts of a system.

IMPLEMENTATION

32


After testing of the system the candidate system is installed and implemented at the

user’s place . the old system is changed to new or modified system and user are

provided training to operate the new system. This is crucial phase of SDLC and is

known as implementation phase,

System Implementation is the third phase in the JISC infoNet lifecycle approach,

during which:

* the hardware and software system components are installed;

* the selected software is configured and tested;

* the software may be customised to meet local functional requirements;

* data mapping, cleansing and migration take place;

* reporting requirements are specified and reports produced;

* the whole system is tested before being approved, signed off and becoming a fully

operational

production system.

Types of implementation

Implementation of following three types

Fresh implementation

Implementation of a totally new computerized system by replacing old manual

system

Replacement implementation

Implementation of new computerized system by replacing old computerized system

Modified implementation

Implementation of modified computerized system by replacing old computerized

system

33


What ever may be the kind of implementation ,the implementation process has the

following two parts.

1. Conversion

2. Training of users

Conversion

Conversion is the process of changing from the old system to modified or new one .

Many different activities are needed to be performed in the conversion process

depending upon the type of implementation . during fresh implementation , all

necessary hardware is installed and manual files are converted to computer compatible

files .during replacement implementation ,

Old hardware may be replaced with new hardware and old files structure also needed

to be converted to the new one.

Training of users

Training of user is another major part of implementation . it is considered most

important part of the software development as it helps user in operation and

maintaining the system.

CONCLUSION

34


Summary Of The Project named “ COMPUTERISATION OF COLLEGE

MANAGEMENT SYSTEM include various aspects of inventory in a nutshell. Our

project include all the basic operation involved in inventory like purchase , sale , and

maintaining the stock . this software deals with the expiry report of various item also .

with this software all the tough manual task can be easily performed . at last but not

least we want to state that we had tried our levl best to make this a successful project

but due to lack of time we have put some other aspect of inventory in the future scope

so that we will continue with it.

Although the implementation stage is , in effect , the final step in the system

development process , it by no mean indicate a definite end to process

Evaluation and review of the system and its total effectiveness is to be

performed throughout the entire life of the system.

The main trait of a good system is he ability of the system to accommodate

change and to receptive to user’s need.

The system developed as a part of the project wok has a ability to be upgraded

and enhancement to meet the newer requirement of the organization that may

be arise in future

We have tried our best to include all the activities involved but somehow due due to

lack of time we have kept some aspects in future scope. These include financial

accounts system , which include all the financial details.

35


BIBLIOGRAPHY

1. Introduction to ACCESS : D.K AGGARWAAL

2. ADVANCE JAVA : EBALAGURUSWAMI

3. SIMPLIFIED APPROACH TO : PRAJAKTA MANE

ADVANCE JAVA

4.SOFTWARE ENGINEERING :PANKAJ JALOTE

5.SQLBY :KALENDELANEY

6.WEBSITES

: www.google.com

: www.collegel3.com

36

http://www.collegel3.com/

http://www.google.com/


37

College Management System

Documents

Transcript of College Management System