DOCSLIB.ORG

Architecture Layers Document

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Architecture Layers Document CTMS/CTIS INTEGRATION Contract Routing No. 04 HAA 00063 Architecture Layers Version 1.1 Approved By Robert Wycoff CDOT ITS Office Signature: ___________________________ Date: _______________________________ John Williams CDOT ITS Office Signature: ___________________________ Date: _______________________________ Prepared By: CTMS/CTIS Version: 1.1 Architecture Layers Date: 08 Mar 2004 Revision History Date Version Description Author 08-Mar-2004 0.1 First Draft Jason Westra Sachin Saindane 27-Apr-04 0.2 Scheduler and Communications are Jason Westra services, not layers. Added Delegate Layer. 11-May-04 0.3 Added Notifications service and Services Jason Westra Catalog 21-May-04 0.4 Added New Architecture Drawing Sachin Saindane 07-March-05 1.1 Added more depth around layers and Jason Westra guidelines Confidential ©EnRoute Traffic Systems, Inc. Page 2 of 17 CTMS/CTIS Version: 1.1 Architecture Layers Date: 08 Mar 2004 Table of Contents i. Executive Summary 5 1.Introduction 6 1.1 Purpose 6 1.2 Scope 6 1.3 Audience 6 1.4 References 6 2. Logical Architecture Reference Model 7 2.1 Architectural Layers 7 3. Application Layer 9 3.1 Client Layer 10 3.2 Delegate Layer 11 3.3 Messaging Layer 11 3.4 Services Layer 12 4. Application Support Layer 13 5. External Services Layer 14 6. Platform Services Layer 15 7. Tiers 16 7.1 Client Tier 16 7.2 Presentation Tier 16 7.3 Business Tier 16 7.4 Integration Tier 17 7.5 Resource Tier 17 7.6 Achieving Deployment Agility 17 Confidential ©EnRoute Traffic Systems, Inc. Page 3 of 17 CTMS/CTIS Version: 1.1 Architecture Layers Date: 08 Mar 2004 Table of Figures Figure 1: A Four-Layer Organizational Structure For Application Components ..........................................................7 Figure 2: Conceptual Application Layer .......................................................................................................................9 Figure 3: CTMS Application Layer.............................................................................................................................10 Table 1: Application Support Layer ............................................................................................................................13 Table 2: External Services Layer.................................................................................................................................15 Table 3: Platform Services Layer ................................................................................................................................16 Confidential ©EnRoute Traffic Systems, Inc. Page 4 of 17 CTMS/CTIS Version: 1.1 Architecture Layers Date: 08 Mar 2004 Architecture Layers i. Executive Summary This particular document describes the roles and responsibilities of the various layers that are central to the CTMS/CTIS architecture and catalogs the services available to the architecture. Confidential ©EnRoute Traffic Systems, Inc. Page 5 of 17 CTMS/CTIS Version: 1.1 Architecture Layers Date: 08 Mar 2004 1. Introduction This document describes the application architecture of CTMS and the various roles and responsibilities of each layer that contributes to the overall CTMS/CTIS software architecture. 1.1 Purpose The purpose of this document is: • To supplement the technical information provided in the Messaging Architecture Assessment Document. • To capture and convey the significant messaging architectural issues and decisions which have been made during meetings and discussions. 1.2 Scope The scope of this document is the CTMS/CTIS system. 1.3 Audience This document describes the underlying messaging architecture within the core CTMS architecture from various perspectives. Since most sections are technical in nature, the document is focused towards technical managers, technical architects and the software development team. 1.4 References The following references were either used in the creation of this document or may be used to supplement the detailed descriptions of the CTMS/CTIS system: • The CTMS/CTIS Architecture Assessment Document. • The CTMS/CTIS Messaging Architecture Assessment Document. • Design Patterns: Elements of Reusable Object-Oriented Software - Gamma, Helm, Johnson, Vlissides • Core J2EE Patterns: Best Practices and Design Strategies – Alur,Crupi, Malks Confidential ©EnRoute Traffic Systems, Inc. Page 6 of 17 CTMS/CTIS Version: 1.1 Architecture Layers Date: 08 Mar 2004 2. Logical Architecture Reference Model The logical architecture makes it possible to communicate the design of the system with both technical and business audiences. It covers the structure, guidelines, and capabilities of the system without getting mired in the details of the technical implementation of the architecture such as protocols and interfaces. The logical architecture organizes broad definitions into categories and organizes them in such a way as to allow the implementation to be carried out effectively and efficiently. It provides a way to help determine build vs. buy for each category whether at a coarse-grained or granular level. For instance, it can help make decisions like whether or not to implement a whole subsystem with COTS (e.g., an ERP solution) or just a few services in the subsystem with a specific OTS (commercial off the shelf) product. 2.1 Architectural Layers Application services may be organized into layers, each representing a gross classification of the degree to which services in the layer have to do with business or technology. Services in higher layers have more to do with business and are most likely custom built while services in lower layers tend to be more technical and are often purchased rather than built. Figure 1, below, illustrates a four-layer classification scheme with Application, Application Support, External Services and Platform Services layers. The foundation of the application architecture is the Platform Services that represent the raw technology upon which a solution is built. Examples include operating systems, computer and networking hardware, operating systems, network operating systems, interface cards, and communication protocols. Provides the user interface, business logic, and process flow custom-built for the application. Application Layer Example: UI, images, and services Provides common, but custom services to the Application Layer that function as adapters/ wrappers to External Services. Application Support Layer Example: A wrapper around SNMP protocols or a J2CA Connector to a legacy system Provides third-party APIs and components that the application must interface with. External Services Layer Example: DB, Java Mail API, Java Comm APIs Network, operation systems, and hardware. Platform Services Layer Example; Routers, Unix on Solaris, firewalls Figure 1: A Four-Layer Organizational Structure For Application Components The External Services Layer represents purchased or pre-existing software with which your system must integrate. Examples include database management systems, messaging services, application monitoring services, e-mail, and legacy systems. These services are purchased or pre-existing and rely on underlying Platform Services Layer in order to operate. The Application Support Layer sits above the External Services layer. Services in this layer may include application security (e.g., authentication and authorization), object identity and naming, exception and event handling, logging, and transaction management. These services form the common, architectural plumbing of your enterprise infrastructure and are reusable across multiple applications. In addition to the services just mentioned, perhaps one of the most powerful services in this layer is the adapter service that can be used to encapsulate access to external and platform services, insulating Application Layer components from technology changes. Confidential ©EnRoute Traffic Systems, Inc. Page 7 of 17 CTMS/CTIS Version: 1.1 Architecture Layers Date: 08 Mar 2004 To understand how each layer provides insulation for the next, consider this example. Multiple components in the Application Layer require authentication and authorization services. Users and permissions are stored in a relational database. The components requiring security services call a Service Adaptor interface that exposes methods like “login(username, password)”, “logout(user)”, and ‘hasPermission(permission, user)”. Depending on the request, the Service Adaptor might query the relational database using SQL to validate login credentials or to see if the user has the permission specified. As the company grows, an enterprise security provider is chosen and all applications must now conform to. It happens to use an LDAP Directory Server for the storage of users and permissions. The Service Adaptor simply needs to change its implementation to make LDAP directory calls now instead of SQL queries. Applications that used the Service Adaptor did not have to change. Unfortunately, applications in the company that did not use the Service Adaptor have to change each “touch point” in the system to conform to the new LDAP directory APIs. At the top of the architecture stack, the Application Layer represents services unique to a particular system—its presentation, business logic and data storage logic. These are nearly always custom built components because they have to do with a specific business problem. Adherence to layering rules increases the technical agility of a system in that underlying technology can be replaced with minimal, if any, impact on the operation of higher-level services.
Load more

