Skip to main content
CBE Nexus · Undergraduate Information Systems · Chapter 15

Research Methods and Information Systems Strategy

University-level study of research design, scholarly evidence, data collection and analysis, ethics, professional practice and evidence-based information systems decisions.

Course guide

Learning outcomes

After studying this chapter, learners should be able to formulate research problems and objectives; conduct a critical literature review; select and justify a research paradigm and design; apply quantitative, qualitative and mixed methods; select samples; collect and analyse data; assess validity, reliability and trustworthiness; protect participants and research data; prepare a proposal or dissertation; and demonstrate ethical professional practice.

Study approach: Use a real information systems issue as a running example. Move from the problem to research questions, evidence, design, analysis and recommendations. Keep a research journal documenting decisions and assumptions.

Important: Follow your institution's current research handbook, ethics review process, data protection requirements and referencing style. This chapter provides academic guidance, not a substitute for institutional approval or legal advice.

Research process

RESEARCH CONTEXT / PRACTICAL PROBLEM
                 |
                 v
       PROBLEM AND QUESTIONS
                 |
                 v
      LITERATURE + FRAMEWORK
                 |
                 v
       DESIGN + ETHICS REVIEW
                 |
                 v
    SAMPLING AND DATA COLLECTION
                 |
                 v
       ANALYSIS AND INTERPRETATION
                 |
                 v
       CONCLUSIONS / CONTRIBUTION
                 |
                 v
     DISSEMINATION AND REFLECTION
                 |________________
                    iteration
Figure 15.1: A research process is systematic but iterative; findings may refine questions and conceptual understanding.

1. Nature and purpose of information systems research

Information systems research investigates the relationships among people, organisations, processes, data and technologies. It asks how information systems are designed, adopted, governed and used, and how they influence organisational and social outcomes. The field is interdisciplinary: it draws on computer science, management, economics, psychology, sociology, design, law and statistics. A research problem may concern a technical artefact, a human behaviour, an organisational practice or the interaction among these elements.

Research is more than collecting opinions or describing a technology. It is a systematic inquiry guided by a question, a defensible method, transparent evidence and reasoned interpretation. A study should explain what is known, what remains uncertain, why the question matters, how evidence was obtained and what conclusions the evidence can support. The method must fit the question rather than being selected merely because it is familiar.

Information systems research can be explanatory, exploratory, descriptive, evaluative, predictive or design-oriented. Explanatory work investigates why a phenomenon occurs; exploratory work develops understanding where knowledge is limited; descriptive work characterises a situation; evaluative work judges an intervention against criteria; predictive work estimates future outcomes; and design-oriented work creates and evaluates an artefact or method.

Research quality depends on coherence among the problem, literature, conceptual framework, method, analysis and claims. A large sample cannot rescue a poorly defined construct, and sophisticated software cannot compensate for biased sampling. Researchers should make limitations explicit and distinguish evidence-based findings from assumptions, speculation and recommendations.

Research application: In a practical assignment, connect this topic to a clearly bounded information systems problem. State the assumptions you are making, identify the evidence that would challenge your interpretation and explain how another researcher could assess the quality of your decisions.

2. Research problems, questions and objectives

A research problem identifies a meaningful gap between a current state and a desired understanding or outcome. It may arise from operational failure, conflicting findings, a new technology, a policy change or an unanswered scholarly question. A good problem is specific enough to investigate, significant enough to justify effort and feasible within available time, access, skills and resources.

The problem statement should establish context, describe the issue using evidence, identify who or what is affected, explain consequences and show what knowledge is missing. Avoid presenting a solution as though it were the problem. For example, 'the institution needs a mobile application' assumes an answer; 'students experience delays accessing registration information across fragmented channels' defines a problem that can be investigated through several possible interventions.

Research questions translate the problem into answerable inquiries. Questions may ask what, how, why, to what extent or under what conditions. Objectives state the specific tasks required to answer them, such as identifying user needs, measuring system availability, comparing adoption factors or evaluating a prototype. Each objective should map to a method and an expected form of evidence.

Scope delimitations identify what the study includes and excludes, such as a particular institution, user group, process, period or system. Researchers should justify these boundaries and avoid generalising beyond them. A concise set of aligned questions and objectives is usually stronger than a long list of loosely connected ambitions.

Research application: In a practical assignment, connect this topic to a clearly bounded information systems problem. State the assumptions you are making, identify the evidence that would challenge your interpretation and explain how another researcher could assess the quality of your decisions.

4. Theoretical and conceptual frameworks

A theory is a structured explanation of relationships among concepts. In information systems, theories may explain technology acceptance, organisational change, social influence, task-technology fit, information quality, trust or institutional behaviour. A theoretical framework uses an established theory to guide a study's concepts, hypotheses and interpretation.

A conceptual framework is a reasoned representation of the key constructs and proposed relationships relevant to a particular study. It may be derived from one or more theories, prior evidence or a design model. A framework should clarify assumptions and relationships rather than simply decorate a proposal with boxes and arrows.

Constructs are abstract concepts such as perceived usefulness, trust, service quality or organisational readiness. Variables are operational representations that can be observed or measured. Researchers must define constructs conceptually and operationally. If 'system success' is measured only by login counts, important dimensions such as task quality, reliability and user outcomes may be missed.

Framework selection should be justified by fit to the research question, context and evidence. Researchers should not force a theory onto a problem because it is popular. They should also recognise boundary conditions: a model developed in one country, sector or technology context may not transfer unchanged to another.

Research application: In a practical assignment, connect this topic to a clearly bounded information systems problem. State the assumptions you are making, identify the evidence that would challenge your interpretation and explain how another researcher could assess the quality of your decisions.

5. Research paradigms and philosophical assumptions

Research paradigms express assumptions about reality, knowledge and how it can be studied. Ontology concerns what exists and the nature of reality; epistemology concerns what counts as knowledge and how it can be justified; axiology concerns the role of values; and methodology concerns the overall logic of inquiry. These assumptions influence question design, data collection and interpretation.

Positivist approaches commonly seek patterns, relationships and explanations through observable measures and structured testing. Interpretivist approaches seek to understand meaning and experience in context. Critical approaches examine power, inequality, ideology and structures that shape technology and work. Pragmatism focuses on the research problem and uses methods that provide useful, defensible answers.

These positions are not simplistic labels for quantitative and qualitative techniques. A quantitative study can investigate meaning through structured measures, while qualitative research can be conducted within different philosophical positions. Researchers should explain their assumptions and how those assumptions shape the study rather than treating paradigms as rigid checklists.

