/

Developer Guide

User Stories

This page catalogues CrowdVision’s user stories and the personas behind them. Each story carries a MoSCoW priority — Must, Should, or Could — reflecting what’s load-bearing for the platform to function at all versus what refines the experience once it does. Nothing currently carries a Won’t; the backlog hasn’t yet had to cut scope.

Acceptance criteria here are functional: they say what must be true, not how fast. Every latency, throughput, or rate target lives on the Quality Attribute Scenario that owns it, and the stories it holds accountable link to it — a number stated in two places drifts in one of them. The two most load-bearing stories carry their criteria in full Gherkin on Acceptance Criteria, where the functional criteria and the QAS target meet in one executable file.


Conventions

User stories are expressed in a simple sentence, structured as follows:

“As a [persona], I [want to], [so that].”

Breaking this down:

“As a [persona]” — Who are we building this for? We’re not just after a job title, we’re after the persona of the person. Max. Our team should have a shared understanding of who Max is. We’ve hopefully interviewed plenty of Max’s. We understand how that person works, how they think and what they feel. We have empathy for Max.

“Wants to” — Here we’re describing their intent, not the features they use. What is it they’re actually trying to achieve? This statement should be implementation free — if you’re describing any part of the UI and not what the user goal is, you’re missing the point.

“So that” — How does their immediate desire to do something fit into their bigger picture? What’s the overall benefit they’re trying to achieve? What is the big problem that needs solving?


Personas

Stories

Account & Access

Building & Twin

Sensors & Alerting

Live Dashboard

AI Assistant