Self-Organizing Systems Design Method Jordan Hall Mohsin Waqar Nathan Young ME6101 – End of Semester Presentation 7 Dec 2006.

Slides:



Advertisements
Similar presentations
Research skills. OUTLINE Mission and Vision What is Research? Ten Steps for Good Research Resources of Research Types of research Skills (Top_5 Skills)
Advertisements

Test Automation Success: Choosing the Right People & Process
Object-Oriented Analysis and Design LECTURE 3: REQUIREMENTS DISCIPLINE.
Lecture # 2 : Process Models
Software Project Management
Chapter 2 – Software Processes
May 2, May 2, 2015May 2, 2015May 2, 2015 Azusa, CA Sheldon X. Liang Ph. D. Software Engineering in CS at APU Azusa Pacific University, Azusa, CA.
Unit-III Requirements Engineering
Systems Engineering in a System of Systems Context
SE curriculum in CC2001 made by IEEE and ACM: Overview and Ideas for Our Work Katerina Zdravkova Institute of Informatics
INDUSTRIAL & SYSTEMS ENGINEERING
Technical Writing II Acknowledgement: –This lecture notes are based on many on-line documents. –I would like to thank these authors who make the documents.
Requirements Analysis Concepts & Principles
Chapter 10: Architectural Design
LEARN. NETWORK. DISCOVER. | #QADexplore Implementing Business Process Management: Steps to Success WCUG – November 18, 2014.
Sharif University of Technology Session # 4.  Contents  Systems Analysis and Design Sharif University of Technology MIS (Management Information System),
Chapter 1 The Product Design Process
Enterprise Architecture
Development Processes and Organizations
Effective Methods for Software and Systems Integration
Framework for K-12 Science Education
Unit 2: Engineering Design Process
THE DESIGN PROCESS. General Design Process Need –Determine functional requirements… Specification –Identify essential problems […] –Search for … solution.
EENG 1920 Chapter 1 The Engineering Design Process 1.
European Network of Excellence in AI Planning Intelligent Planning & Scheduling An Innovative Software Technology Susanne Biundo.
Educator Effectiveness Academy STEM Follow-Up Webinar December 2011.
Design Science Method By Temtim Assefa.
CS CS 5150 Software Engineering Lecture 3 Software Processes 2.
EEA 2012 – Middle School STEM Day 3 Content Session.
2Object-Oriented Analysis and Design with the Unified Process The Requirements Discipline in More Detail  Focus shifts from defining to realizing objectives.
Software Engineering Management Lecture 1 The Software Process.
1 Chapter 5 Software Engineering Practice. 2 What is “Practice”? Practice is a broad array of concepts, principles, methods, and tools that you must consider.
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by.
Coming up: Software Engineering: A Practitioner’s Approach, 6/e Chapter 5 Practice: A Generic View copyright © 1996, 2001, 2005 R.S. Pressman & Associates,
EPT 221 CONCEPTUAL DESIGN. Lecture Objectives Define and describe concept design Describe and apply methods to clarify functional requirements of a design:
Engineering Design George E. Dieter Mc Graw Hill.
Ken Youssefi Mechanical Engineering department 1 Design Process Concurrent Engineering.
Chapter 7: A Summary of Tools Focus: This chapter outlines all the customer-driven project management tools and techniques and provides recommendations.
CHECKPOINTS OF THE PROCESS Three sequences of project checkpoints are used to synchronize stakeholder expectations throughout the lifecycle: 1)Major milestones,
Introduction Complex and large SW. SW crises Expensive HW. Custom SW. Batch execution Structured programming Product SW.
Science Fair How To Get Started… (
Reduced Cost for Using The most important justification for the companies who resorts to outsourcing is petty expenses for searching. More of that companies.
Review of Software Process Models Review Class 1 Software Process Models CEN 4021 Class 2 – 01/12.
1 Lecture #1: PD - Ch 1. Introduction Ref: Product Design and Development by Karl T. Ulrich and Steven D. Eppinger, McGRAW-Hill
Product Management. Facts about Product Management Many managers realized that investment in INNOVATION is critical for future growth & even in the survival.
1 Software Engineering: A Practitioner’s Approach, 6/e Chapter 5 Practice: A Generic View Software Engineering: A Practitioner’s Approach, 6/e Chapter.
Software Architecture Evaluation Methodologies Presented By: Anthony Register.
Chapter 2 – Software Processes Lecture 1 Chapter 2 Software Processes1.
Chapter 6: THE EIGHT STEP PROCESS FOCUS: This chapter provides a description of the application of customer-driven project management.
1 Chapter 8 Building the Analysis Model (1) Analysis Concepts and Principles.
Software Engineering Jon Walker. What is Software Engineering? Why do we call it Software Engineering? Why not just call it programming or software development?
Engineering Design Process
SOFTWARE ENGINEERING. Objectives Have a basic understanding of the origins of Software development, in particular the problems faced in the Software Crisis.
Level 2 Unit 2 Investigating Engineering Design Engineering Diploma Level 2 Unit 2 Investigating Engineering Design In this unit you will find out how.
Overview of RUP Lunch and Learn. Overview of RUP © 2008 Cardinal Solutions Group 2 Welcome  Introductions  What is your experience with RUP  What is.
Chapter 2: Development process and organizations
Requirement Engineering
Introduction Complex and large SW. SW crises Expensive HW. Custom SW. Batch execution Structured programming Product SW.
Requirement engineering & Requirement tasks/Management. 1Prepared By:Jay A.Dave.
UTA/ARRI. Enterprise Engineering for The Agile Enterprise Don Liles The University of Texas at Arlington.
Software Development Process CS 360 Lecture 3. Software Process The software process is a structured set of activities required to develop a software.
Lectures 2 & 3: Software Process Models Neelam Gupta.
What has been accomplished at the end of MSD 1 & 2?
The Engineering Design Process
Process 4 Hours.
ECE361 Engineering Practice
Identify the Risk of Not Doing BA
The Systems Engineering Context
Software Requirements
Chapter 2: Development process and organizations
Presentation transcript:

Self-Organizing Systems Design Method Jordan Hall Mohsin Waqar Nathan Young ME6101 – End of Semester Presentation 7 Dec 2006

Q4S (Modified): “How should the Pahl & Beitz systematic design method be augmented and personalized to support the concurrent realization of technical systems for a global market place in a distributed environment based on self-organization concepts?”

World of 2020: Vision ContextDriverMetric Business: Process Costs Time to Market Supply Chain Profitability Globalization: Global Consumers Customer Satisfaction Technology: Web-Based Collaboration Bandwidth Computing Power Speed

World of 2020: Requirements List for Design Method General Design method must be systematic Augmented Support multidisciplinary/distributed design team Personalized Support concurrent engineering practices Parallel information flow

Plan of Action Our Personalized and Augmented Pahl and Beitz Systematic Design Method Requirements List (Design specification) Plan and clarify the task: 1)Identify customer desires: ethnographic research, in use studies, etc. 2)Clarify task 3)Develop Master Validation Plan 4) Elaborate a requirements list Task Market, Company, Economy Develop the principal solution: 1) Identify essential problems through abstraction 2) Establish function structures 3) Search for working principles and working structures 4) Combine and firm up into concept variants 5)Perform safety/manufacturing process simulations Concept (Principal Solution) Evaluate and specify DfX Subdivide Tasks Develop and define the construction structure: Check for errors, disturbing influences, and minimum costs Prepare the preliminary parts, production, and assembly doc 1) Preliminary form design and calculation 2) Select best preliminary layouts 3) Refine and improve layouts Eliminate the weak spots Determine efficiency of integrationDefinitive Layout Prepare production and operating documents: 1) Elaborate detail drawings and parts lists 2)Verify and validate 3)Complete production, assembly, transport, and operating instructions 4)Check all documents Product Documentation Solution Continuous Improvement/Manufacture Product Realization

