This article is within the scope of WikiProject Business, a collaborative effort to improve the coverage of business articles on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.BusinessWikipedia:WikiProject BusinessTemplate:WikiProject BusinessWikiProject Business articles
In looking at the link between IT and the business, it has become apparent that there needs to be more formally defined sets of relationships between IT architecture and business architecture. In addition, the concept of business architecture is probably 10-15 years behind the maturity of the IT architecture world. For example, the relationship between business rules and processes is not apparent and the role of organizational governance is similarly disconnected.
Therefore, we are initiating the business architecture working group (BAWG). Business architecture was recently defined as - "Formal models and diagrammatic representations of governance structures, business semantics and value streams across the extended enterprise." This can certainly be debated, but there is no argument to the fact that there is a need for formalization of business architecture to align business to business and business to IT. Join us for this first session in Burlingame at the OMG Technical Meeting on Wednesday, December 12, 2007.
Comment: Definition has been cited in the about six books (excluded books by Kevin Roebuck (different title with same content)), and about 13 more articles. Books:
Kerrie Holley, Ali Arsanjani (2010) 100 SOA Questions: Asked and Answered, 2010.
William M. Ulrich, Philip Newcomb (2010) Information Systems Transformation, 2010. p. 4
Jonathan Whelan, Graham Meaden. Business Architecture: A Practical Guide. 2012, p. 254
Jan vom Brocke, Michael Rosemann. Handbook on Business Process Management 2, 2014.
Stephan Murer, Bruno Bonati Bruno Bonati Consulting. Managed Evolution, 2010.
2009
A BA is a formal blueprint of governance structures, business semantics and value streams across the extended enterprise. It articulates the structure of an enterprise in terms of its capabilities, governance structure, business processes, and business information. The business capability is “what” the organization does, the business processes, are “how” the organization executes its capabilities. In articulating the governance and information.” … “In defining the structure of the enterprise, BA considers customers, finances, and the ever-changing market to align strategic goals and objectives with decisions regarding products and services; partners and suppliers; organization; capabilities; and key initiatives.
Business Architecture Working Group, http://www.omgwiki.org/bawg/doku.php [Accessed July 5, 2009]. as cited in: Grigoriev, Lev, and Dmitry Kudryavtsev. "The Ontology-based Business Architecture Engineering Framework." in: New Trends in Software Methodologies, Tools and Techniques 233. H. Fujita and T. Gavrilova (Eds.) IOS Press, 2011. p. 233-255
2015
Over the past four years, business architecture has transitioned from a loosely set of defined concepts and theories to a robust discipline benefitting organizations worldwide. Business architecture today benefits from a well-formed foundation, formal framework and best practices spreading organically across a myriad of industries. As the discipline evolves, the Business Architecture Guild continues to pursue its mission to promote best practices and expand the business architecture knowledgebase. To that end, the Business Architecture Guild and OMG are presenting the 3rd annual Business Architecture Innovation Summit in Reston, VA on March 24-25, 2015.
In 2007, the Business Architecture Working Group (BAWG) was founded as part of the Object Management Group (OMG). The BAWG aims at establishing industry standards, supporting the creation, and alignment of business blueprints. In this context, it is planned to develop a Business Architecture, connecting OMG's existing and proposed business standards (see Figure 3). The current status of the work is published in whitepapers and on the group’s wiki (see e.g., BAWG 2009b, BAWG 2009a, or TSG, Inc. 2008). BAWG’s BA ecosystem is planned to cover all business domains on an abstract and detailed level (i.e., strategy & structure, business networks, operations, and revenue & performance model). As the BAWG’s BA is still in its infancy, it has not yet become a standard in BA.
Glissman, Susanne, and Jorge Sanz. "A comparative review of business architecture." IBM Research Report, 2009; Reprinted in: Paul P. Maglio, Cheryl A. Kieliszewski, James C. Spohrer (2010) Handbook of Service Science. p. 259
Conceptual Model. Currently, the BAWG provides partially varying concepts about the key components of a BA ecosystem. The current status of the proposal of an integrated IT and BA ecosystem, published in BAWG’s BA requirements for a standard, is illustrated in the fol-lowing (BAWG 2009b). In the proposal, the BA ecosystem covers aspects regarding the motivation, the organizational unit, capabilities, value chain, initiatives & projects, products & services, customer & suppliers, information semantics & rules, business processes, and decision models. As depicted in the figure above, these areas are addressed by existing and planned BA standards. As the standards represent silos, which are not connected, the planned BA work shall integrate these standards. As the work by the BAWG is still in an initial state, the maturity of the conceptual model can be described as low.
Methodology. In addition to the integration of standards in the BA and IT ecosystem, the Business Architecture Working Group has published business scenarios to illustrate the application areas and value of BA. Furthermore, a roadmap for the integrated BA ecosystem was defined and an overview of existing business models is given. Tools. The current unfinished state of the BA cannot be supported by any tool. Service Focus. In the Business Architecture by the BAWG, the service is defined as one element in the BA ecosystem. However, no further information is currently provided on the service in general, or its specific role as connecting element between BA and other IT architectures. The numerous conceptual areas in the BA ecosystem and the IT architecture ecosystem (see Figure 3) indicate that the service element will most likely not be the only element that will link these two ecosystems.
Mr. Ulrich is Co-Chair of the OMG Architecture-Driven Modernization Task Force, Co-Chair of the OMG Business Architecture Special Interest Group, Editorial Director of the Business Architecture Institute, and author of hundreds of articles and...
William M. Ulrich, Philip Newcomb (2010) Information Systems Transformation: Architecture-Driven ... - Pagina xv
2012
A traditional determination of the first signification is defined by the Object Management Group's Business Architecture Working Group as follows A blueprint of the undertaking that supplies a ordinary knowhow of the organization and is being ...
Brandon Bobby (2012), Certified Business Architect (CBA) Secrets To Acing The Exam and Successful Finding And Landing Your Next Certified Business Architect (CBA) Certified Job. p. 9
However, the representation of the business architecture in a way that can be linked to the corresponding IT architecture has been a challenge for a ... How do we represent both these architectures and what “language” should we use? ...
In the business architecture overview by the Business Architecture Working Group (BAWG, 2011), the business capability is described as the primary business functions of an enterprise and the pieces of the organization that perform those functions.
Mistrik, Ivan (2012). Aligning Enterprise, System, and Software Architectures. p. 210
Pure-play organizations emerge to create business architecture “vortex”
Influencers led followed by communities of practice and standards-setting bodies; vendors followed. Conflicting ideas provide opportunity to define the future of business architecture profession.
