January 11, 2007Russ Abbott Complex systems are no longer mysterious.Complex systems are no longer mysterious. We have a broad consensus aboutWe have a.

Slides:



Advertisements
Similar presentations
An introduction to complexity in Management Science: a personal view Mike Pidd Management Science
Advertisements

Design Project (Last updated: Nov. 22/2010) Change since August 31: added the notes to the presentation in the next slide.
AuthorAID Workshop on Research Writing Nepal March 2011.
Multimedia Specification Design and Production 2013 / Semester 1 / week 7 Lecturer: Dr. Nikos Gazepidis
Finance | Ralfi Vanlaethem | 5 May 2008 | 1 5 May 2008Finance | Ralfi Vanlaethem1 Fortis Group 5 th of May 2008.
First volume was published in We publish twice a year. Older volumes are available online at Ole Miss’ library (except for the most recent three.
Project Management Workshop. Nick Cook  Citigroup Corporate and Investment Bank  European Technology Business Office Manager Edinburgh University April.
Not a mystery any more. Complex Systems Engineering Not a mystery any more. It’s time to put complex systems to work.
Complex Systems CoP Complex System Engineering R. Abbott Corporate Chief Architect/Engineer Division (Rotation) 19 April 2007.
January 11, 2007Russ Abbott Complex systems are no longer mysterious.Complex systems are no longer mysterious. We have a broad consensus aboutWe have a.
Chien Hsing James Wu David Gottesman Andrew Landahl.
Knowledge Acquisitioning. Definition The transfer and transformation of potential problem solving expertise from some knowledge source to a program.
January 11, 2007Russ Abbott Complex systems are no longer mysterious.Complex systems are no longer mysterious. We have a broad consensus aboutWe have a.
We have a broad consensus about what we mean by a c omplex system.We have a broad consensus about what we mean by a c omplex system. They are not a mystery.
January 11, 2007Russ Abbott Complex systems are no longer mysterious.Complex systems are no longer mysterious. We have a broad consensus aboutWe have a.
January 11, 2007Russ Abbott Complex systems are no longer mysterious.Complex systems are no longer mysterious. We have a broad consensus aboutWe have a.
Complex systems are no longer mysterious.Complex systems are no longer mysterious. We have a broad consensus aboutWe have a broad consensus about –what.
Title and Authors of the Paper you reviewed goes here Your name goes here.
Architectural Design Principles. Outline  Architectural level of design The design of the system in terms of components and connectors and their arrangements.
Complex systems are no longer mysterious.Complex systems are no longer mysterious. We have a broad consensus aboutWe have a broad consensus about –what.
We have a broad consensus about what we mean by a c omplex system.We have a broad consensus about what we mean by a c omplex system. They are not a mystery.
We have a broad consensus about what we mean by a c omplex system.We have a broad consensus about what we mean by a c omplex system. They are not a mystery.
The Unified Modeling Language (UML) Class Diagrams.
COMP313A Programming Languages Introduction. More Housekeeping Stuff Reading Material Textbook –Programming Languages: Principles and Practice by Kenneth.
Software Engineering 2003 Jyrki Nummenmaa 1 USE CASES In this lecture: Use cases - What are use cases? - Why to use use cases? - How to write.
Resolving Unique and Persistent Identifiers for Digital Objects Why Worry About Identifiers? Individuals and organizations, including governments and businesses,
Chapter 7 Designing Classes. Class Design When we are developing a piece of software, we want to design the software We don’t want to just sit down and.
Why Analysis Process Refer to earlier chapters Models what the system will do makes it easier for understanding no environment considered (hence, system.
Petter Nielsen Information Systems/IFI/UiO 1 Software Prototyping.
OHTO -99 SOFTWARE ENGINEERING LECTURE 5 Today: - An overview to OO Analysis and OO Design - Introduction of Assignment 2.
Invitation to Computer Science, Java Version, Second Edition.
CS CS 5150 Software Engineering Lecture 3 Software Processes 2.
11 Chapter 11 Object-Oriented Databases Database Systems: Design, Implementation, and Management 4th Edition Peter Rob & Carlos Coronel.
LOGO The 4 th Electronic International Interdisciplinary Conference EIIC 2015 August , 2015 [please insert title of your paper here]
CS 4310: Software Engineering Lecture 4 System Modeling The Analysis Stage.
Requirements as Usecases Capturing the REQUIREMENT ANALYSIS DESIGN IMPLEMENTATION TEST.
Software Engineering Principles. SE Principles Principles are statements describing desirable properties of the product and process.
SONIC-3: Creating Large Scale Installations & Deployments Andrew S. Neumann Principal Engineer, Progress Sonic.
Webinar 13: Implementation Barriers. Summary of Last Week’s Call Making the debriefing count: The McLeod Experience Tips on engaging your colleagues when.
Example: object diagram for Scheduler, v What is wrong with this diagram? Seems like a lot of similarity between Task and UnplannedTask Can use.
1 CMPT 275 High Level Design Phase Modularization.
The Rational Unified Process 1 EECS810: Software Engineering.
SONIC-3: Creating Large Scale Installations & Deployments Andrew S. Neumann Principal Engineer Progress Sonic.
1 OO Analysis & Design - Introduction to main ideas in OO Analysis & design - Practical experience in applying ideas.
1 Database Systems Entity Relationship (E-R) Modeling.
February 8, 2006copyright Thomas Pole , all rights reserved 1 Lecture 3: Reusable Software Packaging: Source Code and Text Chapter 2: Dealing.
Lecture 4 Page 1 CS 111 Online Modularity and Virtualization CS 111 On-Line MS Program Operating Systems Peter Reiher.
INFO 620Lecture #71 Information Systems Analysis and Design Design Class Diagrams and others INFO 620 Glenn Booker.
Instructional Leadership for Complex Instruction EBCC Symposium January 27, 2012.
Analysis Yaodong Bi. Introduction to Analysis Purposes of Analysis – Resolve issues related to interference, concurrency, and conflicts among use cases.
How Web Servers Work Put Your Name Here Class Period: Date:
Bits don’t have error bars Russ Abbott Department of Computer Science California State University, Los Angeles.
Bits don’t have error bars Russ Abbott Department of Computer Science California State University, Los Angeles.
1 Sobah Abbas Petersen Adjunct Associate Professor, NTNU Researcher, Sintef TDT4252 Modelling of Information Systems Advanced Course TDT4252,
Chapter 10 Software quality. This chapter discusses n Some important properties we want our system to have, specifically correctness and maintainability.
© 2015 ASPCA ®. All Rights Reserved. Succession Planning & People Development Practical Tools for Managers Cheryl Bucci - Vice President, Human Resources.
Object-Oriented Programming
Method – Notation 8 Hours.
Modularity Most useful abstractions an OS wants to offer can’t be directly realized by hardware Modularity is one technique the OS uses to provide better.
CompSci 280 S Introduction to Software Development
Software Engineering Lecture 4 System Modeling The Analysis Stage.
Copyright © 2014 Hassan Gomaa and Robert Pettit
Engineering and Debugging an App Chapter 15
Apply Expert, Creator, Controller, Low Coupling, High Cohesion
Quantum Computers Superposition Interference Entanglement and Quantum Error Correction Lesson 1 By: Professor Lili Saghafi
Unit/Organization Name or Event
Final Report Structure
CMNS 110: Term paper research
Software Analysis.
Logical Architecture & UML Package Diagrams
Presentation transcript:

January 11, 2007Russ Abbott Complex systems are no longer mysterious.Complex systems are no longer mysterious. We have a broad consensus aboutWe have a broad consensus about –what we mean by a complex system, –what their properties are, and –how they operate. It’s time to put complex systems to work.It’s time to put complex systems to work.

January 11, 2007Russ Abbott Multi-scalar, i.e., multiple levels of abstractionMulti-scalar, i.e., multiple levels of abstraction –IT systems involve quantum physics, solid-state electronics, gates & logic, software (often many levels), CONOPs, … –Prone to phase transitions/chaos: small change → big effect. –Each level illustrates emergence, sometimes planned sometime unplanned. If the system involves real physical stuff …If the system involves real physical stuff … –No useful bottom level. Quarks? Quantum waves? Strings? Hence no good models of evolutionary arms races.Hence no good models of evolutionary arms races. –The levels cannot be completely isolated from each other … or we would have magic, i.e., new sources of causation, e.g., vitalism.or we would have magic, i.e., new sources of causation, e.g., vitalism. except when implemented in software.except when implemented in software. Includes “loosely coupled” components with a certain degree of autonomy, e.g., agents.Includes “loosely coupled” components with a certain degree of autonomy, e.g., agents.

January 11, 2007Russ Abbott Intimately entangled with its environment.Intimately entangled with its environment. –Built to interact with its environment—to do something in the world. –Can often be controlled/manipulated by modifying its environment. Each level of abstraction is often a multi-sided platform.Each level of abstraction is often a multi-sided platform. –A shopping center, an operating system, a browser, a standard. –Whoever owns it controls it! (See governance below.) Boundaries are deliberately permeable and indistinct.Boundaries are deliberately permeable and indistinct. –Must extract energy from its environment to persist. (“Far from equilibrium.”) –Societies (of internal and external “agents”); not monolithic structures. System of systems; the operator goes home; a new president is elected.System of systems; the operator goes home; a new president is elected. Must adapt to a continually changing environmentMust adapt to a continually changing environment –The environment continually adapts to it. –Simultaneously (a) deployed and (b) under development and self-repair. e.g., us (you and me), a government, a corporation, Wikipedia.e.g., us (you and me), a government, a corporation, Wikipedia. –A social entity; hardware and software are only bones and nerves. –Requires a well thought out governance structure.

January 11, 2007Russ Abbott To refine, clarify, and formalize them.To refine, clarify, and formalize them. To evangelize.To evangelize. –To make them intuitive, commonplace, and everyday—a part of everyone’s vernacular. To use them to conceptualize our systems.To use them to conceptualize our systems. To make them operational.To make them operational. –To adapt them to practice in building real systems. –To create development processes based on them. –To build tools that allow anyone to use them.

January 11, 2007Russ Abbott This is an interdisciplinary symposiumThis is an interdisciplinary symposium Most of us are not expert in many of the issues discussed in the papers.Most of us are not expert in many of the issues discussed in the papers. –What’s obvious to you may be a complete mystery to me—and vice versa. Don’t be afraid to ask for simplified explanations or to ask, “What questions motivate you?”Don’t be afraid to ask for simplified explanations or to ask, “What questions motivate you?” We are here to learn from each other.We are here to learn from each other.

January 11, 2007Russ Abbott Introductions: name, affiliation, interests.Introductions: name, affiliation, interests. –Spend a couple of minutes each on your interests so that we get to know each other. Author overviews: 5-10 minutes.Author overviews: 5-10 minutes. –The elevator version for non-specialists. What are the big ideas in your paper?What are the big ideas in your paper? What are the intuitions you want to get across?What are the intuitions you want to get across? Discussion.Discussion. –How do the papers relate complex systems to systems engineering? –How do they relate to your work?

January 11, 2007Russ Abbott Wiley’s Complexity is one of the premier journals in Complex Systems.Wiley’s Complexity is one of the premier journals in Complex Systems. Alfred Hubler, Executive Editor, is one of our participants.Alfred Hubler, Executive Editor, is one of our participants. He has suggested a special issue of papers related to this symposium.He has suggested a special issue of papers related to this symposium. If you want to submit a paper, please send it to me by March 4.If you want to submit a paper, please send it to me by March