Two weeks ago, we had the opportunity to present our research at the Rijksuniversiteit Groningen (RUG) in The 15th Workshop on Service-oriented Enterprise Architecture for Enterprise Engineering. It's been an exciting journey, and in about a month, our findings will be published in the workshop proceedings of EDOC 2023. Over the past six months, we've been dedicated to this research, and we would like to share our insights.
Initiating and Sustaining Design Systems for the Enterpriseuxpin
1. The document discusses athenahealth's efforts to establish an enterprise design system called Forge to improve design quality, velocity, and consistency across their 200+ product teams.
2. It outlines the challenges of the current state including design debt and wasted time recreating common interfaces.
3. The goals of Forge include focusing designer time on higher-value work, establishing design standards and guidelines, and enabling greater code and design reuse across teams.
Platform Engineering is the practice of building and operating a common platform as a product for technology teams.
In this session, we will talk about why and when we need a platform. How to build Platform Engineering and demo.
Jirayut Nimsaeng
Founder & CEO
Opsta (Thailand) Co., Ltd.
Youtube Record: https://youtu.be/brBZYbNbnAo
Dev Mountain Tech Festival 2022 @ Khaoyai
March 19, 2022
This document summarizes the role of an architect and key aspects of architecture. It discusses that an architect understands architectural drivers, designs technical strategies while considering things that are costly to change. An architect fits between the product owner and project manager. The document also covers architecture frameworks, modeling approaches, technical architecture styles, non-functional requirements, and testing non-functional requirements.
With so many different tools at our disposable, how do you pick which ones to learn? At our latest meetup for Denver Code Club, we explored some best practices on evaluating new technology and how you can choose the right tools for you.
The document summarizes a MuleSoft meetup focused on creating an effective internal support model. It discusses why having a support model is important, covering aspects like operations, monitoring, issue resolution processes and more. The meetup agenda includes an overview of the MuleSoft Catalyst framework, which centers around customer success, technology delivery, and organizational enablement. The final section provides guidance on how to create an internal support model based on the Catalyst methodology.
Luna is a desktop application that manages npm dependencies through a modern UI. The presentation discusses:
1) The motivation for creating Luna to address limitations in existing tools and help other developers.
2) The challenges in building something new that fulfills needs and gains community acceptance.
3) The architecture and technology stack of Electron, React, Redux and RxJS that provides testability, maintainability and scalability.
4) The branching model of GitFlow and project structure that keeps development organized.
The Rational Unified Process (RUP) is an iterative and incremental software development framework. It includes artifacts, roles, activities and workflows. Projects using RUP go through inception, elaboration, construction and transition phases with iterations within each phase. The goals are to develop software iteratively while managing requirements, using component architectures, modeling software visually, verifying quality and controlling changes.
Initiating and Sustaining Design Systems for the Enterpriseuxpin
1. The document discusses athenahealth's efforts to establish an enterprise design system called Forge to improve design quality, velocity, and consistency across their 200+ product teams.
2. It outlines the challenges of the current state including design debt and wasted time recreating common interfaces.
3. The goals of Forge include focusing designer time on higher-value work, establishing design standards and guidelines, and enabling greater code and design reuse across teams.
Platform Engineering is the practice of building and operating a common platform as a product for technology teams.
In this session, we will talk about why and when we need a platform. How to build Platform Engineering and demo.
Jirayut Nimsaeng
Founder & CEO
Opsta (Thailand) Co., Ltd.
Youtube Record: https://youtu.be/brBZYbNbnAo
Dev Mountain Tech Festival 2022 @ Khaoyai
March 19, 2022
This document summarizes the role of an architect and key aspects of architecture. It discusses that an architect understands architectural drivers, designs technical strategies while considering things that are costly to change. An architect fits between the product owner and project manager. The document also covers architecture frameworks, modeling approaches, technical architecture styles, non-functional requirements, and testing non-functional requirements.
With so many different tools at our disposable, how do you pick which ones to learn? At our latest meetup for Denver Code Club, we explored some best practices on evaluating new technology and how you can choose the right tools for you.
The document summarizes a MuleSoft meetup focused on creating an effective internal support model. It discusses why having a support model is important, covering aspects like operations, monitoring, issue resolution processes and more. The meetup agenda includes an overview of the MuleSoft Catalyst framework, which centers around customer success, technology delivery, and organizational enablement. The final section provides guidance on how to create an internal support model based on the Catalyst methodology.
Luna is a desktop application that manages npm dependencies through a modern UI. The presentation discusses:
1) The motivation for creating Luna to address limitations in existing tools and help other developers.
2) The challenges in building something new that fulfills needs and gains community acceptance.
3) The architecture and technology stack of Electron, React, Redux and RxJS that provides testability, maintainability and scalability.
4) The branching model of GitFlow and project structure that keeps development organized.
The Rational Unified Process (RUP) is an iterative and incremental software development framework. It includes artifacts, roles, activities and workflows. Projects using RUP go through inception, elaboration, construction and transition phases with iterations within each phase. The goals are to develop software iteratively while managing requirements, using component architectures, modeling software visually, verifying quality and controlling changes.
All'interno della presentazione trovate il dettaglio del settimo Mulesoft Meetup. Si è potuto approfondire strumenti come AnyPointMQ, il valore delle API stabilendo dei KPI e tracciandone l'andamento
APSI - Analisa Perancangan Sistem InformasiFauzi Rakhman
The document discusses various topics related to systems analysis and design projects. It covers project phases like planning, analysis, design, and implementation. It discusses methodologies like prototyping and object-oriented approaches. It emphasizes that the goal is to create business value and that the systems analyst plays a key role in analyzing needs and designing solutions. Projects require identifying tasks, creating workplans, staffing roles, and controlling the project schedule and budget.
How to Choose an Integration Platform Vendor for Your BusinessWSO2
Learn about the key aspects that need to be considered when selecting an integration platform for your business regardless of the business domain you are in.
This document provides an overview of software engineering and development trends presented over 2 days of lectures and demos. It begins with introductions of the lecturer, Vladimir Kotov, and states the topic is software engineering and development FAQs. It then presents and defines key concepts in software engineering like what software and software engineering are, software processes, process models, methods, architecture and enterprise applications. It outlines 5 trends: 1) increasing software complexity, 2) raising abstraction levels, 3) continuous process improvement, 4) adapting to changing requirements, and 5) experience reuse to address recurring problems. It promotes agile principles and software reuse benefits and challenges.
Want to make sure your scope is accurate? How do you dissect requirements to meet your implementation needs? Learn the pitfalls, how to plan MVP projects and what it takes to dig deep and find success when you start your AEM projects.
Dev, Ops, DevOps, Platform Teams – and everybody has it’s own interpretation. But what is meant by platform engineering, actually? What’s the difference to ops? And isn’t that contradictionary to DevOps?
In this talk, Philipp shows Scout24’s journey from separate dev and ops departments to platform teams and the steps in-between. You’ll see how the organisation changed and why this was necessary. On some real-world examples he explains how the platform teams now uses AWS and Docker to enable the feature teams to become faster and more productive.
Software Engineering- Crisis and Process ModelsNishu Rastogi
The document discusses various software engineering process models including the waterfall model, iterative waterfall model, prototyping model, evolutionary model, rapid application development model, and spiral model. It provides details on the key activities and stages in each model's software development life cycle. The document also compares the different models and discusses when each may be best applied based on factors like the problem's understandability, decomposability into modules, and tolerance for incremental delivery.
The document outlines an Architecture Delivery Process (ADP) that guides the creation of architecture deliverables throughout a project's lifecycle. The ADP defines roles and responsibilities for deliverables, inputs required, and how architecture resources are utilized during projects. It aims to maximize the value of architecture by clearly linking business capabilities to technical solutions and ensuring accountability of architects. The ADP also determines what projects require architect involvement based on an architecture significance assessment.
The document discusses the evolutionary architecture and design approach taken for the CIS (Corporate Information System) application developed by Pragati Software. It describes how the architecture and design were incrementally implemented and refined over multiple sprints through story implementation and refactoring. This allowed the architecture to evolve based on real requirements rather than being pre-defined, reducing risks while delivering value to customers early. Key principles included envisioning architecture needs early but evolving them over time through real code and refactoring.
SACON NY 19: "Creating an effective developer experience for cloud-native apps"Daniel Bryant
Many organizations are embracing cloud-native technologies, such as microservices, containers, and Kubernetes, but are struggling to adapt their developer experience (DevEx or DX) and continuous delivery processes. Failure to adapt leads to longer lead times for delivery, frustration for developers, and stability issues in production. Architects and technical leaders need to drive this change.
The developer experience with modern cloud-native technologies is very different than the classic enterprise experience of the 1990s or even the early cloud experiences of the 2000s. For example, it’s often no longer possible to spin up an entire application or system on local hardware, and the extra layers of abstract of containers and VMs make debugging and observing systems more challenging.
Daniel Bryant explores the core concepts of the cloud-native developer experience, introduces and compares several useful tools, and shares lessons learned from the trenches.
This is take two of the presentation, some things added, some removed, but still the regurgitation is best..
The purpose is to raise your awareness of software architecture in light of modern day agile development. Disciplines to incorporate and reconsider
Whitepaper_ State of Platform Engineering Report.pdfjuancarlos747007
This document provides an overview of platform engineering including its origins from DevOps practices, definitions, principles and best practices. Platform engineering emerged as organizations invested in building internal developer platforms to provide self-service capabilities for engineering teams and minimize cognitive load. It is defined as designing toolchains and workflows that enable self-service for application development. Key principles for platform teams include having a clear mission focused on improving developer experience, treating the internal platform as a product, and focusing on common problems across engineering organizations.
Presentation on growing architects presented at the Australian Architecture Forum 2009. This is a further developed concept from the similar SAF presentation.
The document discusses various aspects of managing software projects and processes. It covers tasks that a project manager would be responsible for, including planning, scheduling, directing teams, and monitoring progress. It also discusses different software development models like the waterfall model and agile development. Project managers play an important role in planning projects, estimating costs and schedules, and building effective teams to complete software work.
This story is about engagement of a Solution Architect into absolutely new and complex business domain – life science, where a client wants to modernize his legacy platform, which itself is a unique technological offering on the market. Sounds challenging already? Let’s have a look on how a Solution Architect can be successful in such project.
The document describes a Microsoft workshop where participants will design an end-to-end solution for a customer, Wide World Importers, to orchestrate and deploy updates to their deep learning models and applications in a unified manner. The workshop will cover designing a DevOps pipeline to deploy models and web applications, investigating standardizing models to ONNX format to simplify inference, and monitoring models after deployment. At the end of the workshop, participants will be able to design solutions for fully operationalizing deep learning models throughout the model lifecycle.
Software Development Life Cycle Models | What are Software Process Models ?
Here you are going to know What is Software Development Life Cycle Model or What are Software Process Models?
Software Process Models defines a distinct set of activities, actions, tasks, milestones, and work products that are required to engineer high-quality software...
For more knowledge watch full video...
Video URL:
https://youtu.be/3Lxnn0O3xaM
YouTube Channel URL:
https://www.youtube.com/channel/UCKVvceV1RGXLz0GeesbQnVg
Google+ Page URL:
https://plus.google.com/113458574960966683976/videos?_ga=1.91477722.157526647.1466331425
My Website Link:
http://appsdisaster.blogspot.com/
If you are interested in learning more about topics like this so Please don't forget to like, share, & Subscribe to this channel.
Thanks
Software Process Models | Software Development Process Models | SDLC | Traditional Software Process Models | Waterfall Model Incremental Model | Prototyping Model | Evolutionary Process Model
Working with software architects - advice to project managersYaniv Pessach
This document provides advice to project managers on working with software architects. It defines what software architecture is and discusses different styles such as big design up front, emerging architecture, and good enough architecture. It also covers what architects do including technical oversight, standards enforcement, and long term technical visioning. The document advises involving architects early and regularly throughout the project lifecycle from initiation and planning through execution, monitoring, and closing. Architects are positioned as key partners to project managers.
Artificia Intellicence and XPath Extension FunctionsOctavian Nadolu
The purpose of this presentation is to provide an overview of how you can use AI from XSLT, XQuery, Schematron, or XML Refactoring operations, the potential benefits of using AI, and some of the challenges we face.
Essentials of Automations: The Art of Triggers and Actions in FMESafe Software
In this second installment of our Essentials of Automations webinar series, we’ll explore the landscape of triggers and actions, guiding you through the nuances of authoring and adapting workspaces for seamless automations. Gain an understanding of the full spectrum of triggers and actions available in FME, empowering you to enhance your workspaces for efficient automation.
We’ll kick things off by showcasing the most commonly used event-based triggers, introducing you to various automation workflows like manual triggers, schedules, directory watchers, and more. Plus, see how these elements play out in real scenarios.
Whether you’re tweaking your current setup or building from the ground up, this session will arm you with the tools and insights needed to transform your FME usage into a powerhouse of productivity. Join us to discover effective strategies that simplify complex processes, enhancing your productivity and transforming your data management practices with FME. Let’s turn complexity into clarity and make your workspaces work wonders!
More Related Content
Similar to Paving the path towards platform engineering using a comprehensive reference model.pptx
All'interno della presentazione trovate il dettaglio del settimo Mulesoft Meetup. Si è potuto approfondire strumenti come AnyPointMQ, il valore delle API stabilendo dei KPI e tracciandone l'andamento
APSI - Analisa Perancangan Sistem InformasiFauzi Rakhman
The document discusses various topics related to systems analysis and design projects. It covers project phases like planning, analysis, design, and implementation. It discusses methodologies like prototyping and object-oriented approaches. It emphasizes that the goal is to create business value and that the systems analyst plays a key role in analyzing needs and designing solutions. Projects require identifying tasks, creating workplans, staffing roles, and controlling the project schedule and budget.
How to Choose an Integration Platform Vendor for Your BusinessWSO2
Learn about the key aspects that need to be considered when selecting an integration platform for your business regardless of the business domain you are in.
This document provides an overview of software engineering and development trends presented over 2 days of lectures and demos. It begins with introductions of the lecturer, Vladimir Kotov, and states the topic is software engineering and development FAQs. It then presents and defines key concepts in software engineering like what software and software engineering are, software processes, process models, methods, architecture and enterprise applications. It outlines 5 trends: 1) increasing software complexity, 2) raising abstraction levels, 3) continuous process improvement, 4) adapting to changing requirements, and 5) experience reuse to address recurring problems. It promotes agile principles and software reuse benefits and challenges.
Want to make sure your scope is accurate? How do you dissect requirements to meet your implementation needs? Learn the pitfalls, how to plan MVP projects and what it takes to dig deep and find success when you start your AEM projects.
Dev, Ops, DevOps, Platform Teams – and everybody has it’s own interpretation. But what is meant by platform engineering, actually? What’s the difference to ops? And isn’t that contradictionary to DevOps?
In this talk, Philipp shows Scout24’s journey from separate dev and ops departments to platform teams and the steps in-between. You’ll see how the organisation changed and why this was necessary. On some real-world examples he explains how the platform teams now uses AWS and Docker to enable the feature teams to become faster and more productive.
Software Engineering- Crisis and Process ModelsNishu Rastogi
The document discusses various software engineering process models including the waterfall model, iterative waterfall model, prototyping model, evolutionary model, rapid application development model, and spiral model. It provides details on the key activities and stages in each model's software development life cycle. The document also compares the different models and discusses when each may be best applied based on factors like the problem's understandability, decomposability into modules, and tolerance for incremental delivery.
The document outlines an Architecture Delivery Process (ADP) that guides the creation of architecture deliverables throughout a project's lifecycle. The ADP defines roles and responsibilities for deliverables, inputs required, and how architecture resources are utilized during projects. It aims to maximize the value of architecture by clearly linking business capabilities to technical solutions and ensuring accountability of architects. The ADP also determines what projects require architect involvement based on an architecture significance assessment.
The document discusses the evolutionary architecture and design approach taken for the CIS (Corporate Information System) application developed by Pragati Software. It describes how the architecture and design were incrementally implemented and refined over multiple sprints through story implementation and refactoring. This allowed the architecture to evolve based on real requirements rather than being pre-defined, reducing risks while delivering value to customers early. Key principles included envisioning architecture needs early but evolving them over time through real code and refactoring.
SACON NY 19: "Creating an effective developer experience for cloud-native apps"Daniel Bryant
Many organizations are embracing cloud-native technologies, such as microservices, containers, and Kubernetes, but are struggling to adapt their developer experience (DevEx or DX) and continuous delivery processes. Failure to adapt leads to longer lead times for delivery, frustration for developers, and stability issues in production. Architects and technical leaders need to drive this change.
The developer experience with modern cloud-native technologies is very different than the classic enterprise experience of the 1990s or even the early cloud experiences of the 2000s. For example, it’s often no longer possible to spin up an entire application or system on local hardware, and the extra layers of abstract of containers and VMs make debugging and observing systems more challenging.
Daniel Bryant explores the core concepts of the cloud-native developer experience, introduces and compares several useful tools, and shares lessons learned from the trenches.
This is take two of the presentation, some things added, some removed, but still the regurgitation is best..
The purpose is to raise your awareness of software architecture in light of modern day agile development. Disciplines to incorporate and reconsider
Whitepaper_ State of Platform Engineering Report.pdfjuancarlos747007
This document provides an overview of platform engineering including its origins from DevOps practices, definitions, principles and best practices. Platform engineering emerged as organizations invested in building internal developer platforms to provide self-service capabilities for engineering teams and minimize cognitive load. It is defined as designing toolchains and workflows that enable self-service for application development. Key principles for platform teams include having a clear mission focused on improving developer experience, treating the internal platform as a product, and focusing on common problems across engineering organizations.
Presentation on growing architects presented at the Australian Architecture Forum 2009. This is a further developed concept from the similar SAF presentation.
The document discusses various aspects of managing software projects and processes. It covers tasks that a project manager would be responsible for, including planning, scheduling, directing teams, and monitoring progress. It also discusses different software development models like the waterfall model and agile development. Project managers play an important role in planning projects, estimating costs and schedules, and building effective teams to complete software work.
This story is about engagement of a Solution Architect into absolutely new and complex business domain – life science, where a client wants to modernize his legacy platform, which itself is a unique technological offering on the market. Sounds challenging already? Let’s have a look on how a Solution Architect can be successful in such project.
The document describes a Microsoft workshop where participants will design an end-to-end solution for a customer, Wide World Importers, to orchestrate and deploy updates to their deep learning models and applications in a unified manner. The workshop will cover designing a DevOps pipeline to deploy models and web applications, investigating standardizing models to ONNX format to simplify inference, and monitoring models after deployment. At the end of the workshop, participants will be able to design solutions for fully operationalizing deep learning models throughout the model lifecycle.
Software Development Life Cycle Models | What are Software Process Models ?
Here you are going to know What is Software Development Life Cycle Model or What are Software Process Models?
Software Process Models defines a distinct set of activities, actions, tasks, milestones, and work products that are required to engineer high-quality software...
For more knowledge watch full video...
Video URL:
https://youtu.be/3Lxnn0O3xaM
YouTube Channel URL:
https://www.youtube.com/channel/UCKVvceV1RGXLz0GeesbQnVg
Google+ Page URL:
https://plus.google.com/113458574960966683976/videos?_ga=1.91477722.157526647.1466331425
My Website Link:
http://appsdisaster.blogspot.com/
If you are interested in learning more about topics like this so Please don't forget to like, share, & Subscribe to this channel.
Thanks
Software Process Models | Software Development Process Models | SDLC | Traditional Software Process Models | Waterfall Model Incremental Model | Prototyping Model | Evolutionary Process Model
Working with software architects - advice to project managersYaniv Pessach
This document provides advice to project managers on working with software architects. It defines what software architecture is and discusses different styles such as big design up front, emerging architecture, and good enough architecture. It also covers what architects do including technical oversight, standards enforcement, and long term technical visioning. The document advises involving architects early and regularly throughout the project lifecycle from initiation and planning through execution, monitoring, and closing. Architects are positioned as key partners to project managers.
Similar to Paving the path towards platform engineering using a comprehensive reference model.pptx (20)
Artificia Intellicence and XPath Extension FunctionsOctavian Nadolu
The purpose of this presentation is to provide an overview of how you can use AI from XSLT, XQuery, Schematron, or XML Refactoring operations, the potential benefits of using AI, and some of the challenges we face.
Essentials of Automations: The Art of Triggers and Actions in FMESafe Software
In this second installment of our Essentials of Automations webinar series, we’ll explore the landscape of triggers and actions, guiding you through the nuances of authoring and adapting workspaces for seamless automations. Gain an understanding of the full spectrum of triggers and actions available in FME, empowering you to enhance your workspaces for efficient automation.
We’ll kick things off by showcasing the most commonly used event-based triggers, introducing you to various automation workflows like manual triggers, schedules, directory watchers, and more. Plus, see how these elements play out in real scenarios.
Whether you’re tweaking your current setup or building from the ground up, this session will arm you with the tools and insights needed to transform your FME usage into a powerhouse of productivity. Join us to discover effective strategies that simplify complex processes, enhancing your productivity and transforming your data management practices with FME. Let’s turn complexity into clarity and make your workspaces work wonders!
May Marketo Masterclass, London MUG May 22 2024.pdfAdele Miller
Can't make Adobe Summit in Vegas? No sweat because the EMEA Marketo Engage Champions are coming to London to share their Summit sessions, insights and more!
This is a MUG with a twist you don't want to miss.
Launch Your Streaming Platforms in MinutesRoshan Dwivedi
The claim of launching a streaming platform in minutes might be a bit of an exaggeration, but there are services that can significantly streamline the process. Here's a breakdown:
Pros of Speedy Streaming Platform Launch Services:
No coding required: These services often use drag-and-drop interfaces or pre-built templates, eliminating the need for programming knowledge.
Faster setup: Compared to building from scratch, these platforms can get you up and running much quicker.
All-in-one solutions: Many services offer features like content management systems (CMS), video players, and monetization tools, reducing the need for multiple integrations.
Things to Consider:
Limited customization: These platforms may offer less flexibility in design and functionality compared to custom-built solutions.
Scalability: As your audience grows, you might need to upgrade to a more robust platform or encounter limitations with the "quick launch" option.
Features: Carefully evaluate which features are included and if they meet your specific needs (e.g., live streaming, subscription options).
Examples of Services for Launching Streaming Platforms:
Muvi [muvi com]
Uscreen [usencreen tv]
Alternatives to Consider:
Existing Streaming platforms: Platforms like YouTube or Twitch might be suitable for basic streaming needs, though monetization options might be limited.
Custom Development: While more time-consuming, custom development offers the most control and flexibility for your platform.
Overall, launching a streaming platform in minutes might not be entirely realistic, but these services can significantly speed up the process compared to building from scratch. Carefully consider your needs and budget when choosing the best option for you.
OpenMetadata Community Meeting - 5th June 2024OpenMetadata
The OpenMetadata Community Meeting was held on June 5th, 2024. In this meeting, we discussed about the data quality capabilities that are integrated with the Incident Manager, providing a complete solution to handle your data observability needs. Watch the end-to-end demo of the data quality features.
* How to run your own data quality framework
* What is the performance impact of running data quality frameworks
* How to run the test cases in your own ETL pipelines
* How the Incident Manager is integrated
* Get notified with alerts when test cases fail
Watch the meeting recording here - https://www.youtube.com/watch?v=UbNOje0kf6E
Quarkus Hidden and Forbidden ExtensionsMax Andersen
Quarkus has a vast extension ecosystem and is known for its subsonic and subatomic feature set. Some of these features are not as well known, and some extensions are less talked about, but that does not make them less interesting - quite the opposite.
Come join this talk to see some tips and tricks for using Quarkus and some of the lesser known features, extensions and development techniques.
Transform Your Communication with Cloud-Based IVR SolutionsTheSMSPoint
Discover the power of Cloud-Based IVR Solutions to streamline communication processes. Embrace scalability and cost-efficiency while enhancing customer experiences with features like automated call routing and voice recognition. Accessible from anywhere, these solutions integrate seamlessly with existing systems, providing real-time analytics for continuous improvement. Revolutionize your communication strategy today with Cloud-Based IVR Solutions. Learn more at: https://thesmspoint.com/channel/cloud-telephony
Neo4j - Product Vision and Knowledge Graphs - GraphSummit ParisNeo4j
Dr. Jesús Barrasa, Head of Solutions Architecture for EMEA, Neo4j
Découvrez les dernières innovations de Neo4j, et notamment les dernières intégrations cloud et les améliorations produits qui font de Neo4j un choix essentiel pour les développeurs qui créent des applications avec des données interconnectées et de l’IA générative.
Mobile App Development Company In Noida | Drona InfotechDrona Infotech
Looking for a reliable mobile app development company in Noida? Look no further than Drona Infotech. We specialize in creating customized apps for your business needs.
Visit Us For : https://www.dronainfotech.com/mobile-application-development/
Mobile app Development Services | Drona InfotechDrona Infotech
Drona Infotech is one of the Best Mobile App Development Company In Noida Maintenance and ongoing support. mobile app development Services can help you maintain and support your app after it has been launched. This includes fixing bugs, adding new features, and keeping your app up-to-date with the latest
Visit Us For :
Graspan: A Big Data System for Big Code AnalysisAftab Hussain
We built a disk-based parallel graph system, Graspan, that uses a novel edge-pair centric computation model to compute dynamic transitive closures on very large program graphs.
We implement context-sensitive pointer/alias and dataflow analyses on Graspan. An evaluation of these analyses on large codebases such as Linux shows that their Graspan implementations scale to millions of lines of code and are much simpler than their original implementations.
These analyses were used to augment the existing checkers; these augmented checkers found 132 new NULL pointer bugs and 1308 unnecessary NULL tests in Linux 4.4.0-rc5, PostgreSQL 8.3.9, and Apache httpd 2.2.18.
- Accepted in ASPLOS ‘17, Xi’an, China.
- Featured in the tutorial, Systemized Program Analyses: A Big Data Perspective on Static Analysis Scalability, ASPLOS ‘17.
- Invited for presentation at SoCal PLS ‘16.
- Invited for poster presentation at PLDI SRC ‘16.
Preparing Non - Technical Founders for Engaging a Tech AgencyISH Technologies
Preparing non-technical founders before engaging a tech agency is crucial for the success of their projects. It starts with clearly defining their vision and goals, conducting thorough market research, and gaining a basic understanding of relevant technologies. Setting realistic expectations and preparing a detailed project brief are essential steps. Founders should select a tech agency with a proven track record and establish clear communication channels. Additionally, addressing legal and contractual considerations and planning for post-launch support are vital to ensure a smooth and successful collaboration. This preparation empowers non-technical founders to effectively communicate their needs and work seamlessly with their chosen tech agency.Visit our site to get more details about this. Contact us today www.ishtechnologies.com.au
Do you want Software for your Business? Visit Deuglo
Deuglo has top Software Developers in India. They are experts in software development and help design and create custom Software solutions.
Deuglo follows seven steps methods for delivering their services to their customers. They called it the Software development life cycle process (SDLC).
Requirement — Collecting the Requirements is the first Phase in the SSLC process.
Feasibility Study — after completing the requirement process they move to the design phase.
Design — in this phase, they start designing the software.
Coding — when designing is completed, the developers start coding for the software.
Testing — in this phase when the coding of the software is done the testing team will start testing.
Installation — after completion of testing, the application opens to the live server and launches!
Maintenance — after completing the software development, customers start using the software.
Hand Rolled Applicative User ValidationCode KataPhilip Schwarz
Could you use a simple piece of Scala validation code (granted, a very simplistic one too!) that you can rewrite, now and again, to refresh your basic understanding of Applicative operators <*>, <*, *>?
The goal is not to write perfect code showcasing validation, but rather, to provide a small, rough-and ready exercise to reinforce your muscle-memory.
Despite its grandiose-sounding title, this deck consists of just three slides showing the Scala 3 code to be rewritten whenever the details of the operators begin to fade away.
The code is my rough and ready translation of a Haskell user-validation program found in a book called Finding Success (and Failure) in Haskell - Fall in love with applicative functors.
Need for Speed: Removing speed bumps from your Symfony projects ⚡️Łukasz Chruściel
No one wants their application to drag like a car stuck in the slow lane! Yet it’s all too common to encounter bumpy, pothole-filled solutions that slow the speed of any application. Symfony apps are not an exception.
In this talk, I will take you for a spin around the performance racetrack. We’ll explore common pitfalls - those hidden potholes on your application that can cause unexpected slowdowns. Learn how to spot these performance bumps early, and more importantly, how to navigate around them to keep your application running at top speed.
We will focus in particular on tuning your engine at the application level, making the right adjustments to ensure that your system responds like a well-oiled, high-performance race car.
GraphSummit Paris - The art of the possible with Graph TechnologyNeo4j
Sudhir Hasbe, Chief Product Officer, Neo4j
Join us as we explore breakthrough innovations enabled by interconnected data and AI. Discover firsthand how organizations use relationships in data to uncover contextual insights and solve our most pressing challenges – from optimizing supply chains, detecting fraud, and improving customer experiences to accelerating drug discoveries.
Takashi Kobayashi and Hironori Washizaki, "SWEBOK Guide and Future of SE Education," First International Symposium on the Future of Software Engineering (FUSE), June 3-6, 2024, Okinawa, Japan
Paving the path towards platform engineering using a comprehensive reference model.pptx
1. Paving the path towards
platform engineering
using a comprehensive
reference model
by
Ruben van de Kamp
Kees C. Bakker
Zhiming Zhao
2. About Ruben
● Recent graduate Master Software
Engineering at the University of Amsterdam
● Senior Software Engineer
● Working on services, integrations,
automation and frontend
● Passionate about web development and
platform engineering
● TypeScript / Python
Databricks, NodeJS, Flask
Sports, Economy
Ruben van de Kamp
ruvdkamp@gmail.com
linkedin.com/in/ruben-vd-kamp
3. 3
About Kees
● Pathfinder & Software Engineer
for Wehkamp Tech
● Working on architecture, integrations,
automation and chatops
● Passionate about web, marketing &
automation
● C# / .NET Core
TypeScript+NodeJS, PySpark+Databricks
Techblog, History
Kees C. Bakker
@KeesTalksTech
KeesTalksTech.com
kbakker@wehkamp.nl
linkedin.com/in/keescbakker
4. 1. Who is Wehkamp?
2. How to implement platform engineering?
3. Case study
4. Conclusions & future work
4
Topics
7. over 2.500 brands
WE Fashion // Vingino //Mango // Tommy Hilfiger // Scotch & Soda // ONLY // Private Label
wehkamp home // HK living // Woood // Zuiver // Riverdale // House Doctor
>300.000
different
products
>560.000
daily
visitors
783 million
Sales
21/22
>11 million
sent
packages
>1.000
colleagues
80%
of all customers
shop mobile
72%
of our customers
are female
Wehkamp facts
Focus on: fashion // living // beauty / baby & kids
8. How we run www.wehkamp.nl
Focus on: delivery
334.000
avg. requests
per minute*
19.6 GiB
avg. bandwidth
per minute*
3
FE stacks: web,
IOS, Android
150
Micro-sites &
services
50+
engineers + POs
10
autonomous
DevOps teams
1
platform
team
It ain’t easy being fast
Not just a website. It’s an e-commerce platform!
* Thursday 2023-10-24
20:00 - 22:30 CEST
according to Cloudflare
Statistics Dashboard
10. 10
What ignited our research?
Feels like they are
describing what
we’re trying to do.
Platform as a self-
service product for
developers?
Source: thenewstack.io/how-is-platform-
engineering-different-from-devops-and-sre/
11. 11
What ignited our research?
Many of our
services have the
same basic features
in terms of
observability. We
must be able to
scaffold or provision
them, just like our
databases, right?
Source: engineering.atspotify.com/2020/08/
How-we-use-golden-paths-to-solve-
fragmentation-in-our-software-ecosystem
12. Definition | Research questions | Related work | Reference Model
How to implement
platform engineering?
13. ● Discipline to improve productivity and
efficiency across teams by standardizing
and centralizing tools by introducing a
platform.
● Instead of focussing on a team level, it
focuses on the organization level.
● Tries to solve the following challenges:
proliferation of tools
deployment difficulties
cloud expenses and
communication between teams 13
What is platform engineering?
14. Main research question
How can a software organization
effectively integrate platform engineering
using a comprehensive reference model?
14
Research Questions
RQ1
How to model platform
engineering in the context of a
software company?
RQ2
How to define a customized
platform engineering design
tailored to a specific organization?
RQ3
How to effectively construct a
technical platform engineering
implementation?
15. ● Scientific research → scarcity
15
How to implement platform engineering?
Related work
16. ● Scientific research → scarcity
● Industry related articles →
technical (commercial) approach
16
How to implement platform engineering?
Related work
17. ● Based on the Reference Model
of Open Distributed Processing
(ODP-RM)
17
How to implement platform engineering?
The Platform Engineering Reference Model (PE-RM)
26. ● Implementation of the platform
26
Platform Engineering Reference Model
Technology viewpoint
27. ● Implementation of the platform
● Brownfields vs greenfield
27
Platform Engineering Reference Model
Technology viewpoint
Can be: Grafana, Prometheus,
CloudWatch, Datadog, etc.
Can be: Jenkins, CircleCI,
GitHub Actions, etc.
Start with the tooling that is
currently used.
28. Conceptual design | Technical implementation | Experiments
How to validate
platform engineering?
30. 30
Conceptual design
Enterprise viewpoint
● Gap analysis
● Organizational structure is in place
● Need to redefine roles
● Missing consultation structures (1) Pathfinders: more
formally involved in
the engineering
lifecycle.
31. 31
Conceptual design
Enterprise viewpoint
● Gap analysis
● Organizational structure is in place
● Need to redefine roles
● Missing consultation structures (1) Pathfinders: more
formally involved in
the engineering
lifecycle
(2) Accountability on
platform changes should
be made more formal:
planning and delivery to
stakeholders
32. 32
Conceptual design
Enterprise viewpoint
● Gap analysis
● Organizational structure is in place
● Need to redefine roles
● Missing consultation structures (1) Pathfinders: more
formally involved in
the engineering
lifecycle.
(3) Main stakeholders of
the platform.
(2) Accountability on
platform changes should
be made more formal:
planning and delivery to
stakeholders.
33. 33
Conceptual design
Enterprise viewpoint
● Gap analysis
● Organizational structure is in place
● Need to redefine roles
● Missing consultation structures (1) Pathfinders: more
formally involved in
the engineering
lifecycle.
(2) Accountability on
platform changes should
be made more formal:
planning and delivery to
stakeholders.
(3) Main stakeholders of
the platform.
(4) New stakeholder for
golden path adaptations
which should implement
new platform features.
35. 35
Conceptual design
Informational viewpoint
(2) To enhance understanding
of the platform and productivity
of the development teams.
(1) Improve documentation
and facilitate communication
between platform and
development teams.
36. 36
Conceptual design
Informational viewpoint
(3) Boost productivity,
increase standardization and
best practices, resulting in
improved onboarding time
(2) To enhance understanding
of the platform and productivity
of the development teams.
(1) Improve documentation
and facilitate communication
between platform and
development teams.
41. 41
Conceptual design
Technology viewpoint
No developer portal as a central
starting point for self service
provisioning, docs, observability,
software catalog, etc.
The platform is not
treated as 1
integrated product.
42. By building a prototype
in which we can experiment.
How to validate
platform engineering?
49. 50
What experiments did we design?
Experiment 1
Does the platform improve
productivity?
Experiment 2
Is this something the developer
community wants?
Experiment 3
Is this doable in a
production environment?
performance
analysis
usability
study
expert
feedback
51. ● Use case
● Three tasks
1. Deploy react application to dev
2. Deploy nestjs application to prod
3. Gather logs and metrics of
application in production
Experiments
Performance analysis
52. ● Role
● Ease of use
● Platform task ratio
Experiments
Usability study
easy difficult
53. ● Role
● Ease of use
● Platform task ratio
● Likeable feature
● Recommendation
Experiments
Usability study
54. ● Role
● Platform design
● Ease of use
Experiments
Platform experts feedback
difficult easy
55. ● Role
● Platform design
● Ease of use
● Applicability in organization
● Integration other systems
● Recommendation
Experiments
Platform experts feedback
not applicable very applicable
57. ● PE-RM to model platform engineering in the context of an organization
● Conceptual design guided by the PE-RM
● Technical implementation guided by the PE-RM
● Expose the added value and practical implementation of platform engineering
● Complexity of modelling a methodology (example: accountability)
● Organizational depended decisions
58
Conclusions
Achievements
58. RQ1: How to model platform engineering in the
context of a software company?
● Platform Engineering Reference Model (PE-RM)
● Validation by case study
59
Conclusions
Research questions
59. RQ2: How to define a customized platform engineering
design tailored to a specific organization?
● Conceptual design guided by the PE-RM
60
Conclusions
Research questions
60. RQ3: How to effectively construct a technical platform
engineering implementation?
● Basic engineering platform implementation
● Validation with experiments
● Showcase added value of platform engineering
61
Conclusions
Research questions
61. Main research question: How can a software
organization effectively integrate platform engineering
using a comprehensive reference model?
● Platform Engineering Reference Model
● Case study validation
62
Conclusions
Research questions
62. ● Implement the reference model in a case study
to measure the outcomes
● Case studies within different types of
organizations
● NOTE: The field is new → changes could be
needed
63
Conclusions
Future work
63. Paving the path towards
platform engineering
using a comprehensive
reference model
by
Ruben van de Kamp
Kees C. Bakker
Zhiming Zhao
Editor's Notes
KEES
Paper is based on the master thesis of Ruben van de Kamp, investigating platform engineering at Wehkamp.
KEES
Recent graduate Master Software Engineering at the University of Amsterdam - - graduated with an honours
Have been working for Wehkamp almost 4 years (Product Information team)
KEES
Explain path finder:
Not only enterprise architecture
Also way of working
Turning strategy into delivery
KEES
First we’re going to give some context about Wehkamp and our engineering setup
Then we’re going to look at platform engineering
We’ll elaborate on our case study
And we’ll share the conclusions
KEES
KEES
WRG: Wehkamp Retail Group
3 webshops: Wehkamp, Kleertjes.com and Union River
KEES
Let’s focus on Wehkamp and some statistics
Quite an operation
KEES
KEES
How did we get here?
KEES
Article by The New Stack introducing Platform Engineering
Had not heard about it yet
It feels like a fit, we already use many tools in our container platform.
KEES
Golden paths feel like a fit
Again, the fit is there: observability (logs, metrics) are 100% shared.
Most services use a form of dependency injection and ORM that is not so different.
So the main question is: How can we implement platform engineering?
One way to start: get a graduate student to do some research! So here’s where Ruben comes in!
RUBEN
RUBEN
Before we dive into the research we first want to give a short explanation of what platform engineering is and why it is important
Platform to centralize and standardize tools
Focusses on organization instead of team level
RUBEN
Main focus:
How can platform engineering be implemented
In order to give answer: 3 questions:
How to model
How to design guided by PE-RM
How to implement guided by PE-RM
RUBEN
It can be concise: not a lot of research done.
We have focussed on what reference models there are related to other methodologies:
DevOps and Agile
Focusses on team level and therefore not sufficient for platform engineering
How to model a reference model:
ODP-RM -> later will be explained
RUBEN
Many articles talking on what they believe platform engineering is
White paper from humanitec -> reference architecture, but only focusses on technical implementation
RUBEN
ODP-RM → multiple viewpoints to give better understanding
RUBEN
Created with a iterative process where we interviewed different experts
RUBEN
First thing will be how the platform lifecycle will work, by introducing a platform it needs to have a lifecycle
Two starting positions: no adoption, new features
Lead to same lifecycle where platform is build
RUBEN
The existing development lifecycle will stay the same
Platform engineering will have impact on provision of application domain that will help in development lifecycle
RUBEN
First talk about platform team
Talk about development team and that they are stakeholders of the platform
Development guild → important for golden paths
Enterprise architects
RUBEN
Point out the platform version and golden paths
Development guilds are maintaining these golden paths
RUBEN
Explain that the development team will create an application design and based on that they can come up with platform feature requests
RUBEN
Operations can be separated into two functionalities: getting applications in production and keeping applications in production
Computational viewpoint is more difficult → can be different for each organisation
Golden paths are essential in the translation of these operations
The sequence diagram separates the different actors in planes which we will showcase in the engineering viewpoint
Diagram link: https://app.diagrams.net/#G13CGjLkFYjmYsTMrY3XqGA_1XHfFMPVkd
RUBEN
Based on the Humanitec reference architecture since the separation of planes are valid
Normally it is important to point out the objects and channels, but this way we can better translate into real world scenarios
Developer Portal: one stop shop for self service
RUBEN
It depends on the organization and what tools they already use
Brownfield project
More focussed on the standardization and guidelines on what would be most suitable in this platform
RUBEN
It depends on the organization and what tools they already use
Brownfield project
More focussed on the standardization and guidelines on what would be most suitable in this platform
KEES
Nice overview by Ruben
Let’s see how this matches at Wehkamp
First we’ll create a conceptual design
And than Ruben will guide us through a prototype to do some experiments so validate our model
KEES
Implementation of features
Do’s or don’t – guard against excessive feature
KEES
KEES
Now: users, eat what you get
PE: stakeholder with influence
KEES
Golden path as a reference architecture
Golden path as a jump start
No formal delivery, poor versioning of the platform
Individual tools are now versioned and communicated
Platform should be one integrated product
Measure effectiveness
Missing golden paths
Missing process to further do platform development from the dev team perspective
Again: it is all about individual tools
Less effort
Standardize on default settings
KEES
Let’s add the tools to the boxes of the technology viewpoint
Our tools fit very well within the model
KEES
No dev portal
KEES
The platform is not treated as 1 integrated product.
Ruben wants to do some experiments
We’re missing metrics
Let’s get them from our pipelines / GitHub
Ruben wants to do some experiments
Ruben wants to do some experiments
We’re missing metrics
Let’s get them from our pipelines / GitHub
RUBEN
RUBEN
We mainly used two open source tools from which we continued to implement the platform:
Otomi: PaaS solution → helps to setup a lot of the tooling, however the configurations of the tooling and the way it all interacts as one implementation in this research had to be done manually
Backstage: this is the main point of work, this linked everything together including templates etc.
RUBEN
In order to showcase the added value a platform will bring to the organization and development teams we have created a very based application lifecycle
You will start with creating your application domain:
Create repository
Pipelines
Maybe some boilerplating
You will develop your application
You want to update your domain by making deployment files
You want to monitor you application
RUBEN
We have created golden paths that will have only one input: the application name
It will do the following:
Create your repository
Create your CI/CD pipelines
Create your docker registry
Scaffold the application with best practices
RUBEN
When you want to deploy an application you can use a different golden path → setup deployment workload files
This will take care of the following
Create yaml files for argocd to deploy application
Setup the docker image to the latest version that has been stored
Update pipelines to automatically deploy when new version is released
RUBEN
Because the application are scaffolded in the golden paths they will all expose defaults metrics
Use predefined dashboards to see the metrics
RUBEN
Now that we have created a prototype we can do some experiments to see if it actually has any effects
RUBEN
We did three experiments:
Performance analysis: validate if it is actually helping developers
Usability study: is this platform something that the developers want
Expert feedback: is the implementation suitable within an organization
Performance analysis and usability study are done in one experiment
People from inside and outside the organization were asked
Before we did the experiments we asked the participants to give an estimation on the time it would take them to deploy an entire application to production in which they already have the tools available, they only have to make the entire devops lifecycle
Average: almost 7 hours
The participants are divided into two categories:
No tutorial: deploy react application to dev
Tutorial: deploy nestjs application to Prod, but also dev
Tutorial: gather logs and metrics of application in production
The average time it took to get an application to production was around 22 minutes which is much lower than the average of almost 7 hours.
After the tasks the participants were asked to fill in a questionnaire
Role → different type of roles to get feedback from different experienced people
Ease of use → accidentally reversed the scale, however the ease of use was pretty create, however the open questions suggests that the multiple ui’s made it more difficult
Based on open questions a tutorial and documentation is very helpful especially when onboarding new developers
Task ratio → the platform did almost all the tasks, which is exactly how the participants experienced the experiments
Likeable feature → backstage and the golden paths, since it gave the developers an easier time setup their infrastructure
Recommendation → everybody suggests to introduce this within their work
IMPORTANT: tell about the fact that we first did a demo and discussion to give them the most information before the questionnaire
Role → different types of roles, not on experience but more on the way they are located in the organization, different viewpoints
Platform design → the design of the platform was great, both technical as well as functional
Ease of use → they believe the platform is easy to use
Applicability → not always very high → this was expected since each organization could have their own way of implementing things or have an existing tool set
Integration with other systems → same thing, depends on the organization since green field projects is not likely
Recommend → everybody would recommend the platform however Otomi is not always the best solution
RUBEN
Now that we have explained to you what we have done it is time to wrap things up and summarize our research
RUBEN
Now we only have created a reference model and validated it with a conceptual design and a separate prototype
It would be better to implement it in a real organization and see the effect, but that will take time
Case studies within more organizations to see if is applicable to a range of organizations
The field is new, so it can change fast and therefore the reference model needs to be updated (if necessary)
Although we have tried to keep it as general as possible