1. Title of the Project.

College Administrative Active Website

Introduction This project is online website to manage all the activities of

the college. It provide very good interface between college administration with students. On implementing this project students can get all the information they want easily. This project can make the tedious & mistake-prone job easier and faster. It can be used both in top-level and bottom-level management for daily operation. All the facilities for retrieving like student information, teachers information, library management, courses and fees management will be added, deleted, updated and saved in the project i.e. when a new student want admission all the information regarding the admission will be provided online. So he will get all the information related course, fees, ,teachers or non teaching staff information ,library etc. The application will be scalable and easily maintained. It could be easily changeable to the changing needs of users. The site is also implanted with the face recognition to logon to the site. With this student can login easily. The same also can be implemented for attendance, so there is no need of taking the attendance by the lecturer.

2. Introduction and Objectives of the Project.

DRAWBACKS OF EXISTING SYSTEM STUDY

Existing System study reveals that all the booking was done manually on registers, which was very tedious and error prone job. Searching and report generation was also not possible in the existing system. Also the work of Institute was manually maintained. There was register or file system in the Institute. Present mode of working is based on manual system in which the all the information is first received and than entered in the register. It is very difficult job and time consuming also. Moreover, the existing system is also dependent on employees, if the employees are absent; it leads to problem and affects the business performance. Due to large volume of data, a lot of complexities are involved in maintaining, updating and retrieving selected information. Since old system is totally maintained manually, some of the complexities involved in existing system are as follows:1. Redundancy of data: - Due to improper maintenance of data, inconsistency is there which leads to problem like duplication of data. 2. Difficulty in updating the data:- Problem of updating data in the existing system since everything is stored in registers and files. It is very difficult and time consuming to update data. 3. Non-centralized data:- In the existing system, data records are kept under file maintenance system, due to this system the placement of the data

is not at one particular place. This results in more confusion and more consumption of time for the proper maintenance of records. 4. Delay in retrieving information: - Retrieving information is quite timeconsuming process because of large volume of data, if it is required to locate a particular record a large number of registers have to be scanned. 5. Problem for keeping the data: -As the data is voluminous, more space is required to store it. Also everything is stored on papers. This type of storage is more prone to damage with time and due to other accidental factors. 6. No integration or relation between the data: - Present system does not support any type of data integrity. 7. Not proper retrieval of information: - It is very difficult to get data information in the existing system if any information is required for any specific purpose.

PROPOSED SYSTEM STUDY

The new system will automate the whole working of institute. In this project we will retrieve the information of student or update the information easily by the use of computer. If any new student come into the institute for admission all the information regarding the student and in which course he / she wants to take admission or what the roll no given to the student all the information is stored into the database .we can easily retrieved , changed , updated or saved the information whenever we want. Information regarding the teachers or non teaching staff are also in this project .Here we will manage the library also that is how many books are in the library and information of all the issued books from the library. Fine of the student is also calculated by the use of computer from the attendance chart. Managing the funds of students by monthly basis or semester basis. Proposed System is built with technique i.e. ASP.net with SQL Server. Proposed system is very fast, easily and efficient system. The proposed system is also less dependent on employees. It works without any help of employees. The whole software is automatic. The entire software is full of photographs of all topics categorized under different groups.

OBJECTIVE OF NEW SYSTEM

The objective is to design a system that can integrate all the above features in a single system, so that it can be easy to use .The new system should have all the records and files of the old system in a comprehensively linked manner so that whenever we want to retrieve some information, it can be done in an efficient manner. The system should be a one-step shop solution where all the different jobs regarding the various operations and functions in the centers can be done on a single window with least hassle. That is, the new system should be able to do work in the least amount of time and with much more efficiency and effectiveness than the existing system. The designing aspects of new system should be aimed towards basing all the data fields and data records in a single database, from where any operation on the data or data retrieval can be done easily. It should be designed in such a way that only the required information is displayed when asked for. Not like the manual system where one has to search in hard copy files to look for a particular record. It should remove, if not all majority of the problems that exists in the old system. Also it should be compatible, easy to understand and easy to modify. The aim would be to remove as many problems as possible from the existing system and design the new system in such a manner that it looks a very comprehensive approach to the stated objectives. The organization structure of the old system should be clearly understood so that the objectives it aims to achieve can be designed. There should be complete interaction between the various sub-systems of the main system so that there can be efficient functioning of the system.

