Most ERP procedures are based on past successes. So who gets to decide which are the right ones? Methods developed in the United States or Western Europe are often adopted as templates. Yet, it may be challenging to transfer systems to Asia. When did you start thinking that? How could procedures in several nations vary (beyond the apparent "language" barrier)?

Most ERP procedures are based on past successes. So who gets to decide which are the right ones? Methods developed in the United States or Western Europe are often adopted as templates. Yet, it may be challenging to transfer systems to Asia. When did you start thinking that? How could procedures in several nations vary (beyond the apparent "language" barrier)?

Database System Concepts

7th Edition

ISBN:9780078022159

Author:Abraham Silberschatz Professor, Henry F. Korth, S. Sudarshan

Publisher:Abraham Silberschatz Professor, Henry F. Korth, S. Sudarshan

Chapter1: Introduction

Section: Chapter Questions

Problem 1PE

See similar textbooks

Related questions

Q: Where do we draw the line between generality, overfitting, and underfitting?

A: Overfitting and Underfitting are concepts used in Machine Learning used in Generalizing a machine…

Q: Can the billing system be described and implemented using the waterfall methodology? Do you have any…

A: An internal web system used by the organisation to manage vendor and supplier invoice records is…

Q: The software development life cycle would be incomplete without the testing step. If we are…

A: No, it is not recommended to skip the testing step in the software development life cycle, even if…

Q: What visual associations do you have when you think about email? When an email is sent, what…

A: Email has become an indispensable component of our lives and businesses in the digital age. When an…

Q: Which SDLC model steps are covered by the waterfall technique? Regarding the origins of Barry…

A: The Waterfall model is a sequential software development lifecycle (SDLC) model that follows a…

Q: Is there a way to optimise it, when exactly is it utilised, and what exactly is it? These questions,…

A: An optimising compiler is a type of compiler that examines and edits source code to enhance the…

Q: SO can someone explain in a short concise response what KNN is & its implementation?

A: K-Nearest Neighbors is a straightforward and versatile algorithm that makes predictions based on the…

Q: A crucial part of the SDLC process is testing. Is it possible to skip this step in favor of a more…

A: No, it's never a good idea to skip testing as a phase in SDLC, let's learn out why.

Q: Where do incremental and cascade methodologies diverge and converge? What, if any, are the…

A: There are two different methods for developing software: incremental and cascade. While there are…

Q: What is your opinion of emailing? How does an email get from point A to point B? Be certain to grant…

A: Email has become an integral part of communication in our daily lives. It enables us to communicate…

Q: Who first came up with ADTs? What do you mean by that? How exactly do they function? In concrete…

A: The abstract data type (AFT): Is a mathematical construct for representing various sorts of data.…

Q: Although the methods you are trying to convey don't have anything to do with system analysis, you…

A: The first step will include the provision of structured English to explain procedures that are not…

Q: If you could perhaps elaborate on what we mean by "universal description," "universal discovery,"…

A: Universal Description, Discovery, and Integration (UDDI) is a platform-independent, XML-based…

Concept explainers

Requirement Analysis

A process that determines the user expectations for a software product is called requirement analysis. In software engineering, requirement analysis is known as requirement engineering. It involves communication with end-users and stakeholders to determine whether the system or software requirements are validated, conflicts are solved, and key requirements are documented. The first activity of the Software Development Life Cycle (SDLC) is requirement analysis.

Question

Most ERP procedures are based on past successes. So who
gets to decide which are the right ones? Methods developed
in the United States or Western Europe are often adopted as
templates. Yet, it may be challenging to transfer systems to
Asia. When did you start thinking that? How could
procedures in several nations vary (beyond the apparent
"language" barrier)?

Expert Solution

This question has been solved!

Explore an expertly crafted, step-by-step solution for a thorough understanding of key concepts.

SEE SOLUTION Check out a sample Q&A here

Step 1

VIEW

Step 2

VIEW

Step by step

Solved in 2 steps

SEE SOLUTION Check out a sample Q&A here

Knowledge Booster

Learn more about

Need a deep-dive on the concept behind this application? Look no further. Learn more about this topic, computer-science and related others by exploring similar questions and additional content below.

Similar questions

How do you picture email? How does an email work? Make a list of all your findings. What caused these inequalities? Does your model handle complexity well?
Imagine an email, what do you see? Is it possible for information to go to the right people? The collected information must be documented. Just how crucial is it to understand the distinctions between the two? Specifically, how abstract or detailed are various models, and how do they stack up against one another?
When you think about email, what images pop into your head? What occurs after an email is sent? Jot down anything you can think of at the moment. Is there anybody or anything we can point the finger at for these discrepancies? How successfully do your models scale up or down in complexity?
What opinions do you have on the usage of email? What steps must be taken in order for an email to be delivered from A to B? Make a mental note of how much you understand right now. What does it mean precisely to distinguish between objects, and why is it so crucially necessary to do so? Take a look at how much minute detail has been included into each model (or abstraction).
In your mind's eye, what does an email seem like? In the case of email, the journey begins and ends in the same spot. Keep track of your findings. If there should be no distinctions, why are there any? Look at how the levels of detail (or lack thereof) in the models vary.
Imagine an email, what do you see? Is it possible for information to go to the right people? The collected information must be documented. Just how crucial is it to understand the distinctions between the two? Specifically, how abstract or detailed are various models, and how do they stack up against one another?
Email in your future? Emails go from sender to receiver. Note everything. What causes the differences? Assume there exist models of different complexity (or abstraction)?
Normalization is not the same as standardization. As far as I know, there is no difference. What examples can you think of for each of these categories?