Brilliant Software Architecture or How to Build Good Software

•

0 likes•80 views

The document discusses what makes good software architecture. It recommends having an agile development process to handle changing requirements. The software should be modular and flexible to enable changes. Testing all aspects of the software is important to allow flexibility and robustness. Having an automated build pipeline enables continuous testing and improves software quality.

BRILLIANT SOFTWARE
ARCHITECTURE
OR HOW TO BUILD GOOD
SOFTWARE

ME
Matthias Gronwald, Technical Director
matthias.gronwald@turbinekreuzberg.com
15+ years web developer
10+ years eCommerce
(Developement, Technical PM, Technical PO,
Solution Architecture, DevOps, Administration,
Requirements Engineering, ...)

Projekttitel 30. Juni 2017
WHAT MAKES GOOD
SOFTWARE?

Projekttitel 30. Juni 2017 Kapitel
Well crafted
• Needs architecture
• Flexible
• Robust
• Easy to maintain
Does exactly what it should do
• Application behaviour
• Fulﬁls clients needs
What makes good software?

Projekttitel 30. Juni 2017 Kapitel
• Less assumptions more asking
• Question complexity
• Use cases are fun
• Happy path ﬁrst
• Requirements will change — always
Requirements

Projekttitel 30. Juni 2017 Kapitel
• Setup agile process
• Deﬁne release cycles
• Scope releases
• Involve client early
• Also possible for classical projects
with ﬁxed deadline and budget
Be agile

Projekttitel 30. Juni 2017
DESIGN FOR CHANGE?

Projekttitel 30. Juni 2017 Kapitel
Don‘t
• Premature optimization based on
assumptions
Do
• Split up and modularize
Design for change?

Projekttitel 30. Juni 2017 Kapitel
On application level
• Identify subject areas and functional
components that could be replaceable
• No monolith — implement identiﬁed
components independent from each
other (nearly)
• Think Microservices and DDD
On code level
• Loose coupling
• Interfaces
• Think SOLID design principles
Be modular

Projekttitel 30. Juni 2017 Kapitel
What about dependencies?
• Build contracts
• JSON Schema
• XML Schema
• Interfaces
• DTOs / Transfer objects

Projekttitel 30. Juni 2017
BE INCREMENTAL

Projekttitel 30. Juni 2017 Kapitel
• Do not head for the best solution that
would ﬁt all possible future problems
you are going to expect
• Head for the best solution you can
come up for your current problem
• Adapt and extend only when needed
• Evolving order principle / less is more
• Do Spikes if you are unsure about
some implementation approach
Be incremental

Projekttitel 30. Juni 2017
TEST ALL THE THINGS

Projekttitel 30. Juni 2017 Kapitel
• Tests are the key to ﬂexible and robust
Software
• Increase the maturity in your Software
• Enables possibility to change things
• Add layer of security
• Also for legacy code
• Try to practice Test Driven
Development
Test all the things

Projekttitel 30. Juni 2017
BUILD PIPELINE

Projekttitel 30. Juni 2017 Kapitel
• Enables regular automated testing
• Provides metrics on code quality
• Continuous integration
• Increases software quality
Build Pipeline

Projekttitel 30. Juni 2017
GREAT POSSIBILITIES

Projekttitel 30. Juni 2017 Kapitel
• Experience of more than 5 decades of
software development available in
books, papers, talks etc.
• Exciting technologies and tools (VMs,
Containers, Frameworks) only recently
• Now starts the time to write good
software
Great possibilities

Projekttitel 30. Juni 2017 Kapitel
• Requirements change constantly
• It needs an agile process to deal with
that
• We need to follow a modular approach
to software
• Tests enable change
• No tests without a pipeline
• So many possibilities — No excuses
anymore
Summary

Projekttitel 30. Juni 2017
MUITO OBRIGADO

Turbine Kreuzberg GmbH
Ohlauer Straße 43
10999 Berlin
MUITO OBRIGADO
Contact
matthias.gronwald@turbinekreuzberg.com
Book recommendations
• Clean Code by Robert „Uncle Bob“ C. Martin
• Code Complete: A Practical Handbook of
Software Construction by Steve McDonnell
• The Pragmatic Programmer by Andrew Hunt,
David Thomas and Ward Cunningham

This document summarizes how an insurance webshop was developed in 6 months using agile and Scrum methods. A cross-functional co-located team worked in 3-week sprints with daily stand-ups and demonstrations. Prototyping was done before coding to refine requirements and design. While most of the project went smoothly, one off-site team caused communication issues until an embedded developer solved integration problems. Using agile practices like Scrum allowed the project to be completed on time and on budget.

Mini LeSS Huge

Xudong Yu

