Get Topological UML Modeling. An Improved Approach for Domain Modeling and Software Development. A volume in Computer Science Reviews and Trends 1st Edition Edition Janis Osis And Uldis Donins (Auth.) - eBook PDF free all chapters
Get Topological UML Modeling. An Improved Approach for Domain Modeling and Software Development. A volume in Computer Science Reviews and Trends 1st Edition Edition Janis Osis And Uldis Donins (Auth.) - eBook PDF free all chapters
com
https://ebooksecure.com/product/ebook-pdf-introduction-to-management-
science-a-modeling-and-case-studies-approach-with-spreadsheets-6th-
edition/
ebooksecure.com
ebooksecure.com
ebooksecure.com
https://ebooksecure.com/product/ebook-pdf-an-introduction-to-
community-health-brief-edition-brief-edition/
ebooksecure.com
(eBook PDF) Ten Lessons in Introductory Sociology 2nd
Edition
https://ebooksecure.com/product/ebook-pdf-ten-lessons-in-introductory-
sociology-2nd-edition/
ebooksecure.com
https://ebooksecure.com/product/ebook-pdf-organisational-behaviour-
core-concepts-applications-4th/
ebooksecure.com
https://ebooksecure.com/product/ebook-pdf-abrams-clinical-drug-
therapy-rationales-for-nursing-practice-11th-edition/
ebooksecure.com
https://ebooksecure.com/product/ebook-pdf-international-business-by-
michael-geringer/
ebooksecure.com
https://ebooksecure.com/product/original-pdf-business-communication-
in-person-in-print-online-10th-edition/
ebooksecure.com
Goldman-Cecil Medicine 26th Edition Lee Goldman - eBook
PDF
https://ebooksecure.com/download/goldman-cecil-medicine-ebook-pdf/
ebooksecure.com
Topological UML Modeling
Topological UML Modeling
An Improved Approach for Domain
Modeling and Software Development
Janis Osis
Uldis Donins
Elsevier
Radarweg 29, PO Box 211, 1000 AE Amsterdam, Netherlands
The Boulevard, Langford Lane, Kidlington, Oxford OX5 1GB, United Kingdom
50 Hampshire Street, 5th Floor, Cambridge, MA 02139, United States
Copyright r 2017 Elsevier Inc. All rights reserved.
No part of this publication may be reproduced or transmitted in any form or by any means, electronic or
mechanical, including photocopying, recording, or any information storage and retrieval system, without
permission in writing from the publisher. Details on how to seek permission, further information about the
Publisher’s permissions policies and our arrangements with organizations such as the Copyright Clearance
Center and the Copyright Licensing Agency, can be found at our website: www.elsevier.com/permissions.
This book and the individual contributions contained in it are protected under copyright by the Publisher
(other than as may be noted herein).
Designations used by companies to distinguish their products are often claimed as trademarks or registered
trademarks. In all instances in which Elsevier/Morgan Kaufmann Publishers is aware of a claim, the product
names appear in initial capital or all capital letters. Readers, however, should contact the appropriate
companies for more complete information regarding trademarks and registration.
The following are trademarks of the Object Management Group, Inc., in the United States and/or other
countries: CWM, MDA, MOF, OCL, OMG, UML, XMI.
Notices
Knowledge and best practice in this field are constantly changing. As new research and experience broaden
our understanding, changes in research methods, professional practices, or medical treatment may become necessary.
Practitioners and researchers must always rely on their own experience and knowledge in evaluating and using
any information, methods, compounds, or experiments described herein. In using such information or methods
they should be mindful of their own safety and the safety of others, including parties for whom they have a
professional responsibility.
To the fullest extent of the law, neither the Publisher nor the authors, contributors, or editors, assume any
liability for any injury and/or damage to persons or property as a matter of products liability, negligence or
otherwise, or from any use or operation of any methods, products, instructions, or ideas contained in the
material herein.
British Library Cataloguing-in-Publication Data
A catalogue record for this book is available from the British Library
Library of Congress Cataloging-in-Publication Data
A catalog record for this book is available from the Library of Congress
ISBN: 978-0-12-805476-5
Unfortunately, the hue and cry that resulted from this simple and
abundantly useful catalog was a huge surprise to Dr. Hutt, myself, and
all of the OMG members and staff who participated in the production
of the catalog. We were told that standardization would result in the
freezing of forward momentum in software development methodology.
Research remained fluid, we heard, and the researchers didn’t want to
see development stop in the face of new discoveries.
And, in fact, not just in the software industry—UML has been used
in many other ways, as a way to express business processes, systems
architectures, even electronic circuits. The success of a product (or in
this case a standard) perhaps can be best measured as how broadly it
is used both inside and outside of its intended purpose. UML has also
spawned numerous related languages: the Meta-Object Facility (MOF)
that underlies the UML is now the underpinnings also of other lan-
guages (like the Business Processing Model & Notation (BPMN) and
others); the executable Functional UML (fUML), sufficiently precise
to be directly executed like a programming language itself; UML has
also been extended to explicitly support other modeling regimes like
Systems Engineering (with the Systems Modeling Language, SysML)
and work as of this writing is focusing on product architectures, busi-
ness architectures, and others. UML (and MOF) in 2000 also became
the major underpinning of the Model Driven Architecture (MDA), a
model-based way to develop software, just as modeling and simulation
underlie other engineering disciplines. Itself already approaching
20 years of age, the MDA is becoming a way to express semantics, and
the UML is the key technology that makes that possible.
One weak spot for UML and MDA has always been the
computation-independent model (CIM) layer that captures the design of
a software engineering artifact without regard to how it is implemen-
ted. The CIM is then translated into a platform-independent model and
thus to a platform-specific model which generally means some coding
language, although it might be more complicated than that. Many
methodologies have been developed over the past 20 years for CIM’s
that are sufficiently abstract to express design without regard to plat-
form, but sufficiently precise to specify exactly one process. Solving
Foreword xiii
UML is a notation and as such its specification does not contain any
guidelines of software development process. This chapter discusses the
current state of the art of UML-based software development approaches.
Most attention is paid on the artifacts created by using the UML.
Chapter 3. Adjusting Unified Modeling Language
1.1 INTRODUCTION
Unified Modeling Language—abbreviated as UML—is a graphical
language officially defined by Object Management Group (OMG) for
visualizing, specifying, constructing, and documenting the artifacts of a
software system [106]. An artifact in software development is an item
created or collected during the development process (example of arti-
facts includes use cases, requirements, design, code, executable files,
etc.). UML offers a standard way to write system’s blueprints, includ-
ing conceptual things such as business processes and system functions
as well as concrete things such as programming language statements,
database schemas, and reusable software components [37]. Despite that
UML is designed for specifying, visualizing, constructing, and document-
ing software systems, it is not restricted only for software modeling. UML
has been used for modeling hardware, and is used for business process
modeling, systems engineering modeling and representing organizational
structure, among many other domains [125].