ScholarQuill logoScholarQuillUniversity Notes
My Semester
Explore Notes
Past Papers12 New
Video CoursesNew
Search
Settings
Study Tools
GPA/CGPA Calculator
Schedule & To-Do
Student Portal
Contact
Contact
ScholarQuill logo
My Semester
Explore Notes
Past Papers12 New
Video CoursesNew
Search
Settings
GPA/CGPA Calculator
Schedule & To-Do
Student Portal
Contact
ScholarQuill logoScholarQuillUniversity Notes
Study PortalITEC3128Determining Customer R…
Ctrl + K
Login
Explore
Search
Semester
Papers
CGPA
    ITEC3128

    Information Technology Infrastructure

    Progress0 / 56 done
    Topics56
    1Definitions and Infrastructure management activities2Evolutions of Systems since 1960s (Mainframes-to-Midrange-to-PCs-to-Client-server computing-to-New age systems) and their Management3Growth of internet, current business demands and IT systems issues4Complexity of today's computing environment5Total cost of complexity issues6Value of Systems management for business7Factors to consider in designing IT organizations and IT infrastructure8Determining customer's Requirements9Identifying System Components to manage10Exist Processes, Data, applications, Tools and their integration11Patterns for IT systems management12Introduction to the design process for information systems
    13Complexity of current computing, multiple technologies, multiple vendors, multiple users14e-Waste disposal15Total cost of ownership
    16Common tasks in IT system management17Approaches for organization Management18Models in IT system design19IT management systems context diagram20Patterns for IT system Management21Information system costs and benefits22Capital budgeting for information system23Real Options pricing models24Limitation of financial models
    25IT services continuity management26Capacity management27Availability management and service desk
    28Service support process29Configuration Management30Incident management31Problem management32Change management33Release management
    34backups, Archive, Recovery, Disaster recovery35Space management36Hierarchical storage management37Network attached storage38Storage area network39Bare machine recovery40Data retention41Database protection
    42Introduction Security43Identity management44Single sign-on45Access Management46Basics of network security47LDAP fundamentals48Intrusion detection49Firewall50Security information management
    51Introduction to Cyber Ethics52Intellectual Property53Privacy and Law54Computer Forensics55Ethics and Internet56Cyber Crimes
    3 min read
    Topic 8 of 56
    Topic Study Note Illustration
    08

    Determining customer's Requirements

    Subject: Information Technology Infrastructure

    πŸ“˜ 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 view and download past papers

    Click on Show Past Papers to load available exam papers.

    Reading Progress
    0%
    3mremaining
    562words
    Beginnerlevel
    On This Page

    No headings found

    Study Toolkit

    Subject Portal

    Information Technology Infrastructure