Research Methods and Ethics in IT

Research Methods and Ethics in IT

• Research is a systematic investigation that explores hypotheses, interprets data/texts, and poses new research questions.
• Reasons for research include pursuing new interests, confirming/disproving positions, enhancing/creating products/services, creating/learning new things, and contributing to knowledge.
• Research methodology defines the process of collecting information/data for business decisions.
• Research methodology can be quantitative or qualitative.
• Methods of data collection vary based on methodology.

Qualitative Research Methods

• Interviews
• Observations

Quantitative Research Methods

• Surveys
• Experiments
• Simulations

Research Ethics

• Adherence to rules for distinguishing right from wrong is crucial.
• Acting ethically in all situations is mandatory.
• Be mindful of scientific misconduct, research fraud, plagiarism, and avoiding harm to participants.

Literature Review and References

• Literature reviews discuss published information within a specific subject area or time period.
• Reasons for literature reviews include serving as a guide, illustrating past research, determining the originality of research, and providing alternative directions.
• A reference/citation is a formal way to credit others' work (thinking, writing, or research).
• Materials used in academic writing must be attributed to their authors.
• Attribution gives credit to sources of information and ideas.

Electronic Health Records (EHRs)

• EHRs are digital versions of patient charts.
• They are real-time, patient-centered, and provide instant/secure access for authorized users.
• EHR systems encompass more than just medical/treatment histories and can include a broader view of patient care.

System Planning

• Planning involves developing a view of the future to guide decision-making.
• Three types of planning include strategic, tactical, and operational.
• Planning for system development involves understanding people, processes, technology, and governance.
• It emphasizes organizational problems/needs to improve use of people and methods.

Systems Strategy

• Systems Planning is part of a broader Systems Strategy.
• Keys questions for systems planning include: the purpose of the information system development; current and future system users; and whether the system is new, an upgrade, or an extension.

The Systems Development Life Cycle (SDLC)

• SDLC is a series of phases for software/application development.
• Key SDLC characteristics include defining the problem/opportunity; including many names and applications; analysis vs. synthesis; variability across stages; a disciplined approach; and systems approach.
• The outputs of each phase become the inputs for the next.

Systems Analysis - Data Requirements

• Analyzing the needs of a system's design.
• Research is crucial; similar individuals may fulfil many roles.
• Analysis is part of gathering requirements.
• Two common approaches to analysis and design include structured systems analysis/design (SSAD) and object-oriented approaches.

Systems Analysis- Workflows

• Process models formally depict how a business operates.
• Data flow diagrams illustrate business processes and the flow of associated data.
• Logical process models describe processes without detailing execution.
• Physical process models represent implementation details.

Systems Analysis- Conceptual Modeling

• Data flow diagrams capture data requirements and flows.
• Conceptual data modeling establishes the relationships between relevant data elements.
• Conceptual data models help translate into physical designs.

Systems Design - Logical Requirements

• Clear system requirements are crucial for successful design.
• The system requirements document provides a framework for the design stage.
• Errors and omissions in the requirement document might negatively impact the final product.
• Thorough analysis and a well-defined requirements document are essential to design phase success.

Systems Design - Physical Requirements

• Logical data design informs key physical design decisions (storage format, physical records, and arrangement of secondary storage for efficient retrieval/update).
• Data choices for efficiency of access (media and structuring).

Business and Technical Requirements (BTR)

• The BTR document contains all essential information for planning and designing new systems, including the purpose of the project (e.g., a new EHR system), descriptions of current systems, potential problems, and the proposed system.

BTR- Presentation

• The BTR presentation shares the research purpose, data sources, current/prior system issues, and proposed system features, alongside flowcharts for the new system and reflections on the project.