Our Configurations

The following predefined configurations are currently available for our ReqSuite®. You can adapt all configurations completely and easily to your needs or create your own configurations from scratch. See here how easy this works.

Simple Sample Configuration

Context & Target Group

This configuration is aimed at companies that want an overview of the basic functionality of ReqSuite® and want to gain insights into a simple requirements management in the context of IT systems.

Benefits

  • Easy entry into ReqSuite® without having to deal with the configuration in more detail beforehand
  • Suggestions for designing your own requirements management

Contents & Results

You can use this configuration to describe and manage the following requirements types or information:

  • (Project) Objectives
  • Business processes (incl. process diagram)
  • Use cases (incl. use case diagrams)
  • Functions / functional requirements
  • Glossary terms

The contents of a project based on this configuration can be exported to a Word document with a corresponding structure. Furthermore, you can export the contents to Excel, JIRA, TFS, or ReqIF.

Try out now

Requirements Management according to IREB

Context & Target Group

This configuration is aimed at companies that want to standardize and optimize their requirements management in the context of their product development. The configuration is kept quite simple in order to support the entry into a systematic requirements management. Selected best practices from the IREB standard for Certified Professional for Requirements Engineering (CPRE) are used.

Benefits

  • Easy access to systematic best-practice requirements management
  • Increased efficiency and quality through structured, guided, traceable, standardized and centralized handling of requirements
  • Suggestions for designing your own requirements management

Contents & Results

You can use this configuration to describe and manage the following request types or accompanying information:

  • (Project) Goals (optional with garget tree)
  • Contextual elements such as stakeholders, third-party systems, workflows, etc.
  • System or the development object
  • System components (optional with component diagram)
  • Use cases (incl. use case diagram)
  • Functional requirements (optional with UML diagram)
  • Quality requirements
  • Constraints
  • Glossary terms

The contents of a project based on this configuration can be exported to a Word document with a structure based on the ISO 29148-2011 standard. Furthermore, you can export the contents to Excel, JIRA, TFS, or ReqIF.

Try out now

Customer Requirements Specification

Context & Target Group

This configuration is aimed at companies that want to formulate their requirements for a system to be procured and, if necessary, to put them out to tender. The configuration addresses all important requirement and content categories, which are of relevance within a professional system procurement and tendering.

Benefits

  • Good work support and guidance in the elaboration of specifications (also for less experienced project participants)
  • Reduced risk of misunderstandings between client and contractor
  • Suggestions for the design of your own requirement specification process

Contents & Results

This configuration allows you to describe and manage the following request types or information:

  • Customer
  • Project dates / time schedule
  • System / procurement object
  • System context (incl. context diagram)
  • Relevant external systems, stakeholders and workflows (incl. process diagram)
  • Constraints
  • Motivating as-is situation including challenges
  • (Project) Goals
  • Required services
  • Excluded topics
  • Use cases (incl. use case diagram)
  • Required system functions and data objects (including data model)
  • Quality requirements
  • Interfaces to be integrated
  • Glossary terms

The contents of a project based on this configuration can be exported to a Word document with a structure based on best practices. Furthermore, you can export the contents to Excel, JIRA, TFS, or ReqIF.

Try out now

Requirements Management according to Volere (coming soon)

Context & Target Group

This configuration is aimed at companies that want to standardize and optimize their requirements management in the context of their development projects. It is usable in the context of market-driven development as well as in the context of individual software development. The configuration is very comprehensive and is based of the well-known Volere template.

Benefits

  • Full-fledged best-practice requirements management approach including related project management topics
  • Increased quality through structured, guided, traceable, standardized and centralized handling of requirements
  • Suggestions for designing your own requirements management

Contents & Results

You can use this configuration to describe and manage the following request types or accompanying information:

  • Project
  • Stakeholders
  • Goals
  • Development phases
  • Tasks
  • Risks
  • Costs
  • System context
  • Facts
  • Assumptions
  • Constraints
  • Business use cases
  • Business rules
  • Business data
  • Product use cases
  • Several Types of requirements incl. e.g.,
    • Functional requirements
    • Usability requirements
    • Performance requirements
    • etc.
  • Off-the-shelf solutions
  • Solution ideas
  • Problems
  • Glossary terms

The contents of a project based on this configuration can be exported to a Word document with a structure similar to the Volere template. Furthermore, you can export the contents to Excel, JIRA, TFS, or ReqIF.

