Wednesday, March 11, 2020
Khan Doc Essays
Khan Doc Essays Khan Doc Essay Khan Doc Essay System manages the schedule of courses and teachers according to the rooms. Time Table is the key in any educational institution, as it allows scheduling the courses for study. All the students and teachers follow this schedule for effective study. Time Table Management System shall allow different teachers to schedule their courses and it shall also avoid clash of rooms and shall keep in mind the other subjects of the class to avoid any clash. 2. General Goal: Time table management is a difficult task in any educational institute management system and it is done manually.Goal of this project is to try to automate the process of Time Table Management. Automated Time Table Management System can be very effective in any educational management system. Another Goal of this project is to try to make it intelligent so it know a little about time table based upon user input and help the user in making the correct decision. Time Table Management System will be multi agent meaning that differ ent entities will exist independently and Time Table Management System will only provide a way for them to interact. . Current System: Current system in any SMS works manually and requires minimal input from involving entities and putting the entire decision making on one person, making extra work for that person. Teachers give their preferred time to the person responsible of Time Table Management. The Person responsible for time table management consider Teacher input and selects a subject, teacher, class, sees the available time slots and room and enters that information. Whole process is done manually. 4. Proposed System: 4. 1 Overview:We will design a multi agent based system, with teacher entering their desired timing and system will accept our available rooms. System will keep record of previous time table as well. System will also provide the list of the available rooms and time slots. 4. 2 Functional requirements: 1- There shall not be time table clash for a class or teache r. 2- Teacher can select room and subject to teach. 3- Subject or room already taken shall not be available again. 4- It shall not put the entire load on one person. 5- System can schedule time table dynamically. 6- Easy report generation. Teacher can not modify or update information. 8- If required system shall access teacher information from existing profiles and records. 4. 3 Non-Functional requirement: 1- Separate account for users with access types. As many people will be accessing the system simultaneously or separately, so it is necessary to maintain different account and access rights for the users. 2- Security implemented through account and login. The system need to be very secure apart from the automation, so it do not allow the users to make unwanted changes in any part of the system and it should not llow the unwanted users. 3- Report for available slot. Members shall have the able to view report about the available rooms and time slots. 4- Reports room, time and subje ct. Members shall be able to view time table in different ways, i. e. room wise, subject wise or time wise. 5- Information sent to teachers for any update in time table. If time table is updated by the admin due to any reason then a notification is to be sent to the concerned teachers. 6- Distributed application. The application shall be distributed and shall be available for access from different areas. 4. 4 ERD: [pic] 4. System Model: 4. 6 USE CASES: 4. 6. 1 Diagrammatic Use Cases: DEO Fig 1: Data Entry Operatorââ¬â¢s Use Cases Teacher Fig 2: Teacherââ¬â¢s Use Cases Student and others Fig 3: Studentââ¬â¢s Use cases. Fig 4: System Only Process 4. 6. 2 Descriptive Use Cases: 4. 6. 2. 1 Administration |UC-DEO-1 Enter Room Information | |Scope: |Administration | |Actor: |Data entry operator.To enter data | | |Admin to enter data. | |Pre condition | User logged in and identified | |Work Flow: | |User action |System Response | | |1.System provides List of existing room | |2. Us er enter room name. | | |3. User saves records. | | | |4. If record is saved then message is generated. | |Post condition |System enters the record and stays at the page. | |Occurrence |Very rarely only the start. | UC-SG-1 Generate available slots | |Scope: |Administration | |Actor: |System for calculation. | | |DEO to active it. | |Pre condition |Subject information is available. | | |Teacher information is available. | | |Semester information is available. | |Room information is available. | |Work Flow: | |User action |System Response | | |system generate available slot by making calculation | |Post condition |Record is saved. | | |Admin is informed. | |Occurrence |Frequently.To view the information. | |UC-SG-2 Make update schedule | |Scope: |Administration | |Actor: |System for calculation. | | |DEO to active it. | |Pre condition |Subject information is available. | | |Teacher information is available. | |Semester information is available. | | |Room information is available. | | |Timetable is Available. | |Work Flow: | |User action |System Response | | |system give schedule | |2- User makes changes. | |3- User saves Record. | | | |system update record | |Post condition |Record saved admin informed | |Occurrence |Frequently. To update the schedule. |UC-DEO-3 Enter teacher information | |Scope: | Administration | |Actor: | DEO to enter teacher information. | | |Admin to enter or view teacher information. | |Pre condition |User is logged in and identified. |Work Flow: | |User action |System Response | | |1- system provides existing records | | | | |2- User enters name, address, rank and educational | | |level. | | |3- User saves the record. | | | |4- System generate success message. | |Post condition |User is informed and stays on the page | |Occurrence |Rarely, only it starts. | UC-DEO-4 Account Creation | |Scope: |Administration | |Actor: |Data entry operator. To enter data | | |Admin to enter data. | |Pre condition | User logged in and identified | |Work F low: | |User action |System Response | |1.User will login name, email address and account type (DEO, Student, and | | |teacher) of the account. | | |2. User will enter name, address, status and study level of the account | | |3. User saves records. | | | |4. If record is saved then message is generated. | |Post condition |System enters the record and stays at the page. | |Occurrence |Very rarely only the start. | 4. 6. 2. 2 Reports UC-VI-1 View information | |Scope: |Report | |Actor: |DEO, to view information about Time Table. | | |Admin, to view information about Time Table. | | |Student, to view information about Time Table. | | |Teacher, to view information about Time Table. | |Pre condition |User is logged in and identified. |Work Flow: | |User action |System Response | | 1- User select report type (time table ,room schedule, teacher) | | | |2- System generate the report | |Post condition |System stays at the page. | |Occurrence |Very frequently to view reports. | 4. 6. 2. 3 Tea cher |UC-TE-1 Teacher time table entry | |Scope: |Teacher | |Actor: Teacher gives available time. | |Pre condition |Teacher logged in and identified. | | |Room and subject record exists. | |Work Flow: | |User action |System Response | | 1- User select subject to time table for | | | |2- System present previous time table for subject | |3- User selects room. | | |4- System gives available timing for that room | | 5- user select available timing | | | | | |6- User save record | | | |7. System generates the success message. | |Post condition |System update time table. | | |System informs admin. | | |System other teacher. | |Occurrence |Rarely. To enter information from the teacher at the start of the course. | 5. 0 Hardware and Software Requirements. 5. 1 Hardware specifications:Our System will require minimum system specification at the user end. With minimum P2 with 366 MHz processor with 64 MB RAM Internet connectivity. Our system will require high end system at the server end wit h minimum P4 1. 3 GHz processor with 512 MB ram 24 hour internet connectivity Power source. 5. 2 Software Requirements: At the user end our system will require Operating System Internet Browser At the server end our system will require an Operating system Web Server Software (i. e. Apache) PHP MySQL database. 5. 3 User Characteristics: Following types of users will interact with our system. Administrator: Responsible with over all functionality of the system. Data Entry Operator: DEO to assist admin in data entry process. Teacher: To enter his/her preferred time into the system to generate time table. And to view information. Student: To view time table information [pic] Enter room information Enter teacher information Enter subject information View available information Enter Timing View schedule View information Generate available slot Make/ update time table Administration Enter Room Information Generate available slots Make update schedule Enter teacher information Teacher Teacher time table entry Reports Account Creation 1 M M M M M 1 M 1 M Follow Follow Have Study Teach Subject Student Teacher Time Table
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment
Note: Only a member of this blog may post a comment.