Introduction of System Analysis and Design

System Analysis and Design is the process of analyzing and designing information systems to improve efficiency and meet organizational goals.

Introduction of System Analysis and Design

What is System Analysis and Design?

System Analysis and Design (SAD) is a structured process used to develop and maintain information systems. It involves analyzing a problem, designing a solution, and implementing that solution using system components like hardware, software, data, and users.

Key Concepts:

Term

Description

System

A set of components that work together to achieve a goal.

Analysis

Understanding and breaking down the current system to find problems.

Design

Creating a blueprint or plan for a new or improved system.

 

Purpose of SAD:

  • To build efficient and reliable information systems.
  • To solve organizational problems through technology.
  • To ensure system requirements are correctly gathered and implemented.

Example of SAD:

Example: Online Examination System

Step

Description

System Analysis

Identify current exam methods (paper-based), problems like manual checking, delays in result.

System Design

Plan a digital system where students can log in, take exams online, and receive auto-evaluated results.

Phases of SAD:

  1. Preliminary Investigation
  2. System Analysis
  3. System Design
  4. Development
  5. Testing
  6. Implementation
  7. Maintenance

Diagram: System Analysis and Design Process

Why SAD is Important?

  • Ensures the system meets user needs
  • Reduces cost and errors
  • Improves system quality and efficiency
  • Provides documentation and long-term support

---------------------------------------

Definition of System:

A system is a set of interrelated components working together toward a common goal by accepting inputs and producing outputs in an organized transformation process.

Fundamentals of a System:

Element

Description

Input

Data or materials entered into a system for processing.

Process

Transformation of input into a useful output.

Output

The final result or information produced by the system.

Control

Guides the system and ensures it functions properly (rules, policies).

Feedback

Output that is used to adjust or improve future inputs and processes.

Boundary

Defines the scope of the system, what is inside and what is outside.

Environment

Everything outside the system boundary that affects the system.

Interface

The point of interaction between components or between systems.

Block Diagram of a System:

Example: Library Management System

Element

Description

Input

Book details, student details, borrowing request

Process

Verify user, check book availability, record transaction

Output

Issue slip, due date, updated database

Control

Rules (e.g., maximum 3 books, return within 15 days)

Feedback

Late return penalty reports, usage logs

Boundary

Only library-related activities included

Environment

Students, librarians, book vendors

 

Importance of Understanding System Fundamentals:

  • Helps in problem identification
  • Ensures better design
  • Improves efficiency and effectiveness
  • Aids in system integration

Important term related to system

  1. System

A system is a set of interrelated components working together toward a common goal.

  • Example: A college management system includes modules for student data, attendance, and fee management.

  

  1. Subsystem

A subsystem is a smaller component of a larger system, performing a specific task.

  • Example: In a hospital system, the billing department is a subsystem.

 

  1. Input

The data or material received by the system for processing.

  • Example: Student details entered during admission.

  1. Process

The operation or action performed on input to convert it into output.

  • Example: Calculating student grades from marks.

 

  1. Output

The result or information produced by the system after processing.

  • Example: Report card or bill.

 

  1. Feedback

Information about the output that is used to improve the system.

  • Example: User complaints used to improve the website interface.

 

  1. Control

Controls are rules or policies that guide the system and ensure it operates correctly.

  • Example: Students must pay fees before accessing results.

 

  1. Boundary

Defines the limits of the system, separating it from the external environment.

  • Example: A school's library system does not handle student fees (outside its boundary).

 

  1. Environment

Everything outside the system boundary that interacts or affects the system.

  • Example: Government policies affecting school systems. 

 

  1. Interface

The point of interaction between two systems or between users and the system.

  • Example: Login screen of a student portal.

 

  1. Data

Raw facts or figures that are processed to generate information.

  • Example: Marks, names, ID numbers.

 

  1. Information

Processed or organized data that is meaningful and useful.

  • Example: Average class performance report.

 

  1. System Analyst

A professional who studies, analyzes, designs, and implements systems.

  • Example: An IT expert designing a hospital record system.

----------------------------------------

Classification of System in System Analysis and Design

Systems can be classified based on their nature, structure, functionality, and interactions with the environment. Understanding these classifications helps system analysts choose the right design and development approach.

1. Physical vs. Abstract System

Type

Description

Example

Physical System

