Complex systems are no longer mysterious.Complex systems are no longer mysterious. We have a broad consensus aboutWe have a broad consensus about –what.

Slides:



Advertisements
Similar presentations
Kellan Hilscher. Definition Different perspectives on the components, behavioral specifications, and interactions that make up a software system Importance.
Advertisements

Unit 2. Software Lifecycle
Finance | Ralfi Vanlaethem | 5 May 2008 | 1 5 May 2008Finance | Ralfi Vanlaethem1 Fortis Group 5 th of May 2008.
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.
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.
Chapter 1. Introduction This course is all about how computers work But what do we mean by a computer? –Different types: desktop, servers, embedded devices.
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.
IS Terms and Introductory Concepts. Contemplative Questions What is an information system? What is an information system? Why do we care about the difference.
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.
January 11, 2007Russ Abbott Complex systems are no longer mysterious.Complex systems are no longer mysterious. We have a broad consensus aboutWe have a.
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.
Overview of Computing. Computer Science What is computer science? The systematic study of computing systems and computation. Contains theories for understanding.
University of Utah SoCCS Lecture 61 Architecture – An Introduction CS Lecture 6 Nathan Dykman.
1 CMPT 275 Software Engineering Requirements Analysis Phase Requirements Analysis Activity (Identifying Objects, Scenarios) Janice Regan,
Computer Science 101 Database Concepts. Database Collection of related data Models real world “universe” Reflects changes Specific purposes and audience.
11 Chapter 11 Object-Oriented Databases Database Systems: Design, Implementation, and Management 4th Edition Peter Rob & Carlos Coronel.
Sommerville, Mejia-Alvarez, 2009Software Engineering, Slide 1 Software Design u Deriving a solution which satisfies software requirements.
Vienna Conference on Consciousness Part I "What is the neural basis of consciousness? Where is it in the brain?" Contribution by Michael L. Berger (Center.
CS 4310: Software Engineering Lecture 4 System Modeling The Analysis Stage.
Models in Science SWBAT describe various types of models; discuss limitations of models.
Develop a Safety Assurance approach for Complex Systems (Problem Definition) Supervisors: Tim Kelly, Rob Alexander Chris Leong HISE Group Giving a Presentation.
Software Engineering Principles. SE Principles Principles are statements describing desirable properties of the product and process.
An Introduction to Software Engineering
Example: object diagram for Scheduler, v What is wrong with this diagram? Seems like a lot of similarity between Task and UnplannedTask Can use.
VCE IT Theory Slideshows By Mark Kelly Vceit.com Problem Solving Methodology 3 Development.
1 CMPT 275 High Level Design Phase Modularization.
Software Design: Principles, Process, and Concepts Getting Started with Design.
Lecture 2 Page 1 CS 111 Online System Services for OSes One major role of an operating system is providing services – To human users – To applications.
순천향대학교 정보기술공학부 이 상 정 1 1. Computer Abstractions and Technology.
The Rational Unified Process 1 EECS810: Software Engineering.
Introduction to OOAD and the UML
® IBM Software Group © 2004 IBM Corporation Developing an SOA with RUP and UML 2.0 Giles Davies.
1 Database Systems Entity Relationship (E-R) Modeling.
Page 1 COMPSCI 290.2: Computer Security “Quantum Cryptography” including Quantum Communication Quantum Computing.
1 Prof. Dr. Nizamettin AYDIN
Generalizable Element Namespace Model Element name visibility isSpecification Classifier isRoot Constraint Body Coming up: Unified Modeling Language Introduction.
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.
1 SYS366 Week 2 - Lecture 2 Visual Modeling & UML.
Stages involve Discontinuous (qualitative) change Invariant sequence –Stages are never skipped.
1. 2 An Introduction to Software Engineering 3 What is software? Computer programs and associated documentation such as requirements, design models and.
Generalizable Element Namespace Model Element name visibility isSpecification Classifier isRoot Constraint Body Introduction to the Unified Modeling Language.
Data Centers and Cloud Computing 1. 2 Data Centers 3.
Object Oriented Systems Design
System-on-Chip Design
CompSci 280 S Introduction to Software Development
Software Engineering Lecture 4 System Modeling The Analysis Stage.
Copyright © 2014 Hassan Gomaa and Robert Pettit
Course Outcomes of Object Oriented Modeling Design (17630,C604)
Introduction to the Unified Modeling Language
COMPSCI 290.2: Computer Security
Coupling and Cohesion 1.
which satisfies software requirements
Reference: COS240 Syllabus
Software Testing and Maintenance Designing for Change
Quantum Computers Superposition Interference Entanglement and Quantum Error Correction Lesson 1 By: Professor Lili Saghafi
Java Messaging Service (JMS)
Java Messaging Service (JMS)
Introduction to the Unified Modeling Language
Introduction to the Unified Modeling Language
Software Design Lecture : 8
Software Analysis.
Linear Vector Space and Matrix Mechanics
Logical Architecture & UML Package Diagrams
Presentation transcript:

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.

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? E.g., an evolutionary arms race.E.g., an evolutionary arms race. –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.

Entangled with its environment.Entangled with its environment. –Built to act on 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. –An operating system, a browser, a shopping center, a standard. –Whoever owns it controls it! (See governance below.) Boundaries are deliberately permeable and indistinct.Boundaries are deliberately permeable and indistinct. –Exchanges energy and materials with its environment: eats & excretes. –Must extract energy from its environment to persist. (Far from equilibrium.) –System of systems; the operator goes home; a new president is elected. Must adapt to a continually changing environment—that is continually adapting to it.Must adapt to a continually changing environment—that is continually adapting to it. –Simultaneously deployed and 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.

To refine, clarify, and formalize these concepts.To refine, clarify, and formalize these concepts. To make them intuitive, commonplace, and everyday.To make them intuitive, commonplace, and everyday. To make them operational.To make them operational. –To adapt them to practice in building real systems. –To define development processes based on these perspectives. –To build tools to allow anyone to use them.