SAD MIDTERMS

System

• Is a group of interconnected components that work together to achieve a specific goal

Input

• These are the information or resources entering the system

Process

• These are the activities that transform the input

Output

• These are the result produced by the system

Feedback

• These are the information used to evaluate or improve the system

Control

• Rules or mechanisms that keep the system working properly

Information system

• Is a combination of people, processes, data, and technology that work together to collect, process, store, and provide information

System Analysis

• It is the process of studying a problem, understanding how the current system works, and identifying what the users and organization need from a new or improved system

System Design

• It is the process of planning how the proposed system will work and what it will look like

System Analyst

• It is a professional who studies business or organizational problems and helps design information systems that meet user and organizational needs

System Design Artifacts

• These artifacts help us understand and communicate the proposed system

Subsystem

• It is a smaller system that is part of a larger system

• They are interconnected so a problem with one can affect the others

Control

• Refers to the rules, procedures, standards, or mechanisms used to ensure that a system operates properly.

System Environment

• These are everything that is outside the system that can influence or be influenced by the system

System Boundary

• This defines what is inside and outside the system

Open System

• It is a type of system that interacts with its environment

• EX: Business, school, hospital, E-commerce website

Closed System

• It has little to no interaction with its environment

• EX: Highly controlled laboratory system, and theoretical automated machines

Data

• Raw facts that have not been processed yet

Information

• Processed and organized data that has a meaning

Hardware

• These are the physical components or devices in an IS

Software

• These are the programs and application in an IS

data

• These are the facts and records handled by the IS

People

• Users and IT professionals that uses IS

Proceedures

• These are the rules and processes of the IS

Networks

• These are the communication Infrastructure used by the IS

Transaction Processing System

• A system that records and processes routine day-to-day transactions

Management Information System

• These system provides managers with reports and information needed to monitor and manage operations

• Its main purpose is to support management and operational decision-making

Decision Support System

• This system helps managers make decisions by analyzing data, models, and different scenarios

• It can analyze possible outcomes and supports What-if analysis, Forecasting, Comparison, Problem-solving

Executive Information System

• This system provides senior executives with summarized information to support strategic decision-making

Enterprise Resource Planning

• This system integrates different business functions into one system

Customer Relationship Management

• This system helps organizations manage interactions and relationships with customers

• The goal is to improve customer relationship and satisfaction

Software Development Life Cycle

• It is a structures process for planning, analyzing, designing, developing, testing, implementing, and maintaining an information system

Planning

• This phase answers the question what problem are we trying to solve

• It involves identifying the problem/opportunity, defining project goals and scope, identifying stakeholders, estimating resources, and identifying major risks

• Skipping this phase can lead to unclear goals and project scope

Requirements Analysis

• This phase answers the question what do users need

• It involves interviewing and observing users, studying current process, identifying functional and non-functional requirements, and documenting and validating requirements

• Skipping this phase may result in Missing or Incorrect Features

Design

• This phase answers the question how will the system work

• It involves planning the system architecture, designing the database, modeling the system processes and data flow, designing user screens and navigation, and planning access controls and security

• Skipping this phase may result into Poor Structure and confusing workflows

Testing

• This phase answers the question does the system work correctly and meet requirements?

• Skipping this phase may result into defects that may reach users

Implementation

• This process answers the question how will the users start using the system

• It involves deploying or installing the system, configuring accounts and permissions, migrating existing data when needed, training users, and providing support and guide.

• Skipping this phase may result into unprepared users

Maintenance

• This phase answers that question how do we keep the system useful and reliable

• It involves fixing bugs and errors, applying security updates, improving features and usability, adapting to policy and business changes, and backing up data and monitoring performance

• Skipping this phase may result in persistent security and reliability issues

Functional Requirement

• It defines what the system must do

Non-functional Requirement

• Defines how well the system must perform

Use case diagram

• Shows the users and the function they perform with the system

Data flow diagram

• Shows how information moves between entities, processes, and data stores

Entity Relationship Diagram

• Shows the data entities and how they relate to each other

Screen Layout

• Shows the planned layout of pages and interface elements

Unit Testing

• Checks individual Components

Integration testing

• Checks whether components work together

System Testing

• Checks the complete system

User Acceptance Testing

• Checks whether the system meets user needs

Waterfall

• Phases generally follow a sequence

• Requirements are planned early

• Often useful when needs are stable

Agile

• Works in delivered iterations

• Requires frequent user feedback

• Adapts to changing needs

Spiral

• Repeated development cycles

• strong focus on risk analysis

• Can suit complex, high-risk projects

System Project Initiation

• It is an early stage of a project in which an organization identifies a need, examines a problem or opportunity, and determines whether a proposed IS deserves further investigation

Root-cause analysis

• This helps to identify why a problem occurs instead of merely treating its symptoms

Stakeholders

• People or groups who affect, fund, approve, build, operate, or are affected by the project

Users

• People who will directly interact with the system

In scope

• Functions and activities that are expected to be included

Out of scope

• Function that are intentionally excluded from the current project

Scope Creep

• Occurs when project work expands beyond the agreed scope without proper review or approval

Constraints

• These are limits such as budget, staffing, infrastructure, or policy

Assumptions

• Conditions believed to true for initial planning but needing validation

Risks

• Uncertain events that may affect project objectives

Feasibility

• It determines whether a proposed system appears practical and worthwhile

Business Case

• It explains why a project should be considered

• Summarizes the problem, proposed approach, strategic alignment, and expected benefits

• Presents preliminary costs, feasibility findings, risks, and alternatives

• Recommends whether to proceed, revise, postpone, or reject the proposal

Project charter

• This document records the initial direction and justification of a proposed project

• It keeps the team aligned before detailed requirements analysis begins