This diagram type is used to model most of the Business Architecture elements except the Business Processes. It uses the (EA)<sup>2</sup> Business Architecture Toolbox.
(EA)<sup>2</sup> Business Architecture Toolbox
(EA)<sup>2</sup> Business Architecture
External Role – this represents a type of external entity that does business with the enterprise. It may be a human or a business system.
Internal Role – this represents a type of business worker that performs activities within business processes and/or interacts with use cases.
Mission Statement – this is a statement describing the main reason why the enterprise exists which guides everything that is done within the enterprise.
Business Capability – this represents some functionality that the enteprise provides to the External Roles. The set of Business Capabilites describes what the enterprise does to stay in business.
Business Objective – this is something that must be accomplished to eliminate a risk or take advantage of an opportunity.
Business Opportunity -
Business Principle – this is provides the "guiding light" that should be considered in everything that is done by the enterprise
Business Risk -
Policy – a set of similar rules
Rule –a statement that defines or constrains some aspect of the business.
Organization Unit – a department or other organizational grouping which contains Internal Roles.
Function – business functionality that is performed by a single Internal Role. A Function can be used in various Business Processes
Entity – a part of the business that comprise information rather than process. Example: Customer, Purchase Order.
XML Document
(EA)<sup>2</sup> Business Requirements
BusinessNeed – a high level functional requirement that can be elaborated on with use cases. (It's name does not include spaces because it is derived from Sparx Requirement type which has limit on the number of characters in the name).
Quality Attribute – a non-functional requirement, e.g. performance requirements, availability, etc. These can be captured as tagged values on business processes and activities.
Report – a required report.
Use Case – a way in which an Internal Role uses the systemt to realize part of all of a business process or activity
(EA)<sup>2</sup> Business Architecture Configurables
These are user modeled classes that define the values that may be given to other model element's tagged values.
Business Need Priority – used to create the list of priorities for BusinessNeeds. Business Need Priority – examples: <<Business Need Priority>> Must Have, <<Business Need Priority>> Should Have, <<Business Need Priority>>Could Have, <<Business Need Priority>> Must Have
Schedule – used to create the types of schedules that may apply to business processes, activities, ETL Jobs, etc. Examples: <<Schedule>> Monthly, <<Schedule>> Daily, <<Schedule>> Intra-day.
