Difference between revisions of "Enterprise Architecture Quarter"

From CNM Wiki
Jump to: navigation, search
(Concepts)
(Concepts)
Line 17: Line 17:
 
#*[[Startup business]] (or, simply, [[startup]]). (1) A [[business]] in its search of its [[business model]], which usually means ways not to depend on external [[funding]]; (2) An [[enterprise]] in the early stages of operations. [[Startup]]s are usually seeking to solve a [[problem]] of fill a need, but there is no hard-and-fast rule for what makes a [[startup]] since situations differ. Often, a company is considered a [[startup]] until they stop referring to themselves as a [[startup]].
 
#*[[Startup business]] (or, simply, [[startup]]). (1) A [[business]] in its search of its [[business model]], which usually means ways not to depend on external [[funding]]; (2) An [[enterprise]] in the early stages of operations. [[Startup]]s are usually seeking to solve a [[problem]] of fill a need, but there is no hard-and-fast rule for what makes a [[startup]] since situations differ. Often, a company is considered a [[startup]] until they stop referring to themselves as a [[startup]].
 
#*[[Operational business]]. Any [[business]], which [[business model]] generates revenue.
 
#*[[Operational business]]. Any [[business]], which [[business model]] generates revenue.
#'''[[System]]'''. A collection of interrelated and/or interdependent elements working together as a unified whole to produce a desired [[output]] out of consumed [[input]] through one or more [[process]]es. System elements can include hardware, software, and people. One system can be a sub-element (or subsystem) of another system.
 
#*[[Mission]]. An undertaking that is supported by the system to be designed to be successful (e.g. space mission).
 
#*[[Open system]]. A [[system]] that interacts with its environment.
 
#*[[Closed system]]. A [[system]] that is not influenced by and does not interact with its environment.
 
#*[[External interface]]. An interface with other systems (hardware, software, and human) that a proposed system will interact with.
 
#*[[System boundary]]. A separation between the interior of a [[system]] and what lies outside.
 
#'''[[System design]]'''. The identification of all the necessary components, their role, and how they have to interact for the system to fulfill its purpose.
 
#*[[System integration]]. The activity of integrating all the components of a system to make sure they work together as intended.
 
#*[[Interdisciplinarity]]. People from different disciplines working together to design systems.
 
#*[[Specification]]. The technical requirements for [[system design]].
 
#'''[[Systems engineering]]'''. The orderly process of bringing a system into being using a systems approach.
 
#*[[Systems approach]]. The application of a systematic disciplined engineering approach that considers the system as a whole, its impact on its environment and continues throughout the lifecycle of a project.
 
#*[[Human factor]]. Also called ergonomics. The scientific discipline of studying interactions between humans and external systems, including human-computer interaction. When applied to design, the study of human factors seeks to optimise both human well-being and system performance.
 
#*[[Datapoint-device architecture]].
 
#*[[Object-oriented modeling]]. An approach to software engineering where software is comprised of components that are encapsulated groups of data and functions which can inherit behavior and attributes from other components; and whose components communicate via messages with one another. In some organizations, the same approach is used for business engineering to describe and package the logical components of the business.
 
#'''[[Context diagram]]'''. An analysis model that illustrates product scope by showing the system in its environment with the external entities (people and systems) that give to and receive from the system.
 
#*[[Context]]. The users, other systems and other features of the environment of the system that the system will interact with.
 
 
#'''[[Innovation]]'''. Taking [[change idea]]s and turning them into new products, product features, production methods, pricing strategies, and ways of [[enterprise administration]].
 
#'''[[Innovation]]'''. Taking [[change idea]]s and turning them into new products, product features, production methods, pricing strategies, and ways of [[enterprise administration]].
 
#*[[Sustaining innovation]]. Small and incremental changes in established products rather than dramatic breakthroughs.
 
#*[[Sustaining innovation]]. Small and incremental changes in established products rather than dramatic breakthroughs.

Revision as of 19:29, 2 May 2018

Enterprise Architecture Quarter (hereinafter, the Quarter) is a lecture introducing the learners to portfolio design primarily through key topics related to enterprise architecture. The Quarter is the third of four lectures of Portfolio Quadrivium, which is the first of seven modules of Septem Artes Administrativi (hereinafter, the Course). The Course is designed to introduce the learners to general concepts in business administration, management, and organizational behavior.


Lecture outline

Feasibility Study Quarter is the predecessor lecture. In the enterprise analysis series, the previous lecture is Enterprise Intelligence Quarter.

Portfolio design is the enterprise design of the enterprise portfolio. This lecture concentrates on enterprise architecture because this architecture is the main outcome from this design.

Concepts

  1. Enterprise architecture. A composition of the interrelated businesses, process assets, enterprise factors, and personnel that together are known as an enterprise.
  2. Enterprise business. The actual or potential practice of making enterprise's profit by engaging in commerce.
    • Business. (1) An individual's regular occupation, profession, or trade; (2) The practice of making one's profit by engaging in commerce.
    • Departmentalization. The basis by which jobs in an enterprise are grouped together.
  3. Efficiency vs effectiveness
    Portfolio engineering. The application of scientific principles to designing and/or modifying of the enterprise portfolio.
  4. Innovation. Taking change ideas and turning them into new products, product features, production methods, pricing strategies, and ways of enterprise administration.
  5. Exit strategy. A business strategy that seeks to withdraw an enterprise out of a particular business at the lowest cost and biggest gain. With regard to startup businesses, this is how their founders usually get rich. An exit strategy is the method by which an investor and/or entrepreneur intends to "exit" their investment in a company. Commons options are an IPO or buyout from another company. Entrepreneurs and venture capitalists often develop an exit strategy while the startup business is still growing.
    • Buyout. A common exit strategy. The purchase of a company's shares that gives the purchaser controlling interest in the company.
    • Liquidation. The process of dissolving a company by selling off all of its assets (making them liquid).
    • IPO. Initial public offering. The first time shares of stock in a company are offered on a securities exchange or to the general public. At this point, a private company turns into a public company (and is no longer a startup).
    • Harvesting. Exiting a venture when an entrepreneur hopes to capitalize financially on the investment in the future.

Roles

  1. Enterprise architect. A practitioner of enterprise architecture.

Instruments

BCG matrix
  1. BCG matrix. A strategy tool that guides resource allocation decisions on the basis of market share and growth rate of strategic business units.

Results

  1. Enterprise portfolio. A collection of all businesses in which a particular enterprise operates.

Practices

Iterative Development Quarter is the successor lecture. In the enterprise design series, the next lecture is Business Modeling Quarter.

Materials

Recorded audio

Recorded video

Live sessions

Texts and graphics

See also