19-01-2013, 10:42 AM
ENROLLMENT MANAGEMENT SYSTEM
ENROLLMENT MANAGEMENT.docx (Size: 83.65 KB / Downloads: 28)
INTRODUCTION
Throughout history, as machine invented by extraordinary people, they attempted
to make their jobs easier. This desire to simplify lives and perform more effectively
Creates a new technology for improving lives within our society. Because needs exist,
Man developed and applied new technology to fill those needs. Technology is one of the tools
to solve those problems. Man keeps on developing new technology. These new technology leads
Changes in the way jobs are being performed, but the changes present new problems in which
can be solve by much improving technological advancement and so computers were
developed to deal with information needs and case. Today, most establishment and institution in the country are already using Modern technologies for theme to be able to serve their clients fast and efficient.
One of the most important sectors in our country is our educational institution where almost 10
Million students enrolled yearly. In line with this, it is better for a college to have a
Computerized enrolment system instead of the traditional manual system to have an
Efficient and faster enrolment operation and to use as an advantage over their counter
Part school especially schools that is located in metropolitan places. Aside from good
Quality education, good services are also one of the factors looking by a new student.
The Computerized Enrolment System was proposed in replacement of the manual process of enrollment in govt. colleges for it to have an organized flow of transaction and an ease of work. The study is concerned on how the manual enrolment performs throughout the company’s transaction. The numerous transactions that the manual system covers, such as updating and adding student records, generating the advising and assessment slips, and the like are commending the manual enrolment system to be inefficient for the needs of the System to be inefficient for the needs of the
institution. Since the study involves proper records handling, tracing the constraints and
evaluation of the manual system is essential. Thus, the proponents gathered necessary data that will help in the progress of enhancing the existing system. Nowadays computer serves as an important role in our society, most especially in colleges premise. Most colleges uses computer to help their students deal in our modern technology. But as the population of the students continue to grow, many colleges face difficulties in handling their enrolment in a manual process. And one of the solutions in this problem is to make their manual enrolment into a computerized system. The system design project, Enrolment System that will provide the needed and storing information in a faster, more convenient way by storing file of the student enrolees in a computer system that will lessen the effort of faculty staff in storing files of each student every now and then. This information here can be viewed in just a second without worrying that a single file is lost. The idea behind enrolment system is not a new concept. As student enrolees increase every year, enrollment procedure become harder to deal. This will only serve to increase the problem facing enrollment that provides more easy way in enrolling. The project focuses on the development of Computerized Enrolment System for a collage or institute.
PROPOSED SYSTEM
The current manual system has various problems and to solve those problems, a new application is developed which will be computerized and will use the MS Access software for it. This application will be less time consuming and error free. Various types of queries will be performed using MS Access and coding will be done through Visual Basic.net software. In case of new system, the data once filled by the librarian on the form will be added to the computer. As a result there will be no need to maintain the forms in proper manner.
BACK END: MS ACCESS
Microsoft Office Access, previously known as Microsoft Access, is a relational database management system from Microsoft that combines the relational Microsoft Jet Database Engine with a graphical user interface and software development tools. It is a member of the Microsoft Office suite of applications and is included in the Professional and higher versions for Windows and also sold separately. There is no version for MacOS or for Microsoft Office Mobile.
Access stores data in its own format based on the Access Jet Database Engine. It can also import or link directly to data stored in other Access databases, Excel, SharePoint lists, text, XML, Outlook, HTML, dBase, Paradox, Lotus 1-2-3, or any ODBC-compliant data container including Microsoft SQL Server, Oracle, MySQL and PostgreSQL. Software developers and data architects can use it to develop application software and non-programmer "power users" can use it to build simple applications. It supports some object-oriented techniques but falls short of being a fully object-oriented development tool.
Characteristics of a Relational DBMS Model
• The relational database management model eliminates all parent-child relationships and instead represents all data in the database as simple row/column tables of data values.
• A relation is similar to a table with row/column similar to its data values. The rows of a table are referred to as
• Tuples and the columns are referred as Attributes
• Several tuples of equal length placed one below the other create a table.
• Each table is an independent entity and there is no physical relationship between tables.
• Most data management system based on the relational model has a built-in support for query language like ANSI SQL or QBE (Query by Example).These queries are simple English constructs that allow adhoc data manipulation from a table.
• Relational model of data management is based on set theory. Built-in query language is designed in the RDBMS, so that it can manipulate sets of data (one or more tuples). The user interface used with relational models is non-procedural because only what needs to be done is specified and not how it has to be done.
• In a RDBMS, all user requests to insert, Update or Delete in a table must be routed through the RDBMS engine only. Direct calls for data cannot be made to the tables themselves.
• If the RDBMS engine is not loaded and running in a computer memory, user security and request for a table data are simply not entertained.
OBJECTIVE & SCOPE OF WORK
Enrollment management, as a concept and process, remains relatively new to higher education. Developed initially within private institutions, the enrollment management concept soon spread to public institutions and gained popularity among two-year colleges. The development of enrollment management occurred in response to widespread focus on increasing new student enrolments. Concern for larger and more profitable enrolments in private colleges served as the impetus to develop an operational unit that would increase the integration, efficiency, and effectiveness of key operations; improve tactics and strategies
of those areas to strengthen articulation with prospective students; and following enrollment, enhance the retention of those new students. These new directions became the springboard for new thinking and organizational change that would build enrollment demand and provide more focus on the
Students’ collegiate experience.
Vertical Partitioning Algorithms for Database Design
Vertical partitioning is applied in three contexts: a database stored on devices of a single type, database stored in different memory levels, and a distributed database. In a two-level memory hierarchy, most transactions should be processed using the fragments in primary memory. In distributed databases, fragment allocation should maximize the amount of local transaction processing. Partitioning in database design is the process of assigning a logical object(relation) from the logical schema of the database to several physical objects(files) in a stored database. Vertical partitioning subdivides attributes into groups and assigns each group to a physical object. Horizontal partitioning subdivides object instances (tuples) into groups, all having the same attributes of the original object. We refer to the physical objects that are a result of vertical or horizontal partitioning as horizontal or vertical fragments.
A binary vertical partitioning (BVP) generates two fragments. A BVP is said to be no overlapping if the intersection of the two fragments is empty, otherwise it is said to be overlapping.
The following is a general statement of the vertical partitioning problem (VPP): Database and Transaction Specification. A database consisting of a set of objects is given in terms of a schema definition. Each object has a set of attributes with given lengths. A set of transactions is defined a priori for the database; our assumption of knowing important transactions a priori is consistent with the common practice of distributed applications and with the notion of precompiled transactions of the R* Distributed Database System [24], or of transaction classes in SDD-1 [ 191. The transaction specification relevant to the vertical partitioning of an object consists of the following information:
(i) The frequency (per unit time period) of occurrence of the transaction; when the same transaction can be issued at multiple sites in a distributed database, the frequency at each site is specified;
(ii) The subset of the attributes used for retrieval or update by the transaction;
(iii) The total number of instances of the object selected on the average by one
Occurrence of the transaction. This information is typically available after the “logical design” phase of the overall database design activity.
PRELIMINARY INVESTIGATION
At this Stage we had to perceive the problem and opportunities. We went to the hospital to review existing system. We had to find out initially what are the hospital activities and problem have been, and whether those could be resolved through available techniques known to me. Then we established the scope, preliminary requirement and constraints of the proposed system and project schedule. We found out that, such proposed system would be possible to make within given scope and it might be a feasible solution for the hospital.
SYSTEM ANALYSIS
At this stage of System Development Process we studied the existing system and tried to find out the requirements of the proposed system in details. we found out what is the purpose of the hospital department's activity, what are the steps performed in hospital department, how, where, how long and how often are they performed, how great the volume of transaction, who use the resulting information, what are the constraints, what is the input of each process and what are the outputs. We found out whether the proposed system would be feasible or not, what will be user requirements, record requirements.
SYSTEM DESIGN
After finishing the analysis part, started the designing phase of System Development Process. In this part I used both logical and physical design. For logical design - we used process modeling by DFD (Data Flow Diagram) and data modeling by ER-D (Entity¬-Relationship Diagram).
Here I tried to implement my findings, which I got in System Analysis phase by DFD and ER-D. How the system would work and how the output will be given was the main concern at this level. In logical design part-for the-we used MS Access for the database design and for front-end design, I used visual basic.net
CODING
Coding is the heart of software development. After the designing phase, we got up to coding. For Development of my project we chose MS Access, as it is very much suitable for building database applications quickly and effectively.
TESTING
After the development of the software had been finished, it went for testing. There are two types of testing- White Box and Black Box testing. I had done only Black Box testing for my software. After testing we found a test report and later on, we fixed those errors according to report. Some new requirements were imposed and enhancement request was made. The development process was stopped after testing.