In component-based development (CBD), logic for an application can be separated into discrete functional elements or components.
Each component is represented by an implementation model and a specification model. An implementation model contains the actual programming logic of the component. The specification model contains the interface definition for the component. Specifically, this model contains the procedure step and action block signatures as well as data model elements needed for users of the component.
The final player in CBD is the consuming model. This model imports the specification model and uses the interface definitions to make calls to the components. During the assemble process, the executable portions of the implementation model are combined with the built consuming model to create a complete application. A consuming model may consume more than one component. The consuming model could be a component and be consumed.
Each public operation in the component may be transactional or subtransactional in nature. Transactional public operations are modeled as procedure steps. Subtransactional public operations are modeled as action blocks in the implementation model and external action blocks in the specification model.
This chapter discusses additional topics of interest to customers who are using CBD techniques.
|
Copyright © 2014 CA.
All rights reserved.
|
|