The document describes a framework called Mini LeSS Huge used for large-scale Scrum development with multiple teams. It has the following key aspects: - Uses Scrum and LeSS principles with 10 developers split across backend and frontend teams. - Features a single product backlog, product owner, and sprint planning meetings to coordinate work across teams. - Implements "feature teams" where each team works on user stories from end-to-end rather than separating tasks. - Emphasizes continual review of working software, collaboration between teams, and feedback from stakeholders to ensure successful delivery each sprint.

Building Lean and Agile in the Real World

Kevin Goldsmith

The document discusses lessons learned from implementing lean and agile approaches in three different products or organizations: Microsoft Windows CE.Net Platform Builder, Adobe Revel, and Spotify. For each product, both positive and negative lessons are outlined, such as isolating the effort as an experiment and being careful of early success for Windows, and balancing autonomy and collaboration for Spotify.

"How we make Agile and CI/CD works" by Rendra Toro (OLX Indonesia)

Tech in Asia ID

Rendra Toro is a CTO at OLX Indonesia, the world’s leading classifieds platform, with a presence in more than 40 countries around the globe. This slide was shared on Tech in Asia DevTalk : “Fundamental of Agile Software Development” in collaboration with Jenius on 27 October 2016. Get updates about our dev events delivered straight to your inbox by signing up here: http://bit.ly/tia-dev ! Be the first to know when new information is available!

Tricks to get the most out of your DevOps

RaTul Basak

DevOps is a software development methodology that combines development and IT operations. It aims to shorten the development life cycle and improve collaboration by automating the process of software builds, testing, and releases, and monitoring infrastructure changes. Some key components of DevOps include continuous integration, where code changes are automatically built and tested; continuous deployment to automatically deploy code changes; and treating infrastructure as code to provision and manage servers through code. Logging and monitoring tools are also important for microservices and scaling systems to handle large amounts of data and traffic.

Resume

Jason Morganson

Jason Morganson is an experienced engineering manager and software developer with over 15 years of experience leading teams and managing projects. He is currently the Engineering Manager at GameChanger where he coordinates a cross-functional product development team. Previously, he was the Director of Engineering at Krossover where he grew the engineering team from one to six developers and helped the company scale from 12 to over 70 employees. He also has experience as a software engineer, devops engineer, and entrepreneur through starting his own general contracting business.

Metrics To Support An Agile Transformation

Hugo Messer

Let's Talk DevOps

Hugo Messer

This document discusses DevOps implementation at PT Prudential Life Assurance. It explains that DevOps aims to improve collaboration between development and operations teams to enable faster and more effective releases with better quality. Some key DevOps benefits include increased speed of delivery, reliability through automated testing, ability to scale, and improved collaboration between teams. The document also notes that Agile and DevOps can be used together, with Agile focusing on managing small features and DevOps focusing on collaboration between teams. It lists common DevOps best practices such as microservices, continuous integration, continuous delivery, infrastructure as code, monitoring and logging, and communication.

The Home Depot has over 3500 engineers averaging nearly 6000 git commits per day, with 91% of software written in-house. They have invested $11.1 billion over 4 years, hiring over 1000 new engineers to transform the company from projects to products and experiences. They focus on living their culture and values by investing in associates through cohorts, ongoing education, and onboarding to create an attractive environment for engineers while accomplishing great things like award-winning mobile apps and changing associates' lives.

WEBINAR: How you can implement continuous delivery and deliver software faster

Belatrix Software

Every technical organization is looking to deliver faster, cheaper and with better quality. To help achieve this, increasingly organizations are turning to continuous delivery. Implementing continuous delivery means organizations can frequently adapt software to the needs of their users, improve customer satisfaction and boost business results. In this webinar we were joined by quality assurance expert, Steven Winter, founder of GuerrillaQA, and Federico Tacchini of Belatrix, to examine, de-mystify, and provide a clear path towards continuous delivery and testing.

Introducing Agile to Product Teams

Jeremy Horn

Slides Ari Tiktin recently used in his discussion w/ mentees of The Product Mentor. The Product Mentor is a program designed to pair Product Mentors and Mentees from around the World, across all industries, from start-up to enterprise, guided by the fundamental goals…Better Decisions. Better Products. Better Product People. Throughout the program, each mentor leads a conversation in an area of their expertise that is live streamed and available to both mentee and the broader product community.

Boosting your SW development with Devops

Timo Stordell

This document discusses how DevOps practices can improve software development. It begins by providing background on the author and their company Eficode. It then contrasts classic/waterfall software development approaches with more modern agile approaches enabled by DevOps. Classic approaches are prone to "Epic Fail" through lack of prioritization, coordination, and automation. Modern approaches emphasize prioritizing requirements, completing features incrementally, defining minimum viable products, sharing information efficiently, continuous optimization, embracing automation and tools, building cross-functional teams, and applying DevOps practices across the entire organization and product development lifecycle.

