Learning Objectives
By the end of this project, you will be able to:
- Select a real (or realistic) Nepal organization and map its core business processes.
- Identify the information systems that support operations, customers, and decisions.
- Analyze gaps using course concepts (TPS, FAIS/ERP, CRM/SCM, analytics, cloud/mobile/social).
- Recommend practical IS improvements with benefits, risks, and implementation steps.
- Produce a group project report that meets the faculty case-study requirement.
Syllabus requirement
The official syllabus asks students to study and prepare a project report on information systems useful in organizations. Work in groups of at most 3 members.
This brief turns that requirement into a concrete deliverable with a marking rubric.
Choose an organization
Pick one organization your group can interview or research with public information. Prefer a Nepal context:
| Option | Example focus |
|---|---|
| Retail / marketplace | Daraz seller, local supermarket chain, pharmacy network |
| Banking / payments | Commercial bank branch, cooperative, eSewa/Khalti merchant use |
| Hospitality / tourism | Hotel in Pokhara or Kathmandu, trekking agency |
| Education | College admin office, coaching center |
| Manufacturing / FMCG | Dairy, garment, or food distributor with multi-city stock |
| Healthcare | Clinic or diagnostic lab appointment and records flow |
| SME services | Logistics courier, salon chain, restaurant with delivery |
If you cannot access a real firm, build a named fictional Nepal SME with realistic processes (state that clearly in the report).
Deliverables
1. Project report (main)
Length: 2,500–4,000 words (or 8–12 pages), excluding cover and appendix.
Structure (use these headings):
- Cover — course code, title, group members, college, date.
- Organization overview — industry, size, locations, customers, products/services.
- Business processes — at least two cross-functional processes (e.g. order-to-cash, hire-to-retire, procure-to-pay). Inputs, activities, outputs.
- Current information systems — TPS / FAIS / ERP / CRM / SCM / analytics / cloud / mobile / social as applicable. Name tools if known (Excel, Tally, custom software, SaaS).
- Analysis — strengths, information silos, data quality, customer or supplier pain, decision latency. Link each point to a course concept and cite the relevant unit.
- Recommendations — 3–5 prioritized IS improvements. For each: problem → solution → expected benefit → cost/risk → 90-day first step.
- Conclusion — what the group learned about BIS in Nepal organizations.
- References — interviews, websites, course notes, textbooks.
- Appendix (optional) — process diagram, interview notes summary, screenshots.
2. Short presentation (optional but recommended)
5–7 slides, 8–10 minutes: organization → one process → one gap → one recommendation.
Constraints and academic honesty
- Do not invent “ERP implementations” you cannot defend; scale recommendations to the organization’s size.
- Anonymize confidential data; get permission before using internal screenshots.
- Write in your own words; cite the course notes and textbooks where you reuse frameworks (Porter, BPI/BPR, CRM types, BA process).
Marking rubric (100 points)
| Criterion | Weight | Excellent | Adequate | Weak |
|---|---|---|---|---|
| Organization & process clarity | 15 | Clear scope; processes mapped with inputs/outputs | Processes listed but shallow | Vague or off-topic |
| IS identification (course vocabulary) | 20 | Correct use of TPS/FAIS/ERP/CRM/SCM/analytics/cloud etc. | Some correct labels | Buzzwords without fit |
| Analysis depth | 25 | Gaps tied to data, process, and strategy | Description > analysis | Opinion only |
| Recommendations | 20 | Feasible, prioritized, Nepal-aware | Generic software wishlist | Unrealistic or none |
| Structure, citation, teamwork | 10 | Clean report; sources; equal contribution note | Minor formatting issues | Missing sections / plagiarism risk |
| Communication | 10 | Clear Nepali/English business writing; optional slides strong | Readable | Hard to follow |
Suggested grade bands: 80+ distinction-level; 60–79 solid pass; below 50 revise and resubmit process/IS sections.
Self-check before submission
- Group size ≤ 3 and all names on the cover
- At least two business processes documented
- At least three course units explicitly referenced in the analysis
- Recommendations are sized for a Nepal organization (not “buy SAP tomorrow” for a 5-person shop)
- References and honesty statement included
