Table of Contents 1. Introduction2 1. 1. Purpose2 1. 2. Scope2 1. 3. Technologies to be used2 1. 4. Overview2 2. Overall Description2 2. 1. Goals of proposed system2 2. 2. Background2 2. 3. Project Requirements2 2. 4. User Characteristics2 2. 5. Hardware Requirements2 2. 5. 1. Processor RAM Disk Space2 2. 6. Software Requirements2 2. 6. 1. Operating System2 2. 6. 2. Application(s)2 2. 6) Definitions of problems2 2. 7. Alternative Solutions2 3. Feasibility Study2 3. 1. Steps in feasibility analysis2 3. 2. Technical feasibility2 3. 2. 1. Front-end and back-end selection2 3. 2. 2. Front-end selection2 3. 3. Economical feasibility2 3. 4. Operational Feasibility2 3. 5. Schedule feasibility2 4. General Information2 4. 1. Entities2 4. 2. ERD Diagram2 4. 3. Data Dictionary and Normalization2 5. Testing2 6. Conclusion2 List of Tables Table 1: Entity course2 Table 2: Entity Lecturer2 Table 3: Entity Room2 Table 4: Entity subject2 Table 5: Entity subject_timetable2 1. Introduction Purpose The project aims to make an online university timetable which provides facilities to teachers and student to check out the classes that are going on presently. The purpose of creating a database is to keep track of class schedules and location. As current work is all paper based, an approach towards automation is being made to reduce human efforts by preventing them to look for a particular class in an index. The purpose of database on the whole is to: * Maintain daily time table such as information related to class schedule. * Provide information about teacher, room number and subject being taught Scope Interface and database on a back end that are being used can provide a greater scope and opportunities for students and teachers to look for their room number rather than contacting Admin Dept. to ask for the room number. Technologies to be used Initially, our intended goal was to create web-based application but due to lack of knowledge on working ASP. NET and other related technologies, our application will be desktop based. This application will be designed on Visual Studio 2005. Following technologies are used in our project * MS Visio (For designing ERD diagram) * SQL Server 2005 (Database design and creation of database schema) * Visual Studio (for form design, interface and testing) Overview Main facilities that are associated with this project are:- • Maintaining records of Classes, Room No, Computer lab, Teacher Information. • Maintaining Notice Board for the students. Maintaining Every Section records. Overall Description Goals of proposed system * Planned approach towards working: - It is necessary that the process, for its smooth on-going, should be well organized and structured. All the data will be stored properly in data stores, which will help in retrieval of information as well as its storage. * Accuracy: - The level of accuracy in the proposed system will be higher. All operation would be done correctly and it ensures that whatever information is coming from the center is accurate. * Reliability: - The reliability of the proposed system will be high due to the above stated reasons. The reason for the increased reliability of the system is that now there would be proper storage and retrieval of information. * No Redundancy: - In the proposed system, we can assure that no Information is repeated anywhere, in storage or otherwise. On the contrary, if a proposed system is paper based, there are high chances of redundant data. * Immediate retrieval of information: - The main objective of proposed system is to provide for a quick and efficient retrieval of information. * Immediate storage of information: - In manual system, there are many problems to store the huge amount of data and handling them. Easy to Operate: - The system should be easy to operate and should be such that it can be developed within a short period of time and fit in the limited budget of the user. Background As students enter university, they look for their classes. They waste their precious time and knowledge while finding their classes. They have certain things in their mind such as “Where will be the class? ”, “Is today’s class cancelled? ”, “Is teacher available? “, etc. For that concern, students have to rely on Academic controller to provide them with their desired information. Thus, Academic controller also gets busy in solving student queries rather than performing other important tasks. Project Requirements Following are the project requirements * The DBMS should be a generic software system, independent of any database instance. * The DBMS should have a user friendly and interactive interface. * The DBMS should have features for backup and recovery of data stored in the database. * The DBMS should provide for efficient retrieval of required data elements. * The DBMS should allow for constraints enforcement like data integrity, and referential integrity. The DBMS should allow for the definition of primary keys and indexing on the basis of keys. * The DBMS should allow for the definition of dependencies between tables. * The database tables must be modifiable with ease. * The DBMS must allow for selection of the specific database instance. * The DBMS must ensure that its operations are performed within reasonable limits of time and resources. User Characteristics Every user should be: * Comfortable of working with computer. * Able to understand the proposed system properly which means that interface to be designed with respect to human computer interaction. Having ‘read only’ access so that they can at least view the data. Hardware Requirements Processor RAM Disk Space * Pentium IV or higher * 512 MB RAM or higher * 40GB Hard Disk Software Requirements Operating System * Win-98, Win-XP, Win-2003, Linux(with GUIs) Application(s) * SQL Server * MS Visio * Visual Studio 2005 2. 6) Definitions of problems Problems with conventional system * Lack of immediate retrievals The information is very difficult to retrieve like, for example, to find out about the class room, students have to inquire Academic controller to know about their class room. Lack of immediate information storage The information that is being generated, such as any extra class, takes times and efforts to be stored at right place. * Lack of prompt updating Various changes to information like Classroom change, Teacher Availability, Class Schedules. Alternative Solutions This system provides online storage/ update and retrieval facility. This system promises very less or no paper work and also helps Student and Academic Controller staff. This system is fully automated so that information can be retrieved very easily without searching for data at various places. Feasibility Study Feasibility study is a test of system proposal according to its workability, impact of the organization, ability to meet needs and effective use of the resources. It focuses on these major questions: * What resources are available for given system? * What are the likely impacts of the system on the organization? * Whether it is worth to solve the problem? Steps in feasibility analysis Steps that are involved in the feasibility analysis are: 1. Form a project team and appoint a project leader: A group of three people is formed out of which one is selected as project leader and other two as a team member. Team Leader * Rameez Xaveri Team Member(s) * Ali Asghar * Meysam Alizadeh 2. Assign each Group member a particular Task After forming a team, task was distributed among team members. Each individual is given some tasks that lead to the success of the project. Rameez Xaveri: He designed and implemented the front end for this project on MS Visual Studio 2005. Ali Asghar: He prepared the report for this project. Meysam Alizadeh: He designed the database on MS SQL Server 2005. 3. Prepare system flow charts All the system flow charts are designed on MS Visio which helped us in designing the database. 4. Determine and evaluate performance and cost effective of each proposed system 5. Weight system performance and cost data. Technical feasibility Front-end and back-end selection An important issue for the development of a project is the selection of suitable front-end and back-end. When we decided to develop the DBMS we went through an extensive study to determine the most suitable platform that suits the needs of the users. The aspects of our study included the following factors. Front-end selection 1. It must have a graphical user interface that every Non technical User can understand it easily. . Scalability and extensibility. 3. Flexibility. 4. Platform independent. 5. Easy to debug and maintain. According to the above stated features we selected Visual Studio 2005 as the front-end for developing our project. Economical feasibility Economical Feasibility means that how much it cost the organization for implementing the software. Does it fulfill the users’ needs, Does it beneficial to the university. The financial and the economic questions during the preliminary investigation are verified to estimate the following: • The cost to conduct a full system. The cost of hardware and software for the class of application being considered. • The benefits in the form of reduced cost. • This feasibility checks whether the system can be developed with the available funds. The University Time Table Management System does not require enormous amount of money to be developed. Operational Feasibility The points to be considered are: • What changes will be brought with the system? • What new skills will be required? Do the existing staff members have these skills? If not, can they be trained in due course of time? The system is operationally feasible as it is very easy for the end users to operate it. It only needs basic information about Windows platform. Schedule feasibility Time evaluation is the most important consideration in the development of project. The time schedule required for the developed of this project is very important since more development time affects machine time and causes delay in the development of other systems. A reliable University Time table Management system can be developed in the considerable amount of time. General Information Entities 1. Tb_course 2. Tb_lecturer 3. Tb_room 4. Tb_subject 5. Tb_subject_timetable ERD Diagram Data Dictionary and Normalization Column Name| Column Type| Description| Course_id| Int (primary key)| ID associated with the course| Course_name| Varchar(30)| Name of the course| Table [ 1 ]: Entity course Column Name| Column Type| Description| Lecturer_ID| Int (primary key)| ID associated with the lecturer| Lecturer_name| Varchar(35)| Name of the lecturer| Table [ 2 ]: Entity Lecturer Column Name| Column Type| Description| Room_ID| Int (primary key)| ID associated with the room| Room_number| Int| In which room class is going on| Table [ 3 ]: Entity Room Column Name| Column Type| Description| Subject_id| Int (primary key)| ID associated with the course| Subject_name| Varchar(30)| Name of the course| C_id| Int(foreign key to tb_course. course_id)| Course id for building up relationship between two tables| Lecturer_id| Int(foreign key to tb_lecturer. lecturer_id)| Lecturer id for building up relationship between two tables| Table [ 4 ]: Entity subject Column Name| Column Type| Description| ID| Int (primary key)| ID associated with the course| Subject_ID| Int(foreign key to tb_subject. ubject_id)| Subject ID for building up relationship between two tables| Room_ID| Int(foreign key to tb_room. room_id)| Room ID for building up relationship between two tables| Course_Id| Int(foreign key to tb_course. course_id)| Course ID for building up relationship between two tables| hour| Int| For how long the class will be held| Time_start| Int| At what time the class will be started| Days| Varchar(30)| On which day class will be held| Table [ 5 ]: Entity subject_timetable Testing University Timetable Data Base has been fully tested on the Windows XP / VISTA / 7 Operating System, installed on an INTEL-PC Compatible System. Performance restrictions and efficiency considerations of Timetable Data Base were affected by the performance of the Operating System on which it was deployed. Conclusion The Timetable Relational Database Management System is successfully designed, implemented, tested and deployed. It is able to efficiently store, retrieve data from database tables stored on disk files as and when requested. The University Timetable Data Base front – end Application is able to suitably format and display the retrieved database information to the user in a comprehensive manner.
Read full document← View the full, formatted essay now!