Submissions

Author Guidelines

Before preparing and submitting article manuscripts, please note that author(s) are discouraged from withdrawing submitted papers after it is in the publication process (review, copyedit, layout, etc.). During that time, INTENSIF had spent valuable resources besides time spent in the process.

Please prepare your manuscript before submission using the following guidelines and the article template below:

Ethical Statement Author(s)
I (We) hereby confirm that :
The article I (we) have submitted to INTENSIF for review is original, written by the stated author(s), and has not been published elsewhere.
The article is not currently being considered for publication by any other journal and will not be submitted for such review while under review by this journal.
3. The article contains no libellous or other unlawful statements and no materials that violate any personal or proprietary rights of any other person or entity.
4. We have obtained written permission from copyright owners for any excerpts from copyrighted works (if any) included and have credited the sources in our article.

Format

Article files should be provided in Document format (doc, docx, rtf, and odt). We do not accept other formats, such as LaTex or PDF files.

Article Length

Articles should be between 10-20 pages, including references. A maximum of 4 pages of lengthy appendices are allowed.

Article Title

A title of 15 (fifteen) words maximum should be provided.

Author Details and Authorship

All contributing authors’ names should be added, and their names should be arranged in the correct order for publication. A correct email address should be supplied only by the corresponding author. Each author's full name must be present in the exact format they should appear for publication, including or excluding any middle names or initials as required. The affiliation of each contributing author should be correct on their individual author name.

The criteria of authorship are as follows: Substantial contributions to the conception or design of the work; or the acquisition, analysis, or interpretation of data for the work; drafting the work or revising it critically for important intellectual content; final approval of the version to be published; Agreement to be accountable for all aspects of the work in ensuring that questions related to the accuracy or integrity of any part of the work are appropriately investigated and resolved.

Structured Abstract

Authors must supply a structured abstract in their submission, which includes:

• Purpose/Introduction
• Design/methods/approach
• Findings/results
• Conclusions

A maximum of 250 words in total, excluding keywords. It has to be in English regardless of the article's content's languages.

Keywords

The authors should provide appropriate, short keywords that encapsulate the paper's principal topics. The maximum number of keywords is 5 (five) words.

Article Organization

The body of articles should be organized (at least) into the IMRaD structure as follows;

• The introduction Section provides adequate background or context (problem and its significance) for the study. The subject should not be written extensively. It is expected that the rationale or purpose of the study (gap analysis), the objective in general and specific, and the hypothesis (if any) should be expressed clearly. Present a clear "state of the art" of the subject, which discusses literature and theoretical concepts behind it. A concise general background may be included in the article. Present at least 5 (five) recent related works to support the novelty of the research.
• Methods Section provides sufficient details to allow the work to be reproduced by an independent researcher. Methods already published should be summarized and indicated by a reference. If quoting directly from a previously published method, use quotation marks and cite the source. Any modifications to existing methods should also be described. Indicate the participants observed, including demographic data, number of respondents, the rationale of respondent's selection, etc. Describe the design of the experiment, such as the experiment procedures, surveys, interviews, observation characteristics, etc. Write the complete research procedure. Be sure that explanations made in the article will allow other researchers to reproduce the work or make future work out of it.
• Results and discussions. Write results in a logical sequence. Results with important findings should be presented first. When presenting results in a table or figure, do not repeat all those contents in the text. Present only the summary of the text. Describe only new and important aspects of the study. Do not repeat all information from the results section or any section above. Present limitations of the study. Write the issues that are new or unsolved for future research. This section consists of What/How the presented data were produced; no raw data should be present in the article. The produced data are presented in tables or figures with an explanation of the results/findings from the work. The section must also address connections between findings and basic concepts or hypotheses made earlier. The authors should also express whether any arguments relating to other works by other researchers were needed. Write the implications of the work related to theoretical or applications.
• Conclusions Section. The conclusion should be linked to the title and objectives of the study. Do not make statements that are not adequately supported by your findings. Write the improvements made to the industrial engineering field or science in general. Do not make further discussions, repeat the abstract, or only list the results of research results. Do not use bulleted points; use paragraphed sentences instead.

Biographies and Acknowledgments

Those who contribute but do not meet all criteria for authorship should not be listed as authors but should be acknowledged at the end of the text. Only the names of the persons, but not their roles, should be written under the acknowledgement section. Authors must declare all sources of external research funding in their article, and a statement to this effect should appear in the Acknowledgements section.

Authors who wish to include these items should save them in the MS Word file to be uploaded with the submission. A brief professional biography of 100 words maximum should be supplied for each named author if they are to be included.

Article Categories

