DOCSLIB.ORG

Information Integration for Concurrent Engineering (Iice) Idef4 Object-Oriented Design Method Report

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Information Integration for Concurrent Engineering (Iice) Idef4 Object-Oriented Design Method Report INFORMATION INTEGRATION FOR CONCURRENT ENGINEERING (IICE) IDEF4 OBJECT-ORIENTED DESIGN METHOD REPORT DRAFT - January 1995 KNOWLEDGE BASED SYSTEMS, INC. ONE KBSI PLACE 1408 UNIVERSITY DRIVE EAST COLLEGE STATION TX 77840-2335 HUMAN RESOURCES DIRECTORATE LOGISTICS RESEARCH DIVISION AIR FORCE SYSTEMS COMMAND WRIGHT-PATTERSON AIR FORCE BASE, OHIO 45433-6573 INFORMATION INTEGRATION FOR CONCURRENT ENGINEERING (IICE) IDEF4 OBJECT-ORIENTED DESIGN METHOD REPORT Version 2.0 DRAFT - January 1995 Knowledge Based Systems, Inc. One KBSI Place 1408 University Drive East College Station TX 77840-2335 Prepared for: Armstrong Laboratory Human Resources Group WPAFB OH 45433-6573 TABLE OF CONTENTS TABLE OF CONTENTS............................................................................................................................................. i LIST OF FIGURES .................................................................................................................................................... v LIST OF TABLES ..................................................................................................................................................... ix PREFACE.................................................................................................................................................................... x FOREWORD.............................................................................................................................................................. xi METHOD ANATOMY...................................................................................................................................................... xi FAMILY OF METHODS ................................................................................................................................................. xiii EXECUTIVE SUMMARY......................................................................................................................................... 1 WHAT IS IDEF4? ........................................................................................................................................................... 1 IDEF4 Layers........................................................................................................................................................... 2 IDEF4 Artifact Status............................................................................................................................................... 3 IDEF4 Design Models.............................................................................................................................................. 3 Design Features ....................................................................................................................................................... 3 WHY USE IDEF4? ......................................................................................................................................................... 3 HOW DOES IDEF4 WORK?............................................................................................................................................ 5 PURPOSE AND ORGANIZATION OF THIS DOCUMENT ....................................................................................................... 7 SUMMARY ..................................................................................................................................................................... 8 INTRODUCTION TO IDEF4.................................................................................................................................... 9 IDEF4 OBJECT-ORIENTED CONCEPTS............................................................................................................................ 9 Domains ................................................................................................................................................................... 9 Features, Artifacts, and Objects............................................................................................................................. 10 Object Instance....................................................................................................................................................... 13 Classes.................................................................................................................................................................... 14 Subclass/Superclass ............................................................................................................................................... 15 Partitions................................................................................................................................................................ 16 Attributes................................................................................................................................................................ 18 Object States........................................................................................................................................................... 19 Method ................................................................................................................................................................... 20 Message and Polymorphism................................................................................................................................... 21 Event....................................................................................................................................................................... 22 Object Life cycles ................................................................................................................................................... 23 Client/Server .......................................................................................................................................................... 23 Relationships and Roles ......................................................................................................................................... 24 Inheritance ............................................................................................................................................................. 25 Encapsulation and Information Hiding.................................................................................................................. 26 IDEF4 PROCEDURE ..................................................................................................................................................... 27 IDEF4 ORGANIZATION ................................................................................................................................................ 28 Static Model ........................................................................................................................................................... 29 Dynamic Model ...................................................................................................................................................... 29 Behavior Model...................................................................................................................................................... 30 Design Rationale Component................................................................................................................................. 30 Design Artifact Specifications................................................................................................................................ 30 SUMMARY ................................................................................................................................................................... 31 IDEF4 MODEL ORGANIZATION ........................................................................................................................ 33 i THE STATIC MODEL..................................................................................................................................................... 34 IDEF4 Structure Diagrams.................................................................................................................................... 35 IDEF4 Class Inheritance Diagram. ....................................................................................................................... 35 Relation Diagram..................................................................................................................................................................36 Link Diagram........................................................................................................................................................................37 Instance Link Diagram..........................................................................................................................................................37 BEHAVIOR MODEL....................................................................................................................................................... 38 Behavior Diagram.................................................................................................................................................. 38 DYNAMIC MODEL........................................................................................................................................................ 39 Client/Server Diagrams.........................................................................................................................................
Load more

