1 © 2003, Cisco Systems, Inc. All rights reserved. DMTF and Cisco Profile overview/comparison August 17, 2005.

Slides:



Advertisements
Similar presentations
Helmut König, Siemens Medical Solutions
Advertisements

18 Copyright © Oracle Corporation, All rights reserved. Transporting Data Between Databases.
ISO DSDL ISO – Document Schema Definition Languages (DSDL) Martin Bryan Convenor, JTC1/SC18 WG1.
Introduction to Control Flow Patterns and BizAgi
Unified Modeling Language Philip Liew
TSS Architecture Definition Context. TSS Scoping Study Context Detailed Requirements Specification (products, functionality) High Level Architecture Description.
Copyright ©2004 Cezary Z Janikow 1 Domain Model n Visualization of entities and relationships n In UP presented as Class Diagrams – Classes, Relationships,
Copyright © 2011 Pearson Education, Inc. Publishing as Pearson Addison-Wesley Chapter 7 Data Modeling Using the Entity- Relationship (ER) Model.
7. 2Object-Oriented Analysis and Design with the Unified Process Objectives  Detailed Object-Oriented Requirements Definitions  System Processes—A Use.
Sharif University of Technology1 Design and Use-case Realization Software Engineering Laboratory Fall 2006.
Chapter 8 Structuring System Data Requirements
Web Service Architecture Part I- Overview and Models (based on W3C Working Group Note Frank.
® Eurostep.ESUKPC v0.1©Copyright Eurostep Limited An Introduction to ISO STEP Part 25 David Price.
Final Design and Implementation
Object-Oriented Analysis and Design
Object-Oriented Analysis and Design
1 CIM User Group Conference Call december 8th 2005 Using UN/CEFACT Core Component methodology for EIC/TC 57 works and CIM Jean-Luc SANSON Electrical Network.
Unified Modeling Language User Guide Section 2—Basic Structural Modeling Chapter 4—Classes.
SEG4110 – Advanced Software Design and Reengineering
UML Collaboration Diagram. Recap System Sequence Diagrams (SSD) UML for SSD Examples.
Organizing Information Digitally Norm Friesen. Overview General properties of digital information Relational: tabular & linked Object-Oriented: inheritance.
BPMN By Hosein Bitaraf Software Engineering. Business Process Model and Notation (BPMN) is a graphical representation for specifying business processes.
XML CPSC 315 – Programming Studio Fall 2008 Project 3, Lecture 1.
PLANNING RSTWG Review of Planning Concept of Operations & Requirements Tasks.
Introduction to MDA (Model Driven Architecture) CYT.
Computer Science 101 Database Concepts. Database Collection of related data Models real world “universe” Reflects changes Specific purposes and audience.
Entity Framework Overview. Entity Framework A set of technologies in ADO.NET that support the development of data-oriented software applications A component.
SOEN 343 Software Design Section H Fall 2006 Dr Greg Butler
Copyright 2002 Prentice-Hall, Inc. Chapter 2 Object-Oriented Analysis and Design Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer Joey.
Guideline 12 Provide context and orientation information.
5 - 1 Copyright © 2006, The McGraw-Hill Companies, Inc. All rights reserved.
CS 4850: Senior Project Fall 2014 Object-Oriented Design.
NJIT UML Class Diagrams Chapter 16 Applying UML and Patterns Craig Larman.
1 Innovative Solutions For Mission Critical Systems Using EMF Annotations to Drive Program Behavior February 19, 2014.
Chapter 7 The Object-Oriented Approach to Requirements.
[ Part III of The XML seminar ] Presenter: Xiaogeng Zhao A Introduction of XQL.
Project X Group Y Presenters: (indicate roles). Part I: Project Overview System provides functionality X Motivation for project –Address problem with…
Logical view –show classes and objects Process view –models the executables Implementation view –Files, configuration and versions Deployment view –Physical.
Unified Modeling Language User Guide Section 4 - Basic Behavioral Modeling Chapter 16 - Use Cases Chapter 17 - Use Case Diagrams.
Analyzing Systems Using Data Dictionaries Systems Analysis and Design, 8e Kendall & Kendall 8.
Database Design – Lecture 4 Conceptual Data Modeling.
INFO275 Database Management Term Project. Overview Your project will be to define, design and build a functioning database, to support an application.
William Sanborn Pfeiffer Kaye Adkins
CIM LAB MEETING Presentation on UML Rakesh Mopidevi Kwangyeol Ryu.
1 Developing a Metadata Element Set or an Application Profile Image credits: 6Y old Anthony.
Presentation for Stuttgart Steve Carson GSC Associates
Chapter 5 System Modeling. What is System modeling? System modeling is the process of developing abstract models of a system, with each model presenting.
© 2006 Cisco Systems, Inc. All rights reserved. CUDN v1.1—3-1 Developing a High-Level Design Final Design and Implementation.
AMI -ENT Service Definition Team Step-by-Step Modeling and Artifacts Generation Process.
CONNECTING COMPONENT Pertemuan Matakuliah: M Analisis dan Perancangan Sistem Informasi Lanjut Tahun:
Copyright © 2007, Oracle. All rights reserved. Managing Items and Item Catalogs.
24 Copyright © 2009, Oracle. All rights reserved. Building Views and Charts in Requests.
Chapter 18. Copyright 2003, Paradigm Publishing Inc. CHAPTER 18 BACKNEXTEND 18-2 LINKS TO OBJECTIVES Sort Text in Paragraphs, Columns, and Tables Sort.
UNIT-IV Designing Classes – Access Layer ‐ Object Storage ‐ Object Interoperability.
XML: Extensible Markup Language
Systems Analysis and Design in a Changing World, Fourth Edition
Secrets of the Process Modeler
Group Y Presenters: (indicate roles)
Use Case Model.
Unified Modeling Language
Introduction to Control Flow Patterns and BizAgi
Group Y Presenters: (indicate roles)
Object-Oriented Design
Interactions.
Modelling Clinical Information Using UML
Reporting Guidance Consistency Check
Copyright © 2015, 2012, 2009 Elsevier Inc. All rights reserved.
Systems Architecture & Design Lecture 3 Architecture Frameworks
Copyright © 2015, 2012, 2009 Elsevier Inc. All rights reserved.
CIM Cooperative Work Program (COOP)
Presentation transcript:

1 © 2003, Cisco Systems, Inc. All rights reserved. DMTF and Cisco Profile overview/comparison August 17, 2005

222 © 2003, Cisco Systems, Inc. All rights reserved. What Is a Profile? A Profile is a specification that defines the subset of the CIM Schema and associated behavior for a management domain The management domain is a set of related management tasks DMTF is currently planning on a document based specification for Profiles –Cisco working towards an XML based specification from which a document can be generated.

333 © 2003, Cisco Systems, Inc. All rights reserved. DMTF Profile definition1of 5 Synopsis –Profile name –Version –Organization –CIM Schema version (on which the profile is based) –Specializes –Cisco: Experimental, Final, Deprecated –One paragraph summary that may be used in other documents to describe the profile

444 © 2003, Cisco Systems, Inc. All rights reserved. DMTF Profile definition2 of 5 Description (management domain & model overview) Implementation Requirements/Guidelines (informative) Methods –Class Methods 1 to 2 paragraph description Table specifying the return values and parameters Table specifying standard messages –Intrinsic Methods (3 different table options) Mandatory, Optional, Unspecified Cisco: Included in the CIM Elements section

555 © 2003, Cisco Systems, Inc. All rights reserved. DMTF Profile definition3 of 5 Related Profiles and Conditional Behavior –Table format with the following columns Profile name Organization Version Requirement (Optional, Conditional, Mandatory) Description –Conditional behavior subclauses Cisco: Constraints specified by OCL

666 © 2003, Cisco Systems, Inc. All rights reserved. DMTF Profile definition4 of 5 Use Cases –Defines the steps required to accomplish some goal and the affects to the model –Different starting conditions and ending conditions –All class methods included in the use cases (instance/object and sequence diagrams) Cisco: Various instance/sequence diagrams that also illustrate “conditional” CIM elements Cisco: Included in the method definition in the CIM Elements section

777 © 2003, Cisco Systems, Inc. All rights reserved. DMTF Profile definition5 of 5 CIM Elements –Overview table has rows for Classes and Indications. Columns for: Element name (class or filter) Requirement Description –Each class has a separate subclause Description (relationship of class to underlying implementation) Subclause Table has rows for properties and methods. Columns for: –Element name –Requirement –Description (reference to Method section, values) Cisco: Properties, Methods, & Associations

888 © 2003, Cisco Systems, Inc. All rights reserved. Cisco Parts of a Profile strings Enumeration: Exp, Final, Dep CR tracking

999 © 2003, Cisco Systems, Inc. All rights reserved. Cisco Parts of a Profile - details 1 of 3 of type “body”

10 © 2003, Cisco Systems, Inc. All rights reserved. Cisco Parts of a Profile - details 2 of 3 Name, Organization, Version, RequirementsLevel Language, Constraint, Description

11 © 2003, Cisco Systems, Inc. All rights reserved. Cisco Parts of a Profile - details 3 of 3

12 © 2003, Cisco Systems, Inc. All rights reserved. Cisco Parts of a Profile - class Constraint describing how to distinguish “context” string Language, Constraint, Description WORK in PROGRESS for auto-gen of model diagrams

13 © 2003, Cisco Systems, Inc. All rights reserved. Cisco Parts of a Profile – class: property Enumeration body Value(s) or Pattern

14 © 2003, Cisco Systems, Inc. All rights reserved. Cisco Parts of a Profile – class:method string Text, State, and/or sequence diagrams Language, Constraint, Description

15 © 2003, Cisco Systems, Inc. All rights reserved. Cisco Parts of a Profile – class:assoc string Language, Constraint, Description “MODEL” | # boolean Other participant(s) in the association

16 © 2003, Cisco Systems, Inc. All rights reserved. Cisco Parts of a Profile – Filters

17 © 2003, Cisco Systems, Inc. All rights reserved. Example