Mixed-methods research can integrate numerical patterns and contextual explanations. It is valuable when different forms of evidence answer complementary parts of a question. Integration must be planned: researchers should state which method has priority, how strands connect, how contradictory findings will be examined and what additional insight the combination provides.

Research application: In a practical assignment, connect this topic to a clearly bounded information systems problem. State the assumptions you are making, identify the evidence that would challenge your interpretation and explain how another researcher could assess the quality of your decisions.

6. Quantitative research design

Quantitative research uses numerical observations and statistical analysis to describe patterns, estimate relationships, test hypotheses or evaluate effects. Common designs include descriptive surveys, correlational studies, experiments, quasi-experiments, longitudinal studies and secondary-data analysis. Design choice depends on the causal claim, feasibility, ethical constraints and data structure.

An experimental design manipulates an independent variable and observes an outcome while controlling alternative explanations. Random assignment helps balance known and unknown confounders. A quasi-experiment evaluates an intervention without full random assignment and may use comparison groups, interrupted time series or difference-in-differences reasoning. Observational correlation alone does not establish causation.

Cross-sectional studies measure variables at one point in time and can estimate prevalence or associations, but often cannot establish temporal order. Longitudinal studies observe change over time and may clarify sequence, though attrition and changing conditions create challenges. Repeated measures require appropriate analysis because observations from the same participant are not independent.

Quantitative plans should specify population, sampling frame, sample size rationale, measures, data collection protocol, missing-data strategy and analysis plan. Researchers should predefine primary outcomes where possible and avoid changing hypotheses after inspecting results without disclosure. Transparent reporting helps readers judge robustness and reproducibility.

Research application: In a practical assignment, connect this topic to a clearly bounded information systems problem. State the assumptions you are making, identify the evidence that would challenge your interpretation and explain how another researcher could assess the quality of your decisions.

7. Qualitative research design

Qualitative research explores meanings, experiences, practices and processes using rich contextual evidence. Common approaches include case study, ethnography, phenomenology, grounded theory, narrative inquiry and qualitative content analysis. Each approach has a different purpose; the researcher should select one that fits the question and explain how data and interpretation will be developed.

Interviews may be structured, semi-structured or open-ended. Semi-structured interviews use a guide while allowing probing and clarification. Focus groups explore interaction and shared or contested views, but group dynamics may suppress minority opinions. Observation can reveal actual work practices, informal rules and workarounds that participants may not recall or disclose.

Sampling is usually purposive, selecting participants with relevant experience or perspectives. Maximum-variation sampling seeks diversity; theoretical sampling develops emerging concepts; snowball sampling reaches hard-to-access networks. Sample adequacy depends on the research purpose, richness of evidence and analytic approach rather than a universal number.

Qualitative rigour can be supported through reflexive notes, transparent coding, triangulation, thick description, negative-case analysis, participant feedback where appropriate and an audit trail. Researchers should not claim that one technique automatically proves truth. They should explain how interpretations were developed and consider alternative explanations.

Research application: In a practical assignment, connect this topic to a clearly bounded information systems problem. State the assumptions you are making, identify the evidence that would challenge your interpretation and explain how another researcher could assess the quality of your decisions.

8. Mixed-methods research

Mixed-methods research intentionally combines quantitative and qualitative strands within one study. A convergent design collects both forms of data in a similar period and compares or integrates results. An explanatory sequential design begins with quantitative results and follows with qualitative inquiry to explain patterns. An exploratory sequential design begins qualitatively and uses findings to develop measures or test a model.

Integration may occur at design, sampling, data collection, analysis or interpretation. For example, survey results may identify departments with low system adoption, while interviews explore workload, training and trust as possible explanations. The strands should be connected by a clear rationale rather than simply placing a questionnaire and interviews in the same project.

Mixed-methods studies require adequate competence and resources for each strand. Researchers must consider different sampling logics, timing, data management and possible contradictions. A qualitative explanation that conflicts with an aggregate survey result may reveal subgroup differences or measurement problems rather than invalidating one strand.

Joint displays can place numerical results alongside themes and interpretations. The final report should state where evidence converges, complements or diverges. The contribution of the design is the additional understanding produced by integration, not merely the number of methods used.

Research application: In a practical assignment, connect this topic to a clearly bounded information systems problem. State the assumptions you are making, identify the evidence that would challenge your interpretation and explain how another researcher could assess the quality of your decisions.

9. Sampling strategies and sample size

The target population is the full group about which a study seeks to draw conclusions. An accessible population is the portion realistically reachable, while a sampling frame is the list or mechanism from which units are selected. Coverage errors occur when the frame omits or duplicates members of the target population. Researchers should explain how these limitations affect inference.

Probability sampling gives units a known chance of selection. Simple random sampling selects randomly from a complete frame; systematic sampling selects at regular intervals after a random start; stratified sampling ensures representation of defined subgroups; and cluster sampling selects naturally occurring groups. These methods can support statistical inference when assumptions and implementation are sound.

Non-probability sampling includes convenience, purposive, quota and snowball methods. It can be appropriate for exploratory, qualitative or hard-to-reach populations, but selection probabilities are unknown and population generalisation is limited. A large convenience sample does not automatically represent a population.

Sample size depends on the study design, expected effect, variability, desired precision, confidence level, power, number of predictors, clustering, non-response and practical constraints. Researchers should use an appropriate calculation or rationale rather than a universal rule such as 'ten per cent of the population'. Qualitative sample size should be justified by depth, purpose and analytic sufficiency.

Research application: In a practical assignment, connect this topic to a clearly bounded information systems problem. State the assumptions you are making, identify the evidence that would challenge your interpretation and explain how another researcher could assess the quality of your decisions.

10. Questionnaires and survey measurement

A questionnaire translates research constructs into questions and response options. It should use clear language, one idea per item, neutral wording, suitable response scales and an order that supports comprehension. Double-barrelled questions, leading wording, unexplained technical terms and unnecessary demographic questions can undermine data quality.

Closed questions simplify coding and comparison, while open questions allow respondents to express unanticipated views. Likert-type items measure agreement or frequency, but researchers should define the response anchors and consider whether a neutral option is appropriate. A multi-item scale may capture a complex construct more reliably than a single question.

