Michael B.T. Bell
Get Michael B.T. Bell essential facts below. View Videos or join the Michael B.T. Bell discussion. Add Michael B.T. Bell to your PopFlock.com topic list for future reference or share this resource on social media.
Michael B.T. Bell
Michael B.T. Bell
Bell bt michael.jpg
Alma materCity University of New York
OccupationEnterprise Architect

Michael B.T. Bell is an American enterprise software architect, chiefly recognized for developing the Incremental Software Architecture methodology,[1]Service-oriented modeling framework (SOMF),[2][3][4][5][6] and the cloud computing modeling notation (CCMN).[7] His innovative research and publications in the fields of software architecture, service-oriented architecture, Microservices, model-driven engineering, cloud computing, and big data are recognized internationally for their contribution to the software design and development communities.


Bell earned his computer science master's degree in 1992 from the City University of New York (CUNY).

After graduation, as a software developer and enterprise architect consultant, he dedicated his career to improving business and technological operations of financial institutions in Wall Street. He developed innovative software algorithms and methodologies for high-volume Electronic trading platforms. This included modules for execution of trading applications, persistence methods for large volumes of data, and design of high-speed network and internet software implementations.

He has worked for J.P. Morgan Chase, Citibank, UBS-Paine Webber, Deutsche Bank, American Express, TD Waterhouse, Pfizer, AIG, Prudential. and United States Department of Veterans Affairs.

Bell's Service-Oriented Modeling Methodology

Service-Oriented Modeling Framework (SOMF) Version 2.0

In 2008 Bell introduced the Service-oriented modeling framework (SOMF) [8][9] to the software development community in his book Service-Oriented Modeling.[10]

The service framework, driven by Discipline-specific modeling, was devised to encourage consolidation of software assets, reduction of systems redundancy, and acceleration of time-to-market. SOMF [11] includes a modeling language and a life cycle methodology (see image on the far right) suited for narrowing the gap between the business and the information technology organizations in the enterprise.

The framework also includes modeling disciplines and practices of software systems, for the purpose of designing software applications. Furthermore, SOMF [12] offers a variety of architectural styles, such as enterprise architecture, application architecture, service-oriented architecture,[13] and cloud computing.

Bell's Incremental Software Architecture Methodology

Incremental Software Architecture Process

Traditionally, to promote the establishment and growth of an enterprise end-state architecture, architects, typically senior IT professionals, deliver a diagram that depicts a future production landscape.[14] In most cases, these software designers claim that such as a "to be" architecture is unbreakable and could sustain rapid market trends and complex technological evolution. Their claim also seems to assure that the illustrated architecture would operate flawlessly in production. Would it?

In many cases, though, such laid on paper architecture, is merely an academic proposition, which later fails to deliver system stability, business continuity, and superb performance. In other words, this speculative architecture tends to break down because of design flaws, and most important--lack of organizational architecture strategy.

To tackle the deployment of failing applications and systems to production and reduce the risk of harming the operating environment, the Incremental Software Architecture approach calls for submitting bulletproof architecture blueprints. This enterprise design should also be certified by a wide rainbow of organizational stakeholders to dodge financial calamity and business discontinuity.

How is it possible then to ensure that the illustrated design on paper would indeed render a stable production landscape? The term "stable" means that the deployed systems would meet business and non-functional requirements. The promise of the Incremental Software Architecture, therefore, is rooted in the chief principle, "First Design then Develop." But this alone is short of avoiding financial burden caused by failing implementations. Equally important, another related tenet calls for modifying the charter of development organizations: The software construction phase as we know it now, should focus on proving that architecture assumptions would certainly work in production. Bottomline, "software construction must follow the pace of design evolution." Obviously, not the other way around. The term "design evolution" means that architects should drive the product development life cycle, during which the end-state architecture could be incrementally modified, while software construction follows design alterations until architecture maturity is achieved.

To prove that an end-state architecture would indeed operate flawlessly in production, the grand enterprise design should be decomposed into sub-architectures.[15] Such end-state architecture decomposition, therefore, would allow designers to drill down into their detail architecture and enable developers to focus on constructing architecture segments--one at a time, or some in parallel. But proving that each individual end-state architecture segment works as designed, does not mean that the entire enterprise architecture as a whole would indeed perform flawlessly. To verify if an end-state architecture is stable and could endure production environment pressures, an overall architecture stress testing should be considered to assure its stability and fitness.

