DOCSLIB.ORG

User Interface Specification for Interactive Software Systems

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
User Interface Specification for Interactive Software Systems User Interface Specification for Interactive Software Systems Process-, Method- and Tool-Support for Interdisciplinary and Collaborative Requirements Modelling and Prototyping-Driven User Interface Specification Dissertation zur Erlangung des akademischen Grades des Doktor der Naturwissenschaften (Dr. rer. nat.) Universität Konstanz Mathematisch-Naturwissenschaftliche Sektion Fachbereich Informatik und Informationswissenschaft Vorgelegt von Thomas Memmel Betreuer der Dissertation: Prof. Dr. Harald Reiterer Tag der mündlichen Prüfung: 29. April 2009 1. Referent: Prof. Dr. Harald Reiterer 2. Referent: Prof. Dr. Rainer Kuhlen Prof. Dr. Rainer Kuhlen For Cathrin Acknowledgements I thank my advisor, Prof. Dr. Harald Reiterer, for more than 6 years of great Prof. Dr. Harald Reiterer teamwork. Since I joined his work group as a student researcher, his guidance and friendship have helped me to reach high goals and achieve scientific recognition. I thank Harald for his creative contributions and his unfailing support, which made him the best supervisor I could imagine. Every time I read the Dr. in front of my name, I will think about the person who made it possible. It was Harald! Moreover, I thank him for teaching me many skills, of which especially purposefulness and per- suasive power opened up a world of possibilities. Among the other researchers in the human-computer interaction work group, spe- My colleague and friend Fredrik cial thanks are due to my colleague Fredrik Gundelsweiler. Fredrik and I started working for Harald at the same time, and since then we have shared many experi- ences. I worked with Fredrik at Siemens AG in Munich, and we both gained interna- tional work experience during our stay at DaimlerChrysler AG in Singapore. Al- though our work topics diverged after we worked for the electronics division of Mercedes-Benz, being a PhD student without being able to sit face-to-face with Fredrik in the office would not have been nearly so much fun. I wish with all my heart that Fredrik and I will continue to be close friends and comrade-in-arms in the field of human-computer interaction. As one should never change a winning team, I am sure we will be able to profit from mutual advice and candidness. We travelled through various ups and downs in the last decade and I would not have missed a sin- gle experience we shared. I would also like to thank Jens Gerken, who helped me in evaluating the experi- Members of the workgroup HCI mental tool that is presented in my thesis. As a usability expert, Jens‟ expertise in usability evaluation made it possible to enhance both my conceptual and practical work. Moreover, I thank Florian Geyer and Johannes Rinn, who were Master‟s stu- dents and assistant researchers during my time as a PhD student. Their extraordinary engagement and their reliability helped to make the software tool presented in this thesis a successful contribution to research communities all over the world. I am sure that you and all the other students I was able to supervise will have successful careers. Most importantly, I thank my girlfriend Cathrin for her stamina in staying at my My girlfriend Cathrin side and supporting me through six months of hardship and hard work. Without her, my PhD project would have failed. She helped me to stay focused and resolute. Thanks to her love and friendship, I am beginning a new period of life. Having fin- ished my studies and moved to Switzerland, where I have signed a contract with Zuehlke Engineering AG, I look forward to the best possible life with her by my side. For being a remarkable person and companion, I thank Christian Daum, who de- parted this life in spring 2007. Thank you, Christian, for a wonderful time in South East Asia and for being my friend. I would also like to thank my parents, who gave me the opportunity to study and My parents to continue my education after both the Bachelor‟s and Master‟s degrees. Their trust in my willingness and determination always strengthened my drive to contribute value to the field of computer science. I especially thank my father for his belief in my business instincts. As a team, we were a particularly good balance of wise ex- perience with youthful „get up and go‟. I am proud that you let me contribute to the success of our family business during my studies. I thank all the people mentioned here for having an interest in my profession and General acknowledgement work, for respecting my job and the associated stress and strains, and for supporting me in reaching my goals over and over again. Thank you all. Thomas v vi Abstract Specifying user interfaces (UIs) is a fundamental activity in the UI development life cycle as the specification influences the subsequent steps. When the UI is to be specified, a picture is worth a thousand words, and the worst thing to do is write a natural-language specification for it. In corporate specification processes, Office-like applications dominate the work style of actors. Moving from text-based require- ments and problem-space concepts to a final UI design and then back again is there- fore a challenging task. Particularly for UI specification, actors must frequently switch between high-level descriptions and low-level detailed screens. Good-quality specifications are an essential first step in the development of corporate software systems that satisfy the users‟ needs. But the corporate UI development life cycle typically involves multiple actors, all of whom make their own individual inputs of UI artefacts expressed in their own formats, thus posing new constraints for integrat- ing these inputs into comprehensive and consistent specifications for a future UI. This thesis introduces a UI specification technique in which these actors can in- troduce their artefacts by sketching them in their respective input formats so as to in- tegrate them into one or more output formats. Each artefact can be introduced in a particular level of fidelity (ranging from low to high) and switched to an adjacent level of fidelity after appropriate refining. The resulting advanced format is called an interactive UI specification and is made up of interconnected artefacts that have dis- tinct levels of abstraction. The interactive UI specification is forwarded to the sup- plier, who can utilize its expressiveness to code the final UI in precise accordance with the requirements. The concept of interactive UI specification integrates interdisciplinary and infor- mal modelling languages with different levels of fidelity in UI prototyping. In order to determine the required ingredients of interactive UI specifications in detail, the different disciplines that contribute to corporate UI specification processes are ana- lyzed in similar detail. For each stage in the UI specification process, a set of arte- facts is specified. All stakeholders understand this set, and it can be used as a com- mon vehicle. Consequently, a network of shared artefacts is assembled into a common interdisciplinary denominator for software developers, interaction design- ers and business-process modellers in order to support UI modelling and specifica- tion-level UI design. All means of expression are selected by taking into considera- tion the need for linking and associating different requirements and UI designs. Together, they make up the interactive specification. The UI specification method presented in this thesis is complemented by an in- novative experimental tool known as INSPECTOR. The concept behind INSPECTOR is based on the work style of stakeholders participating in corporate UI specification processes. The tool utilizes a zoom-based design room and white- board metaphor to support the development and safekeeping of artefacts in a shared model repository. With regards to the transparency and traceability of the rationale of the UI specification process, transitions and dependencies can be externalized and traversed much better by using INSPECTOR. Compared to Office applications such as Microsoft Word or PowerPoint, INSPECTOR provides different perspectives on UI specification artefacts, allows the actors to keep track of requirements and sup- ports a smooth progression from the problem-space to the solution-space. In this way, co-evolutionary design of the UI is introduced, defined, and supported by a collaborative UI specification tool allowing multiple inputs and multiple outputs. Finally, the advantages of the approach are illustrated through a case study and by a report on three different empirical studies that reveal how the experts who were interviewed appreciate the approach. The thesis ends with a summary and an out- look on future work directed towards better tool support for multi-stakeholder UI specification. vii Zusammenfassung User Interface (UI) Spezifikationsprozesse involvieren unterschiedliche Akteure mit jeweils eigenen Ausdrucksmitteln. Insbesondere Organisationen, die zwar Soft- wareanwendungen entwickeln möchten, jedoch bei Planung und Umsetzung auf ex- terne Dienstleister angewiesen sind, müssen einen geeigneten Rahmen für die inter- disziplinäre Zusammenarbeit innerhalb und außerhalb des Unternehmens bestimmen. Der Erfolg der UI Entwicklung ist dabei meist von erheblicher Bedeu- tung für die Auftraggeberorganisation. Intern eingesetzte Anwendungen bestimmen die Effizienz und Effektivität softwaregestützter Prozesse maßgeblich. Interaktive Systeme, die in Produkte eingebettet werden oder einen Kommunikationskanal zum Kunden darstellen, müssen Design, Identität und meist auch Qualitätsmerkmale ei-
Load more

