Download Free PDF View PDF
Download Free PDF View PDF
Download Free PDF View PDF
In this scholarly thesis pertinent to the setting up of a automated student performance record management system which enables the users of a university like student and faculty to access the important information with ease through a user friendly web application. This proposed system aims at eliminating the practice of time consuming and vulnerable tradition of manual maintenance of student information in paper at the very basic level. In a university there are many departments all these departments provide various records regarding student. Most of these track records need to maintain information about the students. Thus by proposing a computerizes student record management system will enable the users to access data at any time and any place. The student web portal enables huge storage of data and easy retrieval. There are many departments in a college thus but introducing a student web portal will centralize the administration and the entire system will work as one single entity. The paper work would be reduced and number of workers in each department staff also reduces as one single operator can run this web application
Download Free PDF View PDF
This research is focused on creating an automated students result management system using oracle's database, forms and reports. This is a computerized examinations results management system for tertiary student's examination records. The manual method of students' academic result processing was found to be tedious, especially when carried out for a large number of students, this makes the entire process time-consuming and error prone. The system designed is meant to register students as soon as they have paid their departmental registration and only then will they be able to view their results. The system presents a single platform that will be used to manage the processing of all examination records within the institution. The data used for testing was obtained from the Department of Physics, Nasarawa State University and an empirical evaluation of the system shows that the system expedites the processing of students' examination results and the reporting of it. 1.0 Background. Eludire (2011) noted that the data generated by organizations are usually created in files for use by different departments/units within the organization. If the data contained in these files are not carefully delineated it is very likely that the same data will appear on several of these files. That is these files would contain redundant data for example the University registry file and college or department file would contain the name and address of a student. This would mean that a simple change of address has to be processed in two and probably three or four places, depending on the number of other files on which these data appears. This results in data redundancy. Vecchioli (1999) noted that organizing and managing student records into a cohesive and efficient system might seem like an impossible task. This study was carried out to verify the manual process involved in generating students examination result and to seek a way of automating the system for effective operations. It is pointed out in the research work Student Examination Result Processing System (2012) that the effort expended in the process of registration of students and computation of their examination results is enormous. Hence, the need to evolve a computerized process that will effectively and efficiently capture all the important data associated with the registration and examination result processing within the University. Barrett (1999) notes that in an effort to efficiently document and maintain accountability data, schools are relying more on technology in the form of Student Management Information Systems (SMIS). This system is designed to efficiently handle processes like inputting scores, storing results, automatically calculating grade points, and interpreting the student's overall result. The usual manual process has now reached a level where it is difficult for the available man power to cope with the magnitude of examination work, in the given time. The imbalance between man power availability and the magnitude of work to be done in processing examination results, leads to the delay in the declaration of examination results. An effective measure, which can improve the efficiency of the examination result processing is therefore the introduction of computerization, especially with the use of examinations result processing software. Computerized relational database systems (RDBMS) like Oracle database, Microsoft SQL server, MySQL etc. were developed with goal of reducing data redundancy. Brian (2009) stated that databases are collections of interrelated data of such a nature that the collections can be represented as a number of files but not a single file. Garcia-Molina et al. (2008) also stated that depending on the Database Management System (DBMS) used, these files may be integrated permanently into a single connected structure or integrated temporarily for each interrogation, known as a query. Nearly all departments within an organization require data to be processed into information in a timely manner. Timely information processing and dissemination leads to efficiency and customer satisfaction. Schools are organizations as well and
Download Free PDF View PDF
Download Free PDF View PDF
Database design using relational approaches consists of the following stages: describing business processes, identifying and tapping entities, completing entities with attributes, creating relationship diagrams between entities equipped with cardinality, carrying out normalization processes, making structure language queries (SQL) and translation into programming languages. Managing student data manually, for various information needs at different management lines both horizontally and vertically, will cause several problems. These problems are related to accuracy and response time. This is because each identified file is independent so that when the search for records or data is made difficult, and the accuracy of the data is not maintained due to data redundancy. This research aims to design databases, thereby increasing accuracy and response time by eliminating data redundancies. Based on the condition above, in this study, a database of student data management will be conducted .
Download Free PDF View PDF
Download Free PDF View PDF
We know that a DBMS is a collection of programs that enables users to create and maintain a database. A major purpose of a DBMS is to provide users with an abstract view of the database. This means that the system does not provide all the details of data, rather it hides the details of how data is stored and maintained. However, in order for the system to be usable, data must be retrieved efficiently. This concern leads to the design of complex data structures for the representation of data in the database. Since many database systems end users are not computer trained, the complexities are hidden from them through several levels of abstraction in order to simplify their interaction with the system. Before getting in to the details of database systems architecture, let us discuss two important terms associated with it. View: Normally, a table contains many columns and rows. Sometimes all that data interests the user, and sometimes it does not. There may be a case when only some columns or some rows of a table interest the user. To eliminate data that is not relevant to the current needs, a view is created. A view is a subset of database that an application can process. It may contain parts of one or more tables. Views are sometimes called virtual tables. To the application or the user, views behave in similar fashion as tables; however, they do not have an independent existence. Views allow the user to look at data, but they are not parts of the database. Schema: In any data model, it is important to distinguish between the description of the database and the database itself. The description of a database is called the database schema. The database schema refers to the overall structure of the database tables that store information such as user profile data, metadata or structured information. Hence, the overall logical design of the database is called as the database schema. A schema is a collection of named objects. Schemas provide a logical classification of objects in the database. A schema can contain tables, views, triggers, functions, packages, and other objects. Note that once the schema of the database is created, usually is not changed. If in case it needs to be modified, only the owner of the schema, that is, the DBA, who has access to manipulate the structure of any object in the schema, can modify it. The distinction between the logical and physical representation of data were recognized in 1978 when ANSI/SPARC (American National Standard Institute/ Standards Planning and Requirements Committee) proposed a generalized framework for database systems. According to the ANSI/SPARC DBMS report, a DBMS can be envisioned as a three-layered system: internal, conceptual, and external. 1. Internal (physical) level: this is the lowest level of abstraction and it describes how the data is physically stored and organized on the storage medium, as well as access to the data, such as through data storage in tables and the use of indexes to expedite data access. At this level, complex low-level data structures are described in detail, which deal with actual storage. The internal model separates the physical requirement of the hardware and the operating system from the data model. 2. Conceptual level: Also known as logical or community-user level, conceptual level describes what type of data is actually stored in the data base, and the relationship among the data. At this level, entire database is described in terms of small number of relatively simple structures, such as tables and constraints. Although implementation of the simple structure at the conceptual level may involve complex physical level structures, the user of the conceptual level of abstraction is the DBA, who must decide what information is to be kept in the data base. 3. External level: The external level (or application interface) is the view that the individual user of the database has. This view is often restricted view of the database and the same database may provide a number of different views for different classes of users. This level deals with the methods through which users may access the schema, such as using an input form. In general, the end users and even the application programmers are only interested in the subset of the database. To simplify their interaction with the system, the view level of abstraction is defined. Concisely, this level is concerned with the way in which the data is viewed by individual users.
Download Free PDF View PDF
American Journal of Software Engineering and Applications
