Ce diaporama a bien été signalé.
Nous utilisons votre profil LinkedIn et vos données d’activité pour vous proposer des publicités personnalisées et pertinentes. Vous pouvez changer vos préférences de publicités à tout moment.
Visual Modeling Editor and Ontology API-based 
Analysis for Decision Making in 
Enterprises- Experience and Way Ahead 
Sag...
Motivation 
Change Drivers 
Enterprise 
Evolving Market Conditions 
Competitive Pressure 
Technology Obsolescence and Adva...
Change Drivers 
Enterprise 
AS-IS 
Internal 
External 
Enterprise 
TO-BE 
Reliance on 
Expert 
Document-oriented 
Normal 
...
Our Initial Approach 
Change Drivers 
Enterprise 
AS-IS 
Internal 
External 
Enterprise 
TO-BE 
Using 
Purpose-specific 
M...
Solution Iteration 1 
Enterprise 
AS-IS 
EA-based 
Descriptive 
Models 
[ArchiMate] 
Prescriptive Intentional 
Models [i*]...
Solution Iteration 1 
Archi OpenOME 
Enterprise 
AS-IS 
Enterprise 
TO-BE 
EA-based 
Descriptive 
Models 
[ArchiMate] 
Pre...
Solution Iteration 1 
Archi OpenOME 
Enterprise 
AS-IS 
Strategic 
Alternatives 
Enterprise 
TO-BE 
Enterprise 
Entities 
...
Solution Iteration 1 
 ArchiMate motivation extensions provide goal modeling 
constructs 
– At a very high level- Goals, ...
Reflection 1 
Archi OpenOME 
Enterprise 
AS-IS 
Strategic 
Alternatives 
Enterprise 
TO-BE 
Enterprise 
Entities 
Problem-...
Extended Archi 
with requisite 
concepts for 
Visual Models + 
Ontology with 
ArchiMate + i* 
concepts for 
analyzable mod...
Extended Archi 
with requisite 
concepts for 
Visual Models + 
Ontology with 
ArchiMate + i* 
concepts for 
analyzable mod...
Future Solution Iteration 3 
Extended 
Enterprise 
Metamodel 
Model 
Conforms To 
Visual 
Modeling 
Analysis 
Extended Arc...
Features of Solution Iteration 3 
Modeling/Analysis 
Feature 
Archi (Eclipse 
EMF) 
Adex Required For 
Metamodeling Yes Ye...
(Pre) Reflections on Solution Iteration 3 
 Scoping EA models 
− Modeling enterprise without a clear problem definition i...
Questions? 
I can be reached at sagar.sunkle@tcs.com
Prochain SlideShare
Chargement dans…5
×

Visual Modeling Editor and Ontology API-based Analysis for Decision Making in Enterprises- Experience and Way Ahead

527 vues

Publié le

To stay competitive in dynamic environment, enterprises need to be able to efficiently and effectively respond to changes. Both visual modeling and programmable analysis support is needed for modeling a) motivations behind and goals in response to change, b) the AS-IS state of enterprise, c) possible TO-BE states, and d) operationalization model that captures paths from AS-IS to desired TO-BE states, in a scalable way. We recount our earlier, ongoing, and proposed approaches for tooling in this regards using situation, task, action, results, and reflections structure. Initial research suggests that reflections from past and ongoing experience may help us in extrapolating ways in which our proprietary metamodeling framework may be put to best use for scalable modeling and analysis of enterprise's decision making models.

Publié dans : Logiciels
  • Soyez le premier à commenter

  • Soyez le premier à aimer ceci

