A lightweight Business Analyst workflow prototype designed to transform stakeholder inputs into structured, traceable, and actionable requirements.
The project focuses on common challenges faced during requirement elicitation, including incomplete requirements, ambiguity, prioritization, traceability, and requirement changes.
Try the application:
https://huggingface.co/spaces/Sejal1703/GenAI-Requirements-Assistant
No installation is required. The prototype runs directly in the browser.
Stakeholder requirements are often incomplete, ambiguous, or difficult to translate directly into development-ready requirements.
Business Analysts need to:
- identify missing information
- clarify ambiguous requirements
- define functional requirements
- create user stories and acceptance criteria
- prioritize requirements
- maintain requirement traceability
- assess the impact of requirement changes
This prototype brings these activities together into a single lightweight workflow.
Evaluates a stakeholder requirement on a 0-100 scale using factors such as:
- Actor identification
- Action clarity
- Business conditions
- Measurable values or timelines
- Requirement detail
- Ambiguous terminology
Example:
Weak Requirement:
Make the refund process quick and easy.
Quality Score: 40/100
Improved Requirement:
Customers should be able to request a refund within 7 days after delivery if the order is damaged.
Quality Score: 100/100
Flags unclear or incomplete requirements and identifies areas that require further stakeholder elicitation.
Examples include:
- unclear actor
- missing business conditions
- missing measurable thresholds
- vague terms such as "quick", "easy", "soon", or "efficient"
Transforms stakeholder inputs into BA artifacts including:
- Business Requirement
- Functional Requirements
- User Story
- Acceptance Criteria
- Business Rules & Assumptions
- Clarifying Questions
Organizes requirements into:
- MUST - critical functionality
- SHOULD - important functionality
- COULD - optional enhancements
This helps demonstrate requirement prioritization during scope discussions.
Maps requirements across BA artifacts.
| Requirement ID | Requirement | User Story | Acceptance Criteria | Priority |
|---|---|---|---|---|
| FR-01 | Submit refund request | US-01 | AC-01 | MUST |
| FR-02 | Validate eligibility | US-01 | AC-02 | MUST |
| FR-03 | Track refund status | US-02 | AC-03 | SHOULD |
| FR-04 | Send confirmation | US-02 | AC-04 | SHOULD |
This provides visibility from functional requirements through validation criteria and priority.
Compares an original requirement with an updated stakeholder request.
Example:
Original Requirement
Refunds are allowed within 7 days after delivery.
Updated Requirement
Refunds are allowed within 14 days after delivery.
The tool detects:
Business rule threshold changed from 7 to 14.
It then identifies potentially impacted areas such as:
- Business rules
- Functional requirements
- Acceptance criteria
- Test scenarios
- User-facing communication
- Process validations
- Requirement Traceability Matrix
It also recommends BA actions such as updating documentation, reviewing linked requirements, communicating with stakeholders, and coordinating regression testing.
Stakeholder Requirement
↓
Requirement Quality Analysis
↓
Ambiguity Detection
↓
Functional Requirements
↓
User Story & Acceptance Criteria
↓
MoSCoW Prioritization
↓
Requirement Traceability Matrix
↓
Change Impact Analysis
- HTML
- CSS
- JavaScript
- Hugging Face Spaces
- GitHub
The application is intentionally lightweight and runs entirely in the browser without requiring heavy local installations.
- Requirement Elicitation
- Requirement Analysis
- Functional Requirement Documentation
- User Story Creation
- Acceptance Criteria
- Business Rules
- Gap & Ambiguity Identification
- MoSCoW Prioritization
- Requirement Traceability
- Change Impact Analysis
- Stakeholder Clarification
- Business Process Thinking
The current live version uses transparent rule-based logic to demonstrate the end-to-end BA workflow.
The architecture can be extended with a secure LLM/API backend for contextual requirement generation, semantic ambiguity detection, automated requirement classification, and more advanced change-impact analysis.
- Secure LLM integration
- Export requirements as BRD/User Story documents
- Automatic requirement version history
- Requirement dependency mapping
- Risk and dependency scoring
- Jira integration
- Stakeholder approval workflow
The objective of this project is not simply to generate text, but to demonstrate how requirement analysis activities can be structured into a lightweight digital workflow that supports Business Analysts throughout the requirement lifecycle.