The document discusses a roundtable on Solution Architecture training and CITA-A certification. It provides an overview of the training modules which cover topics like business technology strategy, solution architecture, lifecycles, success metrics, stakeholders, and describing solutions. The training aims to help participants understand the solution architect role and gain skills across software, infrastructure, information, and business domains. It also discusses how solution architects balance conflicting priorities and connect with other architects in an organization.
Practical Enterprise Architecture in Medium-size Corporation using TOGAFMichael Sukachev
Overview on the Practical Enterprise Architecture approach using TOGAF ADM for architectures development, Zachman Framework as artifacts repository and Sparx EA as a modelling tool.
Structured Approach to Solution ArchitectureAlan McSweeney
The role of solution architecture is to identify answer to a business problem and set of solution options and their components. There will be many potential solutions to a problem with varying degrees of suitability to the underlying business need. Solution options are derived from a combination of Solution Architecture Dimensions/Views which describe characteristics, features, qualities, requirements and Solution Design Factors, Limitations And Boundaries which delineate limitations. Use of structured approach can assist with solution design to create consistency. The TOGAF approach to enterprise architecture can be adapted to perform some of the analysis and design for elements of Solution Architecture Dimensions/Views.
Defining the business value proposition of EA and PPM
Eliminating project risks
Accelerating project execution
Managing project and architecture inter-dependencies
Delivering realized value
Improving collaboration of Architecture and PMO
Practical Enterprise Architecture in Medium-size Corporation using TOGAFMichael Sukachev
Overview on the Practical Enterprise Architecture approach using TOGAF ADM for architectures development, Zachman Framework as artifacts repository and Sparx EA as a modelling tool.
Structured Approach to Solution ArchitectureAlan McSweeney
The role of solution architecture is to identify answer to a business problem and set of solution options and their components. There will be many potential solutions to a problem with varying degrees of suitability to the underlying business need. Solution options are derived from a combination of Solution Architecture Dimensions/Views which describe characteristics, features, qualities, requirements and Solution Design Factors, Limitations And Boundaries which delineate limitations. Use of structured approach can assist with solution design to create consistency. The TOGAF approach to enterprise architecture can be adapted to perform some of the analysis and design for elements of Solution Architecture Dimensions/Views.
Defining the business value proposition of EA and PPM
Eliminating project risks
Accelerating project execution
Managing project and architecture inter-dependencies
Delivering realized value
Improving collaboration of Architecture and PMO
The TOGAF® Architecture Development Method recommends that "an architecture description be encoded in a standard language". As the Open Group standard for enterprise modeling, Archimate is a strong candidate for this role. This presentation will explore how a diversified financial services company selected and is using Archimate for its TOGAF® implementation. The speaker will compare available enterprise modeling languages and explain why Archimate was selected, and will explain how his organization developed an enabling metamodel and diagram templates using a leading enterprise modeling tool. Methodology transition will also be covered, including how existing diagram types were mapped to TOGAF®, and how TOGAF® diagram content was mapped to Archimate.
Delivered at February 2011 Open Group San Diego Conference
This examines the potential for the application of Design Science principles to the solution design process within solution architecture to improve the rigour and accuracy of solution designs.
Design Science is the structured and systematic process for creating designs that resolve problems. It is concerned with the structured process for the acquisition and application of knowledge in relation to the problems to the resolved and the solution knowledge to be applied.
The application of Design Science must be a means to an end – better solution quality – and not an end in itself – an incentive for the design function is to become large.
Solution architecture requires a (changing) combination of technical, leadership, interpersonal skills, experience, analysis, appropriate creativity, reflection and intuition applied in a structured manner.
Knowledge management – problem knowledge and solution knowledge – is at the core of the application of design science principles.
Knowledge management requires good management of the solution architecture function.
Digital Transformation And Solution ArchitectureAlan McSweeney
Digital strategy is a statement about the organisation’s digital positioning, competitors and customer and collaborator needs and behaviour to achieve a direction for innovation, communication, transaction and promotion. Digital strategy needs to be defined in the same framework structure as the proposed digital architecture platform.
Achieving the target digital organisation means deploying solutions that enable the digital architecture. Solution architecture needs to design solutions that fit into the target digital architecture framework. This requires:
• Solution architecture team operating in an integrated manner designing solutions to a set of common standards and that run on the platform
• Solution architecture team leadership ensuring solutions conform to the common standards
• Solution architecture technical leadership to develop and maintain common solution design standards
• Solution architecture updates the digital reference architecture based on solution design experience
Digital solution design requires greater discipline to create an integrated set solutions that operate within the rigour of the digital architecture framework. The solution architecture function must interact with other IT architecture disciplines to ensure the set of solutions that implement the digital framework operate together. This requires greater solution architecture team leadership. This needs to be supplemented and supported by a well-defined set of digital solution design standards.
This follows-on from the previous presentation: Digital Transformation And Enterprise Architecture
https://www.slideshare.net/alanmcsweeney/digital-transformation-and-enterprise-architecture.
Introduction to Enterprise architecture and the steps to perform an Enterpris...Prashanth Panduranga
This presentation was used to introduce Enterprise Architecture, Introduction to how to perform an Enterprise Architecture Assessment followed by TechSharp introduction.
Deliverables in the presentation is not clear, the slides represent what was shown as part of the demo.
List of deliverables:
Application Rationalization framework
Portfolio Analysis framework
Road Map
Current state analysis
Target State establishing process
System Context
System Landscape
Solution Architecture Centre Of ExcellenceAlan McSweeney
This is an extract from the book An Introduction to Solution Architecture (https://www.amazon.com/dp/1797567616) that discusses the topic of a Solution Architecture Centre Of Excellence.
The solution architecture function should aspire to be a Solution Architecture Centre Of Excellence (SACOE). This is concerned with developing a mature function that is highly-skilled at solution architecture and design and provides solution and consulting leadership to the organisation.
Developing an SACOE requires vision and resources of both the solution architecture function and information technology management.
The solution architecture function has the capability to develop both the business insight and solution and technology expertise to act as the business/technology authority and be the bridge between the business and technology domains of the organisation.
What is the Value of Mature Enterprise Architecture TOGAFxavblai
Judith Jones received the Open Group award for Outstanding Contributions to the development of TOGAF 9 at 19th Open Group Enterprise Architecture Practitioners Conference Chicago - July 21-23, 2008. Former CEO of Architecting the Enterprise which has been a member of The Open Group for 6 years, she is personnally involved since 1997. As an active member of The Open Group and she is a major contributor and an editor of TOGAF 7, 8 and 9 as well as leading TOGAF projects for localisation, case studies, ADML, synergy and collaboration projects.
http://www.opengroup.org/member/member-spotlight-jones.htm
It is well known that an effective PMO is key to successful and efficient program and project execution. In other words, doing things “right”. Enterprise Architecture is the discipline that plans and monitors enterprise transformation and aligns the business strategy with information technology capabilities. In other words, doing the “right things” to support the business.
Why is it organizations despite having both of these disciplines still struggle with effective enterprise transformation? What can we done to use these disciplines more effectively to effect better business outcomes? What are the roles of each discipline and how do they work together to create business value?
In this presentation, Riaz will address these questions and will provide real life examples that can help build a strong relationship between the PMO and Enterprise Architecture.
Learning Objectives:
• How to build a strong relationship between the PMO and Enterprise Architecture (EA) to deliver positive outcomes for your organization
• Identify the different roles and functions of the PMO and EA as well as their similarities
Modeling Big Data with the ArchiMate 3.0 LanguageIver Band
Health care enterprises use big data methods and technologies to gain insights for improving the efficacy, efficiency, and accessibility of their services. Effective big data initiatives require shared understanding among diverse stakeholders of business challenges and the often complex architectures required to address them. Enterprise and solution architects can use the ArchiMate language to build this understanding with compelling visual models.
This presentation introduces the ArchiMate 3.0 language, and uses it to explore the US National Institute of Standards and Technology (NIST) Big Data Reference Architecture (NBDRA), and to present a health care case study based on the NBDRA. Participants will learn how to use the ArchiMate 3.0 language, in alignment with the TOGAF framework, to propose, justify and plan big data initiatives, and to guide their successful implementation.
A Brief Introduction to Enterprise Architecture Daljit Banger
Presentation to Metropolitan University (London) on the 16th Feb 2017.
The purpose of the session was to introduce core basic concepts around Enterprise Architecture and discuss the role of the Enterprise Architect .
Incorporating A DesignOps Approach Into Solution ArchitectureAlan McSweeney
Solution architecture and design is concerned with designing new (IT) solutions to resolve problems or address opportunities . In order to solve a problem, you need sufficient information to understand the problem. If you do not understand the scope of the required solution you cannot understand the risks associated with the implementation approach.
Getting the solution wrong can be very expensive. The DesignOps approach is a unified end-to-end view of solution delivery from initial concept to steady state operations. It is a design-to-operations approach identifying all the solution design elements needed to ensure the delivery of a complete solution.
Solution architecture and design teams are becoming larger so more co-ordination, standardisation and management is required. The increasing focus on digital transformation increases the need for improved design as business applications are exposed outside the organisation. Solution complexity is increasing. The aim of the DesignOps approach is to improve solution design outcomes.
Integrated Project and Solution Delivery And Business Engagement ModelAlan McSweeney
Projects are a continuum from initial concept to planning, design, implementation and management and operation of the implemented solution (and ultimate decommissioning) and across IT and business functions.
Therefore it is important to have an integrated project delivery approach that crosses these core dimensions.
This describes an integrated approach to solution delivery encompassing Stages - project stages/timeline, Activities - IT and business functions/ roles/ activities, Gates - project review and decision gates and Artefacts - project results and deliverables. This combines project management into all other aspects and activities of project and solution delivery:
• Business
• Business Analysis
• Solution Architecture
• Implementation and Delivery
• Test and Quality
• Organisation Readiness
• Service Management
• Infrastructure
It emphasises early business engagement and solution definition and validation to detail a solution that meet a clear and articulated business need that will deliver a realisable and achievable set of business benefits. It ensures that the complexity of what has to be delivered is understood so there is a strong and solid foundation for solution implementation, delivery and management and operation.
Why IT needs more IT Architects (IASA style)Paddy Baxter
This is a deck I presented to IT leaders in the public sector. In it I explain the IASA definition of IT Architect and how in-house tech leaders can deliver substantially to their teams, IT and their whole organisation by focusing on the skills IASA defines as required for a high performing IT architect.
The TOGAF® Architecture Development Method recommends that "an architecture description be encoded in a standard language". As the Open Group standard for enterprise modeling, Archimate is a strong candidate for this role. This presentation will explore how a diversified financial services company selected and is using Archimate for its TOGAF® implementation. The speaker will compare available enterprise modeling languages and explain why Archimate was selected, and will explain how his organization developed an enabling metamodel and diagram templates using a leading enterprise modeling tool. Methodology transition will also be covered, including how existing diagram types were mapped to TOGAF®, and how TOGAF® diagram content was mapped to Archimate.
Delivered at February 2011 Open Group San Diego Conference
This examines the potential for the application of Design Science principles to the solution design process within solution architecture to improve the rigour and accuracy of solution designs.
Design Science is the structured and systematic process for creating designs that resolve problems. It is concerned with the structured process for the acquisition and application of knowledge in relation to the problems to the resolved and the solution knowledge to be applied.
The application of Design Science must be a means to an end – better solution quality – and not an end in itself – an incentive for the design function is to become large.
Solution architecture requires a (changing) combination of technical, leadership, interpersonal skills, experience, analysis, appropriate creativity, reflection and intuition applied in a structured manner.
Knowledge management – problem knowledge and solution knowledge – is at the core of the application of design science principles.
Knowledge management requires good management of the solution architecture function.
Digital Transformation And Solution ArchitectureAlan McSweeney
Digital strategy is a statement about the organisation’s digital positioning, competitors and customer and collaborator needs and behaviour to achieve a direction for innovation, communication, transaction and promotion. Digital strategy needs to be defined in the same framework structure as the proposed digital architecture platform.
Achieving the target digital organisation means deploying solutions that enable the digital architecture. Solution architecture needs to design solutions that fit into the target digital architecture framework. This requires:
• Solution architecture team operating in an integrated manner designing solutions to a set of common standards and that run on the platform
• Solution architecture team leadership ensuring solutions conform to the common standards
• Solution architecture technical leadership to develop and maintain common solution design standards
• Solution architecture updates the digital reference architecture based on solution design experience
Digital solution design requires greater discipline to create an integrated set solutions that operate within the rigour of the digital architecture framework. The solution architecture function must interact with other IT architecture disciplines to ensure the set of solutions that implement the digital framework operate together. This requires greater solution architecture team leadership. This needs to be supplemented and supported by a well-defined set of digital solution design standards.
This follows-on from the previous presentation: Digital Transformation And Enterprise Architecture
https://www.slideshare.net/alanmcsweeney/digital-transformation-and-enterprise-architecture.
Introduction to Enterprise architecture and the steps to perform an Enterpris...Prashanth Panduranga
This presentation was used to introduce Enterprise Architecture, Introduction to how to perform an Enterprise Architecture Assessment followed by TechSharp introduction.
Deliverables in the presentation is not clear, the slides represent what was shown as part of the demo.
List of deliverables:
Application Rationalization framework
Portfolio Analysis framework
Road Map
Current state analysis
Target State establishing process
System Context
System Landscape
Solution Architecture Centre Of ExcellenceAlan McSweeney
This is an extract from the book An Introduction to Solution Architecture (https://www.amazon.com/dp/1797567616) that discusses the topic of a Solution Architecture Centre Of Excellence.
The solution architecture function should aspire to be a Solution Architecture Centre Of Excellence (SACOE). This is concerned with developing a mature function that is highly-skilled at solution architecture and design and provides solution and consulting leadership to the organisation.
Developing an SACOE requires vision and resources of both the solution architecture function and information technology management.
The solution architecture function has the capability to develop both the business insight and solution and technology expertise to act as the business/technology authority and be the bridge between the business and technology domains of the organisation.
What is the Value of Mature Enterprise Architecture TOGAFxavblai
Judith Jones received the Open Group award for Outstanding Contributions to the development of TOGAF 9 at 19th Open Group Enterprise Architecture Practitioners Conference Chicago - July 21-23, 2008. Former CEO of Architecting the Enterprise which has been a member of The Open Group for 6 years, she is personnally involved since 1997. As an active member of The Open Group and she is a major contributor and an editor of TOGAF 7, 8 and 9 as well as leading TOGAF projects for localisation, case studies, ADML, synergy and collaboration projects.
http://www.opengroup.org/member/member-spotlight-jones.htm
It is well known that an effective PMO is key to successful and efficient program and project execution. In other words, doing things “right”. Enterprise Architecture is the discipline that plans and monitors enterprise transformation and aligns the business strategy with information technology capabilities. In other words, doing the “right things” to support the business.
Why is it organizations despite having both of these disciplines still struggle with effective enterprise transformation? What can we done to use these disciplines more effectively to effect better business outcomes? What are the roles of each discipline and how do they work together to create business value?
In this presentation, Riaz will address these questions and will provide real life examples that can help build a strong relationship between the PMO and Enterprise Architecture.
Learning Objectives:
• How to build a strong relationship between the PMO and Enterprise Architecture (EA) to deliver positive outcomes for your organization
• Identify the different roles and functions of the PMO and EA as well as their similarities
Modeling Big Data with the ArchiMate 3.0 LanguageIver Band
Health care enterprises use big data methods and technologies to gain insights for improving the efficacy, efficiency, and accessibility of their services. Effective big data initiatives require shared understanding among diverse stakeholders of business challenges and the often complex architectures required to address them. Enterprise and solution architects can use the ArchiMate language to build this understanding with compelling visual models.
This presentation introduces the ArchiMate 3.0 language, and uses it to explore the US National Institute of Standards and Technology (NIST) Big Data Reference Architecture (NBDRA), and to present a health care case study based on the NBDRA. Participants will learn how to use the ArchiMate 3.0 language, in alignment with the TOGAF framework, to propose, justify and plan big data initiatives, and to guide their successful implementation.
A Brief Introduction to Enterprise Architecture Daljit Banger
Presentation to Metropolitan University (London) on the 16th Feb 2017.
The purpose of the session was to introduce core basic concepts around Enterprise Architecture and discuss the role of the Enterprise Architect .
Incorporating A DesignOps Approach Into Solution ArchitectureAlan McSweeney
Solution architecture and design is concerned with designing new (IT) solutions to resolve problems or address opportunities . In order to solve a problem, you need sufficient information to understand the problem. If you do not understand the scope of the required solution you cannot understand the risks associated with the implementation approach.
Getting the solution wrong can be very expensive. The DesignOps approach is a unified end-to-end view of solution delivery from initial concept to steady state operations. It is a design-to-operations approach identifying all the solution design elements needed to ensure the delivery of a complete solution.
Solution architecture and design teams are becoming larger so more co-ordination, standardisation and management is required. The increasing focus on digital transformation increases the need for improved design as business applications are exposed outside the organisation. Solution complexity is increasing. The aim of the DesignOps approach is to improve solution design outcomes.
Integrated Project and Solution Delivery And Business Engagement ModelAlan McSweeney
Projects are a continuum from initial concept to planning, design, implementation and management and operation of the implemented solution (and ultimate decommissioning) and across IT and business functions.
Therefore it is important to have an integrated project delivery approach that crosses these core dimensions.
This describes an integrated approach to solution delivery encompassing Stages - project stages/timeline, Activities - IT and business functions/ roles/ activities, Gates - project review and decision gates and Artefacts - project results and deliverables. This combines project management into all other aspects and activities of project and solution delivery:
• Business
• Business Analysis
• Solution Architecture
• Implementation and Delivery
• Test and Quality
• Organisation Readiness
• Service Management
• Infrastructure
It emphasises early business engagement and solution definition and validation to detail a solution that meet a clear and articulated business need that will deliver a realisable and achievable set of business benefits. It ensures that the complexity of what has to be delivered is understood so there is a strong and solid foundation for solution implementation, delivery and management and operation.
Why IT needs more IT Architects (IASA style)Paddy Baxter
This is a deck I presented to IT leaders in the public sector. In it I explain the IASA definition of IT Architect and how in-house tech leaders can deliver substantially to their teams, IT and their whole organisation by focusing on the skills IASA defines as required for a high performing IT architect.
Title: The Role of the Software Architect
Speaker: Hayim Makabee, co-founder of the Israeli Chapter of the International Association of Software Architects (IASA)
Abstract:
In this talk Hayim will present the practical aspects of the role of the Software Architect, including:
- The four areas of expertise: Design, Domain, Technology and Methodology.
- The cooperation with stakeholders: Developers, Team Leaders, Project Managers, QA and Technical Writers.
Understanding the expected areas of expertise is essential for the architect to develop his/her professional skills.
Understanding how to cooperate with the diverse stakeholders is essential to improve the architect's impact and effectiveness.
A Top 10 Key to Success for Architects, delivered by author Pete Eeles, IBM, hosted on the "Good Design is Good Business" group on developerWorks: https://www.ibm.com/developerworks/mydeveloperworks/blogs/669242b1-dd91-4d63-a08f-231314c793bb/entry/top_10_success_secrets_for_software_architects_good_design_is_good_business_series?lang=en
Are You an Accidental or Intention Software ArchitectRandy Ynchausti
This presentation challenges viewers to consider what knowledge body and skills base a professional software architect possesses. It was presented originally at the UT IASA Chapter meeting November 21, 2013.
IASA 2014 Conference - Cape Town, South Africa #iasa2014Karen Du Toit
Report back about attending the most recent International Association of Sound and Audiovisual Association Conference in Cape Town from 5 - 9 October 2014
Only possible to mention but a few of the papers that were read.
Information about the conference can be found here: http://2014.iasa-web.org/
Iasa Architect responsibilities in the cloudiasaglobal
Cloud platforms drive marketing campaigns that offer to simplify the hardest challenges of information technology. From resilience to scalability, disaster recovery to management, the cloud platforms offer to take the challenge off of the table forever! It can be easy to ?buy in? to the platform. Too often, we find out later that our responsibility as architects cannot ?end at the door? to the provider, that there are provisos and implementation considerations we discover ? often after the provider falls down.
This lecture describes the Platform model or Two-sided Markets. Platforms serve multiple customer groups and benefit from network effects that take place with and between those groups. Businesses based on Platforms are able to adopt innovative pricing structures in which one side subsidizes another. When the marginal costs are near zero it can be practical to drop the subsidized price all the way to zero.
Architecting the Enterprise (in a SAFe Context)Mikkel Brahm
Walk-through of a Way of Working with Enterprise Architecture in a SAFe context in a larger Bank. What is EA, How to Steer, How to Govern, How to Lead, and how to wrestle with an emerging Future.
EAC2013 presentation: A Cookbook for Smart EA PracticesRik Farenhorst
Despite the maturation of the discipline, in many organizations Enterprise Architecture is not applied very effectively, mostly because using structured methods and frameworks is preferred over communicating business value and smart planning of IT investments. The various EA frameworks (e.g., TOGAF) that have been proposed over the past years definitely have their merit, but they also seem to seduce architects to focus on blueprints, elaborate process definitions and ivory towers. Architects simply need to work smarter to be of added value. Based on experience in numerous EA projects and EA trainings delivered in the Netherlands, in this presentation a cookbook for smart EA practices is proposed. The cookbook, which is inspired by success stories from the trenches, adopts and adapts elements from contemporary EA frameworks and other methods, (e.g., stakeholder management, architecture visualizations, business model canvas), and as such provides a step-by-step guide for building or professionalizing an EA function.
Presentation on growing architects presented at the Australian Architecture Forum 2009. This is a further developed concept from the similar SAF presentation.
Design Architecture Review Board (ARB) to Enable Digital Strategy Mohan K.
Architecture Review Board (ARB) to Enable Digital Strategy Execution - *Based on case study of establishing Architecture Review Board (ARB) at a multinational manufacturing
Are You an Accidental or Intentional Architect?iasaglobal
The first step in preparing for capability on demand is to set up for capacity on demand, but this can only occur after a CIO gets the IT house in order operationally. An IT organization that cannot manage operations effectively because it lacks understanding of costs relating to business performance and outcomes will have trouble evaluating the price-for-performance trade-offs offered by external suppliers.
Practical Enterprise Architecture - Introducing CSVLOD EA ModelAshraf Fouad
Introduction to Enterprise Architecture in a simpler, modernized, & realistic model (CSVLOD).
Target Audience:
1- Tech Leaders New to Enterprise Architecture.
2- Enterprise Architects.
3- CIO, CTO, CDO, EPMO, ITPMO.
Prezentacja autorstwa Aleksandra Wyki przedstawiona na I Panelu BizDevOps. Omawia:
- Business Architecture - jak Business Capabilities, Value Streams, Business Model I Operating Model mogą wspomóc wdrażanie koncepcji BizDevOps
- Agile Architecture a koncepcja BizDevOps
Max Poliashenko - Enterprise Product Architectureiasaglobal
Enterprise Product Architecture(EPA) is a new kid on the block that hasn't been established as well nor even well understood by industry analysts, yet it may be crucial for software product companies. EPA combines methods and governance models of EA however directed at customer facing solution or software products which gives it a distinctly different set of concerns and techniques.
Michael Gonzalez - Do The Sum of The Parts Equal the Wholeiasaglobal
If we're going to say this is "Enterprise Architecture" then why not approach it from an "Enterprise" perspective? Meaning, is it possible to have enterprise business, information, and technical architecture disciplines, all reporting to various stakeholders, effectively partner to yield true enterprise transformation? This presentation explores some of the challenges and opportunities operating EA as a matrixed team to include best practices and lessons learned.
Michael Jay Freer - Information Obfuscationiasaglobal
In this session, Michael Jay Freer will explore defining a common data-masking language, defining standard masking business-rules, defining best practices for manipulating the data, and how to get started without attempting to "Boil-the-ocean."
Creating Enterprise Value from Business Architectureiasaglobal
This presentation will cover the Why (Value) and How (Execution) of a Business Architecture program. You will understand how you can lead your enterprise towards its vision by planning for key Business Capabilities that will get you there.
Scott Whitmire - Just What is Architecture Anywayiasaglobal
An understanding of the fundamentals of architecture: What it is, what it comprises, and how it comes about, are crucial to further developing our practice.
Sean Kenney - Solving Parallel Software Challenges with Patternsiasaglobal
Sean will talk about the various parallel patterns and specifically how they can be used to solve specific parallel design challenges. This session will focus on 6 patterns that attendees will need to understand in order to architect and develop software that leverages parallel programming.
Stephen Cohen - The Impact of Ethics on the Architectiasaglobal
This session will place the Architect as leader, decision maker, risk manager, and agent of change in a context of professionalism and responsibility. We will explore many of the choices and actions Architects take on that are, or should be, guided by more than simple fiscal value creation but clarity of purpose in support of multiple cultures and needs.
This presentation will explain the idea, pros and cons of the Evolution Game. It will also compare it against the usual strategies. Lastly, it will show all tactics that need to be applied in order to involve stakeholders and evaluate the actual architecture sanity, particularly how to measure "evolvability".
Nina Grantcharova - Approach to Separation of Concerns via Design Patternsiasaglobal
Separation of Concerns aims at managing complexity by establishing a well-organized system where each part adheres to a single and unique purpose while maximizing the system's ability to adapt to change and increasing developers' productivity. The goal of this presentation is to promote the understanding of the principle of Separation of Concerns and to provide a selected set of foundational patterns to aid software architects in the designing of maintainable and extensible systems.
Roger Sessions - The Snowman Architectureiasaglobal
It is time for a Radical Transformation of IT. IT projects must be smaller, cheaper, and better aligned with the needs of the business. Simplicity must be a key design feature of every IT project. Projects must be delivered in months, not years. And in this new vision of a transformed IT, it is not IT's responsibility to tell the business what it can do, it is the business's responsibility to tell IT what it must do. Enterprise Architecture can be at the forefront of this vision, but only if it is revamped so that its purpose is no longer delivering useless paperwork, but facilitating high value IT projects. This transformation starts with a Snowman.
GraphRAG is All You need? LLM & Knowledge GraphGuy Korland
Guy Korland, CEO and Co-founder of FalkorDB, will review two articles on the integration of language models with knowledge graphs.
1. Unifying Large Language Models and Knowledge Graphs: A Roadmap.
https://arxiv.org/abs/2306.08302
2. Microsoft Research's GraphRAG paper and a review paper on various uses of knowledge graphs:
https://www.microsoft.com/en-us/research/blog/graphrag-unlocking-llm-discovery-on-narrative-private-data/
UiPath Test Automation using UiPath Test Suite series, part 3DianaGray10
Welcome to UiPath Test Automation using UiPath Test Suite series part 3. In this session, we will cover desktop automation along with UI automation.
Topics covered:
UI automation Introduction,
UI automation Sample
Desktop automation flow
Pradeep Chinnala, Senior Consultant Automation Developer @WonderBotz and UiPath MVP
Deepak Rai, Automation Practice Lead, Boundaryless Group and UiPath MVP
DevOps and Testing slides at DASA ConnectKari Kakkonen
My and Rik Marselis slides at 30.5.2024 DASA Connect conference. We discuss about what is testing, then what is agile testing and finally what is Testing in DevOps. Finally we had lovely workshop with the participants trying to find out different ways to think about quality and testing in different parts of the DevOps infinity loop.
Transcript: Selling digital books in 2024: Insights from industry leaders - T...BookNet Canada
The publishing industry has been selling digital audiobooks and ebooks for over a decade and has found its groove. What’s changed? What has stayed the same? Where do we go from here? Join a group of leading sales peers from across the industry for a conversation about the lessons learned since the popularization of digital books, best practices, digital book supply chain management, and more.
Link to video recording: https://bnctechforum.ca/sessions/selling-digital-books-in-2024-insights-from-industry-leaders/
Presented by BookNet Canada on May 28, 2024, with support from the Department of Canadian Heritage.
Kubernetes & AI - Beauty and the Beast !?! @KCD Istanbul 2024Tobias Schneck
As AI technology is pushing into IT I was wondering myself, as an “infrastructure container kubernetes guy”, how get this fancy AI technology get managed from an infrastructure operational view? Is it possible to apply our lovely cloud native principals as well? What benefit’s both technologies could bring to each other?
Let me take this questions and provide you a short journey through existing deployment models and use cases for AI software. On practical examples, we discuss what cloud/on-premise strategy we may need for applying it to our own infrastructure to get it to work from an enterprise perspective. I want to give an overview about infrastructure requirements and technologies, what could be beneficial or limiting your AI use cases in an enterprise environment. An interactive Demo will give you some insides, what approaches I got already working for real.
Essentials of Automations: Optimizing FME Workflows with ParametersSafe Software
Are you looking to streamline your workflows and boost your projects’ efficiency? Do you find yourself searching for ways to add flexibility and control over your FME workflows? If so, you’re in the right place.
Join us for an insightful dive into the world of FME parameters, a critical element in optimizing workflow efficiency. This webinar marks the beginning of our three-part “Essentials of Automation” series. This first webinar is designed to equip you with the knowledge and skills to utilize parameters effectively: enhancing the flexibility, maintainability, and user control of your FME projects.
Here’s what you’ll gain:
- Essentials of FME Parameters: Understand the pivotal role of parameters, including Reader/Writer, Transformer, User, and FME Flow categories. Discover how they are the key to unlocking automation and optimization within your workflows.
- Practical Applications in FME Form: Delve into key user parameter types including choice, connections, and file URLs. Allow users to control how a workflow runs, making your workflows more reusable. Learn to import values and deliver the best user experience for your workflows while enhancing accuracy.
- Optimization Strategies in FME Flow: Explore the creation and strategic deployment of parameters in FME Flow, including the use of deployment and geometry parameters, to maximize workflow efficiency.
- Pro Tips for Success: Gain insights on parameterizing connections and leveraging new features like Conditional Visibility for clarity and simplicity.
We’ll wrap up with a glimpse into future webinars, followed by a Q&A session to address your specific questions surrounding this topic.
Don’t miss this opportunity to elevate your FME expertise and drive your projects to new heights of efficiency.
Slack (or Teams) Automation for Bonterra Impact Management (fka Social Soluti...Jeffrey Haguewood
Sidekick Solutions uses Bonterra Impact Management (fka Social Solutions Apricot) and automation solutions to integrate data for business workflows.
We believe integration and automation are essential to user experience and the promise of efficient work through technology. Automation is the critical ingredient to realizing that full vision. We develop integration products and services for Bonterra Case Management software to support the deployment of automations for a variety of use cases.
This video focuses on the notifications, alerts, and approval requests using Slack for Bonterra Impact Management. The solutions covered in this webinar can also be deployed for Microsoft Teams.
Interested in deploying notification automations for Bonterra Impact Management? Contact us at sales@sidekicksolutionsllc.com to discuss next steps.
Accelerate your Kubernetes clusters with Varnish CachingThijs Feryn
A presentation about the usage and availability of Varnish on Kubernetes. This talk explores the capabilities of Varnish caching and shows how to use the Varnish Helm chart to deploy it to Kubernetes.
This presentation was delivered at K8SUG Singapore. See https://feryn.eu/presentations/accelerate-your-kubernetes-clusters-with-varnish-caching-k8sug-singapore-28-2024 for more details.
Search and Society: Reimagining Information Access for Radical FuturesBhaskar Mitra
The field of Information retrieval (IR) is currently undergoing a transformative shift, at least partly due to the emerging applications of generative AI to information access. In this talk, we will deliberate on the sociotechnical implications of generative AI for information access. We will argue that there is both a critical necessity and an exciting opportunity for the IR community to re-center our research agendas on societal needs while dismantling the artificial separation between the work on fairness, accountability, transparency, and ethics in IR and the rest of IR research. Instead of adopting a reactionary strategy of trying to mitigate potential social harms from emerging technologies, the community should aim to proactively set the research agenda for the kinds of systems we should build inspired by diverse explicitly stated sociotechnical imaginaries. The sociotechnical imaginaries that underpin the design and development of information access technologies needs to be explicitly articulated, and we need to develop theories of change in context of these diverse perspectives. Our guiding future imaginaries must be informed by other academic fields, such as democratic theory and critical theory, and should be co-developed with social science scholars, legal scholars, civil rights and social justice activists, and artists, among others.
Neuro-symbolic is not enough, we need neuro-*semantic*Frank van Harmelen
Neuro-symbolic (NeSy) AI is on the rise. However, simply machine learning on just any symbolic structure is not sufficient to really harvest the gains of NeSy. These will only be gained when the symbolic structures have an actual semantics. I give an operational definition of semantics as “predictable inference”.
All of this illustrated with link prediction over knowledge graphs, but the argument is general.
Connector Corner: Automate dynamic content and events by pushing a buttonDianaGray10
Here is something new! In our next Connector Corner webinar, we will demonstrate how you can use a single workflow to:
Create a campaign using Mailchimp with merge tags/fields
Send an interactive Slack channel message (using buttons)
Have the message received by managers and peers along with a test email for review
But there’s more:
In a second workflow supporting the same use case, you’ll see:
Your campaign sent to target colleagues for approval
If the “Approve” button is clicked, a Jira/Zendesk ticket is created for the marketing design team
But—if the “Reject” button is pushed, colleagues will be alerted via Slack message
Join us to learn more about this new, human-in-the-loop capability, brought to you by Integration Service connectors.
And...
Speakers:
Akshay Agnihotri, Product Manager
Charlie Greenberg, Host
Smart TV Buyer Insights Survey 2024 by 91mobiles.pdf91mobiles
91mobiles recently conducted a Smart TV Buyer Insights Survey in which we asked over 3,000 respondents about the TV they own, aspects they look at on a new TV, and their TV buying preferences.
2. Roundtable Purpose
Get a sense if the Solution Architecture
Training and CITA-A Certification
would be valuable for you
professionally and for what you do at
your company
3. Approach
Start with context: Solution Architect role and CITA-A certification
50,000 foot view of key modules: highlights according to Don and Rakesh
Business technology strategy
Solution architecture
Lifecycle
Success metrics
Stakeholders
Describing the solution
Deeper dive into Solution architecture module
Finish with review of module's workshop to provoke thoughts
Basing on our personal assessments of value--inviting discussion: what
resonates? do you see it differently? gaining any insights?
4.
5.
6. Module 0 - Business Technology
Strategy
Compares traditional IT Architecture purpose, to enable business
units through technology, to higher calling: use technology to
transform business
Ford Sync, Garmin and digital maps, MRI scanner, Avis pay-at-return
Shows Business architecture model examples such as Strategy
Map, Balanced Scorecard, Roadmaps
Compares Business Technology Strategy to Business Architecture
BTS is lifecycle for managing change , understanding the businsee, and
elevates financial and value arguments reltive to technical one
BTS is common techniquest, BA is form role and accountability for tasks
Compares life cycles of C-Suite, EA, and Projects
7. Module 1 - Solution Architecture
Compares Solution Architect to Software Architect
Solution Architect: skill necessary to deliver end to end solution with
general skills in all four specialization areas
Software Architect: specialist role with depth of skills and experience
in software intensive systems
Describes two "tracks" of Solution Architecture: specialist and
end-to-end or generalist
Summarizes differences between Solution Architect Generalist
and Enterprise Architect
Level of depth to go into when creating strategy for all four areas
Workshop had us create a Solution Architect job description to
support staffing up the architecture department for the fictitious
company
8. Module 2 - Lifecycle
Includes review of industry architecture lifecycles such as
FEAF, Togaf, COBIT and others such as Gated, Agile, Iasa
Solution Lifecycle
Workshop was to create an architecture lifecycle to meet
circumstances of fictional business - similar to task in front of
Don
9. Module 3 - Success Metrics
All about defining value in business terms and relating
architecture work to increasing business value
Architecture value measures are more than participating in projects
that are on-time, within budget, meeting requirements
Describes models like Balanced Scorecard, Business Model
Canvas and others.
Workshop had the class create a Business Model Canvas for
fictitious company
Good for "reverse engineering" business objectives allowing better
linkage of architecture strategies, models, and other deliverables to
business-recognized value
10. Module 4 - Stakeholders
Covers human dynamics aspects of being an Architect
Communicating, influencing, motivating, working with stakeholders with different
backgrounds
Great slide on different motivations of stakeholders and how to address
them at different levels to move a meeting along
Workshop was to create and deliver presentation to executives
persuading them to endorse important architectural objectives for the
fictitious company
11. Module 5 - Describing the Solution
Addresses viewpoints and perspectives and industry
approaches to describing them such as 4+1, Archimate, Woods
and Rozanski, etc.
Workshop was to create a "Viewpoint Library"--very much on
topic for Don
12. What Iasa Says About Solution Architecture Is
The art and science of designing and
delivering a technology strategy against
a measured set of goals and objectives
through a time-constrained set of
activities.
13. Solution Architects Balance Conflicting Forces
Enterprise
• Standards and Constraints
• Strategic Goals
• Target State
Technology
Value
• Increased
ROI
• Constituent
Value
• Market
Opportunities
Project
• Timeline
• Budget
• Team (stakeholders)
Stakeholder
• Requirement
s
• Org
Dynamics
• Conflicting
Goals
Balanced
Solution
14. Solution Architects Work Across Four Domains
Software
• Applications
• Quality Attributes
• Technology Framework
• Maintenance
Infrastructure
• Hardware
• Network
• Frameworks
• Operations
Information
• Data Storage Retrieval
• Information Usage
• Integration
Business
• Goals
• Target State
• Business
Value
15. What Solution Architects Do
• Select and recommend high-value generation approaches for
technology investment
• Generate documents representing the target state value from
technology and functionality of a particular solution
• Review design and architecture documents from extended
team members
• Represent the benefits and costs of chosen technical
direction with stakeholders
• Ensure the ongoing delivery against target state architecture
through build and run phases
• Evaluate the effectiveness of delivered solutions against
planned value
• Communicate value generation throughout the business
environment
• Ensure compliance with internal and external standards and
regulations
16. Solution Architects Perform Different Activities at Each
Scoped Level in the Organization
Select Projects
• Create/Review business case
• Calculate and communicate
value
• Prioritize and select
• Assign architects
Create Architecture(s)
• Capture and analyze
requirements
• Architecture master
•Generic architecture
• Product specific architecture
• Architecture Prototype
• Views/viewpoints
Deliver Architecture(s)
• Stakeholder communication
•Modify and update artifacts
• Delivery
Higher Level
Manage Architecture
• Review and analyze value
• Set architecture goals
• Update Engagement Model
•Communicate value
Project Level
17. How they’re connected with other Architects in the Organization
Finance Sales LOB IT
Business Capability
Data Center
Solution Architects
Software
Architect
Software
Architect
All architects
are included
Specialists
cover
appropriate
areas
Value “rolls up”
Value is clear
to customer
Credit is given
appropriately
Career growth
supported
Business
Architects
Information
Architects
Infrastructure
Architects
Enterprise
Architects
18. Their Project Coverage: Scope of Engagement
Finance Sales LOB IT
Business Capability
Data Center
Solution Architects
Software
Architect
Software
Architect
Business
Architects
Information
Architects
Infrastructure
Architects
Enterprise
Architects
3-5 Projects
Single Project
All Projects
Both Single and Multiple
Both Single and Multiple
19. Why You Should Care – As Is
Set
Goals
Measure
C-Suite
Execute Fund
Portfolio
Mgmt.
Plan EAs
Governance
Asset Mgmt.
Milestone
Review
Measure
Project
Architects
Deliver Design
Project
Architects
Project
Architects
Project
Architects
Project
Architects
20. Why You Should Care – To Be
Set
Goals
Measure
C-Suite
Portfolio
Mgmt.
Asset Mgmt.
EAs
Milestone Governance
Review
Execute Fund
Plan
Design
Project
Architects
Measure
Deliver
Design
Project
Architects
Project
Architects
Project
Architects
Plan
Measure
Project
Teams
Deliver Design
Plan
Measure
Project
Teams
Measure
Deliver Design
Plan
Project
Teams
Deliver Design
Plan
Measure
Project
Teams
Deliver Design
Plan
Measure
Project
Teams
Deliver Design
21.
22.
23.
24.
25. Takeaways
Are you a complete Solution Architect? Do you want to be?
Which type?
Multiple paths to all you need to know and be skilled in
Iasa Solution Architect training followed by CITA-A certification has
Don and Rakesh's stamp of approval
Online classes going regularly
Travel's good: But Seattle in rainy season? Austin in summer?
Let's consider organizing and filling a class here
Editor's Notes
A solution has many often conflicting forces or influences which constrain the output. As architects we approach each of these constraints without bias looking for the most balanced output possible which meet or exceed target measured objectives.
The architect uses these influencers to balance each other as well. Stakeholder concerns are often tactical or focused on non-customer facing optimization, while enterprise goals can be lofty and hard to implement within the tight constraints of a project. The project team may create significant architecture drift in the project using time pressures as a reason for governance exemptions. All of these impact the successful value created in the project.
The architect has many tools to use in a target solution and many areas to optimize their strategy. A full solution architecture includes necessary views in business, information, infrastructure and software. These views may be created by the solution architect in smaller projects or may be created by a team of depth architects with a lead in each area in more complicated projects.
Part of the difficulty with the role of solution architect is that they often need enough skills in each specialization to create the strategy for all four areas. This is also true of enterprise architects but at a different level of depth. Many organizations have difficulty navigating the difference in specialists, those architects with depth in one of the specializations, and generalists like the solution architect who have some skills in each but not the depth of a specialist. This is one reason organizations adopt external standards like those from Iasa to help navigate those complications.
Regardless of how the architects are aligned and staffed, every functional IT organization has a model project cycle, or methodology. Usually this consists of:
Portfolio construction and prioritization
Selection of projects
For each initiative or area (sometimes per project), creation of architecture and associated artifacts
Framing individual projects with specified resources and objectives and specifications and/or requirements
Implementation (often called PMO)
Solution delivery, including release management and transfer to operations; cleanup of architecture artifacts
Realization of the project’s solution (and value)
IASA recognizes several specialties within architecture and the organizational alignment of these roles is often very important in terms of what value can be enabled in the business units. Designing the organization is often a complex exercise to triangulate what skills are present, where certain types of systems may exist, and where optimal value may exist. Even if your organization does not use these exact terms, coverage of the disciplines is still important and the specific job roles should have similar outcomes.
All architects are included
Specialists cover appropriate areas
Value “rolls up”
Value is clear to customer
Credit is given appropriately
Career growth supported
Solution architects typically work on multiple projects and multiple lines of business
Software architects growing skills, working on single project start to finish
Each type of architect may have a different “lifespan” with a given initiative or project. Some may be engaged only in certain phases, whereas others may have specific leadership during the entire project.
Enterprise architects typically have touch points on each project.
Info and biz architects work on both single projects and multiple projects
Example – Google does search, data very important to them
Infrastructure architects – both single and multiple projects at a time
Solution architects – 3-5 projects at a time
Software and infrastructure architects – single project
Context is captured in a process known as current state analysis- this covers all aspects of the “as-is” state, from stakeholder perspectives, to help desk calls, to systems architecture today. This builds a picture that we will modify through the course of a project, to deliver some amount of change. The architect always grounds plans in a grounded assessment of current state.
Fundamentally, as an architect, you need to know what a business is, and how, and why, it operates the way it does. It is imperative for you to comprehend that you are tinkering with an entity that employees people, delivers value to customers, and generates revenue for shareholders. As you create solutions, the effectiveness of these solution can lead to business success, or business failure.
As an architect, you need to understand the type of business environment you will be entering so that you can understand the goals and objectives of the stakeholders and the problem domain. In order to interact effectively, you must understand the “business of the business”, or what they are trying to successfully accomplish.
The architecture you create must be consumable by the business in such a way that leads to business success. The only way to make that possible is to understand the business, and make the architecture relevant and actionable to the business and it’s goals.
The architect the seeks to understand how the future state will be realized, we call this the “to-be” state. Often this involves examining resources for cost estimation, providing stakeholder management or user change management, and framing a project in concrete terms (of budget, people, scope).
