Combining the strengths of UMIST and The Victoria University of Manchester IPG Informatics Process Group School of Computer Science BPMDS'05, Porto 1 On.

Slides:



Advertisements
Similar presentations
Large-Scale, Adaptive Fabric Configuration for Grid Computing Peter Toft HP Labs, Bristol June 2003 (v1.03) Localised for UK English.
Advertisements

Chapter 7 System Models.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 9 Distributed Systems Architectures Slide 1 1 Chapter 9 Distributed Systems Architectures.
©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 8 Slide 1 System models.
Distributed Systems Architectures
CS 501: Software Engineering Fall 2000 Lecture 16 System Architecture III Distributed Objects.
7M701 1 Software Engineering Systems Models Sommerville, Ian (2001) Software Engineering, 6 th edition: Chapter 7 (some items)
Copyright 2004 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Second Edition Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Appendix.
7M822 Software Engineering: System Models 14 September 2009.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 7 Slide 1 System models l Abstract descriptions of systems whose requirements are being.
INTRODUCTION TO WEB DATABASE PROGRAMMING
Chapter 1 Introduction to Visual Basic Programming and Applications 1 Exploring Microsoft Visual Basic 6.0 Copyright © 1999 Prentice-Hall, Inc. By Carlotta.
©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 12 Slide 1 Distributed Systems Architectures.
11 1 Object oriented DB (not in book) Database Systems: Design, Implementation, & Management, 6 th Edition, Rob & Coronel Learning objectives: What.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 7 Slide 1 System models l Abstract descriptions of systems whose requirements are being.
Chapter 4 System Models A description of the various models that can be used to specify software systems.
Fundamentals of Information Systems, Fifth Edition
Chapter 1 소프트웨어의 본질 The Nature of Software 임현승 강원대학교
ASG - Towards the Adaptive Semantic Services Enterprise Harald Meyer WWW Service Composition with Semantic Web Services
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 10Slide 1 Architectural Design l Establishing the overall structure of a software system.
Copyright 2001 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Appendix A Object-Oriented.
Copyright 2002 Prentice-Hall, Inc. Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich Chapter 20 Object-Oriented.
Unified Modeling Language, Version 2.0
© 2004 Prentice-Hall, Inc Chapter 17 Information Technology in the Supply Chain Supply Chain Management (2nd Edition)
©Ian Sommerville 1995/2000 (Modified by Spiros Mancoridis 1999) Software Engineering, 6th edition. Chapter 7 Slide 1 System models l Abstract descriptions.
Chapter 1 The Systems Development Environment Modern Systems Analysis and Design Sixth Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich.
A Novel Approach to Architectural Recovery in Evolving Object- Oriented Systems PhD thesis Koen De Hondt December 11, 1998.
System models l Abstract descriptions of systems whose requirements are being analysed.
Modified by Juan M. Gomez Software Engineering, 6th edition. Chapter 7 Slide 1 Chapter 7 System Models.
Software Engineering, 8th edition Chapter 8 1 Courtesy: ©Ian Somerville 2006 April 06 th, 2009 Lecture # 13 System models.
Sommerville 2004,Mejia-Alvarez 2009Software Engineering, 7th edition. Chapter 8 Slide 1 System models.
Quality views: capturing and exploiting the user perspective on data quality Paolo Missier, Suzanne Embury, Mark Greenwood School of Computer Science University.
Slide 1 Systems Analysis and Design With UML 2.0 An Object-Oriented Approach, Second Edition Chapter 2: Introduction to Object-Oriented Systems Analysis.
Infrastructures for Social Simulation Rob Procter National e-Infrastructure for Social Simulation ISGC 2010 Social Simulation Tutorial.
CS 501: Software Engineering Fall 1999 Lecture 12 System Architecture III Distributed Objects.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 8 Slide 1 System models.
Slide 1 Systems Analysis and Design With UML 2.0 An Object-Oriented Approach, Second Edition Chapter 2: Introduction to Object-Oriented Systems Analysis.
1 Unified Modeling Language, Version 2.0 Chapter 2.
Banaras Hindu University. A Course on Software Reuse by Design Patterns and Frameworks.
Copyright © 2009 Pearson Education, Inc. Publishing as Prentice Hall Appendix A Object-Oriented Analysis and Design A.1.
Introduction to UML and Rational Rose UML - Unified Modeling Language Rational Rose 98 - a GUI tool to systematically develop software through the following.
1 CS 501 Spring 2002 CS 501: Software Engineering Lecture 15 System Architecture III.
Engineering, 7th edition. Chapter 8 Slide 1 System models.
Design Review.
CIIT-Human Computer Interaction-CSC456-Fall-2015-Mr
Chapter 1 The Nature of Software
UML Diagrams By Daniel Damaris Novarianto S..
Definition CASE tools are software systems that are intended to provide automated support for routine activities in the software process such as editing.
Business System Development
Physical Data Model – step-by-step instructions and template
Systems Analysis and Design With UML 2
Systems Analysis and Design With UML 2
ENHANCING MANAGEMENT DECISION MAKING
UML Diagrams Jung Woo.
Software What Is Software?
Abstract descriptions of systems whose requirements are being analysed
Chapter 1 The Nature of Software
Chapter 1 The Nature of Software
Software Design Methodology
The Extensible Tool-chain for Evaluation of Architectural Models
Service-centric Software Engineering
(VIP-EDC) Point 6 of the agenda
Chapter 20 Object-Oriented Analysis and Design
Appendix A Object-Oriented Analysis and Design
Software Engineering with Reusable Components
Internet Influences on the Marketing Environment
Criteria for rapid prototyping
Appendix A Object-Oriented Analysis and Design
Appendix A Object-Oriented Analysis and Design
Presentation transcript:

