1. EASEAM RM-ODPALLOY UMLRM-ODPPart ,

2. RM-ODP Case Study8 10 3. EA: Enterprise Architecture- Enterprise - Enterprise -- system sciencesEA 4. EA:---xlets - 5. UML :Unified Modeling Language(Object Management Group) OMG .. C++,Java , C# 6. Alloy structural properties declaration syntax formula syntax OCL 7. RM-ODP: Reference-Model of Open distributedProcessing ITU-T ISO - - -distributed system description framework(OMA, Model Driven Architecture) OMG - -View Point - 8. RM-ODP Architecture 9. RM-ODP: Five Viewpoints SupportDifferent Concerns 10. RM-ODP: Viewpoints and Modeling Enterprise Viewpoint -Information Viewpoint -Computational Viewpoint -Engineering Viewpoint - Technology Viewpoint - 11. RM-ODP: Focus of Concern 12. 5SEAM: Systematic Enterprise Architecture MethodologyEA - TOGAF ADM (Architecture Development Method)- all US Government Frameworks include a methodology specificto their EAF (DODAF, FEAF, TEAF)- Gartner/Meta Methodology- EAP- EA Cube Method- SEAM 13. 5SEAM IT-SEAM SEAM SEAM -CAD 14. 5SEAM Philosophy SEAM -what is knowledge? -what exists? -what is right or correct?-- ontology EA 15. 5SEAM Philosophy Epistemology- Justification--constructivism principle-all knowledge is relative to the observer 16. 5SEAM Philosophy Ontology---RM-ODPCAD -Alloy- object, action, state, location in time, location in space - type , instance- 17. 5SEAM Philosophy: Ethics -SEAM - - - 18. 6RM-ODP Parts: ---Part RM-ODP -Overview -Foundations -Architecture - Architectural Semantics - 19. 6RM-ODP Parts: Part I Overview -ODP - ODP- ODPODP -- 20. 6RM-ODP Parts: Part II Foundations Specification - - ODP object, interface, object state and communication - ODP - 21. 6RM-ODP Parts: Part IIIArchitecture --:Viewpoints RM-ODP - enterprise, information, computational, engineering and technologyPart II -ODP 22. 6RM-ODP Parts: PartIV Architectural Semantics - ODP - Part II - 23. 7Hierarchy-Oriented Modeling of Enterprise Architecture usingRM-ODP 24. 7Abstract EA[ ] EARM-ODP ODPSeamCad EA RM-ODP SeamCad- SEAMEA 25. 7 Introduction SEAM and its RM-ODP Foundations Motivation Example Challenges in modeling EA hierarchically Leveraging RM-ODP and SEAM Building Block Illustration of building blocks in the Bookstore example Illustration of building blocks in the Bookstore example Illustration of building blocks in the Bookstore example Computational viewpoints Bindings Meta-Modeling and tool support Type and class Meta-Model of SeamCad Interpreting SEAM organizational level and functional level Toolkit Application and feedback 26. 7 Application A case-Study in a masters course on EA and SOA Enterprise model foe an ERP-seeking company in a market of watchparts manufacturing Designing EA with SEAM and SeamCad Lessons learned from building enterprise models in SeamCad Feedback from practitioners, researchers and student Protocol for obtaining users feedback Ratings Related work ODP-based work on Enterprise modeling Non-ODP enterprise modeling Software and System modeling 27. 7 3 Conclusion Contributions Discussions Future work 28. 29. Part II Object Part III RM-ODP View RM-ODP Part III 30. Application and Feedback RM-ODP 31. Enterprise modeling using the foundation concepts of the RM-ODP ISO/ITUstandard(2007)Modeling Distributed Computing Management through RM-ODP(2012)RM-ODP Part II - Concept RM-ODP Part II 32. CADprototypeSEAM SeamCadhttp:uow.edu.aulleSeamCad 33. RM-ODP Part IIRM-ODP , 34. RM-ODP Part II 35. view as compositeorganizational viewview as whole RM-ODPPart II,III 36. Viewpoints RM-ODPPart III 37. Case StudyLet us consider an example of a bookstorewhose management decides toprovide the companys services via the Internet. The management has agoal to specify the services that the bookstore can provide its customerswith and to describe how to implement them using business and ITresources. A book-selling market contains aBookValueNetworkandaCustomer. The value network consists of three companies: a bookstorecompany named BookCo(responsible for the service of processing theordersplaced bythecustomer),ashippingcompanycalledShipCo(responsible for shipping the books ordered) and apublishing companyPubCo(responsible for supplying the books that wereordered but not yet available in the inventory of the bookstore company).The departmental structure of the bookstore company shows twodepartments: one for coping with the purchasing data (PurchasingDep)and the other for managing an inventory of books (WarehouseDep). Wemight have an additional level showing the IT infrastructure of thesedepartments. 38. Case Study: 39. Case Study: 40. Case Study: 41. Case Study: 42. Case Study: 43. Case Study: 44. Case Study: 45. Case Study: 46. Case Study: 47. Case Study: 48. 11EA ITEA-