System Analysis & Design: Basics, IS Types, Planning & Feasibility

Core Concepts

What is a System?

A system is an interconnected set of components working together to achieve a common goal. It consists of:

• Input: Data or resources entering the system.
• Processing: Transformation of inputs into outputs.
• Output: Results produced by the system.
• Feedback: Information used to adjust or improve the system.

Characteristics of a System:

• Interdependence: Components rely on each other.
• Integration: Parts work together as a whole.
• Emergent Properties: The system behaves differently than its individual parts.
• Environment: The system interacts with its surroundings.

classDiagram
    class System {
        +Input
        +Processing
        +Output
        +Feedback
    }
    class Component {
        <<abstract>>
        +Functionality
    }
    System "1" --> "*" Component : contains
    Component --> System : interacts with

A visual representation of a system’s interconnected parts (Image: Jenna Fair, CC BY-SA 3.0, via Wikimedia Commons)

Information Systems (IS)

An information system (IS) is a system that collects, processes, stores, and distributes information to support decision-making and control in an organization.

Types of Information Systems:

In the Real World

1. eSewa (Nepal):

   • Uses a Transaction Processing System (TPS) to handle real-time bill payments, mobile top-ups, and fund transfers. The system processes inputs (user credentials, payment details) and produces outputs (receipts, transaction confirmations) with minimal latency.
   • Example: When you pay your electricity bill via eSewa, the system validates your account, deducts the amount, and updates both your and the NTC’s records instantly.

2. Khalti (Nepal):

   • Implements a Decision Support System (DSS) for fraud detection. Machine learning models analyze transaction patterns (e.g., unusual locations, high-frequency payments) to flag suspicious activities.
   • Example: If you suddenly try to transfer Rs. 500,000 to an unknown account in Kathmandu while your usual transactions are below Rs. 10,000 in Pokhara, Khalti’s DSS may freeze the transaction for review.

3. Daraz (Nepal):

   • Relies on a Management Information System (MIS) to track inventory levels, sales trends, and supplier performance across its warehouses.
   • Example: Daraz’s MIS generates daily reports on low-stock items (e.g., "50 units of Samsung Galaxy phones left in warehouse A") and triggers automatic reorder alerts to suppliers.

System Analysis and Design Process

System Analysis and Design (SAD) is the process of studying, designing, and implementing information systems to solve business problems or improve efficiency. It follows the System Development Life Cycle (SDLC):

stateDiagram-v2
    [*] --> Planning
    Planning --> Analysis
    Analysis --> Design
    Design --> Implementation
    Implementation --> Testing
    Testing --> Maintenance
    Maintenance --> [*]

Key Phases of SDLC:

1. Planning: Define project scope, goals, and feasibility.
2. Analysis: Gather requirements and model the system (e.g., DFDs, ER diagrams).
3. Design: Create system architecture (e.g., database schema, UI wireframes).
4. Implementation: Build and code the system.
5. Testing: Verify correctness (unit, integration, system testing).
6. Maintenance: Update and improve the system post-deployment.

Feasibility Analysis

Feasibility analysis evaluates whether a project is viable in terms of:

1. Economic Feasibility: Can the project generate enough profit?

   • Payback Period: Time to recover initial investment. Example: A system costs Rs. 200,000 to install and generates Rs. 50,000 profit annually. With a 6% interest rate, the payback period is calculated as: $$\text{Payback Period}=\frac{\text{Initial Investment}}{\text{Annual Profit}}=\frac{200,000}{50,000}=4\text{ years}$$
   • Net Present Value (NPV): Discounted cash flows over time. Example: For a system with Rs. 75,000 one-time cost, Rs. 85,000 annual benefits, Rs. 35,000 recurring costs, and a 12% discount rate over 5 years: $$\text{NPV}=\sum _{t=0}^5\frac{{\text{Cash Flow}}_t}{(1+r{)}^t}-\text{Initial Cost}$$ (Use a financial calculator or spreadsheet for exact NPV.)

2. Technical Feasibility: Does the organization have the skills, hardware, or software to implement the system?

   • Example: A bank may lack the expertise to develop a blockchain-based loan system, making it technically infeasible without hiring external consultants.

3. Operational Feasibility: Will users accept and use the system?

   • Example: If employees resist switching from Excel to a new ERP system, the project may fail despite technical success.

4. Legal Feasibility: Does the system comply with laws and regulations?

   • Example: A healthcare app must adhere to Nepal’s Health Information Privacy Act.

System Implementation Methods

Example: NTC might use phased implementation for its new billing system:

1. Phase 1: Deploy in Kathmandu.
2. Phase 2: Roll out to Pokhara and Lalitpur.
3. Phase 3: Expand to rural areas.

Guidelines for Designing Forms and Reports

Forms Design:

1. Minimize Data Entry: Use dropdowns, checkboxes, or radio buttons.
2. Group Related Fields: Logical sections (e.g., "Personal Details," "Payment Info").
3. Clear Labels: Avoid jargon; use simple language.
4. Default Values: Pre-fill common options (e.g., "Nepal" as default country).
5. Error Handling: Provide real-time validation (e.g., "Invalid email format").

Example: A Khalti payment form groups fields as:

• User Info (Name, Phone)
• Payment Details (Amount, Account Number)
• Confirmation (OTP, Submit Button)

Reports Design:

1. Summarize Data: Use tables, charts, or graphs.
2. Highlight Key Metrics: Bold or color-code important figures.
3. Consistent Format: Use the same layout for all reports.
4. Drill-Down Capability: Allow users to explore details (e.g., click on a sales figure to see daily breakdowns).

Example: A Daraz sales report might include:

• Summary Table: Total sales by product category.
• Line Chart: Monthly sales trends.
• Drill-Down: Click on "Electronics" to see sales by brand (Samsung, Apple).

Information System Planning

Planning ensures that IS aligns with organizational goals. Two main approaches:

Example:

• Top-Down: Ncell’s CEO mandates a customer churn reduction system for all regions.
• Bottom-Up: The Pokhara branch identifies a need for a local language support system and proposes it to HQ.

Exam Tip

1. Definitions: Memorize key terms like system, information system, feasibility, and SDLC phases. Exams often ask for definitions with examples.

   • Example Question: "Define an information system and explain its characteristics." Answer: An IS is a system that processes data into information for decision-making. Characteristics include integration, shared data, procedures, and hardware/software.

2. Feasibility Calculations: Practice payback period and NPV problems. Use the formula: $$\text{NPV}=\sum \left(\frac{{\text{Net Cash Flow}}_t}{(1+r{)}^t}\right)-\text{Initial Investment}$$ Where $r$ = discount rate, $t$ = time period.

3. Diagrams: Be ready to draw:

   • DFDs (Data Flow Diagrams): For systems like a library management system (show processes like "Check Out Book").
   • SDLC Flowchart: Label all phases (Planning → Analysis → ... → Maintenance).

4. Real-World Applications: Link concepts to Nepali companies (e.g., eSewa for TPS, Khalti for DSS). Examiners love context!

   • Example: "How does Daraz use an MIS?" → "Daraz’s MIS tracks inventory levels, sales trends, and supplier performance to optimize warehouse operations."

5. Comparison Tables: For topics like implementation methods or IS types, create tables to organize information. Examiners check for clarity and completeness.

6. Worked Examples: Always show step-by-step calculations for feasibility (e.g., payback period). Partial credit is given for correct formulas, even if numbers are wrong.