DOCSLIB.ORG

Case Management Model and Notation

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Case Management Model and Notation Date: May 2014 Case Management Model and Notation Version 1.0 OMG Document Number: formal/2014-05-05 Standard document URL: http://www.omg.org/spec/CMMN/1.0/ Machine Consumable Files: Normative: http://www.omg.org/spec/CMMN/20131201/CMMN10.xmi http://www.omg.org/spec/CMMN/20131201/CMMN10.xsd http://www.omg.org/spec/CMMN/20131201/CMMN10CaseModel.xsd Copyright © 2011, Agile Enterprise Design, LLC Copyright © 2011, BizAgi Limited Copyright © 2011, Cordys Nederland BV Copyright © 2011, International Business Machines Corporation Copyright © 2011, Kofax plc Copyright © 2014, Object Management Group, Inc. Copyright © 2011, Oracle Incorporated Copyright © 2011, SAP AG Copyright © 2011, Stiftelsen SINTEF Copyright © 2011, TIBCO Copyright © 2011, Trisotech USE OF SPECIFICATION - TERMS, CONDITIONS & NOTICES The material in this document details an Object Management Group specification in accordance with the terms, conditions and notices set forth below. This document does not represent a commitment to implement any portion of this specification in any company's products. The information contained in this document is subject to change without notice. LICENSES The companies listed above have granted to the Object Management Group, Inc. (OMG) a nonexclusive, royalty-free, paid up, worldwide license to copy and distribute this document and to modify this document and distribute copies of the modified version. Each of the copyright holders listed above has agreed that no person shall be deemed to have infringed the copyright in the included material of any such copyright holder by reason of having used the specification set forth herein or having conformed any computer software to the specification. Subject to all of the terms and conditions below, the owners of the copyright in this specification hereby grant you a fully-paid up, non-exclusive, nontransferable, perpetual, worldwide license (without the right to sublicense), to use this specification to create and distribute software and special purpose specifications that are based upon this specification, and to use, copy, and distribute this specification as provided under the Copyright Act; provided that: (1) both the copyright notice identified above and this permission notice appear on any copies of this specification; (2) the use of the specifications is for informational purposes and will not be copied or posted on any network computer or broadcast in any media and will not be otherwise resold or transferred for commercial purposes; and (3) no modifications are made to this specification. This limited permission automatically terminates without notice if you breach any of these terms or conditions. Upon termination, you will destroy immediately any copies of the specifications in your possession or control. PATENTS The attention of adopters is directed to the possibility that compliance with or adoption of OMG specifications may require use of an invention covered by patent rights. OMG shall not be responsible for identifying patents for which a license may be required by any OMG specification, or for conducting legal inquiries into the legal validity or scope of those patents that are brought to its attention. OMG specifications are prospective and advisory only. Prospective users are responsible for protecting themselves against liability for infringement of patents. GENERAL USE RESTRICTIONS Any unauthorized use of this specification may violate copyright laws, trademark laws, and communications regulations and statutes. This document contains information which is protected by copyright. All Rights Reserved. No part of this work covered by copyright herein may be reproduced or used in any form or by any means--graphic, electronic, or mechanical, including photocopying, recording, taping, or information storage and retrieval systems--without permission of the copyright owner. DISCLAIMER OF WARRANTY WHILE THIS PUBLICATION IS BELIEVED TO BE ACCURATE, IT IS PROVIDED "AS IS" AND MAY CONTAIN ERRORS OR MISPRINTS. THE OBJECT MANAGEMENT GROUP AND THE COMPANIES LISTED ABOVE MAKE NO WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, WITH REGARD TO THIS PUBLICATION, INCLUDING BUT NOT LIMITED TO ANY WARRANTY OF TITLE OR OWNERSHIP, IMPLIED WARRANTY OF MERCHANTABILITY OR WARRANTY OF FITNESS FOR A PARTICULAR PURPOSE OR USE. IN NO EVENT SHALL THE OBJECT MANAGEMENT GROUP OR ANY OF THE COMPANIES LISTED ABOVE BE LIABLE FOR ERRORS CONTAINED HEREIN OR FOR DIRECT, INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL, RELIANCE OR COVER DAMAGES, INCLUDING LOSS OF PROFITS, REVENUE, DATA OR USE, INCURRED BY ANY USER OR ANY THIRD PARTY IN CONNECTION WITH THE FURNISHING, PERFORMANCE, OR USE OF THIS MATERIAL, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. The entire risk as to the quality and performance of software developed using this specification is borne by you. This disclaimer of warranty constitutes an essential part of the license granted to you to use this specification. RESTRICTED RIGHTS LEGEND Use, duplication or disclosure by the U.S. Government is subject to the restrictions set forth in subparagraph (c) (1) (ii) of The Rights in Technical Data and Computer Software Clause at DFARS 252.227-7013 or in subparagraph (c)(1) and (2) of the Commercial Computer Software - Restricted Rights clauses at 48 C.F.R. 52.227-19 or as specified in 48 C.F.R. 227-7202-2 of the DoD F.A.R. Supplement and its successors, or as specified in 48 C.F.R. 12.212 of the Federal Acquisition Regulations and its successors, as applicable. The specification copyright owners are as indicated above and may be contacted through the Object Management Group, 109 Highland Avenue, Needham, MA 02494, U.S.A. TRADEMARKS IMM®, MDA®, Model Driven Architecture®, UML®, UML Cube logo®, OMG Logo®, CORBA® and XMI® are registered trademarks of the Object Management Group, Inc., and Object Management Group™, OMG™ , Unified Modeling Language™, Model Driven Architecture Logo™, Model Driven Architecture Diagram™, CORBA logos™, XMI Logo™, CWM™, CWM Logo™, IIOP™ , MOF™ , OMG Interface Definition Language (IDL)™ , and OMG Systems Modeling Language (OMG SysML)™ are trademarks of the Object Management Group. All other products or company names mentioned are used for identification purposes only, and may be trademarks of their respective owners. COMPLIANCE The copyright holders listed above acknowledge that the Object Management Group (acting itself or through its designees) is and shall at all times be the sole entity that may authorize developers, suppliers and sellers of computer software to use certification marks, trademarks or other special designations to indicate compliance with these materials. Software developed under the terms of this license may claim compliance or conformance with this specification if and only if the software compliance is of a nature fully matching the applicable compliance points as stated in the specification. Software developed only partially matching the applicable compliance points may claim only that the software was based on this speci- fication, but may not claim compliance or conformance with this specification. In the event that testing suites are implemented or approved by Object Management Group, Inc., software developed using this specification may claim compliance or confor- mance with the specification only if the software satisfactorily completes the testing suites. OMG’s Issue Reporting Procedure All OMG specifications are subject to continuous review and improvement. As part of this process we encourage readers to report any ambiguities, inconsistencies, or inaccuracies they may find by completing the Issue Reporting Form listed on the main web page http://www.omg.org, under Documents, Report a Bug/ Issue (http://www.omg.org/report_issue.htm). Table of Contents Preface ....................................................................................................ix 1 Scope .......................................................................................................... 1 2 Conformance ............................................................................................... 1 2.1 General ..........................................................................................................1 2.2 Visual Notation Conformance ........................................................................2 2.3 Case Modeling Conformance ........................................................................3 2.4 BPMN Compatibility Conformance ................................................................3 2.5 CMMN Complete Conformance ....................................................................4 3 References .................................................................................................. 4 3.1 Normative References ...................................................................................4 3.2 Non-normative References ............................................................................4 4 Additional Information .................................................................................. 5 4.1 General Concept ...........................................................................................5 4.2 Target Users ..................................................................................................6 4.3 Interoperability ...............................................................................................6 4.4 Submitting and Supporting Organizations .....................................................6 4.5 IPR and Patents ............................................................................................7
Load more

