Step 2: Functional Requirements
π Progress: Step 2 of 6 β±οΈ Estimated Time: 1 hour
Executive Summary
This step focuses on understanding the business context and user requirements for the IFS Knowledge Assistant. By analyzing the scenario and identifying key functional needs, youβll establish a clear foundation for your agentic AI solution that delivers tangible value to IFS employees and customers.
Home > AI Agent Challenge > Step 2 - Functional Requirements
- β¬ οΈ Previous: Step 1 - Principles (prerequisite)
- Next: Step 3 - Non-Functional Requirements β‘οΈ
This section is part of the IFS AI Agent Challenge. Here, youβll analyze the business scenario and user needs for the IFS Knowledge Assistant chatbot.
flowchart LR
A[π Start] --> B[π Step 1 Principles]
B --> C[π Step 2 Functional Req]
C -->|Current| D[π Step 3 Non-Functional Req]
D --> E[ποΈ Step 4 Solution Design]
E --> F[π Step 5 Integration]
F --> G[π Step 6 Presentation]
style C fill:#90EE90,stroke:#333,stroke-width:2px
π― Objective
Understand the business context, user needs, and high-level goals for the RAG chatbot solution.
π Activities
- Review the scenario below.
- As a team, discuss and answer:
- What are the main user needs and business drivers for the IFS Knowledge Assistant?
- What are the high-level inputs, processes, and outputs for this solution?
- What are the key constraints (e.g., private network, Azure AI Search, security)?
Scenario
Innovate Financial Services (IFS) wants to empower its employees by providing quick and accurate answers to questions about internal policies, procedures, and market analysis reports. They have decided to build an internal web-based chatbot, the βIFS Knowledge Assistantβ. This application needs to:
- Provide employees access to company information quickly and efficiently
- Answer questions based on internal documents, policies, and procedures
- Maintain strict security and compliance requirements
- Scale to support thousands of employees globally
- Integrate with existing Azure infrastructure and systems
Functional Requirements
User Stories
As an IFS employee, I want to:
- Ask natural language questions about company policies and receive accurate answers
- Upload documents that the system can then answer questions about
- See citations for where information is sourced from
- Use the chatbot from my workspace without having to access external systems
- Get relevant, contextualized answers that account for my role and department
- Have conversation history preserved during a session for context continuity
- Access the system securely with my existing corporate credentials
System Capabilities
The IFS Knowledge Assistant must:
- Retrieve and index content from:
- SharePoint document libraries
- Azure Storage accounts
- HR policy documents
- Financial procedure manuals
- Market analysis reports
- Internal wikis and knowledge bases
- Process and understand:
- Natural language queries
- Document context and relationships
- User intent and search refinements
- Generate and deliver:
- Accurate, relevant responses
- Source citations and confidence levels
- Follow-up question suggestions
- Document access links when appropriate
Integration Points
The solution must integrate with:
- Identity systems:
- Azure Entra ID for authentication
- Role-based access controls
- Content repositories:
- SharePoint Online
- Azure Blob Storage
- Microsoft 365 applications
- Security systems:
- Azure Key Vault for secret management
- Azure Private Endpoints for secure connectivity
- Logging and monitoring solutions
- Frontend interfaces:
- Web application interface - Teams integration (future phase)
- Mobile accessibility (future phase)
Success Criteria β
By the end of this step, you should have:
- β Identified the key business drivers for the IFS Knowledge Assistant
- β Documented core user needs based on the scenario analysis
- β Defined primary use cases that the agent should support
- β Listed integration requirements with existing systems
To successfully complete this step, ensure you have a clear understanding of what the IFS Knowledge Assistant needs to accomplish from a business and user perspective.