Home > Complexity
Complexity
Links
Urban and Enterprise Architectures: A Cross-Disciplinary Look at Complexityhttp://www.objectwatch.com/white_papers.htm#SessionsSalingaros Roger Sessions and Nikos A. Salingaros: Complexity is a major problem in enterprise architecture. Complexity obstructs business/IT alignment. Complexity obscures project vision. Complexity delays schedules, drives cost overruns, and hinders delivery of value. For enterprise architecture, complexity is the enemy. Complexity is also a problem for urban architecture. In urban architecture complexity causes habitats that are destructive to the human psyche. Complexity can cause a variety of stress responses such as increased heart rate, sweating, and pupil dilation. For urban architecture, complexity is not just a matter of aesthetics; it is a matter of social wellbeing. Although the symptoms of unmanaged complexity differ in these two fields, the laws governing architectural complexity are universal. Successful architectures follow the same basic principles whether those architectures describe biological, urban, or enterprise systems. And in all cases, the cost of ignoring these principles is disorder, dissolution, and ultimately chaos. This cross-disciplinary paper explores the universal principles of controlling complexity and draws on lessons from urban architecture to better understand how to design successful enterprise architecture.- Complexity - Enterprise Architecture - |
From induction to abduction, a new approach to research and productive inquiryVideos from seminar with Dave Snowden, Founder & Chief Scientific Officer Cognitive Edge Pte Ltd. Tuesday February 9th 2010- Knowledge Management - Complexity - |
Complexity, chaos and enterprise-architecturehttp://weblog.tomgraves.org/index.php/2010/02/19/complexity-chaos-and-ea/ Tom Graves: Courtesy of a link by fellow enterprise-architect Sally Bean, I've just spent the past couple of hours viewing and then reviewing an online seminar on complexity by one of the thought-leaders on complexity-theory and practice, Dave Snowden.- Complexity - Enterprise Architecture - |
Jamshid Gharajedaghi (2005)
The first edition of Systems Thinking was the first book to develop a working concept of systems theory and to deal operationally with systems methodology. The author has been working for the last 5 years to incorporate parallel development in quantum theory, self-organizing systems and complexity theory, the sum of which is included in this new 2nd edition. He has tested these concepts with 200 executive MBA students, and also with Russell Ackoff, one of the founding fathers of systems thinking. Ackoff reported that it was the most comprehensive systems methodology he has seen. The 2nd edition features the synthesis of holistic thinking (iteration of structure, function and process), operational thinking (understanding chaos and complexity), sociocultural systems (movement toward a predefined order), and interactive design (redesigning the future and inventing ways to bring it about). Also added are the operational thinking and self-organizing aspect of sociocultural systems, with updates made to the holistic thinking and interactive design parts to incorporate recent new developments.
|
|
Roger Sessions (2008)
Dismantle the overwhelming complexity in your IT projects with strategies and real-world examples from a leading expert on enterprise architecture. This guide describes best practices for creating an efficient IT organization that consistently delivers on time, on budget, and in line with business needs. IT systems have become too complex - and too expensive. Complexity can create delays, cost overruns, and outcomes that do not meet business requirements. The resulting losses can impact your entire company. This guide demonstrates that, contrary to popular belief, complex problems demand simple solutions. The author believes that 50 percent of the complexity of a typical IT project can and should be eliminated - and he shows you how to do it. You’ll learn a model for understanding complexity, the three tenets of complexity control, and how to apply specific techniques such as checking architectures for validity. Find out how the author’s methodology could have saved a real-world IT project that went off track, and ways to implement his solutions in a variety of situations.
|
|