Combining the strengths of UMIST and The Victoria University of Manchester IPG Informatics Process Group School of Computer Science BPMDS'05, Porto 1 On the architecture and form of flexible process support R.A. Snowdon, B.C. Warboys, C. Holland, P. Kawalek and D.Shaw * University of Manchester, UK * Nottingham University, UK

Combining the strengths of UMIST and The Victoria University of Manchester IPG Informatics Process Group School of Computer Science BPMDS'05, Porto 2 Overview The problem –What are the structures and properties of ICT systems supporting sustainable businesses? Approach –Systemic, cybernetic –Active models Experimentation –The Flexible Business Integration (FBI) project –An example Issues and Discussion

Combining the strengths of UMIST and The Victoria University of Manchester IPG Informatics Process Group School of Computer Science BPMDS'05, Porto 3 Flexibility “…the ability of a firm's processes and systems to respond quickly to changes in the business environment. It includes the capacity to accommodate shifts in consumer demand, in competitors' strategies, in rate of growth, and in suppliers' deals and shipment problems…” A property of a business (system) which allows it be sustainable in a changing world How is this property manifest in a business and how can ICT be formed to support such a property?

Combining the strengths of UMIST and The Victoria University of Manchester IPG Informatics Process Group School of Computer Science BPMDS'05, Porto 4 Business is a system Business as a system Environment To be sustainable the business must be effective not only in fulfilling its function but in its development in the environment How can ICT support this need?

Combining the strengths of UMIST and The Victoria University of Manchester IPG Informatics Process Group School of Computer Science BPMDS'05, Porto 5 ICT as an active model Non ICT system ICT system Reaction and proaction relationships The business system is a set of interacting processes. The ICT system is a set of interacting processes modelling the business system, linked by react and proact relationships. The systems co-evolve What are the form and characteristics that support this?

Combining the strengths of UMIST and The Victoria University of Manchester IPG Informatics Process Group School of Computer Science BPMDS'05, Porto 6 The Viable System Model (VSM) 3 4 3* Environment 5 The VSM is a cybernetic process model. Distinguishes meta and operational processes. Apply it to the non ICT and the ICT systems as an architecture.

Combining the strengths of UMIST and The Victoria University of Manchester IPG Informatics Process Group School of Computer Science BPMDS'05, Porto 7 Modelling - POSD POSD (Process Oriented Systems Design) models systems as interacting processes B C A A is a system (process) composed of the interaction of processes B and C Interaction is shown by “touch” (or equivalently a line) Interaction is fulfilled by shared component processes

Combining the strengths of UMIST and The Victoria University of Manchester IPG Informatics Process Group School of Computer Science BPMDS'05, Porto 8 VSM POSD “icon” S5 S4 S3 S3* S1 S2

Combining the strengths of UMIST and The Victoria University of Manchester IPG Informatics Process Group School of Computer Science BPMDS'05, Porto 9 Supply chain scenario Muzak.com, Eshop.com use B2b.com to arrange partnership. Partnership operates Partners break apart again. Arrange new partnership Etc. POSD models with narrative can describe the activity.

Combining the strengths of UMIST and The Victoria University of Manchester IPG Informatics Process Group School of Computer Science BPMDS'05, Porto 10 Starting position Muzak.com S5 S4 S3 S3* S1 S2 S5 S4 S3 S3* S1 S2 B2b.com S5 S4 S3 S3* S1 S2 Eshop.com S5 S4 S3 S3* S1 S2 Customer

Combining the strengths of UMIST and The Victoria University of Manchester IPG Informatics Process Group School of Computer Science BPMDS'05, Porto 11 Decide to form partnership Muzak.com S5 S4 S3 S3* S1 S2 S5 S4 S3 S3* S1 S2 S5 S4 S3 S3* S1 S2 Eshop.com B2b.com S5 S4 S3 S3* S1 S2 Customer

Combining the strengths of UMIST and The Victoria University of Manchester IPG Informatics Process Group School of Computer Science BPMDS'05, Porto 12 Do business B2b.com Muzak.com S5 S4 S3 S3 * S1 S2 S5 S4 S3 S3* S1 S2 S5 S4 S3 S3* S1 S2 Eshop.com S5 S4 S3 S3* S1 S2 Customer

Combining the strengths of UMIST and The Victoria University of Manchester IPG Informatics Process Group School of Computer Science BPMDS'05, Porto 13 Break apart Muzak.com S5 S4 S3 S3* S1 S2 S5 S4 S3 S3* S1 S2 S5 S4 S3 S3* S1 S2 Eshop.com S5 S4 S3 S3* S1 S2 Customer