Dicoding Developer Coaching #38: Android | 5 Library Android yang Patut Kamu ...

DicodingEvent

Dicoding Developer Coaching merupakan webinar, yang membahas tuntas kendala maupun pertanyaan yang sering ditanyakan di Academy Dicoding. Tema kali ini adalah "5 Library Android yang Patut Kamu Coba di 2021" Library sering sekali membantu kita sebagai developer untuk mengembangkan aplikasi dengan lebih cepat dan efisien. Nah, di sini kita akan memilih 5 Library yang patut kamu coba di tahun 2021. Ada library yang dapat membantu dalam memanajemen log dan juga error ketika aplikasi dirilis. Ada juga library yang dapat membuat desain aplikasi menjadi lebih menarik. Selain itu, ada juga library yang dapat digunakan untuk menampilkan peta. Penasaran library apa sajakah itu? Yuk ikuti developer coaching penutup dari series Android ini.

What can we do to create more Efficient Model Based Collaboration

Alan Didcock

Five ways continuous delivery can be a product managers superpower empower b...

Suzie Prince

Five ways continuous delivery can be a product manager's superpower outlines how continuous delivery can transform an organization, improve software development performance, and cultivate a high-performing culture. Continuous delivery allows for frequent, incremental updates to be deployed safely and quickly, enabling product managers to implement lean practices like experimentation and incorporating customer feedback. Studies show continuous delivery is associated with 50% higher market growth and reducing burnout compared to traditional software development approaches. The presentation provides recommendations for product managers to start mapping current processes and working in small batches to realize these benefits.

Accept innovation jam pcamp 2011

Nils Davis

An innovation jam is a short, focused period where employees think creatively and work collaboratively outside normal processes. The company held a week-long innovation jam where employees proposed and voted on ideas, then teams spent a weekend developing top ideas using new technologies. While teams made progress prototyping ideas, fully developing products requires more time. However, the jam was a success in testing ideas, motivating employees with new technologies, and giving the company opportunities to contribute to product progress. The company plans to hold more innovation jams going forward.

Agile Development Methodology: 10 Important Principles

dsp

Agile Management with ITPP

Smidigkonferansen

This document discusses the ITPP certification program in agile management. ITPP combines principles from PRINCE2 and Agile Contracting and Execution (ACE). ITPP trains professionals in agile practices like value-based prioritization, iterative delivery, and benefits tracking from the customer's perspective. Since launching in 2012, over 250 people have earned the ITPP certification in Norway. An online English version was released in 2015.

Agile Metrics Meetup: What to Measure and How?

Hugo Messer

This document discusses agile metrics and how to measure them properly. It begins by introducing AMOEBA, a corporate startup program within Telkom Indonesia. It then discusses the need for agility and some examples of business, innovation, team, and method metrics. It emphasizes the importance of ensuring an organization is agile-ready by assessing how well it aligns with agile principles. It also discusses principles for staying grounded, using metrics properly, and how measuring agile metrics is a learning journey. The overall message is on the importance of measuring agile metrics correctly to improve product development.

Building Agility Brick by Brick : A report on how Agile imbibed successfully ...

Amit Srivastava, PMP

How to sell SilverStripe in the enterprise and public sector markets - Stripe...

Sylvain Reiter

Silverstripe is an amazing CMS framework that competes with the biggest names in our industry. In that presentation, my goal is to convince you of this. I know that being here you are not thinking about Drupal, SiteCore or Kentico but if you have ever talked to clients, they might have challenged you on that statement? Has that happened to any of you recently? So if you still have any doubt, I will demonstrate how we made that statement come true.

UX in a Dual Track Agile World

Andrea Neuhoff

What do you get when user experience drives the agile process? Dual-Track Agile, where the features of the product are discovered alongside the development of the product itself. This session will explain what dual-track agile is, the benefits of dual-track agile, the role of UX, and what to expect. It will focus on the discovery cycle, the role of validated hypotheses and assumptions and how UX uniquely contributes to this invaluable process.

Fishbowl Opc.Com Presentation

AIIM Minnesota

The document discusses the benefits of using a web content management (WCM) system over a traditional website update process. It provides an overview of typical challenges with traditional websites where IT support is needed for all updates. WCM allows non-technical users to directly edit and update website content. The document also describes a case study of how Oglethorpe Power Corporation implemented a new WCM-powered website within 6 weeks to allow for easy inline content updates by internal users.

"The Agile Journey in Jenius" by Wijayawati Yip (Jenius)

Tech in Asia ID

