Enterprise systems engineering

Last updated

Enterprise systems engineering (ESE) is the discipline that applies systems engineering to the design of an enterprise. [1] As a discipline, it includes a body of knowledge, principles, and processes tailored to the design of enterprise systems.

Contents

An enterprise is a complex, socio-technical system that comprises interdependent resources of people, information, and technology that must interact to fulfill a common mission. [1]

Enterprise systems engineering incorporates all the tasks of traditional systems engineering but is further informed by an expansive view of the political, operational, economic, and technological (POET) contexts in which the system(s) under consideration are developed, acquired, modified, maintained, or disposed.[ citation needed ] [2]

Enterprise systems engineering may be appropriate when the complexity of the enterprise exceeds the scope of the assumptions upon which textbook systems engineering are based. Traditional systems engineering assumptions include relatively stable and well understood requirements, a system configuration that can be controlled, and a small, easily discernible set of stakeholders.[ citation needed ]

An enterprise systems engineer must produce a different kind of analysis on the people, technology, and other components of the organization in order to see the whole enterprise. As the enterprise becomes more complex, with more parameters and people involved, it is important to integrate the system as much as possible to enable the organization to achieve a higher standard. [3]

Elements

Four elements are needed for enterprise systems engineering to work. These include development through adaption, strategic technical planning, enterprise governance, and ESE processes (with stages). [4]

Development through adaptation

Development through adaptation is a way to compromise with the problems and obstacles in complex systems. Over time, the environment changes and adaptation is required to continue development. For example, mobile phones have undergone numerous modifications since their introduction. Initially, the devices were considerably larger than those seen in later iterations. Over time, variations in size and design have been observed across different generations of mobile phones. Additionally, the evolution of mobile data technology from 1G to 5G has influenced the speed and convenience of mobile phone usage. [5]

Strategic technical planning

Strategic technical planning (STP) gives the enterprise the picture of their aim and objectives. STP components are: [6] [7]

Enterprise governance

Enterprise governance is defined as 'the set of responsibilities and practices exercised by the board and executive management to provide strategic direction, ensure that objectives are achieved, ascertain that risks are managed appropriately and verify that the organization's resources are used responsibly,' according to CIMA Official Terminology. [8] EG allows one to make the right decision on the choice of CEO and executives for the company, and also to identify the risks of the company. [9]

Processes

Four steps comprise the enterprise system engineering process: technology planning (TP); capabilities-based engineering analysis (CBEA); enterprise architecture (EA); and enterprise analysis and assessment (EA&A). [10] [3]

Technology planning

TP looks for technologies key to the enterprise. This step aims to identify the innovative ideas and choose the technologies that are useful for the enterprise.[ citation needed ]

Capabilities-based engineering analysis

CBEA is an analysis method that focuses on elements that the whole enterprise needs. [11] The three steps are purpose formulation, exploratory analysis, and evolutionary planning:

Purpose formulation

  • Assess stakeholder Interest – understand what the stakeholders want and like
  • Specify outcome spaces – find solutions for several conditions and the goal for the operations
  • Frame capability portfolios - collect fundamental elements

Exploratory analysis

  • Assess performance and cost – identify the performance and cost in different conditions and find solutions to improve
  • Explore concepts – search for new concepts and transform advanced capabilities
  • Determine the need for more variety – examine the risks and chances and decide whether new ways are needed

Evolutionary planning

  • Assess enterprise impacts – investigate the effects on the enterprise in technical and capability aspects
  • Examine evolution strategies – explore and construct more strategies and evolution route
  • Develop capability road map – plan for the capability area which includes analysis and decision making which is a tool for assessment and development for the enterprise

Enterprise architecture

The prospective of Enterprise Architecture Enterprise Architecture Domain Reference Architecture.JPG
The prospective of Enterprise Architecture

EA is a model that illustrates the vision, network and framework of an organization. The four aspects (according to Michael Platt) are business prospects, application, information and technology. [12] The diagram shows the structure of enterprise architecture. The benefits are improvement of decision making, increased IT efficiency and minimizes losses. [13]

All the elements are dependent and rely on each other in order to build the infrastructure. [14]

Enterprise analysis and assessment

Enterprise analysis and assessment aims to assess whether the enterprise is going in the right direction and help to make correct decisions. Qualities required for this step include awareness of technologies, knowing and understanding command and control (C2) issues, and using modeling and simulation (M&S) explore the implications. [15]

