Difference between revisions of "Enterprise Architecture (EA)"
m |
m (→Conway's Law) |
||
(14 intermediate revisions by the same user not shown) | |||
Line 8: | Line 8: | ||
[https://www.google.com/search?q=Enterprise+Architecture+artificial+intelligence+deep+learning+AI ...Google search] | [https://www.google.com/search?q=Enterprise+Architecture+artificial+intelligence+deep+learning+AI ...Google search] | ||
− | + | * [[Architectures]] for AI ... [[Generative AI Stack]] ... [[Enterprise Architecture (EA)]] ... [[Enterprise Portfolio Management (EPM)]] ... [[Architecture and Interior Design]] | |
− | + | * [[Strategy & Tactics]] ... [[Project Management]] ... [[Best Practices]] ... [[Checklists]] ... [[Project Check-in]] ... [[Evaluation]] ... [[Evaluation - Measures|Measures]] | |
− | + | * [[Analytics]] ... [[Visualization]] ... [[Graphical Tools for Modeling AI Components|Graphical Tools]] ... [[Diagrams for Business Analysis|Diagrams]] & [[Generative AI for Business Analysis|Business Analysis]] ... [[Requirements Management|Requirements]] ... [[Loop]] ... [[Bayes]] ... [[Network Pattern]] | |
− | + | * [[Development]] ... [[Notebooks]] ... [[Development#AI Pair Programming Tools|AI Pair Programming]] ... [[Codeless Options, Code Generators, Drag n' Drop|Codeless]] ... [[Hugging Face]] ... [[Algorithm Administration#AIOps/MLOps|AIOps/MLOps]] ... [[Platforms: AI/Machine Learning as a Service (AIaaS/MLaaS)|AIaaS/MLaaS]] | |
− | + | * [[Risk, Compliance and Regulation]] ... [[Ethics]] ... [[Privacy]] ... [[Law]] ... [[AI Governance]] ... [[AI Verification and Validation]] | |
− | + | * [[Perspective]] ... [[Context]] ... [[In-Context Learning (ICL)]] ... [[Transfer Learning]] ... [[Out-of-Distribution (OOD) Generalization]] | |
− | + | * [[Causation vs. Correlation]] ... [[Autocorrelation]] ...[[Convolution vs. Cross-Correlation (Autocorrelation)]] | |
− | + | * [[Excel]] ... [[LangChain#Documents|Documents]] ... [[Database|Database; Vector & Relational]] ... [[Graph]] ... [[LlamaIndex]] | |
− | ** [[Development]] | ||
− | |||
− | |||
− | |||
− | |||
− | * [[ | ||
− | * [[ | ||
* [[Defense]]: [[Joint Capabilities Integration and Development System (JCIDS)]] | * [[Defense]]: [[Joint Capabilities Integration and Development System (JCIDS)]] | ||
− | |||
* [https://www.nist.gov/cyberframework Cybersecurity Framework | NIST] | * [https://www.nist.gov/cyberframework Cybersecurity Framework | NIST] | ||
** [https://csrc.nist.gov/projects/risk-management/risk-management-framework-(RMF)-Overview Risk Management Framework (RMF) - NIST] | ** [https://csrc.nist.gov/projects/risk-management/risk-management-framework-(RMF)-Overview Risk Management Framework (RMF) - NIST] | ||
Line 54: | Line 46: | ||
*** [https://www.orbussoftware.com/ppc/archimate-30-starter-pack/ ArchiMate Orbus] …[https://publications.opengroup.org/guides/archimate Guide] | *** [https://www.orbussoftware.com/ppc/archimate-30-starter-pack/ ArchiMate Orbus] …[https://publications.opengroup.org/guides/archimate Guide] | ||
− | In order to bring measurable value to their firms, Enterprise Architects of Tomorrow must understand, utilize, and evangelize the latest technologies driving the industry. These current trends include | + | In order to bring measurable value to their firms, Enterprise Architects of Tomorrow must understand, utilize, and evangelize the latest technologies driving the industry. These current trends include [[Predictive Analytics]], [[Deep Learning]], prescriptive analytics, and [[Machine Learning (ML)]]. All of these trends use current data to make predictions about unknown future events. [https://blog.leanix.net/en/an-enterprise-architects-guide-to-machine-learning-series-part-1 Lesa Moné | LeanIX] |
==== Architecture Attributes for AI ==== | ==== Architecture Attributes for AI ==== | ||
Line 72: | Line 64: | ||
* Dropout rate (or not) | * Dropout rate (or not) | ||
* Threshold | * Threshold | ||
+ | |||
+ | |||
+ | <hr> | ||
+ | <center><b><i>Architecture drives data (management) which is the 'oil of machine intelligence'</i></b></center> | ||
+ | <hr> | ||
+ | |||
Line 140: | Line 138: | ||
** An example can be ‘Assign Sales person’ – essentially through a mechanism that is to be followed for assigning a particular sales person on availability to the customer – the service that helps to locate the next available sales person to be booked. Another example can be ‘update customer details’ as they apply for the offer through a system/application. Remember these services can be called upon by other processes also – ‘Assign sales person’ can be used to assign sales person for solving a customer complaint as well. | ** An example can be ‘Assign Sales person’ – essentially through a mechanism that is to be followed for assigning a particular sales person on availability to the customer – the service that helps to locate the next available sales person to be booked. Another example can be ‘update customer details’ as they apply for the offer through a system/application. Remember these services can be called upon by other processes also – ‘Assign sales person’ can be used to assign sales person for solving a customer complaint as well. | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
= Enterprise Architecture Frameworks = | = Enterprise Architecture Frameworks = | ||
Line 260: | Line 251: | ||
<youtube>MuG5JGi2CZo</youtube> | <youtube>MuG5JGi2CZo</youtube> | ||
<b>Introduction to Enterprise Architecture | <b>Introduction to Enterprise Architecture | ||
− | </b><br>The Zachman Framework™ is an enterprise ontology and metamodel for enterprise architecture. which provides a formal and structured way of viewing and defining an enterprise. The ontology is a two dimensional classification schema that reflects the intersection between two historical classifications. The Zachman Framework is not a methodology, like the TOGAF® Architecture [[Development]] Method (ADM), but rather a template describing how different abstract ideas are viewed from different perspectives. It is an ontology matrix simply that helps to form a logical structure for classifying and organizing artifacts developed in enterprise architecture. Zachman is focused on identifying the different viewpoints that might be relevant for different purposes while TOGAF is focused on the process of developing architectures. Presenter: John A. Zachman | + | </b><br>The Zachman Framework™ is an enterprise [[Graph#Ontology|ontology]] and metamodel for enterprise architecture. which provides a formal and structured way of viewing and defining an enterprise. The [[Graph#Ontology|ontology]] is a two dimensional classification schema that reflects the intersection between two historical classifications. The Zachman Framework is not a methodology, like the TOGAF® Architecture [[Development]] Method (ADM), but rather a template describing how different abstract ideas are viewed from different perspectives. It is an [[Graph#Ontology|ontology]] matrix simply that helps to form a logical structure for classifying and organizing artifacts developed in enterprise architecture. Zachman is focused on identifying the different viewpoints that might be relevant for different purposes while TOGAF is focused on the process of developing architectures. Presenter: John A. Zachman |
|} | |} | ||
|<!-- M --> | |<!-- M --> | ||
Line 325: | Line 316: | ||
<img src="https://PRIMO.AI/BCM/BCM.InformationLevels.jpg" width="800"> | <img src="https://PRIMO.AI/BCM/BCM.InformationLevels.jpg" width="800"> | ||
+ | |||
+ | = <span id="Conway's Law"></span>Conway's Law = | ||
+ | |||
+ | Conway's Law is an adage in the field of software development, coined by computer programmer Melvin Conway in 1968. It states that "organizations which design systems ... are constrained to produce designs which are copies of the communication structures of these organizations." In simpler terms, the structure of a software system tends to mirror the communication structure of the organization that produces it. | ||
+ | |||
+ | <hr> | ||
+ | |||
+ | <center><b><i>Any organization that designs a system (defined broadly) will produce a design whose structure is a copy of the organization's communication structure.</i> — Melvin E. Conway</b> [https://en.wikipedia.org/wiki/Conway%27s_law - Conway's Law]</center> | ||
+ | |||
+ | <hr> | ||
+ | |||
+ | This principle implies that the way a team is organized, the communication channels between team members, and the dynamics of collaboration will inevitably influence the design and architecture of the software they create. For instance, if a team is organized into separate functional silos, with limited communication between them, the resulting software might end up being composed of distinct modules that correspond to those silos, potentially leading to integration challenges and inefficiencies. | ||
+ | |||
+ | In the context of AI development, Conway's Law suggests that the organization of teams working on AI projects will impact the design and structure of the AI systems they produce. If teams are organized around specific AI techniques or technologies (e.g., natural language processing, computer vision), the resulting AI systems may reflect this organizational structure, potentially leading to disjointed or fragmented solutions. Conway's Law serves as a reminder that the social and organizational aspects of AI development are as crucial as the technical aspects, and paying attention to how teams are organized and how they communicate can ultimately impact the quality and effectiveness of the AI systems they produce. | ||
= <span id="ITIL - IT Service Management"></span>ITIL - IT Service Management = | = <span id="ITIL - IT Service Management"></span>ITIL - IT Service Management = | ||
Line 398: | Line 403: | ||
<youtube>J5uaKjNKbw8</youtube> | <youtube>J5uaKjNKbw8</youtube> | ||
<b>Transforming Organizational Capability and Performance Using CMMI V2.0 | Ronald Lear | <b>Transforming Organizational Capability and Performance Using CMMI V2.0 | Ronald Lear | ||
− | </b><br>Key Topics covered include: Operational Excellence Business Transformation Lean Transformation Lean Manufacturing Six Sigma Continuous Improvement Digital Transformation Cultural Transformation Agile & Agile Culture Business Process Management / iBPM Robotic Process Automation (RPA) Download the FREE 130 pages research report, the most comprehensive study of critical challenges and future trends within Operational Excellence. https://bit.ly/BTOEreport | + | </b><br>Key Topics covered include: Operational Excellence Business Transformation Lean Transformation Lean Manufacturing Six Sigma Continuous Improvement Digital Transformation Cultural Transformation Agile & Agile Culture Business Process Management / iBPM [[Robotic Process Automation (RPA)]] Download the FREE 130 pages research report, the most comprehensive study of critical challenges and future trends within Operational Excellence. https://bit.ly/BTOEreport |
|} | |} | ||
|<!-- M --> | |<!-- M --> |
Latest revision as of 10:24, 7 June 2024
Youtube search... ...Google search
- Architectures for AI ... Generative AI Stack ... Enterprise Architecture (EA) ... Enterprise Portfolio Management (EPM) ... Architecture and Interior Design
- Strategy & Tactics ... Project Management ... Best Practices ... Checklists ... Project Check-in ... Evaluation ... Measures
- Analytics ... Visualization ... Graphical Tools ... Diagrams & Business Analysis ... Requirements ... Loop ... Bayes ... Network Pattern
- Development ... Notebooks ... AI Pair Programming ... Codeless ... Hugging Face ... AIOps/MLOps ... AIaaS/MLaaS
- Risk, Compliance and Regulation ... Ethics ... Privacy ... Law ... AI Governance ... AI Verification and Validation
- Perspective ... Context ... In-Context Learning (ICL) ... Transfer Learning ... Out-of-Distribution (OOD) Generalization
- Causation vs. Correlation ... Autocorrelation ...Convolution vs. Cross-Correlation (Autocorrelation)
- Excel ... Documents ... Database; Vector & Relational ... Graph ... LlamaIndex
- Defense: Joint Capabilities Integration and Development System (JCIDS)
- Cybersecurity Framework | NIST
- Cloud Design Patterns | Microsoft
- Technology Business Management (TBM)
- What is Zero Trust? A model for more effective security - Zero Trust Architecture (ZTA) | Mary K. Pratt - CSO
- Becoming NetCentric - Leveraging an Information Network with Communities of Interests, Architectures, and Ontologies
- Tackling artificial intelligence using architecture | Daniel Lambert - CIO
- How can Machine Learning help the Enterprise Architect? | Crayon
- Machine learning may supercharge enterprise architecture | Joe McKendrick - Service Oriented - ZDNet
- Building a Cognitive Enterprise Architecture | Josh Sutton - CIOReview
- How to Get AI Right Using Enterprise Architecture | Raz Mitache - BiZZdesign
- What exactly does an AI architect do? | Jenny Darmody - SiliconRepublic
- Applied Enterprise Architecture | James Parnitzke
- Intersection of Artificial Intelligence and Architecture | Raj Ramesh
- There's No AI (Artificial Intelligence) without IA (Information Architecture) | Seth Earley - InfoQ
- Data Architecture and Artificial Intelligence: How Do They Work Together? | Paramita Ghosh
- AIOps/MLOps
- AI Models for Business Process Reengineering | E. Yu, J. Mylopoulos, and Y. Lesperance - Enterprise Modeling
- A knowledge-based approach for business process reengineering, SHAMASH | R. Aler, D. Borrajo, D. Camacho, and A. Sierra-Alonso
- Tools:
In order to bring measurable value to their firms, Enterprise Architects of Tomorrow must understand, utilize, and evangelize the latest technologies driving the industry. These current trends include Predictive Analytics, Deep Learning, prescriptive analytics, and Machine Learning (ML). All of these trends use current data to make predictions about unknown future events. Lesa Moné | LeanIX
Contents
Architecture Attributes for AI
- Variables type
- Variable scaling
- Cost function
- Type of neural network - CNN, RNN, FFN
- Number of layers, hidden
- Type of layers
- LSTM, Dense, Highway
- Convolutional
- Pooling
- Weight initialization type
- Number of nodes
- Type of activation function - linear, Sigmoid, ReLU
- Dropout rate (or not)
- Threshold
|
|
|
|
Taxonomy
Youtube search... ...Google search
- Taxonomy for Process/Capability/Function/Service | Eswar Ganesan | Toolbox
- How do you differentiate between a Business Function and a Capability? and Service, function and capability (again) | Tom Graves
- Service vs. Capability vs. Process | Daniel Dekkers
- Business Functions vs. Business Capabilities- how is your company handling these? | Mike Robison
- The TOGAF® Standard, Version 9.2 Definitions | The Open Group
- Function vs Activity - The Difference | Functionly
- Define Your Terms | Fred Nickols ...Clearing Up the Confusion Among Function, Process, Procedure, Operation, Task, Step and Activity
- Capability - what ability to do something; in terms of expertise and capacity realized by its people, processes, information, and technology; focused on specific business outcomes. Used for strategic planning purposes on its own, a capability literally has no function.
- Examples of Capabilities include: Capability to sell a new Product, Capability for eCommerce, Capability for rapid merger and acquisition activities, Capability to survive the credit crunch, Capability to conduct research, Capability to achieve delivery objectives and be ready for future unknown challenges. An example for capabilities can be ‘Manage Offers’ – the skills required by the role-players in effectively managing the business processes – effective in presenting the offer with brochures, advertisements etc, effective in negotiating with the customers to make them accept the offer, effective in shipping the goods quickly to reach the customer as well effective in collecting checks at the shortest possible time from customers.
- Function - what something does or is used for; encapsulating terms such as value chain, process area, capability, business function, etc. a function needs to be linked to a capability in order to do anything. The people who possess the specialized skills found in a functional area are typically organized into a system of hierarchically distributed authority (i.e., reporting relationships).
- Examples of Functions include: Sales, Mаrketing, Supply Chаin Management, Finаnciаl Mаnаgement, Operations, Customer Relationship Management, Product Management, Supplier/Pаrtner Relаtionship Mаnаgement. An example can be ‘Sales Function’ which includes the related processes of fulfill an offer, advertise the offer, manage funds for offers, analyze need for offers and fine tune processes of similar nature as required for effectively managing it. Functions help manage processes effectively.
- Activity - how the functional objective is achieved; traditionally a granular very specific action. One of the more common work activities with a clearly defined beginning and ending is the task. Task descriptions are often referred to as procedures.
- Examples of Activities include: To answer phones, make travel arrangements and cover reception during lunch, monthly meeting with team to walk through plan, make adjustments to the strategy, Send to CEO for review and set meeting to discuss
- Process - Series of services together in some way to achieve some kind of outcome; may include systematic purposeful concepts, activities, courses of action, sequences, structures, interactions, rules, policies, and procedures that govern a system or enterprise. The process view is a horizontal view; it is concerned with flows; it is often the case that no one individual is accountable for processes that cross functional boundaries.
- An example may be ‘Fulfill an offer’ – series of activities can be make an offer to the customer, accept offer by the customer, provide terms and conditions related to the offer to customers, accept the terms and conditions by the customer, dispatch the goods to the customer with invoice, collect the amount and close the deal.
- Service - everything can be represented as a service; function and capability are linked together in order to create a service. A physical service enables access to a set of one or more capabilities consistent with constraints and policies.
- An example can be ‘Assign Sales person’ – essentially through a mechanism that is to be followed for assigning a particular sales person on availability to the customer – the service that helps to locate the next available sales person to be booked. Another example can be ‘update customer details’ as they apply for the offer through a system/application. Remember these services can be called upon by other processes also – ‘Assign sales person’ can be used to assign sales person for solving a customer complaint as well.
Enterprise Architecture Frameworks
|
|
|
|
The OpenGroup Architecture Framework (TOGAF®)
Youtube search... ...Google search
|
|
DOD Architecture Framework (DoDAF)
Youtube search... ...Google search
|
|
Zachman Framework
Youtube search... ...Google search
|
|
Federal Enterprise Architecture (FEA)
Youtube search... ...Google search
|
|
Business-Centric Methodology (BCM)
- Business-Centric Methodology (BCM) | OASIS
- BCM Brochure | Bruce Peat, Mike Lubash - OASIS
- BCM Executive White Paper | OASIS
- BCM Specification | OASIS
- BCM Specification Appendix B: Linking and Switching with Context and Choice Points | OASIS
- BCM Developing For Choice | Audrey Davis - Defense Finance Accounting Service (DFAS)
- BCM Event Template to Financial Management | Bruce Peat
- BCM Event Template | OASIS
- BCM Checklist | OASIS
- BCM.BecomingNetCentric.2003-06-18a.pdf | Bruce Peat
- Posters | Bruce Peat:
The OASIS Business-Centric Methodology (BCM) is a specification that provides business managers with a set of clearly defined methods with which to acquire agile and interoperable e-business information systems within communities of interests. Defining methods to acquire interoperable e-business information systems within communities of interest.
Mindmap: https://PRIMO.AI/BCM/BCM_MindMap_2003-10-18.bmp
Conway's Law
Conway's Law is an adage in the field of software development, coined by computer programmer Melvin Conway in 1968. It states that "organizations which design systems ... are constrained to produce designs which are copies of the communication structures of these organizations." In simpler terms, the structure of a software system tends to mirror the communication structure of the organization that produces it.
This principle implies that the way a team is organized, the communication channels between team members, and the dynamics of collaboration will inevitably influence the design and architecture of the software they create. For instance, if a team is organized into separate functional silos, with limited communication between them, the resulting software might end up being composed of distinct modules that correspond to those silos, potentially leading to integration challenges and inefficiencies.
In the context of AI development, Conway's Law suggests that the organization of teams working on AI projects will impact the design and structure of the AI systems they produce. If teams are organized around specific AI techniques or technologies (e.g., natural language processing, computer vision), the resulting AI systems may reflect this organizational structure, potentially leading to disjointed or fragmented solutions. Conway's Law serves as a reminder that the social and organizational aspects of AI development are as crucial as the technical aspects, and paying attention to how teams are organized and how they communicate can ultimately impact the quality and effectiveness of the AI systems they produce.
ITIL - IT Service Management
Youtube search... ...Google search
- Wikipedia
- ITIL 4 | AXELOS
- ITIL 4 and artificial intelligence White Paper | Julie L. Mohr | AXELOS
- ITIL Process Map for ITIL 4 GbR | Stefan Kempter and Andrea Kempter
- Service Management Blog; The Complete Guide to ITIL 4 | BMC Blogs ... ITIL Best Practice e-Books & history of ITIL
- Spreadsheets:
ITIL is the most widely recognized framework for IT and digitally enabled services in the world. It provides comprehensive, practical and proven guidance for establishing an effective service management system. ITIL Homepage | AXELOS ...AXELOS is a joint venture company, created in 2013 by the Cabinet Office on behalf of Her Majesty’s Government (HMG) in the United Kingdom and Capita plc, to manage, develop and grow the Global Best Practice portfolio.
|
|
|
|
Capability Maturity Model Integration (CMMI)
Youtube search... ...Google search
- Wikipedia
- AI-Infused Project Management | CMMI Institute
- Introducing CMMI Development V2.0 | CMMI Institute
- CMMI Levels of Capability and Performance | CMMI Institute
For 25+ years, high-performing organizations have achieved clear, sustainable business results with ISACA®’s CMMI® maturity models. Originally created for the U.S. Department of Defense to assess the quality and capability of their software contractors, ISACA’s CMMI models have expanded beyond software engineering to help organizations around the world, in any industry, understand their current level of capability and performance and offer a guide to optimize business results. CMMI Institute
- Development
- Services
- Supply Chain
- People Management
|
|
National Association of State Chief Information Officers (NASCIO)
Youtube search... ...Google search
- NASCIO
- NASCIO's Cybersecurity Committee ...help state CIOs formulate high-level security and data protection policies and technical controls to secure the states' information systems and protect the personal and sensitive information within them.
- National Information Exchange Model (NIEM) | ...an XML-based information exchange framework based on a common vocabulary that enables efficient information exchange across diverse public and private organizations. NIEM Wikipedia
|
|
Tailoring
|
|
|
|