B. Business Architecture
(
)
Business outcomes. Approach * Knowledge of the Business Architecture is a prerequisite for architechtur work in the other domains (Data, Application, Technology) and so is the first activity that needs to be undertaken * Business Strategy defines *what* to acheive, Business Architecture descripes *how* to acheive it * This Phase is often reqired to demonstrate business value of subsequent work to key stakeholders * Scope depends on existing stregy and planning - update and verkfy - bridge betwen high-level business drivers, strategy and goals and specific busnies requirements * If there is no existing stratgey or plannign ... Approach (continued) Baseline * use existing architecutre descipinos or gather information in whatever format comes to hand * Often done bottom up with working assumptions for high-level archtiectures * Principles, models, standards from not carried forward architectures may have an residual value Business mdoelling * Activity/business process model: Describe funcitons and information exchange between activites * Use- case model: Descibes the business processes of an enterprise in terms of use-cases and actors corresponding to business processes and organizational prticipants (people, organizations etc.) * Class models: Descripbe static information and relationships betwween information Architecture repository * Generic business mdoels relevant ot the organization's industry sector (eg. OMG/TMF) * Business models relevant to common high-level business domain (e.g. REA, STEP) * Enterprise-specfic building blocks and applicable standards