inteGREAT is a meta model driven requirements engineering platform that is highly configurable in order to meet users’ needs. This allows an inteGREAT implementation to adhere to the best practices and methodologies of the organization where it is being implemented. inteGREAT comes with predefined configurations to support the Agile, Scrum, CMMI, Iterative and Waterfall development models. However, organizations often use their methodology or hybrid models that evolve over time, in order to fit their organizational needs.
The ability to configure inteGREAT to align with your environment and project management disciplines, leads to an easier adoption of the technology by direct and indirect users of the system. inteGREAT provides the ability to configure the system in the following ways:
inteGREAT provides the ability to define Object Dimensions, Objects, Properties, Relations and Relation Properties. Each piece of information in inteGREAT is referred to as an Object. Objects are grouped into dimensions and Objects have properties. Objects can be linked to each other, called Relations. Relations can have properties as well. The overall object configuration is called a Syntax. Users can define multiple Syntax models for different project types. Here is an example of an object taxonomy:
External System Object, Property and Relation Mapping
inteGREAT provides the ability to map inteGREAT Objects to external system objects such as Microsoft Team Foundation Server Work Items and HP Quality Center Requirements & Test Cases. This mapping is dynamic in the sense that if the definition in the external system or object configuration in inteGREAT changes, the two system can continue to seamlessly interchange information bi-directionally. This external configuration framework is extensible, allowing other systems to be integrated with inteGREAT; be it in-house systems or a 3rd party applications.
Wizards provide a guided approach to requirements elicitation and authoring. inteGREAT provides the ability to configure wizards for specific tasks.
The Structured Documents and Reports that inteGREAT produces are fully configurable by using Word and Excel templates. Users can define exactly what data needs to be extracted from inteGREAT and how best to present that information with Word and Excel. This allows users to define nearly identical output to the existing document templates. Examples of pre-defined documents include:
Project level properties can be defined such as Executive Summary, Expected Benefits and others. Additionally project level reference properties, such as lists and trees, can be defined as requirements of the project. They may reference these properties within Requirements and other Objects. An example of this may be Area and Iteration – which are defined as possible values at the project level and as values set for each of the Requirements.
Specification Type Configuration
Users can define different types of specifications consisting of Object types, Related Wizards and Documents that can be produced. One may define a web service specification to formalize the definition of web services by following a guided approach that produces consistent documentation, while having the ability to reuse the specification across multiple projects.
inteGREAT allows users to author using Word & Excel documents. Templates can be defined where inteGREAT populates Word or Excel templates with project content for further authoring – this content can then be loaded back into inteGREAT. Similarly legacy content from Word & Excel can be loaded into inteGREAT either by tagging the documents or by defining Style Maps to load content into inteGREAT based on document styles.