Author Guidelines

Sistem Informasi, Teknik dan Teknologi Terapan
E-ISSN: 3032-3991 | P-ISSN: 3090-1626

Template rules you must follow throughout (from the SITEKNIK template):

  • Language: English/Bahasa Indonesia
  • Manuscript length: 8–10 pages (A4).
  • Margins: Top 1 cm, Bottom 1 cm, Left 3 cm, Right 3 cm.
  • Font & spacing: Times New Roman, 12 pt, single spacing.
  • Main section headings: ALL CAPS, 12 pt (e.g., INTRODUCTION; METHODS; RESULTS AND DISCUSSION; CONCLUSIONS AND SUGGESTIONS; ACKNOWLEDGMENTS; REFERENCES).
  • Plagiarism: ≤ 15%.
  • Abstract: English; 150–200 words, single spacing, one column, text indented 3 cm inward from the main margins; include background, objectives, novelty, benefits, methods, and results.
  • Keywords: 3–5 words/phrases.
  • Tables: Title above the table, bold 12 pt, centered; Table 1, Table 2, …; table content 10 pt; data source (if any) below the table in 10 pt, centered.
  • Figures: Image centered; title below the figure, bold 12 pt; include source if adapted/quoted.
  • Equations: Use Equation Editor/MathType; left-aligned equation; number on the right in parentheses (e.g., (1)).
  • References: APA 7th; ≥ 20 recent references (last 5 years); only those cited in the manuscript; use tools such as Mendeley/Zotero.

INTRODUCTION

Purpose of the section: Establish the problem context, summarize the state of the art, identify the research gap, state the aim(s)/research questions (and hypotheses, if any), and articulate the novelty, contributions, and benefits of the study.

Template constraints: Do not include any tables, figures, or raw equations in the INTRODUCTION.

What to include (mandatory content)

  1. Context & Motivation (2–3 paragraphs)

    • Define the practical and/or theoretical problem space within information systems, engineering, or applied technology.
    • Explain why the topic matters now (e.g., industry demand, societal relevance, measurable performance gaps).
    • Keep it narrative; avoid dumping numbers or instrument-level details (those belong in METHODS or RESULTS).

  2. Concise State of the Art (1–2 paragraphs)

    • Synthesize—not list—the most relevant recent studies (≤ 5 years).
    • Highlight common findings, dominant approaches, and limitations that persist.

  3. Research Gap & Problem Statement (1 strong paragraph)

    • Move from “what is known” to “what is not yet adequately answered.”
    • State the specific gap your study addresses (methodological, contextual, dataset-related, theoretical, or performance gap).

  4. Objective(s) / Research Questions / Hypotheses (1 paragraph)

    • Declare the primary objective(s) clearly (e.g., “to design and evaluate…”, “to quantify…”, “to compare…”).
    • Optionally add RQs or hypotheses if appropriate to your design.

  5. Novelty & Contributions (1 paragraph)

    • Specify what is new (method, metric, architecture, dataset, evaluation protocol, context) and why it matters.
    • Make contributions auditable (e.g., “a reproducible pipeline…”, “an ablation that isolates…”).

  6. Benefits / Expected Impact (1 paragraph)

    • Articulate expected theoretical (knowledge advance) and practical (design/policy/engineering) benefits.

  7. Scope & Boundaries (optional, 1 short paragraph)

    • Define what you do and do not cover to manage reader expectations.

Recommended paragraph order

  • ¶1–2: Background & significance
  • ¶3: Mini literature synthesis
  • ¶4: Gap & problem statement
  • ¶5: Aim(s)/RQs/Hypotheses
  • ¶6: Novelty & contributions
  • ¶7: Benefits (+ optional scope)

Style cues (examples)

  • “While prior studies have demonstrated X in context Y, little is known about Z under realistic constraints C.”
  • “Accordingly, this study aims to …, and contributes by ….”

Quality checklist for INTRODUCTION

  • No tables/figures/equations.
  • Gap and objective(s) are explicit and traceable to the literature.
  • Novelty and benefits are clearly stated, not implied.
  • Tone is concise, cohesive, and forward-linked to METHODS.

METHODS (Research Methodology)

Purpose of the section: Provide a replicable description of how the study was performed—design, setting/sample or dataset, variables/measures, instruments, procedures/workflow, analyses, and method-bound limitations.

Template alignment: Narrative form; avoid overly granular step‑by‑step manuals. You may use tables (10 pt content; caption above, bold 12 pt, centered, numbered) and figures (caption below, bold 12 pt) in METHODS. Equations are allowed here; format them left-aligned and number on the right (Equation Editor/MathType).

