Author
Michael R. Blaha
Bio: Michael R. Blaha is an academic researcher from General Electric. The author has contributed to research in topics: Relational database & Object-modeling technique. The author has an hindex of 13, co-authored 16 publications receiving 9204 citations.
Papers
More filters
Book•
01 Jan 1990TL;DR: This book discusses Object Modeling as a Design Technique, Object Diagram Compiler, and the Future of Object-Oriented Technology.
Abstract: 1. Introduction. I. MODELING CONCEPTS. 2. Modeling as a Design Technique. 3. Object Modeling. 4. Advanced Object Modeling. 5. Dynamic Modeling. 6. Functional Modeling. II. DESIGN METHODOLOGY. 7. Methodology Preview. 8. Analysis. 9. System Design. 10. Object Design. 11. Methodology Summary. 12. Comparison of Methodologies. III. IMPLEMENTATION. 13. From Design to Implementation. 14. Programming Style. 15. Object-Oriented Languages. 16. Non-Object-Oriented Languages. 17. Databases. 18. Object Diagram Compiler. 19. Computer Animation. 20. Electrical Distribution Design System. 21. Future of Object-Oriented Technology. Appendix A: OMT Graphical Notation. Appendix B: Glossary. Index.
5,408 citations
01 Jan 1991
TL;DR: The OMT Graphical Notation (OMT) as mentioned in this paper is a graphical notation for object-oriented languages that is based on the OMT graph diagram language (OMT).
Abstract: 1. Introduction. I. MODELING CONCEPTS. 2. Modeling as a Design Technique. 3. Object Modeling. 4. Advanced Object Modeling. 5. Dynamic Modeling. 6. Functional Modeling. II. DESIGN METHODOLOGY. 7. Methodology Preview. 8. Analysis. 9. System Design. 10. Object Design. 11. Methodology Summary. 12. Comparison of Methodologies. III. IMPLEMENTATION. 13. From Design to Implementation. 14. Programming Style. 15. Object-Oriented Languages. 16. Non-Object-Oriented Languages. 17. Databases. 18. Object Diagram Compiler. 19. Computer Animation. 20. Electrical Distribution Design System. 21. Future of Object-Oriented Technology. Appendix A: OMT Graphical Notation. Appendix B: Glossary. Index.
2,411 citations
Book•
27 Jul 1997TL;DR: The modeler’s guide to designing and implementation of Relational Databases: Advanced, a meta-modelling and design process for large system problems.
Abstract: 1. Introduction. I. MODELING CONCEPTS. 2. Basic Object Modeling. 3. Advanced Object Modeling. 4. Object Metamodeling. 5. Functional Modeling. II. ANALYSIS AND DESIGN PROCESS. 6. Process Preview. 7. Conceptualization. 8. Analysis. 9. System Design. 10. Detailed Design. 11. Process Review. III. IMPLEMENTATION. 12. Files. 13. Relational Databases: Basics. 14. Relational Databases: Advanced. 15. Object-Oriented Databases: Basics. 16. Object-Oriented Databases: Advanced. 17. Implementation Review. IV. LARGE SYSTEM ISSUES. 18. Distributed Databases. 19. Integration of Applications. 20. Reverse Engineering. Appendix A. Glossary. Appendix B. BNF Grammar for the ONN. Index.
251 citations
TL;DR: This paper proposes a process for reverse engineering of relational databases using object-oriented models because the same modeling paradigm is adept at representing abstract conceptual models and models with implementation decisions.
Abstract: A process for reverse engineering of relational databases is proposed. Object-oriented models provide a natural language for facilitating the re-engineering process. An object-oriented model can describe the existing software, the reverse-engineered semantic intent, and the forward-engineered new system. The Object Modeling Technique (OMT) notation for modeling data is adopted. Graphical OMT models are intuitive and provide a rigorous basis for specifying software. A more robust process than advanced in the literature is proposed. Guidelines for coping with design optimizations and unfortunate implementation decisions are provided. The process emphasizes analysis of candidate keys rather than primary keys. Three sources for information are incorporated: schema, observed patterns of data, and the semantic understanding of application intent. >
212 citations
Book•
01 Jan 1991
TL;DR: This chapter discusses UML Graphical Notation, the building blocks of a modeler’s toolkit, and some of the strategies used to design and implement models.
Abstract: Chapter 1 Introduction Chapter 2 Modeling as a Design Technique Chapter 3 Class Modeling Chapter 4 Advanced Class Modeling Chapter 5 State Modeling Chapter 6 Advanced State Modeling Chapter 7 Interaction Modeling Chapter 8 Advanced Interaction Modeling Chapter 9 Concepts Summary Chapter 10 Process Overview Chapter 11 System Conception Chapter 12 Domain Analysis Chapter 13 Application Analysis Chapter 14 System Design Chapter 15 Class Design Chapter 16 Process Summary Chapter 17 Implementation Modeling Chapter 18 OO Languages Chapter 19 Databases Chapter 20 Programming Style Chapter 21 Iterative Development Chapter 22 Managing Models Chapter 23 Legacy Systems Appendix A: UML Graphical Notation Appendix B: Glossary Answers to Selected Exercises
200 citations
Cited by
More filters
Book•
01 Jan 1994TL;DR: The book is an introduction to the idea of design patterns in software engineering, and a catalog of twenty-three common patterns, which most experienced OOP designers will find out they've known about patterns all along.
Abstract: The book is an introduction to the idea of design patterns in software engineering, and a catalog of twenty-three common patterns. The nice thing is, most experienced OOP designers will find out they've known about patterns all along. It's just that they've never considered them as such, or tried to centralize the idea behind a given pattern so that it will be easily reusable.
22,762 citations
University of Genoa1, University of Manchester2, KEK3, CERN4, Imperial College London5, Stanford University6, Tata Institute of Fundamental Research7, Istituto Nazionale di Fisica Nucleare8, University of Pittsburgh9, Lyon College10, TRIUMF11, Northeastern University12, Thomas Jefferson National Accelerator Facility13, University of Córdoba (Spain)14, Goethe University Frankfurt15, University of Southampton16, University of Udine17, University of Alberta18, Tokyo Metropolitan University19, Helsinki Institute of Physics20, National Research Nuclear University MEPhI21, University of Bath22, Niigata University23, Naruto University of Education24, Kobe University25, University of Calabria26, University of Trieste27, European Space Agency28, University of Birmingham29, Ritsumeikan University30, Qinetiq31, École Polytechnique Fédérale de Lausanne32, Massachusetts Institute of Technology33, Brookhaven National Laboratory34
01 Jul 2003-Nuclear Instruments & Methods in Physics Research Section A-accelerators Spectrometers Detectors and Associated Equipment
TL;DR: The Gelfant 4 toolkit as discussed by the authors is a toolkit for simulating the passage of particles through matter, including a complete range of functionality including tracking, geometry, physics models and hits.
Abstract: G eant 4 is a toolkit for simulating the passage of particles through matter. It includes a complete range of functionality including tracking, geometry, physics models and hits. The physics processes offered cover a comprehensive range, including electromagnetic, hadronic and optical processes, a large set of long-lived particles, materials and elements, over a wide energy range starting, in some cases, from 250 eV and extending in others to the TeV energy range. It has been designed and constructed to expose the physics models utilised, to handle complex geometries, and to enable its easy adaptation for optimal use in different sets of applications. The toolkit is the result of a worldwide collaboration of physicists and software engineers. It has been created exploiting software engineering and object-oriented technology and implemented in the C++ programming language. It has been used in applications in particle physics, nuclear physics, accelerator design, space engineering and medical physics.
18,904 citations
Book•
01 Jan 1999
TL;DR: In The Unified Modeling Language User Guide, the original developers of the UML provide a tutorial to the core aspects of the language in a two-color format designed to facilitate learning.
Abstract: In The Unified Modeling Language User Guide, the original developers of the UML--Grady Booch, James Rumbaugh, and Ivar Jacobson--provide a tutorial to the core aspects of the language in a two-color format designed to facilitate learning. Starting with a conceptual model of the UML, the book progressively applies the UML to a series of increasingly complex modeling problems across a variety of application domains. This example-driven approach helps readers quickly understand and apply the UML. For more advanced developers, the book includes a learning track focused on applying the UML to advanced modeling problems.With The Unified Modeling Language User Guide, readers will:Understand what the UML is, what it is not, and why it is relevant to the development of software-intensive systemsMaster the vocabulary, rules, and idioms of the UML in order to "speak" the language effectivelyLearn how to apply the UML to a number of common modeling problemsSee illustrations of the UML's use interspersed with use cases for specific UML features, andGain insight into the UML from the original creators of the UML.
6,634 citations
Journal Article•
6,559 citations
01 Jan 2002
TL;DR: An ontology defines a common vocabulary for researchers who need to share information in a domain that includes machine-interpretable definitions of basic concepts in the domain and relations among them.
Abstract: 1 Why develop an ontology? In recent years the development of ontologies—explicit formal specifications of the terms in the domain and relations among them (Gruber 1993)—has been moving from the realm of ArtificialIntelligence laboratories to the desktops of domain experts. Ontologies have become common on the World-Wide Web. The ontologies on the Web range from large taxonomies categorizing Web sites (such as on Yahoo!) to categorizations of products for sale and their features (such as on Amazon.com). The WWW Consortium (W3C) is developing the Resource Description Framework (Brickley and Guha 1999), a language for encoding knowledge on Web pages to make it understandable to electronic agents searching for information. The Defense Advanced Research Projects Agency (DARPA), in conjunction with the W3C, is developing DARPA Agent Markup Language (DAML) by extending RDF with more expressive constructs aimed at facilitating agent interaction on the Web (Hendler and McGuinness 2000). Many disciplines now develop standardized ontologies that domain experts can use to share and annotate information in their fields. Medicine, for example, has produced large, standardized, structured vocabularies such as SNOMED (Price and Spackman 2000) and the semantic network of the Unified Medical Language System (Humphreys and Lindberg 1993). Broad general-purpose ontologies are emerging as well. For example, the United Nations Development Program and Dun & Bradstreet combined their efforts to develop the UNSPSC ontology which provides terminology for products and services (www.unspsc.org). An ontology defines a common vocabulary for researchers who need to share information in a domain. It includes machine-interpretable definitions of basic concepts in the domain and relations among them. Why would someone want to develop an ontology? Some of the reasons are:
4,838 citations