| Rommana | |
General | ||
Platform | Server: Windows 2003, 2008, Vista, XP, Windows 7 Client: IE6 or higher | Server: AIX, Linux, Sun Solaris, Windows (2000, 2003) Client: IE6, not possible to work with IE9 or higher |
Architecture | Rommana does not require any specific architecture other than the server must be running IIS. | HP recommends a 3-tiered approach: Tier 1 - Load Balancer (Depending on your organization's network structure, the Load Balancer may require purchasing additional licenses). Tier 2 - Application - Supported platforms are JBoss (which requires subscription and maintenance costs), Websphere (license cost associated) and Weblogic (license cost associated). Tier 3 - Database - Supported platforms are Oracle or SQL Server, both of which require licenses. There is also a 4th tier that normally required but is not mentioned in the documentation, and that's the File Repository. |
Data Base Used | | |
Integration | Rommana is a fully integrated system that uses one single repository (SQL Server) and one Common User interface to support all 6 components listed under features | |
Methodology Supported | Rommana supports the following methodologies: - Scenario Bases Development and Testing (SBDT™) - Requirement Based Project Management (RBPM™) | No specific methodology support. Quality Center needs to be customized to work as you need. |
Requirement Management Features | ||
Custom Attributes | Yes. | Yes. |
Associating Models, files, and artifacts to requirements | Yes. Rommana allows the use of models and artifacts such as decision tables, state models, process flows, user interface and screen prototypes, etc to provide more details for a requirement or a group of requirements. The use can define any type of model as appropriate. Rommana by default sort the requirements by functional and non-functional requirements. | You need to know how to set this link among these objects, otherwise when you try to get metrics from dashboard your results will not be trustable. |
Requirement Versioning | Yes, Rommana maintains different versions of the same requirement as requirements are changed based on change requests. | |
Associating Use Cases with Requirements | Yes. Rommana allow defining use cases for a requirement to provide more details. Use cases can be changed any time to reflect changes in the requirement. The Use Case Management component of Rommana supports all details of a Use Case Based requirement process. | Quality center does not support Use Cases. Quality Center only support requirements and then you link them directly to the test cases. There is a gap, because scenarios (use cases) are not documented. |
Associating Tasks with Requirements | Yes. Rommana allows associating project tasks to a requirement or a group of requirements. These tasks can be almost any thing that the project team needs to do in order to deliver the requirement. Tasks are defined by the user. Based on the specific methodology they are using. The purpose is for the Project Management component of Rommana to provide effort and cost estimation as well as progress for each requirement or a group of requirements. | There is no specific method to track tasks. |
Associating Project Risks with Requirements | Yes. | |
Associating Actions with Requirements | Yes. | There is no specific method to track action items. |
Importing requirements from Word documents | Yes. | Yes. Quality Center supports a Microsoft Word template and Excel template for importing Requirements. |
Breaking requirements down to scenarios | Yes. | There is no support of the concept of scenarios. You need to do a detailed information in the same module “Requirements”. And you can get a mess of trees. |
Planning requirements for different releases | Yes. | Quality Center introduced |
Associating Change Requests to requirements | Yes. | |
Test Management Features | ||
Methodology | Rommana uses a scenario-based test design methodology | No specific methodology support. You need to configure one, do codification on it. |
Defining Test Case based on Scenarios | Rommana supports creating and grouping test cases by scenarios | No support of scenario based test design. Quality Center has a module “Test Plan” dedicated to create test cases. Not scenarios. |
Defining Test Cases based on Use Cases | Yes. | No support of Use Cases |
Separating Test Cases from Test Scripts | Yes. Rommana enforces data-driven test design by separating the Test Case, which consists of input, Pre-Conditions, Output, and Post-conditions, from the Test Script, which is merely the set of steps to be followed to run a group of test cases (a Test Set). | A Test Case in |
Grouping Test Cases into a Test Set that uses the same Script | Yes. To minimize the number of test scripts, | |
Allowing a Test Case to be moved to a different Test Set. | Yes. User can move a Test Case from on Test Set to another any time. The Case will then use the script defined for the new Test Set. | Yes. A user can move a Test Case to another Test Set. However, the steps and all other elements in the Test Case remain the same. |
Defining Pre-conditions and Post-conditions for each Test Case | Yes. | With customization, Quality Center can define pre-conditions and post-conditions. You need to create these fields in the feature “Customize”, it takes a couple of minutes to do this. |
Maintaining the relationship from a Test Case back to Scenarios, Use Cases, and Requirements. | Yes. Test Case Traceability in | No support of Scenarios or Use Case. Quality Center only keeps traceability from Requirements to the Test Cases. |
Allowing a test Case to be moved to a different Requirement, a different Scenario, or a different Use Case. | Yes. When moving a test case to a different requirement, the user will need to specify the Use Case and/or the Scenario from those defined for the new requirement. | Links between entities can be defined and deleted at any time in |
Providing statistics for each Test Set regarding number of Test Cases passed, failed, or not executed yet as well as % of completion and % of readiness for release | Yes. | Yes. |
Providing statistics for each requirement regarding number of Test Cases passed, failed, or not executed yet as well as % of completion and % of readiness for release | Yes. | Yes. |
Providing the option to open an Issue Report when a Test Case fails | Yes. When a test case is marked as Fail, Rommana gives the option to open an Issue Report and it fills in some info from the failing test case. | Yes. |
Enforcing the association between Test Cases and Issue Reports as the status of either changes | Yes. When a test case is marked as pass, if there is any issue report associated with the test case still open, Rommana displays a warning and give the option to close the issue report. | |
Ad hoc Test | Yes. Rommana allows creating a test on the fly without following the Rommana Scenario Based methodology. However, an Ad hoc test may optionally have a related requirement, a related use case, or a related scenario | Quality Center allows Test Case creation through its standard interface. You only need to create a special folder in the tree menu for this purpose. |
Defect/Issue Management | ||
Enforcing the association between Test Cases and Issue Reports as the status of either changes | Yes. When a test case is marked as pass, if there is any issue report associated with the test case still open, | |
Enforcing Impact analysis | Yes. | Comments are an optional field in the Defects module in |
Issue Report Lifecycle | Yes. | Yes. |
Ad hoc Issue Reports | Yes. Rommana allows creating an issue report that is not based on a specific test case. However, an Ad hoc issue report may optionally have a related requirement, a related use case, a related scenario, or a related Ad hoc test. (Release 1.1) | Through customization, |
Use Case Management | ||
| · Define use cases to provide more details for a requirement · Define use case scenarios for both development and testing · Auto-validate use cases for completeness · Maintains the traceability between Use Cases, Scenarios and Test Cases | Not Supported |
Project Management | ||
| · Allocate and manage project resources, roles, responsibilities and access rights. · Create and manage project task for both development and testing on the project level as well as on the requirement level. · Create and maintain action item lists for both development and testing effort · Manage risks throughout the project for both development and testing on the project level as well as on the requirement level. · Create and maintain project timeline for all project tasks for both development and testing. · Create and maintain cost and time estimates for both development and test tasks either on the projects level or the requirement level. · Manage product release and features included in each release | Not Supported as 100%. But: · Maintain certain traceability on the test components you create, but not linked automatically. · You can manage releases in “Release” module. · You can execute test cases based on risks. · You cannot do estimation on. · You can allocate and define roles, but only developers and testers. You need to modify code if you desire more roles. |
Change Management | ||
| · Create change requests either based on an existing requirements or just as a new feature · Associate change requests to existing requirements to create new versions of the requirement · Allow developers to provide impact analysis information for each change request for the test team to use for effective regression testing | Not Supported |
Collaborative Inspections and Reviews | ||
| The Collaboration Management component of Rommana provides very strong support for collaboration between all project team. It allows for collaborative reviews of all project entities such as requirements, test cases, scenarios, change requests, etc. | Not supported |
Test Execution | ||
| Supported through integration with Quick Test Pro | Supported through integration with Quick Test Pro |
Prices | ||
Free Trial | 20 floating users for 6 months either installed or hosted | 3o days free trial |
Fixed License | $5,000 for first 5 users | Not available |
Floating License | $10,000 for First 5 users | There are three different versions of Quality Center supporting three different Architectures: Enterprise, and Premier. The only version that supports multiple project teams at multiple sites the same way Rommana does is the Premier version. It must be noted that all three versions of Although HP does not publish Quality Center Prices, the prices for the premier version as provided by sales staff is as follows: $37,000 for the first 5 users $ 5,400 for each additional user |
Subscription (SAAS) Rommana is running on hosted environment | $100 per user for 1-10 users $90 per user for 11-20 users $80 per user for 20-30 users $70 per user for 31-40 users $60 per user for 41-50 users $50 per user for 51 or more users | Not available |
Tech Support | Annually at 20% of invoice | Annually at 22% of invoice |
No comments:
Post a Comment