1 / 18

How to cope with Real World constraints in a Model Driven Reality

How to cope with Real World constraints in a Model Driven Reality. Hans Pronk and Roberto Uding. TU/e, 10 december 2008. Drs. Hans Pronk. Principal Consultant @ VKA Loves Business Architecture & Technology Blogs: http://www.hnzz.nl/ http://delicious.com/hnzz

tuyet
Download Presentation

How to cope with Real World constraints in a Model Driven Reality

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. How to cope with Real World constraints in a Model Driven Reality Hans Pronk and Roberto Uding TU/e, 10 december 2008

  2. Drs. Hans Pronk • Principal Consultant @ VKA • Loves Business Architecture & Technology • Blogs: • http://www.hnzz.nl/ • http://delicious.com/hnzz “The future is already here, it's just not widely distributed yet!” 2

  3. Drs. Roberto Uding • Consultant @ VKA • Loves Politics, Strategy, Organisational change & Technology • TOGAF Certified Architect • M.A. International Relations and Organisations (Groningen) • Yoga teacher 3

  4. Message of the Day • Enterprise Architects have a Holistic perspective on Human based systems. • Errors in human perspective ( Social & Technological) lead to errors in communication (language). This language is translated in models of system/software development and poses constraints. • Enterprise Architecture is like Area planning, where you set the stage, the rules & principles, and requirements for others to fill in the space. 4

  5. Contents of this presentation • What is Architecture? • So you Wanna be an Architect? • World views and perspectives • Language 5

  6. IEEE 1471 – What’s Architecture? • So, what is an architecture? We're not sure, but we know one when we see one. Seriously, it is a difficult concept to make precise. Perhaps this is not too surprising, given that the civil architecture community, with 5000 years or so of practice, has had little more success defining the architecture of a building. • Broadly speaking, an architecture is that which is essential or unifying about a system. It is that set of things about a system which largely determine the system's value, cost, and risk. The definition in the recommended practice is: • Architecture: the fundamental organization of a system embodied in its components, their relationships to each other and to the environment and the principles guiding its design and evolution. 6

  7. architecture is hard 7

  8. IEEE 1471 8

  9. Role of the Architect Executive Law Principles of construction Principles Models Standards Drivers Architect Contractor Form, Aesthetics & Beauty Functions Sustainability ( time horizon) 9

  10. So you wanna be Architect? 10

  11. View on the world: population 11

  12. Views on the world: age 100+ 12

  13. Views on the world: royalties & license fees exports 13

  14. Implementation Technical Business Functional Technical principles Businessprinciples Implementationprinciples Functionalprinciples Rationale Rationale Rationale Rationale Implications Implications Implications Implications Obstacles Obstacles Obstacles Obstacles Actions Actions Actions Actions Principles, Rationale and Trade-offs Business drivers Goals 14

  15. Driver:Competition is outstripping us on delivery Implementation view Business view Functional view Technical view Develop e-commerce capability Customersbrowse, check inventory, order, pay without help Use scripts, database to check inventoryand validity Use Microsoft based commercesystems Goal:Improve time-to- market Reduces order processing time Needed for e-commerce Customer must check inventory, make valid orders “Ramp-up” time is reduced Will have to partner to acquire needed expertise Needs modifications to IT infrastructure Requires 24 X 7 systemavailability Need to develop or outsource Beyond year’s budget No resourcesfor 24X7 support Compatibility,integration issues Limited skill set Survey customers Investigate partners Research db products Train resources 15

  16. Language 16 • Natural languages • the case of the missing/implicit ontology • viewpoints • Formal languages • standards • usage • algorithmic /declarative /rule-based

  17. Message of the Day • Enterprise Architects have a Holistic perspective on Human based systems. • Errors in human perspective ( Social & Technological) lead to errors in communication (language). This language is translated in models of system/software development and poses constraints. • Enterprise Architecture deals is like Area planning, where you set the stage, the rules & principles, and requirements for others to fill in the space. 17

  18. Links for further enjoyment • http://www.whitehouse.gov/omb/egov/a-2-EAModelsNEW2.html • http://www.opengroup.org/architecture/togaf8-doc/arch/ • http://www.archimate.org/en/about_archimate/ • http://www.via-nova-architectura.org/en • http://www.vka.nl/ • http://www.e-overheid.nl/home.html • http://www.demo.nl/ • http://www.dilbert.com/ • http://www.gregthearchitect.com/ • http://www.zachmaninternational.com/index.php/home-article/13#maincol 18

More Related