Recommended publications
  • DATA MODELS to SUPPORT METROLOGY by Saeed
    DATA MODELS TO SUPPORT METROLOGY by Saeed Heysiattalab A dissertation submitted to the faculty of The University of North Carolina at Charlotte in partial fulfillment of the requirements for the degree of Doctor of Philosophy in Mechanical Engineering Charlotte 2017 Approved by: ______________________________ Dr. Edward P. Morse ______________________________ Dr. Robert G. Wilhelm ______________________________ Dr. Jimmie A Miller ______________________________ Dr. M. Taghi Mostafavi ______________________________ Dr. Jing Xiao ii ©2017 Saeed Heysiattalab ALL RIGHTS RESERVED iii ABSTRACT SAEED HEYSIATTALAB. Data models to support metrology (Under the supervision of Dr. EDWARD P. MORSE) The Quality Information Framework (QIF) is a project initiated in 2010 by the Dimensional Metrology Standards Consortium (DMSC is an American Standards Developing Organization) to address metrology interoperability. Specifically, the QIF supports the exchange of metrology-relevant information throughout the product lifecycle from the design stage through manufacturing, inspection, maintenance, and recycling / end-of-life processing. The QIF standard is implemented through a set of XML schemas called "Application Schemas" along with common core "XML schema libraries". Of these schemas, QIF Measurement Resources and QIF Rules are the two application schemas on which this research is focused. QIF Measurement Resources is an application schema developed to provide standard representations of physical measuring tools and components, and can be used to support measurement planning, statistical studies, traceability, etc. The Resources schema was supported by the creation of a new hierarchy of metrology resources in support of the product lifecycle. The QIF Rules schema is under development to provide the language with which manufacturers can define how dimensional measurement equipment is selected for various tasks, and how this equipment is used during the measurement task.
    [Show full text]
  • Modelling, Analysis and Design of Computer Integrated Manueactur1ng Systems
    MODELLING, ANALYSIS AND DESIGN OF COMPUTER INTEGRATED MANUEACTUR1NG SYSTEMS Volume I of II ABDULRAHMAN MUSLLABAB ABDULLAH AL-AILMARJ October-1998 A thesis submitted for the DEGREE OP DOCTOR OF.PHILOSOPHY MECHANICAL ENGINEERING DEPARTMENT, THE UNIVERSITY OF SHEFFIELD 3n ti]S 5íamc of Allai]. ¿Hoot (gractouo. iHHoßt ¿Merciful. ACKNOWLEDGEMENTS I would like to express my appreciation and thanks to my supervisor Professor Keith Ridgway for devoting freely of his time to read, discuss, and guide this research, and for his assistance in selecting the research topic, obtaining special reference materials, and contacting industrial collaborations. His advice has been much appreciated and I am very grateful. I would like to thank Mr Bruce Lake at Brook Hansen Motors who has patiently answered my questions during the case study. Finally, I would like to thank my family for their constant understanding, support and patience. l To my parents, my wife and my son. ABSTRACT In the present climate of global competition, manufacturing organisations consider and seek strategies, means and tools to assist them to stay competitive. Computer Integrated Manufacturing (CIM) offers a number of potential opportunities for improving manufacturing systems. However, a number of researchers have reported the difficulties which arise during the analysis, design and implementation of CIM due to a lack of effective modelling methodologies and techniques and the complexity of the systems. The work reported in this thesis is related to the development of an integrated modelling method to support the analysis and design of advanced manufacturing systems. A survey of various modelling methods and techniques is carried out. The methods SSADM, IDEFO, IDEF1X, IDEF3, IDEF4, OOM, SADT, GRAI, PN, 10A MERISE, GIM and SIMULATION are reviewed.
    [Show full text]
  • H)EF3 Technical Report Version 1.0 Chard J. Mayer Christopher P
    L. H)EF3 Technical Report Version 1.0 _| i L, _chard J. Mayer Christopher P. Menzel : i_:_pa_la S.D. Mayer Know!edge Based Systems Laboratory L Depar tment- 0 fin-dustrial Engineering Texas A&M University College Station TX 77843 Reviewed by Michad-K, Painter, Capt, USAF Armstrong Laboratory Logistics Research Division Wright-Patterson =Air Force Base, Ohio 45433-6503 :_ _=_January 1991 i _: ?_ | - , i (NASA-CR-I90279) {RESEARCH ACCOMPLISHED AT N92-26587 THE KNOWLEDGE BASED SYSTEMS LAB: IDEF3, VERSION 1.0] (Texas A&M Univ.) 56 p Unclag G]/_I 0086873 L == ; IDEF3 Technical Report Version 1.0 Richard J. Mayer Christopher P. Menzel Paula S.D. Mayer Knowledge Based Systems Laboratory Department of Industrial Engineering Texas A&M University College Station TX 77843 Reviewed by Michael K. Painter, Capt, USAF Armstrong Laboratory Logistics Research Division Wright-Patterson Air Force Base, Ohio 45433-6503 January 1991 umd w _- :7. m w Preface This paper describes the research accomplished at the Knowledge Based Systems Laboratory of the Department of Industrial Engineering at Texas A&M University. Funding for the Laboratory's research in Integrated Information System Development Methods and Tools has been provided by the Air Force Armstrong Laboratory, Logistics Research Division, AFWAL/LRL, Wright-Patterson Air Force Base, Ohio 45433, under the technical direction of USAF Captain Michael K. Painter, under subcontract through the NASA RICIS Program at the University of Houston. The authors and the design team wish to acknowledge the technical insights and ideas provided by Captain Painter in the performance of this research as well as his assistance in the preparation of this report.
    [Show full text]
  • The IDEF Family of Languages
    CHAPTER 10 The IDEF Family of Languages Christopher Menzel, Richard J. Mayer The purpose of this contribution is to serve as a clear introduction to the modeling languages of the three most widely used IDEF methods: IDEFO, IDEFIX, and IDEF3. Each language is presented in turn, beginning with a discussion of the underlying "ontology" the language purports to describe, followed by presentations of the syntax of the language - particularly the notion of a model for the language - and the semantical rules that determine how models are to be interpreted. The level of detail should be sufficient to enable the reader both to understand the intended areas of application of the languages and to read and construct simple models of each of the three types. 1 Introduction A modeling method comprises a specialized modeling language for represent­ ing a certain class of information, and a modeling methodology for collecting, maintaining, and using the information so represented. The focus of this paper will be on the languages of the three most widely used IDEF methods: The IDEFO business function modeling method, the IDEFIX data modeling method, and the IDEF3 process modeling method. Any usable modeling language has both a syntax and a semantics: a set of rules (often implicit) that determines the legitimate syntactic constructs of the language, and a set of rules (often implicit) the determines the meanings of those constructs. It is not the purpose of this paper is to serve as an exhaus­ tive reference manual for the three IDEF languages at issue. Nor will it dis­ cuss the methodologies that underlie the applications of the languages.
    [Show full text]
  • Analysis of Methods TECHNICAL REPORT
    Analysis of Methods Final Report Richard J. Mayer, ed. Knowledge Based Systems Laboratory Texas A&M University March 8, 1991 w -o _0 co ! m f_ U cD C 0 Z 0 Cooperative Agreement NCC 9-16 Research Activity No. IM.06: Methodologies for Integrated 0 Information Management Systems r CDOC NASA Johnson Space Center Information Systems Directorate Information Technology Division -J • 0 _D A _OE e._ ,t C I LL -C,-- ::2" I C" m E Research Institute for Computing and Information Systems v;I _0 University of Houston-C/ear Lake TECHNICAL REPORT The RICIS Concept The University of Houston-Clear Lake established the Research lnsUtute for Computing and Information Systems (RICIS) in 1986 to encourage the NASA Johnson Space Center (JSC) and local industry to actively support research in the computing and information sciences. As part of thls endeavor. UHCL proposed a partnership with JSC to Jointly define and manage an integrated program of research in advanced data processing technology needed for JSC's main missions, including administrative, engineering and science responsi- bilities. JSC agreed and entered into a continuing cooperative agreement with UHCL beginning in May 1986, to Jointly plan and execute such research through RICIS. Additionally, under Cooperative Agreement NCC 9-16, computing and educaUonal facilities are shared by the two instituUons to conduct the research. The UHCL/RICIS mission is to conduct, coordinate, and disseminate research and professional level edueaUon in computing and information systems to serve the needs of the government, industry, community and academia. RICIS combines resources ofUHCLand Itsgateway affiliatestoresearch and develop materials, prototypes and publications on topics of mutual interest to its sponsors and researchers.
    [Show full text]
  • Product Realization Process Modeling
    NAT’L INST. OF STAND & .TECH R I.C III! Ill" I" 'I mill mill II ml II II AlllDM NISTIR 5745 Product Realization Process Modeling: A study of requirements, methods and and research issues Kevin W. Lyons U.S. DEPARTMENT OF COMMERCE Technology Administration National Institute of Standards and Technology Gaithersburg, MD 20899 Michael R. Duffey Richard C. Anderson George Washington University QC 100 NIST .056 NO. 5745 1995 Product Realization Process Modeling: A study of requirements, methods and and research issues Kevin W. Lyons U.S. DEPARTMENT OF COMMERCE Technology Administration National Institute of Standards and Technology Gaithersburg, MD 20899 Michael R. Duffey Richard C. Anderson George Washington University June 1995 c U.S. DEPARTMENT OF COMMERCE Ronald H. Brown, Secretary TECHNOLOGY ADMINISTRATION Mary L. Good, Under Secretary for Technology NATIONAL INSTITUTE OF STANDARDS AND TECHNOLOGY Arati Prabhakar, Director . r•^ - . 'it'/ ' ' ' ' - ' ' -•*'1 X' . r • ^.,' v./f/v ’• '^^,. • T,?. - ^ •' V.y' ’ ' :AIa ' / ><- l> r / PRP Modeling: Page 2 1. Introduction 7 2. Definition of a PRP Model 8 3. Overview of PRP Methods and Modeling Issues in Manufacturing Industries 9 3.1 PERT-based Models 9 3.2 IDEF-based Models 10 3.3 Traditional PRP Modeling Practices 12 3.4 Emerging PRP Model Applications in Industry 14 3.5 Industry Requirements for PRP Models 14 4. Modeling Issues for Advanced PRP Computer Tools 16 4. 1 Activity Network Representations 17 4.2 Representing Design Iteration and Activity "Overlapping" 18 4.3 Uncertainty Modeling of a PRP 20 4.3.1 Some Simulation Considerations 20 4.3.2 Activity Duration Uncertainty 21 4.3.3 Concurrent Activities and Stochastic Modeling 22 4.3.4 Alternative Representations of Uncertainty 23 4.4 Representing Economic Information 24 4.5 Data Collection and Validation Issues for PRP Models 27 4.6 Knowledge-Based Representations in PRP Models 28 5.
    [Show full text]
  • Enabling an Executable Context Simulation Framework (ECSF)
    Old Dominion University ODU Digital Commons Computational Modeling & Simulation Computational Modeling & Simulation Engineering Theses & Dissertations Engineering Spring 2011 Adding Executable Context to Executable Architectures: Enabling an Executable Context Simulation Framework (ECSF) Johnny J. Garcia Old Dominion University Follow this and additional works at: https://digitalcommons.odu.edu/msve_etds Part of the Computer Sciences Commons Recommended Citation Garcia, Johnny J.. "Adding Executable Context to Executable Architectures: Enabling an Executable Context Simulation Framework (ECSF)" (2011). Doctor of Philosophy (PhD), Dissertation, Computational Modeling & Simulation Engineering, Old Dominion University, DOI: 10.25777/yr2g-yp42 https://digitalcommons.odu.edu/msve_etds/26 This Dissertation is brought to you for free and open access by the Computational Modeling & Simulation Engineering at ODU Digital Commons. It has been accepted for inclusion in Computational Modeling & Simulation Engineering Theses & Dissertations by an authorized administrator of ODU Digital Commons. For more information, please contact [email protected]. ADDING EXECUTABLE CONTEXT TO EXECUTABLE ARCHITECTURES: ENABLING AN EXECUTABLE CONTEXT SIMULATION FRAMEWORK (ECSF) by Johnny J. Garcia M.S. December, 2002, Florida Institute of Technology M.B.A. December, 2003, Florida Institute of Technology B.S. May, 1999, St. Leo College B.A. May, 1999, St. Leo College A dissertation submitted to the faculty of Old Dominion University in partial fulfillment of the Requirements for the degree of DOCTOR OF PHILOSOPHY MODELING AND SIMULATION OLD DOMINION UNIVERSITY May 2011 Approved by: Andreas Tolk (Director) Tom Pawlowski (Member) rederic D. McKenzie (Member) ABSTRACT ADDING EXECUTABLE CONTEXT TO EXECUTABLE ARCHITECTURES: ENABLING AN EXECUTABLE CONTEXT SIMULATION FRAMEWORK (ECSF) Johnny J. Garcia Old Dominion University, 2011 Director: Dr.
    [Show full text]
  • Ueml: Towards a Unified Enterprise Modelling Language
    3e Conférence Francophone de MOdélisation et SIMulation «Conception, Analyse et Gestion des Systèmes Industriels» MOSIM’01 – du 25 au 27 avril 2001 - Troyes (France) UEML: TOWARDS A UNIFIED ENTERPRISE MODELLING LANGUAGE F. VERNADAT Vice-chairman of the IFAC-IFIP Task Force on Architectures for Enterprise Integration LGIPM & MACSI-INRIA ENIM/Université de Metz Ile du Saulcy F-57045 Metz cedex 1, France Mél : [email protected] or [email protected] ABSTRACT : The paper presents the rationale and principles of a unified language devoted to the area of Enterprise Modelling. The language, named UEML, for Unified Enterprise Modelling Language, is not intended to replace existing languages but is intended to provide a uniform interface to enterprise modelling tools and a neutral format for exchange of enterprise models. It therefore builds on previous languages and provides constructs to cover function, information, resource and organization aspects of business entities. It is also aligned with results of CEN TC 310, ISO TC 184 and IFAC-IFIP GERAM efforts in the area of enterprise modelling and engineering. KEY-WORDS : Enterprise Modelling, Modelling languages, UEML 1. INTRODUCTION analysis. Models produced were mainly static. In the 80’s, specific methods have been proposed to model In today’s highly competitive global economy, many large manufacturing systems to support their design, business companies need to better understand and possibly with a link to simulation (e.g. IDEF suite of harness the way they operate. They must also frequently methods, GRAI method). EM has then significantly realign their organisation structure to face the need for improved shifting from an activity (or function) centred change as imposed by their environment for increased view to a more business process centred view as customer satisfaction in terms of quality, cost and delay.
    [Show full text]
  • SADT — Structured Analysis & Design Technique
    Workshop: SADT: Structured Analysis & Design Technique SADT — Structured Analysis & Design Technique Yuling Li 12/5/16 1 Workshop: SADT: Structured Analysis & Design Technique How to Make a Pizza? 2 Workshop: SADT: Structured Analysis & Design Technique 3 Workshop: SADT: Structured Analysis & Design Technique How to Make a Pizza (Process/Activities) Systematically? • Analysis Determine what the system will do • Design Define subsystems and their interfaces • Implementation Create the subsystem independently • Integration Combine the subsystems into a single unit • Testing Verify the system workings • Installation Make the system operational • Operation Use the system 4 Workshop: SADT: Structured Analysis & Design Technique “M models A if M answers questions about A” ---- Douglas T. Ross 5 Workshop: SADT: Structured Analysis & Design Technique Contents 1 Overview of SADT 2 Syntax and Semantics 3 SADT Diagrams 4 Cases 6 Workshop: SADT: Structured Analysis & Design Technique 1 Overview of SADT SADT IDEF0 IDEF Family 7 Workshop: SADT: Structured Analysis & Design Technique Emergent 1950s “hierarchic, layered modular system” SA Box ➕ 1960s “system of systems for building systems” SA Decomposition “top-down hierarchic decomposition” ➕ Cell 1970s “Hori’s Human-directed activity cell model” modelling “language for blueprinting systems” SADT • Douglas T. Ross developed SADT (1969-1973 ) • SADT is a trademark of SofTech, Inc. (After 1973) 8 Workshop: SADT: Structured Analysis & Design Technique Develop • During the 1970s, the U.S. Air Force Program
    [Show full text]
  • Tools Used in Modeling of the Economic Processes Marian Pompiliu Cristescu
    EBEEC 2019 Economies of the Balkan and Eastern European Countries Volume 2019 Conference Paper Tools Used in Modeling of the Economic Processes Marian Pompiliu Cristescu Abstract The paper aims at identifying the economic process modeling languages, starting from the premise that the main beneficiaries of the resulting models are economists or decision-makers, respectively economic researchers. There are a large number of languages that have been developed with different objectives, but they have all been used to describe business processes. Languages have studied different aspects of business processes (dynamic, functional, organizational, informational) and may be more or less formal, depending on the intended use and audience. There is no easy way to classify these languages along a single dimension. However, the languages fall into four groups, clearly defined scientifically or professionally: traditional process modeling languages, object-oriented languages, dynamic process modeling Corresponding Author: languages, and the integration of languages. Economic processes are generally very Marian Pompiliu Cristescu complex and, therefore, different points can be formulated about their modeling. [email protected] Keywords: Formal language, model, simulation, algorithm, business processes. Received: 17 November 2019 Accepted: 6 January 2019 Published: 12 January 2020 Publishing services provided by Knowledge E Marian Pompiliu 1. Introduction Cristescu. This article is distributed under the terms of Business units are complex organizational forms that involve customers, business units, the Creative Commons Attribution License, which resources, and even systems. They extend over many different processes that interact in permits unrestricted use and a seemingly chaotic way. When trying to change business processes in an organization, redistribution provided that the original author and source are change is confronted and confused with great complexity.
    [Show full text]
  • IDEF1 Information Modeling
    IDEF1 Information Modeling A Reconstruction of the Original Air Force Wright Aeronautical Laboratory Technical Report AFWAL-TR-81-4023 Dr. Richard J. Mayer, Editor Knowledge Based Systems, Inc. IDEF1 Information Modeling A Reconstruction of the Original Air Force Wright Aeronautical Laboratory Technical Report AFWAL-TR-81-4023 Dr. Richard J. Mayer, Editor Knowledge Based Systems, Inc. Knowledge Based Systems, Inc. One KBSI Place 1408 University Drive East College Station, Texas 77840-2335 (409) 260-5274 This manual is copyrighted, with all rights reserved. Under the copyright laws, the manual may not be reproduced in any form or by any means, in whole or in part, without written consent of Knowledge Based Systems, Inc. (KBSI). Under the law, reproducing includes translating into another language or format. © 1990, 1992 by Knowledge Based Systems, Inc. One KBSI Place 1408 University Drive East College Station, Texas 77840-2335 (409) 696-7979 Table of Contents List of Figures .......................................................................................................................... v Foreword.................................................................................................................................. ix 1.0 Introduction.................................................................................................................... 3 2.0 IDEF1 Concepts ............................................................................................................. 7 2.1 Introduction........................................................................................................
    [Show full text]
  • Section 7.0 Data Collection for IDEF Modeling
    1 Section 6.0 Author’s Guide to Creating IDEF1 Diagrams 1:M Relation ATTRIBUTE CLASS M:N Relation 1:1 Relation ENTITY CLASS M:1 Relation 2 3 6.0 Author’s Guide To Creating IDEF1 Diagrams 6.1 Phase Zero - Context Definition The IDEF1 information model must somehow be described and defined in terms of both its limitations and its ambitions. The modeler is one of the primary influences in the development of the scope of the model. Together, the modeler and the project manager unfold the plan for reaching the objectives of Phase Zero. These objectives include: 1. Project definition – a general statement of “what” has to be done, “why” and “how” it will get done. 2. Source material – a plan for the physical compilation of source material, including the indexing and filing of it. 3. Author conventions – a fundamental declaration of the conventions (optional methods) by which the author chooses to make and manage the model. The products of these objectives, coupled with other descriptive and explanatory documents and information, become the products of the Phase Zero effort–the Phase Zero Kits. The purpose of these kits will be described more fully later in this section. 6.2 Project Definition 6.2.1 The Strategic Objective The first activity in the modeling project is to establish where the project is going, how, and, to some extent, why. In this process, the project manager will establish his authority and mandate for the project. Some rough guidelines establishing the scope of the project in terms of money, time, and breadth of effort will have been laid down, usually in a project manager’s authorizing documents.
    [Show full text]