Activities and actions for this event include:

Traditional systems engineering

Traditional systems engineering (TSE) is a term to be defined as an engineering sub-system. [16] [17] Elements:

A survey compared ESE and TSE. The survey reported that the two are complementary and interdependent. ESE had a higher rating while TSE could be part of ESE. The combination could be ideal. [18]

Applications

The two types of ESE application are Information Enterprise Systems Engineering and Social Enterprise Systems Engineering.

Information Enterprise Systems Engineering (IESE)

It is a system that builds up to meet the requirements and expectations of different stakeholders in the organization. There must be an input device to collect the information and output device to satisfy the information needs. [19]

There are three different aspects for the framework of IESE:

Also, there are different rules for the IESE model. [20]

Social Enterprise System Engineering

This is a framework that involves planning, analyzing, mapping, and drawing a network of the process for enterprises and stakeholders. Moreover, it creates social value for entrepreneurship and explores and focuses on social and societal issues. It forms a connection between social enterprise and system engineering. There is a Social Enterprise Systems Engineering V-model, in which two or more social elements are established based on the system engineering framework—for example, more social interface analysis that reviews stakeholders' requirements, and more activities and interactions between stakeholders to exchange opinion. [21]

Opportunity and risk management

There are opportunities and risks in ESE and they have to be aggressive in seeking opportunities and also finding ways to avoid or minimize the risks. Opportunity is a trigger element that may lead to the accomplishment of objectives. Risk is a potential occurrence and will affect the performance of the entire system. [22] There are several reasons for the importance of risk management. [23]

  1. To identify the risks before head which can prepare actions to prevent or minimize the risks
  2. Since risks can cost the enterprise, determining the risk events can reduce the amount of loss
  3. Help to know how to allocate the human or technology resources in order avoid the most critical risks

There are few steps in Enterprise risk and opportunity Management Process

See also

Related Research Articles

<span class="mw-page-title-main">Risk management</span> Identification, evaluation and control of risks

Risk management is the identification, evaluation, and prioritization of risks followed by coordinated and economical application of resources to minimize, monitor, and control the probability or impact of unfortunate events or to maximize the realization of opportunities.

<span class="mw-page-title-main">Systems engineering</span> Interdisciplinary field of engineering

Systems engineering is an interdisciplinary field of engineering and engineering management that focuses on how to design, integrate, and manage complex systems over their life cycles. At its core, systems engineering utilizes systems thinking principles to organize this body of knowledge. The individual outcome of such efforts, an engineered system, can be defined as a combination of components that work in synergy to collectively perform a useful function.

<span class="mw-page-title-main">Software architecture</span> High level structures of a software system

Software architecture is the set of structures needed to reason about a software system and the discipline of creating such structures and systems. Each structure comprises software elements, relations among them, and properties of both elements and relations.

Information technology (IT)governance is a subset discipline of corporate governance, focused on information technology (IT) and its performance and risk management. The interest in IT governance is due to the ongoing need within organizations to focus value creation efforts on an organization's strategic objectives and to better manage the performance of those responsible for creating this value in the best interest of all stakeholders. It has evolved from The Principles of Scientific Management, Total Quality Management and ISO 9001 Quality management system.

System of systems is a collection of task-oriented or dedicated systems that pool their resources and capabilities together to create a new, more complex system which offers more functionality and performance than simply the sum of the constituent systems. Currently, systems of systems is a critical research discipline for which frames of reference, thought processes, quantitative analysis, tools, and design methods are incomplete. The methodology for defining, abstracting, modeling, and analyzing system of systems problems is typically referred to as system of systems engineering.

Enterprise architecture (EA) is a business function concerned with the structures and behaviours of a business, especially business roles and processes that create and use business data. The international definition according to the Federation of Enterprise Architecture Professional Organizations is "a well-defined practice for conducting enterprise analysis, design, planning, and implementation, using a comprehensive approach at all times, for the successful development and execution of strategy. Enterprise architecture applies architecture principles and practices to guide organizations through the business, information, process, and technology changes necessary to execute their strategies. These practices utilize the various aspects of an enterprise to identify, motivate, and achieve these changes."

<span class="mw-page-title-main">Department of Defense Architecture Framework</span> Enterprise architecture framework

The Department of Defense Architecture Framework (DoDAF) is an architecture framework for the United States Department of Defense (DoD) that provides visualization infrastructure for specific stakeholders concerns through viewpoints organized by various views. These views are artifacts for visualizing, understanding, and assimilating the broad scope and complexities of an architecture description through tabular, structural, behavioral, ontological, pictorial, temporal, graphical, probabilistic, or alternative conceptual means. The current release is DoDAF 2.02.

Business analysis is a professional discipline focused on identifying business needs and determining solutions to business problems. Solutions may include a software-systems development component, process improvements, or organizational changes, and may involve extensive analysis, strategic planning and policy development. A person dedicated to carrying out these tasks within an organization is called a business analyst or BA.

A federal enterprise architecture framework (FEAF) is the U.S. reference enterprise architecture of a federal government. It provides a common approach for the integration of strategic, business and technology management as part of organization design and performance improvement.

Technology strategy is the overall plan which consists of objectives, principles and tactics relating to use of technologies within a particular organization. Such strategies primarily focus on the technologies themselves and in some cases the people who directly manage those technologies. The strategy can be implied from the organization's behaviors towards technology decisions, and may be written down in a document. The strategy includes the formal vision that guide the acquisition, allocation, and management of IT resources so it can help fulfill the organizational objectives.

<span class="mw-page-title-main">System Architect</span> Enterprise architecture tool

Unicom System Architect is an enterprise architecture tool that is used by the business and technology departments of corporations and government agencies to model their business operations and the systems, applications, and databases that support them. System Architect is used to build architectures using various frameworks including TOGAF, ArchiMate, DoDAF, MODAF, NAF and standard method notations such as sysML, UML, BPMN, and relational data modeling. System Architect is developed by UNICOM Systems, a division of UNICOM Global, a United States-based company.

<span class="mw-page-title-main">Enterprise architecture framework</span> Frame in which the architecture of a company is defined

An enterprise architecture framework defines how to create and use an enterprise architecture. An architecture framework provides principles and practices for creating and using the architecture description of a system. It structures architects' thinking by dividing the architecture description into domains, layers, or views, and offers models – typically matrices and diagrams – for documenting each view. This allows for making systemic design decisions on all the components of the system and making long-term decisions around new design requirements, sustainability, and support.

Information security management (ISM) defines and manages controls that an organization needs to implement to ensure that it is sensibly protecting the confidentiality, availability, and integrity of assets from threats and vulnerabilities. The core of ISM includes information risk management, a process that involves the assessment of the risks an organization must deal with in the management and protection of assets, as well as the dissemination of the risks to all appropriate stakeholders. This requires proper asset identification and valuation steps, including evaluating the value of confidentiality, integrity, availability, and replacement of assets. As part of information security management, an organization may implement an information security management system and other best practices found in the ISO/IEC 27001, ISO/IEC 27002, and ISO/IEC 27035 standards on information security.

<span class="mw-page-title-main">ArchiMate</span> Enterprise architecture modeling language

ArchiMate is an open and independent enterprise architecture modeling language to support the description, analysis and visualization of architecture within and across business domains in an unambiguous way.

A glossary of terms relating to project management and consulting.

<span class="mw-page-title-main">View model</span>

A view model or viewpoints framework in systems engineering, software engineering, and enterprise engineering is a framework which defines a coherent set of views to be used in the construction of a system architecture, software architecture, or enterprise architecture. A view is a representation of the whole system from the perspective of a related set of concerns.

<span class="mw-page-title-main">Enterprise Architecture Assessment Framework</span>

The Enterprise Architecture Assessment Framework (EAAF) was created by the US Federal government Office of Management and Budget (OMB) to allow federal agencies to assess and report their enterprise architecture activity and maturity, and advance the use of enterprise architecture in the federal government.

<span class="mw-page-title-main">Business Motivation Model</span>

The Business Motivation Model (BMM) in enterprise architecture provides a scheme and structure for developing, communicating, and managing business plans in an organized manner. Specifically, the Business Motivation Model does all the following:

In software engineering, a software development process or software development life cycle (SDLC) is a process of planning and managing software development. It typically involves dividing software development work into smaller, parallel, or sequential steps or sub-processes to improve design and/or product management. The methodology may include the pre-definition of specific deliverables and artifacts that are created and completed by a project team to develop or maintain an application.

