MANTIS-Platform Requirements or How to Make Sure the Platform Fulfils Partner’s Needs

One of the most important tasks to ensure flawless working on different work packages is to have fully consolidated requirements towards the MANTIS platform. Not only is it important to have all different requirements aggregated, but also to know in which project tasks those requirements will be addressed, by whom and how to manage those during the project lifetime. To handle this challenge with excellence, MANTIS partners decided to do a 4-step approach in requirement definition towards the MANTIS platform.

Defining User Scenarios & Deriving Requirements

In the MANTIS project, we do have specific use cases we later on want to test the platform against. Each of these use cases detailed their scenarios and related them to the MANTIS objectives. From there on, requirements in the form of a table were compiled. Those requirements cover functional, non-functional, technological and business needs. As a result, we had the first form of requirements which – of course- still needed unification and consolidation.

Extending Maintenance Use Case Requirements by MANTIS Partner Requirements

This task focused on what technology can and should be used for the user scenarios. The main task members therefore were the technology providing partners. We also expected requirements originating from technology push of the providers. Those additional requirements were the second form of requirements we had which – again, of course – still needed unification and consolidation. Nonetheless, correlations to the user scenario requirements were already identified and noted.

Requirements and Project Objects Consolidation

The platform requirements and the user scenario requirements were revisited for consistency and updates. Furthermore, a refinement of the requirements was performed based on the early sketches of the MANTIS architecture. As a result, 45 different requirement categories were identified, 27 of those categories were then identified as “not to be addressed inside of MANTIS”, since those categories mainly were basic requirements towards a general platform architecture and not MANTIS specific.


MANTIS requirements categories
MANTIS requirements categories


Refinement of the Requirements

As the last task, which is currently still running strong, we wanted to match all those 900+ requirements that were identified and defined to the 45 defined requirement categories. At the time of writing this article, the matching is completed and 900 requirements could be reduced to about 330 MANTIS specific requirements. Also, the MANTIS specific requirement categories were matched to the different project task, to make sure that the requirements will definitely be addressed.

So what’s ahead: Definition of MANTIS platform requirements is near its end. What’s left to do is to choose a good way to manage the requirements during projects lifetime. As it seems, this will be done by separating Excel sheets according to tasks and categories. This will keep management of requirements handy and easy.


Matching Requirements to MANTIS requirement categories
Matching Requirements to MANTIS requirement categories