2. 1 CROSSING THE CHASM Business Process to Information System Reading Assignment Supplementary module 5

3. 2 Tangible Objects, Processes & Mechanisms Tangible Information Information Logistics, Interface & Technology Layers Abstract Meanings & Patterns that unify INFORMATION SPACE (A CONNECTING HUB) REAL WORLD INFORMATION SYSTEM THE BRIDGES FROM INFORMATION SPACE Information is the essence of an object –Its meaning An abstract pattern of information in an abstract place –We have named this place Information Space –Contains patterns of possibilities, the meaning of impossible and of meaninglessness itself –Carved from inchoate information by constraints; contains the meaning of constraint itself Physical space and time are only one aspect, a facet of information space Information is expressed in physical space with symbols A physical object may be considered a format of the information it conveys –A manifestation of the information it conveys Information space is also a hub that can sweep information from reality to information systems

4. 3 © Amit Mitra & Amar Gupta PERCEPTION AND COMMUNICATION OF MEANING Five fundamental formatting domains based on five senses –Visible (Visual) Formats: normalizes behavior common to visual perception –Eg: 3d, movement and rotation in space, viewpoints from different locations, color, size, contrast, brightness, etc. Script: Written symbols such as alphabets, numerals and words Graphics: diagrams, pictures etc. –Audible (Audio) Formats: normalizes behavior common to audible perception –Eg: loudness (volume), pitch –Tactile (Haptics) formats: normalize behavior about touch –Eg: feeling of pressure, roughness or smoothness, heat or cold, hardness and softness, sharpness or bluntness, friction etc. –Olfactory Formats: normalizes behaviors natural to sense of smell –Taste Formats: normalizes behaviors natural to sense of taste Bridge between Business and Interface Layers TECHNOLOGY RULES INTERFACE RULES (HUMAN & AUTOMATION) INFORMATION LOGISTICS BUSINESS RULES Vision Process Events Value Policy/Strategy Exceptions BUSINESSPATTERNS DATA MOVEMENT GUIs & FORMATTING COMPONENTS PERFORMANCE OPTIMIZATION COMPONENTS Meaning to algorithm or formula

5. 4 Unload cookie Bake dough Cookie batch Cookie Sheet (in use) Cookie (information) Cookie Sheet (used) (information) Change state of cookie sheet Create cookie Begin (not necessarily together) End (not necessarily together) (effect) (PROCESS) precede (Process) Cookie Cookie Sheet (used)  (Mutually Inclusive Effects) (PRODUCTS) (RESOURCES) BUSINESS PROCESS TO COMPUTER PROCESS

6. 5 Unload cookie Bake dough Cookie batch Cookie Sheet (in use) Cookie (information) Cookie Sheet (used) (information) Change state of cookie sheet Create cookie Begin (not necessarily together) End (not necessarily together) (effect) (PROCESS) precede (Process) Cookie Cookie Sheet (used)  (Mutually Inclusive Effects) (PRODUCTS) (RESOURCES) BUSINESS PROCESS TO COMPUTER PROCESS Must begin and end together in real life Only mutually inclusive in an automated system –Defines a transaction, roll back-recovery –Differrent from a business rule that requires the process be restarted with fresh dough if it has been suspended for more than an hour

7. 6 I/S control Process (A) THE INFORMATION SYSTEMS ASSEMBLY LINE Interface (“P” for Presentation of information) navigates the information system by triggering control processes Object response to Business Event (“E” for Effect) Effect Object The same I/S control process (“C”) reused within another control Process Controls use of, & sequences Accesses & Updates Effect Object (recording of events & data, navigation through screens, dialogs, menus etc) The same components may be invoked by different control processes Objects (Reusable Components) (Effects of Events on Objects) Re-usable Process (C) (A subassembly of effects and controls) PARALLEL PROCESSES I/S control Process (B) HOW OBJECTS RESPOND TO EVENTS (Effects of Events on Objects) Actor Accesses & Updates Triggers, Interrupts and controls (Event) Process (Another Reusable Component) INFORMATION INPUT AND OUTPUT PROCESSES (Flow of Time) Information systems Control Processes derived from business process maps (C) Orchestration determined by the process map Business processes are triggered by business events Business Events act on business objects –These actions are effects of business events. – Effects... Create or delete object instances and effects Update attributes, or states of objects Create, destroy or switch relationships between particular instances of objects The sequence of effects must match the sequences of processes they were derived from Otherwise the integrity of information may be compromised