Authors must categorize their paper as part of the article information. The category most closely describes their paper should be selected from the list below.

• Research paper. This category covers papers that report on any research the authors undertake. The research may involve the construction or testing of a model or framework, action research, data testing, market research or surveys, or empirical, scientific, or laboratory research. 
• Technical paper. Describes and evaluates technical products, processes, or services. 
• Conceptual paper. These papers will not be based on research but will develop hypotheses. The papers will likely be discursive and will cover philosophical discussions and comparative studies of others' work and thinking. 
• Case study reports describe actual interventions or experiences within organizations. They may well be subjective and will not generally report on research. A description of a legal case or a hypothetical case study used as a teaching exercise would also fit into this category. 

Headings

Headings must be concise, clearly indicating the distinction between the hierarchy of headings. The format is provided in the article's template.

Notes/Endnotes

Notes or Endnotes should be used only if absolutely necessary. They must be identified in the text by consecutive numbers, enclosed in square brackets and listed at the end of the article.

Figures

All Figures (charts, diagrams, line drawings, web pages/screenshots, and photographic images) should be submitted electronically. All Figures should be high quality, legible and numbered consecutively with Arabic numerals. Graphics may be supplied in colour to facilitate their appearance on the online database. Figures created in MS Word, MS PowerPoint, and MS Excel should be supplied in native formats. Electronic figures created in other applications should be copied from the origination software and pasted into an MS Word template document. Photographic images should be inserted in the article's main body and of high quality.

Tables

Tables should be typed and included in the main body of the article. The position of tables should be inserted in the text as close to the point of reference as possible. Ensure that any superscripts or asterisks are shown next to the relevant items and that corresponding explanations are displayed as footnotes to the table, figure, or plate.

References

INTENSIF prefers articles that refer mainly to journal articles, research reports, and conference proceedings rather than rely heavily on textbooks or handbooks to demonstrate articles' novelty in the subject discussed. The use of Mendeley as a tool in referencing is preferable and encouraged. References should be carefully checked for completeness, accuracy, and consistency.

Author(s) should cite publications in the text following the IEEE citation style. At the end of the paper, a reference list in alphabetical order should be supplied as follows:

[1]        P. L. L. Belluano, “Penerapan Sistem Replikasi Dan Integrasi Basis Data Terdistribusi Pada Pangkalan Data Pendidikan Tinggi (PDPT),” ILKOM Jurnal Ilmiah, vol. 9, no. 1, pp. 42–48, 2017.

[2]        S. Sucipto, E. K. Dewi, N. C. Resti, and I. H. Santi, “Improving The Performance of Alumni Achievement Assessment by Integrating Website-Based Tracer Study Information Systems and Telegram API,” Teknik, vol. 41, no. 1, pp. 72–77, 2020, doi: 10.14710/teknik.v41i1.25307.

[3]        M. A. Baazizi, D. Colazzo, G. Ghelli, C. Sartiani, and S. Scherzinger, “Negation-closure for JSON Schema,” Theor Comput Sci, vol. 955, p. 113823, Apr. 2023, doi: 10.1016/J.TCS.2023.113823.

[4]        T. Whairit, B. Phadermrod, and V. Attasena, “JINDEX: JSON and index search system for plant germplasm database,” Journal of King Saud University - Computer and Information Sciences, vol. 35, no. 8, p. 101701, Sep. 2023, doi: 10.1016/J.JKSUCI.2023.101701.

[5]        E. Chavarriaga, F. Jurado, and F. D. Rodríguez, “An approach to build JSON-based Domain Specific Languages solutions for web applications,” J Comput Lang, vol. 75, p. 101203, Jun. 2023, doi: 10.1016/J.COLA.2023.101203.

[6]        M. Pirani, A. Cucchiarelli, and L. Spalazzi, “Paradigms for database-centric application interfaces,” Procedia Comput Sci, vol. 217, pp. 835–845, 2023, doi: https://doi.org/10.1016/j.procs.2022.12.280.

[7]        L. Diop, C. T. Diop, A. Giacometti, and A. Soulet, “Pattern on demand in transactional distributed databases,” Inf Syst, vol. 104, p. 101908, 2022, doi: https://doi.org/10.1016/j.is.2021.101908.

[8]        A. B. Warsito, A. Ananda, and D. Triyanjaya, “Penerapan Data JSON Untuk Mendukung Pengembangan Aplikasi Pada Perguruan Tinggi Dengan Teknik Restfull Dan Web Service,” Technomedia Journal, vol. 2, no. 1, pp. 26–36, 2017, doi: 10.33050/tmj.v2i1.313.

