Jama Vs Jira Feature Comparison From A Test Perspective V0.2 35x2q
This document was ed by and they confirmed that they have the permission to share it. If you are author or own the copyright of this book, please report to us by using this report form. Report 2z6p3t
Overview 5o1f4z
& View Jama Vs Jira Feature Comparison From A Test Perspective V0.2 as PDF for free.
More details 6z3438
- Words: 652
- Pages: 5
JAMA versus JIRA Feature Comparison from a Test Perspective Document Status: Draft Version No. Author: Effective Date: File Name:
0.2 Kamran Sultan 2014-08-21 ???
Revision History
Revision History Ver #
Comments
Author
0.1
Initial Draft
Kamran Sultan
0.2
Minor changes correction to one of the feature
Kamran Sultan
Reviewed -
Approved
Date
-
2014-08-21
Document Approvals Name
File Name: Version No.: 0.1 Copyright
2013 Schneider Electric (Australia) Pty. Ltd.
Role
Date
Page
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: Version No.: 0.1 Copyright
2013 Schneider Electric (Australia) Pty. Ltd.
Page
Revision History
4
Features comparision in JAMA versus JIRA
Features
JAMA
JIRA
Test management tool?
Yes
Bug-tracking? Export and Import data? Requirements Management? Does it provide the ease for mapping Requirements to test artefacts? Bug Generation from Failed Steps? Can a Fail a test case at a specific test? Does it provide the capability of Traceability from bugs to Tests and Requirements? Does it have ability to map requirements to test cases to validate that the functionality works as expected? Can we view the /fail status of the tests that cover each requirement? Can we create templates feature for our test cases, test plan? Can we specify the expected result and suggested sample data for each test step in the system? Does it have the Test planning capability? Does it provide a single click to automatically track the time for test execution to assess for re-execution? Does it provide the ease of checking all the requirements have a test against it? Drill down from requirements to tests and incidents?
Yes Yes Yes Yes
No - An additional plugin is needed called Zephyr Yes Yes No No
Yes Yes
No No
Yes
Questionable as a lot effort involved in order to setup the traceability in JIRA No
The simplicity of managing all QA artefacts in one environment? Does it provide ability to Baseline our
File Name: Version No.: 0.1 Copyright
2013 Schneider Electric (Australia) Pty. Ltd.
Yes
Yes
Yes – Difficult to trace as compared to JAMA
Yes
No
Yes
No
Yes
No
Yes
No
Yes
No
Yes – very powerful level of drill capability which could be done bidirectional Yes
No
Yes
No
No
Page
Revision History
test case to the requirements? Does the Audit log of all changes made to requirements in the system? Discussion threads / comments attached to Requirements Ability to pause an incomplete test run and continue running it at a later date. Complete traceability from a recorded incident to the underlying requirement that was not satisfied Requirements and Test Cases can be 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? Single Click Impact Analysis which connects everything together with end-to-end traceability and impact analysis Digital Sign off on Test cases from the Dev team Review centre feature to bring the whole team on a single platform to provide comments and on the test cases or any other artefacts Specific functionality to individual Test Cycles
File Name: Version No.: 0.1 Copyright
2013 Schneider Electric (Australia) Pty. Ltd.
Yes
No
Yes
No
Yes
No
Yes
No
Yes
No
Yes Yes
No No
Yes
No
Yes
No
Yes
No
Page
0.2 Kamran Sultan 2014-08-21 ???
Revision History
Revision History Ver #
Comments
Author
0.1
Initial Draft
Kamran Sultan
0.2
Minor changes correction to one of the feature
Kamran Sultan
Reviewed -
Approved
Date
-
2014-08-21
Document Approvals Name
File Name: Version No.: 0.1 Copyright
2013 Schneider Electric (Australia) Pty. Ltd.
Role
Date
Page
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: Version No.: 0.1 Copyright
2013 Schneider Electric (Australia) Pty. Ltd.
Page
Revision History
4
Features comparision in JAMA versus JIRA
Features
JAMA
JIRA
Test management tool?
Yes
Bug-tracking? Export and Import data? Requirements Management? Does it provide the ease for mapping Requirements to test artefacts? Bug Generation from Failed Steps? Can a Fail a test case at a specific test? Does it provide the capability of Traceability from bugs to Tests and Requirements? Does it have ability to map requirements to test cases to validate that the functionality works as expected? Can we view the /fail status of the tests that cover each requirement? Can we create templates feature for our test cases, test plan? Can we specify the expected result and suggested sample data for each test step in the system? Does it have the Test planning capability? Does it provide a single click to automatically track the time for test execution to assess for re-execution? Does it provide the ease of checking all the requirements have a test against it? Drill down from requirements to tests and incidents?
Yes Yes Yes Yes
No - An additional plugin is needed called Zephyr Yes Yes No No
Yes Yes
No No
Yes
Questionable as a lot effort involved in order to setup the traceability in JIRA No
The simplicity of managing all QA artefacts in one environment? Does it provide ability to Baseline our
File Name: Version No.: 0.1 Copyright
2013 Schneider Electric (Australia) Pty. Ltd.
Yes
Yes
Yes – Difficult to trace as compared to JAMA
Yes
No
Yes
No
Yes
No
Yes
No
Yes
No
Yes – very powerful level of drill capability which could be done bidirectional Yes
No
Yes
No
No
Page
Revision History
test case to the requirements? Does the Audit log of all changes made to requirements in the system? Discussion threads / comments attached to Requirements Ability to pause an incomplete test run and continue running it at a later date. Complete traceability from a recorded incident to the underlying requirement that was not satisfied Requirements and Test Cases can be 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? Single Click Impact Analysis which connects everything together with end-to-end traceability and impact analysis Digital Sign off on Test cases from the Dev team Review centre feature to bring the whole team on a single platform to provide comments and on the test cases or any other artefacts Specific functionality to individual Test Cycles
File Name: Version No.: 0.1 Copyright
2013 Schneider Electric (Australia) Pty. Ltd.
Yes
No
Yes
No
Yes
No
Yes
No
Yes
No
Yes Yes
No No
Yes
No
Yes
No
Yes
No
Page
Related Documents c2h70
Jama Vs Jira Feature Comparison From A Test Perspective V0.2 35x2q
December 2019 78
Feature Comparison Model 6m1k4z
October 2019 103
Tails From A Different Perspective 3b193p
September 2021 0
Feature Charts From Hayes 291fu
November 2019 39
Rhema Vs Logos A Scholar's Perspective 2j49d
December 2019 28
Jira Tutorial.ppt z6258
November 2022 0More Documents from "Bogdan Bogdan" 661k1g
Jama Vs Jira Feature Comparison From A Test Perspective V0.2 35x2q
December 2019 78
Hp Microserver Gen8 Service Manual e5a2j
November 2019 102
6g3p1u
March 2023 0
Slaves Of The Maelstrom Ver3.0 2w4k3v
December 2019 93
Sinuzita 325t5f
December 2019 126