Wijayawati Yip is a VP, Scrum Master at JENIUS (jenius.com), a revolutionary application from PT Bank Tabungan Pensiunan Nasional Tbk (BTPN) for managing life finance. This slide was shared on Tech in Asia DevTalk : “Fundamental of Agile Software Development” in collaboration with Jenius on 27 October 2016. Get updates about our dev events delivered straight to your inbox by signing up here: http://bit.ly/tia-dev ! Be the first to know when new information is available!

VPLinit

Bill Gladwin

The document outlines a proposed website project for a virtual project leader. The project aims to [1] create a website documenting the process of developing a project to serve as a reference for others, [2] include forms, procedures and milestones to demonstrate a standard approach to projects, and [3] allow for updates and suggestions to track changes over time. The project scope is moderate, using a simple development tool, and will be worked on during the developer's free time with a proposed 3 month timeline.

How we use Silverstripe CMS to deliver bilingual and accessible websites

MichaelPritchard21

From dysfunction to cross function in 8,593 easy steps- team building at the cbc

Sam Lightowler

When it comes to scaling Agile, there is no one size fits all solution. Frameworks like Scrum and XP prescribe roles, events, artifacts, and rules that make it very clear how interaction should take place within a team. When we begin to add more teams to the mix, communication between teams becomes more complex. This complexity threatens to reduce our transparency and damage our culture. How can we share information, build our culture and work together, all while keeping with Agile values? During this session Sam Lightowler and Jade Stephen will take an in depth look at the successes and failures of CBC Digital Operations when it comes to cross-team collaboration and information sharing. We will discuss what meetings and techniques have helped us build a one-team-one-product mindset, a sense of community, and a culture of Collaboration, Learning and Improvement. We will also discuss what we have tried in the past and how learning from those experiments helped us evolve into the agile-friendly and unified team that we are today.

Usa prácticas de integración continua y sobrevive para luchar otro día.

Software Guru

The document discusses continuous integration (CI) and continuous delivery (CD) practices. It defines CI as ensuring good health of the codebase through frequent commits and automated testing. CD is defined as reliably releasing new features to market frequently through deployment pipelines. The document provides benefits of CI/CD like improved quality and risk mitigation. It also gives best practices and lessons learned from implementing CI/CD in an e-commerce platform, such as knowing the product, not changing everything at once, being pragmatic, trusting the process, and making everyone responsible.

Produce reliable content_v5

COM&TEC Assoc. Ital. per la Comunicaz. Tecn.

The document discusses how a DITA CMS (Content Management System) can help produce reliable content. It outlines the content lifecycle and how a CMS can automate workflows, enable reuse, and help with quality control through features like version control, reviews, and translation management. The document also provides an overview of DITA (Darwin Information Typing Architecture) and examples of how medical device and technology companies have benefited from implementing a DITA CMS.

Implement DevOps Like a Unicorn—Even If You’re Not One

TechWell

Etsy, Netflix, and the unicorns have done great things with DevOps. Although most people don't work at a unicorn, they still want to combine agility and stability. To close the gap between developers and operations, Mason Leung says his company runs operation workshops, blogs about infrastructure, and experiments with different tools—and are solving the same problems as the unicorns only on a smaller scale. Mason explains that you don't get to millions of requests without going through the first several hundred. Ideas you can take from unicorns include how to use containers to enhance development experience, how to avoid production meltdown with continuous deployment, how to tame infrastructure gone wild, why “new shiny” is not always the correct solution, and why putting all your eggs in a cloud service provider is a good idea. There is no single, correct way to DevOps. By observing the unicorns and applying the lessons to your situation, your DevOps journey can be less volatile and more fulfilling as you prepare for the hypergrowth.

What's hot

Barabara Sanders SpringOne Platform keynote

VMware Tanzu

WEBINAR: How you can implement continuous delivery and deliver software faster

Belatrix Software

Introducing Agile to Product Teams

Jeremy Horn

Boosting your SW development with Devops

Timo Stordell

Dicoding Developer Coaching #38: Android | 5 Library Android yang Patut Kamu ...

DicodingEvent

What can we do to create more Efficient Model Based Collaboration

Alan Didcock

Five ways continuous delivery can be a product managers superpower empower b...

Suzie Prince

Accept innovation jam pcamp 2011

Nils Davis

Agile Development Methodology: 10 Important Principles

dsp

Agile Management with ITPP

Smidigkonferansen

Agile Metrics Meetup: What to Measure and How?

Hugo Messer

Building Agility Brick by Brick : A report on how Agile imbibed successfully ...

Amit Srivastava, PMP

How to sell SilverStripe in the enterprise and public sector markets - Stripe...

Sylvain Reiter

UX in a Dual Track Agile World

Andrea Neuhoff

Fishbowl Opc.Com Presentation

