URS Parser

The URS Parser extracts structured requirements from unstructured text.

When to Use

When you have a requirements document, email, or scope text that needs to be broken into structured FR/NFR/constraint rows with priority and source citation.

How to Use

1. Click the URS Parser tab under AI Pillars
2. (Optional) Enter a document title
3. Paste the document text — keep input under ~10 pages for best results
4. Click Analyze (typical latency: 3-5 seconds)

What You Get

Each requirement is returned with:

• ID — REQ-001, REQ-002, etc.
• Category — functional / non_functional / constraint / assumption
• Title and Description
• Priority — Critical / High / Medium / Low
• Source — back-reference to the original FR/NFR/C label

Golden-Path Input

2. Functional Requirements
FR-01  Public users shall submit complaints via mobile, web, and WhatsApp.
FR-02  Each complaint receives a unique ticket ID in MPSJ-YYYYMMDD-NNNNN.
3. Non-Functional Requirements
NFR-01  P95 latency shall not exceed 2 seconds.
4. Constraints
C-01  Must integrate with existing MPSJ SSO (LDAP).

WARNING

Outputs are scratchpad — they live only in your browser tab. Copy or screenshot anything you want to keep.