Skip to main content
This path is for Business Analysts working post-award from solicitation materials, discovery notes, and stakeholder input.

When to use this path

  • You have a contract award, and you have conducted (or are conducting) discovery.
  • Your inputs are solicitation materials, interview notes, JAD session transcripts, and existing documentation.
  • You do not have a legacy codebase to analyze — or you have already analyzed it using Path B.

Set up your project for requirements development

1

Open your project

Work in the Prototype tab.
2

Upload your input files

Add the SOW, RFP sections, discovery notes, JAD transcripts, and interview summaries.
3

Organize into Requirement Folders

Group inputs by feature area or functional domain.

Generate user stories from solicitation materials

1

Write a prompt referencing your uploaded documents

For example: “Based on the attached SOW and discovery notes, generate user stories for the permit intake workflow. Include acceptance criteria for each story.”
2

Review for accuracy and completeness

Confirm the generated user stories reflect what’s actually in your source materials.
3

Iterate as needed

For example: “Add user stories for the document upload and verification steps.”

Generate a Requirements Traceability Matrix

Prompt the agent directly:
“Generate a Requirements Traceability Matrix that maps each requirement from the attached SOW to a user story and test case.”
Review the result for completeness and identify any gaps.

Generate compliance-ready documentation

  • “Generate acceptance criteria for each user story that include accessibility compliance requirements aligned to Section 508.”
  • “Generate a data model and workflow diagram based on the requirements we have developed.”

Prepare Phase 2 outputs for handoff to Phase 3

1

Save your outputs

Save all finalized user stories, the RTM, and supporting documentation as files.
2

Review your Requirement Folders

Confirm they reflect the final organization of your work.
3

Document open questions

Note any assumptions or unresolved items that need attention before System Design.
4

Proceed to Phase 3

Continue to System Design once your requirements are finalized.

Phase 3: System Design

Continue to the next phase.