Book Image

Quality Assurance for Dynamics AX-Based ERP Solutions

By : Anil Kumar Gupta
Book Image

Quality Assurance for Dynamics AX-Based ERP Solutions

By: Anil Kumar Gupta

Overview of this book

<p>Dynamics AX is a next-generation ERP system that can be customized in any area to provide a competitive edge by facilitating ERP implementations that follow the time-proven processes being used by businesses. This ERP system not only provides additional flexibilities but also has some other unique features such as its layered customization approach, separation of language elements from code, feature keys, etc. All these features add great value allowing implementation of solutions in a flexible, cost-effective, risk-free, and timely manner but these things may add challenges in quality assurance of these solutions.</p> <p>This book discusses the methodology to ensure quality standards in Dynamics AX customization projects and IBI-compliant independent software vendor application development. Dynamics AX customization is not equivalent to fresh application development; however, Dynamics is so flexible that it allows customization in almost all areas, which poses greater challenges for correctness, accuracy, and trustworthiness of customized Dynamics AX-based ERP solutions.</p> <p>This book discusses the quality expectations from Dynamics AX-based ERP solutions, best practices that need to be followed to meet the quality expectations, and the strategies to test a customized Dynamics AX ERP application.</p>
Table of Contents (15 chapters)
Quality Assurance for Dynamics AX-Based ERP Solutions
Credits
About the Author
About the Reviewer
Preface
Index

Defect Classification


From the perspective of defect management defects can be classified into two categories i.e. security related defects and non security related defects. The security-related defects need some additional information attached with each security defect. Defect classification in Dynamics AX, for all kinds of defects (i.e. irrespective of the type of testing discovering the bugs), is based on the following factors:

  • Bug priority

  • Category

  • Issue status

  • Requirement Ref.

  • STRIDE

  • Severity

  • Discoverability

  • Mitigation

  • Vulnerability

  • Resources

The defect management tool should have the provision to accept all the security-related defects' information. The tool should ensure that when a defect is logged as a security-related issue, the user enters all the required information. The tool should also be able to generate reports as per all the dimensions mentioned above.

Bug Priority

The bug priority categorization indicates overall importance and determines the order in which bugs should be fixed. To...