Practicing modeling at large scale

Transcription

1 Practicing modeling at large scale The road to a scalable modeling environment at ASML. Marc Hamilton

2 Content Introduction Abstraction pyramid Model relations Mode Driven Engineering practice Design Change issues Managing models The Model Unit The Model Unit Development Environment Status and Experience 2

3 ASML Litho scanner 5 by 3 by 2 m, ~20000 kg > lines of code > 250 SW components > 3700 interface files 10 architectural layers > 10 releases / y > 600 SW developers > 4300 docs (VanDale: 4300 pages) Gradual introduction of MDE facilities 3

4 Abstraction pyramid Abstract description of system. Typically expressed in terms as defined in the domain the system operates in. Increasing detail Detailed description of system. Can even end up in implementation code. Ack: W. Alberts, ASML 4

5 Abstraction vs. Aggregation Abstraction Aggregation Note that the amount of detail increases. It is not uncommon to introduce new terms when describing the details Brand: alfa Type: 139 Color: red fire Max speed: 160 kmh Motor: 4 cilinder Price: 8000 Here, the whole is decomposed into parts without adding detail, though some new parts may be revealed. Ack: W. Alberts, ASML 5

6 System of systems Knowledge intensive systems will be organized according to competences. Driver Car infrastructure system account payment subsystem System X drive drive-inn Fuel Station System A subsystem Car tank System B System of Interconnected Systems pattern 6

7 Model of models System X subsystem System A subsystem System B 7

8 Context: (Software) Construction Manual Construction Subject Conceptual Essential Logical model DSL Automated Construction Physical Facility model Code Code Code Code Code Code Code Code Code 8

9 Model of models (revised) System X subsystem System A subsystem System B 9

10 ASML Formal definition (meta model) of abstraction levels is a necessity for introduction of MDE Formalization is done by design of a DSL Conceptual Logical Physical Ack: W. Alberts, ASML 10

11 Design change My responsibility System X System X Others responsibility Others responsibility System A System B System A System B Doesn t scale Not manageable 11

12 Design change: decoupled role spec <<compliant with>> System X System X Spec Q Spec R Spec Q Spec R <<compliant with>> System A System B System A System B Scalable Manageable 12

13 Managing coupling role spec System X Spec Q Spec R Weak coupling <<compliant with>> <<compliant with>> System A System B Strong coupling 13

14 The model project : Model Unit Models are too large to handle Archive requires modular structure (e.g. components) Model Unit is a component, a unit of maintenance Identical to source code project: Public visible sections exposing black-box (specification) Must be self-contained Private/friend sections containing white box (realization) No relations flowing in 14

15 Model Unit structure overview (global) mu A = shareable (public) conceptual model logical model logical realizations logical interface logical rolespec physical model physical realizations physical interface physical rolespec 15

16 Inter-model unit relations (logical) mu A mu A is a user of mu P, mu P is contributor to mu A mu P = shareable (public) logical model <<uses>> logical interface Publishes black-box view mu B logical model realization <<realizes>> mu B is a contributor of mu Q mu Q logical interface <<compliant with>> logical rolespec Depends on external realization 16

17 Model Unit structure (logical) logical model = shareable (public) logical realization logical interface CC <<viewpoint>> Ia p <<specification>> CC Ib Ia p:q z:y d:x Ib logical rolespec Y Ix <<component>> X <<component>> R Q Ia e:r Ix {isabstract = true} {isabstract = true} 17

18 Model Development Environment Baseline Workspace Validation/Simulation =Target =Target 18

19 Example: Model Unit setup in Eclipse PDE Workspace mu.b internal logrealization.uml logstructure.uml external loginterface.uml loginterface mu.a Target external loginterface.uml mu.b external loginterface.uml mu.c external loginterface.uml =target:/plugin/mu.c/external/loginterface.uml 19

20 End-user experience Overwhelmed by complexity Not addressed by most traditional methods Unclear definition of logical level Old (wide-spread) tooling has only limited support Addressing these by: Introduce with new facilities Explicit DSL for logical level Clear procedures Based on new tooling 20

21 Questions? 21

22 BACKUP

23 Reflection Models are identical to (software) components Only language level is different Models have public sections exposing the systems as black boxes Models have private (protected) sections that contain the realizations The eclipse plug-in development environment is a good example of dealing with components 23

24 Inter-model unit relations: Consolidation mu A mu M logical model logical architecture z:y Ia p:q CC d:x Ib <<viewpoint>> logical interface Ia p <<specification>> CC Ib <<compliant with>> logical interface Im <<specification>> MM Y logical rolespec Ia Ix Q e:r Ix <<component>> X <<component>> R <<replace>> mu N Consolidated view z:y Ia p:q CC d:nn Ib <<compliant with>> <<replace>> logical interface In <<specification>> NN Y Ix Ia Q e:mm Ix 24

25 Model Driven Engineering DSL s, Optimized for Engineering Efficiency Formal, Executable languages Increasing detail System (Software) Construction Analysis Verification Validation Code Code HW, SW Code Code HW, SW 25