DOCSLIB.ORG

A Social Collaborative Distributed Software Development Environment,” Has Been Reviewed in Final Form

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
A Social Collaborative Distributed Software Development Environment,” Has Been Reviewed in Final Form A Social Collaborative Distributed Software Development Environment A Dissertation Presented in Fulfillment of the Requirements for the Degree of Doctor of Philosophy with a Major in Computer Science in the College of Graduate Studies University of Idaho By Hani Ahmad Bani-Salameh August 16, 2011 Major Professor: Dr. Clinton Jeffery Copyright © 2010-2011 Hani Bani-Salameh. All rights reserved. ii Authorization to Submit Dissertation This dissertation of Hani Ahmad Bani-Salameh, submitted for the degree of Doctor of Philosophy with a major in Computer Science and entitled “A Social Collaborative Distributed Software Development Environment,” has been reviewed in final form. Permission, as indicated by the signatures and dates given below, is now granted to submit final copies to the College of Graduate Studies for approval. Major Professor: Date: Dr. Clinton Jeffery Committee member: Date: Dr. Jim Alves-Foss Committee member: Date: Dr. Robert Rinker Committee member: Date: Dr. Barry Willis Department Administrator: Date: Dr. Gregory W. Donohoe Discipline’s College Dean: Date Dr. Larry A. Stauffer Final Approval and Acceptance by the College of Graduate Studies: Date: Dr. Jie Chen iii Abstract Software engineering is usually a team effort. Distributed software development needs real-time collaboration tools that help replicate the benefits of face-to-face meetings and support interaction among team members. Unfortunately, most of the tools that exist have limited capabilities, such as source code editing, and developers face collaboration and communication challenges in working with each other. Over the past decade software researchers have invented various development tools that integrate collaborative features. Unfortunately, most software developers still lack the right means and level of communication to coordinate their work and perform their tasks effectively, particularly in distributed settings. Developers still lack a sense of remote team members’ presence, and in some contexts, such as open source development, they still find it difficult to find appropriate project partners. This draws attention to the need for community integration inside collaborative development environment tools. This dissertation investigates collaboration and communication mechanisms for distributed software development. The research results include solutions to problems that are associated with providing online awareness and presence information, and determine the prospective gains from the use of these solutions. This research contributes the core idea and novel design and implementation techniques for a real-time social collaborative integrated development environment (IDE). It describes the design and implementation of a social collaborative IDE inside a virtual environment named Collaborative Virtual Environment (CVE) where users can interact with each other within a 3D virtual world. A subsystem of CVE called Social Collaborative Integrated Development Environment (SCI) is presented that supports communication and collaboration within a distributed software development community, and integrates community and social features inside the development environment. SCI addresses the communication and collaboration needs in a variety of different phases in a team software development process, unifies the concepts of social networking and collaborative IDE, and integrates presence information and collaborative development tools into a single environment. In addition, this dissertation relates the contributions to previous research and describes directions for future work. This dissertation discusses social networking features that offer a context, and provide activity, and presence information within a development community. A central component of these features is an awareness monitor that shows the team members’ activity, and provides general awareness of projects’ progress and development changes, and makes them easy to track. iv Acknowledgment Every dissertation is a joint effort and mine is no exception. I would like to express my gratitude to all the people who supported this work. It has been a long journey involved with major research challenges and overcoming critical developments obstacles. I would like to thank my major professor, Dr. Clinton Jeffery, for his critical eye and foresight. It has been pleasure learning from his experience and insights for these past six years. Without his early guidance and encouragement, my years as a Ph.D. student would have been far less productive. I thank him for his encouragement, patience, support, and knowledge. I would like to thank my committee members: Dr. Jim Alves-Foss, Dr. Robert Rinker, and Dr. Barry Willis, for their encouragement and constructive criticism about the presented research and the formatting of this dissertation. They have been a strong supporter of my work and they provided invaluable feedback. I would like to thank Mr. Bruce Bolden and every member of the computer science I class from the Summer 2011 session who participated in the evaluation studies. This work would have been much more difficult without them. Finally, thank you also to the corporate and governmental sponsors of this work. This research was supported in part by a grant from the National Science Foundation under agreement number DUE-0402572. In addition, this work was supported in part by the Specialized Information Services Division of the U.S. National Library of Medicine. Hani Bani-Salameh August 16, 2011 v Table of contents Authorization to Submit Dissertation ............................................................................. ii Abstract ............................................................................................................................. iii Acknowledgment .............................................................................................................. iv Table of contents ............................................................................................................... v List of Figures ................................................................................................................... ix List of Tables ................................................................................................................... xii Part I Introduction and Background Research ......................................................... xiii Chapter 1 Introduction..................................................................................................... 1 1.1 Problem Description ........................................................................................................ 2 1.2 Research Hypotheses ....................................................................................................... 3 1.3 Contributions.................................................................................................................... 3 1.4 Organization ..................................................................................................................... 4 1.5 The state of this dissertation ............................................................................................ 5 Chapter 2 Background Research .................................................................................... 6 2.1 The Importance of Collaboration ..................................................................................... 6 2.2 Research Related to Collaborative Software Engineering ............................................... 7 2.2.1 Collaborative Software Systems (Groupware) ......................................................... 7 2.2.2 Collaborative Development Environments ............................................................ 14 2.2.3 Comparison to SCI Tool ........................................................................................ 20 2.3 Summary ........................................................................................................................ 22 Chapter 3 Social Networks ............................................................................................. 23 3.1 Definition of Social Network ......................................................................................... 23 3.2 Social Network Research Advances and Applications .................................................. 24 3.3 Developers’ Social Networks ........................................................................................ 25 3.4 Social Network Examples for Software Development .................................................. 26 3.5 Summary ........................................................................................................................ 28 Part II Primary Contributions (Synchronous and Asynchronous Features) ........... 30 Chapter 4 Synchronous Collaborative IDE System Support ..................................... 31 4.1 Overview of CVE .......................................................................................................... 31 4.2 Overview of ICI ............................................................................................................. 32 4.2.1 Use Scenarios ......................................................................................................... 35 vi 4.3 Design ............................................................................................................................ 35 4.3.1 Collaborative Sessions ..........................................................................................
Load more

