Original Software is not practical for JD Edwards Systems Testing

Below are my reasoning and perspectives on the product and their solutions. You can agree or disagree on it however I want to at least provide you, who are reading this, with some insights.

First of all, the setup and configurations for it, so I am hearing, is that it would require a top down model design flow as suppose to bottom up. Does it matter? or make a difference? Yes it does in my own view and opinion it. Reason is because not every business process or business task in JD Edwards can be clearly defined and specially true in a rapid changing or growing business and sure there are some core and/or key tasks which the business typically would do in areas such as Manufacturing, Distribution, and so on. And even if we could define it in some areas and put them together into a business process and further define into a business task. What is a business task? You may think of it as Entering a Work Order, Entering a Sales Order, or Entering a Purchase Order. What is a business process? You can think of it as a process which a business unit typically would perform from a start to finish such as Work Order Processing, Sales Order Processing, etc. Each business task, in JD Edwards, is tied or linked into a menu and ultimately to object and version. Since in JDE, an object such as an interactive application can have multiple versions and a business task may only use a specify version of an application. Thus, each business process, as we may know it, can have various business tasks, and therefore it can have multiple links to various JD Edwards objects and versions. So, the bottom line, is to define it from the top down would be unjust or unrefined as it is not always going to fit exactly but rather define it from the bottom up where each 'action' or 'script entity' where it should be tied directly to a JDE object and version and that each business task can link to a specific to 'script entity' and each of those related business tasks can ultimately link up to a business process (that is unique to a specific company or industry). With that, each individual 'script entity' can be tested by its own unit or department or individual key player.

Each business process and business task can be further defined for specific company and industry. For example, a business task, Entering a Sales Order, may be defined to process only specific Sales Order types or branch or items. In JDE, we can define and control it through object (application) version because it can have its own processing rules or business processing rules / logic. With that in mind, each business process is a string or collection of business tasks. A business task can be specific to a business process and in some cases it can be part of another business process.

Furthermore, the method or approach for this, if it is to work nicely for JD Edwards systems, is for it to provide an easy wizard or import tool to bring all of object list and version list from Object Librarian and build the 'action script' out of that. From that, we can pick and choose a specific 'action script' that would be into a business task.

to be continue....