Plan of Action Communicate with Advisor Start Develop Common Vision Conduct Background Research Clarify Task Plan Validation Develop Req. List for Project Abstract Project Develop Best Outline A A ID Core Ideas Relate Core Ideas Develop Rough Draft Subdivide Tasks Identify Parallel Info. Flow Define DfX Write Section 1 Write Section n (function structure) (working structure) (principal concept) (layout) Proof Read and Refine Verify and Validate Submit Report Continue Research Digest Feedback. Our Plan: Deliver a comparison between the Pahl & Beitz (P&B) systematic design method and design methods for self-organizing systems. Conduct On-going Research Phase I Phase II Phase III Phase IV Phase V

Project Tasks 10/5 Crux of Task 10/7 PEI Diagram 10/21 Requirements List for Deliverable 10/21 Master Validation Plan 11/2 Report Outline 11/14 Complete SO Research 11/14 Complete Systematic Design Research 11/19 Rough Draft 11/21 Requirements List for SOSDM 11/30 Verification & Validation 12/2 Gap Analysis 12/11 Final Report Phase IPhase IIPhase IIIPhase IV

Verification and Validation Theoretical Structural Validation (Square 1): Is the method internally consistent? YES 1) P&B core transforms are retained. 2) Requirements list for project deliverable is satisfied. Empirical Structural Validation (Square 2) Is our research project appropriate for the method? YES/NO/MAYBE 1) An open-ended problem is posed. 2) Team work was required. 3) Time was constrained. 4) Constructs of method are applied. But not all augmentations utilized. Empirical Performance Validation (Square 3) Did the method contribute to the success of our research project? YES 1) Met our targets for content, quality and time. Theoretical Performance Validation (Square 4) Is there utility of the method beyond our research project? YES 1) Suitable for technical research papers.