Try out now

Offer Preparation & Solution Specification

Context & Target Group

This configuration is intended for companies that want to create an offer or a solution specification based on the requirements of their customers. The configuration is deliberately kept quite simple in order to be able to be used in different industries (hardware, software, services).

Benefits

  • Good work support and guidance in preparing offers
  • Greater transparency through direct reference to underlying customer requirements
  • Suggestions for designing your own offer process

Contents & Results

You can use this configuration to describe and manage the following requirements types or information:

  • Customer / Client
  • Motivating situation
  • Customer requirements
  • Proposed solution
  • Solution elements (incl. properties and diagrams)
  • Prices and quantity structures
  • Conditions
  • Project phases (incl. schedule)
  • References
  • Glossary terms

The contents of a project based on this configuration can be exported to a Word document with a corresponding structure according to the aforementioned categories. Furthermore, you can export the contents to Excel, JIRA, TFS, or ReqIF.

Try out now

Requirements-driven IT Portfolio Management (coming soon)

Context & Target Group

This configuration is aimed at companies that want to continuously develop their internal IT on the basis of demands from their business units. The configuration is divided into a sub-configuration for a rough description of requirements (demands) and a further sub-configuration for the derivation of detailed business concepts based on these requirements.

Benefits

  • Good work support and guidance in the collection and management of demands as well as in the creation of related technical concepts
  • Greater transparency through cross-project status and impact control
  • Suggestions for designing your own demand and portfolio management

Contents & Results

You can use this configuration to describe and manage the following requirements types or information:

  • Demands and corresponding cost-benefit evaluations
  • Main changes
  • Affected organizational units, business processes, and systems
  • Releases

Furthermore, as part of the business concept, the following contents are addressed:

  • Business requirements
  • To-be business process
  • Automated and supported business activities
  • User Stories
  • Interface requirements

The contents of a project based on this configuration can be exported to Word documents experessing either the demand profiles or the detailed business concept. Furthermore, you can export the contents to Excel, JIRA, TFS, or ReqIF.

Try out now

Requirements Management according to SCRUM

Context & Target Group

This configuration is aimed at companies that want to standardize and optimize requirements management in the context of their agile product development. The configuration is deliberately kept slim in order to fit the concepts of agile development. For this purpose, common concepts from SCRUM are used.

Benefits 

  • Easy access to systematic requirements management within SCRUM
  • Increased efficiency and quality through structured, guided, traceable, standardized and centralized handling of requirements
  • Suggestions for the design of your own (agile) requirements management

Contents & Results

You can use this configuration to describe and manage the following requirements types or information:

  • Product (Vision)
  • Stakeholders / Personas
  • Themes
  • Epics
  • Features
  • User Stories
  • Sprints
  • Acceptance tests
  • Glossary terms

The contents of a project based on this configuration can be exported to a Word document. Furthermore, you can export the contents to Excel, JIRA, TFS, or ReqIF.

Try out now

Enterprise Architecture Management according to TOGAF® (coming soon)

Context & Target Group

This configuration is aimed at companies that want to standardize and optimize the way of managing their enterprise architecture documentation. The configuration is based on the well-known TOGAF® framework with some smaller modifications to better fit ReqSuite® capabilities.

Benefits 

  • Easy access to systematic enterprise architecture management
  • Increased efficiency and quality through structured, guided, traceable, standardized, and centralized handling of architectural artifacts
  • Suggestions for the design of your own enterprise architecture management

Contents & Results

You can use this configuration to describe and manage the following requirements types or information:

  • Enterprise
  • Organizational units (incl. Organization chart)
  • Actors and roles
  • Drivers
  • Goals and objectives
  • Business processes (incl. Process maps and process diagrams)
  • Functions and events
  • Business services
  • Business objects (incl. Class diagrams)
  • Products
  • Software services
  • Data components and databases (incl. Class diagrams)
  • Application components and platform components (incl. Component diagrams)
  • Application software and  platform technology (incl. Deployment diagrams)
  • Locations
  • Change projects
  • Requirements, assumptions and solution elements

The contents of a project based on this configuration can be exported to a Word documents describing the enterprise architecture or the requirements for change projects. Furthermore, you can export the contents to Excel, JIRA, TFS, or ReqIF.

Try out now