inteGREAT supports the definition of hardware requirements. Since inteGREAT is built on a meta model, the taxonomy is configurable to meet specific business needs. For example, one configuration allows users to define systems, subsystems, components, features, test cases and test plans, along with goals, user scenarios, use cases, requirements, and building blocks.
Each object type in turn has a number of associated properties which are also configurable.
Predefined document templates have been configured to include
Reuse specifications (groupings of requirements)
Specifications that have been defined can then be reused across multiple projects; for example a component specification may be the same in multiple subsystems. Thus by creating a library of specifications, users may speedup requirements engineering while creating consistent artifacts.