Building & Managing IS: Systems Development, Project Mgmt, Agile, Cloud & Security

Key Concepts in Building Information Systems

1. Systems Development Life Cycle (SDLC)

The SDLC is a structured process for planning, creating, testing, and deploying an information system. It ensures systematic development while managing risks and costs.

Phases of SDLC

flowchart TD
    A["1. Planning"] --> B["2. Analysis"]
    B --> C["3. Design"]
    C --> D["4. Implementation"]
    D --> E["5. Testing"]
    E --> F["6. Deployment"]
    F --> G["7. Maintenance"]
    G -->|"Feedback"| A

Worked Example: Ncell’s Mobile App Upgrade

Ncell wanted to improve its Ncell App for bill payments, recharge, and customer support. They followed SDLC:

• Planning: Defined scope (mobile-first, offline support).
• Analysis: Surveyed users (70% wanted faster payments).
• Design: Created wireframes for a one-tap payment feature.
• Implementation: Developed in Agile sprints (see next section).
• Testing: Beta-tested with 5,000 users; fixed crashes in data sync.
• Deployment: Rolled out in phases (Kathmandu → nationwide).
• Maintenance: Added AI chatbot post-launch.

Why SDLC?

• Pros: Reduces errors, ensures stakeholder alignment, scalable.
• Cons: Rigid (slow for fast-changing needs), high upfront cost.

2. Project Management in IS Development

Projects fail when scope, time, or budget spiral. PMBOK (Project Management Body of Knowledge) and Agile are two key approaches.

Comparison: Waterfall vs. Agile

Real-World Agile: Daraz’s "Lightning Deals"

Daraz uses Scrum (Agile) to launch flash sales:

• Sprint Goal: "Increase mobile checkout by 30% in 3 weeks."
• Daily Standups: Devs, marketers, and UX teams sync.
• Sprint Review: Tested with 10,000 users in Pokhara before nationwide rollout.
• Result: 40% conversion rate (vs. 25% baseline).

Key Tools:

• Gantt Charts (for timelines):

  gantt
    title Daraz Lightning Deal Project
    dateFormat  YYYY-MM-DD
    section Development
    Backend API   :a1, 2023-10-01, 14d
    Frontend UI   :after a1, 7d
    section Testing
    QA Phase      :2023-10-16, 7d

• Critical Path Method (CPM): Identifies delays (e.g., if payment gateway integration fails, the whole project stalls).

3. Cloud Computing in IS Management

Cloud adoption in Nepal grew 300% in 2022 (NTA report). Firms use it for scalability, cost savings, and disaster recovery.

Cloud Service Models

mindmap
  root((Cloud Computing))
    SaaS["Software as a Service"]
      Example: **Google Workspace (eSewa uses for email)**
    PaaS["Platform as a Service"]
      Example: **Heroku (Nepali startups like "Khalti" use for backend)**
    IaaS["Infrastructure as a Service"]
      Example: **AWS (Ncell’s CDN for video streaming)**

Case Study: Nabil Bank’s Cloud Migration

• Challenge: Legacy core banking system was slow during Diwali season (high transaction volume).
• Solution: Migrated customer data and transaction logs to AWS RDS (relational database service).
• Outcome:
  • 95% faster login times.
  • Cost saved: Rs. 12M/year (no physical server maintenance).
  • Security: AWS KMS (Key Management Service) encrypts sensitive data.

Cloud Deployment Models:

4. Security Management in IS

Cyberattacks in Nepal rose 200% in 2023 (NTA). Key threats:

• Phishing (e.g., fake eSewa SMS asking for OTP).
• Data Breaches (e.g., Nepal Police’s 2022 leak of 1M records).
• Ransomware (e.g., Kathmandu University’s 2021 attack).

Security Frameworks

flowchart TD
    A["1. Risk Assessment"] --> B["2. Policy Creation"]
    B --> C["3. Implementation"]
    C --> D["4. Monitoring"]
    D -->|"Feedback"| A

Worked Example: Khalti’s Two-Factor Authentication (2FA)

• Problem: Fraudsters used stolen OTPs to drain accounts.
• Solution: Added biometric + PIN for high-value transactions (>Rs. 50K).
• Result:
  • Fraud drop: 80% in 6 months.
  • User trust: 60% of transactions now require 2FA.

Security Controls:

5. Change Management & User Adoption

70% of IT projects fail due to poor user adoption (McKinsey). Key strategies:

1. Training: e.g., Nepal Rastra Bank’s mandatory core banking training for bank staff.
2. Incentives: e.g., Daraz’s "referral cash" for users who switch to its app.
3. Feedback Loops: e.g., Pathao’s in-app surveys after rides.

ADKAR Model for Change Management

mindmap
  root((ADKAR Model))
    Awareness["1. Awareness of need for change"]
    Desire["2. Desire to support change"]
    Knowledge["3. Knowledge on how to change"]
    Ability["4. Ability to implement change"]
    Reinforcement["5. Reinforcement of new behavior"]

Case Study: NEPSE’s Online Trading Platform

• Challenge: Traders resisted moving from phone-based orders to the web portal.
• Solution:
  • Pilot: Trained 100 brokers in Lalitpur.
  • Incentive: Waived fees for first 3 months.
  • Result: 85% adoption in 6 months.

In the Real World

1. eSewa’s Microservices Architecture

   • Idea: Decoupled services (payments, notifications, fraud detection).
   • How? Each service (e.g., Khalti integration) runs independently, allowing real-time updates without downtime.
   • Impact: Enabled same-day Diwali transactions even during peak load.

2. Pathao’s Agile + Cloud Strategy

   • Idea: Continuous deployment (Agile) + serverless cloud (AWS Lambda).
   • How? Riders get auto-updated app features (e.g., electric scooter routing) without full redeploys.
   • Impact: 3x faster feature releases than competitors.

3. NTC’s Fiber-Optic Network (SDLC + Project Mgmt)

   • Idea: Phased rollout (SDLC) + critical path analysis (PMBOK).
   • How? Built Kathmandu-Pokhara backbone first, then expanded to Dharan and Biratnagar.
   • Impact: 99.9% uptime in 2023 (vs. 95% in 2020).

Exam Tip

What Examiners Look For

1. SDLC Traceability

   • Do: Map a real project (e.g., Ncell App) to all 7 phases.
   • Avoid: Generic answers like "SDLC is a process."

2. Agile vs. Waterfall

   • Do: Compare with a Nepali example (e.g., Daraz’s Agile vs. NTC’s Waterfall).
   • Avoid: Just listing pros/cons without context.

3. Cloud Security

   • Do: Link to Nepal’s data laws (e.g., Electronic Transactions Act 2008) + AWS/Azure controls.
   • Avoid: Vague terms like "cloud is secure."

4. Change Management

   • Do: Use ADKAR or Kotter’s 8-Step Model with a case study (e.g., NEPSE traders).
   • Avoid: Generic steps without real-world ties.

Common Pitfalls

• Ignoring Nepal-specific examples (e.g., Ncell, Khalti, NTC) → 0 marks for irrelevant global cases.
• Skipping visuals → Examiners penalize answers without diagrams/tables.
• Overcomplicating → Stick to 1-2 key points per subtopic with clear links to business impact.