8. 7 CFO SIGNATURE EVENT EFFECT OF CFO SIGNATURE ON CHECK OPERATIONS 1. Store CFO Signature 2. If CEO signature is not null set check Payability indicator to “Payable” Guard condition Operations in Effect CHECK (OBJECT) Subtype of Set (store) occurrence of CFO signature (state indicator) Set (store) CFO signature One operation may be a subtype of another depending on its information content Store is a polymorphism of Set in the information logistics layer An effect may –create an (information) object. –delete an (information) object. –Update the state an (information) object. The object may also be a relationship, attribute or an effect. –If the object is a relationship, the effect might switch the relationship from one instance of an object to another –Eg: A Person, tied to a product via a purchasing relationship, becomes a customer EFFECT OF AN EVENT ON AN OBJECT An operation may: –Replace the value of a feature –Delete or create an object –Replace, create or delete an effect Eg: Sealing an agreement deletes an effect May be implemented by a guard condition Reopening an agreement adds an effect

9. 8 CFO SIGNATURE EVENT EFFECT OF CFO SIGNATURE ON CHECK OPERATIONS 1. Store CFO Signature 2. If CEO signature is not null set check Payability indicator to “Payable” Guard condition Operations in Effect CHECK (OBJECT) Subtype of Set (store) occurrence of CFO signature (state indicator) Set (store) CFO signature One operation may be a subtype of another depending on its information content Store is a polymorphism of Set in the information logistics layer An effect may –create an (information) object. –delete an (information) object. –Update the state an (information) object. The object may also be a relationship, attribute or an effect. –If the object is a relationship, the effect might switch the relationship from one instance of an object to another –Eg: A Person, tied to a product via a purchasing relationship, becomes a customer EFFECT OF AN EVENT ON AN OBJECT An operation may: –Replace the value of a feature –Delete or create an object –Replace, create or delete an effect Eg: Sealing an agreement deletes an effect May be implemented by a guard condition Reopening an agreement adds an effect

10. 9 Information Conveyance Process Information Input Process Information Input Process Information Output Process Information Output Process INPUT/OUTPUT PARTITION (sourcing process) (delivery process) Information logistics Information logistics Information Interface Information Interface BUSINESS PROCESS AUTOMATION PARTITION subtype of

11. 10 NORMAL EXCEPTION PROCESS INPUT PROCESS OUTPUT PROCESS BUSINESS PROCESS Business Information Business Information   

12. 11 NORMAL EXCEPTION PROCESS INPUT PROCESS OUTPUT PROCESS TRANSFORMATION PROCESS Business Information Business Information (information exception) (Information output exception for normal business process) (Information output exception for business exception process) (Information input for normal business process) (Information input for business exception process) BUSINESS PROCESS INFORMATION PROCESS FOR NORMAL BUSINESS BUSINESS EXCEPTION PROCESS     INFORMATION PROCESS FOR BUSINESS EXCEPTIONS         Each Information input and output process will also have information logistics and interface layers

13. 12 May raise alarms –Business (eg: oven failure, constraint violation, missing resource, broken conveyance mechanism) – BPA (eg: missing file, data in unexpected format, corrupted data, data from questionable source etc) –Technical exceptions (Eg: network failure, defective program) Information Exception Layers –Interface layer of information exception output process may be output device sensitive (Eg: sounding alarm, showing in a different color etc.) –Information logistics layer of information exception output process will manage storage & transportation of information exceptions –Interface layer of information exception input process will accept corrections that could change the state of information exceptions –Information logistics layer of information exception input process will manage storage, staging and transportation of input data that might change the state of information exceptions –Information Exception Transformation process will set and change the states of information exceptions Information exception output process will interpret these states in a format appropriate for different actors Unknown exception process –Accept exception procedures at execution time if process is “unknown” Unstructured process Users may be alerted, inputs accepted by automated agent Agent may store the solution and use the Principle of Parsimony to reuse the solution as appropriate –Confirm application with an actor Actor may add information, confirm or deny –Apply without confirmation –Use a governing process to determine the right option Referential Integrity Exceptions –Rules of interdependency: When the lawful state space of one (or more) object or composition refers to (is constrained by) another (others) Applies to mandatory relationships such as subtypes and existence dependency Eg: Occurrence of orders is contingent on the existence of a customer Eg: Should a customer be deleted if open orders are pending? –“Snap-on” change parts (options) Automatic cascading delete Optional cascading delete Prohibited deletion Exceptions

14. 13 Interface Events & Effects Control & Navigation Information Logistics Events & Effects Control Technology Events & Effects Control Unaugmented Control Process (Business Effects Control) part of 0 or more [Composed of 1] Augmented part of 0 or more [Composed of 1] part of 0 or more [Composed of 1] part of 0 or more [Composed of 1] INFORMATION INPUT & OUTPUT PROCESS IMPLEMENTING THE CONTROL PROCESS IN AUTOMATION Control Process Orchestration Interruption Rollback-recovery The sequence of effects must not violate the sequences of business processes they were derived from Reusable asset May be combined with different orchestrations of interface events, effects, navigation and control processes Eg: 3270 vs. GUI May be combined with different orchestrations of technology events, effects, navigation and control processes Stricter than “consists of” Must assert when, and under what conditions embedded non- business effects will be invoked Stricter than “consists of” Must assert when, and under what conditions embedded non- business effects will be invoked Stricter than “consists of” Must assert when, and under what conditions embedded non- business effects will be invoked Stricter than “consists of” Must assert when, and under non-business effects will be invoked Some control processes may not be implemented See supplementary Materials Box 64