Every component of the system should be able to interact with other components through a common interface. There should be such an interaction interface, that if one component wants the output from other subsystem then it can do so freely and without hindrance. Also all sub-systems should be interdependent on each other and also independent, it means that whenever some sub-system wants some information from other sub-system, it can do so without any problem, also when a system functions independently then it does not have to wait for data to be processed. All the sub-systems should be performing the designed operations on the given data in a comprehensive manner so that all of them are aimed towards achieving a common goal. The main objectives of the new system are mentioned below:1. Fast and Efficient: - As compared to existing system, in new system the user can get the information fast, easily and efficiently from the software. 2. Reliable and accurate: -As in new system, the information is stored and processed in computers so that data will be more reliable and accurate. 3. Centralized Data:-In the existing system, data records are kept under file maintenance system due to this system the placement of the data is not at one particular place. But in new system, each and every record is maintained on computer, which leads to the centralization of data. 4. Non Redundant Information: - As in proposed system data is maintained on the computers so inconsistency does not occur which will never lead to problem like duplication of data. 5. Easy to Access: -As compared to existing system, in new system the users can easily and efficiently accesses the information from the computer.

6. No Documentation: -As everything is stored on the computer, so there is no need of documentation or maintaining the files.

3. Project Category

Web Application

This is online site, works globally. So student and lecturers can access the web wherever they are.

4. Tools / Platform, Hardware and Software Requirement specifications.

Hardware and Software requirement

Hardware Requirement Processor RAM Harddisk Monitor Keyboard Mouse : : : : : : Intel Core Duo 2.0 GHz or more 1 GB or More 80GB or more 15 CRT, or LCD monitor Normal or Multimedia Compatible mouse

Software Requirement Front End : Visual Web Developer 2008 With Sql Server Compact Edition Language Back End Operation System Browser : : : : Visual Basic or C# MS Sql Server Windows XP with server pack 3 Or Windows 7 Internet Explorer or Google Crome

6. A complete structure which includes

Functional Description
The problem under study is being divided into several modules/functions discussed below to understand the approach to the solution in the broader way:

This Project have major three modules

1. 2. 3.

Admin Module Staff Module Student Module

System architecture description

Document Outline

Here is the outline of the proposed template for software design pacifications. Please note that many parts of the document may be extracted automatically from other sources and/or may be contained in other, smaller documents. What follows is just one suggested outline format to use when attempting to present the architecture and design of the entire system as one single document. This by no means implies that it literally is a single document (that would not be my personal preference):

Major Screens

1.

Admin Module
i. Main Page ii. Login Page iii. Main page with links iv. Course Details Form v. Fee Structure Form vi. Student List vii. Fee List viii. Staff List ix. FAQ

2.

Staff Module
i. Registration Page ii. Login Page iii. Main page with links iv. View Student List v. Attendance Entry vi. Test Marks Entry vii. FAQ

3.

Student Module
i. Registration Page ii. Login Page iii. Main page with links iv. View Classes Form v. Fee Payment vi. View Test Marks vii. FAQ

SYSTEM ANALYSIS

System

Analysis

is

an

activity

that

feeds

information

to

the

specification activity. It is essential that during analysis a complete and consistent set of specifications emerge for the system. For achieving this, the first major problem is to obtain the necessary information. The second problem of analysis is to organize the information obtained so the information can be effectively evaluated for completeness and consistent. The third problem is resolving the contradictions that may exist in the information from different parties. Lastly the fourth problem is avoiding internal design. The proposed system is developed keeping in mind all these steps and is designed in such a manner that it satisfies all the requirements to be called a good system design. The database designed follows 3 rd level normalization and the input output forms show a better match with the backend. Thus solves the problem of collecting information and storing it. The collected information is logically related and stored in the database following the database rules that form the data dictionary for the various database operations. Which is removes all the possible contradictions that may arrive and results in proper functioning of the data repository. Thus having proper functioning of the modules which integrate together to work to their best.

