Author Guidelines
AUTHOR GUIDELINES
RESKOM: Jurnal Rekayasa Sistem Komputer
Guidelines for manuscript preparation, submission, review, and publication
RESKOM: Jurnal Rekayasa Sistem Komputer welcomes scholarly manuscripts in the field of computer systems engineering, computer science, information technology, software engineering, computer networks, embedded systems, artificial intelligence, internet of things, cybersecurity, data systems, and related areas of digital technology. These author guidelines are designed to help authors prepare manuscripts that meet academic, technical, ethical, and editorial standards before submission through the journal’s online system.
Originality
Manuscripts must be original, unpublished, and not under consideration by another journal or publisher.
Technical Quality
The manuscript should show clear technical contribution, methodological rigor, and relevance to computer systems engineering.
Ethical Compliance
Authors must comply with publication ethics, plagiarism policy, citation accuracy, and responsible research conduct.
1. General Submission Rules
Manuscripts submitted to RESKOM: Jurnal Rekayasa Sistem Komputer must be original works that have not been previously published and are not being reviewed or considered for publication elsewhere. Authors are responsible for ensuring that the submitted manuscript is free from plagiarism, duplicate publication, data fabrication, and unethical authorship practices.
All submissions should be prepared according to the journal template and submitted through the official online submission system. Manuscripts that do not follow the journal’s format, focus, scope, or ethical standards may be returned to authors before peer review.
Authors should carefully check the manuscript for completeness, language accuracy, technical clarity, citation consistency, and formatting before submission.
2. Types of Manuscripts
RESKOM accepts several types of scholarly manuscripts, including:
- Research Articles
Original empirical, experimental, computational, or development-based research in computer systems engineering and related fields. - System Design and Development Articles
Manuscripts reporting the design, development, testing, and evaluation of hardware, software, applications, networks, information systems, or integrated computer systems. - Review Articles
Systematic, narrative, or critical reviews that synthesize current knowledge, technologies, frameworks, algorithms, tools, or trends in computer systems and information technology. - Case Studies
In-depth analysis of implementation, system deployment, technology adoption, institutional computing practices, or applied digital solutions in specific contexts. - Conceptual and Technical Notes
Short scholarly contributions presenting models, frameworks, technical insights, or early-stage innovations relevant to computer systems engineering.
3. Manuscript Language
Manuscripts may be written in Bahasa Indonesia or English. Authors should use formal academic language, clear technical terminology, and consistent writing style throughout the manuscript.
English manuscripts must be written in clear academic English. Indonesian manuscripts should use standard academic Indonesian and avoid informal expressions. Technical terms, acronyms, and abbreviations should be defined when first used.
4. Manuscript Structure
A manuscript should be organized in a logical, systematic, and technically clear structure. The recommended structure is as follows:
| Title | Concise, specific, and reflecting the main contribution of the study. |
| Author Information | Author names, affiliations, email addresses, and corresponding author information. |
| Abstract | Briefly explains the problem, objective, method, findings, and conclusion. |
| Keywords | Three to five keywords representing the main topic and technical domain. |
| Introduction | Research background, problem statement, research gap, novelty, and objective. |
| Method | Research design, system design, tools, dataset, instruments, and testing procedures. |
| Results and Discussion | System output, experimental results, performance evaluation, interpretation, and comparison. |
| Conclusion | Summary of findings, contribution, limitation, and future work. |
| References | Complete list of cited sources according to the journal citation style. |
5. Title, Authors, and Affiliation
- The title should be concise, informative, and not overly broad.
- The title should clearly reflect the system, method, algorithm, technology, or problem being studied.
- Author names should be written without academic titles.
- Each author should provide institutional affiliation and email address.
- The corresponding author must be clearly identified for editorial communication.
6. Abstract and Keywords
The abstract should be written in one paragraph and should not exceed 200–250 words. It should summarize the research problem, objective, method, main findings, technical contribution, and conclusion.
The abstract should not include citations, tables, figures, equations, or undefined abbreviations. It must be sufficiently informative so readers can understand the core contribution of the study.
Keywords should consist of three to five terms, such as computer system, software engineering, artificial intelligence, internet of things, embedded system, computer network, cybersecurity, data mining, information system, cloud computing, or machine learning.
7. Introduction
The introduction should explain the background of the problem, current technological development, research gap, urgency, novelty, and objectives of the study. Authors should clearly explain why the topic is important in the field of computer systems engineering or information technology.
A strong introduction should be supported by relevant and recent references, especially journal articles, conference papers, technical standards, or reputable academic sources.
The final paragraph of the introduction should state the research objective, research contribution, and, where applicable, the main research question or hypothesis.
8. Method
The method section should explain how the research, system design, experiment, simulation, or development process was conducted. The explanation should be detailed enough to allow readers to understand, evaluate, and, where possible, replicate the study.
Depending on the type of manuscript, this section may include:
- Research design or system development model;
- System architecture, flowchart, block diagram, or use case design;
- Hardware and software specifications;
- Dataset, data source, or data collection procedure;
- Algorithm, model, framework, protocol, or computational method;
- Testing, validation, simulation, or performance evaluation technique;
- Tools, programming language, platform, and experimental environment.
For software or hardware development studies, authors should clearly explain the development stages and evaluation criteria used to determine system performance or usability.
9. Results and Discussion
The results section should present findings clearly and objectively. Results may include system implementation, interface design, algorithm performance, accuracy, response time, throughput, latency, usability testing, simulation results, experimental findings, or comparative evaluation.
The discussion should interpret the results, explain the technical meaning of the findings, compare them with previous studies, identify strengths and limitations, and clarify the contribution of the study to computer systems engineering or related fields.
Authors should avoid simply describing tables and figures. Instead, the discussion should explain what the data mean, why the results matter, and how they contribute to the field.
10. Tables, Figures, Algorithms, and Source Code
- Tables and figures must be clear, numbered consecutively, and cited in the text.
- Table titles should be placed above the table, while figure captions should be placed below the figure.
- Diagrams, architecture models, circuit designs, screenshots, and flowcharts must be readable and relevant to the discussion.
- Algorithms should be presented clearly using pseudocode, flowcharts, or structured explanation.
- Source code should be included only when necessary for understanding the study and should be formatted clearly.
- Large datasets, software documentation, or code repositories may be cited or linked where appropriate.
11. Conclusion
The conclusion should summarize the main findings and technical contribution of the study. It should answer the research objective and highlight the significance of the results.
The conclusion may include limitations of the study, practical implications, and recommendations for future research, system development, or technological improvement.
12. Manuscript Formatting
| File Format | Microsoft Word, OpenOffice, or RTF format |
| Paper Size | A4 |
| Main Font | 12-point font or according to the official journal template |
| Spacing | Single-spaced or according to the official journal template |
| Figures and Tables | Placed near the relevant text, not grouped at the end |
| Template | Authors are strongly encouraged to use the official RESKOM manuscript template |
13. Citation and References
Authors must cite all sources used in the manuscript accurately and consistently. The reference list should contain only sources cited in the text, and every in-text citation must appear in the reference list.
For technical manuscripts in computer systems engineering, authors are encouraged to use a consistent numbered citation style or the style required by the official journal template. Reference management tools such as Mendeley, Zotero, or EndNote are recommended.
Example of journal article reference:
[1] A. Author and B. Author, “Title of article,” Journal Name, vol. x, no. x, pp. xx–xx, year, doi: xx.xxxx/xxxxx.
14. Ethical Requirements
Authors must follow ethical standards in scholarly publishing. The manuscript must be free from plagiarism, self-plagiarism, duplicate submission, data fabrication, data falsification, citation manipulation, and inappropriate authorship.
Research involving human participants, user data, institutional data, sensitive information, or security-related systems should respect privacy, consent, confidentiality, and relevant ethical principles.
Authors are responsible for obtaining permission for copyrighted materials, including images, diagrams, datasets, code, software, or instruments owned by other parties.
15. Plagiarism Screening
All manuscripts submitted to RESKOM may be checked using plagiarism detection software. Manuscripts with excessive similarity, missing citations, improper paraphrasing, or indications of plagiarism may be returned to authors, rejected, or subjected to further editorial evaluation.
Authors should ensure that all quotations, paraphrased ideas, figures, algorithms, datasets, code fragments, and technical materials from other sources are properly cited.
16. Peer Review Process
Submitted manuscripts will undergo editorial screening before being sent for peer review. The screening includes scope suitability, manuscript completeness, formatting, originality, and ethical compliance.
Manuscripts that pass the initial screening will be reviewed by reviewers with relevant expertise. Reviewers evaluate the technical quality, novelty, methodology, system performance, discussion, citation, and contribution of the manuscript.
Possible editorial decisions include accepted, revision required, resubmit for review, or rejected. Authors must revise their manuscripts according to reviewers’ and editors’ comments within the specified period.
17. Data, Software, and Reproducibility
Authors are encouraged to provide sufficient information about datasets, software, hardware, experimental configuration, source code, and testing procedures to support transparency and reproducibility.
Where possible, authors may provide links to datasets, repositories, documentation, or supplementary materials. However, sensitive data, security vulnerabilities, user information, and private institutional data must be protected according to ethical and legal requirements.
Authors should clearly describe any limitations related to data access, software availability, system environment, or experimental constraints.
18. Use of Artificial Intelligence Tools
Authors may use AI-assisted tools for grammar checking, language editing, translation support, formatting assistance, or coding support where appropriate. AI tools must not replace the authors’ intellectual contribution, technical analysis, data interpretation, or responsibility for the manuscript.
If AI tools are used in preparing the manuscript, authors must disclose their use in a declaration statement. Authors remain fully responsible for the accuracy, validity, originality, and ethical integrity of all manuscript content.
Suggested declaration: During the preparation of this manuscript, the author(s) used [name of tool/service] for [purpose]. After using this tool, the author(s) reviewed, revised, and approved the content and take full responsibility for the final manuscript.
19. Copyright and License
Authors retain the copyright of their work while granting RESKOM the right of first publication. Published articles may be read, downloaded, cited, shared, and used for academic and educational purposes with proper acknowledgment of the original source.
License: Articles are distributed under the journal’s open access policy. Authors and readers must properly cite the author(s), article title, journal name, and publication source when using published works.
20. Submission Preparation Checklist
Before submitting the manuscript, authors should ensure that:
- The manuscript fits the focus and scope of RESKOM.
- The manuscript has not been published or submitted elsewhere.
- The manuscript file is in Microsoft Word, OpenOffice, or RTF format.
- The manuscript follows the official journal template.
- The title, abstract, keywords, tables, figures, equations, and references are complete.
- All citations and references are accurate and consistent.
- The manuscript is free from plagiarism and unethical publication practices.
- Figures, tables, diagrams, and algorithms are placed near the relevant text.
- The manuscript has been proofread for grammar, clarity, and technical accuracy.
- All required declarations have been prepared where applicable.







