BFH Requirements Platform

About this platform

Thinking about requirements together — trilingual, versioned, link-friendly.

A shared workspace for capturing what an internally-developed application should do: who uses it, what those people need, and how it behaves — in German, French and English at the same time. Instead of Word documents that age the moment kickoff ends, you cultivate a living model of the requirements here.

  • Define requirements collaboratively. Product owners, developers, sponsors and end users edit the same models — without losing translations or cross-references along the way.
  • Make existing and emerging roles visible. Personas are modelled with inheritance: shared behaviour at the top, special cases below. New roles appear next to the established ones — not hidden inside one person's head.
  • Document live, not after the fact. Every story, process, business rule and data object has a stable URI. Your own application can link from a help icon straight to the current explanation — no separate manual to maintain.
3
Apps
3
Personas
0
Stories
1
Processes
0
Nodes
0
Sequence flows
0
Business Rules
0
Data Objects
0
Statuses
0
Phases
1
Users

Persona hierarchy

Inheritance across all apps — a child persona inherits its parent's properties.

  • User
    #1
    common
    Any user of a target application.
    • Authenticated User
      #2
      common
      Signed-in user with a persistent identity and personalised state.
    • Visitor
      #3
      common
      Anonymous visitor who has not signed in.

Common Personas

#1
Base personas that other app personas can inherit from.

User

#1
Any user of a target application.

Processes

Authenticated User

#2
Signed-in user with a persistent identity and personalised state.

Visitor

#3
Anonymous visitor who has not signed in.

Order System

#2
Online ordering platform for B2B customers.

No personas defined yet.

HR Portal

#3
Staff administration for Muster AG.

No personas defined yet.