ICT 110: IT for Business
You rarely "buy" software. Instead, you purchase a license.
Analogy: It's like a movie ticket. You don't own the film; you have permission to watch it under certain conditions (in this cinema, at this time).
Understanding the model is key to controlling costs, flexibility, and risk.
Source code is private. Owned and sold by a company.
Examples: Microsoft Office, Adobe Photoshop, Tally ERP
Pros: Professional support, stable, feature-rich.
Cons: High cost, vendor lock-in, limited flexibility.
Source code is public. Can be freely used, modified, and shared.
Examples: Linux, Odoo (ERP/CRM), Apache Web Server
Pros: Low/no cost, flexible, community support.
Cons: Support can be community-based, may require in-house expertise.
Software is rented, not owned. Accessed online via subscription.
Examples: Salesforce, Google Workspace, Microsoft 365
Pros: Low initial cost, accessible anywhere, automatic updates.
Cons: Ongoing fees, requires internet, data privacy concerns.
Software-as-a-Service (SaaS) has transformed how businesses access technology.
A new trekking agency in Pokhara needs a system to manage bookings and finances. Their budget is very tight, but one founder is tech-savvy.
Discussion: Which licensing model would you recommend and why? (Hint: Consider cost and flexibility).
A major commercial bank like Nabil Bank needs a new core banking system. It must be extremely secure and reliable, with 24/7 vendor support guaranteed.
Discussion: What model is the only viable choice here? (Hint: Consider risk and support).
Different models are chosen for strategic reasons in Nepal.
Next Topic: Introduction to Networks and Communication Elements