1 ME886.3 Topic 1: System and System Design (I). 2 What we design?

Slides:



Advertisements
Similar presentations
Ch:8 Design Concepts S.W Design should have following quality attribute: Functionality Usability Reliability Performance Supportability (extensibility,
Advertisements

Component Oriented Programming 1 Chapter 2 Theory of Components.
Architecture Representation
Chapter 3 Process Models
Using the Crosscutting Concepts As conceptual tools when meeting an unfamiliar problem or phenomenon.
OASIS Reference Model for Service Oriented Architecture 1.0
Developing MAS The GAIA Methodology A Brief Summary by António Castro and Prof. Eugénio Oliveira.
INDUSTRIAL & SYSTEMS ENGINEERING (Lecture # 2). 2 Functional Groupings of I & SE o Work Measurement o Performance Rating o Time Standards o Motion Study.
Π-Method: A Model-Driven Formal Method for Architecture- Centric Software Engineering By Flavio Oquendo Presented by: Sajith Wickramaratne.
L3-5d-S1 Class Diagrams © M.E. Fayad SJSU -- CmpE Software System Engineering Dr. M.E. Fayad, Professor Computer Engineering Department, Room.
Unified Modeling (Part I) Overview of UML & Modeling
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 1 Slide 1 An Introduction to Software Engineering.
Modified from Sommerville’s originalsSoftware Engineering, 7th edition. Chapter 8 Slide 1 System models.
1/31 CS 426 Senior Projects Chapter 1: What is UML? Chapter 2: What is UP? [Arlow and Neustadt, 2005] January 22, 2009.
Describing Syntax and Semantics
Systems Engineering Foundations of Software Systems Integration Peter Denno, Allison Barnard Feeney Manufacturing Engineering Laboratory National Institute.
1 CS 426 Senior Projects Chapter 1: What is UML? Chapter 2: What is UP? [Arlow and Neustadt, 2002] January 26, 2006.
Spring 2009CS 225 Introduction to Software Design Chapter 1.
Introduction to Software Design Chapter 1. Chapter 1: Introduction to Software Design2 Chapter Objectives To become familiar with the software challenge.
Engineering Systems of.
Chapter 3 Software Processes.
COMPUTER VIZUALIZATION OF MULTY-LINK MECHANISMS WITH TWO DEGREES OF FREEDOM Georgian Technical University PhD Student Marina Razmadze.
What is UML? What is UP? [Arlow and Neustadt, 2005] January 23, 2014
Chapter 6 System Engineering - Computer-based system - System engineering process - “Business process” engineering - Product engineering (Source: Pressman,
Liang, Introduction to Java Programming, Sixth Edition, (c) 2007 Pearson Education, Inc. All rights reserved Chapter 12 Object-Oriented.
Math and Science Integration F. Mumba University of Virginia MSP Workshop 2014.
Robust Design Strategies I Gruia-Catalin Roman and Christopher Gill Washington University in St. Louis.
Python Mini-Course University of Oklahoma Department of Psychology Day 2 – Lesson 6 Program Design 4/18/09 Python Mini-Course: Day 2 - Lesson 6 1.
What is linguistics  It is the science of language.  Linguistics is the systematic study of language.  The field of linguistics is concerned with the.
Lecture 9: Chapter 9 Architectural Design
Programming in Java Unit 3. Learning outcome:  LO2:Be able to design Java solutions  LO3:Be able to implement Java solutions Assessment criteria: 
SOFTWARE DESIGN.
Chapter 1: Introduction Omar Meqdadi SE 2730 Lecture 1 Department of Computer Science and Software Engineering University of Wisconsin-Platteville.
Design engineering Vilnius The goal of design engineering is to produce a model that exhibits: firmness – a program should not have bugs that inhibit.
Major objective of this course is: Design and analysis of modern algorithms Different variants Accuracy Efficiency Comparing efficiencies Motivation thinking.
An Introduction to Software Engineering. Communication Systems.
DIDACTICTS IS THE ART AND SCIENCE OF TEACHING  The word is derived from the greek: didaskein (to teach) tekne (art)  The concept is both a science.
Software Engineering Prof. Ing. Ivo Vondrak, CSc. Dept. of Computer Science Technical University of Ostrava
Basics of Research and Development and Design STEM Education HON4013 ENGR1020 Learning and Action Cycles.
Software Design Process
International Conference on cybernetics and intelligent system, p.p , Sept Modeling Large-Scale Manpower Dynamics: An Expert Systems Approach.
Chapter 6 – Architectural Design Lecture 1 1Chapter 6 Architectural design.
MODEL-BASED SOFTWARE ARCHITECTURES.  Models of software are used in an increasing number of projects to handle the complexity of application domains.
1 ME886.3 Topic 1: System and System Design (II).
Digital Libraries1 David Rashty. Digital Libraries2 “A library is an arsenal of liberty” Anonymous.
From Hoare Logic to Matching Logic Reachability Grigore Rosu and Andrei Stefanescu University of Illinois, USA.
Software Engineering Chapter: Computer Aided Software Engineering 1 Chapter : Computer Aided Software Engineering.
Thinking behind the environment for Making Construals (MCE)
Chapter 5 System Modeling. What is System modeling? System modeling is the process of developing abstract models of a system, with each model presenting.
Mahmut Ali GÖKÇEIndustrial Systems IEU Introduction to System Engineering ISE 102 Spring 2007 Notes & Course Materials Asst. Prof. Dr. Mahmut.
Human Factors Engineering Principles of System Design.
Object-Oriented Software Engineering Practical Software Development using UML and Java Modelling with Classes.
CSCI 383 Object-Oriented Programming & Design Lecture 7 Martin van Bommel.
Interpreting the Object Constraint Presented by: Ed Kausmeyer.
Diagrams. Typically, we view the static parts of a system using one of the four following diagrams. 1. Class diagram 2. Object diagram 3. Component diagram.
1 1- Introduction Focus of Human Factors: Human factors (or ERGONOMICS) focus on human beings and their interaction with products, equipment, facilities,
DESIGN PROCESS AND CONCEPTS. Design process s/w design is an iterative process through which requirements are translated into a “blueprint” for constructing.
Chapter 5 Process Modeling By Muna Shabaneh. What is a Model? What is a process? What is a Process modeling? What are the Perspectives in process representation.
What is UML? What is UP? [Arlow and Neustadt, 2005] October 5, 2017
OVERVIEW Impact of Modelling and simulation in Mechatronics system
ME886.3 Topic 1: System and System Design (II)
Socio-Cultural Influences
Chapter 10: Process Implementation with Executable Models
Generalization of robots
Linear Control Systems
Model-Driven Analysis Frameworks for Embedded Systems
Principles and Elements of design
Software Design Methodologies and Testing
Software Development Process Using UML Recap
UML  UML stands for Unified Modeling Language. It is a standard which is mainly used for creating object- oriented, meaningful documentation models for.
Presentation transcript:

1 ME886.3 Topic 1: System and System Design (I)

2 What we design?

3 1. What we design

4

5 My dream living room

6 1. What we design Courtesy to a friend of mine in China (N. Ouyang)

7 1. What we design  We design everything. Design is to create a thing that is not existed. Why we design?

8

9  Design things for purpose and there are three purposes: 1. Function: design a thing that can assist in a human’s activities. 2. Comfort: design a thing humans can feel comfortable with when interacting with the thing. 3. Emotion: design a thing humans can change their emotion when interacting with the thing.  Things designed will have a mixture of function, comfort, and emotion.  The difference between design of an arts product and design of a non-arts product lies in that arts design is only for the purpose of emotion. 2. Why we design

10 2. Why we design – cook is a design Function: meet hungry and provide nutrition. Comfort: size and mechanical property of cookies. Emotion: graceful, clean, simple, light, positive, delicate.

11  Different non-arts products can have different emphases on function, comfort and emotion. For example, for products such as industrial robots, their functions are more emphasized than human’s comfort or emotion. However, fashion products may put more emphasis on human’s emotion.  For non-arts products or products design, 80% of the total cost of a product is determined at the design stage. 2. Why we design How we design?

12 How we design?

13 3. How we design  Explore and develop design science and technology.  First, unify the things to be designed; that is to say, having a theory to describe everything using one formalism – system.  Second, be aware of the nature of design which is: (a) open-ended, (b) empirical, and (c) iterative.  It is (a) because device technology and device are evolving, and constraints (conditions to function) keep changing.  It is (b) because design is an action of humans, the process of which has yet to be fully automated.  It is (c) because of the limitation of humans.

14 Everything is a system! To have a knowledge that is useful to design all these different objects, we need to find a unified understanding of everything, that is to system.

15 4. Everything is a system The goal is to find commonalities for various things we will be designing. It can be achieved by viewing them as a system. Roughly, a system is composed of a set of components. For example, a class room is composed of chairs, tables, and electric facilities. This may be viewed as an attribute of a system called “system is decomposable”.  The decomposable attribute of a thing is called the structural attribute of the thing; or simply say, everything has a structure.  Putting together the commonalities of everything with a name that is system. So the system is a generic everything or a generic model of everything.

16 4. Everything is a system  A model of X is not X. That is to say, a system or generic model of everything is just an abstraction of everything but not everything.  System of everything = system’s view of everything = generic model of everything.  A system or generic model includes the following common attributes: structure, state, behavior, principle, context, function.

FCBPSS Framework Lin, Y and Zhang, WJ, “Towards a novel interface design framework: function-behavior-state paradigm,” International Journal of Human Computer Studies, Vol. 61, No. 3, pp Principle Context Behaviour Function State Structure 4. Everything is a system

Structure: a set of elements with their relationships. For example, 1 connects with 2, 2 connects with 3, 3 connects with 4, 4 connects with 1, but 2 and 4 have no direction connection, etc Everything is a system: an example

State α s State variable (S) State value (S=3) There are many state variables or states for a system depending on your purpose or interest in a particular aspect of the system (e.g., kinematics, etc.). For instance, the stress in the component could also be a state, as if interest is in whether the system is broken or not System behavior: the relation between the state variables (e.g., s=s(α)) System dynamic behavior: changes in states with respect to time. For example, α is a function of time, t, so s will be a function of t 4. Everything is a system: an example

Constrained by the ground α s Principle: Polygon keep closure if the assembly is of integrity Procedure: Step 1: assign vector to each edge of the polygon. Step 2: define vector with concerned state variables. Step 3: use math language to express the principle What governs the behavior, e.g., the relation between s and α ? 4. Everything is a system: an example

α s S=S(α) 4. Everything is a system: an example

Context and function Engine 4. Everything is a system: example 1

Context and function Context: The pre-condition, post-condition, and environment where a structure is placed. Function: The usefulness of a structure with respect to the human, ecological, and technical system Sewing machine 4. Everything is a system: example 2

Zhang and Lin’s FCBPSS: System or Generic Model of Everything Principle Context Behaviour Function State Structure

25 FCBPSS makes design more systematic

FCBPSS-based design process Required function & context Required state & behavior Proposed structure Compress the gas Volume change –> displacement, rotation to translation Slider- crank linkage Synthesis Analysis The above applies to conceptual, embodiment, and detailed design Evaluation

FCBPSS-based design process Required function & context Required state & behavior Proposed structure Compress the gas Volume change –> displacement, rotation to translation Slider- crank linkage Synthesis Analysis The above activity loop implies that design iterates Evaluation

FCBPSS-based design process Required function & context Required state & behavior Proposed structure When the evaluation shows unsatisfactory with the required function with context, there may be several options to adjust: 1.Change the required function 2.Change the required context (or constraint or condition) 3.Find new structures