Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.5K Microsoft Dynamics NAV
- 18.5K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 115 Navision DOS
- 854 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 615 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 267 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 992 SQL General
- 384 SQL Performance
- 33 SQL Tips & Tricks
- 34 Design Patterns (General & Best Practices)
- Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.7K General
- 1.1K General Chat
- 1.6K Website
- 79 Testing
- 1.2K Download section
- 23 How Tos section
- 259 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
Options
Difference between configuration/design and development
Ashika
Member Posts: 6
Hi Can anyone tell me...
What is the difference between configuration/design and development and customization.
How are they different?
If they are all same then why use different terminologies?
Thanks,
Ashly
What is the difference between configuration/design and development and customization.
How are they different?
If they are all same then why use different terminologies?
Thanks,
Ashly
0
Comments
Configuring an ERP system is largely a matter of balancing the way the customer wants the system to work with the way it was designed to work. ERP systems typically build many changeable parameters that modify system operation. For example, an organization can select the type of inventory accounting—FIFO or LIFO—to employ, whether to recognize revenue by geographical unit, product line, or distribution channel and whether to pay for shipping costs when a customer returns a purchase
Customization
ERP vendors do offer customers configuration options that allow organizations to incorporate their own business rules but there are often functionality gaps remaining even after the configuration is complete. ERP customers have several options to reconcile functionality gaps, each with their own pros/cons. Technical solutions include rewriting part of the delivered functionality, writing a homegrown bolt-on/add-on module within the ERP system, or interfacing to an external system. All three of these options are varying degrees of system customization, with the first being the most invasive and costly to maintain
Key differences between customization and configuration include:
Customization is always optional, whereas the software must always be configured before use (e.g., setting up cost/profit center structures, organisational trees, purchase approval rules, etc.)
-Mohana
http://mohana-dynamicsnav.blogspot.in/
https://www.facebook.com/MohanaDynamicsNav
design/development - done by designer/developer (code changes, page changes....)
customization - a) additional changes for specific customer (e.g. configuring actions and fields on page for specific role, without using the development tool, just by "customizing" the view)
b) development done for specific customer (but I preffer a)
setup/configuration - done by end-user (could be together with consultant) - setting the app to work as needed - no code changes, no "customizations". Just set the data inside system...
MVP - Dynamics NAV
My BLOG
NAVERTICA a.s.