Tangible systems composed of physical components.

Computer, Engine, Human Body

Abstract System

Conceptual or logical systems, often models or theories.

Software algorithm, Accounting system, Organizational structure

 

2. Open vs. Closed System

Type

Description

Example

Open System

Interacts with the environment, receives input and produces output.

Business organization, School

Closed System

Does not interact with the external environment (ideal case).

Chemical reaction in sealed container, Watch mechanism (theoretically)

In reality, no system is fully closed; all systems have some interaction with their environment.

3. Deterministic vs. Probabilistic System

Type

Description

Example

Deterministic System

Operates in a predictable and predefined manner.

Calculator, Payroll system

Probabilistic System

Outcomes are uncertain; relies on probability or chance.

Stock market prediction, Weather forecasting

 

4. Man-Made vs. Natural System

Type

Description

Example

Man-Made System

Created by humans to serve a purpose.

Computer system, Railway network

Natural System

Exists in nature without human intervention.

Solar system, Ecosystem

 

5. Permanent vs. Temporary System

Type

Description

Example

Permanent System

Exists for a long period, often indefinitely.

Education system, Judicial system

Temporary System

Designed for short-term goals or time-bound.

Event management system, Election system

 

6. Adaptive vs. Non-Adaptive System

Type

Description

Example

Adaptive System

Changes in response to environmental changes.

AI software, Learning management system

Non-Adaptive System

Remains unchanged regardless of the environment.

Traditional mechanical watch

 

Diagram: Classification of System

Why Classification is Important in SAD?

  • Helps in understanding system behavior and complexity
  • Aids in selecting appropriate design and implementation techniques
  • Improves system performance and maintainability

--------------------------------------

Real-Life Business Subsystems

In System Analysis and Design, a subsystem is a smaller part of a larger system that performs specific tasks and contributes to the overall system functionality.

A business system (like an organization) is composed of multiple subsystems, each handling specific functions such as finance, marketing, HR, etc.

Definition of Subsystem:

A subsystem is a component of a larger system that has its own function but works together with other subsystems to achieve the overall goal.

 

Example: Real-Life Business – University as a System

Subsystem

Description

Function

Admission Subsystem

Handles student applications and enrollment

Accepts forms, verifies documents

Academic Subsystem

Manages classes, syllabus, timetable

Schedules lectures, assigns faculty

Examination Subsystem

Conducts exams and publishes results

Sets papers, evaluates, declares results

Library Subsystem

Manages books and lending services

Issues/returns books, maintains inventory

Finance Subsystem

Manages fees, salaries, budgets

Processes payments, maintains records

Hostel Subsystem

Manages accommodation for students

Allots rooms, handles complaints

HR Subsystem

Manages employee details and payroll

Hiring, salary management, records

All these subsystems interact with each other. For example, the finance subsystem collects fees and passes student status to the academic subsystem.

 

Example: Real-Life Business – E-commerce Company

Subsystem

Function

Order Management

Processes customer orders

Inventory System

Tracks stock levels

Customer Support

Handles customer queries and complaints

Logistics System

Manages shipping and delivery

Payment Gateway

Handles payments and refunds

Marketing System

Manages promotions, campaigns

 

 Diagram: Real-Life Business System with Subsystems

Each block here is a subsystem that performs a specific role, but collectively they help the main system (e.g., university) function effectively.

Why Subsystems are Important:

  • Divide and conquer: Breaks down complex systems into manageable units
  • Improves efficiency: Each subsystem specializes in its task
  • Easier maintenance: Changes can be made in one subsystem without affecting others
  • Supports modular design: Encourages reuse and scalability

----------------------------------

Real-Time System

What is a Real-Time System?

A Real-Time System (RTS) is a system that must respond to inputs or events within a strict time limit. The correctness of the system depends not only on producing the correct result, but also on producing it at the correct time.

Key Characteristics of Real-Time Systems:

Feature

Description

Time Constraint

Must respond within a fixed time limit (deadlines).

Deterministic

Predictable behavior with defined outcomes.

Reliability

High reliability and availability.

Concurrency

Handles multiple inputs/events at once.

Event-Driven

Triggered by real-world events or signals.

 

Types of Real-Time Systems:

Type

Description

Example

Hard Real-Time

Missing a deadline causes system failure.

Airbag system, Pacemaker

