The document discusses the evolution of software application development, highlighting the transformation from traditional coding methods to visual modeling tools like low-code and no-code solutions. It emphasizes the need for standards in digital process automation, specifically BPMN 2.0, CMMN, and DMN for different types of use cases. The text also notes the impact of recent dynamics on accelerating business agility and the emergence of a new breed of developers focused on business needs.

1. NextGeneration
AppDevelopment
An Introduction

2. Evolution of Software
App Development
How application building is transforming
2

3. The Usual Method
3

4. The Usual Method
4
Development Test Pre-Production Production
Developers
Develop and unit tests using
traditional coding
Testers
Validate functionality
using traditional testing
ApplicationOwners
Monitor release cycles,
and authorize releases
Consumers
Use applications
Requirements
BusinessAnalyst
Analyze and document
requirements

5. The Modelling Method
5

6. The Modelling Method
6
Model Simulate &Test Production
Developers
Models and builds
applications
Consumers
Use applications
 Faster
 Less errors (defects)
 Easier to make changes
 Self documented
 Easier to maintain

7. Rise of Visual Modelling Tools
7
High Code Low Code No Code
 Model Ui and Data Structures
 Code the logic
 Model Ui and Data Structures
 Use out of the box solutions
 Customize
 Model Business Processes
 Model Ui and Data Structures
 Use instantly

8. A Crowded Space!
8

9. Digital Process Automation
Standards and Gaining Maturity
9

10. Need for Standards
 BPMN 2.0 - A well-defined modelling notation
 Object Management Group (OMG) – The standards body
10

11. Modelling Business Use Cases
Nature of use cases are different – Need different notations!
 BPMN — is about the processing
 CMMN — is about managing
 DMN — is about deciding
Complex use cases might require multiple notations to model
11

12. BPMN – Business Process Model & Notation
12
Suitable for modelling structured, predefined flow-oriented use cases

13. CMMN
Case Management
Model & Notation
13
Suitable for modelling unstructured, event driven use
cases where knowledge workers are aware of domain
knowledge and handle the process.

14. DMN – Decision Model & Notation
14
Suitable for precise specification of business decisions and rules
Inputs Outputs

15. Developing Applications
15
Modelling App Generation &
Simulation
App Use

16. Why Should We Care?
 Post Pandemic Dynamics — More automation, faster
 Business Agility – Need changes in days than months!
 Limitations of Traditional Development — Does not scale!
 New Breed of Developers — More business focused
16