The Requirements Package Browser provides you with a view of the Package tree. A Requirements Package is organized as a hierarchical tree with Requirement Categories and Requirements representing nodes.

Stand-alone application systems are in the process of slowly disappearing. In the services-oriented world, systems and applications are interrelated. As a consequence, we have designed Requirements that are reusable in many different contexts.

Licensees of an Evaluation Specification can import Requirements from a Requirements Package using drag & drop. We consider this a superior approach compared to providing bloated Evaluation Specifications, which would require you to manually remove hundreds of irrelevant Requirements.   

The Requirements Package Browser is intended to provide you with an idea of how a Requirement Package is structured, without having to download the Evaluator's Application Suite (EAS) first.

Please note that a license is required to view the contents of the Requirements Package. Without a valid license, only the first 10 Requirements will be displayed without restrictions. All remaining Requirements will contain '***hidden' in some fields to indicate that a license key has not been provided.

Requirements Packages are constantly enhanced and updated. The Requirements Package Browser allows you to see the Requirements Package growing.

Users with a valid license will be able to view the Package tree in the Evaluation Specification Editor (ESEdit) application and import Requirements into Evaluation Specifications. An Evaluation Specification is input to the RFP (Request For Proposal) generator. An RFP forms the basis for software evaluation and selection. 

The Package tree is available for viewing here .