Recommended publications
  • OES 2 SP3: Novell CIFS for Linux Administration Guide 9.2.1 Mapping Drives from a Windows 2000 Or XP Client
    www.novell.com/documentation Novell CIFS Administration Guide Open Enterprise Server 2 SP3 May 03, 2013 Legal Notices Novell, Inc., makes no representations or warranties with respect to the contents or use of this documentation, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc., reserves the right to revise this publication and to make changes to its content, at any time, without obligation to notify any person or entity of such revisions or changes. Further, Novell, Inc., makes no representations or warranties with respect to any software, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc., reserves the right to make changes to any and all parts of Novell software, at any time, without any obligation to notify any person or entity of such changes. Any products or technical information provided under this Agreement may be subject to U.S. export controls and the trade laws of other countries. You agree to comply with all export control regulations and to obtain any required licenses or classification to export, re-export or import deliverables. You agree not to export or re-export to entities on the current U.S. export exclusion lists or to any embargoed or terrorist countries as specified in the U.S. export laws. You agree to not use deliverables for prohibited nuclear, missile, or chemical biological weaponry end uses. See the Novell International Trade Service Web page (http://www.novell.com/info/exports/) for more information on exporting Novell software.
    [Show full text]
  • Shared Resource Matrix Methodology: an Approach to Identifying Storage and Timing Channels
    Shared Resource Matrix Methodology: An Approach to Identifying Storage and Timing Channels RICHARD A. KEMMERER University of California, Santa Barbara Recognizing and dealing with storage and timing channels when performing the security analysis of a computer system is an elusive task. Methods for discovering and dealing with these channels have mostly been informal, and formal methods have been restricted to a particular specification language. A methodology for discovering storage and timing channels that can be used through all phases of the software life cycle to increase confidence that all channels have been identified is presented. The methodology is presented and applied to an example system having three different descriptions: English, formal specification, and high-order language implementation. Categories and Subject Descriptors: C.2.0 [Computer-Communication Networks]: General--se- curity and protection; D.4.6 ]Operating Systems]: Security and Protection--information flow controls General Terms: Security Additional Key Words and Phrases: Protection, confinement, flow analysis, covert channels, storage channels, timing channels, validation 1. INTRODUCTION When performing a security analysis of a system, both overt and covert channels of the system must be considered. Overt channels use the system's protected data objects to transfer information. That is, one subject writes into a data object and another subject reads from the object. Subjects in this context are not only active users, but are also processes and procedures acting on behalf of the user. The channels, such as buffers, files, and I/O devices, are overt because the entity used to hold the information is a data object; that is, it is an object that is normally viewed as a data container.
    [Show full text]
  • Shared Resource
    Shared resource In computing, a shared resource, or network share, is a computer resource made available from one host to other hosts on a computer network.[1][2] It is a device or piece of information on a computer that can be remotely accessed from another computer transparently as if it were a resource in the local machine. Network sharing is made possible by inter-process communication over the network.[2][3] Some examples of shareable resources are computer programs, data, storage devices, and printers. E.g. shared file access (also known as disk sharing and folder sharing), shared printer access, shared scanner access, etc. The shared resource is called a shared disk, shared folder or shared document The term file sharing traditionally means shared file access, especially in the context of operating systems and LAN and Intranet services, for example in Microsoft Windows documentation.[4] Though, as BitTorrent and similar applications became available in the early 2000s, the term file sharing increasingly has become associated with peer-to-peer file sharing over the Internet. Contents Common file systems and protocols Naming convention and mapping Security issues Workgroup topology or centralized server Comparison to file transfer Comparison to file synchronization See also References Common file systems and protocols Shared file and printer access require an operating system on the client that supports access to resources on a server, an operating system on the server that supports access to its resources from a client, and an application layer (in the four or five layer TCP/IP reference model) file sharing protocol and transport layer protocol to provide that shared access.
    [Show full text]
  • Resource Management in Multimedia Networked Systems
    University of Pennsylvania ScholarlyCommons Technical Reports (CIS) Department of Computer & Information Science May 1994 Resource Management in Multimedia Networked Systems Klara Nahrstedt University of Pennsylvania Ralf Steinmetz University of Pennsylvania Follow this and additional works at: https://repository.upenn.edu/cis_reports Recommended Citation Klara Nahrstedt and Ralf Steinmetz, "Resource Management in Multimedia Networked Systems ", . May 1994. University of Pennsylvania Department of Computer and Information Science Technical Report No. MS-CIS-94-29. This paper is posted at ScholarlyCommons. https://repository.upenn.edu/cis_reports/331 For more information, please contact [email protected]. Resource Management in Multimedia Networked Systems Abstract Error-free multimedia data processing and communication includes providing guaranteed services such as the colloquial telephone. A set of problems have to be solved and handled in the control-management level of the host and underlying network architectures. We discuss in this paper 'resource management' at the host and network level, and their cooperation to achieve global guaranteed transmission and presentation services, which means end-to-end guarantees. The emphasize is on 'network resources' (e.g., bandwidth, buffer space) and 'host resources' (e.g., CPU processing time) which need to be controlled in order to satisfy the Quality of Service (QoS) requirements set by the users of the multimedia networked system. The control of the specified esourr ces involves three actions: (1) properly allocate resources (end-to-end) during the multimedia call establishment, so that traffic can flow according to the QoS specification; (2) control resource allocation during the multimedia transmission; (3) adapt to changes when degradation of system components occurs.
    [Show full text]
  • Novell Cluster Services,. for Linux. and Netware
    Novell Cluster Services,. for Linux. and NetWare. ROB BASTIAANSEN SANDER VAN VUGT Novell PRESS. Novell. Published by Pearson Education, Inc. 800 East 96th Street, Indianapolis, Indiana 46240 USA Table of Contents Introduction 1 CHAPTER 1: Introduction to Clustering and High Availability 5 Novell Cluster Services Defined 5 Shared Disk Access 6 Secondary IP Addresses 7 Clustering Terminology 8 High-Availability Solutions Overview 12 Novell Cluster Services 12 Business Continuity Clustering 13 PolyServe Matrix Server 15 Heartbeat Subsystem for High-Availability Linux 16 When Not to Cluster Applications 16 Availability Defined 18 High Availability Defined 18 Calculating Average Downtime 21 Avoiding Downtime 22 Hardware 22 Environment 23 Software 23 Procedures 24 Novell Cluster Services Requirements 24 Hardware Requirements 24 Software Requirements 26 CHAPTER 2: Examining Novell Cluster Services Architecture 27 Novell Cluster Services Objects and Modules 27 Cluster eDirectory Objects 28 Cluster Modules 31 IH Novell Cluster Services for Linux and NetWare Heartbeats, Epoch Numbers, and the Split Brain Detector 35 Removing a Failing Slave Node 36 Removing a Failed Master Node 37 Summary 37 CHAPTER 3: Clustering Design 39 Cluster Design Guidelines 39 How Many Nodes to Choose 39 Using a Heartbeat LAN or Not 40 Use NIC Teaming 41 Choosing Storage Methods 42 Mirror the Split Brain Detector Partition 48 Selecting Applications to Run in a Cluster 48 eDirectory Cluster Guidelines 50 Creating a Failover Matrix 52 Application-Specific Design Guidelines
    [Show full text]
  • Novell® Platespin® Recon 3.7.4 User Guide 5.6.4 Printing and Exporting Reports
    www.novell.com/documentation User Guide Novell® PlateSpin® Recon 3.7.4 September 2012 Legal Notices Novell, Inc., makes no representations or warranties with respect to the contents or use of this documentation, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc., reserves the right to revise this publication and to make changes to its content, at any time, without obligation to notify any person or entity of such revisions or changes. Further, Novell, Inc., makes no representations or warranties with respect to any software, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc., reserves the right to make changes to any and all parts of Novell software, at any time, without any obligation to notify any person or entity of such changes. Any products or technical information provided under this Agreement may be subject to U.S. export controls and the trade laws of other countries. You agree to comply with all export control regulations and to obtain any required licenses or classification to export, re-export or import deliverables. You agree not to export or re-export to entities on the current U.S. export exclusion lists or to any embargoed or terrorist countries as specified in the U.S. export laws. You agree to not use deliverables for prohibited nuclear, missile, or chemical biological weaponry end uses. See the Novell International Trade Services Web page (http://www.novell.com/info/exports/) for more information on exporting Novell software.
    [Show full text]
  • Characterizing Peer-Level Performance of Bittorrent
    Characterizing Peer-level Performance of BitTorrent DRP Report Amir H. Rasti ABSTRACT 1. INTRODUCTION BitTorrent is one of the most popular Peer-to-Peer During the past few years, peer-to-peer appli- (P2P) content distribution applications over the cations have become very popular on the In- Internet that significantly contributes in network ternet. BitTorrent in one of the most popu- traffic. lar peer-to-peer applications providing scalable peer-to-peer content distribution over the In- In BitTorrent, a file is divided into segments ternet. Some recent studies [8] have shown that and participating peers contribute their outgoing BitTorrent is accountable for approximately bandwidth by providing their available segments 35% of the Internet traffic. BitTorrent is a to other peers while obtaining their missing peers scalable peer-to-peer content distribution sys- from others. Characterization of BitTorrent is use- tem that enables one-to-many distribution of ful in determining its performance bottlenecks as large files without requiring a large access link well as its impact on the network. bandwidth at the source. Similar to other peer- In this study, we try to address the following two to-peer systems, it uses resources of participat- key questions through measurement: (i) What are ing peers to increase the capacity of the system. the main factors that affect observed performance The main shared resource in BitTorrent is the by individual peers in BitTorrent?, and (ii) What up-link bandwidth of individual peers. The file are the contributions of these factors on the per- being distributed is divided into a large number formance of individual peers? To address these of segments.
    [Show full text]
  • Server I/O Networks Past, Present, and Future Renato John Recio Chief Architect, IBM Eserver I/O IBM Systems Group, Austin, Texas [email protected]
    Server I/O Networks Past, Present, and Future Renato John Recio Chief Architect, IBM eServer I/O IBM Systems Group, Austin, Texas [email protected] Abstract • Low latency - the total time required to transfer the first bit of a message from the local application to the remote appli- Enterprise and technical customers place a diverse set of cation, including the transit times spent in intermediate requirements on server I/O networks. In the past, no single switches and I/O adapters. network type has been able to satisfy all of these requirements. As • High throughput - the number of small block transactions a result several fabric types evolved and several interconnects performed per second. The size and rate of small block I/O emerged to satisfy a subset of the requirements. Recently several depends on the workload and fabric type. A first level technologies have emerged that enable a single interconnect to be approximation of the I/O block size and I/O throughput rates required for various I/O workloads can be found in used as more than one fabric type. This paper will describe the “I/O Workload Characteristics of Modern Servers” [4]. requirements customers place on server I/O networks; the various • High bandwidth - the number of bytes per second sup- fabric types and interconnects that have been used to satisfy those ported by the network. Typically, used to gauge perfor- requirements; the technologies that are enabling network mance for large block data transfers. Peek bandwidth convergence; and how these new technologies are being deployed describes the bandwidth provided by a given link; whereas on various network families.
    [Show full text]
  • NFS Gateway for Netware 6 Administration Guide October 22, 2003
    Novell Confidential Manual (99a) 11 September 2003 Novell * NFS Gateway for NetWare® 6 www.novell.com ADMINISTRATION GUIDE October 22, 2003 Novell Confidential Manual (99a) 11 September 2003 Legal Notices Novell, Inc. makes no representations or warranties with respect to the contents or use of this documentation, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc. reserves the right to revise this publication and to make changes to its content, at any time, without obligation to notify any person or entity of such revisions or changes. Further, Novell, Inc. makes no representations or warranties with respect to any software, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc. reserves the right to make changes to any and all parts of Novell software, at any time, without any obligation to notify any person or entity of such changes. You may not export or re-export this product in violation of any applicable laws or regulations including, without limitation, U.S. export regulations or the laws of the country in which you reside. Copyright © 2003 Novell, Inc. All rights reserved. No part of this publication may be reproduced, photocopied, stored on a retrieval system, or transmitted without the express written consent of the publisher. U.S. Patent No. 5,157,663; 5,349,642; 5,455,932; 5,553,139; 5,553,143; 5,572,528; 5,594,863; 5,608,903;5,633,931; 5,652,859; 5,671,414;
    [Show full text]
  • Casual Resource Sharing with Shared Virtual Folders
    MASTER THESIS IN COMPUTER SCIENCE Casual Resource Sharing with Shared Virtual Folders Siri Birgitte Uldal June 15th, 2007 FACULTY OF SCIENCE Department of Computer Science University of Tromsø, N-9037 Tromsø Casual Resource Sharing with Shared Virtual Folders Siri Birgitte Uldal June 15th, 2007 ___________________ University of Tromsø 2007 Abstract Proliferation of wireless networks has been a major trigger behind increased mobility of computing devices. Along with increased mobility come requests for ad-hoc exchange of resources between computing devices as an extension of humans interacting. We termed it casual resource sharing where resources in this thesis have been narrowed down to files only. We have named our casual resource sharing model for shared virtual folders (SVF). SVFs can be looked upon as a common repository much in the same way as the tuplespace model. The SVF members perceive the repository similarly to a common file directory on a server, while in reality all participating devices stores their own contribution of files. All types of files could be added to the repository and shared. To become a SVF member one needs to be invited by another member or initiate a SVF oneself. All members are free to withdraw their SVF membership whenever they wish. They are also free to log on to the SVF and log out as they please. The SVF cease to exist when the last member has drawn his membership. The SVF implements a simple versioning detection system to alert members when a file has been modified by another member. Feasibility of the model is demonstrated in a prototype implementation based on Java and the JXTA middleware, a peer-to-peer (P2P) infrastructure middleware supporting the Internet protocol.
    [Show full text]
  • A Pattern Language for Designing Application-Level Communication Protocols and the Improvement of Computer Science Education Through Cloud Computing
    Utah State University DigitalCommons@USU All Graduate Theses and Dissertations Graduate Studies 5-2017 A Pattern Language for Designing Application-Level Communication Protocols and the Improvement of Computer Science Education through Cloud Computing Jorge Edison Lascano Utah State University Follow this and additional works at: https://digitalcommons.usu.edu/etd Part of the Computer Sciences Commons Recommended Citation Lascano, Jorge Edison, "A Pattern Language for Designing Application-Level Communication Protocols and the Improvement of Computer Science Education through Cloud Computing" (2017). All Graduate Theses and Dissertations. 6547. https://digitalcommons.usu.edu/etd/6547 This Dissertation is brought to you for free and open access by the Graduate Studies at DigitalCommons@USU. It has been accepted for inclusion in All Graduate Theses and Dissertations by an authorized administrator of DigitalCommons@USU. For more information, please contact [email protected]. A PATTERN LANGUAGE FOR DESIGNING APPLICATION-LEVEL COMMUNICATION PROTOCOLS AND THE IMPROVEMENT OF COMPUTER SCIENCE EDUCATION THROUGH CLOUD COMPUTING by Jorge Edison Lascano A dissertation submitted in partial fulfillment of the requirements for the degree of DOCTOR OF PHILOSOPHY in Computer Science Approved: ______________________ ____________________ Stephen W. Clyde, Ph.D. Curtis Dyreson, Ph.D. Major Professor Committee Member ______________________ ____________________ Haitao Wang, Ph.D. Young-Woo Kwon, Ph.D. Committee Member Committee Member ______________________ ____________________ Luis Gordillo, Ph.D. Mark R. McLellan, Ph.D. Committee Member Vice President for Research and Dean of the School of Graduate Studies UTAH STATE UNIVERSITY Logan, Utah 2017 ii Copyright © Jorge Edison Lascano 2017 All Rights Reserved iii ABSTRACT A Pattern Language for Designing Application-Level Communication Protocols and the Improvement of Computer Science Education through Cloud Computing by Jorge Edison Lascano, Doctor of Philosophy Utah State University, 2017 Major Professor: Stephen W.
    [Show full text]
  • Security and Resource Sharing in an Nt Environment
    84-10-51 DATA SECURITY MANAGEMENT SECURITY AND RESOURCE SHARING IN AN NT ENVIRONMENT Gilbert Held INSIDE Overview; Share Creation; Setting Permissions; Multiple Identities; Considering Subfolders; Operational Control Because an understanding of the method by which shares are created fa- cilitates an understanding of different levels of data security associated with resource sharing, this article examines in detail the creation of a shared folder on one computer and its access via another computer. In doing so, this article references a series of screen images that illustrate the actual use of the Windows NT operating system to create shares and discusses and describes methods that control access to shared resources, providing different levels of security concerning the ability of network users to access shared resources and, once accessed, their ability to ma- nipulate data. PAYOFF IDEA OVERVIEW The ability to enable remote users to share re- Windows NT provides users with the sources on NT workstations and servers repre- ability to share access to the contents sents one of the major benefits of the use of this of an entire drive or folder over a operating system. By enabling employees in an organization to share access to drives, folders, network. Although shares only oper- and files, one obtains the ability to significantly ate at the drive and folder level, the enhance productivity. However, one also pro- operating system provides several vides the potential for other persons with access methods to control access down to to the organization’s network to either intention- individual files. ally or unintentionally read or modify existing data as well as store new files whose contents could Because sharing is integrated with have an adverse effect on the operation of the or- the operating system’s database of ganization.
    [Show full text]