Computing in Higher Education: a Planning Perspective for Administrators

Total Page:16

File Type:pdf, Size:1020Kb

Computing in Higher Education: a Planning Perspective for Administrators LIWL.VV1L'aVfl il.OUVLJ;J ED 236 974 HE 016 659 AUTHOR Chachra, Vinod; Heterick, Robert C. TITLE Computing in Higher F3ucation: A Planning Perspective for Administrators. CAUSE Monograph Series. INSTITUTION CAUSE, Boulder, Colo. PUB DATE 82 NOTE 201p. AVAILABLE FROM CAUSE Publications, 737 Twenty-Ninth Street, Boulder, CO 80303 ($6.00, members; $10, nonmember colleges; $20, others). PUB TYPE Guides Non-Classroom Use (055) Viewpoints (120) EDRS PRICE MF01 Plus Postage. PC Not Available from EDRS. DESCRIPTORS Administrative Principles; Administrator Guides; *College Administration; College Planning; *Computer Oriented Programs; Computer Program ;Databases; *Data Processing; Economic Climate; Higher Education *Information Networks; *Management Information Systems; Microcomputers; Minicomputers; Program Administration; Technological Advancement; Word Processing ABSTRACT Options for using computers in managing higher education institutions and technological questions are considered in a collection of nine essays developed by the authors for this monograph. An introduction considers historical developments and provides an overview of computing modes and languages. After considering some of the economic and technological influences under which computing centers of the 1980s will have to operate, attention is directed to the following concerns: the question of whether to do different tasks on the same machine, management techniques, the reporting structure of the information systems department, job shop scheduling versus utility operation, development versus maintenance, and evaluation and audits. Topics concerning software development include models and design of data-based management systems, systems development life cycle, and structured techniques. Operations concerns are also covered, including scheduling, critical paths, service charging, job accounting, and queuing and simulation. The role of the user and the system view are considered, along with perspectives on office systems and word processing, and planning for the automated office. Issues concerning networks and sharing are also discussed, including the impact of the micro/mini computers and software sharing. Perspectives on the future of administrative computing are also considered. (SW) *********************************************************************** Reproductions supplied by EDRS are the best that can be made from the original document. *********************************************************************** CAUSE MONOGRAPH SERIES Computing In Higher Education: A Planning Perspective For Administrators By Vinod Chachra and Robert C. lieterick U.S. DEPARTMENT OF EDUCATION PERMISSION TOREPRODUCE HIS NATIONAL. INSTITUTE OF EDUCATION i A -11,1%AI MATERIAL INMICROFICHE ONLY Fil NI °RYA F ION (I VII fli1 RIC I HAS BEEN GRANTEDBY " 1..1.11,1 v. TO THE EDUCATIONALRESOURCES INFORMATION CENTER(ERIC)." The Professional Association for Development. Use, and Management of Information Systems in Higher Education ti Library or Congress Cataloging in PublicationData (. \ ' - I. i01).II t ,c,I),.r.--1),H (y-,!-: I 11}4--P1 (11111 i r1,,111t1,11 (. 1 . Het_ rick ,obi rC., . I I.Ti .C.,. 8')-2 SI) Copies of this monographare availabletcstaff of CAUSE member institutions at$6 per copy, to non-member colleges and universitiesat$10,and to othersat$20. Orders should be pre-paid :aid addressedto: CAUSE Publications 73' Twenty-Ninth Street Boulder, Colorado 80303 (303) 1449-141430 Copyright © 1982Vinod Chachra and Robert C. lieterick Allrights reserved. No part ofthispublication may be reproduced, stored ina retrieval system, or transmitted in any formorbyany means electronic,mechanical, photocopying,recording,orotherwise withoutprior written permission of the authors. ,Printed in the United States of America. Library of Congress Catalog number82-22989. 3 Preface A word of explanation isin order for the reader about to embark upon pursuing the contents herein. The reader will discover aloose collectionof essays dealing with what iscommonly called Administrative Data Processing. The collectionhasresultedfrom theoftexpresseddesireto bring together the management of the College or University to discuss the ways, means and idosyncracies of compOer- aided institutional management. When the opportunitypresenteditselfto conduct a series of professional development seminars dealing with the computer and administrationinhigher education, we drew upon a stock ofpreviousarticlesand positionpapersto construct the nucleus ofthis present work.We both are productsofthe computerrevolution. We have studied, taught and managed educational computing for the entirety ofour-professionalcareers. Our viewpointshavebeen shaped not only by our management experiences (primarily inlargerinstitutionalsettings) but also by our classroom challenges. We have not attempted to produce a -how tomanual, but rather to cast a hostoftechnologicalquestionsin a management perspective. Neitherofusfeelsthereis a -r-rrht way- to conduct administrative data processing, only tl there is-a way- that best compliments and enhances the distinctive management style of a given institution at a particulartimeinitsdevelopment. Because institutional administrationisdynamic,itisuseful, perhaps necessary, to be aware of the range of hardware, development, organi- zation, etc. options for administrative computing. We wish to acknowledc.3e, the financial assistance of the IBM Corporationin providing the support to CAUSE for the Initial distribution of this work. We ,need alsoto acknow- ledge the careful criticism of the style of this work by Julia A. Rudy of CAUSE and the thoughtful construction of the figures by Fred W.Lacerda. The text and figures were produced by the authors us inAPL and SCRIPT as part of a test documentations ystom currently under development. Any errors in the fln:s hed work are solely of our owncon- struction. V. Chachra R. C. Hnterick Blacksburg, Virginia January 1982 iv About CAUSE CAUSE, the Professional Associationfor Development, Use, and Management ofInformation Systemsin Higher Educa- tion, helps member institutions strengthen their management capabilities through improved informa;ion systems CAUSE provides member institutionsNith many services to increase the effectiveness of their administrative information systems. These servicesinclude:the Exchange Library, whichis a clearinghousefornon-proprietaryinformation and systems contributedby members; an Information Request Service tolocatespecific systems or information; consulting services to review AIS organization and manage- ment plans; organizational publicationsincluding a bi- monthly newsletter,a bi-monthly professional magazine and the CAUSE Monographs; and the CAUSE National Confer- ence. Additional details on the CAUSE organization and activities may be obtained from the CAUSE National Office in Boulder, Colorado. v About the Authors Vincd Chachra is the Assistant Provost for Planning and Information Systems at VirginiaTech. Inthisposition, he is responsible for academic planning aswell as directsupervisionoftheUniversity Library,the University Computing Center and the University Registrar. In addition he serves asthedirector for the Center for Library Automation.. He has several pro- fessional publications tohis credit andis co-author ofa book on graph theory pub- lishedbyAmerican Elsevier. He was elected as delegatetothe WhiteHouse Conference on Library and Information Sci- ences. Dr. Chachra is a past president of CAUSE. Robert C. Heterick, Jr.isDirector of the Design AutomationLaboratoryat Virginia Tech. Prior to his current position,Dr. HeterickwasDirectoroftheComputing Center at the University.He has lectured widely oncomputersystemsmanagement and isthe author of several papers on the subjects of resource allocation in computing systems and decision support systems. He hasserved as a consultanttotheIBM Corporation,the Governor of Virginia, the President's Privacy Protection Study Com- mission and numerous universities and pri- vatecorporations on computersystems management and distributedcomputingin networks of microprocessors. vii Table of Contents Chapter 1:COMPUTING PERSPECTIVES Archimedes Lever 1 Ai Brief Look Backward 3 Analog Applications . 10 The Modern Computer 11 Architecture of Computing Systems 18 Computer Languages . 23 Modes of Computing Chapter 2:TECHNOLOGICAL TRENDS Cost of Computing 31 Hardware Costs Hardware Strategies . 39 Personnel Problems 43 Software 45 Impact of Software and Personnel 45 Chapter 3:ORGANIZING FOR COMPUTING Combined vs. Separate 49 Management Tecfir iques 51 Reporting Structures . ....... 56 Job Shop vs. Utility Operation 59 Security and Disaster Plan ning Development vs. Maintenance 64 Evaluation and Audit . 68 Chapter 4: SOFTWARE DEVELOPMENT The Data Base Approach 73 Architecture of DBMS . 76 Models of DBMS 78 Data Administrator 79 Systems Development Life Cycie 80 Structured Techniques 83 Problem Areas 86 Mamigemerit Information Systems and Beyond 88 Seqiie Design Cnrideline 97 The Data Digraph 101 Chapter 5:OPERATIONS MANAGEMENT Scheduling 103 Critical Path 106 Service Charging 112 Job Accounting 118 Accliting 122 Otieueing and Simulation 125 Security and Privacy 127 Chapter 6:INFORMATION MANAGEMENT ROLES Ihe User 131 The System Perspective 132 Data Ownership 133 Control 134 Planning for Change 138 Software Directions 143 Chapter 7:INTRA-INSTITUTION COMMUNICATION Office Systems in Perspective 147 Word Processing Attitudes 151 Local Networks 155 Terminals for Managers Program 161 Planning for the Automated
Recommended publications
  • Eagle: Tcl Implementation in C
    Eagle: Tcl Implementation in C# Joe Mistachkin <[email protected]> 1. Abstract Eagle [1], Extensible Adaptable Generalized Logic Engine, is an implementation of the Tcl [2] scripting language for the Microsoft Common Language Runtime (CLR) [3]. It is designed to be a universal scripting solution for any CLR based language, and is written completely in C# [4]. Su- perficially, it is similar to Jacl [5], but it was written from scratch based on the design and imple- mentation of Tcl 8.4 [6]. It provides most of the functionality of the Tcl 8.4 interpreter while bor- rowing selected features from Tcl 8.5 [7] and the upcoming Tcl 8.6 [8] in addition to adding en- tirely new features. This paper explains how Eagle adds value to both Tcl/Tk and CLR-based applications and how it differs from other “dynamic languages” hosted by the CLR and its cousin, the Microsoft Dy- namic Language Runtime (DLR) [9]. It then describes how to use, integrate with, and extend Ea- gle effectively. It also covers some important implementation details and the overall design phi- losophy behind them. 2. Introduction This paper presents Eagle, which is an open-source [10] implementation of Tcl for the Microsoft CLR written entirely in C#. The goal of this project was to create a dynamic scripting language that could be used to automate any host application running on the CLR. 3. Rationale and Motivation Tcl makes it relatively easy to script applications written in C [11] and/or C++ [12] and so can also script applications written in many other languages (e.g.
    [Show full text]
  • Preview Tcl-Tk Tutorial (PDF Version)
    Tcl/Tk About the Tutorial Tcl is a general purpose multi-paradigm system programming language. It is a scripting language that aims at providing the ability for applications to communicate with each other. On the other hand, Tk is a cross platform widget toolkit used for building GUI in many languages. This tutorial covers various topics ranging from the basics of the Tcl/ Tk to its scope in various applications. Audience This tutorial is designed for all those individuals who are looking for a starting point of learning Tcl/ Tk. Therefore, we cover all those topics that are required for a beginner and an advanced user. Prerequisites Before proceeding with this tutorial, it is advisable for you to understand the basic concepts of computer programming. This tutorial is self-contained and you will be able to learn various concepts of Tcl/Tk even if you are a beginner. You just need to have a basic understanding of working with a simple text editor and command line. Disclaimer & Copyright Copyright 2015 by Tutorials Point (I) Pvt. Ltd. All the content and graphics published in this e-book are the property of Tutorials Point (I) Pvt. Ltd. The user of this e-book is prohibited to reuse, retain, copy, distribute, or republish any contents or a part of contents of this e-book in any manner without written consent of the publisher. We strive to update the contents of our website and tutorials as timely and as precisely as possible, however, the contents may contain inaccuracies or errors. Tutorials Point (I) Pvt.
    [Show full text]
  • Python and Epics: Channel Access Interface to Python
    Python and Epics: Channel Access Interface to Python Matthew Newville Consortium for Advanced Radiation Sciences University of Chicago October 12, 2010 http://cars9.uchicago.edu/software/python/pyepics3/ Matthew Newville (CARS, Univ Chicago) Epics and Python October 12, 2010 Why Python? The Standard Answers Clean Syntax Easy to learn, remember, and read High Level Language No pointers, dynamic memory, automatic memory Cross Platform code portable to Unix, Windows, Mac. Object Oriented full object model, name spaces. Also: procedural! Extensible with C, C++, Fortran, Java, .NET Many Libraries GUIs, Databases, Web, Image Processing, Array math Free Both senses of the word. No, really: completely free. Matthew Newville (CARS, Univ Chicago) Epics and Python October 12, 2010 Why Python? The Real Answer Scientists use Python. Matthew Newville (CARS, Univ Chicago) Epics and Python October 12, 2010 All of these tools use the C implementation of Python. NOT Jython (Python in Java) or IronPython (Python in .NET): I am not talking about Jython. Why Do Scientists Use Python? Python is great. The tools are even better: numpy Fast arrays. matplotlib Excellent Plotting library scipy Numerical Algorithms (FFT, lapack, fitting, . ) f2py Wrapping Fortran for Python sage Symbolic math (ala Maple, Mathematica) GUI Choices Tk, wxWidgets, Qt, . Free Python is Free. All these tools are Free (BSD). Matthew Newville (CARS, Univ Chicago) Epics and Python October 12, 2010 Why Do Scientists Use Python? Python is great. The tools are even better: numpy Fast arrays. matplotlib Excellent Plotting library scipy Numerical Algorithms (FFT, lapack, fitting, . ) f2py Wrapping Fortran for Python sage Symbolic math (ala Maple, Mathematica) GUI Choices Tk, wxWidgets, Qt, .
    [Show full text]
  • RAND Suicide Prevention Program Evaluation TOOLKIT
    CHILDREN AND FAMILIES The RAND Corporation is a nonprofit institution that helps improve policy and EDUCATION AND THE ARTS decisionmaking through research and analysis. ENERGY AND ENVIRONMENT HEALTH AND HEALTH CARE This electronic document was made available from www.rand.org as a public service INFRASTRUCTURE AND of the RAND Corporation. TRANSPORTATION INTERNATIONAL AFFAIRS LAW AND BUSINESS Skip all front matter: Jump to Page 16 NATIONAL SECURITY POPULATION AND AGING PUBLIC SAFETY Support RAND SCIENCE AND TECHNOLOGY Purchase this document TERRORISM AND Browse Reports & Bookstore HOMELAND SECURITY Make a charitable contribution For More Information Visit RAND at www.rand.org Explore the RAND National Defense Research Institute View document details Limited Electronic Distribution Rights This document and trademark(s) contained herein are protected by law as indicated in a notice appearing later in this work. This electronic representation of RAND intellectual property is provided for non- commercial use only. Unauthorized posting of RAND electronic documents to a non-RAND website is prohibited. RAND electronic documents are protected under copyright law. Permission is required from RAND to reproduce, or reuse in another form, any of our research documents for commercial use. For information on reprint and linking permissions, please see RAND Permissions. This report is part of the RAND Corporation tool series. RAND tools may include models, databases, calculators, computer code, GIS mapping tools, practitioner guide- lines, web applications, and various toolkits. All RAND tools undergo rigorous peer review to ensure both high data standards and appropriate methodology in keeping with RAND’s commitment to quality and objectivity. RAND Suicide Prevention Program Evaluation TOOLKIT Joie D.
    [Show full text]
  • Multi-Platform User Interface Construction – a Challenge for Software Engineering-In-The-Small
    Multi-platform User Interface Construction – A Challenge for Software Engineering-in-the-Small Judith Bishop Department of Computer Science University of Pretoria Pretoria 0002 South Africa [email protected] ABSTRACT The popular view of software engineering focuses on managing 1. INTRODUCTION teams of people to produce large systems. This paper addresses a 1.1 Software engineering different angle of software engineering, that of development for Software engineering as a discipline is perceived as tackling re-use and portability. We consider how an essential part of computing in-the-large. It elevates tools and techniques from the most software products – the user interface – can be successfully level of a craft, to where they can be efficiently and reproducibly engineered so that it can be portable across multiple platforms harnessed for the successful completion of large projects. and on multiple devices. Our research has identified the structure of the problem domain, and we have filled in some of Thirty years ago in 1975, Fred Brooks introduced us to the the answers. We investigate promising solutions from the mythical man month of software development [Brooks 1975] model-driven frameworks of the 1990s, to modern XML-based and followed this with the “no silver bullet” paper, in which he specification notations (Views, XUL, XIML, XAML), multi- talked about software engineering as being a process of building platform toolkits (Qt and Gtk), and our new work, Mirrors software with “specifications, assembly of components, and which pioneers reflective libraries. The methodology on which scaffolding” [Brooks 1987]. Boehm, too, found in 1976 that Views and Mirrors is based enables existing GUI libraries to be software engineering was, encouragingly, concentrating on the transported to new operating systems.
    [Show full text]
  • FOSDEM 2006 – Saturday 25Th February (Part 1) 1/6
    FOSDEM 2006 – Saturday 25th February (part 1) 1/6 10:00 OpenGroupware ▼ Opening Talks Tutorials KDE openSUSE Embedded Mozilla Tcl/Tk 13:00 (Janson) (H2215/Ferrer) (H.1301) (H.1302) (H.1308) (H.1309) +GNUstep (H.2111) (AW1.105) 13:00 lunch break 13:00 Movitation, 13:00 Opening and GNUstep devtools: Goals and 13:15 13:15 introduction GORM, StepTalk Opportunities Axel Hecht Nicolas Roard Systems VoIP 13:30 DTrace S. Krause-Harder, SETR LiveCD 13:30 M. Loeffler (Janson) (Lameere) 13:45 Jon Haslam Hector Oron 13:45 Mozilla 14:00 14:00 Kubuntu openSUSE Build 14:00 Foundation CoreData Intro to Plan9 SER Service Intro 14:15 14:15 Jonathan 14:15 G. Markham Sašo Kiselkov Tcl/Tk Uriel M. Jan Janak A. Schroeter, 14:30 Pereira 14:30 Ridell C. Schumacher, Optimizing 14:30 Mozilla Clif Flynt A. Bauer 14:45 14:45 Linux kernel 14:45 Europe 15:00 15:00 Open SUSE Linux and apps 15:00 Tristan Nitot Web applicationsGUI for DTrace Asterisk M.Opdenacker 15:15 Jon Haslam Mark 15:15 Key Devroom Power Mngmt 15:15 SeaMonkey with SOPE ASIC 15:30 Spencer 15:30 Signing Timo Hoenig, Lock-free data 15:30 Project Marcus Mueller verification 15:45 15:45 Holger Macht exchange for 15:45 Robert Kaiser Karel Nijs Real-Time apps 16:00 16:00 SUSE Linux 16:00 Xen Speex Asterisk Marketing Peter Soetens Flock GNUstep on the Hecl: 10.2: 16:15 Ian Pratt J.-M. Valin 16:15 Mark KDE 16:15 Z. Braniecki Zaurus PDA scripting Quo vadis ? 16:30 16:30 Spencer Sebastian Alsa SoC layer16:30 Nicolaus Schaller for mobiles Kügler M.Loeffler,C.Thiel D.N.Welton 16:45 16:45 Liam Girdwood 16:45 Mozilla 17:00 Closing Talks (Janson) 17:00 17:00 Project BOF 17:15 17:15 17:15 FOSDEM Donators Return 17:30 17:30 17:45 17:45 17:30 FSF Europe Opening Talks (Janson) Hacker Rooms LPI Exam Sessions 10:00 FOSDEM Core Staff Welcome Speech Building H: H2213 Saturday 13:00-14:30 10:30 Keynote Building AW: AW1.117 (H2214) 15:00-16:30 Richard M.
    [Show full text]
  • Pygtk 2.0 Tutorial
    PyGTK 2.0 Tutorial John Finlay October 7, 2012 PyGTK 2.0 Tutorial by John Finlay Published March 2, 2006 ii Contents 1 Introduction 1 1.1 Exploring PyGTK . .2 2 Getting Started 5 2.1 Hello World in PyGTK . .7 2.2 Theory of Signals and Callbacks . .9 2.3 Events . 10 2.4 Stepping Through Hello World . 11 3 Moving On 15 3.1 More on Signal Handlers . 15 3.2 An Upgraded Hello World . 15 4 Packing Widgets 19 4.1 Theory of Packing Boxes . 19 4.2 Details of Boxes . 20 4.3 Packing Demonstration Program . 22 4.4 Packing Using Tables . 27 4.5 Table Packing Example . 28 5 Widget Overview 31 5.1 Widget Hierarchy . 31 5.2 Widgets Without Windows . 34 6 The Button Widget 35 6.1 Normal Buttons . 35 6.2 Toggle Buttons . 38 6.3 Check Buttons . 40 6.4 Radio Buttons . 42 7 Adjustments 45 7.1 Creating an Adjustment . 45 7.2 Using Adjustments the Easy Way . 45 7.3 Adjustment Internals . 46 8 Range Widgets 49 8.1 Scrollbar Widgets . 49 8.2 Scale Widgets . 49 8.2.1 Creating a Scale Widget . 49 8.2.2 Methods and Signals (well, methods, at least) . 50 8.3 Common Range Methods . 50 8.3.1 Setting the Update Policy . 50 8.3.2 Getting and Setting Adjustments . 51 8.4 Key and Mouse Bindings . 51 8.5 Range Widget Example . 51 9 Miscellaneous Widgets 57 9.1 Labels . 57 9.2 Arrows . 60 9.3 The Tooltips Object .
    [Show full text]
  • "ESF Load Sequencer Software Verification & Validation Rept."
    ' ESF LOAD SEQUENCER SOFTWARE VERIFICATION AND VALIDATION REPORT prepared by: SIMPACT ASSOCIATES'NC. 5520 Ruffin Road San Diego, CA 92123 September 9, 1982 ESF LOAD SEQUENCER SOFTWARE VERIFICATION AND VALIDATION REPORT TABLE OF CONTENTS Pacae ~ 1 OB JECTIVE ~ o ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ o ~ ~ ~ 1 2. STUDY PROCEDURE AND RESULTS SUMMARY ~ ~ ~ ~ ~ ~ ~ t 0 4 I ~ 0 ~ 2 3. SPECIFICATION REQUIREMENTS ~ ~ ~ ~ ~ 0 ~ ~ ~ ~ 0 t I ~ 4 4 SOFTWARE STRUCTURE ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ 5 5. SYSTEM ~ ~ ~ ROUTINES ... .... ....... .... ~ ... ~ ... 7 6. UNDERVOLTAGE MONITORING ~ 0 ~ ~ ~ ~ ~ ~ ~ ~ 0 ~ ~ ~ 9 7. ESF BUS LOAD SEQUENCING o ~ ~ ~ ~ ~ ~ o ~ ~ ~ ~ e ~ 10 8. AUTOTESTING ............................... 12 9. PERFORMANCE/DESIGN DEMONSTRATION TEST RESULTS . 16 10. CONCLUSION ~ ....... ........ .. ~ .. ~ ~ .. .. ~ .; ~ . 17 APPENDIX A ~ ~ ~ ~ ~ ~ ~ ~ .. ... ... ~ ~ ... ~ ~ ~ ~ ~ .. ~ . ~ . ~ . ~ ~ .A-1 ESF LOAD SEQUENCER SOFTWARE VERIFICATION AND VALIDATION REPORT 1 OBJECTIVE The objective of the Software Verification and Validation Study is to verify that the software of the ESF Load Sequencer meets the requirements of the design specification, and that no sneak software paths (circuits) exist that would render the system inoperable. The ESF Load Sequencer is a module in the Balance of Plant (BOP) Engineered Safety Features Actuation System (ESFAS) supplied by General Atomic Company (GA) to the Palo Verde Nuclear Generating Station under Arizona Public Service Company Purchase Order 10407-13-JM-104 and Bechtel Power Corporation Speci fication 13-JM-104. This module controls loading of the station ESF bus and diesel generators under loss of power conditions or if an accident signal is present. The purpose of this report is to outline the methods used to perform this study and to detail the findings of the study. 2. STUDY PROCEDURE AND RESULTS SUMMARY The following steps were taken to per form the study: a ~ Review of Bechtel Specification (13-JM-104).
    [Show full text]
  • 13A04806 LINUX PROGRAMMING and SCRIPTING UNIT 4 TCL/ TK SCRIPTING:Tcl Fundamentals, String and Pattern Matching, Tcl Data Struct
    13A04806 LINUX PROGRAMMING AND SCRIPTING UNIT 4 TCL/ TK SCRIPTING:Tcl Fundamentals, String and Pattern Matching, Tcl Data Structures ,Control Flow Commands, Procedures and Scope , Evel, Working With UNIX, Reflection and Debugging, Script Libraries, Tk Fundamentals ,Tk by Examples, The Pack Geometry Manager, Binding Commands to X Events, Buttons and Menus, Simple Tk Widgets, Entry and Listbox Widgets Focus, Grabs and Dialogs 13A04806 LINUX PROGRAMMING AND SCRIPTING Tcl - Overview Tcl is shortened form of Tool Command Language. John Ousterhout of the University of California, Berkeley, designed it. It is a combination of a scripting language and its own interpreter that gets embedded to the application, we develop with it. Tcl was developed initially for Unix. It was then ported to Windows, DOS, OS/2, and Mac OSX. Tcl is much similar to other unix shell languages like Bourne Shell (Sh), the C Shell (csh), the Korn Shell (sh), and Perl. It aims at providing ability for programs to interact with other programs and also for acting as an embeddable interpreter. Even though, the original aim was to enable programs to interact, you can find full-fledged applications written in Tcl/Tk. Features of Tcl The features of Tcl are as follows − ∑ Reduced development time. ∑ Powerful and simple user interface kit with integration of TK. ∑ Write once, run anywhere. It runs on Windows, Mac OS X, and almost on every Unix platform. ∑ Quite easy to get started for experienced programmers; since, the language is so simple that they can learn Tcl in a few hours or days. ∑ You can easily extend existing applications with Tcl.
    [Show full text]
  • Metadata Specifications Cablelabs VOD Content Specification Version 1.1 MD-SP-VOD-CONTENT1.1-C01-120803
    Metadata Specifications CableLabs® VOD Content Specification Version 1.1 MD-SP-VOD-CONTENT1.1-C01-120803 CLOSED Notice This specification is the result of a cooperative effort undertaken at the direction of Cable Television Laboratories, Inc. for the benefit of the cable industry and its customers. This document may contain references to other documents not owned or controlled by CableLabs. Use and understanding of this document may require access to such other documents. Designing, manufacturing, distributing, using, selling, or servicing products, or providing services, based on this document may require intellectual property licenses from third parties for technology referenced in this document. Neither CableLabs nor any member company is responsible to any party for any liability of any nature whatsoever resulting from or arising out of use or reliance upon this document, or any document referenced herein. This document is furnished on an "AS IS" basis and neither CableLabs nor its members provides any representation or warranty, express or implied, regarding the accuracy, completeness, noninfringement, or fitness for a particular purpose of this document, or any document referenced herein. Cable Television Laboratories, Inc. 2002-2012 MD-SP-VOD-CONTENT1.1-C01-120803 Metadata Specifications DISCLAIMER This document is published by Cable Television Laboratories, Inc. ("CableLabs®"). CableLabs reserves the right to revise this document for any reason including, but not limited to, changes in laws, regulations, or standards promulgated by various agencies; technological advances; or changes in equipment design, manufacturing techniques, or operating procedures described, or referred to, herein. CableLabs makes no representation or warranty, express or implied, with respect to the completeness, accuracy, or utility of the document or any information or opinion contained in the report.
    [Show full text]
  • Proximal Junctional Kyphosis in Lenke 5 AIS Patients
    Zhou et al. BMC Musculoskeletal Disorders (2021) 22:185 https://doi.org/10.1186/s12891-021-04052-8 RESEARCH ARTICLE Open Access Proximal junctional kyphosis in Lenke 5 AIS patients: the important factor of pelvic incidence Quan Zhou†, Bowen Hu†, Xi Yang*, Yueming Song, Limin Liu, Linnan Wang, Lei Wang, Chunguang Zhou, Zhongjie Zhou, Peng Xiu and Liang Wang Abstract Background: The purpose of the study was to investigate whether pelvic incidence (PI) will affect the occurrence of PJK in Lenke 5 AIS patients after correction surgery and try to explore a better surgical scheme based on PI. Methods: Lenke 5C AIS patients that underwent correction surgery with a minimum of a 2-year follow-up were identified. Demographic and radiographic data were collected preoperatively, postoperatively, and at the final follow-up. The comparison between the PJK and the Non-PJK group was conducted and the subgroup analysis was performed based on the preoperative value of PI to investigate the potential mechanism of PJK. Clinical assessments were performed using the Scoliosis Research Society (SRS)-22 questionnaire. Results: The mean preoperative Cobb angle of the TL/L curve was 53.4°±8.6. At the final follow-up, the mean TL/L Cobb angle was drastically decreased to 7.3°±6.8 (P < 0.001). The incidence of PJK in Lenke 5 AIS was 18.6 %, 21.9 % (7/32) in the low PI group (PI < 45°) and 15.8 % (6/38) in the high PI group (PI ≥ 45°), and there was no statistical difference between the two groups (χ2 = 0.425, P = 0.514).
    [Show full text]
  • Clean Rooms – Environmental Monitoring
    PhEn-602 Notes # 4 J. Manfredi Pharmaceutical Facility Design Spring 2009 1 Clean Rooms and Controlled Environments Basic definitions Clean Room: A room in which the concentration of airborne particles is controlled and contains one or more clean zones Clean Zone: A defined space in which the concentration of airborne particles is controlled to meet a specified airborne particulate class. Pharmaceutical Facility Design Spring 2009 2 Clean Rooms and Controlled Environments Federal Standard 209E (FS-209E) provides Clean Room Classes Rooms classified based on number of particles > 0.5 micron per cubic foot Class descriptions still in use today. FS 209E is concerned about the following particle sizes, in microns: 0.1, 0.2, 0.3, 0.5, 5.0 Pharmaceutical Facility Design Spring 2009 3 Clean Rooms and Controlled Environments Types of Contaminants Viable Particulates Non-Viable Particulates Pharmaceutical Facility Design Spring 2009 4 Controlled Environments - Types of Contaminants Non-viable Particulates Metal specks, fiber from clothing Obtained from: Equipment, people, tools Viable (micro-organisms) Bacteria Yeast, molds Obtained from: People, outside air, water, equipment, tools, excipients, active ingredients Pharmaceutical Facility Design Spring 2009 5 Clean Rooms and Controlled Environments Sources of particulate generation Internal: Personnel Normally the highest source of contamination Process Air conditioning system Introduction of raw materials Introduction of equipment and materials External Outside air Pharmaceutical Facility Design Spring 2009 6 Clean Rooms and Controlled Environments Some interesting facts: Visible indoor air particles constitute only about 10% of particles present in indoor air. It may be possible to see particles as small as 10 microns It may be possible to see particles as small as 10 microns under favorable conditions.
    [Show full text]