Example project to illustrate how requirements engineering and management can be implemented in a scientific context using OpenProject.
We use a structured hierarchy to ensure full traceability from high-level goals down to the source code:
Level Epics: High-level functional domains (e.g., Device Inventory).
Level Use Cases: Captured in OpenProject as Features. They describe how a user interacts with the system, including context and scenarios.
Level User Stories / Tasks:
User Stories: Functional (e.g., Metadata entry) and non-functional (e.g., Responsiveness) features from a users' perspective.
Tasks: Technical implementation steps or technical non-functional requirements (NFR).
Key Features of this Blueprint
Status Workflow: We distinguish between requirements being In Specification and Specified before they enter development.
NFRs: Non-Functional Requirements (Security, Performance, Legal) are explicitly tracked via Categories and dedicated Features, User Stories / Tasks.
Visibility & Progress: High-level progress is tracked in different views within the Work Packages module, as well as in the Roadmap, while daily execution happens on the Agile Boards.
How to get started
Check the 👉️ Wiki
Browse the 👉️ Work Packages
Visit the 👉️ Boards
Get in contact 👇️ and contribute your ideas!
This widget is currently empty.
This widget is not available.