En
Contact Us
Requirement as Artifact
Artifact Types
Almware provides several general types of artifacts, which are organized in separate directories and have different basic properties and possibilities of relationship. In addition, you can add your own subtypes for each artifact to organise your requirements more effectively.
Requirements
The business requirements artifact is used to define high-level requirements. It can be used for use cases, business rules, business objectives.
The module artifact is a set of software requirements. Modules simplify requirements handling by grouping sets of related requirements and allow to work with them as a single entity.
The software requirements artifact is used to define low-level requirements. It can describe particular software function or non-functional requirement.
Software Specifications
Data Entity is used to describe project data model. It describes entities (like User, Product, Invoice etc.), reference data, value lists.
The user interface artifact is used to define user interaction points. It can describe entire screens, forms, popups and their states.
The software interface artifact is used to define programming interface of a system. It can describe internal or external API and other types of interaction between software systems.
Custom artifact can be used to organize a directory of specific system artifacts that need to be traced. These can be events, notifications, configuration variables, etc.