Questionnaire development includes mapping items to constructs, expert review, cognitive interviewing and piloting. A pilot checks completion time, confusing wording, missing response options, routing, device compatibility and data export. Pilot participants should resemble the intended population, but pilot data should not be silently merged with the main sample if the instrument changes materially.

Response rate is not a direct measure of representativeness. Non-response bias occurs when respondents differ systematically from non-respondents on relevant characteristics. Researchers can improve response through accessible design, clear purpose, appropriate reminders and trusted distribution, while avoiding coercion or excessive incentives.

Research application: In a practical assignment, connect this topic to a clearly bounded information systems problem. State the assumptions you are making, identify the evidence that would challenge your interpretation and explain how another researcher could assess the quality of your decisions.

11. Interviews, observation and focus groups

Interview protocols should begin with an explanation of purpose, consent, confidentiality limits and recording arrangements. Questions should be open and neutral, progressing from accessible context to specific experiences. Probes such as 'Can you describe an example?' help obtain concrete evidence. Interviewers should avoid leading participants toward the researcher's preferred explanation.

Observation can be participant or non-participant, structured or open. Researchers may observe task sequences, interruptions, handoffs, tool use and workarounds. Field notes should distinguish direct observation from interpretation. Access permissions, privacy, safety and the observer's influence on behaviour need consideration.

Focus groups typically involve a small group discussing a defined topic under a facilitator. They can reveal shared vocabulary and differences in perspective. The facilitator should manage dominant voices, invite quieter participants and avoid implying that group comments are confidential beyond the researcher's control. Sensitive topics may be better explored individually.

Audio recordings and transcripts must be handled securely. Transcription conventions should be appropriate to the analysis: exact speech may matter for discourse analysis, while cleaned transcripts may be adequate for thematic analysis. Researchers should document edits, anonymisation and translation decisions.

Research application: In a practical assignment, connect this topic to a clearly bounded information systems problem. State the assumptions you are making, identify the evidence that would challenge your interpretation and explain how another researcher could assess the quality of your decisions.

12. Case study and action research

A case study investigates a contemporary phenomenon in its real-life context, particularly where the boundary between phenomenon and context is not clear. Cases may be single or multiple, holistic or embedded. Data can include interviews, documents, observations, system logs and artefacts. The case boundary, selection rationale and unit of analysis must be explicit.

Multiple-case research can compare settings and identify patterns, but cases are not equivalent to a random sample. Analytical generalisation connects findings to concepts or theory rather than claiming statistical representativeness. Researchers should consider rival explanations and preserve a chain of evidence from source material to conclusions.

Action research combines inquiry with deliberate action to address a practical problem. A cycle may involve diagnosing, planning, acting, observing and reflecting. Participants contribute to defining the issue and evaluating change. Researchers must manage their dual role as investigator and change agent, including power, consent and the possibility that intervention affects evidence.

Action research can produce practical improvement and transferable insight, but claims should acknowledge context and researcher involvement. Documentation of decisions, iterations and unintended consequences is essential. A successful intervention in one organisation does not prove that the same solution will work everywhere.

Research application: In a practical assignment, connect this topic to a clearly bounded information systems problem. State the assumptions you are making, identify the evidence that would challenge your interpretation and explain how another researcher could assess the quality of your decisions.

13. Design science research and artefact evaluation

Design science research creates and evaluates an artefact intended to solve an identified problem or improve a capability. Artefacts may include constructs, models, methods, processes, architectures or software instantiations. The research contribution is not simply that a system was built; it must explain the problem, design rationale, novelty or adaptation and evidence of utility.

A disciplined process identifies the problem and motivation, defines objectives, designs and develops the artefact, demonstrates it in a relevant setting, evaluates it and communicates results. Iteration is expected. Evaluation may include experiments, usability tests, technical benchmarks, expert assessment, field deployment or analytical comparison.

Design requirements should be derived from stakeholder needs and relevant knowledge. Trade-offs among usability, security, performance, cost, maintainability and fairness should be explicit. A prototype that performs well in a laboratory may fail under real workload, connectivity or organisational constraints.

Evaluation criteria should be specified before results are known where possible. Researchers should report context, participants, test data, baseline, metrics, limitations and failures. Negative results and design limitations can be valuable contributions because they identify boundary conditions and prevent unsupported claims.

Research application: In a practical assignment, connect this topic to a clearly bounded information systems problem. State the assumptions you are making, identify the evidence that would challenge your interpretation and explain how another researcher could assess the quality of your decisions.

14. Data collection, provenance and quality assurance

Data collection plans specify what evidence is required, from whom or what, by which instrument, at what time and under what conditions. Operational definitions and standard procedures improve consistency. Researchers should pilot collection procedures and train assistants so that variation in administration does not become an uncontrolled source of error.

Data provenance records origin, collection method, transformation, ownership and access history. For system log analysis, researchers should document event definitions, time zones, missing events, retention filters and changes to production systems. For surveys, they should record recruitment routes, field dates, instrument versions and response handling.

Quality checks may include range validation, duplicate detection, consistency rules, timestamp checks, missingness analysis, outlier review and audit sampling. Cleaning decisions should be documented and, where possible, performed through reproducible scripts. Researchers should preserve an untouched source copy and work on controlled derived datasets.

Data quality is contextual. An outlier may be an error or a meaningful unusual event; deleting it without investigation can distort findings. Missing values may arise from non-response, system failure or a question that does not apply. The treatment should be justified and tested through sensitivity analysis when it could change conclusions.

Research application: In a practical assignment, connect this topic to a clearly bounded information systems problem. State the assumptions you are making, identify the evidence that would challenge your interpretation and explain how another researcher could assess the quality of your decisions.

15. Quantitative data analysis and descriptive statistics

Descriptive statistics summarise the observed dataset. Frequencies and percentages describe categories; the mean summarises arithmetic average; the median is the middle value; and the mode is the most frequent value. Range, variance, standard deviation and interquartile range describe dispersion. Choice of summary should reflect measurement level and distribution.

Visualisation helps identify patterns and anomalies. Bar charts suit categories, histograms show numerical distributions, box plots summarise spread and potential outliers, and scatter plots examine relationships between two numerical variables. Axes, units, sample size and definitions should be clear. Avoid misleading scales or decorative complexity.

Suppose 80 users report task completion times with a mean of 12 minutes and a standard deviation of 3 minutes. The mean describes the average in this sample, while the standard deviation indicates variation around it. It does not imply that every user completes the task between 9 and 15 minutes; distributional assumptions matter.

