Search

Unexpected hurdles in dealing with integration, variability, and interoperability in software development can be overcome using higher-order process integration. Even in its simplicity-oriented, tamed version, this approach fosters a powerful plug-and-play discipline, where processes and services are moved around like data. [ABSTRACT FROM PUBLISHER]

The article focuses on continuous-model-driven engineering (CMDE) and its view of placing the consistent dialogue of all involved stakeholders into the center to provide application-level control, continuous and ongoing quality assurance, and specific service-oriented support for integrating new technologies. It cites the ideas that the CMDE borrows from software and system development paradigms. The One-Thing Approach (OTA) and CMDE's application in industrial projects are also discussed.

The article presents a means of providing full life-cycle support for end-to-end processes. This approach combines service orientation and model-driven design in a way that bridges the gap between business objectives and information technology (IT) implementations. Principals from business and development collaborate at the very beginning when the product is defined. The implementation is supported by a toolset based on the Java Application Building Center framework, which can support a variety of languages including C, Java, and JavaScript.

The article explores open-world software in the realm of business processes. The authors argue for the application of service-oriented design that has long driven the telecommunications infrastructure development and applications development. Because of its strong emphasis on modularization, development of service-oriented software radically alters the way business processes are modeled, realized, and maintained. The complex functions of the underlying business applications are virtualized by domain-specific services so that they can be loosely coupled to form transorganizational processes. They suggest new tools to guarantee a vertically seamless development of the modeled process.

The article talks about the cycle wherein a system becomes outdated before actual use due to the conversion, implementation and adaptation stages. It cites as an example a project in the aerospace industry which take years to plan and renders the technology obsolete before the project starts. Weaknesses mentioned include complex components and lack of interoperability. The author suggests the use of simple design that is similar to how Lego blocks work and uses Apple and Windows 7 as examples.