📦 An Information System is a structured combination of:

• People + Processes + Data + Technology + Networks

that collects, processes, stores, and distributes information to support decision-making, coordination, and control in an organization.

💡 Exam Trick: Remember mnemonic "PP-DTN" → People, Process, Data, Technology, Networks

📦 The systematic process of collecting, identifying, and documenting the needs, expectations, and constraints of stakeholders to define what the information system must accomplish.

• ✅ Users of the system → Pharmacists, technicians, patients
• ✅ Forms & documents → Prescription pads, invoice formats, stock registers
• ✅ Procedure manuals → SOPs for dispensing, storage guidelines
• ✅ Rule books → Pharmacy Act, NDMA regulations, hospital policies
• ✅ Reports → Monthly sales reports, expiry alerts, audit logs
• ✅ Existing programs → Legacy inventory software (if any)

💡 Pro Tip: Always use triangulation — combine ≥2 methods (e.g., Interview + Observation) to validate findings.

🎯 Exam Mnemonic: "U-F-P-R-R" for sources → Users, Forms, Procedures, Rules, Reports

📦 The process of identifying, documenting, and validating what the system must do (functional) and how well it must perform (non-functional).

• Analyst predicts needs based on prior experience & domain knowledge
• Example: Knowing that pharmacists need expiry alerts → proactively include this feature

• Actively gathering requirements using techniques:
• → Interviews, Questionnaires, Brainstorming, Prototyping
• Example: Conducting focus group with pharmacy staff to list "must-have" features

• Validating requirements with users to ensure accuracy & completeness
• Technique: User walkthrough — analyst + user review SRS document together
• Example: Pharmacist confirms: "Yes, the system must flag drug-drug interactions"

• Documenting requirements formally in SRS (System Requirements Specification)
• Format: Clear, unambiguous, testable statements
• Example SRS line: "System shall display warning if prescribed drug interacts with patient's current medication"

🎯 Exam Mnemonic: "AEAS" → Anticipation, Elicitation, Assurance, Specification

📦 Evaluation of whether a proposed project is viable from technical, economic, operational, and other perspectives before committing resources.

💡 Exam Trick: Draw a small table with TECOPS headers — examiners love structured answers!

📦 A graphical representation showing how data moves through an information system — illustrating inputs, processes, outputs, and data stores without showing control logic.

🎯 Exam Mnemonic: "PEST" → Process, Entity, Store, Transfer (Flow)

• 📄 Delivery Note: Order No, Vendor Code, Item Name, Item Code, Delivery Date, Quantity Supplied
• 📄 Items Received Note: Order No, Item Code, Quantity Received, Inspection Result
• 📄 Discrepancy Note: + Excess/Deficiency, Days Late/Early, Reason Code
• 📄 Order File: Order No, Order Date, Vendor Details, Quantity Ordered, Expected Delivery

• ✅ Rule 1: IF delivery note order# NOT in order file → RETURN item to vendor
• ✅ Rule 2: IF item code mismatch → RETURN item to vendor
• ✅ Rule 3: IF quantity delivered ≠ ordered → SEND discrepancy note to purchase office
• ✅ Rule 4: IF delivery date early/late → SEND discrepancy note with delay reason

💡 Exam Tip: Always label DFD elements clearly. Use pharmacy-specific terms to show applied knowledge.

• 🔹 Physical DFD: Shows HOW the system works — includes people, departments, physical files
  • Example: "Pharmacist manually checks stock register"
• 🔹 Logical DFD: Shows WHAT the system does — focuses on business processes, independent of implementation
  • Example: "System validates prescription against formulary"

📦 A detailed description of the logic, rules, and transformations applied within a DFD process to convert inputs into outputs. It answers: "HOW exactly does this process work?"

