TDT4252 Modelling of Information Systems Advanced Course

Transcription

1 1 TDT4252 Modelling of Information Systems Advanced Course Sobah Abbas Petersen Adjunct Associate Professor

2 2 Today s Lecture AKM in Industry: an example Purpose: To describe an approach of how AKM can be applied in an enterprise or business network setting. Based on: Lecture slides from Spring 2009, by John Krogstie and a presentation by Håvard Jørgensen, Commitment AS Based on: Lillehagen and Krogstie (2008), Chapters 7, Springer-Verlag, Berlin, Heidelberg. pp

3 3 Customer Problem Approaches Customer problem analysis; - from strategic planning, to competence and operational problem solving problem decides main focus! Target setting based on analysis steady improvements or radical changes based on new ways of working, decides ambition of project. Level of ambition Modelling for understanding and learning Modelling for role-specific work process improvement Modelling for new ways of designing and engineering solutions Modelling to support active knowledge driven continuous solutions Critical factors Urgency wrt. market demand, trends, and competition Available resources and return of investment (ROI) analyses Degree of customer personell involvement Avoiding technology islands, become IT expert independent

4 4 Project Approach / Methodology Concept Scaffolding Scenario modeling Solution configuration Platform integration Platform delivery Performing Concept, exploring main objectives and overall solution approaches Scaffolding creates an overview of current ways of working Scenarios are developed in close interaction with users Solution configuration defines views and workplaces Platform configuration integrates pre-existing applications and data Platform delivery includes training and practicing Performing agile business, continuously adapting and extending the solution

5 5 Knowledge Architecture Driven Approach Top-down modeling Knowledge architecture Middle-up-down modeling Continuous extension Bottom-up Modeling Concept Scaffolding Scenarios Solutions Configuration Platform Integration Platform Delivery Performance Improvement Customer Delivery Process

6 6 Requiremen t Component Is reflected in Design concept User Solution Model Variant parameter Structural Rule Technical constraint Solution Configuration Model Informatio n Role Task View Support s User team Solution configuration team Concurrent Teamworking Configures Configurable Product Platforms Configurable Visual Workplaces Software development Configurable Task Patterns Configurable Rule Execution Is reflected in Infrastructure team EKA Model Repository

7 7 Developing the Active Knowledge Architecture - AKA Building layers of reflective methodic and operational knowledge Customer Users - designers Customer Delivery Platform Methods Engineers Suppliers &Service Providers Partnering Innovation Platform Modelling Facilitator AKM Modelling CPPD Components AKA Methodology Platform Core Software Platform AKM Software Components Systems Integrator System Integration Platform Systems Engineer The AKA, Partnering Innovation and Customer Delivery Platforms must be developed in a teaming effort applying the IRTV language, capturing POPS, and other views!

8 8 The Role of Partners AKM defines a library of basic elements Information elements (basic types used for modeling) Tasks (edit object, relate objects, define structure, define interface etc.) Views (for each of the generic tasks, adapted to information element type) Roles (responsible, manager, customer etc.) Methodology & service providers should define Task patterns with roles Views for each task... still on a rather generic level, e.g. independently of concrete information content? User teams should define Concrete task patterns with roles Concrete information structures Possibly customise existing views

9 9 1. Concept Selection Capture the main objectives and challenges Experiment with existing concepts Make the users familiar with modeling Trigger discussions about opportunities Existing solution concepts Previous projects Methodologies already in use by the company Methodologies in use in the industry AKM methodologies for e.g. product design Concept Scaffolding Scenario modeling Solution configuration Platform integration Platform delivery Performing

10 10 Objectives Model Example An instantiated model

11 11 Objectives and Issues Metamodel

12 12 Solution Concepts Metamodel

13 13 Argumentation Metamodel

14 14 Decision Metamodel

15 15 2. Scaffolding - Get an Overview Capture the domain as an active knowledge model The stakeholders and roles The main tasks they perform The information they use and produce Main views and perspectives Raise the customer s understanding of modelling. Suggested to proceed with the analysis mainly in the above order. Top-down modeling Concept Scaffolding Scenario modeling Solution configuration Platform integration Platform delivery Performing

16 16 Scaffolding Model

17 17 Key Questions for the Modeling Session Information What information do you need to perform your work? What is hard to find today? Roles Who do you collaborate with, on what? What is their expertise? Tasks What do you do? What are your responsibilities? Views What should your workplace on the computer look like? What should it contain?

