There is no reason why an object-oriented design approach should be limited to the entities of the OS/400 shipped system. You can introduce your own entities and design applications in terms of operations performed upon them. For instance, if you decide that ‘Customers’ and ‘Orders’ are design entities, you could provide the following functions:
Note: An object-based approach gives you underlying rationale for a naming convention on OS/400.
Not all of your design objects will necessarily result in a separate OS/400 object, but the same object-oriented design principles can still be used when naming sub-entities such as fields and members. Because of the strictures of some of the OS/400 HLLs such as RPG III, you may need to use additional compression rules; for example, reducing the standard three-letter mnemonics to two.
|
Copyright © 2014 CA.
All rights reserved.
|
|