Contact Us
Unlike a WIKI, where work is done with arbitrary documents without any restrictions, Reqode helps to keep project knowledge more structured and organized.
Information is stored as small, separate documents of different types (we call them artifacts). Each type is used for its own layer of project knowledge. E.g., entity specifications for the data model, UI screen specifications, and others.
Artifact types, templates, and their properties can be customized according to the specifics of your product.
Artifact can include a text description (with Markdown formatting and links to other artifacts), files, diagrams, and structured data (e.g., description of entity attributes or UI prototype).
Artifacts
Reqode allows you to follow different approaches to break down and organize requirements with various sets of artefacts. You can use only feature specifications, or you can complement them with data model descriptions, user interfaces, and other artifacts. Using separate artefacts makes the structure a bit more complex, but it greatly improves consistency and traceability.
Module
Module is a set of related features grouped together. Modules allow you to manage a set of features as a single item and get an abstract overview of the project.
Feature
Feature describes the requirements for a specific function or a particular feature of the software. It can have different subtypes for various kinds of features.
Data Entity
Entities are used to describe the data model for the subject area.
User Interface
Used for describing screens, forms, pop-ups, and other user interface items.
API Contracts
Used to describe how subsystems interact with each other and with external systems.
Custom Artifacts
Configurable artifacts based on your product and process specifics, such as events, notifications, configuration variables, user documentation, and more.
Traceability
Breaking down knowledge into artifacts and linking them allows Reqode to extract the relevant information both for manual analysis and for AI assistants.