Consider the Incremental Software Architecture process,[16] as depicted in the provided image:
1. End-State Architecture Discovery and Analysis. Ascertaining systems and related applications in an end-state architecture proposition
2. End-State Architecture Decomposition. The decomposition process is driven by segmenting the enterprise grand design into structural, behavioral, and volatile regions, so developers can prove that these sub-architectures would indeed work in production
3. End-State Architecture Verification. Authentication tasks include design substantiation (software construction,) end-state architecture stress testing, and enterprise capacity planning.


Michael Bell has published several books and articles. The following is a selection:

  • 2005. "An Organizational Model: The AOM-3, Architecture Organization Structure and Role Models". IP Publishing. ISBN 978-0-9896935-3-0
  • 2006. "Service-Oriented Architecture: A Planning and Implementation Guide for Business and Technology". With Eric Marks. Wiley & Sons. ISBN 978-0471768944
  • 2008. "Service-Oriented Modeling: Service Analysis, Design, and Architecture". Wiley & Sons. ISBN 978-0470141113
  • 2010. "SOA Modeling Patterns for Service Oriented Discovery and Analysis". Wiley & Sons. ISBN 978-0470481974
  • 2011. Service Oriented Modeling Specifications for SOMF. Includes Service design and cloud computing.
  • 2016. "Incremental Software Architecture: A Method for Saving Failing IT Implementations" . Wiley & Sons. ISBN 978-1119117643


  1. ^ Bell, Michael (2016). "The Need for Incremental Software Architecture". Incremental Software Architecture: A Method for Saving Failing IT Implementations. Wiley & Sons. p. 1. ISBN 978-1119117643.
  2. ^ Bell, Michael (2008). "Introduction to Service-Oriented Modeling". Service-Oriented Modeling: Service Analysis, Design, and Architecture. Wiley & Sons. ISBN 978-0-470-14111-3.
  3. ^ Thuraisingham, Bhavani (2010). Secure Semantic Service-Oriented Systems. CRC Press. pp. 42, 43, 152, 153. ISBN 9781420073324.
  4. ^ Hybertson, Duane (2012). Model-oriented Systems Engineering Science: A Unifying Framework for Traditional and Complex Systems (Complex and Enterprise Systems Engineering). Auerbach Publication. pp. 256, 329. ISBN 978-1420072518.
  5. ^ Thuraisingham, Bhavani (2013). Developing and Securing the Cloud. CRC Press. p. 87. ISBN 9781439862919.
  6. ^ Buyya, Rugkumar (2013). Mastering Cloud Computing. Tata McGraw-Hill. pp. 2-30. ISBN 9781259029950.
  7. ^ "Cloud Computing Modeling Notation". Sparx Systems.
  8. ^ Sosinsky, Barrie (2010). Cloud Computing Bible. Wiley & Sons. pp. 288, 289. ISBN 9781118023990.
  9. ^ Trujillo, Juan (2010). Advances in Conceptual Modeling - Applications and Challenges. Springer Science & Business Media. pp. 87, 88. ISBN 9783642163845.
  10. ^ Bell, Michael. "Service-Oriented Modeling". Wiley & Sons.
  11. ^ Dustdar, Schahram (2010). Service Engineering: European Research Results. Springer Science & Business Media. pp. 112, xi. ISBN 9783709104156.
  12. ^ Bell, Michael (2009). SOA Modeling Patterns for Service Oriented Discovery and Analysis. Wiley & Sons. pp. 185, 240. ISBN 9780470579695.
  13. ^ Bell, Michael. "Service-Oriented Architecture". Wiley & Sons.
  14. ^ Bell, Michael (2016). "The Need for Incremental Software Architecture". Incremental Software Architecture: A Method for Saving Failing IT Implementations. Wiley & Sons. pp. 2, 3, 4. ISBN 978-1119117643.
  15. ^ Bell, Michael (2016). "The Need for Incremental Software Architecture". Incremental Software Architecture: A Method for Saving Failing IT Implementations. Wiley & Sons. pp. 5, 6. ISBN 978-1119117643.
  16. ^ Bell, Michael (2016). "The Need for Incremental Software Architecture". Incremental Software Architecture: A Method for Saving Failing IT Implementations. Wiley & Sons. p. 9. ISBN 978-1119117643.

External links

  This article uses material from the Wikipedia page available here. It is released under the Creative Commons Attribution-Share-Alike License 3.0.



Music Scenes