Soft Real-Time

Missing deadline reduces system quality but doesn’t cause failure.

Video conferencing, Online gaming

Firm Real-Time

Occasional missed deadlines tolerated, but result becomes useless.

Stock trading system

 

Real-Time System Example: Airbag Control System in Cars

Component

Real-Time Action

Crash Sensor

Detects collision instantly

Control Unit

Processes data within milliseconds

Airbag Deployment

Inflates airbag immediately to save life

Diagram: Real-Time System Workflow

More Real-Life Examples of Real-Time Systems:

System

Real-Time Application

ATM

PIN verification, cash dispense

Air Traffic Control

Aircraft tracking and navigation

Medical Monitoring

Heartbeat and oxygen level tracking

Industrial Robots

Automatic welding, assembling

Autonomous Vehicles

Obstacle detection and braking

 

Why Real-Time Systems are Important?

  • Safety-Critical Operations (e.g., airbag systems)
  • Timely Decision Making
  • Constant Monitoring and Response
  • Increased Efficiency and Automation

--------------------------------

Distributed System

Simple Definition:

A Distributed System is like a team of computers (or devices) working together over a network to achieve a common goal, but they look and feel like a single system to the user.

 

In Short:

A Distributed System is like a team of workers in different rooms of a building — each doing a part of the job, but to the customer, it feels like one smooth service.

Human-Friendly Explanation:

Imagine you order food from a food delivery app (like Zomato or Swiggy):

  • One server shows the menu
  • Another server checks your location
  • Another one processes payment
  • Another one manages delivery

All these parts work together, but they are running on different computers in different places. Still, to you, it feels like one single app — that’s a distributed system

Features (in simple terms):

Feature

Meaning

Multiple Computers

Different machines work together

Connected by Network

Communicate via the internet or LAN

Work as One

User feels it's one system

Shared Workload

Tasks are divided between computers

Fault Tolerance

If one machine fails, others can take over

Real-Life Examples of Distributed Systems:

Example

Description

Google Search

Millions of computers answering billions of queries together

Banking Systems

ATM, online banking, mobile app all work together from different servers

Cloud Storage (Google Drive, Dropbox)

Files are stored across many servers, but you access them like one folder

Online Games

Game data is handled across multiple servers worldwide

Diagram (Simple View of a Distributed System)

-------------------------------------

Development of a Successful System

Developing a successful system involves a step-by-step process to ensure the system is useful, user-friendly, reliable, and solves the real problem for which it is created.

Definition:

The development of a successful system is the structured process of analyzing, designing, building, testing, and implementing an information system that meets the objectives of users and organizations effectively and efficiently.

Key Stages in Successful System Development (with Explanation):

Step

Description

Example

1. Problem Identification

Understand the real problem or need for the system.

Manual attendance is slow and inaccurate.

2. Feasibility Study

Check if the system is possible technically, economically, and legally.

Can we afford a biometric system?

3. System Analysis

Study the current system and gather user requirements.

Talk to teachers and students about current issues.

4. System Design

Create a blueprint for the new system (layout, data flow, interfaces).

Design a biometric-based attendance system.

5. Development/Coding

Build the actual system using programming or tools.

Code the attendance app and connect it to a fingerprint device.

6. Testing

Check the system for errors or issues (bugs, performance, security).

Test if the app marks attendance correctly.

7. Implementation

Install the system in the real environment and train users.

Set up the system in classrooms and train staff.

8. Maintenance

Fix issues, update features, and improve the system as needed.

Add holiday and leave management features later.

9. Evaluation

Review if the system meets goals and improves performance.

Compare attendance speed and accuracy before and after.

 

Factors for System Success:                                                 

Factor

Role

User Involvement

Users must be involved in planning and testing.

Clear Objectives

Purpose and goals should be well-defined.

Proper Planning

Project must have timelines and resources.

Good Design

System must be user-friendly and error-free.

Testing and Feedback

Catch and fix errors before full use.

Regular Maintenance

Keep the system updated and relevant.

 

Diagram: Development of a Successful System

Real-Life Example: School Management System

  • Problem: Paper-based attendance and marks taking time
  • Solution: Develop a digital School Management System
  • Result: Faster reporting, better tracking, parent access to progress reports

-----------------------------------

What's Your Reaction?

like

dislike

love

funny

angry

sad

wow