Contact us

We'll show and tell you about the system, give you an account. Fill out the form or write us.


Artifacts and instruments



The domain model allows to systematize related artifacts of the same subject area and subareas.


A separate software component of a multi-component software system (e.g., backend, microservice, frontend, mobile application and others).


An artifact describing the type of users according to the user and functional requirements.

Requirements Artifacts

User Requirement

Top-level requirement that describes how the system works in the context of value to the end user.

Functional Requirement

Detailed description of the specific system function, including acceptance criteria, associated requirements, QA and implementation details.

Data Requirement

Software data model used in implementation of functional requirements.

Business Rule

External and internal business and technical rules, restrictions and conditions affecting software requirements.

UI Requirement

Description of user interfaces (e.g. list, forms, etc). Can be accompanied by images and links to external prototypes.

Non-functional Requirement

Requirements not related to the behavior and functions of the system. Non-functional requirements include requirements such as quality criteria, stress and fault tolerance and others.

Management Artifacts


Release is the distribution of the new version of a software. Used for top-level development planning, including a set of change requests and tasks scheduled to be done by a certain date within the current version.

Change Request

A change request describes a new functionality or a significant change in existing functions. Change request combines requirements changes and tasks to implement these changes.


Issues, bugs or tasks for the project team members to implement. Tasks can have different workflow and stages of execution depending on the type of issue.


A classifier, reflects the version of the software application or the entire project.

Design Artifacts

Software Unit

A software unit is a smallest testable part of a software system. It typically refers to a specific function or module within a larger program.

Data Unit

A data source artifact used to implement functional and data requirements. Can be a table in a relational database, file (or set of files) in a file system, or document in a NoSQL repository.

API Method

API method used for intra-system interaction between applications or interaction with external systems.

Software Library

External software library used to implement the software.


Test Cases

Scenario and data for testing a single function or set of functions of a functional requirement.

Test Run

The result of the test case execution in the specified environment and version.

Test Suite

The test suite groups test cases and defines the goals and objectives of testing.

Fighting Uncertainty in Software Development

Request Access