Download College Management System: A Java-Based Solution for Efficient Institutional Management and more Essays (high school) Computer science in PDF only on Docsity!
PREFACE
This project has been submitted in the fulfillment of the requirements for the diploma of engineering. We the team members of this project, take pleasure in presenting the detail project report that reflects our efforts in academic year 2009-10. Our project involves designing a Grid framework for executing complex applications where the process is divided into threads and accordingly the threads are executed by the executors. The outputs generated by the executors are given back to the manager which in turn gives the results to the owner. This is a dedicated in which the manager can select particular executors to run the application. Initially manager is started by connecting it to a storage application. The executors are connected to the manager by providing the required credentials. Once the executors get connected to the manager the execution of the required can be started. Additionally there is a Grid console which keeps track of the executors connected and the applications running. A record of all the operations performed by either of the logger is maintained in a log file.
ACKNOWLEDGEMENT
We have immense pleasure in presenting the report for our project entitled “College Management System”. We would like to take this opportunity to express our gratitude to a number of people who have been sources of help & encouragement during the course of this project. We are very grateful and indebted to our project guide Mr. Atul D. Mairale & our respected HOD Mr. Ashish Kulkarni for providing their enduring patience, guidance & invaluable suggestions. They were the one who never let our morale down & always supported us through our thick & thin. They were the constant source of inspiration for us & took utmost interest in our project. We would also like to thank all the staff members for their invaluable co-operation & permitting us to work in the computer lab. We are also thankful to all the students for giving us their useful advice & immense co-operation. Their support made the working of this project very pleasant. Group Members:
**1. RuchiraBhagat.
- PoojaKadam.
- Priyanka Mali.
- MonicaLandge.**
CHAPTER-
INTRODUCTION
Introduction
For accomplishing big projects , the number of developers work collectively on different modules. Their efforts when combined together gives the final outcome .However ,a member working on one module may encounter the need to understand other modules. Hence , he may feel the need of telling the concerned member to explain his module. It may be time consuming and troublesome for the concerned member to explain the entire code of the module .Therefore,there arises a need for a tool like CLASS BROWSER which gives the class diagram of the entire module(project). It is quite reliable and easy to understand.It also helps in debugging large projects. The traditional view of software development takes an algorithmic perspective. In this approach, the main building block of all software is the procedure or function. This view leads developers to focus on issues of control and the decomposition of larger algorithms into smaller ones. There is nothing inherently evil about such a point of view except that it tends to yield brittle systems. As requirements change and the system grows, systems built on algorithmic focus turn out to be very hard to maintain. The contemporary view of software development takes an object-oriented perspective.In this approach , the main building block of all software systems is the object or class.Simply put, an object is a thing, generally drawn from the vocabulary of the problem space or the solution space ; a class is a description of a set of common objects. Every object has identity, state ,and behavior.
1.1 INITIAL INVESTIGATION
the first phase of software project is to gather requirements .Gathering software requirements begins as a creative brainstorming process in which the goal is to develop an idea for a new and modules that no other software vendor has thought. New software modules ideas normally developed as a result of analyzing the project The main function of requirements gathering phase is to take an abstract idea that fills a particular needs or that solves a particular problems and create a real world project with a particular sets of objectives, timeline and team. Some of the highlights of the requirements gathering phase include: Collecting project ideas. Gathering customer requirements and proposed solution. Justifying the project. Submitting the request for proposal Getting the team in phase. Preparing the requirements documents. Collecting project ideas: coming up with project ideas can prove expansion exercise.
1.2 SELECTION OF LANGUAGE
JAVA
MYSQL
we are selects the java language for our project, because Java is a object oriented programming language. It has two lives, one as a stand-alone computer language for general-purpose programming
and the other as a supporting language for Internet programming.
Java offers the following features:
- Compiled and Interpreted.
- Platform-Independent and Portable.
- Object-Oriented.
- Robust and Secure.
- Distributed
- Architecture-Neutral.
- Familiar and Simple.
- Multithreaded and Interactive.
- High Performance.
- Dynamic and Extensible
Overview of Swing
The swing package is part of Java Foundation Classes (JFC) in the java platform. The JFC encompasses a group of features to help people build GUIs; swing provides all the components from buttons to split panes and tables. The swing package was first available as an add-on to JDK 1.1. Prior to the introduction of the swing package.the Abstract Window Toolkit (AWT) components provided all the UI components in the JDK 1.0 and 1.1 platform. Altough the JAVA 2 platform still supports the AWT components, we strongly encourage using swing components instead .You can identify swing components because their names start with J. Icons Actions Pluggable look and feel Support for assistive technology Separate data and State models
2.1 INTRODUCTION
Whenever a new system (a hardware or software) is to be introduced, there is a need to study the new system in every aspect or manner before working on it. We get the idea whether the project is adequate or not. The feasibility study on 3mejor questions:
- Does the candidate system meet the user requirement?
- Is the problem worth solving?
- The impact of the system on organization.
2.2 TECHNICAL, ECONOMICALLY & OPERATIONAL
FEASIBILITY
1. Financial feasibility: Financial feasibility refers to financial support required. It refers to finance incurred during the development of the project. 2. Technical feasibility: Technical feasibility refers to technical knowhow and auxiliary devices required. 3. Behavioral feasibility: Refers to reaction of the people towards the project. 4. Operational feasibility: Operational feasibility means is it possible to practically implement the project. While installing this software, the hardware and software requirements should be specified.
2.3 FEASIBILITY GAINEED BY OUR SYSTEM
Technical Feasibility Since our project in JAVA so we need to have a strong base in programming. A computer with JDK installed is needed.
CHAPTER-
SYSTEM ANALYSIS
3.1 INTRODUCTION
The main function of the analysis phase is to look carefully at the requested features with an eye towards the issue that each may create in the actual coding. This phase is the time during which reasonably deliverable thoughts of each team member can decide. User requirements: The following requirements are raised during the analysis of the needs of the users: Ø A Person Should be able to login to the system through the first page of the Application. Ø The Administrator can create users as per user requirement. Ø A general user will have access to see the status of particular Student id number. Ø Student (user) can use all the facilities, same as which are provided to him in the college. Ø Student can see attendance, notices, grades, report and other facilities in updated manner. Ø There will be a separate page for every student as his account in which he can get notices, attendance, grades, assignments etc. Ø Faculty can give the attendances and notices for the students. Ø The administrator verifies all these reports and generates them for users to view them. After analyzing the requirements of the task to be performed, the next step is to analyze the problem and understand its context. The first activity in the phase is studying the existing system and other is to understand the requirements and domain of the new system. Both the activities are equally important, but the first activity serves as a basis of giving the functional specifications and then successful design of the proposed system. Understanding the properties and requirements of a new system is more difficult and requires creative thinking and understanding of existing running system is also difficult, improper understanding of present system can lead diversion from solution.
CHAPTER-
APPLICATION DESIGN
4.1 FORM DESIGNING
Login Form:-
This is login form of the Software, it ask for the id and password of the user, access is given to the authorized persons only. types of logins are there Admin only. .
MDI form:
This screen acts as the home screen for this software. Through this MDI form we can access its child forms. This form gives the user further 5 options:- o Login Page :it contains LOGIN, LOG OUT,and EXIT option to exit from software. o Registration: This module is designed for registration
Form list and details
- Registration Entry Form: registration entry form can be used to enter the new entry of student.
- Student Search Form: student search form can be used by admin, for searching particular student related entering branches and year.
- Notification Form: notification form can be used to add notification related to the exams and schedule of the college. Full authority is given to the admin.
- Fees Form: this can be generated the fees report of the students.
CHAPTER-
SYSTEM DESIGN
5.1 INTRODUCTION
Purpose of College Management System for a College (CMS) Design Document is to describe the design and the architecture of CMS. The design is expressed in sufficient detail so as to enable all the developers to understand the underlying architecture of CMS. Logical architecture of JDBC driver, Server, DML , DDL , Session and Data Store are explained. CMS requires Java JRE 1.5 or higher. Since CMS is written in Java, it can run on any platform that supports the Java runtime environment 1.5 or higher. The compiled files are contained in Java Archives ( JAR’ s) and have to be defined in the CLASSPATH environment variable.
Logical View:
it provides the user with an abstract view of the overall system functionality fig: abstract view of CMS(College Management System)
