Contact us if you have any questions or suggestions regarding Almware. Use the form or write us a letter.
Requirements as Artifacts
Almware adopts a "requirements as artifacts" approach, which implies the decomposition of requirements into separate interrelated and traceable artifacts.
Artifact Types
Almware provides several general types of artifacts, which are organized in separate directories and have different basic properties and possibilities of relationship.
You can add your own subtypes for each artifact to organise your requirements more effectively.
High-level Requirements
Business Requirements
Business requirement defines high-level requirement such as use cases, business rules, business objectives.
Software Requirements
Modules
Module is a set of interrelated features (functions).
Features
Feature defines particular decomposed function of the software.
Requirements
Requirement defines the functional or non-functional characteristic of the feature.
Software Specifications
Data Entities
Data Entity describes data entitiesa and relations within project data model.
User Interfaces
UI describes user interaction points, e.g. entire screens, forms, popups etc.
Software Interfaces (API)
Describes programming interface of a system, e.g. internal or external API.
Custom Artifacts
Сan be configured to organize additional artifacts you need to trace. E.g. events, notifications, configuration variables, etc.
Traceability
This approach allows you to trace the relationship between artifacts and control the development process, from requirements gathering, to development and quality assurance.