Recommended publications
  • Trackdown: Collaborative Writing and Editing of R Markdown (Or Sweave
    Package ‘trackdown’ August 6, 2021 Title Collaborative Writing and Editing of R Markdown (or Sweave) Documents in Google Drive Version 1.0.0 Description Collaborative writing and editing of R Markdown (or Sweave) documents. The lo- cal .Rmd (or .Rnw) is uploaded as a plain-text file to Google Drive. By taking advan- tage of the easily readable Markdown (or LaTeX) syntax and the well-known online interface of- fered by Google Docs, collaborators can easily contribute to the writing and editing process. Af- ter integrating all authors’ contributions, the final document can be downloaded and rendered lo- cally. Depends R (>= 3.5) License GPL-3 Encoding UTF-8 Imports cli (>= 3.0.0), googledrive (> 1.0.1), rmarkdown Suggests covr, devtools, gargle, knitr, pagedown, sodium, testthat (>= 3.0.0), vcr Config/testthat/edition 3 RoxygenNote 7.1.1 VignetteBuilder knitr URL https://github.com/claudiozandonella/trackdown/, https://claudiozandonella.github.io/trackdown/ BugReports https://github.com/claudiozandonella/trackdown/issues NeedsCompilation no Author Emily Kothe [aut] (<https://orcid.org/0000-0003-1210-0554>), Claudio Zandonella Callegher [aut, cre] (<https://orcid.org/0000-0001-7721-6318>), Filippo Gambarota [aut] (<https://orcid.org/0000-0002-6666-1747>), Janosch Linkersdörfer [aut] (<https://orcid.org/0000-0002-1577-1233>), Mathew Ling [aut] (<https://orcid.org/0000-0002-0940-2538>) Maintainer Claudio Zandonella Callegher <[email protected]> Repository CRAN Date/Publication 2021-08-06 18:20:02 UTC 1 2 trackdown-package R topics documented: trackdown-package . .2 download_file . .4 render_file . .4 update_file . .5 upload_file . .6 Index 8 trackdown-package trackdown - R package for improving collaborative writing Description The trackdown package offers a simple solution for collaborative writing and editing of R Mark- down (or Sweave) documents.
    [Show full text]
  • Xp Project Management
    University of Montana ScholarWorks at University of Montana Graduate Student Theses, Dissertations, & Professional Papers Graduate School 2007 XP PROJECT MANAGEMENT Craig William Macholz The University of Montana Follow this and additional works at: https://scholarworks.umt.edu/etd Let us know how access to this document benefits ou.y Recommended Citation Macholz, Craig William, "XP PROJECT MANAGEMENT" (2007). Graduate Student Theses, Dissertations, & Professional Papers. 1201. https://scholarworks.umt.edu/etd/1201 This Thesis is brought to you for free and open access by the Graduate School at ScholarWorks at University of Montana. It has been accepted for inclusion in Graduate Student Theses, Dissertations, & Professional Papers by an authorized administrator of ScholarWorks at University of Montana. For more information, please contact [email protected]. XP PROJECT MANAGEMENT By Craig William Macholz BS in Business Administration, The University of Montana, Missoula, MT, 1997 Thesis presented in partial fulfillment of the requirements for the degree of Master of Science in Computer Science The University of Montana Missoula, MT Autumn 2007 Approved by: Dr. David A. Strobel, Dean Graduate School Dr. Joel Henry Computer Science Dr. Yolanda Reimer Computer Science Dr. Shawn Clouse Business Administration i Macholz, Craig, M.S., December 2007 Computer Science Extreme Programming Project Management Chairperson: Dr. Joel Henry Extreme programming project management examines software development theory, the extreme programming process, and the essentials of standard project management as applied to software projects. The goal of this thesis is to integrate standard software project management practices, where possible, into the extreme programming process. Thus creating a management framework for extreme programming project management that gives the extreme programming managers the management activities and tools to utilize the extreme programming process within a wider range of commercial computing organizations, relationships, and development projects.
    [Show full text]
  • Spacetime Characterization of Real-Time Collaborative Editing Gabriele D’Angelo, Angelo Di Iorio, Stefano Zacchiroli
    Spacetime Characterization of Real-Time Collaborative Editing Gabriele d’Angelo, Angelo Di Iorio, Stefano Zacchiroli To cite this version: Gabriele d’Angelo, Angelo Di Iorio, Stefano Zacchiroli. Spacetime Characterization of Real-Time Collaborative Editing. Proceedings of the ACM on Human-Computer Interaction , Association for Computing Machinery (ACM), 2018, CSCW, 2, pp.1-19. 10.1145/3274310. hal-01882069 HAL Id: hal-01882069 https://hal.inria.fr/hal-01882069 Submitted on 26 Sep 2018 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. 41 Spacetime Characterization of Real-Time Collaborative Editing GABRIELE D’ANGELO, Dept. of Computer Science and Engineering, University of Bologna, Italy ANGELO DI IORIO, Dept. of Computer Science and Engineering, University of Bologna, Italy STEFANO ZACCHIROLI, IRIF, University Paris Diderot & Inria, France Real-Time Collaborative Editing (RTCE) is a popular way of instrumenting cooperative work on documents, in particular on the Web. Little is known in the literature yet about RTCE usage patterns in the real world. In this paper we study how a popular RTCE editor (Etherpad) is used in the wild, digging into the edit histories of a large collection of documents (about 14 000 pads), retrieved from one of the most popular public instances of the platform, hosted by the Wikimedia Foundation.
    [Show full text]
  • The Great Methodologies Debate: Part 1
    ACCESS TO THE EXPERTS The Journal of Information Technology Management December 2001 Vol. 14, No. 12 The Great Methodologies Debate: Part 1 Resolved “Today, a new debate rages: agile software Traditional methodologists development versus rigorous software are a bunch of process- development.” dependent stick-in-the-muds who’d rather produce flawless Jim Highsmith, Guest Editor documentation than a working system that meets business needs. Opening Statement Jim Highsmith 2 Rebuttal Lightweight, er, “agile” Agile Can Scale: Inventing and Reinventing methodologists are a bunch of SCRUM in Five Companies glorified hackers who are going to be in for a heck of a surprise Jeff Sutherland 5 when they try to scale up their “toys” into enterprise-level software. Agile Versus Traditional: Make Love, Not War! Robert L. Glass 12 Business Intelligence Methodologies: Agile with Rigor? Larissa T. Moss 19 Agility with the RUP Philippe Kruchten 27 Extreme Requirements Engineering Larry Wagner 34 Exclusion, Assumptions, and Misinterpretation: Foes of Collaboration Lou Russell 39 Opening Statement by Jim Highsmith In the early 1980s, I participated in rigorous software development. others be able to understand the one round of methodology debate. Agile approaches (Extreme similarities and differences and be Structured analysis and design Programming, Crystal Methods, able to apply the right mix to their champions such as Tom DeMarco, Lean Development, Feature-Driven own organization. Both the SEI and Ed Yourdon, and Tim Lister were Development, Adaptive Software Rational have made wonderful on one side of the debate, while Development, SCRUM, and contributions to software develop- data-driven design aficionados like Dynamic Systems Development ment, but it is important to Ken Orr, Jean-Dominique Warnier, Methodology) populate one camp.
    [Show full text]
  • Devopsuse: Community-Driven Continuous Innovation of Web Information Infrastructures
    DevOpsUse: Community-Driven Continuous Innovation of Web Information Infrastructures Von der Fakultät für Mathematik, Informatik und Naturwissenschaften der Rheinisch-Westfälischen Technischen Hochschule Aachen zur Erlangung des akademischen Grades eines Doktors der Naturwissenschaften genehmigte Dissertation vorgelegt von Diplom-Medieninformatiker István Koren aus Budapest, Ungarn Berichter: Universitätsprofessor Dr. rer. pol. Matthias Jarke Universitätsprofessor Dr.-Ing. Günther Schuh Privatdozent Dr. rer. nat. Ralf Klamma Tag der mündlichen Prüfung: 8. Mai 2020 Diese Dissertation ist auf den Internetseiten der Universitätsbibliothek online verfügbar. ii Abstract Since its invention in 1989, the only reliable factor on the Web has been its continuous change and diffusion into more and more application areas. The evolution was shaped by an interplay of new technologies on the one hand, and innovative application ideas from communities on the other. At a technological scale, alternation between vastly distributed and centralized architectures can be observed. The current challenges caused by the ongoing digital transformation are changing workplace settings and the adoption of the Internet of Things in industrial use cases, as for example in the context of Industry 4.0. On the Web, new technologies and device types sprawl together with new communication protocols and revised application programming interfaces (APIs). This inhibits the demanded rapid innovation cycles and creates a disruptive and unstable environment in which the requirements of endless communities must be met. Information systems infrastructure, while only partially visible and thus hard to grasp, has a strong influence on user practices. Therefore, the aim of this thesis is to stabilize the dichotomies apparent in the Web by means of an agile information systems development methodology.
    [Show full text]
  • Solution Snapshot
    Solution Snapshot Mainsoft and the System z Business Benefits of Porting .NET Apps to the Mainframe By Tony Lock The Sageza Group, Inc. August 2006 The Sageza Group, Inc. 32108 Alvarado Blvd #354 Union City, CA 94587 510·675·0700 fax 650·649·2302 sageza.com London +44 (0) 20·7900·2819 [email protected] Milan +39 02·9544·1646 Mainsoft and the System z ABSTRACT There are two major platforms that today dominate the development of enterprise applications, namely J2EE and Microsoft .NET. Both of these application development environments have attracted large numbers of organizations, and each has its own attractions and limitations. For organizations that have selected Microsoft .NET for application development, the choice of server platform has, until recently, been limited to Microsoft's Windows Server. However, many organizations are now looking to consolidate their server infrastructures to a limited set of platforms, primarily in order to enhance operational security and to minimize the cost of service delivery. The software solutions provided by Mainsoft Corporation now offer enterprise customers the choice of running applications developed using Microsoft .NET on the most secure and highly available server platform available, namely IBM's System z, known to one and all as the mainframe. Mainsoft’s software enables Microsoft .NET applications to run as 100% Java bytecode on a mainframe server. The benefits for organizations deploying applications in this way are many and increasingly desirable. The benefits provided include the ability for experienced .NET developers to continue building and maintaining enterprise applications in the existing environment using the tools with which they are familiar but allowing the organization to deploy said applications in the most robust and secure server platform available, the mainframe.
    [Show full text]
  • Multi-Factor Analysis of Pair Programming Based on PSP
    I S S N 2 2 7 7 - 3 0 6 1 V o l u m e 1 5 N u m b e r 0 4 INTERNATIONAL JOURNAL OF COMPUTERS & TECHNOLOGY Multi-factor analysis of pair programming based on PSP methodology Nabiollah Bayatmoghadam1 (M.S), Ashkan Sami (Ph.D.)2 1Department of Computer Science, Engineering, Shiraz University Email: [email protected] 2Department of Computer Science, Engineering, Shiraz University ABSTRACT In regard with designing software, users play key role. In order to design software, it is necessary to observe standard principles of designation, using templates and using modern methods. Over the decades, using development methods, XP and one of the XP methodologies of paired programming used to design software. These methods have been designed for purpose of enhancing quality of product and rapidresponse to need of market and customer and overcoming weaknesses of traditional methods based on long-term programming and waterfall method. Therefore, every programmer and developer can pass a series of processes for constructing computer software. The processes can be changed daily and efficient processes maynot be effective and useful; although they can be considered as process. The main objective of the present study is multi-factor analysis of pair programming based on PSP methodology. Practical and analytical methodand two PSP methods have been applied for investigations. Key words: software engineering, XP, pair programming, PSP methodology, multi-factor analysis INTRODUCTION In designing software, users play key role. In order to design software, it is necessary to observe standard principles of designation and using templates and using modern technologies.
    [Show full text]
  • ENOVIA Portal Solutions V5.10 Enhances Collaborative Innovation
    Software Announcement October 29, 2002 ENOVIA Portal Solutions V5.10 Enhances Collaborative Innovation Overview • All V4 server-based functions are available with the V5 server. At a Glance ENOVIA Portal Solutions is a • Together these products serve as comprehensive set of scalable ENOVIA Portal Solutions V5.10 the enterprise window to all Web-based, Windows and UNIX delivers new and enhanced product development-related products that enhances collaborative functions: information and support sharing innovation during the product life throughout all enterprise • cycle. Improved preparation of design processes. review data With ENOVIA Portal Solutions, you ENOVIA DMU products deliver • Enhanced performance, can: advanced visualization, analysis, and especially loading large • Propagate and share 2D and 3D simulation for CATIA and non-CATIA mock-ups and clash analysis product data and critical product data. They range from entry-level with code optimization and development information product viewing and collaborative wider use of SMP hardware services (such as design throughout the extended • Enhanced GUI for ease of use enterprise conferencing, markup, analysis, and annotations) to high-end, virtual • • Improved support for clash Access ENOVIA data as well as reality-based digital product management and resolution data from other enterprise synthesis, including human processes information systems, including ergonomic studies, assembly and CAD, product data management disassembly simulations, and • Kinematics data in ENOVIAVPM (PDM), legacy
    [Show full text]
  • More Than Writing Text: Multiplicity in Collaborative Academic Writing
    More Than Writing Text: Multiplicity in Collaborative Academic Writing Ida Larsen-Ledet Ph.D. Thesis Department of Computer Science Aarhus University Denmark More Than Writing Text: Multiplicity in Collaborative Academic Writing A Thesis Presented to the Faculty of Natural Sciences of Aarhus University in Partial Fulfillment of the Requirements for the Ph.D. Degree. by Ida Larsen-Ledet November 2, 2020 Abstract This thesis explores collaborative academic writing with a focus on how it is medi- ated by multiple technologies. The thesis presents findings from two empirical stud- ies with university students and researchers: The first combined semi-structured interviews with visualizations of document editing activity to explore transitions through co-writers’ artifact ecologies along with co-writers’ motivations for per- forming these transitions. The second study was a three-stage co-design workshop series that progressed from dialog through ideation to exploration of a prototype for a shared editor that was based on the participants’ proposed features and designs. The contribution from the second study to this thesis is the analysis of participants’ viewpoints and ideas. The analyses of these findings contribute a characterization of co-writers’ practical and social motivations for using multiple tools in their collaborations, and the chal- lenges this poses for sharing and adressing the work. Multiplicity is also addressed in terms of co-writers bringing multiple and diverse needs and preferences into the writing, and how these may be approached in efforts to design and improve support for collaborative writing. Additionally, the notion of text function is introduced to describe the text’s role as a mediator of the writing.
    [Show full text]
  • De-Risking Government Technology: Federal Agency Field Guide
    De-risking Government Technology Federal Agency Field Guide September 2020 2 DE-RISKING GOVERNMENT TECHNOLOGY Acknowledgements Numerous contributors across GSA made this work possible. We’d like to thank: Project Team Mark Hopson Randy Hart Waldo Jaquith Igor Korenfeld Vicki McFadden Rebecca Refoy Alicia Rouault With Support From Christine Bath, 18F Design Heather Battaglia, 18F Engineering Kristina Britt, TTS outreach Ron Bronson, 18F Design Will Cahoe, 10x Ryan Johnson, 18F Design Nico Papafil, 10x Steven Reilly, 18F Engineering Dahianna Salazar Foreman, TTS outreach 18F Writing Lab Office of Strategic Communications Office of General Counsel TTS Front Office TTS Communications 4 DE-RISKING GOVERNMENT TECHNOLOGY 5 TABLE OF CONTENTS 01 Introduction 6 03 Deciding what to buy 60 About the editors 7 Conduct Modern Market Research 61 Structure of this handbook 8 Use the Agile contract format to procure Agile software 75 development services Basic principles of modern software design 9 Use time and material contract types for custom Agile software 83 development services 02 Planning 20 Evaluate contractor proposals based on industry best practices 89 Assign dedicated and empowered product owners to lead 21 development efforts 04 Doing the work 102 Involve end users early and often in software development efforts 24 Host an effective post-award kick-off meeting to energize 103 Consider tradeoffs in build-or-buy decisions, taking all factors 26 folks for the work to come into consideration Oversee Agile projects by measuring end user outcomes
    [Show full text]
  • Use of Github As a Platform for Open Collaboration on Text Documents Justin Longo Tanya M
    Use of GitHub as a Platform for Open Collaboration on Text Documents Justin Longo Tanya M. Kelley University of Regina Arizona State University Johnson-Shoyama Graduate School of Public Policy School of Public Affairs 3737 Wascana Parkway 411 N. Central Avenue, Suite 400 Regina, SK, Canada S4S 0A2 Phoenix AZ 85004-0687 306-585-5460 602-496-0457 [email protected] [email protected] ABSTRACT provides a platform for social collaboration on non-code artifacts. Recently, researchers are paying attention to the use of the As the uses and users of GitHub move beyond its core community software development and code-hosting web service GitHub for of developers, the present and potential impact on fields such as other collaborative purposes, including a class of activity referred social knowledge creation, open science, open collaboration and to as document, text, or prose collaboration. These alternative uses open governance warrants consideration of the conditions under of GitHub as a platform for sharing non-code artifacts represent which GitHub can facilitate collaboration in non-code domains. an important modification in the practice of open collaboration. Other open access platforms for collaboration certainly exist, We survey cases where GitHub has been used to facilitate including wikis, synchronous co-editing platforms like Google collaboration on non-code outputs, identify its strengths and docs, and centralized file sharing repositories like SharePoint. weaknesses when used in this mode, and propose conditions for However, GitHub includes unique features such as built-in social successful collaborations on co-created text documents. networking functions [6], back-end data capture and reporting [3], and principles of distributed version control and openness by Categories and Subject Descriptors virtue of the underlying Git architecture.
    [Show full text]
  • Using GIS Technology with Linux
    Using Geographic Information System Technology With Linux ® An ESRI White Paper • June 2002 ESRI 380 New York St., Redlands, CA 92373-8100, USA • TEL 909-793-2853 • FAX 909-793-5953 • E-MAIL [email protected] • WEB www.esri.com Copyright © 2002 ESRI All rights reserved. Printed in the United States of America. The information contained in this document is the exclusive property of ESRI. This work is protected under United States copyright law and other international copyright treaties and conventions. No part of this work may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying and recording, or by any information storage or retrieval system, except as expressly permitted in writing by ESRI. All requests should be sent to Attention: Contracts Manager, ESRI, 380 New York Street, Redlands, CA 92373-8100, USA. The information contained in this document is subject to change without notice. U.S. GOVERNMENT RESTRICTED/LIMITED RIGHTS Any software, documentation, and/or data delivered hereunder is subject to the terms of the License Agreement. In no event shall the U.S. Government acquire greater than RESTRICTED/LIMITED RIGHTS. At a minimum, use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in FAR §52.227-14 Alternates I, II, and III (JUN 1987); FAR §52.227-19 (JUN 1987) and/or FAR §12.211/12.212 (Commercial Technical Data/Computer Software); and DFARS §252.227-7015 (NOV 1995) (Technical Data) and/or DFARS §227.7202 (Computer Software), as applicable. Contractor/Manufacturer is ESRI, 380 New York Street, Redlands, CA 92373- 8100, USA.
    [Show full text]