Why Self-Organization? Why SO? Mohsin: I am interested in machine intelligence. I saw this project as an opportunity to learn more about robust systems that can manage themselves. Why this Project? Nathan: I realize that it is critical to always grow as an engineer. I saw this project as an opportunity to diversify my engineering portfolio due to its broad scope and interdisciplinary requirements. Why systematic design? Jordan: I am interested in the practical application of a method such as Pahl and Beitz in the future. Self-organization is an interesting challenge for systematic design processes. How can systematic design be used to create Self-Organizing Systems?

Systematic Design Process Information Flow Diagrams Top-Down Process “Divergent-Convergent” Abstract → Concrete Based on Requirements

Self-Organization ________________ Efficiency Robustness Multi-stability Distributed Control Information Flow Centralized Leadership Agents Information Flow Information Flow Bottleneck

Examples of SO in Practice __________________ Self-assembly - 2D Arrays - 3D Structures Multi-agent Robotics - Chain - Lattice - Swarm

Self-Organizing Systems Design Methodology A few requirements for SOSDM:  Supports various system architectures. How many elements are there and what is their complexity?  Defines interaction rules between agents How much is behavior of an element constrained?  Defines functions/capabilities of each agent Are agents generalists or specialists?  Defines the decision structure (hierarchy vs. autonomous) Who makes decisions?  Define metrics for evaluating macroscopic/global behavior. How do you evaluate the system?

Critical Analysis – The Gap Systematic Information Flow Requirements List What are the similarities between SOSDM and P&B? What are the differences between SOSDM and P&B? Function Structure - How can the nature of a function structure differ between design methods? Indirect Design - What is meant by indirect design and how is that unique to SOSDM? Evolution of System in Design - This is not biology. Why am I talking about evolution?

Future Questions  Can the system function structure be dynamically reconfigured? Can this occur autonomously?  What tasks must occur between manufacturing of the SOS and release to customer to verify system performance?  Is there a way to concurrently design the algorithm and agents for a system? In essence, is the algorithm somewhat generic to SO systems?  What technologies are currently available to develop these types of systems?  What are the core information transforms of a SOSDM? This is an invitation to think with us as we look to the future of SOS design. Please RSVP…

Lesson Learned… Jordan: I gained an understanding of the state of the art in self-organizing systems design. I also gained a deeper understanding of the Pahl and Beitz method by comparing it to self-organization design methodologies. Nathan: I gained insight into the fundamental principles of adaptive systems. I discovered the need for an adaptive systems design method that I will continue to investigate in my research. Mohsin: I learned that more involvement from mechanical engineers is needed to balance the work of computer scientists and improve the feasibility of self- organizing systems.