Normal Business Application Software BAS provides ONLY the business functionality, which is good enough if it works well. However that is never the case particularly for the new functionality offered for the first time. Invariably unforeseen business and software situations arise and the the BAS needs modifications often at design level of the business logic and or the BAS itself. All this has to be done off line. Here it is proposed that both Business Support and Software Development Support be brought ONLINE. Here the Application Software itself becomes AGILE in operation---NOT just the software development process. This is facilitated by two radical design changes. First, the BAS it self is restructured and designed to bring Business Authority ONLINE and set up a Business Policy and Rules Repository BPRR. Second, an additional Framework for Online Software Evolution is provided to bring the BAS Developers and the software development system online. See how the combination works in this and two supplementary PPTs.

1. BizApp with Online Evolution Support
Putcha V. Narasimham
putchavn@yahoo.com
New Version
01AUG22
1
©2022 All rights are reserved by Putcha V Narasimham

2. Errors in Business Application Software/Biz App
 BAS runs on a Platform (not shown)
 BAS may malfunction for many reasons
 Two main reasons:
 Errors in Business Policies and Rules
 Errors in the software of BAS
 BPMN 2.0 introduced a new process
element “Conversation” or “Dialog”
 It is used in UseCase / Process diagrams
CONFIDENTIAL
2
Business
Application
Software
BAS
with Platform
See Glossary
from slide 21

3. New Process Element: Dialog or
Conversation
 Dialog is a sequence of messages
between one entity and another
 It has a name and goal
 Dialog is a high level expressive
process modelling element
 UML UseCase is actually a dialog; a
service dialog; this is not recognized
Entity X
Entity 2
CONFIDENTIAL
3
N
Dialog
Entity 1
equivalent
Conversation
of BPMN 2.0

4. UseCase Diagram:
Business Application Software (ASIS)
 Currently BAS delivers named business
services to Business Actor classes
 No online means for error reporting,
correcting and upgrading BAS
 Only one service dialog per actor is
shown; many are possible
CONFIDENTIAL
4
BAS
with
Platform
Actor 2
Actor N
Actor 1
N
Service Dialog
2
1
See Glossary and slide notes
below for more explanation
Explanation

5. What a user needs from BAS
in addition to business services--1
 To report any issue with the app ONLINE,
 Irrespective of the type of issue---without
screen shots and attachments
 No running from pillar to post OFFLINE
5
Business
Application
Software
BAS
1
Business
Services

6. What a user needs from BAS
in addition to business services--2
 To get quick ONLINE ack and resolution of
the issue
 From all responsible and competent
authorities of the business and software
services
 If resolution takes time, BAS itself must
REPORT Action Taken and or Action
Required from me continually
6
Business
Application
Software
BAS
1
Business
Services

7. Effective means to evolve error-free software
7
Business
Application
Software
BPRR
Business
Authority
BAS
Developer
1
3
2
All the business policies, rules,
information and data: part of BAS
A Business Authority is
online Actor!
 BAS Developers can
be online but……..
?
Business
Authority
Bring all the users, business authority
and software developers online

8. Make the software Agile
 Most software is
error-prone initially
 The best way of
evolving error-free
software is:
 To minimize the
errors to the extent
possible and;
 Provide quick and safe
means of
 Correcting errors online
 Involve the users, the
business authorities and
software developers
online
CONFIDENTIAL
8

9. Means: Framework for Online Software Evolution
 BAS Developer needs full software
development system
 Yes, Continuous Integration and
Continuous Deployment CI/CD also
 But BAS Developer cannot be directly
interfaced with BAS
 A new Framework for Online Software
Evolution FOSE is necessary
CONFIDENTIAL
9
Framework
for Online
Software
Evolution
FOSE

10. UseCase Diagram of BAS
10
Business
Application
Software
Business
Authority
FOSE
1
3
2
Only one service dialog is shown with
each actor but multiple dialogs exist
Business Authority is an
online Actor
BAS Developer is an
actor of FOSE
Business
Authority
Business
Actor

11. Business Policies, Rules, Information and Data
 Informally distributed and
embedded in the BizApp
 It is called hard coding, a bad
programming practice
 If business policies and rules
change, BizApp has to be
stopped, modified and
relaunched
 Ideally, BizApp should
capture and
distribute business
Information and Data
as needed
 However, this is not
done in many
business applications
11

12. Business Polies & Rules Repository BPRR in BAS
 There is a need for a central curated repository
of business policies, rules, information and data
(Business Policies & Rules Repository)—an
internal resource
 BPRR may need special encoding for machine
processing (RDF) or NLP or Executable English ®
 The structure and design of BAS need
fundamental change ---Recommended here
CONFIDENTIAL
12
BAS
Internal resource
will not be shown
hereafter
BPRR

13. BPRR equivalents cited and acknowledged
Ronald Ross
Business
Knowledge
Blueprints ®
Human readable
nonformal text
CONFIDENTIAL
13
BAS
Internal resource
will not be shown
hereafter
BPRR
Machine Readable
Business Ontology.
Adrian Walker’s
Executable English®
may aptly serve this
need
May be viewed as
All the copyrights are
fully acknowledged

14. Online Business Authority: NEW Actor of BAS
 Online Business Authority
 Necessary for the services:
 1 Create and Upload BPRR
 2 Correct BPRR
 3 Approve Software
Correction Request
 Ensures business continuity in
spite of BPRR limitations
CONFIDENTIAL
14
Business
Authority
1
2
Partial UseCase Diagram
BAS
Internals
deliberately
hidden
3

15. Business Errors & Online Corrections
CONFIDENTIAL
15
Business Error:
Improper business
decision or action
caused by errors in
business policies,
rules or information
and data
 An online Business Authority can
