Systems Engineering CSC 595_495 Spring 2018 Howard Rosenthal
|
|
- Bryce Leonard
- 6 years ago
- Views:
Transcription
1 Systems Engineering CSC 595_495 Spring 2018 Howard Rosenthal 1
2 Notice This course is based on and includes material from the text: The Engineering Design of Systems: Models and Methods (Wiley Series in Systems Engineering and Management) 3rd Edition Dennis M. Buede, William D. Miller Publisher: Wiley; 3 edition (February 29, 2016) Language: English ISBN-13: It also utilizes information from these two additional books as well as many cited references: Practical Guide to SysML, Third Edition: The Systems Modeling Language (The MK/OMG Press) 3rd Edition Sanford Friedenthal, Alan Moore, Rick Steiner Series: The MK/OMG Press Publisher: Morgan Kaufmann; 3rd edition (November 7, 2014) ISBN-13: System Engineering Analysis, Design, and Development: Concepts, Principles, and Practices (Wiley Series in Systems Engineering and Management) 2nd Edition Charles S. Wasson Series: Wiley Series in Systems Engineering and Management Hardcover: 882 pages Publisher: Wiley; 2 edition (December 2, 2015) Language: English ISBN-13: Other material was used from these web sites:
3 Lesson Goals Understand what an IDEFØ model is Understand how to construct an IDEFØ model Build an IDEFØ model 3
4 4
5 What is IDEF? IDEF, initially abbreviation of ICAM Definition, renamed in 1999 as Integration DEFinition, refers to a family of modeling languages in the field of systems and software engineering. They cover a wide range of uses, from functional modeling to data, simulation, object-oriented analysis/design and knowledge acquisition The IDEF models include IDEFØ: Function modeling IDEF1 : Information modeling IDEF1X : Data modeling IDEF2 : Simulation model design IDEF3 : Process description capture IDEF4 : Object-oriented design IDEF5 : Ontology description capture IDEF6 : Design rationale capture IDEF7 : Information system auditing IDEF8 : User interface modeling IDEF9 : Business constraint discovery IDEF10 : Implementation architecture modeling IDEF11 : Information artifact modeling IDEF12 : Organization modeling IDEF13 : Three schema mapping design IDEF14 : Network design 5
6 IDEFØ Overview IDEFØ is a method designed to model the decisions, actions, and activities of an organization or system IDEFØ was derived from a well-established graphical language, the Structured Analysis and Design Technique (SADT) The United States Air Force commissioned the developers of SADT to develop a function modeling method for analyzing and communicating the functional perspective of a system IDEFØ was not included in SYSML, but it still remains an important and widely used classical modeling tool IDEF0 is definitely not a sufficient modeling representation for the engineering of systems since it is not precise enough to define a unique dynamic representation of the system's design Effective IDEFØ models help to organize the analysis of a system and to promote good communication between the analyst and the customer IDEFØ is useful in establishing the scope of an analysis, especially for a functional analysis As a communication tool, IDEFØ enhances domain expert involvement and consensus decision-making through simplified graphical devices As an analysis tool, IDEFØ assists the modeler in identifying what functions are performed, what is needed to perform those functions, what the current system does right, and what the current system does wrong IDEFØ models are often created as one of the first tasks of a system development effort. 6
7 IDEFØ Concepts (1) Cell Modeling Graphic Representation The "box and arrow" graphics of an IDEFØ diagram show the function as a box and the interfaces to or from the function as arrows entering or leaving the box To express functions, boxes operate simultaneously with other boxes, with the interface arrows "constraining" when and how operations are triggered and controlled. IDEFØ Communications Features Diagrams based on simple box and arrow graphics. English text labels to describe boxes and arrows and glossary and text to define the precise meanings of diagram elements. The gradual exposition of detail featuring a hierarchical structure, with the major functions at the top and with successive levels of subfunctions revealing well-bounded detail breakout. A "node chart" that provides a quick index for locating details within the hierarchic structure of diagrams. The limitation of detail to no more than six subfunctions on each successive function 7
8 IDEFØ Concepts (2) Something (matter, energy, information, system) transformed by the process Something that guides, facilitates, limits, or constrains the process Something that results from the process A means by which the process is performed A reference to another model. 12 The Basic IDEF Structure 8
9 IDEFØ Concepts (3) Rigor and precision rules in IDEFØ Control of the details communicated at each level (three to six function boxes at each level of a decomposition). Bounded Context (no omissions or additional out-of-scope detail). Diagram Interface Connectivity (Node numbers, Box numbers, C- numbers, and Detail Reference Expression). Data Structure Connectivity (ICOM codes and the use of parentheses). Unique Labels and Titles (no duplicated names). Syntax Rules for Graphics (boxes and arrows). Data Arrow Branch Constraint (labels for constraining the data flow on branches). Input versus Control Separation (a rule for determining the role of data). Data Arrow Label Requirements (minimum labeling rules). Minimum Control of Function (all functions require at least one control). Purpose and Viewpoint (all models have a purpose and viewpoint statement) 9
10 10
11 IDEFØ General Rules & Guidelines Rules Conservation of inputs, controls, outputs & mechanisms Every function has a control and output Guidelines 3 to 6 functions per page arranged diagonally Control-oriented functions placed at top left Major output functions placed on bottom right Arcs & functions are decomposable Feedback is defined by arcs moving from bottom right to top left 11
12 Box and Arrow Rules (1) Boxes Boxes shall be sufficient in size to insert box name Boxes shall be rectangular in shape, with square corners Boxes shall be drawn with solid lines A box shall be named with an active verb or verb phrase Each side of a function box shall have a standard box/ arrow relationship: Input arrows shall interface with the left side of a box Control arrows shall interface with the top side of a box Output arrows shall interface with the right side of the box Mechanism arrows (except call arrows) shall point upward and shall connect to the bottom side of the box Mechanism call arrows shall point downward, shall connect to the bottom side of the box, and shall be labeled with the reference expression for the box which details the subject box 12
13 Box and Arrow Rules (2) Box/Node numbers Single box in context (A-0) diagram numbered A0 ( Activity 0) Boxes in context diagram s child numbered A1, A2, A3,... [A6] Boxes in A1 s child diagram numbered A11, A12,... Boxes in A2 s child diagram numbered A21, A22,... Boxes in A21 s child diagram numbered A211, A212,... and so on... 13
14 Box and Arrow Rules (3) Arrows Arrows that bend shall be curved using only 90 degree arcs Arrows shall be drawn in solid line segments Arrows shall be drawn vertically or horizontally, not diagonally Arrow ends shall touch the outer perimeter of the function box and shall not cross into the box Arrows shall attach at box sides, not at corners Arrow segments, except for call arrows, shall be labeled with a noun or noun phrase unless a single arrow label clearly applies to the arrow as a whole A squiggle shall be used to link an arrow with its associated label, unless the arrow/label relationship is obvious Arrow labels shall not consist solely of any of the following terms: function, input, control, output, mechanism, or call 14
15 Box and Arrow Rules (4) When drawing interface arrows Think control and constraint, not flow Don t worry about sequence All boxes may be active simultaneously Bundle groups of arrows, when possible Don t clutter with arrows. All boxes must have control arrows, but they don t require input arrows. Give arrows noun or noun phrase names 15
16 There Are Three Feedback Loops In IDEFØ label Control Feedback up & over Input Feedback label down & under Mechanism Feedback down & under label 16
17 The Top-Level Context Diagram In IDEFØ Subject of model represented by single box with bounding arrows Called A-0 ( A minus zero ) Box and arrows are very general Sets model scope or boundary and orientation Should include Purpose Viewpoint 17
18 Sample Context Diagram A-0 Assemble Widgets Purpose: To illustrate IDEF0 modeling for the Work Systems Engineering process. Viewpoint: Industrial/manufacturing engineer
19 Sample Context Diagram Another A-0 Diagram With Additional Materials 19
20 The Child Diagram In IDEFØ The single process in Context Diagram (A-0) may be decomposed into subprocesses and modeled in a child (A0) diagram. Each process in the A0 diagram may be decomposed further into subprocesses and modeled in (grand-) child (A1, A2,... A6) diagrams Each (grand-) child process may be decomposed further into subprocesses and modeling (greatgrand-) child diagrams Remember only 3-6 subprocesses per process 20
21 Diagram Features Arrows As Constraints Connecting output of a box representing a process that is input/ control/mechanism to another box means that the second process is constrained by the first in this A0 diagram 21
22 Diagram Features Concurrent Operations Box order and connections do not necessarily imply sequence! Processes may proceed concurrently Concurrent with A32 and A33 22
23 Diagram Features Branching Arrows A & B 27 23
24 Diagram Features Inter-Box Connections (2) Except for A-0, diagrams contain 3 6 boxes Normally organized on diagonal ( staircase ) Any output of one box may be input, control, or mechanism of another box If box is detailed on child diagram, every arrow connected to the box appears on the child diagram (unless it is tunneled) 24
25 Diagram Features Inter-Box Connections (2) Node A
26 Diagram Features Boundary Arrows: Arrows From Parent box On Parent Diagram Node A3 Coded by prefix and number 31 26
27 IDEFØ Page Structure Page # s Function # s A-1 A-11 A-0 A-12 A-13 A-0 A0 A0 A1 A2 A3 A1, A3 A11 A12 A13 A31 A32 A33 A34 A33 A331 A332 A333 A334 A335 Page Number(s) Page Content A - 1 Ancestor or external system diagram A - 0 Context or system function diagram (contains A0) A0 Level 0 diagram with first tier functions specified A1, A2,... Level 1 diagrams with second tier functions specified A11, A12,..., A21,... Level 2 diagrams with third tier functions specified... Chapter 3 - Modeling and Process Modeling 27
28 Example Of The IDEFØ Page Structure Node List A-0: Assemble widgets A0: Assemble widgets A1: Restock parts A2: Get widget parts A3: Assemble parts A31: Hold widget base A32: Position parts in place A33: Secure parts to base A34: Release assembled widget A4: Inspect widgets 28
29 The IDEFØ Page Structure Is A Hierarchical Structure Widgets A0 Assemble Widgets A1 A2 A3 A4 Restock Parts Get Widget Parts Assemble Part Inspect Widgets A31 Hold Widget Base A32 Position Parts In One Place A33 Secure Parts To Base A34 Release Assembled Widget 29
30 Explanatory Materials Used With IDEFØ (1) Text and Glossary Associated textual information used to clarify model. Glossary includes definitions of Processes (activities, functions) Inputs Controls Outputs Mechanisms Examples in the glossary might include Get widget parts (process) The process of getting widget parts from the stock areas so that widgets may be assembled Parts for widgets (output) Parts retrieved from the workstation stock areas and ready to be used in assembly 30
31 Explanatory Materials Used With IDEFØ (2) For Exposition Only Diagram (FEO) Provides supplementary information to help reader understand model Need not comply with IDEFØ rules An example is a flowchart to describe a procedure (action/decision sequence) that can be used to perform the process All of this additional material that exists outside the model is one of the reasons that IDEFØ is not in SYSML IDEFØ was developed when people were just starting to use modeling tools, and long before MBSE came into play 31
32 32
33 A Step By Step IDEFØ Tutorial (1) 1. Identify the system or process to be described. a. Use a name that clearly indicates what it is, possibly adding further description of what is and what is not included. 2. Identify the purpose or objectives of describing the process. a. This will help to determine whether IDEFØ is an appropriate tool, and will also help when making other decisions, for example whether to decompose the system further at lower levels. 3. Decide on the viewpoint from which the process is to be described. a. For example, a sales manager might have a broader view of a sales process than a sales person, as the sales manager includes the clerical activities in the sales office as well as the customer-salesperson process. b. The objectives from step 2 will help with this decision. For example, if the objective is to improve the amount of direct sales, then the viewpoint of the salesperson may be most appropriate. 4. Identify the decomposition strategy to be used. a. This is the set of rules to use when deciding how to break down activities into sub-activities, and may depend on the type of system being described and the objectives from step 2. Possible strategies include: 1) Functional decomposition breaks down activities according to what is done, rather than how it is done, and is probably the most common strategy. 2) Role decomposition breaks down things according to who does what. It can be an easy and useful starting point, but is likely to constrain improvements if it is maintained. 3) Subsystems decomposition divides systems first by major subsystem. This is useful when these subsystems are largely independent of one another. Lifecycle decomposition breaks down a system first by the phases of activity. Again, this is most useful when these phases are clearly defined and relatively independent. 33
34 A Step By Step IDEFØ Tutorial (2) 5. Before starting to draw diagrams, gather information about the system. a. This may start with reading of existing documents or observing the process in action, but the most useful activity is likely to be formal interviews with selected people. This not only is the best source of information, but it will also help to gain involvement and acceptance in any later improvements. Use the following process for interviews: 1) In the initial interview, aim first to agree the purpose and viewpoint, then find sufficient details to be able to draw the first two levels only (A-0 and A0). 2) Before each interview, review existing information and identify the scope of what is to be identified. 3) In interviews, work to acquire the most useful information, asking open questions, probing in key areas and checking the validity of assumptions. First, find out what is produced by and used within the process, including inputs, controls, outputs and mechanisms. This can be helped by asking questions of the process, starting with outputs (What is produced?) and work backwards (What is needed to produce this?). This will result in a list of items (often called the data list) that will form the arrows in the diagram. 4) Next, use the data list to identify the list of activities within the process, asking how items are used or produced. 5) Then explore how activities and data items relate to one another and how they group together. The notes may look like the figure on the next slide. 34
35 A Step By Step IDEFØ Tutorial (3) 35
36 A Step By Step IDEFØ Tutorial (4) 6. From the information gained in step 5, draw a set of diagrams. Draw the A0 diagram first, as illustrated, then summarize this in the A-0 diagram. When drawing a diagram, use the following sequence of actions: a. Use the decomposition strategy from step 4 to identify between three and six activities that will be shown on the diagram (around four is often best). It can be useful to try several different decompositions before settling on one. b. Sort these activities into the order of dominance. The more dominant of a pair of activities is one which has the greatest influence over the other. For example 'produce plan' has higher dominance than 'build product'. c. Place the activity boxes on the diagram, using the general layout strategy of putting most dominant activity in the top left, with subsequent activities along the diagonal, such that the least dominant activity ends up in the bottom right corner. When positioning the activities, try to think ahead to where arrows will go. Put the name of each activity in its box. d. Draw the arrows for each data item, starting with inputs and outputs, then adding controls then mechanisms. 1) Combine and split lines to help simplify the diagram. 2) When the lines are drawn, write in the labels for each line, being careful that the label cannot mistakenly be confused with another item. 3) If a label is not clearly associated with a single line, draw a short squiggly line between it and the line. e. Add parentheses ('tunnel' marks) to the end of any line which will not be shown in its parent or child diagram, as illustrated. Tunnel items that will not add useful information elsewhere. f. Identify the diagram with a node name, title and C-number, as illustrated on next slide. 1) It may also be useful to add other data, such as the date and the status of the diagram (e.g. initial, draft, final). Use a log, as illustrated, to ensure that all C-numbers are unique. g. Review the completed diagram for correctness, consistency, completeness and clarity. Check it against the purpose (step 2), viewpoint (step 3), decomposition strategy (step 4) and available information (step 5). Revise and repeat the above steps as necessary. 36
37 A Step By Step IDEFØ Tutorial (5) A-0 Diagram 37
38 A Step By Step IDEFØ Tutorial (6) 7. For each diagram, it is useful to write a Glossary page that further describes each data item, as illustrated. This can contain any text that will help the understanding of individual items or the overall system, although it should be kept brief, to avoid an 'information overload'. 38
39 A Step By Step IDEFØ Tutorial (7) 8. Decide whether to review the pages produced so far. a. It is useful to review early, when the A-0 and A0 diagrams (and possibly the level below) are completed, and subsequently when significant changes have been made. 1) If you do hold a review until all pages are completed, then this can result in significant extra effort being spent in rework. b. When holding a review, first create a kit, consisting of all pages requiring review, together with a cover page, and send it to appropriate contributing experts for review. 1) The cover page details the reviewer list, the contents of the kit and what is expected of the reviewers, including when to return it and any other special instructions. c. The reviewers read the pages in the kit and write corrections, in red directly on the pages of the kit, before returning it to the author. Specific items to review include: 1) The detail of each diagram, including the title and node name, all activities and arrows, additional glossaries and other material. 2) The overall system, and how the diagrams fit together, including use of the stated breakdown strategy. 3) How well the stated viewpoint is represented. d. The author then examines the reviewer's corrections and writes comments in blue ink (thus differentiating from the reviewer's corrections). 1) Agreement with reviewer corrections are shown with ticks and other comments are written alongside. e. The author and each reviewer then meet and discuss the comments and corrections. They agree to actual changes which the author then implements. 1) Make sure that when an item is changed, all other diagrams affected by the change are also updated. 39
40 A Step By Step IDEFØ Tutorial (8) 9. For each box which has not yet been decomposed, decide whether it is worth taking this step, or whether sufficient detail exists at this point. Considerations of whether to stop decomposition include: a. The final set of diagrams (or 'model') should contain sufficient detail to satisfy the stated purpose from step 2. b. A good point to stop is when boxes start saying 'how' instead of 'what', or where the viewpoint changes. c. Boxes should describe activities that are solid and unique functions, not trivial items nor duplicates of other boxes. d. For boxes that are to be decomposed further, the above process of interview, create and review is repeated as required. 1) Generally, the process experts should be fully involved, but they should not be worn down with too many interviews and reviews, as this is likely to cause them to become annoyed and disinterested, with consequent damage to the model and its use. 40
41 IDEFØ Class Exercise Consider the A-0 Process for System Level Design as defined below. Draw the A0 diagram of this process. Design Function Major Inputs Major Outputs Develop Operational Concept Define System Boundary with External Systems Diagram Develop System Objectives Hierarchy Develop, Analyze and Refine Requirements (Stakeholders and System) Ensure Requirements Feasibility Define the Test System Requirements Obtain Approval of System Documentation Stakeholders Inputs Objective Hierarchy & Value Parameters for Meta-System Recommended Concept Operational Concept Operational Concept Stakeholders Inputs Operational Concept System Boundary, Inputs & Outputs Objectives Hierarchy Stakeholders Inputs Stakeholders & Systems Requirements SE Team s Inputs Stakeholders & Systems Requirements Stakeholders Inputs Stakeholders & Systems Requirements Operational Concept System Concept Input-output traces Meta-system MOEs System Boundary, System s Inputs and Outputs System-level Objectives Hierarchy Stakeholders & Systems Requirements Design Feasibility Test System Requirements Stakeholder & System Requirements Documents 41
42 Full Example See IDEFØ For Widgets.pdf in references 42
Process Analysis and Modeling Using IDEF0. School of Mechanical, Industrial, & Manufacturing Engineering
Process Analysis and Modeling Using IDEF0 IDEF0 Standard http://www.itl.nist.gov/fipspubs/idef02.doc 2 IDEF0 Integrated DEFinition language 0 Originally SADT System Analysis and Design Technique Developed
More informationProcess Analysis and Modeling Using IDEF0
Process Analysis and Modeling Using IDEF0 continued School of Mechanical, Industrial, & Manufacturing Engineerin Tunneled Arrows Arrows that provide information at one level of decomposition but are not
More informationModel Based Systems Engineering with MagicGrid
November 2, 2016 Model Based Systems Engineering with MagicGrid No Magic, Inc. System Model as an Integration Framework Need for Ecosystem 2 2012-2014 by Sanford Friedenthal 19 The modeling language is
More informationAdvanced Manufacturing Laboratory Department of Industrial Engineering. Sharif University of Technology
Advanced Manufacturing Laboratory Department of Industrial Engineering Sharif University of Technology Session # 6 Instructor Omid Fatahi Valilai, Ph.D. Industrial Engineering Department, Sharif University
More informationModel-Based Systems Engineering Methodologies. J. Bermejo Autonomous Systems Laboratory (ASLab)
Model-Based Systems Engineering Methodologies J. Bermejo Autonomous Systems Laboratory (ASLab) Contents Introduction Methodologies IBM Rational Telelogic Harmony SE (Harmony SE) IBM Rational Unified Process
More informationTowards Integrated System and Software Modeling for Embedded Systems
Towards Integrated System and Software Modeling for Embedded Systems Hassan Gomaa Department of Computer Science George Mason University, Fairfax, VA hgomaa@gmu.edu Abstract. This paper addresses the integration
More information1: Assemblage & Hierarchy
What: 1: Assemblage & Hierarchy 2 compositional sequences o abstract, line compositions based on a 9 square grid o one symmetrical o one asymmetrical Step 1: Collage Step 2: Additional lines Step 3: Hierarchy
More informationCSE - Annual Research Review. From Informal WinWin Agreements to Formalized Requirements
CSE - Annual Research Review From Informal WinWin Agreements to Formalized Requirements Hasan Kitapci hkitapci@cse.usc.edu March 15, 2005 Introduction Overview EasyWinWin Requirements Negotiation and Requirements
More informationIndiana K-12 Computer Science Standards
Indiana K-12 Computer Science Standards What is Computer Science? Computer science is the study of computers and algorithmic processes, including their principles, their hardware and software designs,
More informationGEO/EVS 425/525 Unit 2 Composing a Map in Final Form
GEO/EVS 425/525 Unit 2 Composing a Map in Final Form The Map Composer is the main mechanism by which the final drafts of images are sent to the printer. Its use requires that images be readable within
More informationRequirements Analysis aka Requirements Engineering. Requirements Elicitation Process
C870, Advanced Software Engineering, Requirements Analysis aka Requirements Engineering Defining the WHAT Requirements Elicitation Process Client Us System SRS 1 C870, Advanced Software Engineering, Requirements
More informationCC532 Collaborative System Design
CC532 Collaborative Design Part I: Fundamentals of s Engineering 5. s Thinking, s and Functional Analysis Views External View : showing the system s interaction with environment (users) 2 of 24 Inputs
More informationAn Integrated Framework for Assembly-Oriented Product Design and Optimization
Volume 19, Number 2 - February 2003 to April 2003 An Integrated Framework for Assembly-Oriented Product Design and Optimization By Dr. Qiang Su and Dr. Shana Shiang-Fong Smith KEYWORD SEARCH CAD CIM Design
More informationUsing Dynamic Views. Module Overview. Module Prerequisites. Module Objectives
Using Dynamic Views Module Overview The term dynamic views refers to a method of composing drawings that is a new approach to managing projects. Dynamic views can help you to: automate sheet creation;
More informationTHE CONSTRUCTION- AND FACILITIES MANAGEMENT PROCESS FROM AN END USERS PERSPECTIVE - ProFacil
CEC 99 Björk, Bo-Christer, Nilsson, Anders, Lundgren, Berndt Page of 9 THE CONSTRUCTION- AND FACILITIES MANAGEMENT PROCESS FROM AN END USERS PERSPECTIVE - ProFacil Björk, Bo-Christer, Nilsson, Anders,
More informationIAASB Main Agenda (March, 2015) Auditing Disclosures Issues and Task Force Recommendations
IAASB Main Agenda (March, 2015) Agenda Item 2-A Auditing Disclosures Issues and Task Force Recommendations Draft Minutes from the January 2015 IAASB Teleconference 1 Disclosures Issues and Revised Proposed
More informationReal Analog Chapter 3: Nodal & Mesh Analysis. 3 Introduction and Chapter Objectives. 3.1 Introduction and Terminology
Real Analog Chapter 3: Nodal & Mesh Analysis 1300 Henley Court Pullman, WA 99163 509.334.6306 www.store.digilent.com 3 Introduction and Chapter Objectives In Chapters 1 & 2, we introduced several tools
More informationKnowledge Capture, Cross Boundary Communication and Early Validation with Dynamic A3 Architectures
Knowledge Capture, Cross Boundary Communication and Early Validation with Dynamic A3 Architectures Vickram Singh Dresser-Rand AS Kongsberg, Norway vickram.sngh@gmail.com Gerrit Muller Buskerud University
More informationUNIT-III LIFE-CYCLE PHASES
INTRODUCTION: UNIT-III LIFE-CYCLE PHASES - If there is a well defined separation between research and development activities and production activities then the software is said to be in successful development
More informationAddendum 27: Personalized Meander
Addendum 27: Personalized Meander About the Author: Lynn Mintz Photo Lynn Mintz is a Florida resident. She spends summers in New Jersey. Lynn has been quilting, embroidering and digitizing for 20 years.
More informationJoint Steering Committee for Development of RDA Kathy Glennan, ALA Representative 2.7 Production Statement: changing method of recording
page 1 of 25 To: From: Subject: Joint Steering Committee for Development of RDA Kathy Glennan, ALA Representative 2.7 Production Statement: changing method of recording ALA thanks BL for this proposal
More informationThe Industry 4.0 Journey: Start the Learning Journey with the Reference Architecture Model Industry 4.0
The Industry 4.0 Journey: Start the Learning Journey with the Reference Architecture Model Industry 4.0 Marco Nardello 1 ( ), Charles Møller 1, John Gøtze 2 1 Aalborg University, Department of Materials
More informationManaging the Innovation Process. Development Stage: Technical Problem Solving, Product Design & Engineering
Managing the Innovation Process Development Stage: Technical Problem Solving, Product Design & Engineering Managing the Innovation Process The Big Picture Source: Lercher 2016, 2017 Source: Lercher 2016,
More informationSimulating the Architectural Design Process through Matrix-Based Method
2011 2 nd International Conference on Construction and Project Management IPEDR vol.15 (2011) (2011) IACSIT Press, Singapore Simulating the Architectural Design Process through Matrix-Based Method Khairul
More informationAbstract. Justification. Scope. RSC/RelationshipWG/1 8 August 2016 Page 1 of 31. RDA Steering Committee
Page 1 of 31 To: From: Subject: RDA Steering Committee Gordon Dunsire, Chair, RSC Relationship Designators Working Group RDA models for relationship data Abstract This paper discusses how RDA accommodates
More informationDimensioning the Rectangular Problem
C h a p t e r 3 Dimensioning the Rectangular Problem In this chapter, you will learn the following to World Class standards: 1. Creating new layers in an AutoCAD drawing 2. Placing Centerlines on the drawing
More informationTHE APPLICATION OF SYSTEMS ENGINEERING ON THE BUILDING DESIGN PROCESS
THE APPLICATION OF SYSTEMS ENGINEERING ON THE BUILDING DESIGN PROCESS A.Yahiaoui 1, G. Ulukavak Harputlugil 2, A.E.K Sahraoui 3 & J. Hensen 4 1 & 4 Center for Building & Systems TNO-TU/e, 5600 MB Eindhoven,
More informationThis presentation uses concepts addressed by Stevens lectures, by SE books
ARCHITECTURES Tsunami Warning System Manolo Omiciuolo Space System Engineer RUAG Space AG This presentation covers a personal elaboration of topics addressed during a post-grad certificate in Space System
More informationNational Standard of the People s Republic of China
ICS 01.120 A 00 National Standard of the People s Republic of China GB/T XXXXX.1 201X Association standardization Part 1: Guidelines for good practice Click here to add logos consistent with international
More informationGuide to Connected Earth s Telecommunications Object Thesaurus 1.0
Guide to Connected Earth s Telecommunications Object Thesaurus 1.0 Background and administration The version of the Connected Earth Telecommunications Object Thesaurus that is live on the Connected Earth
More informationNX 7.5. Table of Contents. Lesson 3 More Features
NX 7.5 Lesson 3 More Features Pre-reqs/Technical Skills Basic computer use Completion of NX 7.5 Lessons 1&2 Expectations Read lesson material Implement steps in software while reading through lesson material
More informationPhysics 253 Fundamental Physics Mechanic, September 9, Lab #2 Plotting with Excel: The Air Slide
1 NORTHERN ILLINOIS UNIVERSITY PHYSICS DEPARTMENT Physics 253 Fundamental Physics Mechanic, September 9, 2010 Lab #2 Plotting with Excel: The Air Slide Lab Write-up Due: Thurs., September 16, 2010 Place
More informationSoftware Engineering: A Practitioner s Approach, 7/e. Slides copyright 1996, 2001, 2005, 2009 by Roger S. Pressman
Chapter 9 Architectural Design Slide Set to accompany Software Engineering: A Practitioner s Approach, 7/e by Roger S. Pressman Slides copyright 1996, 2001, 2005, 2009 by Roger S. Pressman For non-profit
More informationA FRAMEWORK FOR PERFORMING V&V WITHIN REUSE-BASED SOFTWARE ENGINEERING
A FRAMEWORK FOR PERFORMING V&V WITHIN REUSE-BASED SOFTWARE ENGINEERING Edward A. Addy eaddy@wvu.edu NASA/WVU Software Research Laboratory ABSTRACT Verification and validation (V&V) is performed during
More informationUML and Patterns.book Page 52 Thursday, September 16, :48 PM
UML and Patterns.book Page 52 Thursday, September 16, 2004 9:48 PM UML and Patterns.book Page 53 Thursday, September 16, 2004 9:48 PM Chapter 5 5 EVOLUTIONARY REQUIREMENTS Ours is a world where people
More informationDigital Fabrication Production System Theory: towards an integrated environment for design and production of assemblies
Digital Fabrication Production System Theory: towards an integrated environment for design and production of assemblies Dimitris Papanikolaou Abstract This paper introduces the concept and challenges of
More informationSelecting, Developing and Designing the Visual Content for the Polymer Series
Selecting, Developing and Designing the Visual Content for the Polymer Series A Review of the Process October 2014 This document provides a summary of the activities undertaken by the Bank of Canada to
More informationTIES: An Engineering Design Methodology and System
From: IAAI-90 Proceedings. Copyright 1990, AAAI (www.aaai.org). All rights reserved. TIES: An Engineering Design Methodology and System Lakshmi S. Vora, Robert E. Veres, Philip C. Jackson, and Philip Klahr
More informationUNIT 5 Games and social media to promote intergenerational learning. Module 3 Tools to invent games. Advanced Training Course
2012-2013 Module 3 Tools to invent games Advanced Training Course Adults Learning for Intergenerational Creative Experiences This training course is delivered in the context of LLP Project GRUNDTVIG-ALICE
More informationAnalyzing Engineering Contributions using a Specialized Concept Map
Analyzing Engineering Contributions using a Specialized Concept Map Arnon Sturm 1,2, Daniel Gross 1, Jian Wang 1,3, Eric Yu 1 University of Toronto 1, Ben-Gurion University of the Negev 2, Wuhan University
More informationTile Number and Space-Efficient Knot Mosaics
Tile Number and Space-Efficient Knot Mosaics Aaron Heap and Douglas Knowles arxiv:1702.06462v1 [math.gt] 21 Feb 2017 February 22, 2017 Abstract In this paper we introduce the concept of a space-efficient
More informationISO/TC145-IEC/SC3C JWG 11 N 16A
ISO/TC145-IEC/SC3C JWG 11 N 16A ISO ORGANISATION INTERNATIONALE DE NORMALISATION INTERNATIONAL ORGANIZATION FOR STANDARDIZATION IEC COMMISSION ÉLECTROTECHNIQUE INTERNATIONALE INTERNATIONAL ELECTROTECHNICAL
More informationTables: Tables present numbers for comparison with other numbers. Data presented in tables should NEVER be duplicated in figures, and vice versa
Tables and Figures Both tables and figures are used to: support conclusions illustrate concepts Tables: Tables present numbers for comparison with other numbers Figures: Reveal trends or delineate selected
More informationClick here to give us your feedback. New FamilySearch Reference Manual
Click here to give us your feedback. New FamilySearch Reference Manual January 25, 2011 2009 by Intellectual Reserve, Inc. All rights reserved Printed in the United States of America English approval:
More informationISO/TC145-IEC/SC3C JWG 11 N 16E
ISO/TC145-IEC/SC3C JWG 11 N 16E ISO ORGANISATION INTERNATIONALE DE NORMALISATION INTERNATIONAL ORGANIZATION FOR STANDARDIZATION IEC COMMISSION ÉLECTROTECHNIQUE INTERNATIONALE INTERNATIONAL ELECTROTECHNICAL
More information1 Sketching. Introduction
1 Sketching Introduction Sketching is arguably one of the more difficult techniques to master in NX, but it is well-worth the effort. A single sketch can capture a tremendous amount of design intent, and
More informationModule 5. DC to AC Converters. Version 2 EE IIT, Kharagpur 1
Module 5 DC to AC Converters Version 2 EE IIT, Kharagpur 1 Lesson 37 Sine PWM and its Realization Version 2 EE IIT, Kharagpur 2 After completion of this lesson, the reader shall be able to: 1. Explain
More informationSummer of Sleuthing Saving Our Stories
Family History Library Summer of Sleuthing Saving Our Stories Adults Family History Summer Challenges SOS! Your ancestors can be lost in time if you don t do something to ensure they are remembered. You
More informationGrafiska symboler för scheman Del 1: Allmän information och register. Graphical symbols for diagrams Part 1: General information and indexes
SVENSK STANDARD SS-ISO 14617-1 Fastställd 2002-10-11 Utgåva 1 Grafiska symboler för scheman Del 1: Allmän information och register Graphical symbols for diagrams Part 1: General information and indexes
More information30V 30 R1 120V R V 30 R1 120V. Analysis of a single-loop circuit using the KVL method
Analysis of a singleloop circuit using the KVL method Below is our circuit to analyze. We shall attempt to determine the current through each element, the voltage across each element, and the power delivered
More informationF. Tip and M. Weintraub REQUIREMENTS
F. Tip and M. Weintraub REQUIREMENTS UNIT OBJECTIVE Understand what requirements are Understand how to acquire, express, validate and manage requirements Thanks go to Martin Schedlbauer and to Andreas
More informationMODELS OF ELECTRONIC PACKAGE ENGINEERING
EEP-Vol. 19-1, Advances in Electronic Packaging -- 1997 Volume 1, ASME 1997 MODELS OF ELECTRONIC PACKAGE ENGINEERING Fred L. Cox III Georgia Tech Research Institute Atlanta, Georgia Gintautas B. Jazbutis
More informationNEMA XR X-ray Equipment for Interventional Procedures User Quality Control Mode
NEMA XR 27-2012 X-ray Equipment for Interventional Procedures User Quality Control Mode Published by: National Electrical Manufacturers Association 1300 North 17th Street, Suite 1752 Rosslyn, Virginia
More informationThe case study Encounter Section About case studies. Encounter
4 th Workshop Software Engineering Education and Reverse Engineering Zagreb, 5 12 September 2004 The case study Encounter Section About case studies Živana Komlenov Department of Mathematics and Informatics
More informationSIMGRAPH - A FLIGHT SIMULATION DATA VISUALIZATION WORKSTATION. Joseph A. Kaplan NASA Langley Research Center Hampton, Virginia
SIMGRAPH - A FLIGHT SIMULATION DATA VISUALIZATION WORKSTATION Joseph A. Kaplan NASA Langley Research Center Hampton, Virginia Patrick S. Kenney UNISYS Corporation Hampton, Virginia Abstract Today's modern
More informationThis is a preview - click here to buy the full publication
TECHNICAL REPORT IEC/TR 62794 Edition 1.0 2012-11 colour inside Industrial-process measurement, control and automation Reference model for representation of production facilities (digital factory) INTERNATIONAL
More informationUnit 2. Circuit Analysis Techniques. 2.1 The Node-Voltage Method
Unit 2 Circuit Analysis Techniques In this unit we apply our knowledge of KVL, KCL and Ohm s Law to develop further techniques for circuit analysis. The material is based on Chapter 4 of the text and that
More informationUNIT 5a STANDARD ORTHOGRAPHIC VIEW DRAWINGS
UNIT 5a STANDARD ORTHOGRAPHIC VIEW DRAWINGS 5.1 Introduction Orthographic views are 2D images of a 3D object obtained by viewing it from different orthogonal directions. Six principal views are possible
More informationSample VA Technical Documentation Assessments
Sample 243-251-VA Technical Documentation Assessments EVALUATION OF ASSESSMENT TOOLS USED TO MEASURE ACHIEVEMENT OF IET COURSE COMPETENCIES Please attach copies of all assessment tools used in this section
More informationClass #8: Experiment Diodes Part I
Class #8: Experiment Diodes Part I Purpose: The objective of this experiment is to become familiar with the properties and uses of diodes. We used a 1N914 diode in two previous experiments, but now we
More informationSPECIFICATION FOR PAPER STATIONERY ITEMS FOR SCHOOLS ( First Revision of IS 5195)
FOR BIS USE ONLY DOC:CHD15 (1857)C April 2011 BUREAU OF INDIAN STANDARDS Draft Indian Standard SPECIFICATION FOR PAPER STATIONERY ITEMS FOR SCHOOLS ( First Revision of IS 5195) (Not to be reproduced without
More informationPORTAGE COUNTY WATER RESOURCES DRAFTING STANDARDS. Date: January 26, 2001
PORTAGE COUNTY WATER RESOURCES DRAFTING STANDARDS Date: January 26, 2001 Portage County Water Resources Drafting Standards. AutoCad 2000/Land Development Desktop R2 Friday, January 26, 2001 Preface: Part
More informationPull Down Menu View Toolbar Design Toolbar
Pro/DESKTOP Interface The instructions in this tutorial refer to the Pro/DESKTOP interface and toolbars. The illustration below describes the main elements of the graphical interface and toolbars. Pull
More informationModel Based Systems of Systems Engineering. Fran McCafferty Principal Systems Engineer
Model Based Systems of Systems Engineering Fran McCafferty Principal Systems Engineer fmccafferty@vitechcorp.com 1 System of Systems v System of Subsystems The major distinction between systems as elements
More informationLabVIEW Day 2: Other loops, Other graphs
LabVIEW Day 2: Other loops, Other graphs Vern Lindberg From now on, I will not include the Programming to indicate paths to icons for the block diagram. I assume you will be getting comfortable with the
More informationSpreadsheets 3: Charts and Graphs
Spreadsheets 3: Charts and Graphs Name: Main: When you have finished this handout, you should have the following skills: Setting up data correctly Labeling axes, legend, scale, title Editing symbols, colors,
More informationMILITARY PRODUCTION MINISTRY Training Sector. Using and Interpreting Information. Lecture 6. Flow Charts.
MILITARY PRODUCTION MINISTRY Training Sector Using and Interpreting Information Lecture 6 Saturday, March 19, 2011 2 What is the Flow Chart? The flow chart is a graphical or symbolic representation of
More informationIntroductions. Characterizing Knowledge Management Tools
Characterizing Knowledge Management Tools Half-day Tutorial Developed by Kurt W. Conrad, Brian (Bo) Newman, and Dr. Art Murray Presented by Kurt W. Conrad conrad@sagebrushgroup.com Based on A ramework
More informationInstructions for Use of Resolution Chart
Camera & Imaging Products Association Instructions for Use of Resolution Chart 1. Introduction Thank you very much for your purchase of this resolution chart for digital still cameras. This resolution
More informationMAS336 Computational Problem Solving. Problem 3: Eight Queens
MAS336 Computational Problem Solving Problem 3: Eight Queens Introduction Francis J. Wright, 2007 Topics: arrays, recursion, plotting, symmetry The problem is to find all the distinct ways of choosing
More informationUNECE Comments to the draft 2007 Petroleum Reserves and Resources Classification, Definitions and Guidelines.
UNECE Comments to the draft 2007 Petroleum Reserves and Resources Classification, Definitions and Guidelines. Page 1 of 13 The Bureau of the UNECE Ad Hoc Group of Experts (AHGE) has carefully and with
More informationStudent name: Class: Date:
Writing a procedure Write about the goal. Write what the goal of the procedure is. This should be a short and simple sentence. List the materials and equipment. List everything you need to do the procedure.
More informationTHE TWO COMPONENTS OF A GOOD WRITING CONFERENCE
THE TWO COMPONENTS OF A GOOD WRITING CONFERENCE Component One: Talk with the students about what they are doing as writers Listen to your student What are you doing well as a writer? How is the writing
More informationUnit 5 Shape and space
Unit 5 Shape and space Five daily lessons Year 4 Summer term Unit Objectives Year 4 Sketch the reflection of a simple shape in a mirror line parallel to Page 106 one side (all sides parallel or perpendicular
More informationSOFTWARE ARCHITECTURE
SOFTWARE ARCHITECTURE Foundations, Theory, and Practice Richard N. Taylor University of California, Irvine Nenad Medvidovic University of Southern California Eric M. Dashofy The Aerospace Corporation WILEY
More informationIntroduction to Design Process ME122
Introduction to ME122 https://www.nasa.gov 1. Identify the problem Often identified by a customer need. Would typically be a statement such as How can I design a that will? 2. Define requirements (criteria)
More informationThe secret behind mechatronics
The secret behind mechatronics Why companies will want to be part of the revolution In the 18th century, steam and mechanization powered the first Industrial Revolution. At the turn of the 20th century,
More informationLean Enablers for Managing Engineering Programs
Lean Enablers for Managing Engineering Programs Presentation to the INCOSE Enchantment Chapter June 13 2012 Josef Oehmen http://lean.mit.edu 2012 Massachusetts Institute of Technology, Josef Oehmen, oehmen@mit.edu
More informationIntroduction to QTO. Objectives of QTO. Getting Started. Requirements. Creating a Bill of Quantities. Updating an existing Bill of Quantities
QTO User Manual Contents Introduction to QTO... 5 Objectives of QTO... 5 Getting Started... 5 QTO Manager... 6 QTO Layout... 7 Bill of Quantities... 8 Measure Folders... 9 Drawings... 10 Zooming and Scrolling...
More informationarxiv: v2 [math.gt] 21 Mar 2018
Tile Number and Space-Efficient Knot Mosaics arxiv:1702.06462v2 [math.gt] 21 Mar 2018 Aaron Heap and Douglas Knowles March 22, 2018 Abstract In this paper we introduce the concept of a space-efficient
More informationENGINEERING DRAWINGS MANAGEMENT POLICY (IFC/AS BUILTS)
Approval Amendment Record Approval Date Version Description 15/10/2015 1 This policy takes precedence over L1-NAM-PRO-003 Infrastructure As Built Drawing Management due to business restructures. New Content
More informationGeometric dimensioning & tolerancing (Part 1) KCEC 1101
Geometric dimensioning & tolerancing (Part 1) KCEC 1101 Introduction Before an object can be built, complete information about both the size and shape of the object must be available. The exact shape of
More informationCADTH HEALTH TECHNOLOGY MANAGEMENT PROGRAM Horizon Scanning Products and Services Processes
CADTH HEALTH TECHNOLOGY MANAGEMENT PROGRAM Horizon Scanning Products and Services Processes Service Line: Health Technology Management Program Version: 1.0 Publication Date: September 2017 Report Length:
More information(Refer Slide Time: 01:45)
Digital Communication Professor Surendra Prasad Department of Electrical Engineering Indian Institute of Technology, Delhi Module 01 Lecture 21 Passband Modulations for Bandlimited Channels In our discussion
More informationRoadmapping. Market Products Technology. People Process. time, ca 5 years
- drives, requires supports, enables Customer objectives Application Functional Conceptual Realization Market Products Technology People Marketing Architect technology, process people manager time, ca
More informationSeparation of Concerns in Software Engineering Education
Separation of Concerns in Software Engineering Education Naji Habra Institut d Informatique University of Namur Rue Grandgagnage, 21 B-5000 Namur +32 81 72 4995 nha@info.fundp.ac.be ABSTRACT Separation
More informationLEVEL 2 / UNIT GH12 Step By Step
Student Name Student Unit: Tutorial: Contributor: Cutting Hair Using Basic Techniques Graduated Bob Haircut Stacey Broughton Stacey Broughton s tutorial cover the graduated bob, which is a vital part of
More informationSECTION SUBMITTAL PROCEDURES PART 1 - GENERAL 1.1 RELATED DOCUMENTS
SECTION 01 33 00 - SUBMITTAL PROCEDURES PART 1 - GENERAL 1.1 RELATED DOCUMENTS A. Drawings and general provisions of the Contract, including General and Supplementary Conditions and other Division 01 Specification
More informationQuick Start - ProDESKTOP
Quick Start - ProDESKTOP Tim Brotherhood ProDESKTOP page 1 of 27 Written by Tim Brotherhood These materials are 2000 Staffordshire County Council. Conditions of use Copying and use of these materials is
More informationAdvance Steel. Drawing Style Manager s guide
Advance Steel Drawing Style Manager s guide TABLE OF CONTENTS Chapter 1 Introduction...7 Details and Detail Views...8 Drawing Styles...8 Drawing Style Manager...9 Accessing the Drawing Style Manager...9
More information37 Game Theory. Bebe b1 b2 b3. a Abe a a A Two-Person Zero-Sum Game
37 Game Theory Game theory is one of the most interesting topics of discrete mathematics. The principal theorem of game theory is sublime and wonderful. We will merely assume this theorem and use it to
More informationOverview. The Game Idea
Page 1 of 19 Overview Even though GameMaker:Studio is easy to use, getting the hang of it can be a bit difficult at first, especially if you have had no prior experience of programming. This tutorial is
More informationScotian Basin Exploration Drilling Project: Timeline
Scotian Basin Exploration Drilling Project: Timeline When it comes to exploratory drilling programs that an operator proposes to conduct, the Canada- Nova Scotia Offshore Petroleum Board (CNSOPB) goes
More informationIssues in Emerging Health Technologies Bulletin Process
Issues in Emerging Health Technologies Bulletin Process Updated: April 2015 Version 1.0 REVISION HISTORY Periodically, this document will be revised as part of ongoing process improvement activities. The
More informationFIBONACCI KOLAMS -- AN OVERVIEW
FIBONACCI KOLAMS -- AN OVERVIEW S. Naranan This paper is an overview of all my work on Fibonacci Kolams as of end of the year 2015 that is included in my website www.vindhiya.com/snaranan/fk/index.htm
More informationA Knowledge-Centric Approach for Complex Systems. Chris R. Powell 1/29/2015
A Knowledge-Centric Approach for Complex Systems Chris R. Powell 1/29/2015 Dr. Chris R. Powell, MBA 31 years experience in systems, hardware, and software engineering 17 years in commercial development
More information7 Assessment Focuses Questions to get us thinking about our reading!
St Mary s CE Primary School 7 Assessment Focuses Questions to get us thinking about our reading! P.S. Parents can use these too to help question you about your reading! AF1 I can use a range of strategies
More informationMaking a Drawing Template
C h a p t e r 8 Addendum: Metric Making a Drawing Template In this chapter, you will learn the following to World Class standards: 1. Starting from Scratch 2. Creating New Layers in an progecad Drawing
More informationENGINEERING GRAPHICS ESSENTIALS. (A Text and Lecture Aid) Second Edition. Kirstie Plantenberg University of Detroit Mercy SDC PUBLICATIONS
ENGINEERING GRAPHICS ESSENTIALS (A Text and Lecture Aid) Second Edition Kirstie Plantenberg University of Detroit Mercy SDC PUBLICATIONS Schroff Development Corporation www.schroff.com www.schroff-europe.com
More informationEvaluation of Input Devices for Musical Expression: Borrowing Tools from HCI
Evaluation of Input Devices for Musical Expression: Borrowing Tools from HCI Marcelo Mortensen Wanderley Nicola Orio Outline Human-Computer Interaction (HCI) Existing Research in HCI Interactive Computer
More information