JD Edwards的发展学习曲线是什么? [英] What is the learning curve for development on JD Edwards?
问题描述
平均而言，精通JD Edwards进行开发需要花费多少时间?容易学习吗?有任何先决条件吗?
我假设您有兴趣学习JD Edwards的开发技能，而不是系统实际实现的业务流程.
有2个版本的JDE.其中一个在AS/400平台，DB2数据库上运行，并使用RPG(语言)来实现报告和功能.我不熟悉该版本(界面工作很少，并且由于DB2与我通常使用的数据库风格(Oracle或SQL Server)不同，所以它们都很复杂.
另一个版本是EnterpriseOne(以前称为OneWorld).我从2000年开始为该版本进行开发，一直活跃到2006年.要达到基本的开发水平很容易，然后您将面对系统中的怪异问题和已知问题，以及如何规避它们，这才是您有经验的时候.
所有开发工具都是JDE内部的.有一个表设计器，一个查询设计器(具有类似于任何可视查询设计器的网格界面)，一个交互式程序设计器(窗体)，一个报表设计器和一个业务规则设计器.
如果您有使用任何RDA工具(例如Visual Studio)和数据库开发的经验，则可以使用此知识来简化学习过程.就我而言，我是一名SQL程序员，并且在Visual Basic和Microsoft Access方面拥有丰富的经验.通过了解系统的基本概念并对其进行调整，我可以利用这些经验.我花了大约25个小时与一个经验丰富的程序员进行了培训，使我准备好至少可以对实际客户进行基本操作.很明显，这个小时数因人而异.
但是，我可以说，我的第一位客户每天工作六个月后，才开始感到自己对工具和过程有所了解.大约12到18个月后，我为自己编写的第一个应用程序感到ham愧，因此我实际上回去自己改写了一些应用程序...:-)
关于JDE的事情是:数据库方面几乎没有编码/功能(因为它过去在数据库选择方面很灵活).所有的表格和报告都是通过设计者的方式写在实际系统中的.
所有编码"都是通过简单(有时是愚蠢的)点击界面完成的.例如:您不编写赋值语句，例如var = value.选择分配"按钮，然后在列表中选择变量，然后在列表中选择值(如果固定，则输入值).
以这种方式创建表单，报表和业务规则背后的所有规则.一个例外:编写业务规则时，可以选择使用这种方法(称为命名事件规则-NER)还是使用C语言(称为业务功能).
如果选择NER，则完成后，系统实际上会将其转换为C.
具有用于表单，报表和业务规则的调试功能.
这是基本的发展.通常还会为开发人员分配其他工具和功能，因此您将能够做更多的事情.我在界面，互操作性，工作流等方面做了很多工作.
还值得注意的是，JDE有一个内部工具，用于管理对象，版本控制，签入，签出以及将对象从一个环境转移到另一个环境以完成开发工作.
作为开发人员，您对实施的业务流程了解得越多，越好.您将学习功能的内部(代码，规范)和外部(过程)，这将帮助您成为开发人员，并在您的职业生涯(和薪资)方面有所帮助.
现在，关于我的答案，我唯一需要注意的是:正如我已经提到的，距我离开JD Edwards开发已经有一段时间了.据我所知，事情几乎是一样的，但我不能肯定地说.
我可以提供的最佳建议:请访问www.jdelist.com上的特定问题和问题帮助.要有礼貌，尝试问一些有关特定问题的问题，而不要问一般性问题(我的意思是:如果问那些人学习JDE需要多长时间，他们可能会无视您，但是如果您问诸如您认为呢?是JDE开发人员要掌握的最复杂的任务?"您可能会得到一些很好的答案).
希望它能对您有所帮助，并祝您使用JDE一切顺利.最初的颠簸之后，我非常喜欢骑车.
On an average, how much time does it take to become proficient in development using JD Edwards? Is it easy to learn? Are there any prerequisites?
I'm assuming you're interested on learning the development skills of JD Edwards, not the business processes that the system actually implements.
There are 2 versions of JDE. One runs over AS/400 plataforms, DB2 database and uses RPG (language) to implement reports and functionalities. I'm not acquainted with that version (did very few interface jobs and they were all complicated due to DB2's differences from my usual flavours of databases - Oracle or SQL Server).
The other version is EnterpriseOne (formerly OneWorld). I started developing for this version in 2000 and kept active until 2006. It's very easy to achieve the basic level of development and then you get to face the oddities and known issues from the system and how to dodge them and that's when you become experienced.
All development tools are internal to JDE. There's a table designer, a query designer (with a grid interface that resembles any visual query designer), an interactive programs designer (forms), a report designer and a business rules designer.
If you have experience with any RDA tool (like Visual Studio, for instance) and development for databases, you will be able to use this knowledge to ease the learning curve. In my case, I was a SQL programmer and I had a lot of experience with Visual Basic and Microsoft Access. I was able to use that experience by understanding the underlying concepts of the system and adapting for them. It took me about 25 hours of training with a more seasoned programmer to get me ready to at least do basic stuff on real customers. This amount of hours varies from person to person, obviously.
However, I can say that I only started to feel that I was understanding the tools and the process after 6 months of daily work on my first customer. After about 12-18 months, I was ashamed of the first applications that I wrote, so I actually went back and rewrote some on my own time... :-)
The thing about JDE is: there's very little coding/functionality on the database side (because it used to be flexible on databases choices). All the forms and reports are written inside the actual system by way of the designers.
All "coding" is done by way of a simple (and sometimes dumb) point-and-click interface. For instance: you don't write an assignment statement, like var = value. You select the Assignment button, then you select the variable in a list, then you select the value in a list (or enter the value, if it's fixed).
All the rules behind forms, reports and business rules are created that way. One exception: when you're writing a business rule, you can opt between using this approach (called Named Event Rule - NER) or using the C language (called Business Function).
If you choose NER, after you finish, the system actually converts that to C.
There are debug functionalities for forms, reports and business rules.
This is basic development. There are other tools and functionalities that are usually assigned to developers and so you will be able to do a lot more. I've worked a lot with interfaces, interoperability, workflow and more.
Also noteworthy is that JDE has an internal tool for managing objects, version control, checkins, checkouts and transfering objects from one environment to another to complete the development cicle.
As a developer, the more you learn about the business processes being implemented, the better. You get to learn the inside (code, specs) and outside (process) for the functionalities and this helps you as a developer and helps you in your career (and paygrade).
Now, my only caveat regarding my answer: as I've mentioned, it's been a while since I left JD Edwards development. As far as I know, things are pretty much the same, but I can't say for sure.
Best advice I can offer: go to www.jdelist.com for specific questions and help with issues. Be polite, try to ask questions about specific matters instead of general questions (I mean: if you ask those guys how long does it take to learn JDE, they will probably ignore you, but if you ask stuff like "in your opinion, what are the most complex tasks for a JDE developer to master?" you will probably get some pretty good answers).
Hope it helps and wish you good luck with JDE. After the initial bump, I enjoyed my ride on it quite a lot.
这篇关于JD Edwards的发展学习曲线是什么?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