• ✅ Must contain detailed functional requirements
• ✅ Must specify ALL rules governing data transformation
• ✅ Must include underlying business policies
• ✅ Should NOT describe implementation method (that's design phase)

📋 Process ID: P-101

📋 Process Name: Validate Prescription

📋 Input Data:

• Prescription ID, Patient ID, Drug Code, Quantity, Prescriber ID

📋 Output Data:

• Validation Status (Valid/Invalid), Error Code (if any), Next Step Flag

📋 Processing Logic (Structured English):

   STEP 1: LOOKUP Drug Code in Formulary Database
   STEP 2: IF Drug NOT FOUND → RETURN "Invalid: Drug not in formulary"
   STEP 3: IF Quantity > Max_Limit → FLAG "Requires Doctor Approval"
   STEP 4: CHECK Patient Allergy List → IF Match → RETURN "Allergy Alert"
   STEP 5: VERIFY Prescriber License Status → IF Expired → RETURN "Invalid Prescriber"
   STEP 6: IF all checks pass → RETURN "Valid - Proceed to Billing"

📋 Business Rules:

• Controlled substances require dual verification (Rule BR-07)
• Expired prescriptions (>1 year) auto-reject (Rule BR-12)
• Pediatric doses require weight-based validation (Rule BR-23)

💡 Exam Trick: Use decision tables for 5/10-mark questions — they're compact, clear, and score high!

📦 The process of planning how data will be entered into the system to ensure accuracy, efficiency, and user-friendliness.

• ✅ Simple and easy to use
• ✅ Avoid unnecessary steps in data entry
• ✅ Minimize delay in data interpretation
• ✅ Error-prevention mechanisms built-in
• ✅ Keep process controlled and auditable

• ❓ What data needs to be entered? → Drug code, batch no, expiry, quantity
• ❓ How much data? → Minimize fields; use auto-fill where possible
• ❓ How to code/interpret? → Dropdowns for drug names, numeric-only for quantity
• ❓ User-friendliness? → Tooltips, real-time validation, clear error messages
• ❓ Error handling? → "Undo" option, clear instructions for correction
• ❓ Documentation? → User guide for data entry staff

✅ GOOD DESIGN:

• Patient ID: Auto-suggest from database + barcode scan option
• Drug Name: Searchable dropdown with generic/brand names
• Quantity: Numeric field with max-limit warning
• Doctor Details: Auto-fetch from registered prescribers list
• Real-time Checks: Drug-drug interaction alert, allergy warning
• Feedback: "Prescription Validated ✓" with next-step button

❌ POOR DESIGN:

• Free-text drug name field → spelling errors, duplicates
• No validation on quantity → negative values accepted
• No confirmation message → user unsure if submission succeeded
• No error recovery → single typo forces restart

📦 The process of determining what information the system must produce, in what format, to whom, and when — to meet user business needs.

• ✅ Serve the planned purpose of the user
• ✅ Deliver right amount of output at right time & place
• ✅ Format appropriate for user role & decision context

• 📄 Paper: Prescription printouts, patient instruction leaflets
• 💻 Screen: Real-time alerts, dashboard for inventory manager
• 🗄️ Memory/Storage: Audit logs, backup archives
• 📡 Electronic Media: Email reports, SMS alerts, API feeds to regulatory portals
• 🎧 Audio/Video: Training modules, patient counseling videos
• 💽 CD/DVD: Software distribution, offline data backup

💡 Exam Trick: Always link output design to user role and decision context — shows applied understanding.

🎯 Mnemonic for Output Goals: "RIGHT" → Relevant, Immediate, Graphical (if helpful), Hard/Soft copy, Timely

📦 A structured framework of phases that guides the planning, creation, testing, deployment, and maintenance of an information system.

🎯 Exam Mnemonic: "PRID-IT-MR" → Planning, Requirements, Implementation, Design, Integration, Testing, Maintenance, Review
(Note: Design often comes before Implementation — adjust order as per your syllabus)

💡 Exam Tip: If asked "Which SDLC model for pharmacy project?", justify based on:
• Requirement clarity • Risk level • User involvement • Timeline

📦 The process of defining project goals, scope, resources, timeline, and risk management strategies to ensure successful delivery.

• ✅ Define and justify the need for the project
• ✅ Specify, quantify & agree desired outcomes & benefits
• ✅ Appoint Project Manager & set up Project Board (if needed)
• ✅ Ensure post-project reviews measure benefit achievement
• ✅ Update Business Case based on operational reality
• ✅ Feed lessons learned into strategic planning

• ✅ Plan delivery of outcomes & benefits
• ✅ Manage stakeholder relationships (pharmacists, IT, regulators)
• ✅ Manage delivery process (methodology, milestones)
• ✅ Determine & secure resource requirements (budget, staff, tech)
• ✅ Develop Business Case for SRO/Board approval

• 1⃣ Confirm scope & purpose: What's IN/OUT? (Use MoSCoW: Must, Should, Could, Won't)
• 2⃣ Define deliverables: Tangible outputs (e.g., "Working inventory module")
• 3⃣ Identify & estimate activities: Break work into tasks; estimate time/cost
• 4⃣ Schedule work & resources: Gantt chart; assign people/tools
• 5⃣ Identify risks & design controls: Risk register + mitigation plans
• 6⃣ Document & gain approval: Baseline plan signed by stakeholders