[9]        B. W. Putra, A. Saputra, R. Sanjaya, and D. Kurniawan, “Implementasi Framework CodeIgniter dan Restful API pada Sistem Informasi Manajemen Tugas Akhir 1st,” Prosiding Annual Research Seminar, vol. 5, no. 1, p. 309, 2019.

[10]      E. Susanti, “Implementasi RESTful API dalam Pembuatan Master Data Planogram Menggunakan Framework Flask (Studi Kasus: PT Sumber Alfaria Trijaya, Tbk),” Techno.Com, vol. 19, no. 3, pp. 295–307, 2020, doi: 10.33633/tc.v19i3.3468.

[11]      F. W. Handono, H. Nurdin, F. B. Siahaan, H. Sugiarto, and I. Chaidir, “Jurnal Mantik Mysql Database Syncronization Using Restful Webservice Api PT . Minori,” Jurnal Mantik, vol. 5, no. 36, pp. 855–859, 2021.

[12]      Y. Kasahara, “End of Basic Authentication and Migration to Modern Authentication for Exchange Online,” Proceedings ACM SIGUCCS User Services Conference, pp. 32–35, 2023, doi: 10.1145/3539811.3579560.

[13]      Roger S. Pressman, Software Quality Engineering, 2010th ed., vol. 9781118592. Wiley, 2014. doi: 10.1002/9781118830208.

[14]      M. Bianchi, G. Marzi, and M. Guerini, “Agile, Stage-Gate and their combination: Exploring how they relate to performance in software development,” J Bus Res, vol. 110, pp. 538–553, Mar. 2020, doi: 10.1016/J.JBUSRES.2018.05.003.

[15]      S. Pradhan and V. Nanniyur, “Large scale quality transformation in hybrid development organizations – A case study,” Journal of Systems and Software, vol. 171, p. 110836, Jan. 2021, doi: 10.1016/J.JSS.2020.110836.

[16]      Sucipto et al., “Hidden Treasures of Kediri’s Medicinal Plants: A Collaborative Effort to Map and Validate Authentic Information Using Innovative QR Code Security and Cryptography,” IOP Conf Ser Earth Environ Sci, vol. 1242, no. 1, p. 012036, Sep. 2023, doi: 10.1088/1755-1315/1242/1/012036.

[17]      R. V. Rochim, A. Rahmatulloh, R. R. El-Akbar, and R. Rizal, “Performance Comparison of Response Time Native, Mobile and Progressive Web Application Technology,” Innovation in Research of Informatics (INNOVATICS), vol. 5, no. 1, pp. 36–43, May 2023, doi: 10.37058/INNOVATICS.V5I1.7045.

[18]      S. Jalil, S. Rafi, T. D. Latoza, K. Moran, and W. Lam, “ChatGPT and Software Testing Education: Promises & Perils,” Proceedings - 2023 IEEE 16th International Conference on Software Testing, Verification and Validation Workshops, ICSTW 2023, pp. 430–437, 2023, doi: 10.1109/ICSTW58534.2023.00078.

[19]      K. Xue, V. Yaneva, C. Runyon, and P. Baldwin, “Predicting the Difficulty and Response Time of Multiple Choice Questions Using Transfer Learning,” Proceedings of the Annual Meeting of the Association for Computational Linguistics, pp. 193–197, 2020, doi: 10.18653/V1/2020.BEA-1.20.

[20]      M. Zheng and D. Bender, “Evaluating outcomes of computer-based classroom testing: Student acceptance and impact on learning and exam performance,” Med Teach, vol. 41, no. 1, pp. 75–82, Jan. 2019, doi: 10.1080/0142159X.2018.1441984.

[21]      C. H. Wang, W. J. Lo, and M. J. J. Wang, “Usability evaluation of augmented reality-based maintenance instruction system,” Human Factors and Ergonomics in Manufacturing & Service Industries, vol. 32, no. 3, pp. 239–255, May 2022, doi: 10.1002/HFM.20942.

[22]      R. Silva, A. C. Lima, E. Andrade, A. I. Martins, and N. P. Rocha, “Heuristic Evaluation of the Usability of a Mechanical Ventilator Interface through a Simulator,” Procedia Comput Sci, vol. 219, pp. 1232–1239, 2023, doi: https://doi.org/10.1016/j.procs.2023.01.406.

[23]      X. Chen, Z. Ji, Y. Fan, and Y. Zhan, “Restful API Architecture Based on Laravel Framework,” J Phys Conf Ser, vol. 910, no. 1, 2017, doi: 10.1088/1742-6596/910/1/012016.

[24]      H. Mezni, “Web service adaptation: A decade’s overview,” Comput Sci Rev, vol. 48, p. 100535, May 2023, doi: 10.1016/J.COSREV.2023.100535.

