Objectives for Session Enterprise Modelling • Introduce Enterprise Modelling • Enterprise = … • Different approaches • Model = … – Information Engineering • How would you do it? – OOEM – DFD – Enterprise Ontology – ERD • Issues – UML – getting started – Z – managing change – SD – modelling • Why would you do it? • Research tasks • ………………………. that way? RSRP RSRP Enterprise Modelling Approaches • Its what you want it to be! • Information Engineering • But – James Martin, 198x – should cover whole organisation, not just a – Data oriented single system – Top down • Includes • Object Oriented – business processes – Jacobson, Rumbaugh, Booch, Coad et al, 199x – Data + function (technical) + process – business data (about and for) – Bottom up • More importantly • Ontology Based – organisation goals – Enterprise project (IBM, AIAI, Unilever et al) – system purpose – language / change oriented • Others … Soft Systems (rich pictures), IDEF RSRP RSRP What Is a Goal or an Objective? Information Engineering - EM Outline • Karakostas & Loucopolis • Seven stages - first one is EM Goal = set of values for defined parameters – Information Systems Planning í of a “system” BAA í BSD í TD í Con í Trans í Prod • ISP split into 5 areas Objective = abstract goal, not “when”, – Determine direction: mission í objective í “how” or “how much” strategy í goal í plan í CSF • Can be different from project objectives – Map organisation: hierarchy, subject areas, function diagram Goal = “high level principle that is used to – Activities and data guide project … (e.g.) a space shuttle system that is safe” – Current systems [Bruegge & Dutoit] – Current technology RSRP RSRP Direction - Example Top Down Philosophy The Mission => To provide the maximum return • Reductionist (“divide and rule”) approach for investors through the manufacture and applies in many areas distribution of farm machinery Objective => To become market leader in farm ISP Mission machinery sales in the UK Board Level BAA Objective Strategy => Perform market research to determine Select types of products most needed in the UK BSD Select Strategy Goal => Complete demographic survey of farming population in East Anglia within 3 months TD Goal CSF => Ability to understand customer satisfaction EM Process ISP Process RSRP RSRP Information Engineering - Issues Object Orientation? • Getting started • What is it? – Big bang í management buy-in, cost, culture – (Technical) pilot í tactical use of case tool • Exposure to .. • Managing change – programming – closely coupled ISP: OSGPC í SA í ER – design – waterfall based – analysis – code generation: would work better for tactical systems but IE is big budget • Modelling – separation / co-ordination of data and process RSRP RSRP Object Orientation Object Orientation - Example • OO is an approach, not a method • Goal = Understand customer satisfaction – focus is on objects • Features = log / do / analyse / interact – bottom-up (at least traditionally) • Objects = customer, products, features, – roots in programming (Simula, Smalltalk) problems, surveys, satisfaction scores – weak on process • Scenarios = collect data, commision survey, • OO has annexed user centered, RAD/JAD, analyse situation spiral model ideas • Interactions = select data sample, specify • Models evolve seamlessly key features, identify key correlations, – analysis í design í code output data – refinement – implementation detail RSRP RSRP Object Oriented - EM Outline Object Oriented - Issues • Top down approach from Jacobson • IE issues for Jacobson (but less support!) • Objective Specification = key element of EM • Bottom up approach [Coad] doesn’t do EM – based on / aligned to “strategic goals” • Getting started – process overview – Real world objects (actors + use cases) – measures & goals for process – Patterns (exemplars, composition) – technologies – scenarios • Managing change – CSF / risks – flexibility of OO + iterative / spiral model • Split between – issues of quality of models (hacking in disguise) – external process (use cases) • Modelling – internal process (class models etc) – graphically based • EM as bolt on – extended ER RSRP RSRP Square Pegs, Round Holes Research Tasks • Matching requirements: business vs system • Investigate market for E-commerce solutions • Working with existing systems – What options are available • Development options – Where do they fit on development options scale – constrained – How to specify requirements – configurable – How to model goals and objectives – customisable – How much effort is involoved – components • Ontology-based EM (http://www.aiai.ed.ac.uk/project/enterprise/) – code generation – What advantages does it offer? – complete development – How does modelling differ? • Enterprise component models [Coad] – UML with colour … RSRP RSRP Conclusions References • Object Oriented Software Engineering, Bruegge B& Dutoit A, 2000 • Many different approached to EM • Information Engineering, James Martin, 1989/90 • The Object Advantage: Business Process Reengineering with Object Technology, Jacobson I, Ericsson M, and • Key issue = business / systems alignment Jacobson A, 1995 • Object Models: Strategies, Patterns & Applications, Coad P, 1997 • World view (Weltshung) dictates process • Modelling techniques dictate outcomes RSRP RSRP Objectives for Session Enterprise Modelling • Introduce Enterprise Modelling • Enterprise = … • Different approaches • Model = … – Information Engineering • How would you do it? – OOEM – DFD – Enterprise Ontology – ERD • Issues – UML – getting started – Z – managing change – SD – modelling • Why would you do it? • Research tasks • ………………………. that way? RSRP RSRP Enterprise Modelling Approaches • Its what you want it to be! • Information Engineering • But – James Martin, 198x – should cover whole organisation, not just a – Data oriented single system – Top down • Includes • Object Oriented – business processes – Jacobson, Rumbaugh, Booch, Coad et al, 199x – Data + function (technical) + process – business data (about and for) – Bottom up • More importantly • Ontology Based – organisation goals – Enterprise project (IBM, AIAI, Unilever et al) – system purpose – language / change oriented • Others … Soft Systems (rich pictures), IDEF RSRP RSRP What Is a Goal or an Objective? Information Engineering - EM Outline • Karakostas & Loucopolis • Seven stages - first one is EM Goal = set of values for defined parameters – Information Systems Planning í of a “system” BAA í BSD í TD í Con í Trans í Prod • ISP split into 5 areas Objective = abstract goal, not “when”, – Determine direction: mission í objective í “how” or “how much” strategy í goal í plan í CSF • Can be different from project objectives – Map organisation: hierarchy, subject areas, function diagram Goal = “high level principle that is used to – Activities and data guide project … (e.g.) a space shuttle system that is safe” – Current systems [Bruegge & Dutoit] – Current technology RSRP RSRP Direction - Example Top Down Philosophy The Mission => To provide the maximum return • Reductionist (“divide and rule”) approach for investors through the manufacture and applies in many areas distribution of farm machinery Objective => To become market leader in farm ISP Mission machinery sales in the UK Board Level BAA Objective Strategy => Perform market research to determine Select types of products most needed in the UK BSD Select Strategy Goal => Complete demographic survey of farming population in East Anglia within 3 months TD Goal CSF => Ability to understand customer satisfaction EM Process ISP Process RSRP RSRP Information Engineering - Issues Object Orientation? • Getting started • What is it? – Big bang í management buy-in, cost, culture – (Technical) pilot í tactical use of case tool • Exposure to .. • Managing change – programming – closely coupled ISP: OSGPC í SA í ER – design – waterfall based – analysis – code generation: would work better for tactical systems but IE is big budget • Modelling – separation / co-ordination of data and process RSRP RSRP Object Orientation Object Orientation - Example • OO is an approach, not a method • Goal = Understand customer satisfaction – focus is on objects • Features = log / do / analyse / interact – bottom-up (at least traditionally) • Objects = customer, products, features, – roots in programming (Simula, Smalltalk) problems, surveys, satisfaction scores – weak on process • Scenarios = collect data, commision survey, • OO has annexed user centered, RAD/JAD, analyse situation spiral model ideas • Interactions = select data sample, specify • Models evolve seamlessly key features, identify key correlations, – analysis í design í code output data – refinement – implementation detail RSRP RSRP Object Oriented - EM Outline Object Oriented - Issues • Top down approach from Jacobson • IE issues for Jacobson (but less support!) • Objective Specification = key element of EM • Bottom up approach [Coad] doesn’t do EM – based on / aligned to “strategic goals” • Getting started – process overview – Real world objects (actors + use cases) – measures & goals for process – Patterns (exemplars, composition) – technologies – scenarios • Managing change – CSF / risks – flexibility of OO + iterative / spiral model • Split between – issues of quality of models (hacking in disguise) – external process (use cases) • Modelling – internal process (class models etc) – graphically based • EM as bolt on – extended ER RSRP RSRP Square Pegs, Round Holes Research Tasks • Matching requirements: business vs system • Investigate market for E-commerce