Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Save more on your purchases! discount-offer-chevron-icon
Savings automatically calculated. No voucher code required.
Arrow left icon
All Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Newsletter Hub
Free Learning
Arrow right icon
timer SALE ENDS IN
0 Days
:
00 Hours
:
00 Minutes
:
00 Seconds
Arrow up icon
GO TO TOP
Implementing Microsoft Dynamics 365 for Finance and Operations

You're reading from   Implementing Microsoft Dynamics 365 for Finance and Operations Implement methodology, integration, data migration, and more

Arrow left icon
Product type Paperback
Published in Sep 2017
Publisher Packt
ISBN-13 9781787283336
Length 562 pages
Edition 1st Edition
Arrow right icon
Authors (3):
Arrow left icon
 Mohta Mohta
Author Profile Icon Mohta
Mohta
Yogesh Kasat Yogesh Kasat
Author Profile Icon Yogesh Kasat
Yogesh Kasat
JJ Yadav JJ Yadav
Author Profile Icon JJ Yadav
JJ Yadav
Arrow right icon
View More author details
Toc

Table of Contents (23) Chapters Close

Foreword
Title Page
Credits
Disclaimer
About the Authors
About the Reviewers
www.PacktPub.com
Customer Feedback
Preface
1. Introduction to Microsoft Dynamics 365 FREE CHAPTER 2. Implementation Methodology and Tools 3. Architecture and Deployment 4. Project Initiation and Kickoff 5. Requirements, Business Process Analysis, and Traceability 6. Configuration and Data Management 7. Functional and Technical Design 8. Integration Planning and Design 9. Building Customizations 10. Analytics, Business Intelligence, and Reporting 11. Testing and Training 12. Go Live 13. Post Go Live Support 14. Update, Upgrade, and Migration

Importance of testing


Testing is the process of validating the system processes to meet the business requirements. It includes testing the custom as well as the standard features, along with the migrated data, integrations, reports, and security aspects of the solution. It is an area that is most often underestimated and, as a result, hampers the success of your project.

A very common misconception is that testing starts after the development phase is over. The primary goal of testing is to provide feedback on the product as soon as possible. Identifying any issues in the requirements phase prevents them from becoming a part of the design. Similarly, identifying any issues in the design phase prevents them from being coded. The cost of fixing a defect depends on the phase where it has been detected; the cost of fixing a defect in the early phases of SDLC (Software Development Life Cycle) is much lower in the later phases. The farther you go with the backlog of testing/validation; the more...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $15.99/month. Cancel anytime
Visually different images