What to include (required subsections)

  1. Research Design

    • Identify the design (e.g., experimental, quasi-experimental, survey, case study, design & development, data-driven/ML, benchmarking).
    • Justify why this design best addresses your aim/RQs and gap.

  2. Setting, Population/Sample, or Dataset

    • Context (industry/organization/system/platform).
    • Population & sampling method (probability vs. non-probability), sample size, and inclusion/exclusion criteria; or, for secondary data, dataset origin, collection window, licensing/permissions.
    • Ethics when applicable (informed consent, anonymization, IRB/ethics approval ID).

  3. Variables/Parameters & Measures

    • Define each construct/variable (independent, dependent, control) operationally.
    • Measurement instruments: give sources, scales, and evidence of reliability/validity (e.g., Cronbach’s α, CFA fit indices), or evaluation metrics for systems/ML (accuracy, F1, AUC, RMSE, MAPE, latency, throughput, resource usage).

  4. Procedures / Workflow

    • Data acquisition → cleaning → preprocessing/feature engineering → modeling/implementation → validation/testing.
    • Provide a flow diagram if helpful (caption below, bold 12 pt).
    • If you introduce formulas, use Equation Editor/MathType; e.g.: 
      y = f(X; θ)                                                     (1)
      Explain any symbols not yet defined in a brief sentence following the equation (per template guidance).

  5. Data Analysis Techniques

    • Statistical examples: normality checks; t‑tests/ANOVA; regression; post‑hoc; effect sizes; α level; CIs/p‑values; assumptions and diagnostics.
    • Computational/ML examples: model/architecture, hyperparameters, training/validation/test split (k‑fold, holdout), baselines, ablation protocol, early stopping, seeds, hardware.
    • Systems/Engineering examples: test plan, functional/non‑functional metrics, benchmarking scenarios, workload profiles.

  6. Assumptions & Method‑Bound Limitations

    • State key assumptions (e.g., i.i.d., stationarity, linearity) and methodological constraints (e.g., sampling frame, sensor precision).

  7. Reproducibility & Artifacts (recommended)

    • Software versions, libraries, OS/hardware, parameter settings; optional link to code/data (if policy allows).

Quality checklist for METHODS

  • Design fits the aim/RQs.
  • Sample/dataset is transparent and ethical.
  • Measures/metrics are defined and justified.
  • Workflow is coherent; equations formatted per template.
  • Analysis plan is appropriate; assumptions stated.
  • Any tables/figures follow SITEKNIK caption and font rules.

RESULTS AND DISCUSSION

Purpose of the section: Present the analysis outcomes (not raw dumps) and interpret them against your aims and the literature. SITEKNIK allows tables and figures here, but each must be explained and contextualized.

A. Results (What to present)

  1. Align with your aims/RQs

    • Structure results in the same logical order as your objectives or hypotheses.

  2. Use tables/figures to summarize—not to dump raw data

    • Tables: caption above (bold 12 pt, centered), numbered (Table 1, Table 2, …), content 10 pt, source below if adapted (10 pt, centered). Keep a single page if possible; if continued, repeat header cues.
    • Figures: centered; caption below (bold 12 pt), high‑quality (readable in grayscale if needed); include source if adapted.

  3. Report statistics and metrics clearly

    • Provide units, measures of uncertainty (SD/SE/CI), and effect sizes where relevant.
    • Example phrasing:
      “The proposed approach achieved 85.2% accuracy (SD = 1.7%) and F1 = 0.842, outperforming the baseline by +6.5 pp; t(38) = 2.41, p = 0.02, Cohen’s d = 0.78.”

  4. Avoid: listing unprocessed logs, overly detailed console outputs, or screenshots without analytical value.

B. Discussion (How to interpret)

  1. Interpretation relative to aims/RQs

    • Explain what the results mean and why they matter.

  2. Comparison with prior work

    • Identify agreements, improvements, or contradictions with recent studies; reason about causes (data, context, method, scale).

  3. Mechanisms & Explanations

    • Provide technical or theoretical mechanisms behind observed effects.

  4. Implications

    • Theoretical (frameworks, constructs, models).
    • Practical (design guidelines, deployment implications, policy/management choices).

  5. Limitations (Result‑related)

    • Be explicit about threats to validity (internal/external/construct/statistical conclusion) and their potential impact.

  6. Transition to Suggestions

    • Use your observed limitations and implications to frame future work that is meaningful and feasible.

Sub‑sectioning

  • You may break into subsections (e.g., Performance Evaluation, Ablation Study, Usability Testing, Sensitivity Analysis), as long as each subsection maps back to the aims/RQs.

Common pitfalls to avoid

  • Presenting tables/figures without interpretation.
  • Discussion that does not reference the literature.
  • Deviating from the stated aims/RQs.
  • Captions or fonts not matching the template rules.