18 18 Scenario modelling Modelling the core competences of the enterprise as work-processes for execution as task patterns. Scoping, select a narrower set of Roles Tasks that the further analysis should focus on Which workplaces to demonstrate Which people to involve in the modelling Criteria for selection Demonstrate holistic approach, but simplified Concrete case if possible Assess benefits and values Reuse and adapt existing solution concepts Bottom-up Modeling Concept Scaffolding Scenario modeling Solution configuration Platform integration Platform delivery Performing

19 19 Build Scenario Models Detailed modelling of the selected scope: Information structures from documents Tasks from project handbook Interviews and discussions with stakeholders Add context Where does the information come from? Who do we need to communicate with? How will the information we produce here be used, by who, when, to do what? Main need to narrow the scope. UML Use case modeling: Similar approach with roles and tasks

20 20 Refined Model of Scope Selected roles Decomposition of concept selection tasks for selected roles Outlining the main views (status of information) Defining the main technical concepts elaborated during the work

21 21 Detailed Information Analysis As-is, for every role Which information do they process? Which information do they send to others? Which information do they receive from others? Which information do they own? How much do they see of the work of others and the discussion in other engineering disciplines? In which areas do they propose new solution alternatives? To-be views Needs and opportunities for improved knowledge sharing and interdisciplinary collaboration

22 22 Role Views (Initial)

23 23 Role Views (Improved)

24 24 Solution Configuration Middle-up-down To externalise holistic and pragmatic enterprise knowledge and to present it in an Enterprise Knowledge Architecture. Define workplaces and views for selected users. Define templates Information templates Objects with properties and parameters Reusable structures Patterns of relationships to be managed Task pattern templates Interactive tasks performed by users in model-configured views Workflow processes, event-driven tasks Scripts Modelled rules Define initial model content, test data Users Project data Concept Scaffolding modeling Scenario modeling Solution configuration Platform integration Platform delivery Performing

25 25 Solution Modelling Modelling Aspects Business Process hierarchy (top down) Work Processes (bottom up). Task patterns that are modelled already are adapted. Task patterns are linked to process hierarchy. Develop common views among stakeholders (middleout). Product modelling (lifecycle aspects, components, etc.). Product structures conceptual design of products. Organisational modelling: competences, responsibilities, etc.

26 26 Model-Configured Workplace Workplace for Role Available tasks in view Available tasks for person/role Information elements filtered for role, task, view View for performing a task on an object

27 27 View Modeling View: Defines what to show in which context. Context Information content Roles of current user Task being performed And related tasks available as services Two main types of views Dynamic views defined as queries Static views

28 28 Visual Queries The objects to show are parts of the query object The primary objects have a member relationship from the query object Secondary objects to include if they are linked to the primary

29 29 Visual Queries - Paths Paths consisting og multiple links may be applied. Objects are included if they are members of the type in the criteria. And the relationship that links the objects is a member of the relationship type used in the query. Recursive paths are allowed.

30 30 Visual Queries Property Values Property criteria may be added Use the has criteria relationship type

31 31 Visual Queries My tasks Objects linked to the current context may be selected Current task Current project Current user Current information element Use the Current as the name of the object

32 32 Platform Configuration Integrating other systems and tools by modelling other systems data models and other aspects, often expressed as UML models. Concept Scaffolding Scenario modeling Solution configuration Platform integration Platform delivery Performing

33 33 Platform Delivery Continuous extension Adapts services to continuous growth and change by providing services to perform extensions and still keep consistency and compliance across platforms and networks. Concept Scaffolding Scenario modeling Solution configuration Platform integration Platform delivery Performing

34 34 Performance Improvement Continuous extension Continuously performing improvements and adaptations and providing services to semiautomatically adjust models. Re-generate model-configured and modelgenerated workspaces and services, tuning solutions to produce the desired effects. Concept Scaffolding Scenario modeling Solution configuration Platform integration Platform delivery Performing

35 35 Summary Concept A method to use AKM in industry. Model to capture the enterprise knowledge. Generate views using the model. Scaffolding Scenario modeling Solution configuration Platform integration Platform delivery Performing

36 36 Next Lecture Monday 21 march 2011, 15-17hrs Introduction to Enterprise Architecture Based on: Roger Sessions, A Comparison of the Top Four Enterprise-Architecture Methodologies, ObjectWatch, White paper, May Zachman s Framework,