IC-BPMS (integration-centric business process management suite)
An integration-centric business process management suite (IC-BPMS), also called
integration-centric BPM, is a comprehensive approach to building and upgrading applications and
Web services
that combines the attributes of business process management (BPM) and service-oriented architecture
(SOA) to keep pace with changing market conditions and requirements.
BPM is a systematic approach to making business processes effective, efficient and adaptable.
SOA defines the ways in which computing entities such as programs interact on behalf of one
another. IC-BPMS tools support model-driven development (MDD). This minimizes overhead and allows
for system artifact reuse, which can streamline the evolution of application functionality. In
addition, MDD encourages coordinated efforts among personnel with diverse skills and varying levels
of experience.
This was last updated in March 2007
Email Alerts
Register now to receive SearchSoftwareQuality.com-related news, tips and more, delivered to your inbox.
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States.
Privacy
More News and Tutorials
-
Software consultant Nari Kannan describes how agile practices and work can be scaled appropriately for success in large organizations. Using lean thinking, reduction of waste, and appropriately organizing work and people, agile can be successfully adapted, regardless of the size of the organization.
-
Undiscovered software glitches in complex systems are common, and one of the primary drivers is the loss of mainframe knowledge of a retiring workforce. Software glitches are lurking in many large systems, particularly mainframe systems, and the COBOL programmers that understand the code best are retiring, according to Jeff Papows, author of the new book, "Glitch - The hidden impact of faulty software." Papows describes how faulty software caused a huge charge to debit card holder's account and why such mistakes are on the rise in this interview. Papows notes the three most pressing drivers for software glitches: loss of intellectual knowledge, market consolidation and the ubiquity of technology
-
Karen Johnson suggests a variety of ways that testers can gain additional skills and experience, including social networking and open source testing.
-
Articles
-
Resources from around the Web