Researchers should distinguish sample statistics from population parameters and describe uncertainty. A confidence interval gives a range generated by a method that, under its assumptions, would cover the true parameter at the stated long-run rate. It is not a probability statement about a fixed parameter after the interval has been observed.

Research application: In a practical assignment, connect this topic to a clearly bounded information systems problem. State the assumptions you are making, identify the evidence that would challenge your interpretation and explain how another researcher could assess the quality of your decisions.

16. Inferential statistics and hypothesis testing

Inferential statistics use sample data to estimate population quantities or assess hypotheses. A null hypothesis commonly represents no effect or no association, while an alternative expresses the effect or relationship of interest. The significance level is a preselected threshold for controlling the long-run Type I error rate under the test assumptions.

A p-value is the probability, assuming the null model and its assumptions, of obtaining results at least as incompatible with that model as the observed result. It is not the probability that the null hypothesis is true, nor a measure of practical importance. Statistical significance should be interpreted with effect size, uncertainty and context.

Type I error is rejecting a true null hypothesis; Type II error is failing to reject a false null hypothesis. Statistical power is the probability of detecting a specified effect under assumptions when that effect exists. Larger samples can improve power but do not correct measurement bias, confounding or poor design.

Test selection depends on design, scale, distribution and assumptions. Examples include t-tests for certain mean comparisons, chi-square tests for categorical associations, correlation for association between variables and regression for modelling outcomes. Researchers should report test statistics, degrees of freedom where relevant, effect sizes, confidence intervals and assumption checks.

Research application: In a practical assignment, connect this topic to a clearly bounded information systems problem. State the assumptions you are making, identify the evidence that would challenge your interpretation and explain how another researcher could assess the quality of your decisions.

17. Regression, prediction and causal interpretation

Regression models describe relationships between an outcome and one or more predictors. Linear regression estimates a conditional mean for a continuous outcome under assumptions; logistic regression models the probability of a binary outcome; and other model families address counts, time-to-event or hierarchical data. Model choice should follow the data-generating process and research question.

Regression coefficients require careful interpretation. In a linear model, a coefficient represents the expected change in the outcome for a one-unit predictor increase, holding included predictors constant, under the model specification. In logistic regression, coefficients are on the log-odds scale and are often transformed into odds ratios for interpretation.

Prediction and explanation are different goals. A model can predict well without identifying causal effects. Confounding, reverse causation, selection bias and omitted variables can distort observational relationships. Causal claims require a defensible design and assumptions, not merely a statistically significant coefficient.

Model evaluation should consider residuals, calibration, discrimination where relevant, overfitting, data leakage, external validity and subgroup performance. Train-test separation or cross-validation helps estimate predictive performance, but test data must represent the intended deployment context. Researchers should disclose preprocessing and tuning decisions.

Research application: In a practical assignment, connect this topic to a clearly bounded information systems problem. State the assumptions you are making, identify the evidence that would challenge your interpretation and explain how another researcher could assess the quality of your decisions.

18. Qualitative coding and thematic analysis

Qualitative analysis begins with familiarisation: reading or listening repeatedly, noting initial ideas and understanding the context. Coding assigns labels to meaningful segments of data. Codes may be inductive, developed from the material, or deductive, informed by a framework. Researchers should define codes and record examples to support consistent interpretation.

Thematic analysis develops patterns of shared meaning across a dataset. A typical process includes familiarisation, coding, generating candidate themes, reviewing themes, defining and naming themes, and writing an evidence-based account. Themes should express an analytic idea rather than simply repeat interview questions or broad subject labels.

Researchers should examine variation and negative cases. A theme such as 'staff resist the new system' may conceal differences between workload concerns, accessibility problems, distrust of management and lack of training. More precise analysis explains mechanisms and context rather than attributing every difficulty to attitude.

Software can support coding, retrieval, memoing and audit trails, but it does not perform interpretation automatically. Researchers remain responsible for the analytic decisions. Quotations should be selected to illustrate claims without exposing identities, and translation or editing should preserve meaning.

Research application: In a practical assignment, connect this topic to a clearly bounded information systems problem. State the assumptions you are making, identify the evidence that would challenge your interpretation and explain how another researcher could assess the quality of your decisions.

19. Validity, reliability, credibility and trustworthiness

Validity concerns whether a measure or inference supports the interpretation being made. Content validity asks whether a measure adequately covers the construct; construct validity examines whether it behaves as theory predicts; and criterion validity compares it with an appropriate external criterion. Internal validity concerns causal inference, while external validity concerns transfer to other settings or populations.

Reliability concerns consistency of measurement. Internal consistency may be assessed for multi-item scales, but a high coefficient does not prove that a scale measures the intended construct. Test-retest reliability examines stability over time where stability is expected; inter-rater reliability examines agreement among observers or coders.

Qualitative researchers often discuss credibility, dependability, confirmability and transferability. These can be supported through transparent procedures, contextual description, reflexive practice, triangulation and an audit trail. The techniques should fit the epistemological position and should not be presented as mechanical guarantees of truth.

Threats include selection bias, measurement error, maturation, history effects, instrumentation changes, researcher influence, social desirability and attrition. A strong report identifies plausible threats and explains what was done to reduce them. It should not claim that a study is free of bias.

Research application: In a practical assignment, connect this topic to a clearly bounded information systems problem. State the assumptions you are making, identify the evidence that would challenge your interpretation and explain how another researcher could assess the quality of your decisions.

20. Research ethics and responsible conduct

Ethical research respects autonomy, minimises harm, promotes fairness and protects participants' rights and dignity. Researchers should obtain informed consent where required, explain purpose and procedures, describe foreseeable risks, clarify voluntary participation and explain withdrawal conditions. Consent must be understandable and free from undue pressure.

Privacy and confidentiality are related but different. Privacy concerns appropriate access to people and their information; confidentiality concerns how entrusted information is protected. Anonymisation removes identifying links, while pseudonymisation replaces direct identifiers but retains a re-identification key. Small groups and distinctive quotations may remain identifiable even after names are removed.

Research involving employees, students, patients or dependent groups requires attention to power relationships. A lecturer recruiting students or a manager recruiting staff must avoid coercion and protect people from perceived consequences of refusal. Incentives should compensate reasonably without exerting undue influence.

Ethical review should occur before data collection when required by institutional policy or law. Researchers must report adverse events, protocol changes and conflicts of interest. Fabrication, falsification, plagiarism, undisclosed manipulation and selective reporting undermine the research record. Responsible conduct includes accurate attribution, honest reporting and secure data management.