Analysis
Introduction : In this section we covering context diagram, data flow diagram explanation, and functional decomposition diagram.

Context Diagram
A System Context Diagram (SCD) in software engineering and systems engineering is a diagram that represents the actors outside a system that could interact with that system. This diagram is the highest level view of a system. It is similar to a Block diagram. SCDs show a system, often software-based, as a whole and its inputs and outputs from/to external factors. System Context Diagrams are diagrams used in systems design to represent the more important external factors that interact with the system at hand. This type of diagram according to Kossiakoff (2003) usually "pictures the system at the center, with no details of its interior structure, surrounded by all its interacting systems, environment and activities. The objective of a system context diagram is to focus attention on external factors and events that should be considered in developing a complete set of system requirements and constraints". System context diagrams are related to UML, and show the interactions between a system and other actors with which the system is designed to interface. System context diagrams can be helpful in understanding the context which the system will be part of. Context diagrams are used early in a project to get agreement on the scope under investigation. Context diagrams are typically included in a requirements document. These diagrams must be read by all project

stakeholders and thus should be written in plain language, so the stakeholders can understand items within the document. College Mng Context Diagram

Data Flow Diagram

A Dataflow Diagram also known as Bubble Chart is used to clarify System requirements and identifying major transformations that all become programs in System Design

SYMBOLS

Data Source/Destination

Process

Data Storage

Flow of data

Level 0 Data flow Diagram

Level 1 Data flow Diagram

Level 1 Data flow Diagram

Entity Relationship Diagram

In software engineering, an entity-relationship model (ERM) is an abstract and conceptual representation of data. Entity-relationship modeling is a database modeling method, used to produce a type of conceptual schema or semantic data model of a system, often a relational database, and its requirements in a top-down fashion. Diagrams created by this process are called entity-relationship diagrams, ER diagrams, or ERDs. Data flow diagrams can be used to provide a clear representation of any business function. The technique starts with an overall picture of the business and continues by analyzing each of the functional areas of interest. This analysis can be carried out to precisely the level of detail required. The technique exploits a method called top-down expansion to conduct the analysis in a targeted way. The result is a series of diagrams that represent the business activities in a way that is clear and easy to communicate. A business model comprises one or more data flow diagrams (also known as business process diagrams). Initially a context diagram is drawn, which is a simple representation of the entire system under investigation. This is followed by a level 1 diagram; which provides an overview of the major functional areas of the business.

ER Diagram Symbols

ENTITY

RELATIONSHIP

KET ATTRIBUTE

ATTRIBUTE

College Mng ER Diagram

Future Development
At this stage of time when the whole world is running after advanced technology in every aspect of life and to comfort mans life these small electronic machines like computers have become as indispensable part of our lives. The project broadband services covers various information required by user. In future we hope that this demonstration model can be further improved so that it will define more things about broadband services so the users are further benefited. We can also implement forum to discuss, discussion between technical staff of the college and the students. We can also implement online payment system, through which people can make their payments.

CONCLUSION
Computer is the magic word of todays world. The object of College Administrative Active Website is to harness the power of the computer for our practical and potential need. This report expected to extensively cover this concept and plant a seed of inquisitiveness in the minds of the users.

We are thankful to all the people who have given us their hearty support in this endeavor, we again thank out college for providing us all the facilities and thanks to our beloved Coordinator Mr. G. Somashekar and to our guide

Flowcharting symbols and conventions On a system flowchart, each component is represented by a symbol that visually suggests its function. The symbols are linked by flowlines. A given flow line might represent a data flow, a control flow, and/or a hardware interface. By convention, the direction of flow is from the top left to the bottom right, and arrowheads must be used when that convention is not followed. Arrowheads are recommended even when the convention is followed because they help to clarify the documentation.

College Management System Flow Chart