DOCSLIB.ORG

Oracle® SQL Developer Data Modeler User's Guide

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Oracle® SQL Developer Data Modeler User's Guide Oracle® SQL Developer Data Modeler User's Guide Release 17.3 E90546-01 September 2017 Oracle SQL Developer Data Modeler User's Guide, Release 17.3 E90546-01 Copyright © 2008, 2017, Oracle and/or its affiliates. All rights reserved. Primary Author: Celin Cherian Contributing Authors: Chuck Murray Contributors: Philip Stoyanov This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency- specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government. This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications. Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners. Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group. This software or hardware and documentation may provide access to or information about content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle. Contents Preface Audience xii Documentation Accessibility xii Related Documents xii Conventions xii Third-Party License Information xiii 1 Data Modeler Concepts and Usage 1.1 Installing and Getting Started with SQL Developer Data Modeler 1-1 1.2 Data Modeler User Interface 1-2 1.2.1 Menus for Data Modeler 1-4 1.2.2 Context Menus 1-8 1.3 Working with Data Modeler 1-10 1.3.1 Database Design 1-11 1.3.2 Data Types Model 1-11 1.3.2.1 Data Types Diagram and Subviews 1-12 1.3.2.2 Distinct Types 1-13 1.3.2.3 Structured Types 1-14 1.3.2.4 Collection Types 1-14 1.3.2.5 Logical Types 1-14 1.3.3 Process Model 1-15 1.3.3.1 Data Flow Diagrams 1-16 1.3.3.2 Transformation Processes and Packages 1-16 1.3.4 Logical Model 1-16 1.3.4.1 Logical Diagram and Subviews 1-17 1.3.4.2 Entities 1-18 1.3.4.3 Attributes 1-18 1.3.4.4 Unique Identifiers (UIDs) 1-18 1.3.4.5 Inheritances 1-18 1.3.4.6 Relations 1-18 1.3.4.7 Arcs 1-19 1.3.4.8 Type Substitution 1-19 iii 1.3.4.9 Views 1-19 1.3.5 Relational Models 1-19 1.3.5.1 Relational Diagram and Subviews 1-20 1.3.5.2 Tables 1-21 1.3.5.3 Columns 1-21 1.3.5.4 Indexes 1-21 1.3.5.5 Relations 1-21 1.3.5.6 Relational Views 1-21 1.3.6 Physical Models 1-22 1.3.6.1 Clusters 1-22 1.3.6.2 Contexts 1-23 1.3.6.3 Dimensions 1-23 1.3.6.4 Directories 1-23 1.3.6.5 Disk Groups 1-23 1.3.6.6 External Tables 1-23 1.3.6.7 Indexes 1-23 1.3.6.8 Roles 1-23 1.3.6.9 Rollback Segments 1-24 1.3.6.10 Segments (Segment Templates) 1-24 1.3.6.11 Sequences 1-24 1.3.6.12 Snapshots 1-24 1.3.6.13 Stored Procedures 1-24 1.3.6.14 Synonyms 1-24 1.3.6.15 Structured Types 1-24 1.3.6.16 Tables 1-25 1.3.6.17 Tablespaces 1-25 1.3.6.18 Users 1-25 1.3.6.19 Views 1-25 1.3.7 Business Information 1-25 1.3.7.1 Contacts 1-26 1.3.7.2 Documents 1-26 1.3.7.3 Emails 1-26 1.3.7.4 Locations 1-26 1.3.7.5 Resource Locators 1-26 1.3.7.6 Responsible Parties 1-27 1.3.7.7 Telephones 1-27 1.4 Approaches to Data Modeling 1-27 1.4.1 Top-Down Modeling 1-27 1.4.2 Bottom-Up Modeling 1-29 1.4.3 Targeted Modeling 1-30 1.5 User Preferences for Data Modeler 1-31 iv 1.5.1 Environment 1-31 1.5.2 Data Modeler 1-32 1.5.2.1 DDL 1-33 1.5.2.2 Diagram 1-36 1.5.2.3 Model 1-36 1.5.2.4 Reports 1-39 1.5.2.5 Search 1-40 1.5.2.6 Third Party JDBC Drivers 1-40 1.5.3 Format 1-40 1.5.4 Global Ignore List 1-41 1.5.5 Mouse Actions 1-41 1.5.6 Shortcut Keys (Accelerator Keys) 1-42 1.5.7 SSH (Secure Shell) 1-43 1.5.8 Usage Reporting 1-43 1.5.9 Versioning 1-43 1.5.10 Web Browser and Proxy 1-44 1.6 Saving, Opening, Exporting, and Importing Designs 1-45 1.6.1 Importing a DDL File 1-46 1.6.2 Importing Cube Views Metadata 1-46 1.6.3 Importing from Microsoft XMLA 1-46 1.6.4 Importing an ERwin File 1-46 1.6.5 Importing from a Data Dictionary 1-47 1.6.6 Importing an Oracle Designer Model 1-47 1.6.7 Importing a Data Modeler Design 1-47 1.6.8 Importing a Domain 1-47 1.7 Exporting and Importing Preferences and Other Settings 1-47 1.7.1 Restoring the Original Data Modeler Preferences 1-48 1.8 Data Modeler Reports 1-48 1.8.1 Generating Reports as RTF, HTML, or PDF Files 1-48 1.8.2 Using the Reporting Repository and Reporting Schema 1-50 1.8.3 Using SQL Developer to View Exported Reporting Schema Data 1-51 1.8.3.1 Design Content reports 1-52 1.8.3.2 Design Rules reports 1-52 1.9 Using Versioning 1-53 1.9.1 About Subversion and Data Modeler 1-53 1.9.1.1 Pending Changes 1-53 1.9.2 Basic Workflow: Using Subversion with a Design 1-54 1.10 Data Modeler Accessibility Information 1-55 1.11 For More Information About Data Modeling 1-56 1.12 Third-Party License Information 1-56 v 1.12.1 Batik Version 1.7 1-56 2 Data Modeler Tutorial: Modeling for a Small Database 2.1 Develop the Logical Model 2-1 2.1.1 Adding Domains 2-1 2.1.2 Creating the Books Entity 2-2 2.1.3 Creating the Patrons Entity 2-3 2.1.4 Creating the Transactions Entity 2-4 2.1.5 Creating Relations Between Entities 2-5 2.2 Develop the Relational Model 2-6 2.3 Generate DDL 2-6 2.4 Save the Design 2-7 3 Data Modeler Dialog Boxes 3.1 Add Event 3-1 3.2 Add/Remove Objects 3-1 3.3 Advanced Properties (Connections) 3-2 3.4 Arc Properties 3-2 3.5 Attribute Properties 3-3 3.6 Change Subview Object Names Prefix 3-4 3.7 Change Request Properties 3-4 3.8 Change Requests Administration 3-5 3.9 Check for Updates 3-5 3.10 Choose Directory 3-6 3.11 Collection Type Properties 3-6 3.12 Column Properties 3-7 3.13 Common Information in Dialog Boxes 3-9 3.14 Compare Mapping 3-10 3.15 Compare Modeling Designs 3-10 3.16 Compare Models 3-10 3.17 Color Palette and Custom Colors 3-12 3.18 Connection Information 3-12 3.19 Contact Properties 3-12 3.20 Create Database Connection 3-13 3.21 Create Discovered Foreign Keys 3-14 3.22 Cube Properties 3-15 3.23 Custom Reports Template 3-17 3.24 Data Dictionary Connections 3-18 3.25 Data Dictionary Import (Metadata Extraction) 3-19 vi 3.26 Database Connection Editor 3-20 3.27 DDL File Editor 3-20 3.28 DDL Generation Options 3-21 3.29 Design Properties 3-22 3.30 Design Rules 3-24 3.30.1 Design Rules 3-24 3.30.2 Custom Rules 3-25 3.30.3 Libraries 3-26 3.30.4 Transformations 3-26 3.31 Dimension Properties 3-26 3.32 Display Properties 3-28 3.33 Distinct Type Properties 3-28 3.34 Document Properties 3-28 3.35 Domain Properties (Domains Model) 3-29 3.36 Domains Administration 3-29 3.37 Email Properties 3-30 3.38 Engineering 3-30 3.39 Entity Properties 3-32 3.40 Event Properties 3-34 3.41 Export Cube Views Metadata 3-35 3.42 Export to Microsoft XMLA 3-35 3.43 Export to Oracle Analytic Workspaces 3-35 3.44 Export to Reporting Schema 3-36 3.45 Export Wizard 3-37 3.46 Export/Import Connections 3-38 3.46.1 Export Connections 3-38 3.46.2 Import Connections 3-39 3.47 External Agent Properties 3-39 3.48 External Data Properties 3-41 3.49 File Processing 3-41 3.50 Find Object (Search) 3-41 3.51 Flow Properties 3-42 3.52 Foreign Key Properties 3-43 3.53 Glossary Editor 3-44 3.54 Hierarchy Properties 3-46 3.55 Import Domains 3-47 3.56 Import Glossary (Naming Standard Definitions) 3-47 3.57
Load more

