2.3 Methodology: Business Architecture

== Methodology Section 3 - Business Architecture ==

3.       (IV) Business Architecture

To build the Top-down (IV) Business Architecture, consider the procedure below.  Feed all the collected responses to these questions into the EA repository, noting that items 30 and 31 relate to actual infrastructure and system development, deployment, operation, and maintenance, not enterprise architecture. However, these items form the basis for measuring compliance with the architecture and the success/fit of the architecture to the enterprise/function mission.  Refer to the following illustration in conjunction with this procedure.  You can also view this diagram at slide 541 in http://www.one-world-is.org/rer/owis/gem-core/GEM_Core-Collection.htm.

Endeavor Lifecycle - 32 Questions for Knowledge-Base


0. Identify your enterprise, most typically your organization. For your enterprise, identify the following to the degree you consider economical and relevant. Store and maintain all of this information in a single data store to reduce enterprise operational and analytical fragmentation.

1. What locations are relevant to you? Where do you operate?

2. What is your organization’s name? What are the organization names of your value-chain stakeholders (i.e., customers, suppliers, authorities, your own performers, your subordinate organizations, public groups, and partners), and what are their locations which are relevant to you?

3. What are your organization’s internal units, as typically portrayed as blocks on an organization chart, or more formally identified by a budget, plan, or program within your organization’s aggregate financial management plan? What are the relevant organization units of the value-chain organizations within your organization unit?

4. What are the functions (i.e., assigned work) performed by your organization units? What are the relevant functions performed by their relevant organization unit value-chains?

5. What is the mission of each organizational unit’s function?

6. What policy (minimally the values and perspective per the Carver Policy Governance method) governs the function?

7. Which person, identified by name, unique identifier, and assigned position, is responsible for achieving the function’s mission?

8. What is the boundary of the functional mission’s authority in terms of function, functional interfaces, organization units, organizations, and locations?

9. What is the responsible person’s vision of perfect mission performance?

10. What measurable goals has the responsible person defined to achieve the vision of perfect mission performance?

11. What performance targets (e.g., objectives), specified in terms of schedule, cost, and quality, has the responsible person defined to attain these goals?

12. What quantitative performance success indicators give proof of reaching the objective on time, within budget, to the required quality specified?

13. What strategies, including executing portfolios of investments to organized and prioritized to achieve the success indicators, will enable the responsible person to quantitatively prove, through meeting the specified performance indicators, that they have attained their objectives, and thus goals, and thus mission?

14. What plans, either for recurring (e.g., steady-state) operations or new initiative projects, will be used to implement each strategy?

15. What process will be followed in performing the planned recurring operation or initiative project?

16. What specific procedure will be followed at each defined step of the process, by which Organization Unit, within which Organization, at which Location?

17. What template will be used to collect or present information used in the procedure, and is this template automated (e.g., online form, web service) or manual (paper)?

18. What constraints, rules, or principles must be complied with in using the template?

(Overlapping/interfacing with above Section 2 Data Architecture in items 19-21)

19. What metadata does the template and constraint contain, and what specific semantically-controlled term does the metadata represent?

20. What is the unique ID for each metadata item in each template and each constraint?

21. What is the procedural transaction data for each metadata item in the template or constraint?

(Overlapping/interfacing with above Section 1 Solution and Technology Architectures in items 22 - 24)

22. What equipment, infrastructure, systems, software systems, supplies, and/or service is required to complete the procedure, in what quantity, with what qualities, on what schedule?

23. What category describes each equipment, infrastructure, systems, software systems, supply, and service resource, and is this category approved by the enterprise’s architecture (i.e., component and interface) control authority to avoid wild variance in enterprise resources?

24. What are the item/product/vendor specifics of the equipment, supply or service required for the procedure, and is this technology ubiquitous, in early adoption, or in the research stage?

25. What are the collected requirements, defined in terms of procedural performance resources, in specific quantities, with specific qualities, at specific times, at specific cost, for fully implementing the plans?

26. What is the budget in the current and future years for filling the requirements of the plans, for the strategies, in accomplishing the function’s objectives, goals, and mission?

27. What budget line items, in the aggregate, fully describe the requirement?

28. What elements of expense (i.e., pre-established categories of resources) categorize each budget line?

29. As sub-functions, what programs, as collections of inter-related projects, and which program and project managers, are given responsibility for satisfying the requirements?

30. What capability technology insertion, development, and deployment projects are governed by the Program and Project Managers, and what are their detailed performance schedule, budget, and quality constraints? (I recommend you use ANSI 632 System Engineering Process, and ISO 12207 Software Life Cycle Management as guidelines here)

31. What initial and recurring capability prototyping, operations, and maintenance are governed by the Program or Functional Managers, and what are their detailed performance schedule, budget, and quality constraints? (I recommend you use ANSI 632 System Engineering Process, and ISO 12207 Software Life Cycle Management as guidelines here).
After implementing the Section 3 Business Architecture Procedure, including the details of Section 1 Solution and Technical Architecture and Section 2 Data Architecture, you'll be able to generate "line of sight" records about your enterprise, to enable answering almost any "management" question for which you've collected data.  See the following diagram.  You can also view this diagram at slide 475 in http://www.one-world-is.org/rer/owis/gem-core/GEM_Core-Collection.htm.