<span class="mw-page-title-main">TRAK</span> Enterprise architecture framework

TRAK, or The Rail Architecture Framework, is a general enterprise architecture framework aimed at systems engineers. It is based on MODAF 1.2.

References

  1. 1 2 R.E. Giachetti (2010). Design of Enterprise Systems: Theory, Architecture, and Methods, CRC Press, Boca Raton, Florida, p. 3
  2. "Tools to Enable a Comprehensive Viewpoint". 28 August 2013.
  3. 1 2 Joannou, Paul (2007). "Enterprise, Systems, and Software Engineering--The Need for Integration". Computer. 40 (5): 103–5. doi:10.1109/mc.2007.167. S2CID   1856609.
  4. Enterprise Systems Engineering: Advances in the Theory and Practice. Boca Raton ; London : CRC Press. 2011. p. 8. ISBN   978-1420073294.
  5. "1G, 2G, 3G, 4G: The evolution of wireless generations". Phone Arena. Retrieved 2015-11-01.
  6. Strategic Technology Plan
  7. "What is strategic planning? - Definition from WhatIs.com". SearchCIO. Retrieved 2015-11-01.
  8. Lees, Gillian (June 2007). "Enterprise Governance" (PDF). CIMA. Retrieved 2015-11-02.
  9. "Enterprise Governance – A CIMA discussion paper" (PDF). CIMA. Retrieved 2015-11-02.
  10. Crider, Kimberly A.; Derosa, Joseph K. (2007). "Findings of Case Studies in Enterprise Systems Engineering". 2007 1st Annual IEEE Systems Conference. pp. 1–6. doi:10.1109/SYSTEMS.2007.374650. ISBN   978-1-4244-1040-8. S2CID   12525506.
  11. Webb, Mike. "Capabilities-Based Engineering Analysis (CBEA)" (PDF). The MITRE Corporation. Retrieved 2015-11-02.
  12. "What is enterprise architecture (EA)? - Definition from WhatIs.com". SearchCIO. Retrieved 2015-11-02.
  13. "Enterprise Architecture | Centric". Centric Consulting. Retrieved 2015-11-02.
  14. "DTS Enterprise Architecture". www.montgomerycountymd.gov. Retrieved 2015-11-02.
  15. Roberts, John (2006). "Enterprise Analysis and Assessment of Complex Military Command and Control Environments" (PDF). The MITRE Corporation. Retrieved 2015-11-03.
  16. Hybertson, Duane (2009). Model-oriented systems engineering science : a unifying framework for traditional and complex systems . Boca Raton ; London : CRC Press. pp.  2. ISBN   9781420072518.
  17. Rebovich, George (November 2005). "Enterprise Systems Engineering Theory and Practice Volume 2: Systems Thinking for the Enterprise: New and Emerging Perspectives" (PDF). The MITRE Corporation. Retrieved 2015-11-03.
  18. White, Brian. "On the Pursuit of Enterprise Systems Engineering Ideas" (PDF). The MITRE Corporation. Retrieved 2015-11-03.
  19. Snoeck, Monique (2014-09-20). Enterprise Information Systems Engineering: The MERODE Approach. Springer. p. 70. ISBN   9783319101453.
  20. Nikolaidou, M. and Alexopoulou, N. (2007). Enterprise Information System Engineering: A Model-based Approach based on the Zachman Framework. 1st ed. [pdf] Department of Informatics & Telecommunications, University of Athens, Athens, Greece: arokopio University of Athens, Athens, Greece, pp.1-10. Available at: [Accessed 3 Nov. 2015].
  21. Mason, James (2015). "Social Enterprise Systems Engineering". Procedia Computer Science. 44: 135–46. doi: 10.1016/j.procs.2015.03.067 .
  22. White, B. (2006). Enterprise Opportunity and Risk. 1st ed. [pdf] 202 Burlington Road Bedford, MA: INCOSE, pp.3-6. Available at: [Accessed 3 Nov. 2015].
  23. Pinto, Cesar Ariel; Garvey, Paul R. (2012-10-08). Advanced Risk Analysis in Engineering Enterprise Systems. CRC Press. pp. 6–7. ISBN   9781439826157.

24. "Enterprise Architecture | Centric". Business Consulting. Retrieved 2024-1-30.

Further reading