Recommended publications
  • Create Table Identity Primary Key Sql Server
    Create Table Identity Primary Key Sql Server Maurits foozle her Novokuznetsk sleeplessly, Johannine and preludial. High-principled and consonantal Keil often stroke triboluminescentsome proletarianization or spotlight nor'-east plop. or volunteer jealously. Foul-spoken Fabio always outstrips his kursaals if Davidson is There arise two ways to create tables in your Microsoft SQL database. Microsoft SQL Server has built-in an identity column fields which. An identity column contains a known numeric input for a row now the table. SOLVED Can select remove Identity from a primary case with. There cannot create table created on every case, primary key creates the server identity column if the current sql? As I today to refute these records into a U-SQL table review I am create a U-SQL database. Clustering option requires separate table created sequence generator always use sql server tables have to the key. This key creates the primary keys per the approach is. We love create Auto increment columns in oracle by using IDENTITY. PostgreSQL Identity Column PostgreSQL Tutorial. Oracle Identity Column A self-by-self Guide with Examples. Constraints that table created several keys means you can promote a primary. Not logged in Talk Contributions Create account already in. Primary keys are created, request was already creates a low due to do not complete this. IDENTITYNOT NULLPRIMARY KEY Identity Sequence. How weak I Reseed a SQL Server identity column TechRepublic. Hi You can use one query eg Hide Copy Code Create table tblEmplooyee Recordid bigint Primary key identity. SQL CREATE TABLE Statement Tutorial Republic. Hcl will assume we need be simplified to get the primary key multiple related two dissimilar objects or adding it separates structure is involved before you create identity? When the identity column is part of physician primary key SQL Server.
    [Show full text]
  • Powerdesigner 16.6 Data Modeling
    SAP® PowerDesigner® Document Version: 16.6 – 2016-02-22 Data Modeling Content 1 Building Data Models ...........................................................8 1.1 Getting Started with Data Modeling...................................................8 Conceptual Data Models........................................................8 Logical Data Models...........................................................9 Physical Data Models..........................................................9 Creating a Data Model.........................................................10 Customizing your Modeling Environment........................................... 15 1.2 Conceptual and Logical Diagrams...................................................26 Supported CDM/LDM Notations.................................................27 Conceptual Diagrams.........................................................31 Logical Diagrams............................................................43 Data Items (CDM)............................................................47 Entities (CDM/LDM)..........................................................49 Attributes (CDM/LDM)........................................................55 Identifiers (CDM/LDM)........................................................58 Relationships (CDM/LDM)..................................................... 59 Associations and Association Links (CDM)..........................................70 Inheritances (CDM/LDM)......................................................77 1.3 Physical Diagrams..............................................................82
    [Show full text]
  • Keys Are, As Their Name Suggests, a Key Part of a Relational Database
    The key is defined as the column or attribute of the database table. For example if a table has id, name and address as the column names then each one is known as the key for that table. We can also say that the table has 3 keys as id, name and address. The keys are also used to identify each record in the database table . Primary Key:- • Every database table should have one or more columns designated as the primary key . The value this key holds should be unique for each record in the database. For example, assume we have a table called Employees (SSN- social security No) that contains personnel information for every employee in our firm. We’ need to select an appropriate primary key that would uniquely identify each employee. Primary Key • The primary key must contain unique values, must never be null and uniquely identify each record in the table. • As an example, a student id might be a primary key in a student table, a department code in a table of all departments in an organisation. Unique Key • The UNIQUE constraint uniquely identifies each record in a database table. • Allows Null value. But only one Null value. • A table can have more than one UNIQUE Key Column[s] • A table can have multiple unique keys Differences between Primary Key and Unique Key: • Primary Key 1. A primary key cannot allow null (a primary key cannot be defined on columns that allow nulls). 2. Each table can have only one primary key. • Unique Key 1. A unique key can allow null (a unique key can be defined on columns that allow nulls.) 2.
    [Show full text]
  • Rfgen Users Guide
    DataMax Software Group Inc. 1101 Investment Blvd. El Dorado Hills, CA 95762 USA RFgen Users Guide All Editions RFgen 5.2 © 2021 RFgen Software. A division of DataMAX Software Group, Inc. All Rights Reserved. RFgen 5.2 Users Guide Table of Contents Introduction to RFgen 1 Connection Tab 33 Basic Implementation Steps 2 Connection Tab - SAP 33 Configuration Overview 3 SAP Data Encryption 34 Configurations Shared by Dev Studio To Configure for JDE 35 and Services Console: 3 Adding A New Web Services Connection 40 Connections Shared by Dev Studio Configuring the Host Connection 42 and Services Console: 4 Configuring User Access Control 45 Configurations Available Only in Dev Studio 4 Adding or Removing RFgen Admin- istrators / RFgen SubAdmins 46 Connections Available Only in Dev Studio 4 Dev Studio Configuration Options 47 Configuring the RFgen Application Data- Configuring Menu and Key Settings 48 base 4 System Menu Configuration 48 Configuring Application Preferences 7 Function Key Actions 49 Configuring Application Services 10 Configuring the Scripting Environment 50 Configuring Environment Settings 14 Configuring Source Control Options 52 Configure System Environment 14 Configuring System Properties 54 Configuring Transaction Management DB Connection 19 Download Enterprise Objects 54 Create Application Event Database 19 Downloading ERP Business Functions 55 Configuring System Queues and Tasks 20 Downloading JDE Processing Options 55 Add New Enterprise Connections 22 Viewing Enterprise Objects 57 Adding a New DataSource Connection 22 Viewing
    [Show full text]
  • Data Modeler User's Guide
    Oracle® SQL Developer Data Modeler User's Guide Release 18.1 E94838-01 March 2018 Oracle SQL Developer Data Modeler User's Guide, Release 18.1 E94838-01 Copyright © 2008, 2018, Oracle and/or its affiliates. All rights reserved. Primary Author: Celin Cherian Contributing Authors: Chuck Murray Contributors: Philip Stoyanov This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency- specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs.
    [Show full text]
  • PML, an Object Oriented Process Modelling Language
    PML, an Object Oriented Process Modeling Language Prof. Dr.-Ing. Reiner Anderl 1, and Dipl.-Ing. Jochen Raßler 2 1 Prof. Dr.-Ing. Reiner Anderl, Germany, [email protected] 2 Dipl.-Ing. Jochen Raßler, Germany, [email protected] Abstract: Processes are very important for the success within many business fields. They define the proper application of methods, technologies, tools and company structures in order to reach business goals. Important processes to be defined are manufacturing processes or product development processes for example to guarantee the company’s success. Over the last decades many process modeling languages have been developed to cover the needs of process modeling. Those modeling languages have several limitations, mainly they are still procedural and didn’t follow the paradigm change to object oriented modeling and thus often lead to process models, which are difficult to maintain. In previous papers we have introduced PML, Process Modeling Language, and shown it’s usage in process modeling. PML is derived from UML and hence fully object oriented and uses modern modeling techniques. It is based on process class diagrams that describe methods and resources for process modeling. In this paper the modeling language is described in more detail and new language elements will be introduced to develop the language to a generic usable process modeling language. Keywords: process modeling language, PML, UML 1. Introduction As the tendency of enterprises to collaborate growths steadily, industry faces new challenges managing business processes, product development processes, manufacturing processes and much more. Furthermore, discipline spanning product development processes are increasing, e.
    [Show full text]
  • Plantuml Language Reference Guide (Version 1.2021.2)
    Drawing UML with PlantUML PlantUML Language Reference Guide (Version 1.2021.2) PlantUML is a component that allows to quickly write : • Sequence diagram • Usecase diagram • Class diagram • Object diagram • Activity diagram • Component diagram • Deployment diagram • State diagram • Timing diagram The following non-UML diagrams are also supported: • JSON Data • YAML Data • Network diagram (nwdiag) • Wireframe graphical interface • Archimate diagram • Specification and Description Language (SDL) • Ditaa diagram • Gantt diagram • MindMap diagram • Work Breakdown Structure diagram • Mathematic with AsciiMath or JLaTeXMath notation • Entity Relationship diagram Diagrams are defined using a simple and intuitive language. 1 SEQUENCE DIAGRAM 1 Sequence Diagram 1.1 Basic examples The sequence -> is used to draw a message between two participants. Participants do not have to be explicitly declared. To have a dotted arrow, you use --> It is also possible to use <- and <--. That does not change the drawing, but may improve readability. Note that this is only true for sequence diagrams, rules are different for the other diagrams. @startuml Alice -> Bob: Authentication Request Bob --> Alice: Authentication Response Alice -> Bob: Another authentication Request Alice <-- Bob: Another authentication Response @enduml 1.2 Declaring participant If the keyword participant is used to declare a participant, more control on that participant is possible. The order of declaration will be the (default) order of display. Using these other keywords to declare participants
    [Show full text]
  • Integration Definition for Function Modeling (IDEF0)
    NIST U.S. DEPARTMENT OF COMMERCE PUBLICATIONS £ Technology Administration National Institute of Standards and Technology FIPS PUB 183 FEDERAL INFORMATION PROCESSING STANDARDS PUBLICATION INTEGRATION DEFINITION FOR FUNCTION MODELING (IDEFO) » Category: Software Standard SUBCATEGORY: MODELING TECHNIQUES 1993 December 21 183 PUB FIPS JK- 45C .AS A3 //I S3 IS 93 FIPS PUB 183 FEDERAL INFORMATION PROCESSING STANDARDS PUBLICATION INTEGRATION DEFINITION FOR FUNCTION MODELING (IDEFO) Category: Software Standard Subcategory: Modeling Techniques Computer Systems Laboratory National Institute of Standards and Technology Gaithersburg, MD 20899 Issued December 21, 1993 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 Foreword The Federal Information Processing Standards Publication Series of the National Institute of Standards and Technology (NIST) is the official publication relating to standards and guidelines adopted and promulgated under the provisions of Section 111 (d) of the Federal Property and Administrative Services Act of 1949 as amended by the Computer Security Act of 1987, Public Law 100-235. These mandates have given the Secretary of Commerce and NIST important responsibilities for improving the utilization and management of computer and related telecommunications systems in the Federal Government. The NIST, through its Computer Systems Laboratory, provides leadership, technical guidance,
    [Show full text]
  • Metamodeling and Method Engineering with Conceptbase”
    This is a pre-print of the book chapter M. Jeusfeld: “Metamodeling and method engineering with ConceptBase” . In Jeusfeld, M.A., Jarke, M., Mylopoulos, J. (eds): Metamodeling for Method Engineering, pp. 89-168. The MIT Press., 2009; the original book is available from MIT Press http://mitpress.mit.edu/node/192290 This pre-print may only be used for scholar, non-commercial purposes. Most of the sources for the examples in this chapter are available via http://merkur.informatik.rwth-aachen.de/pub/bscw.cgi/3782591 for download. They require ConceptBase 7.0 or later available from http://conceptbase.cc. Metamodeling and Method Engineering with ConceptBase Manfred Jeusfeld Abstract. This chapter provides a practical guide on how to use the meta data repository ConceptBase to design information modeling methods by using meta- modeling. After motivating the abstraction principles behind meta-modeling, the language Telos as realized in ConceptBase is presented. First, a standard factual representation of statements at any IRDS abstraction level is defined. Then, the foundation of Telos as a logical theory is elaborated yielding simple fixpoint semantics. The principles for object naming, instantiation, attribution, and specialization are reflected by roughly 30 logical axioms. After the language axiomatization, user-defined rules, constraints and queries are introduced. The first part is concluded by a description of active rules that allows the specification of reactions of ConceptBase to external events. The second part applies the language features of the first part to a full-fledged information modeling method: The Yourdan method for Modern Structured Analysis. The notations of the Yourdan method are designed along the IRDS framework.
    [Show full text]
  • BEA Weblogic Platform Security Guide
    UNCLASSIFIED Report Number: I33-004R-2005 BEA WebLogic Platform Security Guide Network Applications Team of the Systems and Network Attack Center (SNAC) Publication Date: 4 April 2005 Version Number: 1.0 National Security Agency ATTN: I33 9800 Savage Road Ft. Meade, Maryland 20755-6704 410-854-6191 Commercial 410-859-6510 Fax UNCLASSIFIED UNCLASSIFIED Acknowledgment We thank the MITRE Corporation for its collaborative effort in the development of this guide. Working closely with our NSA representatives, the MITRE team—Ellen Laderman (task leader), Ron Couture, Perry Engle, Dan Scholten, Len LaPadula (task product manager) and Mark Metea (Security Guides Project Oversight)—generated most of the security recommendations in this guide and produced the first draft. ii UNCLASSIFIED UNCLASSIFIED Warnings Do not attempt to implement any of the settings in this guide without first testing in a non-operational environment. This document is only a guide containing recommended security settings. It is not meant to replace well-structured policy or sound judgment. Furthermore, this guide does not address site-specific configuration issues. Care must be taken when implementing this guide to address local operational and policy concerns. The security configuration described in this document has been tested on a Solaris system. Extra care should be taken when applying the configuration in other environments. SOFTWARE IS PROVIDED "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND
    [Show full text]
  • Using Telelogic DOORS and Microsoft Visio to Model and Visualize Complex Business Processes
    Using Telelogic DOORS and Microsoft Visio to Model and Visualize Complex Business Processes “The Business Driven Application Lifecycle” Bob Sherman Procter & Gamble Pharmaceuticals [email protected] Michael Sutherland Galactic Solutions Group, LLC [email protected] Prepared for the Telelogic 2005 User Group Conference, Americas & Asia/Pacific http://www.telelogic.com/news/usergroup/us2005/index.cfm 24 October 2005 Abstract: The fact that most Information Technology (IT) projects fail as a result of requirements management problems is common knowledge. What is not commonly recognized is that the widely haled “use case” and Object Oriented Analysis and Design (OOAD) phenomenon have resulted in little (if any) abatement of IT project failures. In fact, ten years after the advent of these methods, every major IT industry research group remains aligned on the fact that these projects are still failing at an alarming rate (less than a 30% success rate). Ironically, the popularity of use case and OOAD (e.g. UML) methods may be doing more harm than good by diverting our attention away from addressing the real root cause of IT project failures (when you have a new hammer, everything looks like a nail). This paper asserts that, the real root cause of IT project failures centers around the failure to map requirements to an accurate, precise, comprehensive, optimized business model. This argument will be supported by a using a brief recap of the history of use case and OOAD methods to identify differences between the problems these methods were intended to address and the challenges of today’s IT projects.
    [Show full text]
  • Plantuml Language Reference Guide
    Drawing UML with PlantUML Language Reference Guide (Version 5737) PlantUML is an Open Source project that allows to quickly write: • Sequence diagram, • Usecase diagram, • Class diagram, • Activity diagram, • Component diagram, • State diagram, • Object diagram. Diagrams are defined using a simple and intuitive language. 1 SEQUENCE DIAGRAM 1 Sequence Diagram 1.1 Basic examples Every UML description must start by @startuml and must finish by @enduml. The sequence ”->” is used to draw a message between two participants. Participants do not have to be explicitly declared. To have a dotted arrow, you use ”-->”. It is also possible to use ”<-” and ”<--”. That does not change the drawing, but may improve readability. Example: @startuml Alice -> Bob: Authentication Request Bob --> Alice: Authentication Response Alice -> Bob: Another authentication Request Alice <-- Bob: another authentication Response @enduml To use asynchronous message, you can use ”->>” or ”<<-”. @startuml Alice -> Bob: synchronous call Alice ->> Bob: asynchronous call @enduml PlantUML : Language Reference Guide, December 11, 2010 (Version 5737) 1 of 96 1.2 Declaring participant 1 SEQUENCE DIAGRAM 1.2 Declaring participant It is possible to change participant order using the participant keyword. It is also possible to use the actor keyword to use a stickman instead of a box for the participant. You can rename a participant using the as keyword. You can also change the background color of actor or participant, using html code or color name. Everything that starts with simple quote ' is a comment. @startuml actor Bob #red ' The only difference between actor and participant is the drawing participant Alice participant "I have a really\nlong name" as L #99FF99 Alice->Bob: Authentication Request Bob->Alice: Authentication Response Bob->L: Log transaction @enduml PlantUML : Language Reference Guide, December 11, 2010 (Version 5737) 2 of 96 1.3 Use non-letters in participants 1 SEQUENCE DIAGRAM 1.3 Use non-letters in participants You can use quotes to define participants.
    [Show full text]