TDT4250 – Modeling of Information Systems Autumn 2006 Meta-modeling in METIS John Krogstie IDI, NTNU and SINTEF Meta.ppt 1 TDT4250 – Modeling of Information Systems Autumn 2006 Overview of this week � Why meta-modeling? � Central concepts � Domain-specific modeling using MetaEdit � A19 Kelly and Pohjonen: "Domain-Specific Modelling for Cross-Platform Product Families" (Proc. ER'02) ” � TODAY: Meta-modelling in METIS � B3.6 based on : Krogstie, Dalberg and Jensen: "Using a Model Quality Framework for Requirements Specification of an Enterprise Modeling Languages" in Advanced Topics in Database Research - Vol. 4, (Idea Group 2005) � ++ Q 2 1 1
TDT4250 – Modeling of Information Systems Autumn 2006 System development Developer Traditional models Analysis Specification Design Coding Maintenance Test Adaptation, integration Installation Use Procurement Requirements Interactive User Needs models Q 3 TDT4250 – Modeling of Information Systems Autumn 2006 Discussion task: What reasons are there for creating specialized modeling languages: (structure the discussion according to the language quality categories) Participant Social actor appropriateness explicit Modeller knowledge appropriateness Goals of Social actor modelling Organizational interpretation appropriateness Comprehensibility appropriateness Modeling Language Model domain externalization extension Domain appropriateness Q Technical actor interpretation Tool appropriateness 4 2 2
TDT4250 – Modeling of Information Systems Autumn 2006 Krogstie, Dalberg and Jensen: "Using a Model Quality Framework for Requirements Specification of an Enterprise Modeling Languages" in Advanced Topics in Database Research - Vol. 4, (Idea Group 2005) Meta.ppt 5 TDT4250 – Modeling of Information Systems Autumn 2006 Overview of presentation � Brief description of the problem area (Enterprise modeling) � Brief recap of model quality framework � Description of case-study � Description of approach � Result 1: Specialized modeling language � Result 2: Evaluation of modeling tool � Conclusion and further work Q 6 3 3
TDT4250 – Modeling of Information Systems Autumn 2006 Usage areas of enterprise modelling Human-sense making and communication � Computer-assisted analysis and simulation � Business process management � Model deployment and activation. Models can be activated in three � ways: Through people guided by process 'maps', where the system offers no active � support or enforcement, Automatically , where the system plays an active role in enforcing the 'script', as in � most workflow engines. Interactively , where the computer and the users co-operate in interpreting the � model in the situations that arise. The computer makes decisions about prescribed fragments, while the users resolve ambiguities. As basis and context for a traditional system development project � Difficult to find languages to support all these usage patterns at the � same time Q 7 TDT4250 – Modeling of Information Systems Autumn 2006 Overview of quality framework Perceived semantic Social actor explicit knowledge Social Pragmatic (learning) Goals of Social actor modelling interpretation Physical Organizational Pragmatic Pragmatic (human (action) understanding) Modeling Model Language domain externalization extension Semantic Syntactic Pragmatic Empirical (tool understanding) Technical Q actor interpretation 8 4 4
TDT4250 – Modeling of Information Systems Autumn 2006 Description of case-study � Case organization: World wide organization � Modeling is widely used � � Case project: Units in the relevant BA that have developed their own work � processes. Ongoing project for developing harmonized work processes to � improve efficiency. Implementation of a new software application to support the � processes. Process models used actively for different purposes. � Different stakeholder groups needed different models. � Models developed in a mix of IDEF0 (in Visio), Word and � Excel, not possible to keep updated Need for new modeling approach (language, tool and � methodology) Q 9 TDT4250 – Modeling of Information Systems Autumn 2006 Main past and current modelling tasks Q 10 5 5
TDT4250 – Modeling of Information Systems Autumn 2006 Structure of overall approach Q 11 TDT4250 – Modeling of Information Systems Autumn 2006 Goals of modeling (based on first looking at the goals of the projects) � The harmonized work processes should be documented through the models. � The models should help sharing best practice between different units � The models should teach the developers about the domain. � The models should define the scope of the software application. � The models should help analyze and harmonize the current work processes. � The models should be used as a procedural tool in everyday work. � The models should support the use of the software Q application. 12 6 6
TDT4250 – Modeling of Information Systems Autumn 2006 Identified modeling tasks and roles Modeling task Model developers Model interpreter 1 Visualize processes for communication 1.1 Model harmonized process Process modeler Worker , Tool user Process owner Tool super user Process owner Software designer 1.2 Model local process for comparison Process owner, Process owner Process developer Local user Local worker 2 Analyze processes for Corporate process owner Process owner improvements Local operating manager 3. Manual Activation of model 3.1 Learning the job “Doers” Worker training 3.2 Assisting job performance Doers a) workers b) managers c) planners d) admin. 3.3 Learning the tool Tool super user Tool super user Q Tool User 3.4 Assistance in the use of the tool 4. Use model as basis for Process modeler, Software designer 13 tool development TDT4250 – Modeling of Information Systems Autumn 2006 Identified modeling tasks and roles Modeling task Model developers Model interpreter 1 Visualize processes for communication 1.1 Model harmonized process Process modeler Worker , Tool user Process owner Tool super user Process owner Software designer 1.2 Model local process for comparison Process owner, Process owner Process developer Local user Local worker 2 Analyze processes for Corporate process owner Process owner improvements Local operating manager 3. Manual Activation of model 3.1 Learning the job “Doers” Worker training 3.2 Assisting job performance Doers a) workers b) managers c) planners d) admin. 3.3 Learning the tool Tool super user Tool super user Q Tool User 3.4 Assistance in the use of the tool 4. Use model as basis for Process modeler, Software designer 14 tool development 7 7
TDT4250 – Modeling of Information Systems Autumn 2006 Development of modeling language Main candidate: METIS and METIS ITM (IT-management) – company standard � (other options; Continue with Visio, UML, METIS ABM, EEML) Remodelled the IDEF0 models from Visio, including information from word- � documents and Excel spreadsheets Clarified requirements to new language based on the prioritized areas � Included representatives of main types of model developers and model interpreters � Implemented new modelling language � � Reduced the number of sub-languages (from 27 to 4 domains) Reduced the number of concepts within each of the 4 sub-languages � Added some new relationships and properties (some of which where derived) � Updated visual appearance on some symbols � Tried to minimize difference from METIS ITM to ensure model interoperability within the � organization Iterations of new versions of the language and practical use of it � Analytical evaluation based on quality framework (language quality) � Empirical framework through modelling addittional areas of the business � CR list maintained as new needs and wishes arose among the users � Recast the overall process model in this language � Q Developed model views to suit the needs of the different stakeholders � Language grammar management � 15 TDT4250 – Modeling of Information Systems Autumn 2006 Language quality evaluation Domain appropriateness. The language has been � developed exactly to cater for the domain of use, and to exclude concepts not in the domain. The domain appropriateness has been validated through remodeling the existing models, and further developing these based on current needs in the organization. Extensions to the language are easy to do if new needs arise in the future. Participant appropriateness. The language was based � on the concepts already in use in the organization, and should thus be easy to learn. In practice it turned out that although some people in the organization was used to think in this way, for others there was a learning curve Modeler appropriateness. As indicated above the � language was made using familiar concepts. In addition some of the graphical notation was made specifically to fit the current organization. Q 16 8 8
Recommend
More recommend