Recommended publications
  • Artificial Intelligence in Health Care: the Hope, the Hype, the Promise, the Peril
    Artificial Intelligence in Health Care: The Hope, the Hype, the Promise, the Peril Michael Matheny, Sonoo Thadaney Israni, Mahnoor Ahmed, and Danielle Whicher, Editors WASHINGTON, DC NAM.EDU PREPUBLICATION COPY - Uncorrected Proofs NATIONAL ACADEMY OF MEDICINE • 500 Fifth Street, NW • WASHINGTON, DC 20001 NOTICE: This publication has undergone peer review according to procedures established by the National Academy of Medicine (NAM). Publication by the NAM worthy of public attention, but does not constitute endorsement of conclusions and recommendationssignifies that it is the by productthe NAM. of The a carefully views presented considered in processthis publication and is a contributionare those of individual contributors and do not represent formal consensus positions of the authors’ organizations; the NAM; or the National Academies of Sciences, Engineering, and Medicine. Library of Congress Cataloging-in-Publication Data to Come Copyright 2019 by the National Academy of Sciences. All rights reserved. Printed in the United States of America. Suggested citation: Matheny, M., S. Thadaney Israni, M. Ahmed, and D. Whicher, Editors. 2019. Artificial Intelligence in Health Care: The Hope, the Hype, the Promise, the Peril. NAM Special Publication. Washington, DC: National Academy of Medicine. PREPUBLICATION COPY - Uncorrected Proofs “Knowing is not enough; we must apply. Willing is not enough; we must do.” --GOETHE PREPUBLICATION COPY - Uncorrected Proofs ABOUT THE NATIONAL ACADEMY OF MEDICINE The National Academy of Medicine is one of three Academies constituting the Nation- al Academies of Sciences, Engineering, and Medicine (the National Academies). The Na- tional Academies provide independent, objective analysis and advice to the nation and conduct other activities to solve complex problems and inform public policy decisions.
    [Show full text]
  • The Ingham County News Oh! ~.No ••••• Published THURSDAY AFTERNOONS Rev
    ·stranger Rules Mason While Mayor Fishes Thein m Whllt! M11yor CuriiH Mur•fon of qroc·r!r' nnrl mmnhm· 11f I he C!lly IlnrriHorr \VflH htrsy runnlnr: f!ity r·mrneil. llnrpcr Is jii'I!Sii!ent of the 4 Sections - 20 P4gos uf'f:ilm In Mason Monday, Mnsun's 'lanlsun Eciwol honrd. Mnynr Pnul ftlchlll'ris und Pollen 'l'ha vlr;!Jurs ,were met nt the Chief IInrry Chundler wenl fish· north dly limits nnrl Cicicnrtcd to Copy Mus# Come. Ill!~· 'own hy Cuptnln Tim Stol?. and Mayor Murlon nnrl Mnynr Welt· '::ounellman Nels Ji'nrrlby, of'flclul A· Day Earlier onls r.xdrungPd jnlm Monduy 011 Mn,~nn hosl. After· a ~>lop al city Hospital Pledges 1\ltmtorhll ilay Uri~ year• fllll!i mnyor· cxchungc day, a Jlart of hnll the group nltcnclctl 11 lunch· Mlehlgan weelt. on puhllmUon duy for f.lw lllJI'· con at Mrtson golf cour~e. After hum County New~. 1'1mt nwunH l11nch Counellman F'orrll>y pre­ Evnrymw In 1\ln~;nn Is In· tho lliiJler will lmve lo go to M:ntcrl Mayor· Mut·ton with u gnld Vlfllli ~~~ Nf.op ovm• In JlnrTINon pm~li Wedncr>duy noon lnstmul lwy In Mason, and v!Hitlng women of 'l'IIIII"IHiuy, .Pass $300~000 · In Urelr· h·nvi!IH' llu·nuJ:·h Uw wil h flowers, nnr·t.h nne! Hit 11 whlh!, 'l'hnt'.~ Cot'I'L'IIIIonctnnl!! 111111 IUivm·· Worlwrs in the $500,000 Mason lhnt nil of the eampalgn lltcrn· tho lnrltatlon extmulml hy '!'hn rr•st of llw afl['rnoon May· tlserH rnuHt hlt\'e Uwlr ltmnH hospital cum p nl g n cheered or Murl on's party look a r:rand lure nnrl puhlldty has clearly !Udym· Mnrion dur·ln~; his und co11Y In th(! otfh!e 11 ctuy Wedncs·day night when the score· sllrled fmm the beginning that vl~lt her·e.
    [Show full text]
  • Using the UML for Architectural Description?
    Using the UML for Architectural Description? Rich Hilliard Integrated Systems and Internet Solutions, Inc. Concord, MA USA [email protected] Abstract. There is much interest in using the Unified Modeling Lan- guage (UML) for architectural description { those techniques by which architects sketch, capture, model, document and analyze architectural knowledge and decisions about software-intensive systems. IEEE P1471, the Recommended Practice for Architectural Description, represents an emerging consensus for specifying the content of an architectural descrip- tion for a software-intensive system. Like the UML, IEEE P1471 does not prescribe a particular architectural method or life cycle, but may be used within a variety of such processes. In this paper, I provide an overview of IEEE P1471, describe its conceptual framework, and investigate the issues of applying the UML to meet the requirements of IEEE P1471. Keywords: IEEE P1471, architectural description, multiple views, view- points, Unified Modeling Language 1 Introduction The Unified Modeling Language (UML) is rapidly maturing into the de facto standard for modeling of software-intensive systems. Standardized by the Object Management Group (OMG) in November 1997, it is being adopted by many organizations, and being supported by numerous tool vendors. At present, there is much interest in using the UML for architectural descrip- tion: the techniques by which architects sketch, capture, model, document and analyze architectural knowledge and decisions about software-intensive systems. Such techniques enable architects to record what they are doing, modify or ma- nipulate candidate architectures, reuse portions of existing architectures, and communicate architectural information to others. These descriptions may the be used to analyze and reason about the architecture { possibly with automated support.
    [Show full text]
  • OMG Systems Modeling Language (OMG Sysml™) Tutorial 25 June 2007
    OMG Systems Modeling Language (OMG SysML™) Tutorial 25 June 2007 Sanford Friedenthal Alan Moore Rick Steiner (emails included in references at end) Copyright © 2006, 2007 by Object Management Group. Published and used by INCOSE and affiliated societies with permission. Status • Specification status – Adopted by OMG in May ’06 – Finalization Task Force Report in March ’07 – Available Specification v1.0 expected June ‘07 – Revision task force chartered for SysML v1.1 in March ‘07 • This tutorial is based on the OMG SysML adopted specification (ad-06-03-01) and changes proposed by the Finalization Task Force (ptc/07-03-03) • This tutorial, the specifications, papers, and vendor info can be found on the OMG SysML Website at http://www.omgsysml.org/ 7/26/2007 Copyright © 2006,2007 by Object Management Group. 2 Objectives & Intended Audience At the end of this tutorial, you should have an awareness of: • Benefits of model driven approaches for systems engineering • SysML diagrams and language concepts • How to apply SysML as part of a model based SE process • Basic considerations for transitioning to SysML This course is not intended to make you a systems modeler! You must use the language. Intended Audience: • Practicing Systems Engineers interested in system modeling • Software Engineers who want to better understand how to integrate software and system models • Familiarity with UML is not required, but it helps 7/26/2007 Copyright © 2006,2007 by Object Management Group. 3 Topics • Motivation & Background • Diagram Overview and Language Concepts • SysML Modeling as Part of SE Process – Structured Analysis – Distiller Example – OOSEM – Enhanced Security System Example • SysML in a Standards Framework • Transitioning to SysML • Summary 7/26/2007 Copyright © 2006,2007 by Object Management Group.
    [Show full text]
  • Pivotpoint-Sparx Partnership Promotes Model-Based Systems
    PivotPoint-Sparx Partnership Promotes Model-Based Systems Engineering with SysML PivotPoint Technology and Sparx Systems today announced a technology partnership that will combine their complementary strengths in SysML training and tools for systems engineers. PivotPoint announced that its “SysML Distilled™ with Enterprise Architect™” workshop is immediately available, and will use Sparx’s new MDG Technology for SysML™ product. Fallbrook, California (PRWEB) - October 9, 2006 -- PivotPoint Technology and Sparx Systems today announced a technology partnership to promote model-based systems engineering with the Systems Modeling Language (SysML). SysML is the new domain-specific modeling language for systems engineering applications that was adopted by the Object Management Group as OMG SysML™ in July 2006, and is attracting users among systems engineers worldwide. Under the agreement, PivotPoint will be Sparx’s primary partner for training and consulting services that use Sparx’s new SysML product (MDG Technology for SysML™), which was released last week. PivotPoint showed its readiness to partner by announcing the immediate availability of a new “SysML Distilled™ with Enterprise Architect™” workshop, which combines both SysML language and tool training. SysML extends the Unified Modeling Language (UML), the industry standard for specifying software-intensive systems, so that it can also specify hardware, processes, personnel, and facilities. Systems engineers who want to follow a model-based systems engineering process gain at least two important advantages in using SysML. First, SysML is a smaller language than UML 2.0 since it has fewer diagrams and constructs, so it is easier for engineers to learn and apply. Second, SysML adds to the semantic expressiveness of UML with two new diagrams for defining requirements and parametric constraints, which systems engineers need to fully specify complex systems.
    [Show full text]
  • 03-01-06 BPDM RFP.Pdf
    Business Process Definition Metamodel RFP Object Management Group First Needham Place 250 First Avenue, Suite 100 Needham, MA 02494 Telephone: +1-781-444-0404 Facsimile: +1-781-444-0320 Business Process Definition Metamodel Request For Proposal OMG Document: bei/2003-01-06 Letters of Intent due: June 16, 2003 Submissions due: August 18, 2003 Objective of this RFP This Request For Proposals solicits submissions that specify a business process definition metamodel, which is platform independent with respect to specific business process definition languages. This metamodel will define an abstract language for specification of executable business processes that execute within an enterprise (with or without human involvement); and may collaborate between otherwise- independent business processes executing in different business units or enterprises. The specification developed in response to this RFP is expected to achieve the following: • A common metamodel to unify the diverse business process definition graphical and textual notations that exist in the industry • A metamodel that complements existing UML metamodels so that business processes specifications can be part of complete system specifications to assure consistency and completeness bei/2003-01-06, January 31, 2003 1 Business Process Definition Metamodel RFP • The ability to integrate process models for workflow management processes, automated business processes, and collaborations between business units. • Support for the specification of choreography, describing the collaboration
    [Show full text]
  • Sysml, the Language of MBSE Paul White
    Welcome to SysML, the Language of MBSE Paul White October 8, 2019 Brief Introduction About Myself • Work Experience • 2015 – Present: KIHOMAC / BAE – Layton, Utah • 2011 – 2015: Astronautics Corporation of America – Milwaukee, Wisconsin • 2001 – 2011: L-3 Communications – Greenville, Texas • 2000 – 2001: Hynix – Eugene, Oregon • 1999 – 2000: Raytheon – Greenville, Texas • Education • 2019: OMG OCSMP Model Builder—Fundamental Certification • 2011: Graduate Certification in Systems Engineering and Architecting – Stevens Institute of Technology • 1999 – 2004: M.S. Computer Science – Texas A&M University at Commerce • 1993 – 1998: B.S. Computer Science – Texas A&M University • INCOSE • Chapters: Wasatch (2015 – Present), Chicagoland (2011 – 2015), North Texas (2007 – 2011) • Conferences: WSRC (2018), GLRCs (2012-2017) • CSEP: (2017 – Present) • 2019 INCOSE Outstanding Service Award • 2019 INCOSE Wasatch -- Most Improved Chapter Award & Gold Circle Award • Utah Engineers Council (UEC) • 2019 & 2018 Engineer of the Year (INCOSE) for Utah Engineers Council (UEC) • Vice Chair • Family • Married 14 years • Three daughters (1, 12, & 10) 2 Introduction 3 Our Topics • Definitions and Expectations • SysML Overview • Basic Features of SysML • Modeling Tools and Techniques • Next Steps 4 What is Model-based Systems Engineering (MBSE)? Model-based systems engineering (MBSE) is “the formalized application of modeling to support system requirements, design, analysis, verification and validation activities beginning in the conceptual design phase and continuing throughout development and later life cycle phases.” -- INCOSE SE Vision 2020 5 What is Model-based Systems Engineering (MBSE)? “Formal systems modeling is standard practice for specifying, analyzing, designing, and verifying systems, and is fully integrated with other engineering models. System models are adapted to the application domain, and include a broad spectrum of models for representing all aspects of systems.
    [Show full text]
  • Unifying Modeling and Programming with ALF
    SOFTENG 2016 : The Second International Conference on Advances and Trends in Software Engineering Unifying Modeling and Programming with ALF Thomas Buchmann and Alexander Rimer University of Bayreuth Chair of Applied Computer Science I Bayreuth, Germany email: fthomas.buchmann, [email protected] Abstract—Model-driven software engineering has become more The Eclipse Modeling Framework (EMF) [5] has been and more popular during the last decade. While modeling the established as an extensible platform for the development of static structure of a software system is almost state-of-the art MDSE applications. It is based on the Ecore meta-model, nowadays, programming is still required to supply behavior, i.e., which is compatible with the Object Management Group method bodies. Unified Modeling Language (UML) class dia- (OMG) Meta Object Facility (MOF) specification [6]. Ideally, grams constitute the standard in structural modeling. Behavioral software engineers operate only on the level of models such modeling, on the other hand, may be achieved graphically with a set of UML diagrams or with textual languages. Unfortunately, that there is no need to inspect or edit the actual source code, not all UML diagrams come with a precisely defined execution which is generated from the models automatically. However, semantics and thus, code generation is hindered. In this paper, an practical experiences have shown that language-specific adap- implementation of the Action Language for Foundational UML tations to the generated source code are frequently necessary. (Alf) standard is presented, which allows for textual modeling In EMF, for instance, only structure is modeled by means of of software systems.
    [Show full text]
  • Japanese Bibliographic Records and CJK Cataloging in U.S
    San Jose State University SJSU ScholarWorks Master's Theses Master's Theses and Graduate Research Fall 2009 Japanese bibliographic records and CJK cataloging in U.S. university libraries. Mie Onnagawa San Jose State University Follow this and additional works at: https://scholarworks.sjsu.edu/etd_theses Recommended Citation Onnagawa, Mie, "Japanese bibliographic records and CJK cataloging in U.S. university libraries." (2009). Master's Theses. 4010. DOI: https://doi.org/10.31979/etd.pcb8-mryq https://scholarworks.sjsu.edu/etd_theses/4010 This Thesis is brought to you for free and open access by the Master's Theses and Graduate Research at SJSU ScholarWorks. It has been accepted for inclusion in Master's Theses by an authorized administrator of SJSU ScholarWorks. For more information, please contact [email protected]. JAPANESE BIBLIOGRAPHIC RECORDS AND CJK CATALOGING IN U.S. UNIVERSITY LIBRARIES A Thesis Presented to The Faculty of the School of Library and Information Science San Jose State University In Partial Fulfillment of the Requirements for the Degree Master of Library and Information Science by Mie Onnagawa December 2009 UMI Number: 1484368 All rights reserved INFORMATION TO ALL USERS The quality of this reproduction is dependent upon the quality of the copy submitted. In the unlikely event that the author did not send a complete manuscript and there are missing pages, these will be noted. Also, if material had to be removed, a note will indicate the deletion. UMT Dissertation Publishing UM! 1484368 Copyright 2010 by ProQuest LLC. All rights reserved. This edition of the work is protected against unauthorized copying under Title 17, United States Code.
    [Show full text]
  • Course Structure & Syllabus of B.Tech Programme In
    Course Structure & Syllabus of B.Tech Programme in Information Technology (From the Session 2015-16) VSSUT, BURLA COURSE STRUCTURE FIRST YEAR (COMMON TO ALL BRANCHES) FIRST SEMESTER SECOND SEMESTER Contact Contact Theory Hrs. Theory Hrs. CR CR Course Course Subject L .T .P Subject L. T. P Code Code Mathematics-I 3 - 1 - 0 4 Mathematics-II 3 - 1 - 0 4 Physics/Chemistry 3 - 1 - 0 4 Chemistry/ Physics 3 - 1 - 0 4 Engineering Computer /CS15- CS15- Mechanics/Computer 3 - 1 - 0 4 Programming/Engineering 3 - 1 - 0 4 008 008/ Programming Mechanics Basic Electrical Engineering/ Basic Electronics/Basic 3 - 1 - 0 4 3 - 1 - 0 4 Basic Electronics Electrical Engineering English/Environmental Environmental 3 - 1 - 0 4 3 - 1 - 0 4 Studies Studies/English Sessionals Sessionals Physics Laboratory/ Chemistry Lab/ Physics 0 - 0 - 3 2 0 - 0 - 3 2 Chemistry Lab Laboratory Workshop-I/Engineering Engineering Drawing/ 0 - 0 - 3 2 0 - 0 - 3 2 Drawing Workshop-I Basic Electrical Engineering Basic Electronics Lab/Basic 0 - 0 - 3 2 0 - 0 - 3 2 Lab/Basic Electronics Lab Electrical Engineering Lab Business Communication Programming Lab/ /CS15- CS15- and Presentation Skill/ 0 - 0 - 3 2 Business Communication 0 - 0 - 3 2 984 984/ Programming Lab and Presentation Skill Total 15-5-15 28 Total 15-5-15 28 SECOND YEAR THIRD SEMESTER FOURTH SEMESTER Contact Contact Theory Hrs. Theory Hrs. CR CR Course Subject L .T .P Course Code Subject L. T. P Code Mathematics-III Computer Organization 3 - 1 - 0 4 CS15-007 and Architecture 3 - 1 - 0 4 Digital Systems 3 - 1 - 0 4 CS15-032 Theory
    [Show full text]
  • OMG Meta Object Facility (MOF) Core Specification
    Date : October 2019 OMG Meta Object Facility (MOF) Core Specification Version 2.5.1 OMG Document Number: formal/2019-10-01 Standard document URL: https://www.omg.org/spec/MOF/2.5.1 Normative Machine-Readable Files: https://www.omg.org/spec/MOF/20131001/MOF.xmi Informative Machine-Readable Files: https://www.omg.org/spec/MOF/20131001/CMOFConstraints.ocl https://www.omg.org/spec/MOF/20131001/EMOFConstraints.ocl Copyright © 2003, Adaptive Copyright © 2003, Ceira Technologies, Inc. Copyright © 2003, Compuware Corporation Copyright © 2003, Data Access Technologies, Inc. Copyright © 2003, DSTC Copyright © 2003, Gentleware Copyright © 2003, Hewlett-Packard Copyright © 2003, International Business Machines Copyright © 2003, IONA Copyright © 2003, MetaMatrix Copyright © 2015, Object Management Group Copyright © 2003, Softeam Copyright © 2003, SUN Copyright © 2003, Telelogic AB Copyright © 2003, Unisys USE OF SPECIFICATION - TERMS, CONDITIONS & NOTICES The material in this document details an Object Management Group specification in accordance with the terms, conditions and notices set forth below. This document does not represent a commitment to implement any portion of this specification in any company's products. The information contained in this document is subject to change without notice. LICENSES The companies listed above have granted to the Object Management Group, Inc. (OMG) a nonexclusive, royalty-free, paid up, worldwide license to copy and distribute this document and to modify this document and distribute copies of the modified version. Each of the copyright holders listed above has agreed that no person shall be deemed to have infringed the copyright in the included material of any such copyright holder by reason of having used the specification set forth herein or having conformed any computer software to the specification.
    [Show full text]
  • A Comparison of Flexible BPMN and CMMN in Practice: a Case Study on Component Release Processes
    2018 IEEE 22nd International Enterprise Distributed Object Computing Conference A Comparison of Flexible BPMN and CMMN in Practice: A Case Study on Component Release Processes Andre´ Zensen Jochen M. Kuster¨ Bielefeld University of Applied Sciences Bielefeld University of Applied Sciences Bielefeld, Germany Bielefeld, Germany Email: [email protected] Email: [email protected] Abstract—The Object Management Group maintains two no- derive simple guidelines. While the findings can not be used tations to model business processes, BPMN and CMMN. While to make generalized statements, they can aid in choosing ff ff the two follow di erent approaches, both o er structures to which standard to use to model processes or parts of processes model flexible processes or parts thereof. This gives rise to the question which standard should be chosen to adequately model requiring flexible parts. such processes. We compare BPMN with a focus on its ad-hoc sub- The work is structured as follows: Section II introduces the process with elements of CMMN case models along a practical approaches and modeling standards. Section III describes the case study. While BPMN offers a certain degree of flexibility, case study and process. Section IV describes the models created CMMN has several benefits but also drawbacks. We discuss to capture the work on tasks needed to release a component advantages and disadvantages of both notations. To answer the question of which notation to use for modeling flexible processes, for production. A comparison is made in section V to highlight we derive simple guidelines to help in making an informed choice.
    [Show full text]