Introduction
This reference article explains the different types of artifacts used in the Requirements Management module of Easy8. An artifact is the core unit for capturing and organizing requirements—just as tasks are for managing work.
Artifact Types
| Artifact Type | Description |
|---|---|
| Section | Used to group and organize related requirements into meaningful categories. Sections provide better structure and context for the overall requirements tree. |
| Requirement | The main entity in requirements management. Requirements describe the functionality or condition that must be fulfilled. They can come from stakeholders, user scenarios, or technical specifications. |
| Change request | A request to modify something previously approved. This may affect the project's scope, budget, resources, or timeline. Change requests should be reviewed carefully before approval. |
Additional Terms in Requirements Management
| Term | Explanation |
|---|---|
| Task | Tasks can be linked to artifacts for traceability and implementation tracking. |
| Responsible | The user assigned to oversee or complete the artifact. |
| Acceptance criteria | Defines what must be done or achieved to consider the requirement as fulfilled. |
| Description | A field used for additional information, comments, or references related to the artifact. |
Conclusion
Understanding the different types of requirements artifacts and their supporting elements helps you build a well-structured, traceable, and effective requirements system within your project. Use sections to organize, requirements to define needs, and change requests to manage adjustments along the way.