• 📄 Business Case: Why do this? (Cost-benefit, ROI, strategic alignment)
• 📄 Project Charter: Formal authorization; high-level scope & authority
• 📄 SRS: Detailed functional & non-functional requirements
• 📄 Risk Register: Risks, probability, impact, owner, mitigation
• 📄 Communication Plan: Who needs what info, when, via which channel
• 📄 Test Plan: How system will be validated before go-live

• ✅ On-time delivery (e.g., launch before monsoon stock-up season)
• ✅ Within budget (track actual vs. planned spend monthly)
• ✅ User adoption rate (% of staff actively using new system)
• ✅ Error reduction (e.g., dispensing errors down 40% post-implementation)
• ✅ ROI achieved (e.g., reduced expiry wastage saves ₹X lakhs/year)
• ✅ Compliance maintained (e.g., zero audit findings post-launch)

💡 Pro Tip: In exams, always link project management concepts to healthcare/pharmacy context — shows applied understanding and scores higher.

• IS Components: PP-DTN → People, Process, Data, Technology, Networks
• Info Sources: U-F-P-R-R → Users, Forms, Procedures, Rules, Reports
• Requirements: AEAS → Anticipation, Elicitation, Assurance, Specification
• Feasibility: TECOPS → Technical, Economic, Cultural, Operational, Political, Scheduling
• DFD Symbols: PEST → Process, Entity, Store, Transfer (Flow)
• Input Design Goals: SIMPLE → Simple, Intelligent, Minimal, Prevent errors, Logical, Easy recovery
• Output Design Goals: RIGHT → Relevant, Immediate, Graphical (if helpful), Hard/Soft, Timely
• SDLC Phases: PRID-IT-MR → Planning, Requirements, Implementation, Design, Integration, Testing, Maintenance, Review
• Project Planning: 6 Steps → Scope, Deliverables, Activities, Schedule, Risks, Approval

• Q: "Explain DFD with example" (5/10 marks)
  → Define DFD + draw simple Level-1 DFD (use PEST symbols) + pharmacy context example + mention Logical vs Physical
• Q: "Difference between functional & non-functional requirements"
  → Table: Functional = WHAT (features), Non-functional = HOW WELL (performance, security, usability) + pharmacy examples
• Q: "Why is feasibility analysis important?"
  → Use TECOPS framework + pharmacy-specific risks (regulatory compliance, staff training, ROI)
• Q: "Steps in SDLC"
  → Use PRID-IT-MR mnemonic + 1-line explanation per phase + model comparison if asked
• Q: "Input design considerations"
  → Use SIMPLE mnemonic + pharmacy input example (prescription entry screen)

• ✅ Always use pharmacy/healthcare examples — shows subject mastery & applied knowledge
• ✅ Draw diagrams (DFD, SDLC) even if not explicitly asked — visual answers score higher
• ✅ Use bullet points over paragraphs — easier for examiner to spot key points quickly
• ✅ Define acronyms first time: "SRS (System Requirements Specification)"
• ✅ Time management:
  • 2-mark Q = 3-4 lines + 1 example
  • 5-mark Q = ½ page + diagram/table
  • 10-mark Q = 1 page + diagram + comparison + conclusion
• ✅ Underline key terms: "feasibility analysis", "data flow", "SRS" — helps examiner identify keywords