AIIM Minnesota

"The Agile Journey in Jenius" by Wijayawati Yip (Jenius)

Tech in Asia ID

VPLinit

Bill Gladwin

How we use Silverstripe CMS to deliver bilingual and accessible websites

MichaelPritchard21

From dysfunction to cross function in 8,593 easy steps- team building at the cbc

Sam Lightowler

Usa prácticas de integración continua y sobrevive para luchar otro día.

Software Guru

What's hot (20)

Barabara Sanders SpringOne Platform keynote

WEBINAR: How you can implement continuous delivery and deliver software faster

Introducing Agile to Product Teams

Boosting your SW development with Devops

Dicoding Developer Coaching #38: Android | 5 Library Android yang Patut Kamu ...

What can we do to create more Efficient Model Based Collaboration

Five ways continuous delivery can be a product managers superpower empower b...

Accept innovation jam pcamp 2011

Agile Development Methodology: 10 Important Principles

Agile Management with ITPP

Agile Metrics Meetup: What to Measure and How?

Building Agility Brick by Brick : A report on how Agile imbibed successfully ...

How to sell SilverStripe in the enterprise and public sector markets - Stripe...

UX in a Dual Track Agile World

Fishbowl Opc.Com Presentation

"The Agile Journey in Jenius" by Wijayawati Yip (Jenius)

VPLinit

How we use Silverstripe CMS to deliver bilingual and accessible websites

From dysfunction to cross function in 8,593 easy steps- team building at the cbc

Usa prácticas de integración continua y sobrevive para luchar otro día.

Similar to Brilliant Software Architecture or How to Build Good Software

Produce reliable content_v5

COM&TEC Assoc. Ital. per la Comunicaz. Tecn.

Implement DevOps Like a Unicorn—Even If You’re Not One

TechWell

Microsoft teams a four course developer menu - M365 saturday Oct 19

Asish Padhy

Microsoft Teams is the fastest growing communications and collaboration platform, and has received tremendous adoption in past few years. At the same time, the development landscape for MS Teams has spanned up to include varied number of solution approaches - apps, bots, connectors, extensions, team provisioning etc. This is great but also has meant that developers are spending more time finding the right option and planning the solution through various stages of implementation. In order to increase effectiveness in delivery, we have to start planning best fit solution models for the various offerings and put them in smaller roll outs for quicker and smaller builds to reach the end user goal. In this session, we will look at some of these solution models for each Teams component, pro and cons of each, and then strategies for various team implementations, in way of "The Developer Four course menu", to achieve optimal delivery in a lean and agile way.

The Dual-Track Agile UX Process at Dell EMC

uxpin

How to take the stress out of writing case studies

DesignHammer

Case studies are great sales tools. But how many times have you gotten ready to submit a pitch, and realized you were missing case studies for the projects you want to highlight? You assumed somebody on the team would write one after the projected deployed, but everyone got reassigned to other projects, and it slipped through the cracks, again. And now you are sad. But it doesn’t have to be this way. Learn why we draft our project case studies before writing the first line of code, and how the team uses the case study draft as a quality assurance step to help ensure a successful project outcome.

How to take the stress out of writing case studies

DesignHammer

Research Ready to Build: Compelling Artefacts that Speak Your Agile Team's La...

Joshua Ledwell

This document summarizes two case studies of ensuring user research findings and early design guidance stay relevant for agile teams over time. Case study 1 involved creating a long-term customer data experience strategy to guide four agile teams. Case study 2 aimed to improve a complex software feature with dependencies on other parts. Key lessons included creating artifacts in the team's language, showing how design builds on research, hijacking agile ceremonies, sustaining buy-in from stakeholders, and committing to sustainability over burnout. The document concludes by discussing making artifacts easy to maintain and evolve the practice across projects.

Azure Saturday 2017 - Planning for the Cloud

Eric Berg

Agile engineering practices

Mustafa Savaşcı

User Experience Programme showcase lightening talks

Neil Allison

Agile: Not Just for Sofware

John Carter

This document discusses applying agile methods to product development beyond just software. It argues that agile can accelerate tangible product development by nesting sprints within milestone frameworks and establishing high-performance cross-functional teams. However, functional managers often resist ceding control and collaboration, posing the biggest challenge to success. Case studies show that focusing agile adoption on planning, demos, and facilitation can lead to improved schedule adherence, decision-making, and overall project accuracy despite higher prototyping costs.

Qa role in agile teams

Anwar Sadat

This document discusses the role of QA in agile teams. It begins with an overview of agile methods and quality before comparing the traditional QA role to the agile QA role. In agile, QA is an integral part of the development team. The document then outlines the responsibilities of QA in agile teams such as helping define user stories, participating in planning and estimates, conducting sashimi acceptance testing, automating test cases, and providing continuous feedback. It concludes by discussing common mistakes made with QA in agile.

