📘 Topic: Determining Customer’s Requirements
Subject: Information Technology Infrastructure
1. 📌 Introduction
Before designing any IT system or infrastructure, it is essential to understand what the customer actually needs. Failure to do so can lead to system failure, wasted cost, and dissatisfaction.
2. ✅ Definition
Determining Customer Requirements is the process of identifying, analyzing, and documenting the needs and expectations of users or clients for an IT system or service.
👉 Simple idea:
It means understanding what the customer wants before building the system.
3. 🎯 Objectives
- Ensure the system meets business needs
- Avoid unnecessary features
- Improve customer satisfaction
- Reduce development and maintenance cost
4. 🧩 Types of Customer Requirements
🔑 1. Functional Requirements
- What the system should do
📊 Examples:
- User login system
- Payment processing
🔑 2. Non-Functional Requirements
- How the system should perform
📊 Examples:
- Speed (response time)
- Security
- Availability
🔑 3. Business Requirements
- High-level goals of the organization
📊 Example:
🔑 4. Technical Requirements
📊 Example:
🔑 5. User Requirements
📊 Example:
5. 🔄 Process of Determining Requirements
📊 Step-by-Step Process
🔹 1. Requirement Gathering
- Collect information from stakeholders
🔹 2. Requirement Analysis
- Study and refine requirements
🔹 3. Requirement Documentation
- Write clear and structured requirements
🔹 4. Requirement Validation
- Confirm requirements with customer
🔹 5. Requirement Management
6. 🛠️ Techniques for Gathering Requirements
🔧 1. Interviews
- Direct discussion with customers
🔧 2. Questionnaires/Surveys
- Collect data from many users
🔧 3. Observation
🔧 4. Workshops
🔧 5. Prototyping
- Build a sample system for feedback
🔧 6. Document Analysis
- Study existing systems/documents
7. ⚠️ Challenges in Determining Requirements
🔧 1. Unclear Requirements
- Customers may not know what they want
🔧 2. Changing Requirements
🔧 3. Communication Gap
- Misunderstanding between IT and customers
🔧 4. Conflicting Requirements
- Different stakeholders want different things
🔧 5. Technical Limitations
- Some requirements may not be feasible
8. 📊 Key Rules / Best Practices
- ✔ Use simple and clear language
- ✔ Involve stakeholders continuously
- ✔ Validate requirements regularly
- ✔ Prioritize requirements
- ✔ Document everything properly
9. 🧠 Real-Life Example
A company wants an online shopping system:
👉 Requirements:
- Functional: Add to cart, checkout
- Non-functional: Fast loading, secure payment
👉 If requirements are unclear:
- System may fail or not meet expectations
10. 📊 Diagram Description (For Exams)
🖼️ Requirement Process Diagram
Draw:
Gathering → Analysis → Documentation → Validation → Management
11. 📌 Important Points for Revision
12. 📝 Likely Exam Questions
⭐ Short Questions:
- Define customer requirements.
- What are functional requirements?
- What are non-functional requirements?
- What is requirement validation?
- List requirement gathering techniques.
⭐ Long Questions:
- Explain the process of determining customer requirements.
- Discuss types of customer requirements with examples.
- What challenges are faced in requirement determination?
- Explain techniques for requirement gathering.
- Why is requirement analysis important?
13. 📌 Quick Summary / Conclusion
👉 Final Idea:
A well-understood requirement leads to a successful and effective IT system.
✅ Exam Tip:
Always include:
- Types of requirements
- Process steps
- Examples for better marks.