Visual Modeling Editor and Ontology API-based Analysis for Decision Making in Enterprises- Experience and Way Ahead

  1. 1. Visual Modeling Editor and Ontology API-based Analysis for Decision Making in Enterprises- Experience and Way Ahead Sagar Sunkle and Hemant Rathod Tata Research Development and Design Center, Pune, India.
  2. 2. Motivation Change Drivers Enterprise Evolving Market Conditions Competitive Pressure Technology Obsolescence and Advance Dynamic Supply Chains Regulatory Compliances Internal External
  3. 3. Change Drivers Enterprise AS-IS Internal External Enterprise TO-BE Reliance on Expert Document-oriented Normal Practice Motivation
  4. 4. Our Initial Approach Change Drivers Enterprise AS-IS Internal External Enterprise TO-BE Using Purpose-specific Models For Both Business-As-Usual Improvement/Transformation
  5. 5. Solution Iteration 1 Enterprise AS-IS EA-based Descriptive Models [ArchiMate] Prescriptive Intentional Models [i*] Not just a soft approach! Enterprise TO-BE Change Drivers Internal External
  6. 6. Solution Iteration 1 Archi OpenOME Enterprise AS-IS Enterprise TO-BE EA-based Descriptive Models [ArchiMate] Prescriptive Intentional Models [i*] Not just a soft approach! Change Drivers Internal External
  7. 7. Solution Iteration 1 Archi OpenOME Enterprise AS-IS Strategic Alternatives Enterprise TO-BE Enterprise Entities Problem-specific Models Actors and tasks for TO-BE operationalization Change Drivers Internal External
  8. 8. Solution Iteration 1  ArchiMate motivation extensions provide goal modeling constructs – At a very high level- Goals, Assessment, Drivers- but no goal modeling specific syntax or semantics – i* provides well constructed goal/intention modeling syntax and semantics ArchiMate + Intentional Models
  9. 9. Reflection 1 Archi OpenOME Enterprise AS-IS Strategic Alternatives Enterprise TO-BE Enterprise Entities Problem-specific Models Actors and tasks for TO-BE operationalization Two Problems !! Difficult to keep Archi[ArchiMate] and OpenOME[i*] models in sync Each purposive model needs specific tool Change Drivers Internal External
  10. 10. Extended Archi with requisite concepts for Visual Models + Ontology with ArchiMate + i* concepts for analyzable models From Visual Models to analyzable Export Import models .csv .xlsx .owl Protégé editor, Jena OWL ontology API, Pellet Reasoner API, SPARQL query language Solution Iteration 2
  11. 11. Extended Archi with requisite concepts for Visual Models + Ontology with ArchiMate + i* concepts for analyzable models Reflection 2  Possible to model “Why + What + How”  Ontological representation for constructing enterprise and intentional analyses − EA Change Impact Analysis- Change ripples computed based on semantics attributed to ArchiMate relations − EA Landscape Mapping- Retrieving specific pairs of EA elements from EA model- set of business processes, application services they use, and business services that expose the functionality in business processes − Intentional Analyses- Label propagation for computing relative strengths of alternatives, aggregate analyses such as ability, workability, and viability of a course of action  Combined EA + Intentional analyses − How to execute best strategic alternative on top of AS-IS EA  Idea validated, but scalability and modeling facility remain an issue
  12. 12. Future Solution Iteration 3 Extended Enterprise Metamodel Model Conforms To Visual Modeling Analysis Extended Archi Extended Enterprise Metamodel Model Visual Modeling Analysis ADEX Conforms To Ontology Symbol Designer OMGen
  13. 13. Features of Solution Iteration 3 Modeling/Analysis Feature Archi (Eclipse EMF) Adex Required For Metamodeling Yes Yes Purpose-specific modeling extensions e.g. simulation of enterprise models Visual Modeling Yes Yes Representing visual syntax agreed upon by community Scripting No [EMFScript and other] Yes [OMGen] For programming purpose-specific analyses Database Support XML, CSV File, in memory, MySQL, Oracle etc. Supporting modeling and analysis lifecycle including role-based access to modeling artifacts, and versioning Multi-user/Role Support Versioning NO Yes Diff-Merge
  14. 14. (Pre) Reflections on Solution Iteration 3  Scoping EA models − Modeling enterprise without a clear problem definition is futile- intentional models help define the problem and possible solutions  Adjusting syntax of purpose-specific modeling languages − Enterprise and related models should focus mainly on analysis and lead to decision execution − Accordingly, standard syntax of modeling languages may need tweaking  Enabling domain experts − So far, interaction was team of modelers who knew modeling languages + domain experts-very difficult to make domain experts spare time − Could domain experts model on their own as a matter of practice? − Then they have to learn at least the domain-specific language syntax but this should be OK • Could domain vocabularies + rules help? − Not only to enable different modeling languages talk with each other − But also toward creating models of domain which could then be analyzed purposively
  15. 15. Questions? I can be reached at sagar.sunkle@tcs.com

×