Behavior Driven Development—A Guide to Agile Practices

TechWell

It seems as if the agile methods have lots of DD’s going on. BDD – Behavior Driven Development, ATDD – Acceptance Test Driven Development and several others. Adopting BDD allows for testing to be done as early as possible in the software development life cycle, promoting accurate testing, ensuring proper test coverage, and supporting the introduction of automation testing. One challenge is understanding the characteristics and benefits of “driven” approaches. Join Josh Eastman to discover ways that BDD can be employed to describe and test system behavior, user stories, and user acceptance. Josh will discuss Gherkin - the language to capture behavior descriptions and automation with cucumber and explore the four major values of BDD to ensure product quality, while driving time and cost savings. Leave this session with a ideas to reduce the ambiguity and miscommunications that occurs during development and testing.

Applying both of waterfall and iterative development

Deny Prasetia

This document discusses applying both waterfall and iterative development models to a project to develop a tool with minimum functionality in a short time for an operating lease business. It identifies challenges of growing business needs, lack of standardized processes and manual data entry. An assessment is proposed to clarify requirements and scope. Both waterfall and iterative development models are described. The document recommends using iterative development within the waterfall model to allow for prototyping, user feedback and flexibility to changes. Key success factors include collaborative teams, monitoring progress daily, and continual improvement between iterations. Lessons focus on managing risks, quality processes and using story point estimation.

Storytelling with software

Carl Sziebert

This document summarizes a presentation about the importance of prototyping in UX design. It discusses that prototypes allow designers to: 1) Build a shared understanding of ideas across teams by getting feedback early from stakeholders like engineering and product managers. 2) Foster a deeper understanding of user needs by testing prototypes with real users on real devices. 3) Overcome biases by validating design directions early through user research and feedback. The document provides examples of prototyping tools that may be suitable for different design challenges and scenarios. It emphasizes that prototyping is important for communicating vision, validating designs, and designing as a collaborative rather than individual process.

Evolve 19 | Gina Petruccelli | Let’s Dig Into Requirements

Evolve The Adobe Digital Marketing Community

SCGMIS Agile Business Analysis Workshop July 2014

Justin Petite

This document provides an overview of business analysis in an agile environment. It begins with introductions and objectives, then covers agile principles and methodologies. Key topics include iterative development, Scrum roles and ceremonies, planning techniques like roadmaps and personas, and tools like user stories. The presentation emphasizes the important role of the business analyst in collaborating with teams to decompose requirements and ensure delivery of valuable working software.

Directions NA Water-Agile-Fall methodology and NAV implementation

Aleksandar Totovic

UX in an agile environment, 6 December 2016, Copenhagen

InfinIT - Innovationsnetværket for it

containerdays2017 - Microservice and now?

Björn Jessen-Noak

This document discusses microservices and continuous delivery pipelines. It begins with an introduction to microservices and emphasizes designing them to fail gracefully and testing them heavily. It then covers continuous delivery pipelines, stressing the importance of testing first, integrating second, and deploying to production only when ready. The document recommends automating pipelines fully and using chatbots and sample services to streamline development. It emphasizes maintaining production services through incremental, measured updates and sharing knowledge through culture, automation, measurement, and sharing.

Similar to Brilliant Software Architecture or How to Build Good Software (20)

Produce reliable content_v5

Implement DevOps Like a Unicorn—Even If You’re Not One

Microsoft teams a four course developer menu - M365 saturday Oct 19

The Dual-Track Agile UX Process at Dell EMC

How to take the stress out of writing case studies

Research Ready to Build: Compelling Artefacts that Speak Your Agile Team's La...

Azure Saturday 2017 - Planning for the Cloud

Agile engineering practices

User Experience Programme showcase lightening talks

Agile: Not Just for Sofware

Qa role in agile teams

Behavior Driven Development—A Guide to Agile Practices

Applying both of waterfall and iterative development

Storytelling with software

Evolve 19 | Gina Petruccelli | Let’s Dig Into Requirements

SCGMIS Agile Business Analysis Workshop July 2014

Directions NA Water-Agile-Fall methodology and NAV implementation

UX in an agile environment, 6 December 2016, Copenhagen

containerdays2017 - Microservice and now?

Recently uploaded

Essentials of Automations: The Art of Triggers and Actions in FME

Safe 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!

Microservice Teams - How the cloud changes the way we work

Sven Peters

A lot of technical challenges and complexity come with building a cloud-native and distributed architecture. The way we develop backend software has fundamentally changed in the last ten years. Managing a microservices architecture demands a lot of us to ensure observability and operational resiliency. But did you also change the way you run your development teams? Sven will talk about Atlassian’s journey from a monolith to a multi-tenanted architecture and how it affected the way the engineering teams work. You will learn how we shifted to service ownership, moved to more autonomous teams (and its challenges), and established platform and enablement teams.

GraphSummit Paris - The art of the possible with Graph Technology

Neo4j

A Study of Variable-Role-based Feature Enrichment in Neural Models of Code

Aftab Hussain

Understanding variable roles in code has been found to be helpful by students in learning programming -- could variable roles help deep neural models in performing coding tasks? We do an exploratory study. - These are slides of the talk given at InteNSE'23: The 1st International Workshop on Interpretability and Robustness in Neural Software Engineering, co-located with the 45th International Conference on Software Engineering, ICSE 2023, Melbourne Australia

Orion Context Broker introduction 20240604

Fermin Galan

Empowering Growth with Best Software Development Company in Noida - Deuglo

Deuglo Infosystem Pvt Ltd

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.

Why Mobile App Regression Testing is Critical for Sustained Success_ A Detail...

kalichargn70th171

A dynamic process unfolds in the intricate realm of software development, dedicated to crafting and sustaining products that effortlessly address user needs. Amidst vital stages like market analysis and requirement assessments, the heart of software development lies in the meticulous creation and upkeep of source code. Code alterations are inherent, challenging code quality, particularly under stringent deadlines.

SWEBOK and Education at FUSE Okinawa 2024

Hironori Washizaki

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.

openEuler Case Study - The Journey to Supply Chain Security

Shane Coughlan

May Marketo Masterclass, London MUG May 22 2024.pdf

Adele Miller

Hand Rolled Applicative User ValidationCode Kata

Philip 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.

What is Augmented Reality Image Tracking

pavan998932

Introducing Crescat - Event Management Software for Venues, Festivals and Eve...

Crescat

Crescat is industry-trusted event management software, built by event professionals for event professionals. Founded in 2017, we have three key products tailored for the live event industry. Crescat Event for concert promoters and event agencies. Crescat Venue for music venues, conference centers, wedding venues, concert halls and more. And Crescat Festival for festivals, conferences and complex events. With a wide range of popular features such as event scheduling, shift management, volunteer and crew coordination, artist booking and much more, Crescat is designed for customisation and ease-of-use. Over 125,000 events have been planned in Crescat and with hundreds of customers of all shapes and sizes, from boutique event agencies through to international concert promoters, Crescat is rigged for success. What's more, we highly value feedback from our users and we are constantly improving our software with updates, new features and improvements. If you plan events, run a venue or produce festivals and you're looking for ways to make your life easier, then we have a solution for you. Try our software for free or schedule a no-obligation demo with one of our product specialists today at crescat.io

GreenCode-A-VSCode-Plugin--Dario-Jurisic

Green Software Development

DDS-Security 1.2 - What's New? Stronger security for long-running systems

Gerardo Pardo-Castellote

Neo4j - Product Vision and Knowledge Graphs - GraphSummit Paris

Neo4j

LORRAINE ANDREI_LEQUIGAN_HOW TO USE ZOOM

lorraineandreiamcidl

UI5con 2024 - Boost Your Development Experience with UI5 Tooling Extensions

Peter Muessig

The UI5 tooling is the development and build tooling of UI5. It is built in a modular and extensible way so that it can be easily extended by your needs. This session will showcase various tooling extensions which can boost your development experience by far so that you can really work offline, transpile your code in your project to use even newer versions of EcmaScript (than 2022 which is supported right now by the UI5 tooling), consume any npm package of your choice in your project, using different kind of proxies, and even stitching UI5 projects during development together to mimic your target environment.

APIs for Browser Automation (MoT Meetup 2024)

Boni García

Recently uploaded (20)

Essentials of Automations: The Art of Triggers and Actions in FME

Microservice Teams - How the cloud changes the way we work

GraphSummit Paris - The art of the possible with Graph Technology

A Study of Variable-Role-based Feature Enrichment in Neural Models of Code

Orion Context Broker introduction 20240604

Empowering Growth with Best Software Development Company in Noida - Deuglo

Why Mobile App Regression Testing is Critical for Sustained Success_ A Detail...

SWEBOK and Education at FUSE Okinawa 2024

Need for Speed: Removing speed bumps from your Symfony projects ⚡️

openEuler Case Study - The Journey to Supply Chain Security

May Marketo Masterclass, London MUG May 22 2024.pdf

Hand Rolled Applicative User ValidationCode Kata

What is Augmented Reality Image Tracking

Introducing Crescat - Event Management Software for Venues, Festivals and Eve...

GreenCode-A-VSCode-Plugin--Dario-Jurisic

DDS-Security 1.2 - What's New? Stronger security for long-running systems

Neo4j - Product Vision and Knowledge Graphs - GraphSummit Paris

LORRAINE ANDREI_LEQUIGAN_HOW TO USE ZOOM

UI5con 2024 - Boost Your Development Experience with UI5 Tooling Extensions

APIs for Browser Automation (MoT Meetup 2024)

Brilliant Software Architecture or How to Build Good Software

1. BRILLIANT SOFTWARE ARCHITECTURE OR HOW TO BUILD GOOD SOFTWARE

2. ME Matthias Gronwald, Technical Director matthias.gronwald@turbinekreuzberg.com 15+ years web developer 10+ years eCommerce (Developement, Technical PM, Technical PO, Solution Architecture, DevOps, Administration, Requirements Engineering, ...)

3. Projekttitel 30. Juni 2017 WHAT MAKES GOOD SOFTWARE?

4. Projekttitel 30. Juni 2017 Kapitel Well crafted • Needs architecture • Flexible • Robust • Easy to maintain Does exactly what it should do • Application behaviour • Fulﬁls clients needs What makes good software?

5. Projekttitel 30. Juni 2017 REQUIREMENTS

6. Projekttitel 30. Juni 2017 Kapitel • Less assumptions more asking • Question complexity • Use cases are fun • Happy path ﬁrst • Requirements will change — always Requirements

7. Projekttitel 30. Juni 2017 BE AGILE

8. Projekttitel 30. Juni 2017 Kapitel • Setup agile process • Deﬁne release cycles • Scope releases • Involve client early • Also possible for classical projects with ﬁxed deadline and budget Be agile

9. Projekttitel 30. Juni 2017 DESIGN FOR CHANGE?

10. Projekttitel 30. Juni 2017 Kapitel Don‘t • Premature optimization based on assumptions Do • Split up and modularize Design for change?

11. Projekttitel 30. Juni 2017 BE MODULAR

12. Projekttitel 30. Juni 2017 Kapitel On application level • Identify subject areas and functional components that could be replaceable • No monolith — implement identiﬁed components independent from each other (nearly) • Think Microservices and DDD On code level • Loose coupling • Interfaces • Think SOLID design principles Be modular

13. Projekttitel 30. Juni 2017 Kapitel What about dependencies? • Build contracts • JSON Schema • XML Schema • Interfaces • DTOs / Transfer objects

14. Projekttitel 30. Juni 2017 BE INCREMENTAL

15. Projekttitel 30. Juni 2017 Kapitel • Do not head for the best solution that would ﬁt all possible future problems you are going to expect • Head for the best solution you can come up for your current problem • Adapt and extend only when needed • Evolving order principle / less is more • Do Spikes if you are unsure about some implementation approach Be incremental

16. Projekttitel 30. Juni 2017 TEST ALL THE THINGS

17. Projekttitel 30. Juni 2017 Kapitel • Tests are the key to ﬂexible and robust Software • Increase the maturity in your Software • Enables possibility to change things • Add layer of security • Also for legacy code • Try to practice Test Driven Development Test all the things

18. Projekttitel 30. Juni 2017 BUILD PIPELINE

19. Projekttitel 30. Juni 2017 Kapitel • Enables regular automated testing • Provides metrics on code quality • Continuous integration • Increases software quality Build Pipeline

20. Projekttitel 30. Juni 2017 GREAT POSSIBILITIES

21. Projekttitel 30. Juni 2017 Kapitel • Experience of more than 5 decades of software development available in books, papers, talks etc. • Exciting technologies and tools (VMs, Containers, Frameworks) only recently • Now starts the time to write good software Great possibilities

22. Projekttitel 30. Juni 2017 SUMMARY

23. Projekttitel 30. Juni 2017 Kapitel • Requirements change constantly • It needs an agile process to deal with that • We need to follow a modular approach to software • Tests enable change • No tests without a pipeline • So many possibilities — No excuses anymore Summary

24. Projekttitel 30. Juni 2017 MUITO OBRIGADO

25. Turbine Kreuzberg GmbH Ohlauer Straße 43 10999 Berlin MUITO OBRIGADO Contact matthias.gronwald@turbinekreuzberg.com Book recommendations • Clean Code by Robert „Uncle Bob“ C. Martin • Code Complete: A Practical Handbook of Software Construction by Steve McDonnell • The Pragmatic Programmer by Andrew Hunt, David Thomas and Ward Cunningham

Brilliant Software Architecture or How to Build Good Software

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Similar to Brilliant Software Architecture or How to Build Good Software

Similar to Brilliant Software Architecture or How to Build Good Software (20)

Recently uploaded

Recently uploaded (20)

Brilliant Software Architecture or How to Build Good Software