Foydel advocates an agile programming methodology for developing business applications within OneWorld. He suggests that this is more robust than the waterfall method. Largely, I tend to agree. Note that Foydel deprecates what is perhaps the most extreme aspect of agile, namely the pair programming. But other recommendations of agile I think can be usefully done by you. Like the frequent prototyping and showing of these intermediate stages for your end users. This tight feedback loop can be vital to a project's success. It reduces the pernicious possibility of drift. Where the developers end up coding an application which is not germane to the users' needs.
OneWorld is shown by the book to integrate all the main needs for a company's management. Accounting is naturally a big ability. There are myriad options for the developer. Including for payment processing and inventory costing (eg. LIFO, FIFO). The other main area of the book deals with sales and marketing. There are aspects common to most sales and marketing efforts. These have been factored out and instantiated into the package. Letting you quickly define such key areas like commissions. OneWorld also offers dashboards that show near real time summaries of incoming data. Useful at the executive level, to keep a close continual eye on events.
For some companies turning to OneWorld, the biggest change might be its Software As A Service nature. It differs from loading a package onto your company machines. The benefit offered is that NetSuite handles the storage and backup of OneWorld; freeing your company to focus on its expertise in other areas.
