Scott Hebbard Scott Hebbard Communicatjons Manager at Sparx Systems - - PowerPoint PPT Presentation

▶
scott hebbard scott hebbard
SMART_READER_LITE
LIVE PREVIEW

Scott Hebbard Scott Hebbard Communicatjons Manager at Sparx Systems - - PowerPoint PPT Presentation

Oct 12, 2023 308 likes •848 views

Scott Hebbard Scott Hebbard Communicatjons Manager at Sparx Systems Over 2 decades of experience in computjng and modeling Sparx Systems Sparx Systems Enterprise Architect: Commercially released in 2000 Based in Creswick, near

slide-1
SLIDE 1
slide-2
SLIDE 2

Scott Hebbard Scott Hebbard

  • Communicatjons Manager at Sparx Systems
  • Over 2 decades of experience in computjng and modeling
slide-3
SLIDE 3

Sparx Systems Sparx Systems

  • Enterprise Architect:
  • Commercially released in 2000
  • Based in Creswick, near Melbourne, Victoria, Australia
  • 850,000+ paid users world wide
  • Designing and specifying ‘complex’ systems
  • Customers in all industries including Aerospace, Aviatjon,

Retail Banking, Finance, Insurance, Healthcare, Government, Military, Utjlitjes, Auto, Geospatjal and much more

slide-4
SLIDE 4

Agenda Agenda

  • Discuss the Business Value of Modeling
  • Reasons for implementing tooling
  • Demonstration of the benefjts using Enterprise

Architect

  • Questions and summary
slide-5
SLIDE 5

The Problem The Problem

  • Offjce tools are ubiquitous – not suited for all tasks
  • Spreadsheets are not suitable for requirements
  • Drawing tools are not designed for enterprise

architecture

  • Written reports and diagrams are static with no

traceability

  • As organizations mature and grow, a more

comprehensive approach is required that scales

slide-6
SLIDE 6

Benefjts of Modeling Benefjts of Modeling

  • Gain insight into an organization or system
  • Understand the impact of change
  • Reduce and mitigate risk
  • Reduce Complexity
  • Improve Process
  • Transformation
slide-7
SLIDE 7

Benefjts of Modeling Benefjts of Modeling

  • Gain insight into an organization or system
  • Understand the impact of change
  • Reduce and mitigate risk
  • Reduce Complexity
  • Improve Process
  • Transformation
slide-8
SLIDE 8

Benefjts of Modeling Benefjts of Modeling

  • Gain insight into an organization or system
  • Understand the impact of change
  • Reduce and mitigate risk
  • Reduce Complexity
  • Improve Process
  • Transformation
slide-9
SLIDE 9

Benefjts of Modeling Benefjts of Modeling

  • Reuse
  • Traceability
  • Improves productivity
  • Understand the business
  • Make better decisions
  • Retain knowledge
slide-10
SLIDE 10

Benefjts of Modeling Benefjts of Modeling

  • Captures an understanding of the system
  • Great for training or on-boarding of new stafg
  • Improves documentation
  • Helps to decompose complex systems into meaningful chunks
  • Improve maintenance
  • Reduce defects
slide-11
SLIDE 11

Communicate with Communicate with Stakeholders Stakeholders

  • Clear and Concise
  • Models are easy to understand
  • Explore connectjons
  • Provide relevant informatjon
  • Easily accessible from any device
  • Up to date
slide-12
SLIDE 12

Problems with Offjce T

  • ols

Problems with Offjce T

  • ols
  • Out of date the moment they are published
  • Hard to distribute
  • Static
  • No feedback
  • Hard to reuse without editing
slide-13
SLIDE 13

Drawing vs Modeling Drawing vs Modeling

  • Drawing is static and confjned to a single diagram
  • Any change requires a new diagram
  • Content becomes out of date
  • Diffjcult to maintain
  • Hard to scale
slide-14
SLIDE 14

What Enterprise Architect Ofgers What Enterprise Architect Ofgers

  • Manage and gather requirements
  • Model software and systems
  • Model and analyze business

processes

  • Build design and behavioral models
slide-15
SLIDE 15

What Enterprise Architect Ofgers What Enterprise Architect Ofgers

  • Collaboration and team development
  • Traceability from requirements through to deployment
  • Model any system from a web application to embedded

system

  • Extensive project management support
  • T

est management and code engineering

slide-16
SLIDE 16

Requirements - Gathering Requirements - Gathering

  • Offmine means:
  • White Boards
  • Post IT Notes / Napkins / Notepads
  • Sofuware Based:
  • Word / Excel
  • Visio / Jira
  • Sparx Systems Enterprise Architect
slide-17
SLIDE 17

Requirements – Whiteboards Requirements – Whiteboards

slide-18
SLIDE 18

Requirements – Whiteboard @6pm Requirements – Whiteboard @6pm

slide-19
SLIDE 19

Post IT Notes and Napkins Post IT Notes and Napkins

slide-20
SLIDE 20

Post IT Notes – Advanced Mode Post IT Notes – Advanced Mode

slide-21
SLIDE 21

Right T

  • ol for the T

ask at Hand Right T

  • ol for the T

ask at Hand

  • Allow you to work as you always have done
  • Will allow you to create understandable specifjcatjons
  • Empower you to drive down steam actjvitjes
  • Make subsequent projects faster
  • Retain a history of decisions and implementatjons
slide-22
SLIDE 22

Build Requirements Build Requirements

