• Tidak ada hasil yang ditemukan

semi-automated time scheduling management system for

N/A
N/A
Protected

Academic year: 2023

Membagikan "semi-automated time scheduling management system for"

Copied!
69
0
0

Teks penuh

This project titled “Semi-Automatic Time Scheduling Management System for University Classes” was submitted by Ikhtiar Ahmed, ID no. Grace Joydhar, ID No., and Abdullah-Al-Masum, ID No., Department of Computer Science and Engineering, Daffodil International University, has been accepted as satisfactory in partial fulfillment of the requirements for the degree of B.Sc. Department of Computer Science and Engineering Faculty of Science and Information Technology Daffodil International University. We hereby declare that all information and statements are true to the best of our knowledge and this project has been carried out by us under the supervision of Saiful Islam, Lecturer and Department of CSE Daffodil International University.

We also state that neither this project nor any part of this project has been submitted elsewhere for the award of any degree or diploma. Secondly, we are grateful and wish our profound indebtedness to supervisor, Saiful Islam, Associate Professor, Department of CSE Daffodil International University, Dhaka. Syed Akhter Hossain, Professor and Head, Department of CSE, for his kind help in completing our project and to other faculty members and staff of the CSE Department of Daffodil International University.

The developed system is a web-based application. This project was started from the experience of the teachers in the CSE department of the university in creating, managing and maintaining class routines for each semester. As a result, this project saves time for all students and teachers to find their schedule.

INTRODUCTION

  • Introduction
  • Motivation
  • Objectives
  • Expected Outcome
  • Report Layout

First, when we were admitted to the university, we saw that the routine management faculty prepares the routine of the whole semester manually, and it was very tickling to create a routine manually. Second, we saw that the routine is updated several times according to the teachers' requests or overlaps the time [17]. Finally, we thought it was so difficult and decided to create an automated routine.

After completing our initial research, we saw that it is possible to create a scheduling system using some data, although this is an N-P hard problem. Then we need to collect the data, identify the system requirements, and evaluate these data and requirements. So first design the front-end part for user interaction and then implement the system using PHP or other PHP frameworks.

The final part is testing and validating the system to ensure its successful operation. We expected a complete system that dynamically generates a routine, but due to some limitations it is not possible to create a fully automated routine.

BACKGROUND

  • Introduction
  • Related Works
  • Comparative studies
  • Scope of the problem
  • Challenges

This is the main drawback of our project, and in addition, the overlap is a problem, but it can be overcome. This system reduces the routine work of the committee and students can easily find their routine by using the semester or course code. The project Semi-Automated University Class Timetable Management System is helpful to any educational institution.

However, our project is web-based, so the user interface of this system is easy to use for all students [14]. We think that the educational institution will be interested in our project and they can create an automated system for their institution.

REQUIREMENTS SPECIFICATION

  • Business Process Model
  • Requirements Collection and Analysis
  • Use Case Model
  • Use Case Description
  • Entity Relationship Diagram
  • Logical Data Model
  • Data Flow Diagram
  • Design Requirements

Use case diagram is one kind of scenario that connects in your system or framework with the general people, organization and external system. Normal use case diagram represents the relationship between the user and application in various circumstances. The oval shape represents the use case and stick figure represents the actor or user in the process.

They are first, use case name, actor, prerequisite, user, internal path, exceptional path, and annotation. Prerequisites are those things that must be set before the use case can begin.

Figure 3.3.1: The Use-Case Diagram for the System.
Figure 3.3.1: The Use-Case Diagram for the System.

DESIGN SPECIFICATION

  • Front-end Design
  • Back-end Design
  • Interaction Design and UX
  • Implementation Requirements

Because PHP runs different kinds of platforms and supports many databases like MySQL, Oracle, etc [2]. What we want to achieve through our persona should be well defined by user stories. User expectations: This is the same case when a user comes to an application and performs some actions and expects some reactions from the product.

If the user fills in some form and clicks "Done" he expects a confirmation warning or an error message, if there is something wrong with any field he expects a warning or an error message. Usability: Less attention should be paid to figuring out how to use the app so the user can focus on completing the task. Usability: is the most important factor that focuses on "Does the user find the feature useful?" or “Is the feature important or is it just designed to provide a high-quality user interface? [19]” A function should solve some problem or purpose, and then it is only useful to the user.

Affordance and Signifier: Function that speaks for itself and suggests its own use is affordance. For this I have used Sublime Text to write the code and the languages ​​are HTML, CSS and PHP. Requirements for implementation of Back End: To implement the database I have used XAMPP server to connect the database with PHP and implement database design with MySql database.

IMPLEMENTATION AND TESTING

Implementation of Database

Implementation of Front-End Design

Testing Implementation

Testing is also important to let the developers know if there is something missing to implement that is necessary to satisfy the users of a system. Normally, unit tests are performed by developers before the installation is handed over to the testing team to formally execute the test case. We also test every part of the process, such as the import process, posting to the database, some additions and changes.

Integration testing: Integration testing is a kind of testing that connected parts of the system together to visualize whether they work properly [30]. Bottom-up integration: The bottom-up integration starts with unit testing, followed by the experiment with logically more elevated mixes of units called modules or assemblers. Top-Down Integration: In this test, top-level modules were first tested and then lower-level modules were tested.

Once all components are integrated, the application as a whole process is tested letter by letter to determine quality [30]. The first step is the development life cycle, the second is the verification of the functionality and the third is the verification and validation of the requirements and the architecture of the processor. We check this system with different entries in the second field and incorrect use of ID, password for logging into the system.

Acceptance Testing: This is probably the most important type of testing in a test system. Acceptance testing detects typos, gaps in the interface, and also looks for potential bugs in the system. Regression Testing: Regression testing used to verify that a fixed bug did not cause another requirement.

When the test finds any system defect, it does not publish the result that is being detected in the process. Regression testing also reduces gaps during testing, verifies new changes, moderates risk when testing and also increases speed to market.

Test Results and Report

CONCLUSION AND FUTURE SCOPE

Discussion and Conclusion

Scope for Further Development

APPENDICES

Appendix A: Project Reflection

UI & UX – User interface design or user interface engineering is user design and UX design refers to user experience design while UI design refers to user interface design.

Appendix B: Related Diagrams

15] IM020-09 “An Automated System for Patient Record Managemeny” vol- 22: Faculty of Computing and Information Technology, Makerere University, June 2009. 16] OGBOBE NKECHI AGNES “AUTOMATED HOSPITAL MANAGEMENT SYSTEM: Engineering of Engineering” of Vol-18 , University of Nigeria, Nsukka, Nigeria, , pp-5-7, May 2011 [17] Mohammad Majbah UddinMd. 18] Mugdha Kishor Patil, Rakhe Shruti Subodh, Prachi Ashok Pawar and Naveena Narendrasingh Turkar "Online Application for Automatic Time Table Generation" vol-4 International Journal of Current Engineering and Technology, June 2014.

Gambar

Figure 3.1.1: The Business Process Model for the Proposed Project.
Figure 3.3.1: The Use-Case Diagram for the System.
Table 3.4.1: Use case description of Import Teacher’s Details
Table 3.4.4: Use case description of Import Course Information
+7

Referensi

Dokumen terkait

10 CHAPTER 3 METHODOLOGY AND PROJECT WORK 3.1 Project Flow Chart FIGURE 3.1 Project Flow Chart Ternary Phase Diagram The experimental LLE data will be plotted in Ternary Phase