JAMA versus JIRA

Feature Comparison
from a Test
Perspective Document
Status: Draft
Version No. 0.2
Author: Kamran Sultan
Effective Date: 2014-08-21
File Name: ???
Revision History

Revision History

Ver # Comments Author Reviewed Approved Date

0.1 Initial Draft Kamran Sultan - - 2014-08-21
0.2 Minor changes Kamran Sultan
correction to
one of the
feature

Document Approvals

Name Role Date

File Name: Page

Version No.: 0.1
Copyright 2013 Schneider Electric (Australia) Pty. Ltd.
Revision History

1 Introduction

1 Purpose

2 Document Scope

This feature comparison between JAMA versus JIRA document to evaluate JAMA as a
complete solution that includes requirements management, test management, release
management and defect tracking all fully integrated in a single tool from inception of a
project. This document tries to list some of the many great features that would help make
JAMA as the choice of tool for both Quality Assurance and Quality Control for Schneider
Electric.

3 Intended Audience

The intended audience of this document includes (but is not limited to):

Schneider Electric business stakeholders

Development, Test and Science teams

File Name: Page

Version No.: 0.1
Copyright 2013 Schneider Electric (Australia) Pty. Ltd.
Revision History

4 Features comparision in JAMA versus JIRA

Features JAMA JIRA

Test management tool? Yes No - An additional plugin is
needed called Zephyr
Bug-tracking? Yes Yes
Export and Import data? Yes Yes
Requirements Management? Yes No
Does it provide the ease for mapping Yes No
Requirements to test artefacts?
Bug Generation from Failed Steps? Yes No
Can a user Fail a test case at a Yes No
specific test?
Does it provide the capability of Yes Questionable as a lot effort
Traceability from bugs to Tests and involved in order to setup the
Requirements? traceability in JIRA
Does it have ability to map Yes No
requirements to test cases to validate
that the functionality works as
expected?
Can we view the pass/fail status of Yes Yes Difficult to trace as
the tests that cover each compared to JAMA
requirement?
Can we create templates feature for Yes No
our test cases, test plan?
Can we specify the expected result Yes No
and suggested sample data for each
test step in the system?
Does it have the Test planning Yes No
capability?
Does it provide a single click to Yes No
automatically track the time for test
execution to assess for re-execution?
Does it provide the ease of checking Yes No
all the requirements have a test
against it?
Drill down from requirements to tests Yes very No
and incidents? powerful level of
drill capability
which could be
done bidirectional
The simplicity of managing all QA Yes No
artefacts in one environment?
Does it provide ability to Baseline our Yes No

File Name: Page

Version No.: 0.1
Copyright 2013 Schneider Electric (Australia) Pty. Ltd.
Revision History

test case to the requirements?

Does the Audit log of all changes Yes No
made to requirements in the system?
Discussion threads / comments Yes No
attached to Requirements
Ability to pause an incomplete test Yes No
run and continue running it at a later
date.
Complete traceability from a recorded Yes No
incident to the underlying requirement
that was not satisfied
Requirements and Test Cases can be Yes No
mapped to Releases and Test cycles,
with the option of filtering both by
Release to give a release-specific
picture of a project's requirements
coverage and test execution Status?
Ability to manage Test cycles? Yes No
Single Click Impact Analysis which Yes No
connects everything together with
end-to-end traceability and impact
analysis
Digital Sign off on Test cases from the Yes No
Dev team
Review centre feature to bring the Yes No
whole team on a single platform to
provide comments and feedback on
the test cases or any other artefacts
Specific functionality to individual Test Yes No
Cycles

File Name: Page

Version No.: 0.1
Copyright 2013 Schneider Electric (Australia) Pty. Ltd.