Research application: In a practical assignment, connect this topic to a clearly bounded information systems problem. State the assumptions you are making, identify the evidence that would challenge your interpretation and explain how another researcher could assess the quality of your decisions.

21. Privacy, cybersecurity and research data management

Research data may contain personal, confidential, commercially sensitive or security-relevant information. A data management plan should define data types, collection, lawful basis, access, storage, backup, sharing, retention, archiving and disposal. The plan should cover raw data, transcripts, code, consent records and derived datasets.

Access should follow least privilege and be reviewed when project roles change. Encryption should protect data in transit and at rest where appropriate. Identifiers should be stored separately from research responses, with keys restricted to authorised personnel. Secure transfer methods should replace ordinary unprotected email attachments for sensitive data.

Researchers should assess cloud storage and research software providers for location, access, subcontractors, retention, incident response and contractual terms. A free tool is not automatically suitable for sensitive data. Backups should be tested, and working files should use version control and documented naming conventions.

Data sharing can improve reproducibility, but openness must be balanced with consent, privacy, intellectual property, security and community expectations. Where raw data cannot be shared, researchers may share metadata, instruments, code, synthetic data or controlled access procedures. Deletion and retention must follow the approved plan and applicable requirements.

Research application: In a practical assignment, connect this topic to a clearly bounded information systems problem. State the assumptions you are making, identify the evidence that would challenge your interpretation and explain how another researcher could assess the quality of your decisions.

22. Citation, referencing and academic integrity

Academic writing distinguishes the researcher's contribution from ideas, evidence and words drawn from others. Citations allow readers to locate sources and assess the basis of claims. A reference list should be complete and consistent with the selected style, such as APA, IEEE, Harvard or another institutional standard.

Paraphrasing requires genuine restatement and citation; changing a few words while retaining the source's structure is not adequate. Direct quotations should be limited, accurately reproduced and clearly marked. Page or section details should be provided where the style requires them. Secondary citations should be avoided when the original source can be consulted.

Plagiarism includes presenting another person's words, ideas, code, figures or data as one's own. Self-plagiarism and duplicate publication may also breach institutional or publisher expectations. Collaboration and use of AI tools should follow course and institutional rules, with disclosure where required.

Reference managers can organise sources, attach metadata and format citations, but imported records may contain errors. Students should verify author names, titles, dates, journal details, page ranges and identifiers. Automated similarity scores are indicators for review, not proof of misconduct or originality.

Research application: In a practical assignment, connect this topic to a clearly bounded information systems problem. State the assumptions you are making, identify the evidence that would challenge your interpretation and explain how another researcher could assess the quality of your decisions.

23. Research proposal and dissertation structure

A research proposal normally introduces the topic, background, problem statement, aim, objectives, questions or hypotheses, significance, scope and limitations. It reviews relevant literature, explains the theoretical or conceptual framework, describes the methodology, addresses ethics and data management, and provides a timetable and references.

A dissertation or research report typically includes an abstract, introduction, literature review, methodology, findings, discussion, conclusion, recommendations and references, with appendices where appropriate. The exact structure depends on discipline and institutional guidance. Each chapter should serve a clear purpose and connect logically to the research questions.

The methodology chapter should explain the design, setting, population, sampling, instruments, procedures, analysis, ethics and quality assurance. It should provide enough detail for readers to assess the study and understand how conclusions were reached. Claims about methods should be supported by appropriate methodological literature.

Findings should be reported accurately before being interpreted. Tables and figures should have clear titles, labels and sources. Discussion relates results to prior literature and theory, explains unexpected findings and considers limitations. Conclusions should answer the research questions without introducing unsupported new evidence.

Research application: In a practical assignment, connect this topic to a clearly bounded information systems problem. State the assumptions you are making, identify the evidence that would challenge your interpretation and explain how another researcher could assess the quality of your decisions.

24. Project planning, time and research resources

Research projects need a realistic work plan covering question refinement, literature review, ethics approval, instrument design, piloting, recruitment, collection, analysis, writing, review and submission. Dependencies matter: data collection should not begin before required approvals, and analysis cannot be completed until data quality is checked.

A Gantt chart displays activities over time and can reveal overlap, dependencies and bottlenecks. Critical path analysis identifies tasks whose delay affects the completion date. Researchers should include contingency for recruitment delays, system access, equipment failure, illness and revision cycles.

Resource planning includes software, connectivity, travel, transcription, participant compensation, secure storage, specialist advice and dissemination. Budgets should distinguish one-off and recurring costs. Free and open-source tools can reduce cost but may require additional configuration, training or maintenance.

Progress reviews should compare planned and actual work, identify blockers and agree corrective actions. Scope changes should be documented and approved where necessary. A project that cannot answer every possible question should prioritise the core research objectives and state exclusions transparently.

Research application: In a practical assignment, connect this topic to a clearly bounded information systems problem. State the assumptions you are making, identify the evidence that would challenge your interpretation and explain how another researcher could assess the quality of your decisions.

25. Research software, reproducibility and version control

Research software may support reference management, survey delivery, qualitative coding, statistical analysis, visualisation, simulation and collaborative writing. Tool selection should consider suitability, accessibility, licensing, privacy, reproducibility, export formats and long-term access. Researchers should understand the operations performed by software rather than treating outputs as unquestionable.

Reproducible analysis uses documented steps so that another researcher can understand and, where data access permits, rerun the workflow. This may include scripts, package versions, environment files, data dictionaries, transformation logs and random seeds. Reproducibility does not guarantee that the original design was valid, but it improves transparency.

Version control records changes to code, documents and analytical scripts. Branching and review workflows can support collaboration and reduce accidental overwrites. Sensitive data and credentials should not be committed to public repositories. Access controls and secret management are essential when using hosted version-control platforms.

Research artefacts should be archived with sufficient metadata, licences and documentation. Software dependencies can become unavailable, so long-term projects may need environment snapshots or containerisation. Researchers should preserve the final analysis version and identify which files correspond to published results.

Research application: In a practical assignment, connect this topic to a clearly bounded information systems problem. State the assumptions you are making, identify the evidence that would challenge your interpretation and explain how another researcher could assess the quality of your decisions.

26. Professional practice and the information systems role

Information systems professionals translate organisational needs into dependable digital capabilities. Their responsibilities may include business analysis, systems analysis, product management, architecture, development, data management, cybersecurity, service management, audit, consulting and research. Each role requires technical competence and the ability to communicate trade-offs to non-specialists.

