ScholarQuill logoScholarQuillUniversity Notes
  • Notes
  • Past Papers
  • Blogs
  • Todo
Login
ScholarQuill logoScholarQuillUniversity Notes
Login
NotesPast PapersBlogsTodo
More
SubjectsDiscussionCGPA CalculatorGPA CalculatorStudent PortalCourse Outline
About
About usPrivacy PolicyReportContact
Notes
Past Papers
Blogs
Todo
Analytics
    Current Subject
    🧩
    Information Technology Infrastructure
    ITEC3128
    Progress0 / 56 topics
    Topics
    1. Overview: Definitions and Infrastructure management activities2. Evolutions of Systems since 1960s (Mainframes-to-Midrange-to-PCs-to-Client-server computing-to-New age systems) and their Management3. Growth of internet, current business demands and IT systems issues4. Complexity of today's computing environment5. Total cost of complexity issues6. Value of Systems management for business7. Factors to consider in designing IT organizations and IT infrastructure8. Determining customer's Requirements9. Identifying System Components to manage10. Exist Processes, Data, applications, Tools and their integration11. Patterns for IT systems management12. Introduction to the design process for information systems13. Current computing environment: Complexity of current computing, multiple technologies, multiple vendors, multiple users14. e-Waste disposal15. Total cost of ownership16. IT system Management: Common tasks in IT system management17. Approaches for organization Management18. Models in IT system design19. IT management systems context diagram20. Patterns for IT system Management21. Information system costs and benefits22. Capital budgeting for information system23. Real Options pricing models24. Limitation of financial models25. Service Delivery Processes: IT services continuity management26. Capacity management27. Availability management and service desk28. Service Support Management: Service support process29. Configuration Management30. Incident management31. Problem management32. Change management33. Release management34. Storage Management: backups, Archive, Recovery, Disaster recovery35. Space management36. Hierarchical storage management37. Network attached storage38. Storage area network39. Bare machine recovery40. Data retention41. Database protection42. Security Management: Introduction Security43. Identity management44. Single sign-on45. Access Management46. Basics of network security47. LDAP fundamentals48. Intrusion detection49. Firewall50. Security information management51. IT Ethics: Introduction to Cyber Ethics52. Intellectual Property53. Privacy and Law54. Computer Forensics55. Ethics and Internet56. Cyber Crimes
    ITEC3128›Determining customer's Requirements
    Information Technology InfrastructureTopic 8 of 56

    Determining customer's Requirements

    3 minread
    562words
    Beginnerlevel

    📘 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:

    • Increase online sales

    🔑 4. Technical Requirements

    • Technology-related needs

    📊 Example:

    • Use of cloud computing

    🔑 5. User Requirements

    • Needs of end users

    📊 Example:

    • Easy-to-use interface

    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

    • Handle changes over time

    6. 🛠️ Techniques for Gathering Requirements

    🔧 1. Interviews

    • Direct discussion with customers

    🔧 2. Questionnaires/Surveys

    • Collect data from many users

    🔧 3. Observation

    • Study how users work

    🔧 4. Workshops

    • Group discussions

    🔧 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

    • Needs change over time

    🔧 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

    • Requirements = foundation of system design

    • Types:

      • Functional
      • Non-functional
      • Business
    • Process:

      • Gather → Analyze → Validate

    12. 📝 Likely Exam Questions

    ⭐ Short Questions:

    1. Define customer requirements.
    2. What are functional requirements?
    3. What are non-functional requirements?
    4. What is requirement validation?
    5. List requirement gathering techniques.

    ⭐ Long Questions:

    1. Explain the process of determining customer requirements.
    2. Discuss types of customer requirements with examples.
    3. What challenges are faced in requirement determination?
    4. Explain techniques for requirement gathering.
    5. Why is requirement analysis important?

    13. 📌 Quick Summary / Conclusion

    • Determining customer requirements is the first and most important step in IT system design.

    • It ensures:

      • ✔ Correct system development
      • ✔ Customer satisfaction
      • ✔ Cost efficiency

    👉 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.
    Previous topic 7
    Factors to consider in designing IT organizations and IT infrastructure
    Next topic 9
    Identifying System Components to manage

    Past Papers

    Open this section to load past papers

    Click on Show Past Papers to see past papers.
    On This Page
      Reading Stats
      Est. reading time3 min
      Word count562
      Code examples0
      DifficultyBeginner