[25]      A. D. K. B. W. Putra, A. Saputra, M. R. Sanjaya, “Enabling Collaboration of CodeIgniter Framework and RESTful API for Utilize Web Mobile Interface Implemented on Final Project Management System,” vol. 172, no. Siconian 2019, 2020, doi: 10.2991/aisr.k.200424.080.

[26]      T. Telang, “MicroProfile JSON Web Tokens and Jakarta Security,” Beginning Cloud Native Development with MicroProfile, Jakarta EE, and Kubernetes, pp. 183–212, 2023, doi: 10.1007/978-1-4842-8832-0_8.

[27]      M. Baker, “Authentication and Authorization,” Secure Web Application Development, pp. 287–349, 2022, doi: 10.1007/978-1-4842-8596-1_10.

[28]      A. R. Khan, L. Khalid, A. A. Finance, and S. Arabia, “A Brief Review on Cloud Computing Authentication Frameworks,” Engineering, Technology & Applied Science Research, vol. 13, no. 1, pp. 9997–10004, Feb. 2023, doi: 10.48084/ETASR.5479.

[29]      H. Subramanian and P. Raj, Hands-On RESTful API Design Patterns and Best Practices: Design, develop, and deploy highly adaptable, scalable, and secure RESTful web APIs. Packt Publishing Ltd, 2019.

[30]      K. H. Huynh and J. Kerssens, “Security Evaluation on Amazon Web Services’ REST API Authentication Protocol Signature Version 4,” rp.os3.nl, [Online]. Available: https://rp.os3.nl/2019-2020/p65/report.pdf

[31]      S. U. Meshram, “Evolution of Modern Web Services–REST API with its Architecture and Design,” International Journal of Research in Engineering, Science and Management , vol. 4, no. 7, pp. 83–86, 2021.

[32]      J. A. Suthendra and M. A. I. Pakereng, “Implementation of Microservices Architecture on E-Commerce Web Service,” ComTech: Computer, Mathematics and Engineering Applications, vol. 11, no. 2, pp. 89–95, 2020, doi: 10.21512/comtech.v11i2.6453.

[33]      A. Arcuri, “RESTful API automated test case generation,” Proceedings - 2017 IEEE International Conference on Software Quality, Reliability and Security, QRS 2017, no. 1, pp. 9–20, 2017, doi: 10.1109/QRS.2017.11.

[34]      M. A. Yaghoub-Zadeh-Fard and B. Benatallah, “API2CAN: a dataset & service for canonical utterance generation for REST APIs,” BMC Res Notes, vol. 14, no. 1, pp. 1–3, 2021, doi: 10.1186/s13104-021-05593-w.

[35]      S. Parsa, M. Zakeri-Nasrabadi, and B. Turhan, “Testability-driven development: An improvement to the TDD efficiency,” Comput Stand Interfaces, vol. 91, p. 103877, Jan. 2025, doi: 10.1016/J.CSI.2024.103877.

[36]      S. Sucipto and J. Karaman, “Integration of Legalization Information System Web-Based using Shipping API and Telegram API,” JUITA: Jurnal Informatika, vol. 8, no. 2, p. 131, 2020, doi: 10.30595/juita.v8i2.7104.

[37]      D. Felicio, J. Simao, and N. Datia, “RapiTest: Continuous Black-Box Testing of RESTful Web APIs,” Procedia Comput Sci, vol. 219, pp. 537–545, Jan. 2023, doi: 10.1016/J.PROCS.2023.01.322.

[38]      O. Baniaș, D. Florea, R. Gyalai, and D. I. Curiac, “Automated specification-based testing of REST APIs,” Sensors, vol. 21, no. 16, 2021, doi: 10.3390/s21165375.

[39]      N. Ahmad and S. M. R. Hasan, “A new ASIC implementation of an advanced encryption standard (AES) crypto-hardware accelerator,” Microelectronics J, vol. 117, p. 105255, Nov. 2021, doi: 10.1016/J.MEJO.2021.105255.

[40]      A. Borrego, M. Bermudo, F. Sola, D. Ayala, I. Hernández, and D. Ruiz, “Silence — A web framework for an agile generation of RESTful APIs,” SoftwareX, vol. 20, p. 101260, Dec. 2022, doi: 10.1016/J.SOFTX.2022.101260.

[41]      F. Palma, T. Olsson, A. Wingkvist, and J. Gonzalez-Huerta, “Assessing the linguistic quality of REST APIs for IoT applications,” Journal of Systems and Software, vol. 191, p. 111369, Sep. 2022, doi: 10.1016/J.JSS.2022.111369.