Combining the strengths of UMIST and The Victoria University of Manchester IPG Informatics Process Group School of Computer Science BPMDS'05, Porto 14 Map to BPS – the active model Both systems are structured as VSM arranged sets of interacting processes. Non ICT (social) system active model as PML enacted using Process Web standard browsers internet S5 S4 S3 S3* S1 S2

Combining the strengths of UMIST and The Victoria University of Manchester IPG Informatics Process Group School of Computer Science BPMDS'05, Porto 15 PML-Process Modelling Language Class based concurrent language with inheritance Principal classes –Role, Interaction, Entity, Action Each class is an aggregation of properties arranged by distinguishing categories. Reflexive – callable compiler, run time examination of execution objects. Persistent.

Combining the strengths of UMIST and The Victoria University of Manchester IPG Informatics Process Group School of Computer Science BPMDS'05, Porto 16 Mapping of VSM architecture Almost direct mapping of major VSM behaviours to PML Roles. The E (volution) – P (roduction) pairs. E P E P S1 S3 Each behaviour has a “do” component (P) and an “evolve” component (E). Each P (generally) has partner in non-ICT system.

Combining the strengths of UMIST and The Victoria University of Manchester IPG Informatics Process Group School of Computer Science BPMDS'05, Porto 17 Change process - S3 on S1 and S3 Decide changes to S1 and S3 Formulate changes as PML Apply changes to S1_P via S1_E Apply changes to S3_P via S3_E Operating normally Stopped (frozen) Operating normally (revised) Operating normally (revised) S3 S1

Combining the strengths of UMIST and The Victoria University of Manchester IPG Informatics Process Group School of Computer Science BPMDS'05, Porto 18 Enacting the model (change) social system active model as PML enacted using Process Web internet

Combining the strengths of UMIST and The Victoria University of Manchester IPG Informatics Process Group School of Computer Science BPMDS'05, Porto 19 Changing values

Combining the strengths of UMIST and The Victoria University of Manchester IPG Informatics Process Group School of Computer Science BPMDS'05, Porto 20 And so on … Can explore at ProcessWeb

Combining the strengths of UMIST and The Victoria University of Manchester IPG Informatics Process Group School of Computer Science BPMDS'05, Porto 21 Architectural points Sound basis of VSM coupled with BPS non IT IT time Architecture for change

Combining the strengths of UMIST and The Victoria University of Manchester IPG Informatics Process Group School of Computer Science BPMDS'05, Porto 22 Architectural Points There is much more to VSM –Monitoring and interpretation S3 S1 S3 domain (“values”) (e.g. comfort) S1 domain (“widgets”) (e.g. temperature) Visualisation Decisioning (the homeostat)

Combining the strengths of UMIST and The Victoria University of Manchester IPG Informatics Process Group School of Computer Science BPMDS'05, Porto 23 Architectural points Scenarios –S4 –Embedded use of architecture for potential futures Higher level systems, system composition –Herring and Kaplan B2B Eshop Muzak Recursion

Combining the strengths of UMIST and The Victoria University of Manchester IPG Informatics Process Group School of Computer Science BPMDS'05, Porto 24 Mapping on to “real software” Business system Corporate IT – databases, apps., tools Architecture Passive, design time Active, run time – Co-ordination layer, orchestration

Combining the strengths of UMIST and The Victoria University of Manchester IPG Informatics Process Group School of Computer Science BPMDS'05, Porto 25 Technology points Reflection –S3 code which changes code of S1 and S3 Hypercode RE reification reflection edit eval Need for completeness in E-R relationship

Combining the strengths of UMIST and The Victoria University of Manchester IPG Informatics Process Group School of Computer Science BPMDS'05, Porto 26 Technology points Inheritance –Appealing because of incremental change –Limited to subclassing –Granularity issues ( example) example Open systems –Some state external to system Development support –S3 develops S1 May get it wrong What if?/simulation Checking/proof/analysis tools Real time development

Combining the strengths of UMIST and The Victoria University of Manchester IPG Informatics Process Group School of Computer Science BPMDS'05, Porto 27 Summary The process is the development process.

Combining the strengths of UMIST and The Victoria University of Manchester IPG Informatics Process Group School of Computer Science BPMDS'05, Porto 28 Code example receive_selection : { ! when sv='receive' etc Take(gram=cgi_data, interaction=userRolePorts.userTakeport);.. if cgi_data('formid')='genericS3_P_01' then sv:=cgi_data('selection') elsif cgi_data('formid')='genericS3_P_02' then if cgi_data('selection')='compile' then classcode:=cgi_data('code'); sv:='compile_p' elsif cgi_data('selection')='install' then sv:='install_p' elsif cgi_data('selection')='bindings' then sv:='extractvalues' elsif cgi_data('selection')='abort' then sv:='abort_p' end if elsif cgi_data('formid')='genericS3_P_02F' then.. elsif cgi_data('formid')='genericS3_P_03' then.. end if } when sv='receive' & userRolePorts ~= nil & userRolePorts.userTakeport ~= nil Back