Professional competence includes keeping skills current, recognising limits, seeking expert advice and making decisions based on evidence. Practitioners should document assumptions, communicate uncertainty and avoid promising outcomes that cannot be supported. They should understand when a system may affect safety, rights, livelihoods or access to essential services.

Professional conduct includes honesty, confidentiality, respect, fairness, accountability and avoidance of conflicts of interest. Practitioners should disclose material risks, report serious defects through appropriate channels and resist pressure to conceal evidence. Ethical responsibility does not disappear when work is delegated to a vendor or automated system.

Professional development can include continuing education, mentoring, communities of practice, standards participation, certifications and reflective portfolios. Credentials may demonstrate structured learning but do not replace judgement or practical experience. Professionals should evaluate the relevance and credibility of training and maintain evidence of applied competence.

Research application: In a practical assignment, connect this topic to a clearly bounded information systems problem. State the assumptions you are making, identify the evidence that would challenge your interpretation and explain how another researcher could assess the quality of your decisions.

27. Consulting, business analysis and stakeholder engagement

Consulting begins with understanding the client's context, objectives, constraints and decision environment. A consultant should agree scope, deliverables, roles, assumptions, confidentiality and escalation routes. The consultant's role is not simply to recommend a preferred product but to help the client make an informed decision.

Business analysis identifies needs and recommends solutions that deliver value to stakeholders. Techniques include interviews, workshops, observation, document analysis, process modelling, user stories, use cases, data analysis and requirements traceability. Requirements should be prioritised and validated with stakeholders who understand the real work.

Stakeholder engagement should include people who operate, support, regulate, purchase, depend on or may be adversely affected by the system. Power mapping helps identify whose views may be overlooked. Facilitators should create safe ways to raise concerns and distinguish genuine consensus from silence or pressure.

Consultants should manage conflicts of interest and disclose vendor relationships, commissions or other incentives that may affect recommendations. Advice should distinguish facts, assumptions and professional judgement. Reports should be understandable, evidence-based and clear about limitations.

Research application: In a practical assignment, connect this topic to a clearly bounded information systems problem. State the assumptions you are making, identify the evidence that would challenge your interpretation and explain how another researcher could assess the quality of your decisions.

28. Communication, technical writing and presentation

Technical communication makes complex systems understandable to the intended audience without removing essential accuracy. A report for executives may emphasise outcomes, risks and decisions; a technical specification requires detailed interfaces, constraints and acceptance criteria; and a user guide should explain tasks in the order users perform them.

Good technical writing uses defined terms, consistent structure, concise sentences, labelled diagrams and traceable requirements. Tables should clarify comparisons rather than repeat paragraphs. Figures need captions and references in the text. Accessibility includes meaningful headings, readable contrast, alternative text and documents that work with assistive technologies.

Presentations should begin with the question or decision the audience needs to understand. Evidence should be selected carefully, uncertainty disclosed and recommendations connected to findings. Avoid overcrowded slides, unexplained acronyms and charts with misleading scales. A clear narrative helps an audience evaluate the reasoning.

Communication is two-way. Practitioners should listen, check understanding, invite questions and adapt explanations to stakeholder knowledge. Meeting records should capture decisions, owners and deadlines. Written confirmation is especially important where requirements, risk acceptance or contractual commitments may later be disputed.

Research application: In a practical assignment, connect this topic to a clearly bounded information systems problem. State the assumptions you are making, identify the evidence that would challenge your interpretation and explain how another researcher could assess the quality of your decisions.

29. Professional standards, codes and continuing development

Professional bodies and standards organisations publish codes, guidance and competency frameworks relevant to information systems. Such guidance can help practitioners consider public interest, competence, confidentiality, integrity and responsible use of technology. The applicable code depends on membership, jurisdiction, employer and project context.

Standards can define processes, terminology, controls, quality expectations or technical interfaces. They may be voluntary, contractually required or incorporated into law and regulation. Practitioners should verify the current edition and scope rather than citing a standard from memory or assuming that certification proves every control is effective.

Continuing professional development should be planned around changing responsibilities and technology. A development plan can identify competency goals, learning activities, practice opportunities and evidence of improvement. Reflection should ask what was learned, how practice changed and what remains uncertain.

Professional accountability includes understanding the limits of one's authority. High-impact decisions may require legal, clinical, safety, privacy, security or domain specialists. Escalating beyond one's competence is a sign of responsible practice, not weakness.

Research application: In a practical assignment, connect this topic to a clearly bounded information systems problem. State the assumptions you are making, identify the evidence that would challenge your interpretation and explain how another researcher could assess the quality of your decisions.

30. Emerging issues in information systems research

Research agendas evolve as technologies and social conditions change. Generative AI, autonomous agents, platform governance, digital identity, algorithmic accountability, privacy-enhancing computation, quantum technologies and cyber-physical systems create new opportunities and risks. Researchers should separate demonstrated capability from marketing claims and speculative forecasts.

AI-assisted research raises questions about authorship, source verification, data confidentiality, fabricated references, bias and reproducibility. Researchers should follow institutional rules, disclose material use where required and verify every substantive claim and citation. AI output is not an authoritative source and cannot take responsibility for scholarly conclusions.

Digital inequality includes differences in connectivity, devices, affordability, language, literacy, disability access and confidence. Studies should avoid treating all users as equally connected or capable. Research design should consider who is excluded by recruitment channels, digital-only instruments or assumptions about technology access.

Responsible future research should engage affected communities, assess environmental and social impacts, share methods transparently where safe and examine distribution of benefits and harms. The significance of an information system is not measured only by technical performance but also by its effects on people and institutions.

Research application: In a practical assignment, connect this topic to a clearly bounded information systems problem. State the assumptions you are making, identify the evidence that would challenge your interpretation and explain how another researcher could assess the quality of your decisions.

Choosing a research approach

                 RESEARCH QUESTION
                         |
        +----------------+----------------+
        |                |                |
   MEASURE / TEST   UNDERSTAND MEANING   BUILD / EVALUATE
        |                |                |
   QUANTITATIVE       QUALITATIVE      DESIGN SCIENCE
        |                |                |
        +----------------+----------------+
                         |
            INTEGRATE WHEN JUSTIFIED
                  MIXED METHODS
                         |
            ETHICS + QUALITY ASSURANCE
Figure 15.2: Research approach should follow the question and intended contribution.

Applied research case studies

Case study 1 — Investigating low adoption of a university learning platform