correct business errors by changing the
policies, rules, information and data
maintained in BPRR
 The Business Application Software BAS
is specifically redesigned for adding
BPRR and other services / interfaces

16. Software Error Correction through FOSE
 BAS may have
software errors
 Business Authority
cannot correct them
 He approves & sends
them to the external
framework FOSE
 Framework for Online
Software Evolution FOSE has
a chain of
 BAS developers,
 Software Development System
 Loops back to BAS Platform
CONFIDENTIAL
16

17. BAS corrections & relaunch Process Map Proposed
CONFIDENTIAL 17
BAS Developer
Framework for
Online Software
Evolution FOSE
Business
Application
Software
with Platform
Software
Developent
System
Submit Approved
Software Correction
Requests Relay Approved
Software Correction
Requests
Corrected BAS
Release
corrected BAS
Launch
corrected BAS
Other actors not
shown here

18. DE-Atomate Request from User
De-Automate---Error reporting and correction request.
When a user clicks it BAS opens a Dialog Box
Typical Dialog Screen
Error Correction Request
If you wish to proceed fill-in the following: If not
1: Difficulty faced Describe with examples
2: Correction Required
for any kind of error
Describe with examples &
reasons
3: UX Improvements Describe with examples &
reasons
Quit
Send
Cancel
CONFIDENTIAL
18
De-Automate
Default button on
every or screen
Attachments

19. Expanded UseCase Diagram of BAS
CONFIDENTIAL 19
BAS
with Platform
Business
Authority
Business
Actor
1
1 Error Correction Req
1 Business Policy &
Rules Upload
2 Review requests and
take action
2
1
Framework
for Online
Software
Evolution
FOSE
1
1 Submit
Approved
Sw Ch Req
2 RECEIVE Action Taken.. Reports
3 Launch New BAS
3
2 REPORT Action
Taken & Required
2
2

20. Conclusion:
 Business Actors are enabled to make Error Correction
Requests
 New BPRR and Business Authority added
 Business Authority makes Business Corrections via BPRR
 BAS needs Software Changes also
 This needs BAS modifications and interface with external
framework for online software evolution FOSE
GO
CONFIDENTIAL
17

21. Key concepts, terms and diagrams
Glossary
CONFIDENTIAL 21

22. Business Correction Vs Software Change
 Business Correction is change of
any of Business Policies, Rules,
Information and Data to fix errors
and improve business
 Initiated by business users
 Done by Business Authority
 BAS is designed of the above
 BAS itself does not change
 Software Change needs the
developers to change, test
and launch new version of it
 Complex software and
project management process
involving many professionals
 Separate frameworks and
servers like CI/CD and SAFe
exist for this (not covered here)
CONFIDENTIAL
22

23. Erroneous UML UseCase Model
 UseCase model: Conceptually very
apt, effective, comprehensive and
useful
 However UML spec v 2.5 is too lax,
imprecise and misleading
 Fails to identify the exact nature of
UseCase
 So, it is corrected and used
System under
Consideration
SuC
Business
Actor 1
Business
Actor N
UC 1
UC N
What is wrong and why? What is the correction?
See: https://www.slideshare.net/putchavn/errors-corrections-of-use-case-modeling
CONFIDENTIAL
20
Erroneous UseCase Model

24. Goal of Dialog or Conversation
 A dialog or conversation must have
a goal
 The goal may have multiple
conditional end results
 A log-in conversation should enable
authentic users to access the
system and also blocks others
System under
Consideration
SuC
Business
Actor 1
Business
Actor N
CONFIDENTIAL
21
1
2
N
Service Dialogs
with Goal

25. Need for a Platform for Running Software
 Any software that runs on a computer
needs a special software platform
 Platform consists of Operating System
and Utilities
 A system administrator is necessary to
maintain the OS and Utilities and run
the software---he or she is offline
CONFIDENTIAL
25
See notes of every slide for
more explanation
Software
Platform

26. Business Application Software
 BAS operates for intended business per
business policies and rules
 The essential Platform of OS and Utilities ---
not always shown but implied
 A human System Administrator is necessary
for setting up and running the above (works
offline) --- not shown as an Actor of BAS
CONFIDENTIAL
26
See notes of every slide for
more explanation
Business
Application
Software
BAS
Platform
System
Admin

27. BAS Running on Platform Serving
Users
 Executable object code of BAS runs
on a given platform
 Platform consists of OS + Utilities
 BAS implies BAS in execution
 BAS delivers different services to
Actor classes 1 to N
 Only one service dialog per actor is
shown but more are possible
CONFIDENTIAL
27
BAS
Platform
Actor 2
Actor N
Actor 1

28. Data Governance and Business Authority
 Data Governance emerged in 2006 for data quality, privacy
and other compliances
 Business Authority was proposed around 2010 and
uploaded to SlideShare in 2013
 Business Authority ensures online business error
corrections and business continuity
 Not clear if Business Authority and Data Governance have
any overlap; we consider they are distinct & separate
CONFIDENTIAL
28

29. Data Governance--wikipedia
 https://en.wikipedia.org/wiki/Data_governance
 Data governance is a term used on both a macro
and a micro level.
 The former is a political concept and forms part of
international relations and Internet governance;
 the latter is a management concept and forms part
of corporate governance.
CONFIDENTIAL
29

30. Data Governance--IBM
 IBM (www.ibm.com/analytics/data-governance)
 Data governance (DG) is the process of managing
the availability, usability, integrity and security of
the data in enterprise systems, based on
internal data standards and policies that also
control data usage.
 Effective data governance ensures that data is
consistent and trustworthy and doesn't get
misused.
CONFIDENTIAL
30