Content
View differences
Updated by Marc Hanisch 18 days ago
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:
1. **Epics (Research Goals):** High-level functional domains (e.g., Device Inventory).
2. **Use Cases (Activities):** Captured as **Features**. They describe how a user interacts with the system, including context and scenarios.
3. **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 NFAs.
**Key Features of this Blueprint**
* **Status Workflow:** We distinguish between requirements being _In Specification_ and _Specified_ before they enter development.
* **NFAs:** Non-Functional Requirements (Security, Performance) are explicitly tracked via **Categories** and dedicated **Features, User Stories** or **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 \[\[requirements-engineering-and-management-in-scientific-projects|Wiki\]\]
* Browse the [Work Packages](https://projects.academiccloud.de/projects/agile-re/work_packages)
* Visit the [Boards](https://projects.academiccloud.de/projects/agile-re/boards)
We use a structured hierarchy to ensure full traceability from high-level goals down to the source code:
1. **Epics (Research Goals):** High-level functional domains (e.g., Device Inventory).
2. **Use Cases (Activities):** Captured as **Features**. They describe how a user interacts with the system, including context and scenarios.
3. **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 NFAs.
**Key Features of this Blueprint**
* **Status Workflow:** We distinguish between requirements being _In Specification_ and _Specified_ before they enter development.
* **NFAs:** Non-Functional Requirements (Security, Performance) are explicitly tracked via **Categories** and dedicated **Features, User Stories** or **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 \[\[requirements-engineering-and-management-in-scientific-projects|Wiki\]\]
* Browse the [Work Packages](https://projects.academiccloud.de/projects/agile-re/work_packages)
* Visit the [Boards](https://projects.academiccloud.de/projects/agile-re/boards)