Context

A university has introduced a learning management system, but some departments use it extensively while others rely on email and paper. Management assumes staff resistance is the main cause and proposes compulsory training.

Research design and response

Define a neutral research problem: variation in adoption and its consequences for teaching and student access. Develop questions about perceived usefulness, ease of use, connectivity, workload, leadership support, training, course design and system reliability. Review technology adoption and task-technology fit literature, then use an explanatory sequential mixed-methods design: survey staff and students, analyse adoption patterns, and interview participants from contrasting departments.

Evidence and safeguards

Use stratified sampling to include faculties, staff roles and student groups. Pilot the questionnaire and ensure that participation is voluntary and responses are not available to line managers in identifiable form. Analyse descriptive patterns and relevant associations, then use interviews to explore unexpected differences. Avoid interpreting correlation as proof that training causes adoption.

Interpretation and lessons

The university may discover that low adoption is driven by poor connectivity, duplicated systems, inadequate instructional design or inaccessible content rather than unwillingness. Recommendations should match evidence and be piloted. The case demonstrates why a research question must not embed a predetermined solution.

Case study 2 — Evaluating a digital records prototype in a county office

Context

A county office wants to replace paper files with an electronic records prototype. Developers report that the prototype is faster, but staff complain that search results are inconsistent and managers are concerned about records retention and access.

Research design and response

Use design science research to define the artefact and its intended contribution. Derive requirements from records officers, service users, ICT staff, legal advisers and information-security personnel. Specify evaluation criteria before testing: retrieval accuracy, task completion time, usability, access control, auditability, retention, backup and recovery.

Evidence and safeguards

Conduct a controlled task-based usability evaluation with representative users and realistic but non-sensitive test records. Use a comparison baseline where feasible. Inspect logs and access rules, test role boundaries and simulate failure and restoration. Collect interview evidence to explain observed difficulties. Ensure test data cannot expose real citizens.

Interpretation and lessons

Report both strengths and defects, including the limits of the test environment. The office should not deploy until retention, migration, security and operational support are validated. The case illustrates that an artefact's technical demonstration is not equivalent to evidence of readiness for public use.

Case study 3 — Researching cybersecurity awareness among employees

Context

An organisation has experienced repeated phishing incidents and wants to measure employee awareness. A proposed study would send deceptive emails without informing staff and publish department-level rankings.

Research design and response

The research team should define the purpose, risks and governance before data collection. Consider whether a less intrusive design can answer the question, such as approved simulation with institutional oversight, anonymous surveys, interviews and aggregate incident metrics. Obtain ethics and organisational approvals, clarify the limits of deception and plan debriefing and support.

Evidence and safeguards

Avoid collecting passwords, unnecessary personal information or identifiable performance data. Protect logs, restrict access, set retention periods and ensure that managers do not use research data for punitive individual ranking. Sampling should include different roles, locations and employment arrangements. The analysis should account for exposure opportunity and role-specific threat context.

Interpretation and lessons

Recommendations should focus on improving reporting, safe verification habits, usable reporting tools and organisational controls rather than blaming individuals. The study should disclose limitations such as simulation realism and self-report bias. The case demonstrates that security research must protect participants and avoid creating the very harm it seeks to prevent.

Case study 4 — Consulting study for a small enterprise system replacement

Context

A small enterprise asks a consultant to recommend a new inventory and accounting platform. A vendor offers a commission to the consultant for recommending its product, while the client has not documented its requirements.

Research design and response

The consultant should disclose the potential conflict and establish an impartial evaluation process. Conduct stakeholder interviews and process observation, document current pain points, data quality, integrations, reporting, compliance and growth needs. Develop prioritised functional and non-functional requirements and agree evaluation criteria with the client.

Evidence and safeguards

Compare options using weighted criteria, demonstrations based on realistic tasks, total cost of ownership, implementation capacity, security, data export and support. Record assumptions and distinguish vendor claims from tested evidence. Include migration, training, downtime and exit costs in the business case.

Interpretation and lessons

The final recommendation should explain alternatives, trade-offs, residual risks and the reason for selection. The consultant should not accept undisclosed incentives. The case demonstrates the professional duties of independence, transparency and evidence-based advice.

Research data lifecycle

PLAN -> COLLECT -> VALIDATE -> STORE SECURELY
 ^                                  |
 |                                  v
REVIEW <- ARCHIVE / DELETE <- ANALYSE / SHARE
        (according to approved plan)
Figure 15.3: Data stewardship spans the entire research lifecycle.

University examination questions and model answers

Questions cover definitions, comparison, research design, calculations, ethical reasoning and professional judgement. In extended answers, justify methodological choices and discuss limitations.

1. Define information systems research and explain its interdisciplinary nature.

Model answer: Information systems research systematically investigates interactions among people, organisations, processes, data and technology. It is interdisciplinary because technical design and use are shaped by management, economics, psychology, sociology, law, design and other fields.

2. Distinguish a research problem, research question, aim and objective.

Model answer: The problem describes the issue or knowledge gap; the question states what the study seeks to answer; the aim expresses the overall purpose; and objectives specify the tasks or milestones required to achieve that aim.

3. Explain the difference between a literature review and an annotated bibliography.

Model answer: An annotated bibliography summarises and comments on individual sources. A literature review synthesises and critically compares evidence across sources, identifies themes and contradictions, evaluates methods and establishes the gap or rationale for a study.

4. Differentiate a theoretical framework from a conceptual framework.

Model answer: A theoretical framework applies established theory to guide concepts and relationships. A conceptual framework is a study-specific representation of relevant constructs and proposed relationships, potentially informed by one or more theories and contextual evidence.

5. Compare positivist, interpretivist and pragmatic research orientations.

Model answer: Positivist approaches often test relationships through systematic observation and measurement; interpretivist approaches examine meaning and context; pragmatism selects and integrates methods according to the research problem and the kind of answer needed.

6. Compare experimental and cross-sectional survey designs.

Model answer: An experiment manipulates an intervention and may use random assignment to support causal inference. A cross-sectional survey measures variables at one time and can describe patterns or associations but usually cannot establish temporal order or causality.

7. When is qualitative research particularly suitable for an information systems study?

Model answer: It is suitable when the study seeks to understand experiences, meanings, work practices, organisational processes or reasons behind behaviour, especially where context and participant perspectives are central.

8. Describe three mixed-methods designs.