15. 14 IMPLEMENTING NON TEMPORAL RELATIONSHIPS IN AUTOMATION Injective (one to many) –May be implemented by drop down lists, tables, pull-down windows, graphics etc. Surjective (one-to-many) –Similar (a relationship may be traversed in either direction) Many-to-many –Similar High order or high degree relationships –Tabular With optional visibility into states of constituents of the relationship Navigation processes: The cycle time is not business information any more; it is computer mechanics –Apply to “Observation/Inquiry processes Substitute some non-temporal relationships and algorithms with processes –Eg: Setting a payability indicator for the check after both signatures are updated –Eg: payment = Rent + Utility charges A third order relationship and mutual constraint –The cycle time is not business information any more; it is computer mechanics –The cycle time of the augmented orchestration of effects that maps to a business process must not exceed the cycle time requirements (if any) for the business process

16. 15 © 1996 AMIT MITRA (973)734-1703 THE METAMODEL OF RELATIONSHIP

17. 16 CONSTRAINT

18. 17 OBJECT CLASS INCHOATE OBJECT ACTOR/OBSERVER CONSTRAINT Instance Class OBJECT Instance Class OBJECT Class Instance OBJECT INFORMATION Relationships between instance identifiers are nominal pattern of occurrence Relationships between attributes or domains may be magnitude constraints State space is a pattern Value constraints can carve out lawful regions of conceivable state space Instance identifier is a token for a pattern Governance flows from patterns of patterns Patterns are defined by the Law of Location The Law of Location is a constraint A constraint conveys information –All information flows from some form of the concept of constraint –Constraints shape objects and patterns in information space Constraints are the root of all meaning Constraints create properties A CONSTRAINT MAKES THE INCHOATE CHOATE

19. 18 CONSTRAINT OBJECT CLASS INCHOATE OBJECT ACTOR/OBSERVER CONSTRAINT Instance Class OBJECT Instance Class OBJECT Class Instance OBJECT INFORMATION Relationships between instance identifiers are nominal pattern of occurrence Relationships between attributes or domains may be magnitude constraints State space is a pattern Value constraints can carve out lawful regions of conceivable state space Instance identifier is a token for a pattern Governance flows from patterns of patterns Patterns are defined by the Law of Location The Law of Location is a constraint A constraint conveys information –All information flows from some form of the concept of constraint –Constraints shape objects and patterns in information space Constraints are the root of all meaning Constraints create properties A CONSTRAINT MAKES THE INCHOATE CHOATE

20. THE METAMODEL OF OBJECT PROPERTY See supplementary Materials Module 6

21. OVERVIEW OF THE INTEGRATED METAMODEL OF KNOWLEDGE See supplementary Materials Module 7

22. 21 See Box 30 in your textbook

23. 22 Interface Events & Effects Control & Navigation Information Logistics Events & Effects Control Technology Events & Effects Control Unaugmented Control Process (Business Effects Control) part of 0 or more [Composed of 1] Augmented Control Process part of 0 or more [Composed of 1] part of 0 or more [Composed of 1] part of 0 or more [Composed of 1] INFORMATION INPUT & OUTPUT PROCESS

24. 23 CFO SIGNATURE EVENT EFFECT OF CFO SIGNATURE ON CHECK OPERATIONS 1. Store CFO Signature 2. If CEO signature is not null set check Payability indicator to “Payable” Guard condition Operations in Effect CHECK (OBJECT) Subtype of Set (store) occurrence of CFO signature (state indicator) Set (store) CFO signature One operation may be a subtype of another depending on its information content

25. 24 NORMAL EXCEPTION PROCESS INPUT PROCESS OUTPUT PROCESS BUSINESS PROCESS Business Information Business Information

26. 25 Interface Events & Effects Control & Navigation Information Logistics Events & Effects Control Technology Events & Effects Control Unaugmented Control Process (Business Effects Control) part of 0 or more [Composed of 1] Augmented Control Process part of 0 or more [Composed of 1] part of 0 or more [Composed of 1] part of 0 or more [Composed of 1] INFORMATION INPUT & OUTPUT PROCESS

27. 26 CFO SIGNATURE EVENT EFFECT OF CFO SIGNATURE ON CHECK OPERATIONS 1. Store CFO Signature 2. If CEO signature is not null set check Payability indicator to “Payable” Guard condition Operations in Effect CHECK (OBJECT) Subtype of Set (store) occurrence of CFO signature (state indicator) Set (store) CFO signature One operation may be a subtype of another depending on its information content

28. 27 NORMAL EXCEPTION PROCESS INPUT PROCESS OUTPUT PROCESS BUSINESS PROCESS Business Information Business Information