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

Ch:8 Design Concepts S.W Design should have following quality attribute: Functionality Usability Reliability Performance Supportability (extensibility,
Stereotypes & Framework in conceptual architecture Lecture
[ §4 : 1 ] 4. Requirements Processes I Overview 4.1Fundamentals 4.2Elicitation 4.3Specification 4.4Verification 4.5Validation Requirements Definition Document.
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.
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.
1 Introduction to Complex Systems: How to think like nature Russ Abbott Sr. Engr. Spec. Rotn to CCAE  The.
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.
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.
Emergence Explained Russ Abbott Dept. of Computer Science California State University, Los Angeles and The Aerospace Corporation What’s right and what’s.
UML Sequence Diagrams Eileen Kraemer CSE 335 Michigan State University.
Russ Abbott Dept. of Computer Science California State University, Los Angeles and The Aerospace Corporation Unused Slides from the UCLA HCS Conference.
January 11, 2007Russ Abbott Complex systems are no longer mysterious.Complex systems are no longer mysterious. We have a broad consensus aboutWe have a.
Department of Computer Science 1 CSS 496 Business Process Re-engineering for BS(CS)
The Unified Modeling Language (UML) Class Diagrams.
UML Sequence Diagrams Michael L. Collard, Ph.D. Department of Computer Science Kent State University.
COMP313A Programming Languages Introduction. More Housekeeping Stuff Reading Material Textbook –Programming Languages: Principles and Practice by Kenneth.
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.
UFCEUS-20-2 : Web Programming Lecture 5 : Object Oriented PHP (1)
Why Analysis Process Refer to earlier chapters Models what the system will do makes it easier for understanding no environment considered (hence, system.
Two notions of biological hierarchy John Collier University of KwaZulu-Natal
Petter Nielsen Information Systems/IFI/UiO 1 Software Prototyping.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 19 Slide 1 Component-based software engineering 1.
University of Utah SoCCS Lecture 61 Architecture – An Introduction CS Lecture 6 Nathan Dykman.
9/10/2012ISC 329 Isabelle Bichindaritz1 Entity Relationship (E-R) Modeling.
Software Processes lecture 8. Topics covered Software process models Process iteration Process activities The Rational Unified Process Computer-aided.
CS CS 5150 Software Engineering Lecture 3 Software Processes 2.
1 CMPT 275 Software Engineering Requirements Analysis Phase Requirements Analysis Activity (Identifying Objects, Scenarios) Janice Regan,
11 Chapter 11 Object-Oriented Databases Database Systems: Design, Implementation, and Management 4th Edition Peter Rob & Carlos Coronel.
SOFTWARE DESIGN Design Concepts Design is a meaningful engineering representation of something that is to be built It can be traced to a customer’s requirements.
CS 4310: Software Engineering Lecture 4 System Modeling The Analysis Stage.
Requirements as Usecases Capturing the REQUIREMENT ANALYSIS DESIGN IMPLEMENTATION TEST.
Develop a Safety Assurance approach for Complex Systems (Problem Definition) Supervisors: Tim Kelly, Rob Alexander Chris Leong HISE Group Giving a Presentation.
Service Oriented Architecture CCT355H5 Professor Michael Jones Suezan Makkar.
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.
1 From Conceptual Models to Simulation Models Takashi Iba* Yoshiaki Matsuzawa** Nozomu Aoyama** * Faculty of Policy Management, Keio University ** Graduate.
Software Architectural Views By the end of this lecture, you will be able to: list and describe the views in the 4+1 view model of software architecture.
1 Database Systems Entity Relationship (E-R) Modeling.
INFO 620Lecture #71 Information Systems Analysis and Design Design Class Diagrams and others INFO 620 Glenn Booker.
Analysis Yaodong Bi. Introduction to Analysis Purposes of Analysis – Resolve issues related to interference, concurrency, and conflicts among use cases.
The Software Development Life Cycle: An Overview
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.
Gerhard Dueck -- CS3013Analysis 1. Gerhard Dueck -- CS3013Analysis 2 Why analysis?  Yield a more precise specification of the requirements.  Introduce.
Object Oriented Analysis and Design Introduction to Rational Rose.
Chapter 10 Software quality. This chapter discusses n Some important properties we want our system to have, specifically correctness and maintainability.
Getting the Architecture Right Jeffrey D. Taft, PhD Chief Architect for Electric Grid Transformation Pacific Northwest National Laboratory March 17, 2016.
Method – Notation 8 Hours.
Software Engineering Lecture 4 System Modeling The Analysis Stage.
Copyright © 2014 Hassan Gomaa and Robert Pettit
Common Design Patterns
Coupling and Cohesion 1.
Quantum Computers Superposition Interference Entanglement and Quantum Error Correction Lesson 1 By: Professor Lili Saghafi
Specifying collaborative decision-making systems
Java Messaging Service (JMS)
Java Messaging Service (JMS)
Appendix A Object-Oriented Analysis and Design
Software Analysis.
Object-Oriented PHP (1)
Appendix A Object-Oriented Analysis and Design
Appendix A Object-Oriented Analysis and Design
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 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