Model answer: Convergent designs collect quantitative and qualitative evidence in parallel and integrate them. Explanatory sequential designs use qualitative inquiry to explain quantitative results. Exploratory sequential designs use qualitative findings to develop measures or hypotheses for quantitative testing.

9. Differentiate probability and non-probability sampling.

Model answer: Probability sampling uses known selection probabilities and can support statistical inference under appropriate assumptions. Non-probability sampling selects through methods such as purposive or convenience sampling; it can suit exploratory work but limits population generalisation.

10. A population contains 2,000 records. A researcher selects every 20th record after a random start. Identify the method and expected sample size.

Model answer: This is systematic sampling. Selecting every 20th record gives an approximate sample of 2,000/20 = 100 records, assuming a suitable ordered frame and no problematic periodic pattern.

11. Identify four common questionnaire design errors.

Model answer: Examples include leading questions, double-barrelled items, ambiguous wording, unexplained jargon, unbalanced response scales, missing response options and unnecessary sensitive questions.

12. Explain the difference between interviews, focus groups and observation.

Model answer: Interviews obtain individual accounts and allow probing; focus groups explore group interaction and shared or differing views; observation records behaviour and context directly, including practices participants may not report.

13. What is a case study, and how can multiple cases strengthen analysis?

Model answer: A case study examines a phenomenon in real context. Multiple cases allow comparison and analytical replication across settings, helping identify patterns and boundary conditions, but they do not automatically form a statistically representative sample.

14. Describe the main stages of design science research.

Model answer: Identify and motivate the problem, define solution objectives, design and develop an artefact, demonstrate it, evaluate it and communicate the results. Iteration may occur across stages.

15. State five data quality checks appropriate for a research dataset.

Model answer: Checks may include missing values, duplicate records, valid ranges, inconsistent categories, timestamp and time-zone consistency, outliers, referential integrity and unexpected changes in record counts.

16. A sample has values 4, 6, 6, 8 and 11. Calculate the mean and median.

Model answer: Mean = (4+6+6+8+11)/5 = 35/5 = 7. The ordered middle value is 6, so the median is 6.

17. Explain Type I and Type II errors.

Model answer: Type I error is rejecting a true null hypothesis. Type II error is failing to reject a false null hypothesis. The significance level controls the nominal Type I error rate under assumptions; power is the probability of detecting a specified effect.

18. Why does statistical significance not necessarily imply practical importance?

Model answer: A small effect may be statistically detectable in a large sample but have little real-world value. Interpretation should consider effect size, confidence interval, cost, context and consequences.

19. Distinguish prediction from causal explanation in regression.

Model answer: Prediction estimates outcomes for new observations. Causal explanation seeks to estimate what would happen under an intervention. Predictive accuracy alone does not establish causality because confounding, selection and reverse causation may remain.

20. Describe a defensible thematic analysis workflow.

Model answer: Familiarise with data, generate codes, develop candidate themes, review themes against the dataset, define and name themes, and write an evidence-based account. Record analytic decisions and consider negative cases.

21. Explain validity and reliability in research measurement.

Model answer: Validity concerns whether evidence supports the intended interpretation or construct. Reliability concerns consistency of measurement. A measure can be reliable but invalid if it consistently measures the wrong thing.

22. List key ethical requirements when researching employees or students.

Model answer: Requirements include voluntary informed consent, protection from coercion, confidentiality, privacy, secure data handling, fair recruitment, clear withdrawal conditions, appropriate ethics approval and safeguards against punitive use of responses.

23. Differentiate anonymisation and pseudonymisation.

Model answer: Anonymisation removes identifying links so re-identification is not reasonably possible. Pseudonymisation replaces identifiers with codes but retains a key or other means of re-linking, so the data remain personal data in many legal contexts.

24. What should a research data management plan contain?

Model answer: It should cover data types, collection, lawful basis, ownership, access, storage, encryption, backup, metadata, sharing, retention, archiving, incident response and secure disposal.

25. Identify the major sections of a research proposal.

Model answer: Common sections include title, background, problem statement, aim, objectives, questions or hypotheses, significance, literature review, framework, methodology, ethics, timetable, resources and references.

26. Explain why version control is useful in research.

Model answer: Version control records changes, supports collaboration, allows recovery of earlier work and helps link analytical scripts and documents to reported results. Sensitive data and credentials must be excluded or securely managed.

27. What is a conflict of interest in professional consulting?

Model answer: It occurs when personal, financial or other interests could improperly influence professional judgement or appear to do so. The practitioner should disclose the conflict, manage it transparently and avoid biased recommendations.

28. Discuss the role of continuing professional development in information systems.

Model answer: It maintains competence as technologies, standards, threats and professional responsibilities evolve. Effective development includes applied learning, reflection, mentoring and evidence that new knowledge improves practice.

29. A system usability test has 18 successful task completions out of 24 attempts. Calculate the task success rate.

Model answer: Task success rate = 18/24 × 100 = 75%. The report should also define what counts as success, describe task difficulty and participant characteristics, and examine errors and completion time.

30. Explain why a research report must discuss limitations.

Model answer: Limitations help readers judge the scope and strength of conclusions, understand possible bias and assess transferability. Transparent limitations prevent claims from exceeding what the design and evidence can support.

Research quality and integrity framework

      TRANSPARENT QUESTION AND DESIGN
                    |
          +---------+---------+
          |         |         |
        VALIDITY  RELIABILITY ETHICS
          |         |         |
          +---------+---------+
                    |
        TRACEABLE DATA AND ANALYSIS
                    |
        HONEST REPORTING / LIMITATIONS
                    |
          REPRODUCIBLE CONTRIBUTION
Figure 15.4: Credible research combines methodological quality, ethical conduct and transparent reporting.

Chapter summary

Information systems research is a systematic inquiry into the relationships among technology, people and organisations. A strong study begins with a meaningful and feasible problem, develops aligned questions and objectives, critically reviews relevant scholarship and selects a defensible framework and methodology. Quantitative, qualitative, mixed-methods, case-study, action-research and design-science approaches offer different forms of evidence and contribution.

Research quality requires appropriate sampling, careful instruments, trustworthy data, suitable analysis and honest interpretation. Ethics, privacy, cybersecurity, citation and professional integrity apply throughout the research lifecycle. A well-written proposal or dissertation makes its reasoning traceable and its limitations visible. Information systems professionals use these same habits—evidence, reflection, transparency and accountability—to make better organisational decisions.

Official Education References

Use these official organisations for curriculum guidance, examinations and further learning information.