You can develop applications rapidly by using the WebSphere® Multichannel Bank Transformation Toolkit tooling. You can also extend the WebSphere Multichannel Bank Transformation Toolkit to suit your requirements; for example, you can extend WebSphere Multichannel Bank Transformation Toolkit to implement your own data types of UI widgets.
Application development with WebSphere Multichannel Bank Transformation Toolkit reduces the level of skills that are required of a development team. A high level of technical knowledge is required only from those developers who are responsible for extending the WebSphere Multichannel Bank Transformation Toolkit framework and development platform building. Functional developers can then focus on creating the business logic and the UI with WebSphere Multichannel Bank Transformation Toolkit tooling. WebSphere Multichannel Bank Transformation Toolkit generates the technical infrastructure code of WebSphere Multichannel Bank Transformation Toolkit framework and transaction definition and classes. In many cases, a function developer might not even be required to write any code. We call it zero code development of massive transactions.
WebSphere Multichannel Bank Transformation Toolkit application development involves first top down design and a bottom up implementation with development tooling. Firstly, you need to design the business flow of the transaction; we need to break down the transaction into operations and views, and the transition between them. Then you need to design the data context of the flow and operations and the data map between flow and operation. At the same time, we will design the UI layout and data binding between the UI widgets and data context of flow and operations.
In the implementation phase, you build an application by using UI widgets, data, and operations. Then you assemble the operation and XUI pages into a transaction flow by using the Transaction flow editor.
For more information on the design and implementation phases of the application development process, see the **** MISSING FILE ****.