Development of Integrated Laboratory Management Information System

— In 2021 PGRI Semarang University have at least 64 laboratories. This makes it a challenge for a private university to obtain funding independently in managing and maintaining assets of that size. It is necessary to develop an information system that could provide information input and information output facilities managed by the faculty and laboratory managers at the unit level of study programs and faculties, to be further reported as information to institutions and stakeholders. The researcher wants to make it a research goal, by designing and developing a Laboratory Information System (SILab) at the University of PGRI Semarang, which is validly tested according to the design results and is reliable or proven to be used well by users through user response tests.


I. INTRODUCTION
IKIP PGRI Semarang, which in 2014 transformed into Universitas PGRI Semarang, has made extraordinarily significant development. Starting from the addition of the number of faculties, study programs, educational staff, and supporting facilities such as laboratories. According to the results of the latest survey summarized in the matrix of the distribution of laboratory facilities owned by this university, it was recorded that there were approximately 64 laboratories, spread over Laboratory and SMA Laboratory, PGRI University Semarang 4 Laboratory. This is a challenge in itself, considering that if it is not managed properly, then the facilities which were originally an asset of the institution become a burden in itself. Considering that PGRI Semarang University is a private institution, which obtains its funding independently. From this, a thought emerged that it was deemed necessary to manage such a large asset, it was highly recommended or an effective system for providing information reporting was needed, so that the potential of the laboratory could be well organized and well-structured for its management and development plan. This developed system will later be able to provide informed input and information output facilities which are managed by the faculty and laboratory managers at the unit level of study programs and faculties, to be subsequently reported as information to institutions and stakeholders (both students and lecturers as users, or the general public who requires cooperation in special laboratory tests in universities according to their needs). Business Polytechnic)" uses a DF-Diagram system design based on business process analysis, PHP and MySQL programming languages, the resulting system valid information can be used according to the design. 5. Al Antoni Akhmad's research (Akhmad, 2010)  Explains how to develop an information system or software using the evolutionary method or the latest AGILE which is based or focused on the work process that is usually carried out iterative, where rules and solutions are agreed upon by collaboration between teams in an organized and structured manner. This means that the information system developed is adaptive, or developed and can be redeveloped as needed.

The book or adaptation of Mei
Prabowo, M.Com (Prabowo, nd) entitled "Information System Development Methodology" Says that in addition to the method of developing information systems using the AGILE development model, there is also another method of developing information systems or software, namely the Rapid Method. Application Development and Spiral method. As for testing, the three of them can use several methods, namely using performance testing, system testing, unit testing, or integration testing

II. METHOD
To achieve the research objectives, software development research methods or information systems development methods are used, namely the AGILE evolutionary method, as for the information system design model using Use Case Diagrams which are then interpreted more clearly using Context Diagrams and database design using Entity-Relationship Diagrams (ER). -Diagram). For testing using performance testing based on the design and user response. The research method that the researcher applies is Agile, this method was chosen because the Agile method is faster in making changes or system development

Planning
The next stage is the stage of gathering requirements by focusing on: hardware, software, and Brainware, Brainware itself includes making systems by translating designs or drawings into programming languages, validating and testing the system when the system is ready to use, and performing maintenance on the system so that the system can run. run as needed.

Design
This stage consists of how the system will be built in other words planning software solutions.

Coding
This stage is the stage of code generation, namely translating the image or design into an algorithm that can be implemented into a programming language.

Test
Next is the final stage in making software or system. After doing the analysis, design, and coding, the finished system will be used by the user. Then the software that has been made must be maintained regularly. In performance testing which is based on the design, the researcher focuses on two main modules of the designed system, namely; 1. Front End Module This is the part that is directly visible to the user. Users can directly interact in this section 2. Back End Module Is the back of the layer that can only be accessed by the admin While in testing user responses, researchers use a questionnaire which can be in the form of closed/open questions/statements, and each respondent's answer has a score as follows: With this type of measurement scale, a firm answer will be obtained, namely "yesno"; "True False"; ever -never"; positivenegative and so on. The answer "yes" will be given a score of 1 (one) and for the answer "no" will be given a score of 0 (zero). (Sugiyono, 2016:169).

Figure 2. Context Diagram
In this study using a design model of information system design Use Case Diagram which is then interpreted in more detail using Context while the database design uses Entity Relationship Diagram (ER-Diagram). Shown in the context of the diagram above there are 3 entities, and some of the data flows include: 1

. User Entity
The user entity has 9 data streams. The user will perform the login process by entering the username and password. Furthermore, the user can input (choose) a loan, either laboratory loan or equipment and goods. In addition, the user can also make a return. The system will process according to what is selected by the user, after that the system will provide feedback in the form of a print out of borrowing or returning. Users can also view loan and return reports.

Admin Entity
The admin entity has 12 data streams. Admin will perform the login process by entering the username and password. Admins can access the data on the menus in the dashboard, namely class menus, rooms, courses, lab assistants, goods and tools, laboratory heads, admins, lecturers, students, and practicum schedules. Admin also has search, edit, add, and delete actions on class menus, rooms, courses, lab assistants, goods and tools, laboratory heads, admins, lecturers, students, and practicum schedules. Admin can also print and save loan and return reports.

Entity Head of Laboratory
The head laboratory entity has 5 data streams. The Head of the Laboratory will carry out the login process by entering a username and password. The Head of the Laboratory can print and save reports on the results of borrowing and returning. The head of the laboratory can view login data, as well as data on goods and tools. Next, an Entity Relationship Diagram (ER-Diagram) is shown which shows the relationship between entities and the transactional data that occurs in them.

Figure 3. Entity Relationship Diagram
Furthermore, it is still in relation to database design which is literally a collection of tables in which there are entities, so the following table design and the entities in it are shown.

Class table
The class table contains information about the existing classes in the system. Which in it consists of class code and class name which is described as follows:   Table of practicum courses  The table of practicum courses contains information about practical courses in the information technology education study program. It consists of course code, course name, semester and credits which are described as follows:  The lab assistant table contains information about laboratory assistants in the information technology education study program. Which consists of NPM, assistant name and semester which is described as follows:  Table of tools and goods  The tools and goods table contains information about tools and goods in the laboratory of the information technology education study program. Which in it consists of the code of goods, the name of the goods and the number of goods described as follows: Here is the implementation of the home menu. In the computer laboratory management information system there are two dashboards, namely the admin dashboard and the user dashboard. The admin dashboard has a dashboard menu, master, account, practicum schedule, loans, loan reports and logout. While on the dashboard the user only has a home menu, and logout. However, the admin and user dashboard display designs remain the same, only the menu access makes the difference.
Here is the implementation of the home menu for admin:

Display course menu
The following is the implementation of the course menu. In the course menu there is a table containing the number, course_code, course_name, semester, credits and actions. And there is a table for adding data in the form of data for the course code, subject_name, semester, credits. Here is the implementation of the course menu:

Display menu items and tools
Here is the implementation of the menu of items and tools. In the goods and tools menu there is a table containing the number, item_code, item_name, quantity, status and action. And there is a table added data in the form of data code_barang, nama_barang, amount, status. Here's an implementation of the tools and items menu:

Loan report menu display
The following is the implementation of the loan report menu. In the loan report menu there is a   Using performance testing that focuses on 2 main modules of the system which includes front end and back-end modules

User Response Test Results
Following are the results of testing user responses to the developed Integrated Laboratory Information System Calculations are carried out using the following formula: P=f/n "x" 100%……………………………. [1] Description : P = Percentage f = Frequency of "yes" answers n= Number of questions and obtained the following results: