Introduction to Pattern-Driven Software Problem Solving

•

0 likes•127 views

The slides from Software Diagnostics Services (former Memory Dump Analysis Services) seminar (25th of March, 2011) on pattern-driven software troubleshooting, debugging, and maintenance. Topics include: A Short History of DumpAnalysis.org; Memory Dump Analysis Patterns; Troubleshooting and Debugging Tools (Debugware) Patterns; Software Trace Analysis Patterns; From Software Defects to Software Behavior; Workaround Patterns; Structural Memory Patterns; Memory Analysis Domain Pattern Hierarchy; New Directions.

Software

Agenda (Summary)
 A Short History
 Basic Definitions
 Pattern Categories
 Future Research Directions
© 2011 Memory Dump Analysis Services

DumpAnalysis.org*
5 Years!
* Now Includes: TraceAnalysis.org, www.ForensicAnalysis.org, and Victimware.org
© 2011 Memory Dump Analysis Services

Agenda (Basic Definitions)
 Software Problems
 Software Patterns
 DA+TA
 Pattern Hybridization
© 2011 Memory Dump Analysis Services

Software Problems
 Construction: Requirements, Architecture, Design,
and Implementation
 Post-Construction: Maintenance and Support
© 2011 Memory Dump Analysis Services
Post-construction problem: any observed deviations in
structure and behavior between modeling expectations
and the actual built system.*
* What is a Software Defect?

Software Patterns
 Construction: Requirements, Architecture, Design,
and Implementation
 Post-Construction: Maintenance and Support
© 2011 Memory Dump Analysis Services
Pattern: a common recurrent identifiable problem
together with a set of recommendations and possible
solutions to apply in a specific context

DA+TA
 DA: Dump Artifact / Dump Analysis
Memory snapshots: process, kernel, physical memory dumps
 TA: Trace Artifact / Trace Analysis
Software traces: Event Tracing for Windows, logs
© 2011 Memory Dump Analysis Services

Pattern Hybridization
A bit of Chemistry: Carbon SP3 orbital hybridization
© 2011 Memory Dump Analysis Services
System
+
Environment
DA+TA
Artifacts
DA+TA
Patterns
Debugware
Construction
Patterns
SP3
Software Patterns
3
Software Patterns3
- Structural
- Behavioral
- Debugware
- Debugging

Agenda (Pattern Categories)
 Software Behavior
 Debugware Tools
 Problem Workaround
 Unified Debugging
© 2011 Memory Dump Analysis Services

Software Behavior
 Memory dump and software trace
 Examples: Spiking Thread, Discontinuity
 +200 patterns (DA+TA)
 DumpAnalysis.org
© 2011 Memory Dump Analysis Services

DA: Software Behavior
 Memory dump: a memory snapshot
 Definition, partial classification and
historical list
 Pattern identification case studies
© 2011 Memory Dump Analysis Services

TA: Software Behavior
“Imagine you got a software trace from hundreds of modules
you haven’t written or haven’t seen source code of...”
 Software trace: a sequence of memory
fragments ordered in time
 Definition, and historical list
 Pattern identification case studies
© 2011 Memory Dump Analysis Services

Debugware Tools
 Troubleshooting and Debugging
 Example: Troubleshooting Unit of Work
 13 patterns, case study
 DumpAnalysis.org
© 2011 Memory Dump Analysis Services

Problem Workaround
 Troubleshooting when debugging is not
an option
 Example: Frozen Process
 Patterns
 DumpAnalysis.org
© 2011 Memory Dump Analysis Services

Unified Debugging
 Systematic Pattern Language
 Example:
Analysis Patterns Shared Buffer Overwrite
Architectural Patterns Debug Event Subscription / Notification
Design Patterns Punctuated Execution
Implementation Patterns Breakpoint (software and hardware)
Usage Patterns Kernel vs. user space breakpoints
© 2011 Memory Dump Analysis Services

Agenda (Future Directions)
 Structural Memory Patterns
 Unified Debugging Pattern Language
 Domain Pattern Hierarchy
 Periodic Table of Software Defects
© 2011 Memory Dump Analysis Services

Structural Memory Patterns
 Examples: Memory Region and Region Boundary
 DumpAnalysis.org
© 2011 Memory Dump Analysis Services

Domain Pattern Hierarchy
Repeated patterns through the layers of software
© 2011 Memory Dump Analysis Services

Resources
 DumpAnalysis.org
 Pattern-Driven Memory Dump Analysis
 Memory Dump and Trace Analysis: A Unified Pattern Approach
 Advanced Software Debugging Reference:
Vol 6
November,
2011
© 2011 Memory Dump Analysis Services
Vol 5
April,
2011

Q&A
Please send your feedback using the contact
form on DumpAnalysis.com
© 2011 Memory Dump Analysis Services

Thank you for attendance!
© 2011 Memory Dump Analysis Services
Join DA+TA Facebook Group

The slides from Software Diagnostics Services (former Memory Dump Analysis Services) lecture at E2EVC Virtualization Conference (13th of May, 2011) that introduced an analysis methodology for software execution artifacts. Topics include: A.C.P. Root Cause Analysis; DA+TA; Spatiality vs. Narrativity; Tools for Artifact Analysis; Checklists for Analysis; Software Behavior Patterns; Adjoint Threads; Selected Trace and Log Analysis Patterns; Trace Analysis Case Study.

Log Engineering: Towards Systematic Log Mining to Support the Development of ...

SAIL_QU

Log Engineering: Towards Systematic Log Mining to Support the Development of ...

SAIL_QU

Pattern-Based Software Diagnostics

Dmitry Vostokov

The slides from Software Diagnostics Services seminar (14th of January, 2013) about how pattern-based software diagnostics, troubleshooting, and debugging address software post-construction problem solving pattern life cycle: from the discovery of a new pattern through its integration into an existing pattern catalogue and pattern language, testing, packaging and delivering to pattern consumers with subsequent usage, refactoring and writing case studies. Topics include: Definitions of Software Diagnostics, Diagnostics Pattern, Pattern Orientation, Pattern Cloud, Pattern Catalogs, Pattern Catalog Classification, Pattern Catalog Partition, Pattern Implementation, Pattern Forms, Pattern Networks, The Relationship between Software Construction Patterns and Software Diagnostics Patterns, Pattern Sequences, Pattern-Driven vs. Pattern-Based, Pattern Catalog Evolution, Pattern Packaging and Delivery, Economic Benefits of Pattern-Oriented Software Diagnostics.

Software Analytics - Achievements and Challenges

Tao Xie

ICS UserGroup - 2015 - Infrastructure Assessment - Analyze, Visualize and Opt...Christoph Adler

CHAPTER 1: Creating a Program OBJECTIVES · Analyze some of the issues involved in producing a simple program: · Requirements (functional, nonfunctional) · Design constraints and design decisions · Testing · Effort estimation · Implementation details · Understand the activities involved in writing even a simple program. · Preview many additional software engineering topics found in the later chapters. 1.1 A Simple Problem In this chapter we will analyze the tasks involved in writing a relatively simple program. This will serve as a contrast to what is involved in developing a large system, which is described in Chapter 2. Assume that you have been given the following simple problem: “Given a collection of lines of text (strings) stored in a file, sort them in alphabetical order, and write them to another file.” This is probably one of the simplest problems you will be involved with. You have probably done similar assignments for some of your introduction to programming classes. 1.1.1 Decisions, Decisions A problem statement such as the one mentioned in the above simple problem does not completely specify the problem. You need to clarify the requirements in order to produce a program that better satisfies the real problem. You need to understand all the program requirements and the design constraints imposed by the client on the design, and you need to make important technical decisions. A complete problem statement would include the requirements, which state and qualify what the program does, and the design constraints, which depict the ways in which you can design and implement it. Program requirements Statements that define and qualify what the program needs to do. Design constraints Statements that constrain the ways in which the software can be designed and implemented. The most important thing to realize is that the word requirements is not used as it is in colloquial English. In many business transactions, a requirement is something that absolutely must happen. However, in software engineering many items are negotiable. Given that every requirement will have a cost, the clients may decide that they do not really need it after they understand the related cost. Requirements are often grouped into those that are “needed” and those that are “nice to have.” It is also useful to distinguish between functional requirements—what the program does—and nonfunctional requirements—the manner in which the program must behave. In a way, a function is similar to that of a direct and indirect object in grammar. Thus the functional requirements for our problem will describe what it does: sort a file (with all the detail required); the nonfunctional requirements will describe items such as performance, usability, and maintainability. Functional requirements tend to have a Boolean measurement where the requirement is either satisfied or not satisfied, but nonfunctional requirements tend to apply to things measured on a linear scale where the measurements ca.

Datamingse

Ryan Wang

Cnpm bkdnAnkit yadav

Software Requirement Patterns (SRP)

GESSI UPC

There are many approaches to reuse in software engineering. Among them, patterns hold a prominent position. "Each pattern describes a problem which occurs over and over again in our environment, and then describes the core of the solution to that problem, in such a way that you can use this solution a million times over, without ever doing it the same way twice" (Alexander, 1979). We are interested in the use of patterns for the requirements analysis stage, namely Software Requirement Patterns. The patterns applicability to this context is clear, since requirements that appear over and over in requirements books could be identified as the solution to particular problems in a given context (the classical context-problem-solution scenario of patterns). Presentation of Software Requirement Patterns in the PABRE framework.

An Introduction of Big data; Big data for beginners; Overview of Big Data; Bi...

SpringPeople

Developing an Enterprise Architecture Capability

Anthony Draffin

Pattern-Oriented Memory Forensics

Dmitry Vostokov

This lecture introduces a pattern language for memory forensics - investigation of past software behaviour in memory snapshots. It provides a unified language for discussing and communicating detection and analysis results despite the proliferation of operating systems and tools, a base language for checklists, and an aid in accelerated learning. The lecture has a short theoretical part and then illustrates various patterns seen in crash dumps by using WinDbg debugger.

Software engineering lecture notesAmmar Shafiq

Software Theory Presentationalexmurch

Software engineering lecture notes

Garima Singh

Reference Architecture

Johan Eltes

HOW TO DOWNLOAD MICROSOFT WORD IN ANDROID, and How to convert doc file into ...

TEJVEER SINGH

Notes on software engineering

Ertan Deniz

Pattern-Driven Software Diagnostics: An Introduction

Dmitry Vostokov

The slides from Software Diagnostics Services seminar (25th of June, 2012) about different pattern categories for effective and efficient abnormal software behavior diagnostics: the foundation of scalable and cost-effective pattern-driven software support. Topics include: Diagnostics, Symptoms and Signs, Pattern Groupings, Problem Solving Patterns, Diagnostics Process, Artifact Checklists and Baselines, Pattern Language and Catalogs, Meta-patterns, Pattern Isomorphism, Performance Monitoring and Best Practices, Certification and Diagnostics Audit, Human Side of Software Diagnostics, Automation of Software Diagnostics, Systems and Software Diagnostics, Extending Software Diagnostics to Malware and Victimware Analysis.

ConnectED 2015 BP302: Future-Proofing Enterprise IT

Daniel Reimann

Virtualization, cloud, optimization, migration – Everyone’s talking about the next thing in enterprise IT, but clear answers on direction aren’t readily available and mistakes are costly. Let us show you how to understand the demands and usage patterns across your enterprise in order to make smart strategic decisions that help you manage IT while keeping cost in check. Analyze and visualize what in your IBM ICS Infrastructure is actually used, by whom and where those people are geographically. Learn about security risks, application design complexity and webification readiness without getting (any more) grey hair.

Frequently Used Off Host Developer Toolsl

Sharan S

Towards Reusable Research Software

dgarijo

An increasing number of researchers rely on computational methods to generate the results described in their publications. Research software created to this end is heterogeneous (e.g., scripts, libraries, packages, notebooks, etc.) and usually difficult to find, reuse, compare and understand due to its disconnected documentation (dispersed in manuals, readme files, web sites, and code comments) and a lack of structured metadata to describe it. In this talk I will describe the main challenges for finding, comparing and reusing research software, how structured metadata can help to address some of them, which are the best practices being proposed by the community; and current initiatives to aid their adoption by researchers within EOSC. Impact: The talk addresses an important aspect of the EOSC infrastructure for quality research software by ensuring that software contributed to the EOSC ecosystem can be found, compared and reused by researchers. The talk also aims to address metadata quality of current research products, which is critical for successful adoption. Presented at the EOSC symposium

Accelerated Windows Debugging 3 training public slides

Dmitry Vostokov

The slides from Software Diagnostics Services Accelerated Windows Debugging 3 training. The training description: "The full transcript of Software Diagnostics Services training with 14 step-by-step exercises, notes, and source code of specially created modeling applications. Learn live local and remote debugging techniques in kernel, user process and managed .NET spaces using WinDbg debugger. The unique and innovative course teaches unified debugging patterns applied to real problems from complex software environments. The second edition was fully reworked and updated to use the latest WinDbg version and Windows 10."

Accelerated .NET Memory Dump Analysis training public slides

Dmitry Vostokov

The slides from Software Diagnostics Services .NET memory dump analysis training. The training description: "Covers 22 .NET memory dump analysis patterns plus additional 11 unmanaged patterns. Learn how to analyze CLR 4 .NET application and service crashes and freezes, navigate through memory dump space (managed and unmanaged code) and diagnose corruption, leaks, CPU spikes, blocked threads, deadlocks, wait chains, resource contention, and much more. The training consists of practical step-by-step exercises using Microsoft WinDbg debugger to diagnose patterns in 64-bit and 32-bit process memory dumps. The training uses a unique and innovative pattern-oriented analysis approach to speed up the learning curve. The third edition was fully reworked to use the latest WinDbg version and Windows 10. It also includes 9 optional legacy exercises from the previous editions covering CLR 2 and 4, Windows Vista and Windows 7. Prerequisites: Basic .NET programming and debugging. Audience: Software technical support and escalation engineers, system administrators, DevOps, performance and reliability engineers, software developers and quality assurance engineers."

Navigating the Metaverse: A Journey into Virtual Evolution"

Donna Lenk

Developing Distributed High-performance Computing Capabilities of an Open Sci...

Globus

COVID-19 had an unprecedented impact on scientific collaboration. The pandemic and its broad response from the scientific community has forged new relationships among public health practitioners, mathematical modelers, and scientific computing specialists, while revealing critical gaps in exploiting advanced computing systems to support urgent decision making. Informed by our team’s work in applying high-performance computing in support of public health decision makers during the COVID-19 pandemic, we present how Globus technologies are enabling the development of an open science platform for robust epidemic analysis, with the goal of collaborative, secure, distributed, on-demand, and fast time-to-solution analyses to support public health.

Prosigns: Transforming Business with Tailored Technology Solutions

Prosigns

Unlocking Business Potential: Tailored Technology Solutions by Prosigns Discover how Prosigns, a leading technology solutions provider, partners with businesses to drive innovation and success. Our presentation showcases our comprehensive range of services, including custom software development, web and mobile app development, AI & ML solutions, blockchain integration, DevOps services, and Microsoft Dynamics 365 support. Custom Software Development: Prosigns specializes in creating bespoke software solutions that cater to your unique business needs. Our team of experts works closely with you to understand your requirements and deliver tailor-made software that enhances efficiency and drives growth. Web and Mobile App Development: From responsive websites to intuitive mobile applications, Prosigns develops cutting-edge solutions that engage users and deliver seamless experiences across devices. AI & ML Solutions: Harnessing the power of Artificial Intelligence and Machine Learning, Prosigns provides smart solutions that automate processes, provide valuable insights, and drive informed decision-making. Blockchain Integration: Prosigns offers comprehensive blockchain solutions, including development, integration, and consulting services, enabling businesses to leverage blockchain technology for enhanced security, transparency, and efficiency. DevOps Services: Prosigns' DevOps services streamline development and operations processes, ensuring faster and more reliable software delivery through automation and continuous integration. Microsoft Dynamics 365 Support: Prosigns provides comprehensive support and maintenance services for Microsoft Dynamics 365, ensuring your system is always up-to-date, secure, and running smoothly. Learn how our collaborative approach and dedication to excellence help businesses achieve their goals and stay ahead in today's digital landscape. From concept to deployment, Prosigns is your trusted partner for transforming ideas into reality and unlocking the full potential of your business. Join us on a journey of innovation and growth. Let's partner for success with Prosigns.

How to Position Your Globus Data Portal for Success Ten Good Practices

Globus

Science gateways allow science and engineering communities to access shared data, software, computing services, and instruments. Science gateways have gained a lot of traction in the last twenty years, as evidenced by projects such as the Science Gateways Community Institute (SGCI) and the Center of Excellence on Science Gateways (SGX3) in the US, The Australian Research Data Commons (ARDC) and its platforms in Australia, and the projects around Virtual Research Environments in Europe. A few mature frameworks have evolved with their different strengths and foci and have been taken up by a larger community such as the Globus Data Portal, Hubzero, Tapis, and Galaxy. However, even when gateways are built on successful frameworks, they continue to face the challenges of ongoing maintenance costs and how to meet the ever-expanding needs of the community they serve with enhanced features. It is not uncommon that gateways with compelling use cases are nonetheless unable to get past the prototype phase and become a full production service, or if they do, they don't survive more than a couple of years. While there is no guaranteed pathway to success, it seems likely that for any gateway there is a need for a strong community and/or solid funding streams to create and sustain its success. With over twenty years of examples to draw from, this presentation goes into detail for ten factors common to successful and enduring gateways that effectively serve as best practices for any new or developing gateway.

Large Language Models and the End of Programming

Matt Welsh

Orion Context Broker introduction 20240604

Fermin Galan

Introduction to Pygame (Lecture 7 Python Game Development)

abdulrafaychaudhry

Recently uploaded (20)

2024 RoOUG Security model for the cloud.pptx

Enterprise Software Development with No Code Solutions.pptx

GraphSummit Paris - The art of the possible with Graph Technology

Understanding Globus Data Transfers with NetSage

BoxLang: Review our Visionary Licenses of 2024

Pro Unity Game Development with C-sharp Book

Cracking the code review at SpringIO 2024

Utilocate provides Smarter, Better, Faster, Safer Locate Ticket Management

Lecture 1 Introduction to games development

Dominate Social Media with TubeTrivia AI’s Addictive Quiz Videos.pdf

A Sighting of filterA in Typelevel Rite of Passage

Cyaniclab : Software Development Agency Portfolio.pdf

Custom Healthcare Software for Managing Chronic Conditions and Remote Patient...

Navigating the Metaverse: A Journey into Virtual Evolution"

Developing Distributed High-performance Computing Capabilities of an Open Sci...

Prosigns: Transforming Business with Tailored Technology Solutions

How to Position Your Globus Data Portal for Success Ten Good Practices

Large Language Models and the End of Programming

Orion Context Broker introduction 20240604

Introduction to Pygame (Lecture 7 Python Game Development)

Introduction to Pattern-Driven Software Problem Solving

1. Pattern-Driven Software Problem Solving Presenter: Dmitry Vostokov Memory Dump Analysis Services

6. Software Problems  Construction: Requirements, Architecture, Design, and Implementation  Post-Construction: Maintenance and Support © 2011 Memory Dump Analysis Services Post-construction problem: any observed deviations in structure and behavior between modeling expectations and the actual built system.* * What is a Software Defect?

7. Software Patterns  Construction: Requirements, Architecture, Design, and Implementation  Post-Construction: Maintenance and Support © 2011 Memory Dump Analysis Services Pattern: a common recurrent identifiable problem together with a set of recommendations and possible solutions to apply in a specific context

8. DA+TA  DA: Dump Artifact / Dump Analysis Memory snapshots: process, kernel, physical memory dumps  TA: Trace Artifact / Trace Analysis Software traces: Event Tracing for Windows, logs © 2011 Memory Dump Analysis Services

9. Pattern Hybridization A bit of Chemistry: Carbon SP3 orbital hybridization © 2011 Memory Dump Analysis Services System + Environment DA+TA Artifacts DA+TA Patterns Debugware Construction Patterns SP3 Software Patterns 3 Software Patterns3 - Structural - Behavioral - Debugware - Debugging

13. TA: Software Behavior “Imagine you got a software trace from hundreds of modules you haven’t written or haven’t seen source code of...”  Software trace: a sequence of memory fragments ordered in time  Definition, and historical list  Pattern identification case studies © 2011 Memory Dump Analysis Services

16. Unified Debugging  Systematic Pattern Language  Example: Analysis Patterns Shared Buffer Overwrite Architectural Patterns Debug Event Subscription / Notification Design Patterns Punctuated Execution Implementation Patterns Breakpoint (software and hardware) Usage Patterns Kernel vs. user space breakpoints © 2011 Memory Dump Analysis Services

20. Resources  DumpAnalysis.org  Pattern-Driven Memory Dump Analysis  Memory Dump and Trace Analysis: A Unified Pattern Approach  Advanced Software Debugging Reference: Vol 6 November, 2011 © 2011 Memory Dump Analysis Services Vol 5 April, 2011

Introduction to Pattern-Driven Software Problem Solving

Recommended

Recommended

More Related Content

Similar to Introduction to Pattern-Driven Software Problem Solving

Similar to Introduction to Pattern-Driven Software Problem Solving (20)

More from Dmitry Vostokov

More from Dmitry Vostokov (20)

Recently uploaded

Recently uploaded (20)

Introduction to Pattern-Driven Software Problem Solving