|
[XML-DEV Mailing List Archive Home]
[By Thread]
[By Date]
[Recent Entries]
[Reply To This Message]
Re: How to represent step-by-step procedures in XML?
- From: Damian Morris <damian@moso.com.au>
- To: Roger L Costello <costello@mitre.org>
- Date: Sun, 21 Aug 2022 23:11:01 +0000
 |
Further to Michael’s point, this is a great example of the 80/20 rule - in this case, that around 80% of your code (in a thorough implementation) will commonly be required to deal with exception cases, and only around 20% will handle the actual process you
thought you were implementing (ie, the “success” path).
That means that 80% of your code is super-boring “check for this unexpected outcome and deal with it intelligently” code, rather than interesting “solve this interesting and difficult problem” code.
Of course, the most common case by far is that the boring 80% is only patchily implemented, if at all.
Cheers,
Damian
I am seeking a high-level XML representation, one that is understandable by a manager and at the same time is sufficiently detailed that it can be executed
That's the holy grail of computer science - ever since COBOL, people have been trying to find a language that was simple enough for managers to understand but precise enough to express all the detail. No-one has succeeded. I don't think it's a
language problem; I think it's an abstraction problem. "Managers" want to reason about the process at a level of abstraction that doesn't involve the sordid detail (handling of exception cases, in particular) that's needed to make the process executable.
I remember well a conversation with the marketing manager of a cable TV company, talking about the process for on-boarding new customers. We kept asking "what if" questions, and the manager got quite frustrated: he was only interested in the success
case where everything went smoothly, and wanted someone else to worry about what to do when things went wrong. His staff in the call centre were also quite frustrated: 90% of the calls they took were dealing with things that went wrong, and that weren't covered
by the process manual.
An executable process needs to deal not just with the things that often go wrong, it needs to deal with all the things that can ever go wrong, and that's a level of detail that most managers simply aren't interested in.
Michael Kay
Saxonica
|
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
|
PURCHASE STYLUS STUDIO ONLINE TODAY!
Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!
Download The World's Best XML IDE!
Accelerate XML development with our award-winning XML IDE - Download a free trial today!
Subscribe in XML format
| RSS 2.0 |
 |
| Atom 0.3 |
 |
| |
Stylus Studio has published XML-DEV in RSS and ATOM formats,
enabling users to easily subcribe to the list from their preferred news reader application.
|
Stylus Studio Sponsored Links are added links designed to provide related and additional information to the visitors of this website.
they were not included by the author in the initial post. To view the content without the Sponsor Links please
click here.
|
|
Cart