Recommended publications
  • WEKA Manual for Version 3-7-8
    WEKA Manual for Version 3-7-8 Remco R. Bouckaert Eibe Frank Mark Hall Richard Kirkby Peter Reutemann Alex Seewald David Scuse January 21, 2013 ⃝c 2002-2013 University of Waikato, Hamilton, New Zealand Alex Seewald (original Commnd-line primer) David Scuse (original Experimenter tutorial) This manual is licensed under the GNU General Public License version 3. More information about this license can be found at http://www.gnu.org/licenses/gpl-3.0-standalone.html Contents ITheCommand-line 11 1Acommand-lineprimer 13 1.1 Introduction . 13 1.2 Basic concepts . 14 1.2.1 Dataset . 14 1.2.2 Classifier . 16 1.2.3 weka.filters . 17 1.2.4 weka.classifiers . 19 1.3 Examples . 23 1.4 Additional packages and the package manager . .24 1.4.1 Package management . 25 1.4.2 Running installed learning algorithms . 26 II The Graphical User Interface 29 2LaunchingWEKA 31 3PackageManager 35 3.1 Mainwindow ............................. 35 3.2 Installing and removing packages . 36 3.2.1 Unofficalpackages ...................... 37 3.3 Usingahttpproxy.......................... 37 3.4 Using an alternative central package meta data repository . 37 3.5 Package manager property file . 38 4SimpleCLI 39 4.1 Commands . 39 4.2 Invocation . 40 4.3 Command redirection . 40 4.4 Command completion . 41 5Explorer 43 5.1 The user interface . 43 5.1.1 Section Tabs . 43 5.1.2 Status Box . 43 5.1.3 Log Button . 44 5.1.4 WEKA Status Icon . 44 3 4 CONTENTS 5.1.5 Graphical output . 44 5.2 Preprocessing . 45 5.2.1 Loading Data .
    [Show full text]
  • Tinkertool System 7 Reference Manual Ii
    Documentation 0642-1075/2 TinkerTool System 7 Reference Manual ii Version 7.5, August 24, 2021. US-English edition. MBS Documentation 0642-1075/2 © Copyright 2003 – 2021 by Marcel Bresink Software-Systeme Marcel Bresink Software-Systeme Ringstr. 21 56630 Kretz Germany All rights reserved. No part of this publication may be redistributed, translated in other languages, or transmitted, in any form or by any means, electronic, mechanical, recording, or otherwise, without the prior written permission of the publisher. This publication may contain examples of data used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental. This publication could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. The publisher may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice. Make sure that you are using the correct edition of the publication for the level of the product. The version number can be found at the top of this page. Apple, macOS, iCloud, and FireWire are registered trademarks of Apple Inc. Intel is a registered trademark of Intel Corporation. UNIX is a registered trademark of The Open Group. Broadcom is a registered trademark of Broadcom, Inc. Amazon Web Services is a registered trademark of Amazon.com, Inc.
    [Show full text]
  • Vtpin: Practical Vtable Hijacking Protection for Binaries
    VTPin: Practical VTable Hijacking Protection for Binaries Pawel Sarbinowski Vasileios P. Kemerlis Cristiano Giuffrida Vrije Universiteit Amsterdam Brown University Vrije Universiteit Amsterdam [email protected] [email protected] [email protected] Elias Athanasopoulos Vrije Universiteit Amsterdam [email protected] ABSTRACT 1. INTRODUCTION VTable hijacking has lately been promoted to the de facto technique The recent advances in software hardening have undoubtedly for exploiting C++ applications, and in particular web browsers. made exploitation a challenging craft [45]. Yet, despite the plethora VTables, however, can be manipulated without necessarily corrupt- of defenses in place [37], attackers still find ways to compromise ing memory, simply by leveraging use-after-free bugs. In fact, in essential commodity software, like web browsers [5,6]. Modern the recent Pwn2Own competitions all major web browsers were exploits are highly sophisticated and typically leverage a variety of compromised with exploits that employed (among others) use-after- different vulnerabilities to bypass established protections, such as free vulnerabilities and VTable hijacking. address space layout randomization (ASLR) [42], non-executable In this paper, we propose VTPin: a system to protect against memory [12], and sandboxing [18]. To this end, temporal safety VTable hijacking, via use-after-free vulnerabilities, in large C++ errors, and particularly use-after-free vulnerabilities, are becoming binaries that cannot be re-compiled or re-written. The main idea be- a key component of the attackers’ arsenal [1,2,7,8]. Interestingly, hind VTPin is to pin all the freed VTable pointers on a safe VTable exploiting use-after-free bugs does not require corrupting memory; under VTPin’s control.
    [Show full text]
  • United States Patent (19) 11 Patent Number: 6,061,061 Conrad Et Al
    US006061061A United States Patent (19) 11 Patent Number: 6,061,061 Conrad et al. (45) Date of Patent: *May 9, 2000 54) COMPUTER SYSTEM WITH GRAPHICAL 2693810 6/1991 France. USER INTERFACE INCLUDING SPRING LOADED ENCLOSURES OTHER PUBLICATIONS 75 Inventors: Thomas J. Conrad, San Jose; Yin Yin tiMy“M ft WindowSTM 7 User’sSer's Guide.Oude, MiMicroSOIL ft UorporaC Wong, Menlo Park, both of Calif. “Screen Dumps from Microsoft WindowsTM v3.1.” 73 ASSignee: Apple Computer, Inc., Cupertino, Microsoft Corporation, 1985-1992, pp. 1-10. Calif. Jeff Johnson, et al., “The Xerox Star: A Retrospective,” Computer, Sep. 1989, pp. 11-27. * Notice: This patent is subject to a terminal dis- Brad W. Myers, “Window Interfaces, A Taxonomy of Win claimer. dow Manager User Interfaces.” IEEE Computer Graphics and Applications, Sep. 1988, pp. 65-83. 21 Appl. No.: 08/889,719 “Automatic Window Management Mode.” IBM Technical 9 Disclosure Bulletin, vol. 35, No. 4B, Sep. 1992. 22 Filed: Jul. 8, 1997 (List continued on next page.) Related U.S. Application Data Primary Examiner-Crescelle N. dela Torre 63 Continuation of application No. 08/482,186, Jun. 7, 1995, Attorney, Agent, or Firm Blakely, Sokoloff Taylor & Pat. No. 5,680,562, which is a continuation of application Zafman No. 08/076.253, Jun. 11, 1993, Pat. No. 5,583,984. (51) Int. Cl. ................................................ G06F 15/00 57 ABSTRACT 52 U.S. Cl. ............................................. 345/340; 345/348 A new behavior in a graphical user interface allows the user 58 Field of Search ..................................... 345/340, 326, to open and close enclosures, while dragging an object.
    [Show full text]
  • Analysis Server User Guide
    Analysis Server User Guide This manual explains the basic principles and functionality of the Analysis Server, a software system that enables users to incorporate legacy software into reusable components that can be published on a network. This manual also discusses seven utilities for creating new software components: AnalysisLibraryWrapper, FileWrapper, ExcelWrap- per, ScriptWrapper, PerlWrapper, PXCWrapper, and Java Bean component authoring. The Analysis Server answers several questions that have plagued engineering analysis groups for years: l "How can I provide multi-platform access to our legacy software?" l "How do I make our complicated, convoluted codes a little easier for novices to use?" l "Why do I have to spend all day writing input files and parsing output files when I only want a few critical val- ues?" The Analysis Server allows the user to control complex engineering programs through a simple set of commands (e.g. get, set, and execute). This interface is consistent across all Analysis Server components, so users who understand how to manipulate one component can manipulate them all. The result is enhanced user-friendliness without rewriting the original software. Distributed access and ease of use are only the tip of the Analysis Server's capabilities. Its command set can be incor- porated into a client program, which means that other programs can directly access data from Analysis Server com- ponents. An Analysis Server client can transfer data directly from legacy software to an Excel workbook, for example. If the client program has an integration architecture, it is possible to make several previously stand-alone leg- acy programs from geographically distant, hardware distinct machines work together as though modules of a single program.
    [Show full text]
  • Testing and Maintenance of Graphical User Interfaces Valeria Lelli Leitao
    Testing and maintenance of graphical user interfaces Valeria Lelli Leitao To cite this version: Valeria Lelli Leitao. Testing and maintenance of graphical user interfaces. Human-Computer Inter- action [cs.HC]. INSA de Rennes, 2015. English. NNT : 2015ISAR0022. tel-01232388v2 HAL Id: tel-01232388 https://tel.archives-ouvertes.fr/tel-01232388v2 Submitted on 11 Apr 2016 HAL is a multi-disciplinary open access L’archive ouverte pluridisciplinaire HAL, est archive for the deposit and dissemination of sci- destinée au dépôt et à la diffusion de documents entific research documents, whether they are pub- scientifiques de niveau recherche, publiés ou non, lished or not. The documents may come from émanant des établissements d’enseignement et de teaching and research institutions in France or recherche français ou étrangers, des laboratoires abroad, or from public or private research centers. publics ou privés. THÈSE INSA Rennes présentée par sous le sceau de l’Université Européenne de Bretagne Valéria Lelli Leitão Dan- pour obtenir le grade de tas DOCTEUR DE L’INSA DE RENNES ÉCOLE DOCTORALE : MATISSE Spécialité : Informatique LABORATOIRE : IRISA/INRIA Thèse soutenue le 19 Novembre 2015 devant le jury composé de : Testing and Pascale Sébillot Professeur, Universités IRISA/INSA de Rennes / Présidente maintenance of Lydie du Bousquet Professeur d’informatique, Université Joseph Fourier / Rapporteuse Philippe Palanque graphical user Professeur d’informatique, Université Toulouse III / Rapporteur Francois-Xavier Dormoy interfaces Chef de produit senior, Esterel Technologies / Examinateur Benoit Baudry HDR, Chargé de recherche, INRIA Rennes - Bretagne Atlantique / Directeur de thèse Arnaud Blouin Maître de Conférences, INSA Rennes / Co-encadrant de thèse Testing and Maintenance of Graphical User Interfaces Valéria Lelli Leitão Dantas Document protégé par les droits d’auteur Contents Acknowledgements 5 Abstract 7 Résumé en Français 9 1Introduction 19 1.1 Context ...................................
    [Show full text]
  • GUI Ripping: Reverse Engineering of Graphical User Interfaces for Testing
    GUI Ripping: Reverse Engineering of Graphical User Interfaces for Testing Atif Memon Ishan Banerjee, Adithya Nagarajan Department of Computer Science Department of Computer Science and Fraunhofer Center for University of Maryland Experimental Software Engineering College Park, Maryland, USA University of Maryland {ishan, sadithya}@cs.umd.edu College Park, Maryland, USA [email protected] Abstract trols that represent everyday objects such as menus, but- tons, lists, and windows. Recognizing the importance of Graphical user interfaces (GUIs) are important parts of GUIs, software developers are dedicating large parts of the today’s software and their correct execution is required to code to implementing GUIs [12]. The correctness of this ensure the correctness of the overall software. A popular code is essential to the correct execution of the overall soft- technique to detect defects in GUIs is to test them by exe- ware. A popular technique to detect defects in software is cuting test cases and checking the execution results. Test testing [3, 2, 23]. During testing, test cases are created and cases may either be created manually or generated auto- executed on the software. Test cases may either be created matically from a model of the GUI. While manual testing manually by a tester [10, 27, 8] or automatically by using a is unacceptably slow for many applications, our experience model of the software derived from its specifications [20]. with GUI testing has shown that creating a model that can In all our work to date [20, 17, 21, 16, 18, 19, 15, 12, 14], be used for automated test case generation is difficult.
    [Show full text]
  • Using-Designer.Pdf
    Using Designer AEM 6.3 Forms Legal notices For legal notices, see http://help.adobe.com/en_US/legalnotices/index.html. Last updated 4/26/17 Contents Welcome to Designer . 1 About Designer . 1 Using Designer in the SAP environment . 1 Using Designer in different spaces . 2 New features in Designer . 2 Render XFA forms as HTML5 forms . 2 Support for Turkish Lira locale . 2 Support for Japanese Postal barcode . 3 Accessibility Checker . 3 Add document title to the PDF title bar . 3 Support for Hindi language . 3 New features in Designer . 3 Preview your XDP forms in HTML in Designer . 3 Preview your XDP forms in HTML in forms manager . 4 Accessibility Checker . 4 Add document title to the PDF title bar . 4 Where to find documentation, samples, and tutorials . 4 Get started with samples and tutorials . 5 Add calculations to forms . 5 Enhance forms by using scripts . 5 Getting Started . 7 About forms . 7 Interactive forms . 7 Non-interactive forms . 8 Print and fill forms . 8 About form designs . 8 Form design layouts . 9 i Fixed layout . 9 Flowable layout . 9 Parts of a form design . 10 Master pages . 10 Pages . 11 Content areas . 11 Subforms . 11 Tables . 12 Field objects . 12 Boilerplate or static objects . 13 Installing and configuring Designer . 13 Configuring JVM settings . 13 Looking at the workspace . 14 About editors . 14 About palettes . 17 Customizing the workspace . .23 Managing library palettes . 28 Steps to creating a form design . 33 Basic steps to creating a form design . 33 Plan the form design . 33 Create the form design .
    [Show full text]
  • Mapping Guis to Auditory Interfaces
    Mapping GUIs to Auditory Interfaces Elizabeth D. Mynatt and W. Keith Edwards Graphics, Visualization, and Usability Center College of Computing Georgia Institute of Technology Atlanta, GA 3032-0280 [email protected], [email protected] ABSTRACT little trouble accessing standard ASCII terminals. The line- This paper describes work to provide mappings between X- oriented textual output displayed on the screen was stored in based graphical interfaces and auditory interfaces. In our the computer’s framebuffer. An access program could sim- system, dubbed Mercator, this mapping is transparent to ply copy the contents of the framebuffer to a speech synthe- applications. The primary motivation for this work is to sizer, a Braille terminal or a Braille printer. Conversely, the provide accessibility to graphical applications for users who contents of the framebuffer for a graphical interface are sim- are blind or visually impaired. We describe the design of an ple pixel values. To provide access to GUIs, it is necessary to auditory interface which simulates many of the features of intercept application output before it reaches the screen. This graphical interfaces. We then describe the architecture we intercepted application output becomes the basis for an off- have built to model and transform graphical interfaces. screen model of the application interface.The information in Finally, we conclude with some indications of future the off-screen model is then used to create alternative, acces- research for improving our translation mechanisms and for sible interfaces. creating an auditory “desktop” environment. The goal of this work, called the Mercator1 Project, is to pro- KEYWORDS: Auditory interfaces, GUIs, X, visual impair- vide transparent access to X Windows applications for com- ment, multimodal interfaces.
    [Show full text]
  • Automatically Generating High-Quality User Interfaces for Appliances
    Automatically Generating High-Quality User Interfaces for Appliances Jeffrey Nichols December 2006 CMU-HCII-06-109 Human Computer Interaction Institute School of Computer Science Carnegie Mellon University Pittsburgh, Pennsylvania 15213 Thesis Committee: Brad A. Myers, Chair Scott E. Hudson John Zimmerman Dan R. Olsen, Jr., Brigham Young University Submitted in partial fulfillment of the requirements for the degree of Doctor of Philosophy Copyright © 2006 Jeffrey Nichols. All rights reserved. This research was supported in part by the National Science Foundation (through the author’s Graduate Re- search Fellowship and grants IIS-0117658 and IIS-0534349), Microsoft, General Motors, the Pittsburgh Digital Greenhouse, and Intel. Equipment supporting this research was generously donated by Mitsubishi Elec- tric Research Laboratories, VividLogic, Lantronix, Lutron, IBM Canada, Symbol Technologies, Hewlett- Packard, and Lucent. The views and conclusions contained herein are those of the author and should not be interpreted as necessarily representing the official policies or endorsements, either expressed or implied, of any sponsoring party or the U.S. Government. Keywords: Automatic interface generation, aggregate user interfaces, handheld computers, personal digital assistants, mobile phones, home theater, appliances, personal universal con- troller (PUC), user interface description languages (UIDLs), remote controls, multi-modal interfaces, speech recognition, Smart Templates, user interface consistency, personal consis- tency, familiarity ii Automatically Generating High-Quality User Interfaces for Appliances Jeffrey Nichols iii iv Abstract0B In this dissertation, I show that many appliance usability problems can be addressed by mov- ing the user interface from the appliance to a handheld device that the user is already carrying, such as a Personal Digital Assistant (PDA) or mobile phone.
    [Show full text]
  • Day One: Beginner's Guide to Learning Junos
    DAY ONE: BEGINNER’S GUIDE TO LEARNING JUNOS® The Juniper AmbAssADors Are A Diverse set of inDepenDent network engineers, ConsultAnts, AnD ArChiteCts who work in the fielD with Juniper technologies on A DAily bAsis. Their mission is to spreaD the worD About the power AnD sCAlAbility of Juniper’s network offerings. InDeeD, they Are responsible for over A Dozen ONE: DAY Day One books AnD Countless soCiAl meDiA AppeArAnCes, viDeos, AnD trAining sessions. But they hAve Al- DAY ONE: BEGINNER’S GUIDE TO ways wanteD to fill A mAjor gAp in the networking CAnnon AnD Create A true beginner’s guiDe to the most powerful networking OS in the worlD. AnD now they hAve Done it, the AmbAssADor wAy: hAnDs on, to the ® point, anD complete. It’s all here in the Beginner’s Guide to Learning Junos. LEARNING JUNOS BEGINNER’S GUIDE TO LEARING JUNOS LEARING TO GUIDE BEGINNER’S “Whether you are new to Juniper or not, there isn’t a more complete introduction to Junos available. I wish Nine this book was around when I started my network journey years ago. The Ambassador authors bring together so much knowledge and expert field experience that this book is a one-stop-shop to take you from beginner to Junos expert.” Melchior Aelmans, Lead Engineer Cloud Providers, Juniper Networks The Juniper Ambassadors “Nowadays there are many vendors offering similar services and its difficult to learn them all. What network show you how to stand up engineers need is a clear and easy-to-follow guide to assist them in their learning journey.
    [Show full text]
  • Enterprise Governance, Risk and Compliance Security Implementation Guide Release 8.6.6.1000 Part No
    Oracle® Enterprise Governance, Risk and Compliance Security Implementation Guide Release 8.6.6.1000 Part No. E69143-01 February 2016 Oracle Enterprise Governance, Risk and Compliance Security Implementation Guide Part No. E69143-01 Copyright © 2016 Oracle Corporation and/or its affiliates. All rights reserved. Primary Author: David Christie Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners. The 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 software or related documentation is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable. U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are “commercial computer software” or “commercial technical data” pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms set forth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007).
    [Show full text]