slide-23
SLIDE 23

Convert to a Digital Approach Convert to a Digital Approach

slide-24
SLIDE 24

Work Like You Always Have Work Like You Always Have

slide-25
SLIDE 25

Structured Scenarios Structured Scenarios

  • Text to structure
  • Structure to model
  • Structure to tests
slide-26
SLIDE 26

Structured Scenarios Structured Scenarios

  • Automatjcally create structured data out of existjng

requirements/use cases/user stories

slide-27
SLIDE 27

Structured Scenarios Structured Scenarios

  • Create Diagrams, Tests, Sequence Diagrams and more
slide-28
SLIDE 28

Structured Scenarios Structured Scenarios Activity Diagrams Activity Diagrams

  • Easier to follow
  • Identjfy any erroneous

steps

  • Looks nice in a report
  • No extra efgort needed
slide-29
SLIDE 29

Structured Scenarios Structured Scenarios Basic Simulation Basic Simulation

  • Visually follow the

process

  • Identjfy any botulenecks
  • Repeatable
  • Ensure the process can

fjnish

  • No endless loops
slide-30
SLIDE 30

Structured Scenarios Structured Scenarios T est Sets T est Sets

  • Automatjcally create

the steps needed to test all aspects of the process.

  • Start of Test Driven

Design

slide-31
SLIDE 31

Structured Scenarios Structured Scenarios Sequence Diagrams Sequence Diagrams

  • Start identjfying the actors of a system
  • How to interact with a system
  • Capture the interactjon between objects

in the context of a collaboratjon.

slide-32
SLIDE 32

Structured Scenarios Structured Scenarios Gantt Chart Gantt Chart

  • Role dependent custom views
  • (Gantu, Excel, Document, Model etc.)
  • Assign resources to steps – Project Planning
slide-33
SLIDE 33

Using This Model Using This Model

  • Empower down stream actjvitjes
  • Traceability
  • Impact analysis
  • Create accurate changes
  • Gain insights
  • Model driven development
slide-34
SLIDE 34

Traceability in Diagrams Traceability in Diagrams

  • Can be hand crafued
  • Automatjc

connectors for related elements

slide-35
SLIDE 35

Traceability View Traceability View

  • Can be dynamic
  • Easy to drill down
  • Follow a path from strategy to

implementatjon

  • Context sensitjve
slide-36
SLIDE 36

Traceability for True Impact Traceability for True Impact Analysis Analysis

  • Automatjc
  • Can identjfy unforeseen

relatjonships

  • Hard to reach this insight

with a whiteboard

slide-37
SLIDE 37

Reuse Reuse

  • Never create the same requirement twice
  • Build up a library
slide-38
SLIDE 38

Retain Knowledge Retain Knowledge

  • Specifjcatjons come out of dusty draws
  • Maintainable for years
  • Doesn’t require a “knowledge silo” to

remember the decisions made 10 years earlier

slide-39
SLIDE 39

Communication Communication

  • Web based dashboards
  • Curated views
  • Easily consumable
  • Socialize your business
  • Provides real tjme analysis of the

current model

slide-40
SLIDE 40

Decisions - DMN Decisions - DMN

  • Decision Model and Notatjon (DMN) is intended to provide

a bridge between business process models and decision logic models

  • Build, edit and execute a Decision Table
  • Bridges Business and IT
  • Puts the power in your hands
  • Validate rule models to fjnd and eliminate logical errors
slide-41
SLIDE 41

Decision Model and Notation Decision Model and Notation

  • Easy to use interface that both

business and IT can use

  • Spread Sheet look and feel
  • Easy to modify programming

logic

  • Generate source code directly

to your solutjon.

  • The basis for AI
slide-42
SLIDE 42

Model Complex Decisions Model Complex Decisions

slide-43
SLIDE 43

DMN – Code Generation DMN – Code Generation

slide-44
SLIDE 44

DMN Generation DMN Generation

  • Generate to a number of difgerent

languages

  • Use tree structure to develop extremely

complex decisions

  • Can test the decisions in the tool
  • Rapidly change logic without editjng code
  • Integrates seamlessly to simulate

business processes and logic

slide-45
SLIDE 45

Simulation - BPSim Simulation - BPSim

  • Comprehensive simulatjon of processes
  • Integrates in with BPMN
  • Run and store results from multjple simulatjons
  • Betuer understand your process
slide-46
SLIDE 46

Simulation - BPSim Simulation - BPSim

  • Comprehensive simulatjon of processes
slide-47
SLIDE 47

Simulation - BPSim Simulation - BPSim

  • Step through simulatjon events
  • Know how the simulatjon ran at any point
slide-48
SLIDE 48

Simulation - BPSim Simulation - BPSim

  • Multjple simulatjon confjguratjons outside the process
  • Able to ask “What if” questjons
slide-49
SLIDE 49

Simulation - BPSim Simulation - BPSim

  • Use charts and graphs to display the results
slide-50
SLIDE 50

Sharing Models Sharing Models

slide-51
SLIDE 51

Documents T emplates Documents T emplates

slide-52
SLIDE 52

BABOK Reference Guide BABOK Reference Guide

  • Freely available
  • htup://babok.sparxpublic.com/index.php
  • Access Code: babok.model
slide-53
SLIDE 53

BABOK Reference Guide BABOK Reference Guide

  • Modeling Optjons
  • Diagrams and Tools list
  • Fleshed out examples
  • Access to help