Quality checklist for RESULTS AND DISCUSSION

  • Results follow aims/RQs order; no raw dumps.
  • Every table/figure is referenced in text and interpreted.
  • Statistics/metrics reported with units and uncertainty.
  • Discussion compares to recent literature and explains why.
  • Limitations are candid and inform future directions.
  • Captions, numbering, and fonts adhere to SITEKNIK template.

CONCLUSIONS AND SUGGESTIONS

Purpose of the section: Summarize what was discovered (no new analysis), emphasize contributions and implications, and offer actionable suggestions for practice and clear directions for future research.

Template requirement: Provide at least two paragraphs for Conclusions and at least two paragraphs for Suggestions.

A. Conclusions (at least 2 paragraphs)

  • Stay aligned with your aims/RQs—mirror them in your concluding statements.
  • Do not introduce new data, statistics, or references.
  • Emphasize contributions (novel methodology, dataset, empirical findings, design insights) and their scope of validity.

Suggested structure:

  1. Paragraph 1 – Summary of Findings
    • Restate the problem and concise key findings (what was achieved, by how much, in which context).
  2. Paragraph 2 – Contributions & Implications
    • Clarify what this means for the field and for practitioners; delineate boundaries/conditions.
  3. (Optional)Paragraph 3 – Boundary Conditions
    • State where the findings are most/least applicable (datasets, domains, scales).

B. Suggestions (at least 2 paragraphs)

Separate practical from research suggestions:

  1. Practical Suggestions

    • Action steps for practitioners, engineers, managers, or policy-makers, directly grounded in your results (e.g., deployment priorities, parameter ranges, governance processes).

  2. Research Suggestions

    • Next steps to address limitations (e.g., larger/more diverse samples, different contexts, longitudinal validation, external replication, additional ablation or benchmarking, alternative metrics).

Example phrasing:

  • “Organizations adopting the proposed workflow should first ensure X, then implement Y, to realize Z improvements.”
  • “Future studies should validate these findings in A and examine B using C metrics.”

Quality checklist for CONCLUSIONS AND SUGGESTIONS

  • No new data/analyses appear in Conclusions.
  • Contributions and implications are explicit.
  • Suggestions are actionable (practice) and researchable (future work).
  • Meets the minimum paragraph counts required by the template.

Captions, Equations, and Symbols – Examples (per template)

  • Table caption (above, bold 12 pt, centered):
    Table 1. Hyperparameter Settings for the Proposed Model
    (Table content in Times New Roman 10 pt; if adapted, place “Source: …” below the table, 10 pt, centered.)

  • Figure caption (below, bold 12 pt, centered):
    Figure 1. System Architecture Overview
    (If adapted, include “Source: Author, Year”. Place figure centered and ensure legibility in grayscale.)

  • Equation (left‑aligned; number on the right):

    L(θ) = ∑i ℓ(yi, f(xi; θ))                                      (2)

    Explain any new symbols right after the equation (e.g., “where ℓ denotes the loss function; f(·; θ) is the model parameterized by θ”).

References (APA 7th) – Reminders

  • Include only sources you actually cite in the manuscript.
  • Ensure ≥ 20recent references (last 5 years) wherever possible.
  • Use tools such as Mendeley or Zotero for consistency.
  • Examples (illustrative formats):
    • Journal article: Author, A. A., & Author, B. B. (Year). Title of the article. Journal Title, volume(issue), page–page. https://doi.org/xxxx
    • Conference proceeding: Author, A. A. (Year). Paper title. In Proceedings of … (pp. xx–xx). Publisher.
    • Book: Author, A. A. (Year). Book title: Subtitle (Edition). Publisher.

Compliance Quicklist (Use before submission)

  • A4, margins 1/1/3/3 cm, TNR 12 pt, single spacing.
  • Headings ALL CAPS 12 pt; sequence: INTRODUCTION → METHODS → RESULTS AND DISCUSSION → CONCLUSIONS AND SUGGESTIONS → ACKNOWLEDGMENTS → REFERENCES.
  • Abstract 150–200 words, one column, 3 cm inward indentation; Keywords: 3–5.
  • Introduction contains no tables/figures/equations and clearly states gap, aim(s)/RQs, novelty, and benefits.
  • Methods: design, sample/dataset, measures/metrics, instruments, workflow, analysis plan, assumptions/limitations; equations formatted correctly; any tables/figures follow caption rules.
  • Results & Discussion: present analysis (not raw data); interpret and compare to literature; include implications and limitations.
  • Conclusions (≥2 paragraphs) and Suggestions (≥2 paragraphs) meet scope; no new data.
  • References: APA 7th; ≥ 20 recent sources (≤ 5 years); only cited items.
  • Total length within 8–10 pages; plagiarism ≤ 15%.