18-10-2012, 02:18 PM
i want details and documentation about the topic time table generator
18-10-2012, 02:18 PM
i want details and documentation about the topic time table generator
07-11-2012, 11:08 AM
Time Table Management System.
1Time Table Management.pdf (Size: 862.77 KB / Downloads: 216) INTRODUCTION Technology makes lifestyle easier by providing better support to different systems, better accuracy, better security options, easier maintenance, etc. Now a day’s technology eventually means “computers” which is the greatest achievements of last century. Day by day computers are being more and more popular because of its features like ease of work, ease of learning, greater accuracy with the least time consumption and the last but not the least i.e. ease of maintenance with cost effectiveness. So as a part of these ongoing evolutionary approach traditional systems are being computerized to make them more fruitful than ever. ABSTRACT Time Table Management system is an automated system which genets time table according to the data given by the user. The main requirement of the application is to provide the details about the branch, subjects, no. of labs, total no. of period and details about the lab assistance. Then the application generates the time table according to your need. PROJECT DEFINITION The basic project is to create a Time Table Management System. To create Databases of different entities involved in this process. Maintaining database-containing information about the various semesters, subjects, Labs, teachers etc. Overview of Swing: Swing is a widget toolkit for Java. It is part of Sun Microsystems' Java Foundation Classes (JFC) — an API for providing a graphical user interface (GUI) for Java programs. Swing was developed to provide a more sophisticated set of GUI components than the earlier Abstract Window Toolkit. Swing provides a native look and feel that emulates the look and feel of several platforms, and also supports a pluggable look and feel that allows applications to have a look and feel unrelated to the underlying platform. Architecture Swing is a platform-independent, Model-View-Controller GUI framework for Java. It follows a single-threaded programming model, and possesses the following traits: · Platform independence: Swing is platform independent both in terms of its expression (Java) and its implementation (non-native universal rendering of widgets). · Extensibility: Swing is a highly partitioned architecture, which allows for the "plugging" of various custom implementations of specified framework interfaces: Users can provide their own custom implementation(s) of these components to override the default implementations. In general, Swing users can extend the framework by extending existing (framework) classes and/or providing alternative implementations of core components. · Component-Oriented: Swing is a component-based framework. The distinction between objects and components is a fairly subtle point: concisely, a component is a well-behaved object with a known/specified characteristic pattern of behaviour. Swing objects asynchronously fire events, have "bound" properties, and respond to a well-known set of commands (specific to the component.) Specifically, Swing components are Java Beans components, compliant with the Java Beans Component Architecture specifications. Look and feel Swing allows one to specialize the look and feel of widgets, by modifying the default (via runtime parameters), deriving from an existing one, by creating one from scratch, or, beginning with J2SE 5.0, by using the skinnable synth Look and Feel (see Synth Look and Feel), which is configured with an XML property file. The look and feel can be changed at runtime, and early demonstrations of Swing frequently provided a way to do this. Relationship to AWT Since early versions of Java, a portion of the Abstract Window Toolkit (AWT) has provided platform-independent APIs for user interface components. In AWT, each component is rendered and controlled by a native peer component specific to the underlying windowing system. By contrast, Swing components are often described as lightweight because they do not require allocation of native resources in the operating system's windowing toolkit. The AWT components are referred to as heavyweight components. Much of the Swing API is generally a complementary extension of the AWT rather than a direct replacement. Relationship to SWT The Standard Widget Toolkit (SWT) is a competing toolkit originally developed by IBM and now maintained by the Eclipse Foundation. SWT's implementation has more in common with the heavyweight components of AWT. This confers benefits such as more accurate fidelity with the underlying native windowing toolkit, at the cost of an increased exposure to the native platform in the programming model. The advent of SWT has given rise to a great deal of division among Java desktop developers, with many strongly favoring either SWT or Swing. Sun's development on Swing continues to focus on platform look and feel (PLAF) fidelity with each platform's windowing toolkit in the approaching Java SE 7 release (as of December 2006). In the meantime, there are other sources of high-fidelity PLAFs, many of which are collected on the javootoo site. There has been significant debate and speculation about the performance of SWT versus Swing; some hinted that SWT's heavy dependence on JNI would make it slower when the GUI component and Java need to communicate data, but faster at rendering when the data model has been loaded into the GUI[1]. However, benchmarks show no clear winner, and the results greatly depend on the context and the environments[2]. Design: The goal of the design phase is to transform the requirements specified in the SRS document into a structure that is suitable for implementing in some programming language. In this phase we followed Object-oriented design (OOD) approach. In this technique, various objects that occur in the problem domain and solution domain are first identified and then the different relationships exists among those objects are identified. Coding And Unit Testing: The purpose of the coding and unit testing phase of software development is to translate the software design into source code and test each module in isolation as this is the best way to debug the errors identified at this stage. Integration And System Testing: The basic goal of the integration and system testing is to ensure that the developed system conforms to its requirement specification. During integration and system testing phase, the modules are integrated in a planned manner. We carried out the incrementally over a number of steps. During each integration step, the partially integrated system is tested and sets of previously planned modules are added to it. Finally, when all the modules have been successfully integrated and tested, system testing is carried out Existing System The existing System was manual system. The need for computerization of the existing system arose because of many difficulties, irregularities and inaccuracy present in the current system. The main cause of the worry includes missing mails, information delay, lack of interaction. In previous system colleges were maintaining time table details manually in pen and paper, which was time taking and costly. These all were the causes of the least management strategy. So, the farm decided to computerize this System. Proposed System The proposed System is completely computer-based application. In the proposed system administrator should not to worry about their late and improper management of sales details. All the information will be available by just clicking on a single button. Thousands of records can searched and displayed without taking any significant time. System Planning Planning for information systems has a time horizon and a focus dimension. The time horizon dimension specifies the time range of the plan, where as the focus dimension relates whether the primary concern is strategic, managerial, or operational. The Project that we were assigned was required to complete within 16 weeks. What we had planned is as follows: Requirements analysis, Preliminary Investigation & Information Gathering should be covered within the 1st and 2nd week. Since we were not aware of some of the tools i.e. struts, web server, and tiles we had kept 3 weeks to understand the knot & bolts of these tools. 9 Weeks for the design of the system under development. 1 week for Testing & Implementation. And rest 2 reserve weeks. Information Gathering A key part of feasibility analysis is gathering information about the present system. The analyst must know what information to gather, where to find it, how to collect it, and what to make of it. The proper use of tools for gathering information is the key to successful analysis. The tools are the traditional interview, questionnaires, and on-site observation. Structured Analysis The traditional tools of data gathering have limitations. An English narrative description is often vague and difficult for the user to grasp. System flowcharts focus more on physical than on logical implementation of the candidate system. Because of these drawbacks, structured tools were introduced for analysis. Structured analysis is a set of techniques and graphical tools (DFD) that allow the analyst to develop a new kind of system specifications that are easily understandable to the user. DATA FLOW DIAGRAM Data Flow Diagram is a diagrammatic representation of data movement through a system –manual or automated - from inputs to outputs through processing. The data flow diagrams help in the analysis of the flow of data through a system and thus help in identifying the system requirements. These are of two types – Logical Data Flow Diagrams and Physical Data Flow Diagrams. The Data Flow Diagram (DFD) clarifies system requirements and identifies major transformations that will become programs in system design. It is the starting point of system design that decomposes the requirements specifications down to the lowest level of detail.
21-04-2015, 04:47 PM
time table management system project report pdf
05-02-2016, 12:59 PM
hi vv
03-10-2016, 11:45 AM
04-10-2016, 10:28 AM
Institution Time Table Management System will be software for generating department wise time table for NIT Hamirpur. It will be capable of producing department wise time table for all years and for all courses. It will also show the current status of classes running during a given time slot, so that higher authorities can keep a track of the classes going on. The time table will be available on the NITH official website hence easily accessible to everyone at any time. METHODOLOGY The project will be based on Javascript and PHP and using the concepts of advanced database systems. The designing of the website the project will be through HTML and CSS. The project will consist of three views:- Admin view(Department wise) Student view Teacher view Admin power will be given to one person of each department who will be responsible for formulating and allotting slots for different courses in the department. Time table will be generated by the Admin view in a semi-automatic way. Student and Teacher view can be accessed by all the students and teachers for viewing their respective time table. EXACT DELIVERABLES The following are some of the features that will be delivered by our project on completion:- Generating timetable for each department . Flexibility of time slots according to courses. Admin, Teacher, and Student view for their respective duties. Semi-automatic allotment. Current status of classes going on (Department wise, Year wise). INNOVATION It will be the first project of its kind that will automate the time table generation and will result in saving a lot of time. The project is dynamic and adaptable to the constraints at NIT Hamirpur like time constraints for different courses. |
|