Contact Us

Contact us if you have any questions or suggestions regarding Reqode. Use the form or write us a letter.

Breaking Down Requirements

Split project knowledge into small, linked documents.

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).

Artifact Types

There are three artifact levels available in Reqode. At each level, you can set up your own artifact types to structure product knowledge according to specifics of your product and processes. All artifact types, except for Feature and Module, are optional, and you can disable them for your product.

Top Level

Business Requirements Level

Optional artifact

Business requirement artifacts are used for high-level requirements from the business or users: use cases, business processes, business rules, and more.

System Level

Module

Required artifact

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

Required artifact

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.

Specifications Level

Entity

Optional artifact

Entities are used to describe the data model for the subject area.

User Interface

Optional artifact

Used for describing screens, forms, pop-ups, and other user interface items.

API

Optional artifact

Used to describe how subsystems interact with each other and with external systems.

Custom Artifacts

Optional artifact

Organizes additional artifacts based on your product’s specifics, such as events, notifications, configuration variables, instructions, and more.

Traceability

Breaking down knowledge into artifacts and linking them allows you to automatically get focused, relevant information both for manual analysis and for AI assistants.

Artifacts Structure