应用程序设计/集成
我被要求开发一个应用程序，该应用程序将使用我们 ERP 系统中的可用数据。需要此应用程序是因为 ERP 不提供业务所需的内容。
我的问题是我应该采取什么方法？
如果我要对新应用程序的域进行建模，就会有员工的概念，但是员工的概念已经存在于 ERP 域中，但它没有新应用程序所需的所有数据。我是否应该为新系统创建一个单独的模型，而不考虑 ERP，然后以某种方式集成这两个解决方案？
或者
我的新应用程序是否应该对缺失的部分进行建模并通过 Web 服务从 ERP 系统获取数据，然后将它们组合起来以完成我对员工的看法？
I have been asked to develop an application which will use data available from our ERP system. This application is required because the ERP does not provide what the business requires.
My question is what approach should I take?
If I was to model the domain of the new application there would be the notion of an employee, however the notion of an employee already exists in the ERP domain, however it does not have all the data that is needed by the new application. Should I create a seperate model for the new system regardless of the ERP and then somehow integrate these 2 solutions?
or
Should my new application just model the missing bits and get data from the ERP system via a web service and then combine them to complete my view of an employee?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
为什么要重新发明 ERP 已经涵盖的部分？听起来您只需要增强 ERP 系统，而不是重新构建它。您基本上是在
employee表中添加字段，对吧？只需创建一个 aux 表来保存添加的字段，并将其键值设置为与 ERP 中的employee表相同。至于网络服务的问题，这取决于您期望人们如何使用系统。但是，我要说的是：在应用程序中使用 RESTful Web 服务绝不是一个坏主意。
Why re-invent parts that ERP is already covering? Sounds like you just need to augment the ERP system, not re-make it. You're basically adding fields to the
employeetable, right? Just create an aux table to hold the added fields and key it the same as theemployeetable in ERP.As to the question of a web service, it depends on how you expect folks to work with the system. But, I'll say this: it's never a bad idea to have a RESTful web service fronting an app.