Benefits of a Standardised Modelling Method
Meet our speakers and download this presentation(and more) at http://www.realirm.com/about-us/speakers-forum
Reference Model for ISEB Certificates in Enterprise and Solution ArchitectureAryashree Pritikrishna
This document is a reference model that defines terms used in ISEB examinations for enterprise and solution architecture. It structures architecture concepts into foundation, intermediate, and practitioner levels. The reference model covers multiple architecture domains including business, data, applications, software, infrastructure, and architecture management. It provides definitions for key architecture terms and concepts to help examiners, examinees, and training providers.
This document discusses the information needs of knowledge workers and challenges in meeting those needs. It notes that knowledge workers spend 15-35% of their time searching for information, but are only successful 50% of the time. This results in lost productivity of 20-25%. It also discusses challenges like complicated access controls and understanding results from past similar cases. Opportunities mentioned include understanding information needs in a given domain and extracting relevant entities to drive semantic search tailored to the context of the case being worked on.
Bhadale group of companies cross- discipline engineering catalogueVijayananda Mohire
We offer planning, analysis, requirements management assistance for cross- engineering disciplines.We use Design Engineering guides from IET, INCOSE, CMMI,PMI, ISO standards and engineering codes ,HIPAA, SOX, GDPR, HFMEA HACCP and FMEA
Réussir son analyse fonctionnelle SharePointFranck Cornu
1. The document describes a methodology for conducting functional analysis for SharePoint applications from requirements definition to implementation.
2. It discusses defining requirements through user story mapping and prioritization techniques.
3. The functional analysis process involves 9 steps including visualizing requirements, defining data types and relationships, and determining data storage and access points.
Tangent International offers systems, technical, and enterprise architecture services across all disciplines including ERP systems, packaged applications, open source, and cloud-based solutions. They help organizations transition to private, hybrid, and public clouds as well as Platform as a Service (PaaS), Infrastructure as a Service (IaaS) and Software as a Service (SaaS) models. Their architectural services align technical architecture with business needs to ensure solutions are fit for purpose and cost effective while avoiding supplier and technology lock-in.
Software Architecture Reconstruction: Why What and HowMehdi Mirakhorli
Every system is a legacy system, the moment a programmer writes a line of code it becomes a legacy. Therefore in even relatively new systems similar to long lived systems, developers are faced with a body of code that they need to understand, and from which they need to extract architectural knowledge. Unfortunately, anecdotal evidence has shown that such knowledge tends to be tacit in nature, stored in the heads of people, and inconsistently scattered across various software artifacts and repositories. Furthermore, architectural knowledge vaporizes over time. Given the size, complexity, and longevity of many projects, developers therefore often lack a comprehensive knowledge of architectural design decisions and consequently make changes in the code that inadvertently degrade the underlying design and compromise its qualities.
This technical briefing will answer three fundamental questions about software architecture recovery: Why? What? and How? Through several examples it articulates and synthesizes technical forces and financial motivations that make software companies to invest in software architecture recovery. It discusses “what” are the pieces of design knowledge that can be recovered and lastly demonstrates a methodology as well as required tools for answering “how” to reconstruct architecture from implementation artifacts.
This document discusses social complexity and presents two simple agent-based models. It explains that social systems are complex due to cognitive individuals, downward causation between micro and macro levels, social embeddedness, and context-dependent behavior. Two simple models are described: one on homophily-driven altruism and one on ape dominance interactions. While simple, the models demonstrate emergent phenomena from micro-level rules and help explore social processes, but more complex and empirically-validated models are needed to truly understand social systems.
Using Evolution Patterns to Evolve Software ArchitecturesTom Mens
This presentation explains a theoretical approach and associated tool support to evolve software architecture descriptions expressed in an architectural description language.
Reference Model for ISEB Certificates in Enterprise and Solution ArchitectureAryashree Pritikrishna
This document is a reference model that defines terms used in ISEB examinations for enterprise and solution architecture. It structures architecture concepts into foundation, intermediate, and practitioner levels. The reference model covers multiple architecture domains including business, data, applications, software, infrastructure, and architecture management. It provides definitions for key architecture terms and concepts to help examiners, examinees, and training providers.
This document discusses the information needs of knowledge workers and challenges in meeting those needs. It notes that knowledge workers spend 15-35% of their time searching for information, but are only successful 50% of the time. This results in lost productivity of 20-25%. It also discusses challenges like complicated access controls and understanding results from past similar cases. Opportunities mentioned include understanding information needs in a given domain and extracting relevant entities to drive semantic search tailored to the context of the case being worked on.
Bhadale group of companies cross- discipline engineering catalogueVijayananda Mohire
We offer planning, analysis, requirements management assistance for cross- engineering disciplines.We use Design Engineering guides from IET, INCOSE, CMMI,PMI, ISO standards and engineering codes ,HIPAA, SOX, GDPR, HFMEA HACCP and FMEA
Réussir son analyse fonctionnelle SharePointFranck Cornu
1. The document describes a methodology for conducting functional analysis for SharePoint applications from requirements definition to implementation.
2. It discusses defining requirements through user story mapping and prioritization techniques.
3. The functional analysis process involves 9 steps including visualizing requirements, defining data types and relationships, and determining data storage and access points.
Tangent International offers systems, technical, and enterprise architecture services across all disciplines including ERP systems, packaged applications, open source, and cloud-based solutions. They help organizations transition to private, hybrid, and public clouds as well as Platform as a Service (PaaS), Infrastructure as a Service (IaaS) and Software as a Service (SaaS) models. Their architectural services align technical architecture with business needs to ensure solutions are fit for purpose and cost effective while avoiding supplier and technology lock-in.
Software Architecture Reconstruction: Why What and HowMehdi Mirakhorli
Every system is a legacy system, the moment a programmer writes a line of code it becomes a legacy. Therefore in even relatively new systems similar to long lived systems, developers are faced with a body of code that they need to understand, and from which they need to extract architectural knowledge. Unfortunately, anecdotal evidence has shown that such knowledge tends to be tacit in nature, stored in the heads of people, and inconsistently scattered across various software artifacts and repositories. Furthermore, architectural knowledge vaporizes over time. Given the size, complexity, and longevity of many projects, developers therefore often lack a comprehensive knowledge of architectural design decisions and consequently make changes in the code that inadvertently degrade the underlying design and compromise its qualities.
This technical briefing will answer three fundamental questions about software architecture recovery: Why? What? and How? Through several examples it articulates and synthesizes technical forces and financial motivations that make software companies to invest in software architecture recovery. It discusses “what” are the pieces of design knowledge that can be recovered and lastly demonstrates a methodology as well as required tools for answering “how” to reconstruct architecture from implementation artifacts.
This document discusses social complexity and presents two simple agent-based models. It explains that social systems are complex due to cognitive individuals, downward causation between micro and macro levels, social embeddedness, and context-dependent behavior. Two simple models are described: one on homophily-driven altruism and one on ape dominance interactions. While simple, the models demonstrate emergent phenomena from micro-level rules and help explore social processes, but more complex and empirically-validated models are needed to truly understand social systems.
Using Evolution Patterns to Evolve Software ArchitecturesTom Mens
This presentation explains a theoretical approach and associated tool support to evolve software architecture descriptions expressed in an architectural description language.
Sentence-to-Code Traceability Recovery with Domain OntologiesShinpei Hayashi
The document describes a technique for recovering traceability between natural language sentences and source code using domain ontologies. An automated tool was implemented and evaluated on a case study using the JDraw software. Results showed the technique worked well, recovering traceability between 7 sentences and code with higher accuracy than without using the ontology. The ontology helped improve recall and detect traceability in cases where word similarity alone did not work well. Future work is needed to evaluate on larger cases and domains.
The 4+1 view model provides a framework for documenting software architecture using multiple views. It addresses the different concerns of various stakeholders. The 4+1 view model includes logical, process, development, physical views plus a use case view. Each view is described from the perspective of different stakeholders and uses various UML diagrams. The views are interconnected and together provide a comprehensive architectural description of the system.
Stakeholders and Issues Management Approachessarahobaidee
This document summarizes key concepts around stakeholders, issues management, and crisis management. It defines stakeholders as individuals or groups affected by an organization's decisions. Stakeholder analysis involves understanding relationships between an organization and its constituents. Issues management is used to forecast potential issues and their impact. Crisis management involves four stages: pre-crisis, crisis occurs, lingering effects, and resolution. Managing stakeholders, issues, and potential crises is important for organizations to make ethical decisions and maintain positive relationships.
A Software Architect's View On Diagrammingmeghantaylor
Diagramming is an important tool to have in one’s repertoire but how can one go about learning to do it effectively? This presentation will shed some light on some use cases plus share some research.
Learn about different types of software diagrams, the different diagramming tools available, and Visio tips & tricks to make your diagrams pretty.
The document discusses software architecture documentation. It provides goals for architecture documentation, including presenting common views, defining stakeholders, identifying their concerns, and defining what and how to document. It also discusses the scope of the documentation. Finally, it discusses different approaches to software architecture documentation, including the Rational Unified Process (RUP) and Software Engineering Institute (SEI) methods. The document aims to provide guidance on effective software architecture documentation.
An introduction to fundamental architecture conceptswweinmeyer79
(Note: This is a very dated version of this popular deck, as SlideShare does not provide authors with a mechanism to update their documents. If interested in the latest version, feel free to message me on LinkedIn or at wweinmeyer@gmail.com. Also, feel free to ask SlideShare to bring back the ability to update posted documents.)
A discussion of the fundamentals you need to nail in your architecture practice:
- Architecture vs. Design
- Conceptual vs. Logical vs. Physical architecture
- Viewpoint Frameworks
- Architecture Domains
- Architecture Tiers
You are free to use/copy this information but if you do so, please include an acknowledgement
How to Write Amazing Functional Analysis Documents for your SharePoint Projects GSoft
The document provides an overview of a presentation on how to write functional analysis documents for SharePoint projects. It discusses defining requirements, prioritizing requirements, and a 9-step methodology for functional analysis when using SharePoint. The methodology includes steps like visualizing requirements, describing information types, defining relationships between data, determining data storage and flows, and defining data access points and behaviors. The presentation provides examples and tips for effectively analyzing requirements and functionality for SharePoint solutions.
This document discusses enterprise architecture, service-oriented architecture, and web services architecture. It begins with an outline that describes what will be covered, including definitions of the key terms and discussions of interoperability, the relationships between enterprise architecture, SOA, and web services, and references. It then provides more detailed explanations of enterprise architecture, including its role in governance and alignment with business goals. It also discusses service-oriented architecture and how it can help provide flexibility and integration. Finally, it briefly introduces web services architecture as a set of enabling technologies for implementing software systems based on SOA principles.
This document discusses key concepts in systems analysis and design including:
1. Defining a system and the roles of systems analysts and stakeholders.
2. Describing different types of information systems and the traditional systems development life cycle.
3. Emphasizing the importance of continuous planning, testing, documentation and using a case study approach in systems analysis and design.
The document discusses the role and structure of enterprise architecture. Enterprise architecture provides a conceptual blueprint that defines an organization's structure and operations, with the goal of helping an organization effectively achieve its current and future goals. It examines the current state, helps develop and evaluate designs, and creates a vision for the future. Popular enterprise architecture frameworks include the Zachman Framework and TOGAF, which provide standardized approaches to understanding an organization holistically.
The document discusses the design phase of the system development life cycle. It describes the objectives and steps of the design phase, which include presenting design alternatives, converting logical models to physical models, designing the system architecture, making hardware and software selections, and designing inputs, outputs, data storage, and programs. Common design strategies like custom development, packaged systems, and outsourcing are also covered. The document then explains various system design methods and the stages of system design, including logical, physical, and program design. Finally, it discusses avoiding common design mistakes.
This document contains a summary of Anusha Chitranshi's profile and career objective. She has over 9 years of experience in software development using technologies like .NET, C#, ASP.NET, SQL Server, and SharePoint. She is currently a Technical Lead at Wipro Technologies working on a knowledge management portal for a client. Prior experience includes projects for clients like ONGC and American Express involving development, testing, and support of SharePoint applications.
A set of slides used to support a discussion at the Center for Design Research at Stanford University. Trying to move Design Thinking to DT2.0 so that it is fit for the next phase of development. Time to move from just doing "empathy" to a more system wide approach now that the IIOT/IND4.0 is really here and we have people, equipment, devices and processes all working (or not) together.
This document provides 6 tips for enterprise architects:
1. Create a common requirements vision to define business priorities and IT requirements.
2. Thoroughly evaluate current business and IT environments, including application portfolios and software licensing.
3. Conduct a SWOT analysis to identify strengths, weaknesses, opportunities, and threats to improve IT.
4. Select the best enterprise architecture tools that meet minimum requirements and support a variety of needs.
5. Avoid data element bloat and redundancy by modeling data holistically and defining a data repository.
6. Architect for cloud computing as it will fundamentally change IT infrastructure and enable new business models.
The Enterprise Architecture Toolkit (EATK) is a solution accelerator that introduces new capabilities to simplify and consolidate enterprise architecture design. It leverages existing tools like Microsoft SharePoint, Office, and Visio by providing architecture templates, a portal, and processes. The EATK aims to enable transparency, create a proactive architecture process, and empower architects by surfacing relevant information through its architecture repository.
This is the first webcast in a four-part series in which we discuss the concepts of demand management in Microsoft Project Server 2010. In this webcast, we highlight the new Demand Management feature in Project Server 2010. Topics we cover include how demand management in Project Server 2010:
•Offers positive business impacts for multiple departments.
•Enhances strategic visibility into portfolios, programs, and projects across the enterprise.
•Benefits governance control processes by allowing for multiple lifecycle styles, creation of a central repository for project/program documents and data, and more streamlined capabilities for collecting project data.
Requirements engineering is the discipline that involves establishing and documenting requirements. The various activities associated with requirements engineering are elicitation, specification, analysis, verification and validation, and management.
The document discusses software architecture, including its definition, types of architectures, views, and documentation. It defines software architecture as the fundamental organization of a system, including its components, relationships, and design principles. The document outlines different types of architectures like business, technical, and enterprise architectures. It also discusses common architecture views used in frameworks like RUP, RM-ODP, and DODAF. Finally, it covers architecture documentation and modeling techniques.
The document discusses different techniques for building a Customer Data Hub (CDH), including registry, co-existence, and transactional techniques. It outlines the CDH build methodology, including data analysis, defining the data model and business logic, participation models, governance, and deliverables. An example enterprise customer data model is also shown using a hybrid-party model with relationships, hierarchies, and extended attributes.
This document provides a template for an architecture document that includes:
1. An introduction section describing the purpose, scope, definitions, and references.
2. A business architecture section describing the business context, processes, events, and impacts.
3. A functional architecture section describing the functional composition, most significant functions/use cases, and functional communication/interactions.
4. Additional sections for application architecture, software architecture requirements, technical architecture, deployment architecture, development strategy, data migration strategy, deployment strategy, configuration and version management strategy, security and conformance constraints, risks, and appendices.
(ONLINE) ITIL Indonesia Community - Sinergi ITSM dan Enterprise ArchitectureITIL Indonesia
The document discusses the synergy between IT service management (ITSM) and enterprise architecture (EA). It defines ITSM and EA, provides examples of EA visualizations, and discusses how EA can be used to support various ITSM processes like incident management, service catalog management, and capacity management. The presentation gives an example of how EA artifacts like the service landscape map can be synchronized with the ITSM configuration management database. It addresses common questions about the relationship between EA and ITIL and tools like the CMDB.
Sentence-to-Code Traceability Recovery with Domain OntologiesShinpei Hayashi
The document describes a technique for recovering traceability between natural language sentences and source code using domain ontologies. An automated tool was implemented and evaluated on a case study using the JDraw software. Results showed the technique worked well, recovering traceability between 7 sentences and code with higher accuracy than without using the ontology. The ontology helped improve recall and detect traceability in cases where word similarity alone did not work well. Future work is needed to evaluate on larger cases and domains.
The 4+1 view model provides a framework for documenting software architecture using multiple views. It addresses the different concerns of various stakeholders. The 4+1 view model includes logical, process, development, physical views plus a use case view. Each view is described from the perspective of different stakeholders and uses various UML diagrams. The views are interconnected and together provide a comprehensive architectural description of the system.
Stakeholders and Issues Management Approachessarahobaidee
This document summarizes key concepts around stakeholders, issues management, and crisis management. It defines stakeholders as individuals or groups affected by an organization's decisions. Stakeholder analysis involves understanding relationships between an organization and its constituents. Issues management is used to forecast potential issues and their impact. Crisis management involves four stages: pre-crisis, crisis occurs, lingering effects, and resolution. Managing stakeholders, issues, and potential crises is important for organizations to make ethical decisions and maintain positive relationships.
A Software Architect's View On Diagrammingmeghantaylor
Diagramming is an important tool to have in one’s repertoire but how can one go about learning to do it effectively? This presentation will shed some light on some use cases plus share some research.
Learn about different types of software diagrams, the different diagramming tools available, and Visio tips & tricks to make your diagrams pretty.
The document discusses software architecture documentation. It provides goals for architecture documentation, including presenting common views, defining stakeholders, identifying their concerns, and defining what and how to document. It also discusses the scope of the documentation. Finally, it discusses different approaches to software architecture documentation, including the Rational Unified Process (RUP) and Software Engineering Institute (SEI) methods. The document aims to provide guidance on effective software architecture documentation.
An introduction to fundamental architecture conceptswweinmeyer79
(Note: This is a very dated version of this popular deck, as SlideShare does not provide authors with a mechanism to update their documents. If interested in the latest version, feel free to message me on LinkedIn or at wweinmeyer@gmail.com. Also, feel free to ask SlideShare to bring back the ability to update posted documents.)
A discussion of the fundamentals you need to nail in your architecture practice:
- Architecture vs. Design
- Conceptual vs. Logical vs. Physical architecture
- Viewpoint Frameworks
- Architecture Domains
- Architecture Tiers
You are free to use/copy this information but if you do so, please include an acknowledgement
How to Write Amazing Functional Analysis Documents for your SharePoint Projects GSoft
The document provides an overview of a presentation on how to write functional analysis documents for SharePoint projects. It discusses defining requirements, prioritizing requirements, and a 9-step methodology for functional analysis when using SharePoint. The methodology includes steps like visualizing requirements, describing information types, defining relationships between data, determining data storage and flows, and defining data access points and behaviors. The presentation provides examples and tips for effectively analyzing requirements and functionality for SharePoint solutions.
This document discusses enterprise architecture, service-oriented architecture, and web services architecture. It begins with an outline that describes what will be covered, including definitions of the key terms and discussions of interoperability, the relationships between enterprise architecture, SOA, and web services, and references. It then provides more detailed explanations of enterprise architecture, including its role in governance and alignment with business goals. It also discusses service-oriented architecture and how it can help provide flexibility and integration. Finally, it briefly introduces web services architecture as a set of enabling technologies for implementing software systems based on SOA principles.
This document discusses key concepts in systems analysis and design including:
1. Defining a system and the roles of systems analysts and stakeholders.
2. Describing different types of information systems and the traditional systems development life cycle.
3. Emphasizing the importance of continuous planning, testing, documentation and using a case study approach in systems analysis and design.
The document discusses the role and structure of enterprise architecture. Enterprise architecture provides a conceptual blueprint that defines an organization's structure and operations, with the goal of helping an organization effectively achieve its current and future goals. It examines the current state, helps develop and evaluate designs, and creates a vision for the future. Popular enterprise architecture frameworks include the Zachman Framework and TOGAF, which provide standardized approaches to understanding an organization holistically.
The document discusses the design phase of the system development life cycle. It describes the objectives and steps of the design phase, which include presenting design alternatives, converting logical models to physical models, designing the system architecture, making hardware and software selections, and designing inputs, outputs, data storage, and programs. Common design strategies like custom development, packaged systems, and outsourcing are also covered. The document then explains various system design methods and the stages of system design, including logical, physical, and program design. Finally, it discusses avoiding common design mistakes.
This document contains a summary of Anusha Chitranshi's profile and career objective. She has over 9 years of experience in software development using technologies like .NET, C#, ASP.NET, SQL Server, and SharePoint. She is currently a Technical Lead at Wipro Technologies working on a knowledge management portal for a client. Prior experience includes projects for clients like ONGC and American Express involving development, testing, and support of SharePoint applications.
A set of slides used to support a discussion at the Center for Design Research at Stanford University. Trying to move Design Thinking to DT2.0 so that it is fit for the next phase of development. Time to move from just doing "empathy" to a more system wide approach now that the IIOT/IND4.0 is really here and we have people, equipment, devices and processes all working (or not) together.
This document provides 6 tips for enterprise architects:
1. Create a common requirements vision to define business priorities and IT requirements.
2. Thoroughly evaluate current business and IT environments, including application portfolios and software licensing.
3. Conduct a SWOT analysis to identify strengths, weaknesses, opportunities, and threats to improve IT.
4. Select the best enterprise architecture tools that meet minimum requirements and support a variety of needs.
5. Avoid data element bloat and redundancy by modeling data holistically and defining a data repository.
6. Architect for cloud computing as it will fundamentally change IT infrastructure and enable new business models.
The Enterprise Architecture Toolkit (EATK) is a solution accelerator that introduces new capabilities to simplify and consolidate enterprise architecture design. It leverages existing tools like Microsoft SharePoint, Office, and Visio by providing architecture templates, a portal, and processes. The EATK aims to enable transparency, create a proactive architecture process, and empower architects by surfacing relevant information through its architecture repository.
This is the first webcast in a four-part series in which we discuss the concepts of demand management in Microsoft Project Server 2010. In this webcast, we highlight the new Demand Management feature in Project Server 2010. Topics we cover include how demand management in Project Server 2010:
•Offers positive business impacts for multiple departments.
•Enhances strategic visibility into portfolios, programs, and projects across the enterprise.
•Benefits governance control processes by allowing for multiple lifecycle styles, creation of a central repository for project/program documents and data, and more streamlined capabilities for collecting project data.
Requirements engineering is the discipline that involves establishing and documenting requirements. The various activities associated with requirements engineering are elicitation, specification, analysis, verification and validation, and management.
The document discusses software architecture, including its definition, types of architectures, views, and documentation. It defines software architecture as the fundamental organization of a system, including its components, relationships, and design principles. The document outlines different types of architectures like business, technical, and enterprise architectures. It also discusses common architecture views used in frameworks like RUP, RM-ODP, and DODAF. Finally, it covers architecture documentation and modeling techniques.
The document discusses different techniques for building a Customer Data Hub (CDH), including registry, co-existence, and transactional techniques. It outlines the CDH build methodology, including data analysis, defining the data model and business logic, participation models, governance, and deliverables. An example enterprise customer data model is also shown using a hybrid-party model with relationships, hierarchies, and extended attributes.
This document provides a template for an architecture document that includes:
1. An introduction section describing the purpose, scope, definitions, and references.
2. A business architecture section describing the business context, processes, events, and impacts.
3. A functional architecture section describing the functional composition, most significant functions/use cases, and functional communication/interactions.
4. Additional sections for application architecture, software architecture requirements, technical architecture, deployment architecture, development strategy, data migration strategy, deployment strategy, configuration and version management strategy, security and conformance constraints, risks, and appendices.
(ONLINE) ITIL Indonesia Community - Sinergi ITSM dan Enterprise ArchitectureITIL Indonesia
The document discusses the synergy between IT service management (ITSM) and enterprise architecture (EA). It defines ITSM and EA, provides examples of EA visualizations, and discusses how EA can be used to support various ITSM processes like incident management, service catalog management, and capacity management. The presentation gives an example of how EA artifacts like the service landscape map can be synchronized with the ITSM configuration management database. It addresses common questions about the relationship between EA and ITIL and tools like the CMDB.
Imagine if designers conversed with you in a way that felt like object-oriented programming. Imagine if they handed off a design where, page after page, the objects you needed to code were edged in neon, so clearly defined they popped off the wireframe or comp. Imagine those objects were consistently presented; no one-off cases or guesswork required. Imagine you could take a design and almost create an ERD or rough out an API with it.
Well, good news. There’s no need to imagine it. It exists, and it’s called Object-Oriented UX (OOUX).
OOUX is a design methodology that helps us define usable, consistent products that naturally align with end users’ mental models. Similar to OOP, it asks us to define the objects in the real-world problem domain and design the information and relationships in each object before designing how the user might manipulate them. It's a powerful tool for any digital team, it's relatively easy to do, and it pays dividends fast.
Whether you are a developer, a designer, a content modeler, or someone who has influence over digital teams, OOUX offers a new and exciting option to add to your toolkit that will allow you to deliver better digital projects, quicker and more efficiently, and at a higher level of quality than ever before.
Presentation originally given at THAT Conference 2019
Enterprise Unified Process and rup methodologysaman zaker
The Enterprise Unified Process (EUP) extends the Rational Unified Process (RUP) to address the needs of large enterprises with multiple systems and development teams. It introduces two new phases - Production and Retirement. It also enhances RUP with seven new disciplines like Enterprise Business Modeling, Portfolio Management, and Enterprise Architecture that address enterprise-level concerns beyond software development. The EUP provides a comprehensive lifecycle approach for managing enterprise projects.
This document provides a summary of Abby Brown's technical experience including book reviews and editor roles, software patents submitted and issued, research projects and presentations conducted, and technical memberships. Key details include serving as technical editor for two books on Tibco software, submitting several patents around automated tools for services, metadata, and network alarms, presenting on topics such as cloud computing and SOA, and holding memberships in technical organizations like IEEE, The Open Group, and OASIS.
Phase 1 of systems planning involves identifying and selecting IS projects, and initiating and planning their development. This includes determining the feasibility of projects by evaluating their potential benefits and costs, both tangible and intangible. Cost-benefit analysis methods are used to analyze projects' economic feasibility and compare alternatives. The goal is to select projects that are strategically aligned and will help the organization achieve its objectives in a cost-effective manner.
The latest version of the TOGAF standard has special emphasis on Business Architecture, Digital Trends, and Business Transformation beyond IT. Stuart Macgregor takes us through some of these changes to the TOGAF® 9.2 standard and discuss how they will benefit us.
In this presentation Michael Payne debates the merits of placing Business Architecture within an organisation’s Business, IT or Enterprise Architecture departments. He examines some of the options available to organisations starting out with Business Architecture, and touches on Business Architecture engagement models. In addition, Michael provides a sneak peak into the new developments in the Open-BA Framework.
In this presentation Bruno Vandenborre, The Open Group accredited trainer at Real IRM, explores the purpose and utility of the new version of the ArchiMate standard. As well as a look at the updates and changes to the new version, he discusses the various responses and critiques to ArchiMate, and provide insight into how ArchiMate benefits the South African market.
An overview of The Open Group IT4IT Reference Architecture. It is a vendor and product-agnostic value chain-based operating model for managing the business of IT. While providing guidance on the design, procurement and implementation of the functionality needed to run IT, it also enables the systematic tracking of the state of IT services across the service life-cycle.
This presentation provides an overview of the Open Certified Architect (Open CA) and Open Certified IT Specialist (Open CITS) programmes from The Open Group. These globally recognised, vendor-neutral certification programmes require candidates to submit a portfolio of evidence that details their skills and experience. Suitable for a variety of IT professionals, the Open CA certification has IT Architecture, Enterprise Architecture and Business Architecture streams, and the Open CITS certification caters to IT specialists including Business Analysts, Developers, Testers, Security Specialists, Network Specialists and Service Support Specialists.
Follow our blog and download this presentation(and more) at http://www.realirm.com/blog
You can lead a horse to water… (Managing the Human Aspects of Change in EA Im...Real IRM
Many Enterprise Architecture (EA) implementations do not succeed in realising their full potential due to a failure in managing the “fuzzy” human aspects of organisational transformation. Change management is, or should be, an integral part of EA implementations. This presentation explores the role and composition of EA Change Management and examines how it differs from change leadership. It reviews John Kotter’s 8 steps for leading change and provides an overview of the process of managing human change in EA implementations and organisational transformations. The presentation also includes a consideration of the psychology of change - what psychological factors, change strategies and organisation conditions increase the individual’s motivation to change, and which merely exacerbate normal resistance to change?
Follow our blog and download this presentation(and more) at http://www.realirm.com/blog
Enterprise Architecture - The Linchpin between Corporate Governance & IT Gove...Real IRM
This document discusses the relationship between corporate governance, IT governance, and enterprise architecture. It provides an overview of frameworks like King III, COBIT 5, and TOGAF 9 and how they relate to each other. Enterprise architecture is positioned as the link between corporate governance and IT governance and how developing a strong enterprise architecture practice can provide competitive advantages for organizations.
A Mapping of Current Vendor Solutions to the EMMM Business Capability ModelReal IRM
This document discusses mapping vendor software solutions to a business capability model for the mining industry. It begins with an overview of application portfolio management in mining and the development of an application classification reference model to categorize the diverse set of applications used. A key focus is the Exploration, Mining, Metals and Minerals (EMMM) business capability model. The presentation aims to demonstrate how the application classification model can be mapped to the EMMM model to help analyze vendor solutions against core mining business capabilities.
Reference models a case study for healthcareReal IRM
This presentation is focused on the Healthcare Reference Framework which The Norwegian Healthcare Authority is sponsoring. Sarina looks at the Healthcare vision and business motivation driving the development and adoption of industry reference models and includes the business case for increased South African participation.
Meet our speakers and download this presentation(and more) at http://www.realirm.com/about-us/speakers-forum
Storytelling is an incredibly valuable tool to share data and information. To get the most impact from stories there are a number of key ingredients. These are based on science and human nature. Using these elements in a story you can deliver information impactfully, ensure action and drive change.
The Most Inspiring Entrepreneurs to Follow in 2024.pdfthesiliconleaders
In a world where the potential of youth innovation remains vastly untouched, there emerges a guiding light in the form of Norm Goldstein, the Founder and CEO of EduNetwork Partners. His dedication to this cause has earned him recognition as a Congressional Leadership Award recipient.
Brian Fitzsimmons on the Business Strategy and Content Flywheel of Barstool S...Neil Horowitz
On episode 272 of the Digital and Social Media Sports Podcast, Neil chatted with Brian Fitzsimmons, Director of Licensing and Business Development for Barstool Sports.
What follows is a collection of snippets from the podcast. To hear the full interview and more, check out the podcast on all podcast platforms and at www.dsmsports.net
The Steadfast and Reliable Bull: Taurus Zodiac Signmy Pandit
Explore the steadfast and reliable nature of the Taurus Zodiac Sign. Discover the personality traits, key dates, and horoscope insights that define the determined and practical Taurus, and learn how their grounded nature makes them the anchor of the zodiac.
The Genesis of BriansClub.cm Famous Dark WEb PlatformSabaaSudozai
BriansClub.cm, a famous platform on the dark web, has become one of the most infamous carding marketplaces, specializing in the sale of stolen credit card data.
The APCO Geopolitical Radar - Q3 2024 The Global Operating Environment for Bu...APCO
The Radar reflects input from APCO’s teams located around the world. It distils a host of interconnected events and trends into insights to inform operational and strategic decisions. Issues covered in this edition include:
Garments ERP Software in Bangladesh _ Pridesys IT Ltd.pdfPridesys IT Ltd.
Pridesys Garments ERP is one of the leading ERP solution provider, especially for Garments industries which is integrated with
different modules that cover all the aspects of your Garments Business. This solution supports multi-currency and multi-location
based operations. It aims at keeping track of all the activities including receiving an order from buyer, costing of order, resource
planning, procurement of raw materials, production management, inventory management, import-export process, order
reconciliation process etc. It’s also integrated with other modules of Pridesys ERP including finance, accounts, HR, supply-chain etc.
With this automated solution you can easily track your business activities and entire operations of your garments manufacturing
proces
Cover Story - China's Investment Leader - Dr. Alyce SUmsthrill
In World Expo 2010 Shanghai – the most visited Expo in the World History
https://www.britannica.com/event/Expo-Shanghai-2010
China’s official organizer of the Expo, CCPIT (China Council for the Promotion of International Trade https://en.ccpit.org/) has chosen Dr. Alyce Su as the Cover Person with Cover Story, in the Expo’s official magazine distributed throughout the Expo, showcasing China’s New Generation of Leaders to the World.
[To download this presentation, visit:
https://www.oeconsulting.com.sg/training-presentations]
This PowerPoint compilation offers a comprehensive overview of 20 leading innovation management frameworks and methodologies, selected for their broad applicability across various industries and organizational contexts. These frameworks are valuable resources for a wide range of users, including business professionals, educators, and consultants.
Each framework is presented with visually engaging diagrams and templates, ensuring the content is both informative and appealing. While this compilation is thorough, please note that the slides are intended as supplementary resources and may not be sufficient for standalone instructional purposes.
This compilation is ideal for anyone looking to enhance their understanding of innovation management and drive meaningful change within their organization. Whether you aim to improve product development processes, enhance customer experiences, or drive digital transformation, these frameworks offer valuable insights and tools to help you achieve your goals.
INCLUDED FRAMEWORKS/MODELS:
1. Stanford’s Design Thinking
2. IDEO’s Human-Centered Design
3. Strategyzer’s Business Model Innovation
4. Lean Startup Methodology
5. Agile Innovation Framework
6. Doblin’s Ten Types of Innovation
7. McKinsey’s Three Horizons of Growth
8. Customer Journey Map
9. Christensen’s Disruptive Innovation Theory
10. Blue Ocean Strategy
11. Strategyn’s Jobs-To-Be-Done (JTBD) Framework with Job Map
12. Design Sprint Framework
13. The Double Diamond
14. Lean Six Sigma DMAIC
15. TRIZ Problem-Solving Framework
16. Edward de Bono’s Six Thinking Hats
17. Stage-Gate Model
18. Toyota’s Six Steps of Kaizen
19. Microsoft’s Digital Transformation Framework
20. Design for Six Sigma (DFSS)
To download this presentation, visit:
https://www.oeconsulting.com.sg/training-presentations
Call8328958814 satta matka Kalyan result satta guessing➑➌➋➑➒➎➑➑➊➍
Satta Matka Kalyan Main Mumbai Fastest Results
Satta Matka ❋ Sattamatka ❋ New Mumbai Ratan Satta Matka ❋ Fast Matka ❋ Milan Market ❋ Kalyan Matka Results ❋ Satta Game ❋ Matka Game ❋ Satta Matka ❋ Kalyan Satta Matka ❋ Mumbai Main ❋ Online Matka Results ❋ Satta Matka Tips ❋ Milan Chart ❋ Satta Matka Boss❋ New Star Day ❋ Satta King ❋ Live Satta Matka Results ❋ Satta Matka Company ❋ Indian Matka ❋ Satta Matka 143❋ Kalyan Night Matka..
Zodiac Signs and Food Preferences_ What Your Sign Says About Your Tastemy Pandit
Know what your zodiac sign says about your taste in food! Explore how the 12 zodiac signs influence your culinary preferences with insights from MyPandit. Dive into astrology and flavors!
Best practices for project execution and deliveryCLIVE MINCHIN
A select set of project management best practices to keep your project on-track, on-cost and aligned to scope. Many firms have don't have the necessary skills, diligence, methods and oversight of their projects; this leads to slippage, higher costs and longer timeframes. Often firms have a history of projects that simply failed to move the needle. These best practices will help your firm avoid these pitfalls but they require fortitude to apply.
❼❷⓿❺❻❷❽❷❼❽ Dpboss Matka Result Satta Matka Guessing Satta Fix jodi Kalyan Final ank Satta Matka Dpbos Final ank Satta Matta Matka 143 Kalyan Matka Guessing Final Matka Final ank Today Matka 420 Satta Batta Satta 143 Kalyan Chart Main Bazar Chart vip Matka Guessing Dpboss 143 Guessing Kalyan night
IMPACT Silver is a pure silver zinc producer with over $260 million in revenue since 2008 and a large 100% owned 210km Mexico land package - 2024 catalysts includes new 14% grade zinc Plomosas mine and 20,000m of fully funded exploration drilling.
1. 12 August 2010 | ProcessForum 2010 | ‹#›
Stakeholder Driven EA
Johan Schoeman, Real IRM
12 August 2010
2. Get There Faster.
Benefits of a Standardised Modelling Method
• Common language & understanding
• Consistent information
• Object reuse
12 August 2010 | ProcessForum 2010 | ‹#›
3. Get There Faster.
Modelling Methods
Industry StandardsTool Specific Custom
12 August 2010 | ProcessForum 2010 | ‹#›
4. Get There Faster.
Modelling Methods Tend to be Extensive
• 123 Model types
• 231 Object types
• 461 Connection
types
• 42 Object types
• 148 Relationship
Types
How much of
this do I
need
12 August 2010 | ProcessForum 2010 | ‹#›
5. Get There Faster.
ANSI/IEEE Std 1471-2000
Mission
SystemEnvironment Architecture Rationale
Stakeholder
Concern Viewpoint View
Model
Library
Viewpoint
Architectural
Description
fulfills 1..*
inhabits
influences has an provides
described byhas1..*
participates in
aggregates
1..*
consists of 1..*
participates in 1..*
organised by
1..*
establishes methods for
has source 0..1
conforms to
selects
1..*
identifies
1..*
is important to
1..*
has 1..*
identifies
1..*
used to cover
1..*
is addressed to 1..*
12 August 2010 | ProcessForum 2010 | ‹#›
6. Get There Faster.
Stakeholder
ISO
An individual, team, or
organisation (or classes thereof)
with interests in, or concerns
relative to, the outcome of the
architecture. Different
stakeholders with different roles
will have different concerns.
Interpretation
Roles, teams or organisational
units who are involved in or
clients of Enterprise Architecture.
Mission
SystemEnvironment Architecture Rationale
Stakeholder
Concern Viewpoint View
Model
Library
Viewpoint
Architectural
Description
12 August 2010 | ProcessForum 2010 | ‹#›
7. Get There Faster.
Concern
ISO
Concerns are the key interests that
are crucially important to the
stakeholders in the system, and
determine the acceptability of the
system. May pertain to any aspect
of the system’s functioning,
development, or operation.
Interpretation
Key interests that are crucially
important to the stakeholders and
to be addressed by Enterprise
Architecture.
Mission
SystemEnvironment Architecture Rationale
Stakeholder
Concern Viewpoint View
Model
Library
Viewpoint
Architectural
Description
12 August 2010 | ProcessForum 2010 | ‹#›
8. Get There Faster.
Viewpoint
ISO
A specification of the conventions
for constructing and using a view. A
pattern or template from which to
develop individual views by
establishing the purposes and
audience for a view and the
techniques for its creation and
analysis.
Interpretation
A description of the views that
need to be delivered by Enterprise
Architecture in order to address
the stakeholder concerns.
Mission
SystemEnvironment Architecture Rationale
Stakeholder
Concern Viewpoint View
Model
Library
Viewpoint
Architectural
Description
12 August 2010 | ProcessForum 2010 | ‹#›
9. Get There Faster.
View
ISO
A representation of a whole system
from the perspective of a related
set of concerns.
Interpretation
An instance of a viewpoint
delivered by Enterprise
Architecture, addressing a specific
stakeholder’s concerns, e.g. a
generated Process Guide.
Mission
SystemEnvironment Architecture Rationale
Stakeholder
Concern Viewpoint View
Model
Library
Viewpoint
Architectural
Description
12 August 2010 | ProcessForum 2010 | ‹#›
10. Get There Faster.
Model
ISO
The models provide the specific
description, or content, or an
architecture.
Interpretation
The actual content of the
architecture repository, including
diagrams, matrices and catalogues.
Mission
SystemEnvironment Architecture Rationale
Stakeholder
Concern Viewpoint View
Model
Library
Viewpoint
Architectural
Description
12 August 2010 | ProcessForum 2010 | ‹#›
11. Get There Faster.
ANSI/IEEE Std 1471-2000 in Context
Mission
SystemEnvironment Architecture Rationale
Stakeholder
Concern Viewpoint View
Model
Architectural
Description
Architecture ContentMethod Design
Meta-model
12 August 2010 | ProcessForum 2010 | ‹#›
12. Get There Faster.
Conventional Data Capture
12 August 2010 | ProcessForum 2010 | ‹#›
Inv No Date Cust No Cust Name Cust Address Item No Item Desc Item Qty Item Price Item Total Total Price
123 2009/08/16 A12 ABC Pty Ltd 23 Market St, Johannesburg 563 A4 Exam Pads 4 R 7.56 R 30.24 R 85.83
592 Blue Pens 10 R 2.43 R 24.30 R 85.83
6423 Lever Arch Files 3 R 10.43 R 31.29 R 85.83
124 2009/08/17 B45 CDS CC 67 Church St, Pretoria 453 A4 Paper 5 R 23.65 R 118.25 R 914.25
821 Pins 10 R 4.00 R 40.00 R 914.25
563 A4 Exam Pads 100 R 7.56 R 756.00 R 914.25
Appears in order detail /
Has product
Plays role as /
Is instance of
Is sent to/billed to /
Receives product/invoice
Has details /
Belongs to order
Product
Product ID: String
Product Description: String
Unit Price: Number
Product Name: String
Order
Order Number: Num ber
Order Date: Datetim e
Invoice Date: Datetime
Tax Rate: Number
Order Detail
Line Number: Number
Product ID: String (FK)
Order Number: Num ber (FK)
Quantity: Number
Address
Address ID: Number
Address1: String
Address2: String
City: String
State: String
Zip: String
Order Address
Order Number: Num ber (FK)
Address ID: Number (FK)
Address Type Code: String
Source Data
Data Design - ERD Capturing Mechanism - Screen
13. Get There Faster.
Modelling Tool Data Capture
12 August 2010 | ProcessForum 2010 | ‹#›
Source Data
L0 Enterprise Process L1 Value Chain L2 Process L3 Sub-Process Responsible Accountable Supporting
Application
Develop and Manage
Human Capital
Develop and manage
human resources planning,
policies, and strategies
Develop human
resources strategy
Identify strategic HR needs HR Manager HR Director None
Define HR and business function roles and
accountability
HR Manager HR Director PeopleSoft
Develop and implement
human resources plans
Gather skill requirements according to
corporate strategy and market
environment
HR Coordinator HR Manager SAP HR,
PeopleSoft
L3 – Sub-process Model
L4 – Activity Model
L3 - Sub-process Detail Model
L4 - Activity Detail Model
Business Role Model
Data Design – Meta-model Capturing Mechanism - Model
14. Get There Faster.
Identify Users
Identify User
Requirements
Determine
Required
Functionality
Define Physical
System Design
Define Logical
System Design
Develop & Test
System
Deploy System
Update &
Maintain
System
SDLC Context
12 August 2010 | ProcessForum 2010 | ‹#›
Analysis
Logical
Design
Physical
Design
Implementat
ion
Deployment
Operations &
Maintenance
SDLC Phases Systems Development Process
Identify EA
Stakeholders
Identify
Stakeholder
Concerns
Define
Required
Viewpoints
Define EA
Meta-model
Define EA
Conceptual
Framework
Configure EA
Tool
Deploy Meta-
model
Update and
Maintain Meta-
model
Meta-model Development Process
15. Get There Faster.
Meta-model Definition Process
12 August 2010 | ProcessForum 2010 | ‹#›
Stakeholder
Concern
Viewpoint
View
Model
Meta-model
Identify EA
Stakeholders
Identify
Stakeholder
Concerns
Define
Required
Viewpoints
Define EA
Meta-model
EA Design
Architecture
Content
Define EA
Conceptual
Framework
Configure EA
Tool
16. Get There Faster.
Meta-model Definition Process
12 August 2010 | ProcessForum 2010 | ‹#›
Stakeholder
Concern
Viewpoint
View
Model
Meta-model
Identify EA
Stakeholders
Identify
Stakeholder
Concerns
Define
Required
Viewpoints
Define EA
Meta-model
EA Design
Architecture
Content
Define EA
Conceptual
Framework
Configure EA
Tool
17. Get There Faster.
TOGAF 9
TOGAF Chapter 24: Stakeholder Management
1. Step 1: Identify Stakeholders – Brainstorm all the stakeholders
2. Step 2: Classify Stakeholder Positions - Get an understanding of
the most important stakeholders
3. Step 3: Determine Stakeholder Management Approach – Work out
stakeholder power, influence and interest in order to focus EA on
the key individuals.
4. Step 4: Tailor Engagement Deliverables – Determine what will be
delivered to which stakeholders. (Part of next phases in our
process)
12 August 2010 | ProcessForum 2010 | ‹#›
19. Get There Faster.
Meta-model Definition Process
12 August 2010 | ProcessForum 2010 | ‹#›
Stakeholder
Concern
Viewpoint
View
Model
Meta-model
Identify EA
Stakeholders
Identify
Stakeholder
Concerns
Define
Required
Viewpoints
Define EA
Meta-model
EA Design
Architecture
Content
Define EA
Conceptual
Framework
Configure EA
Tool
20. Get There Faster.
Stakeholder Concerns
12 August 2010 | ProcessForum 2010 | ‹#›
Service Centre Manager
What are the business services which my
organisation provides?
Which organisations are consuming each of
my business services?
What are the end-to-end business processes
which enable my organisations business
services?
From which geographic locations are the
organisations consuming each of my
business services?
21. Get There Faster.
Meta-model Definition Process
12 August 2010 | ProcessForum 2010 | ‹#›
Stakeholder
Concern
Viewpoint
View
Model
Meta-model
Identify EA
Stakeholders
Identify
Stakeholder
Concerns
Define
Required
Viewpoints
Define EA
Meta-model
EA Design
Architecture
Content
Define EA
Conceptual
Framework
Configure EA
Tool
22. Get There Faster.
Viewpoint Types
A design or specification of a view that will help
stakeholders address their concerns
12 August 2010 | ProcessForum 2010 | ‹#›
Diagrams
PL.04.07
L4
Present Total
Budget To
Director Of
Mining
PL.04.09
L4
Prepare Budget
Presentation
For EXCO
PL.04.10
L4
Present
Total Budget
To EXCO
PL.04.11
L4
Determine
Element Of
Budget To
Be Adjusted
Labour Numbers
Or Cost Plan
Adjustment
Required
PL.04.05
L4
Consolidate
Costs For
Total Budget
No
Total Budget
Approved By
Director of Mining
PL.04.01
L4
Determine Costing
Methodology
Considering
CPI Parameters
Production Plan
Adjustment
Required
PL.04.02
L4
Cost Labour
Numbers As Per
Costing
Methodology
Total Budget
Not Approved By
Director of Mining
PL.04.03
L4
Verify
Labour Cost
On Mine
Labour Cost
Verified
On Mine
Labour Cost Not
Verified
On Mine
L3
Verify Annual
Or Five Year
Labour Plan
Yes No
L3
Produce Annual
Or Five Year
Labour Plan
Annual Or
Five Year
Labour Plan
Produced
PL.04.04
L4
Update Labour
Cost Plan
Based On
Verification Feedback
Planned Labour
Numbers Deviate
Unacceptably
From Actual
Labour Numbers
Planned
Labour Numbers
Deviate
From Predefined
Standards
Reason For
Benchmark
Deviation
Not Accepted
Annual Or
Five Year
Labour Plan
Approved
PL.04.13
L4
Notify
Relevant Parties
That Cost Plan
Captured
PL.04.08
L4
Adjust Applicable
Element Of
Total Budget
L3
Perform
Long Term
Production
Planning
PL.04.12
L4
Capture
Next Year
Cost Plan
Relevant Parties
Notified
That Cost Plan
Captured
Annual Or
Five Year
Labour Plan
Not Approved
Yes
Total Budget
Rejected By
Director of Mining
L3
Produce Annual
Or Five Year
Labour Plan
Total Budget
Rejected
By EXCO
L3
Produce Annual
Or Five Year
Labour Plan
Total Budget
Approved By
EXCO
Total Budget
Not Approved By
EXCO
PL.04.06
L4
Capture
Mine Approved
Labour Cost
Plan
Matrices Catalogues Reports
23. Get There Faster.
Viewpoints Addressing Concerns
12 August 2010 | ProcessForum 2010 | ‹#›
Service Centre Manager
From which geographic locations are the
organisations consuming each of my
business services?
24. Get There Faster.
Managing Requirement Scope
12 August 2010 | ProcessForum 2010 | ‹#›Importance
Urgency
Low Medium
LowMediumHigh
Hi
• Application Service
Delivery Model
• Application Service
Support Matrix
• Business Service
Application Delivery
Matrix
• Business Service
Application Delivery
Matrix
• Business Service
Delivery Model
• Business Service
Provider Matrix
• Application Service
Consumer Matrix
• Business Service
Business Object
CRUD Matrix
• Business Service
Consumer Model
• Hardware
Deployment Model
• Hardware
Component Location
Matrix
• Application Service
User Location Matrix
• Business Service
Events Matrix
• Business Service
Process Delivery
Matrix
• Event Trigger Matrix
Viewpoints
25. Get There Faster.
Meta-model Definition Process
12 August 2010 | ProcessForum 2010 | ‹#›
Stakeholder
Concern
Viewpoint
View
Model
Meta-model
Identify EA
Stakeholders
Identify
Stakeholder
Concerns
Define
Required
Viewpoints
Define EA
Meta-model
EA Design
Architecture
Content
Define EA
Conceptual
Framework
Configure EA
Tool
26. Get There Faster.
Conceptual Framework
12 August 2010 | ProcessForum 2010 | ‹#›
Location
Business
Service
Organisation
Process
Is located at consumes
performs
A logical design of the objects and relationship types
required in the meta-model to deliver the required
viewpoints
27. Get There Faster.
Meta-model Definition Process
12 August 2010 | ProcessForum 2010 | ‹#›
Stakeholder
Concern
Viewpoint
View
Model
Meta-model
Identify EA
Stakeholders
Identify
Stakeholder
Concerns
Define
Required
Viewpoints
Define EA
Meta-model
EA Design
Architecture
Content
Define EA
Conceptual
Framework
Configure EA
Tool
28. Get There Faster.
Meta-model
12 August 2010 | ProcessForum 2010 | ‹#›
To define the modelling standards and configure the
modelling tool to implement the relationships required by
the conceptual framework
29. Get There Faster.
Scoping for EA Modelling Initiatives
12 August 2010 | ProcessForum 2010 | ‹#›
Stakeholder
Concern
Viewpoint
Meta-model
Who are the interested stakeholders?
What are their particular concerns to be addressed?
What are the viewpoints required to address these concerns?
What are the models types that need to be captured to generate the viewpoints?
A direct mapping exists to answer the following questions: