Documenting formats

It's convenient to use various formats (store methods) for collection and documenting requirements depending on the situation, selected development process, team members’ qualification, etc. Devprom ALM offers wide possibilities for documenting requirements.
Type of requirements Documenting formats
Primary (custom) requirements

Arbitrary text - requirement is formulated in the user's language (issues, queries, change requests).

User story - text is written in a certain way, reflecting a goal and business context of required functionality.

Business requirements

Files received from external sources (regulations, laws, correspondence, etc.)

Hierarchically structured requirements (documents) with verbal description of business processes, business rules and business limitations.

Requirements written in the form of business models, e.g., with BPMN notation.

System requirements

Technical specification is a document that contains requirements of different types and a common text.

Specification is a document that contains requirements of one type regarding one subsystem.

Use case is a requirement that is written in a certain way describing interaction with system.

UML models are requirements to information, structural and behavioral aspects of the system written in the well-known modeling language.

UI layouts - requirements to user interface.

WYSIWYG editor allows you to document:

  • Mathematical formulas
  • UML models - by means of PlantUML language, or a tool for building draw.io models
  • BPMN models, IE models and other types of charts - by means of a tool for building draw.io models