Book Image

Mastering Microsoft Dynamics NAV 2016

By : Rabindra Sah
Book Image

Mastering Microsoft Dynamics NAV 2016

By: Rabindra Sah

Overview of this book

The book begins by giving you a brief introduction to setting up your NAV environment and shows you how to install and configure it according to your requirements. You will then dive deep into the latest design patterns, network architecture, and topologies. We will show you how you can integrate NAV with the Microsoft platform, and secure your deployment by managing roles and permissions. Moving on, we will explain how to monitor and manage server instances using the Administration tool. We’ll discuss how you can take advantage of the expanded extensibility and connectivity capabilities for a tighter integration with the cloud as well as handheld devices. Then, we’ll show you how you can make use of the PowerBI capabilities that have been built into Dynamics NAV. By the end of the book, you will be confident in developing and administering a Dynamics NAV implementation that will leverage all of the new features.
Table of Contents (19 chapters)
Mastering Microsoft Dynamics NAV 2016
Credits
About the Author
About the Reviewer
www.PacktPub.com
Customer Feedback
Preface

Application lifecycle


The application lifecycle is composed of six main steps, that is, design, development implementation, production, tuneup, and fit/gap, as shown in the following figure. This is a recursive process since the requirement is directly proportional to the life of any software. If any new requirement comes, then you can analyze the gap and find whether the problem can be resolved using the default setting, and if it needs additional development, you can go for it:

In this chapter, we will focus only on design and development considerations. The implementation and tuneup processes are covered in the upcoming chapters.

Design

Software design should be treated as any other engineering design and should be as simple and as compatible as possible. You should be able to design the system so that the end user who is going to use your system along with the standard system must not get confused with your development, and it should also not be alien in look and feel to the standard...