2. Types of Computer Software Contents

Total Page:16

File Type:pdf, Size:1020Kb

2. Types of Computer Software Contents 2. Types of Computer Software Contents 1 Operating system 1 1.1 Types of operating systems ...................................... 1 1.1.1 Single- and multi-tasking ................................... 1 1.1.2 Single- and multi-user ..................................... 1 1.1.3 Distributed .......................................... 1 1.1.4 Templated ........................................... 1 1.1.5 Embedded ........................................... 2 1.1.6 Real-time ........................................... 2 1.2 History ................................................. 2 1.2.1 Mainframes .......................................... 2 1.2.2 Microcomputers ....................................... 4 1.3 Examples of operating systems .................................... 4 1.3.1 Unix and Unix-like operating systems ............................ 4 1.3.2 Microsoft Windows ...................................... 6 1.3.3 Other ............................................. 7 1.4 Components .............................................. 7 1.4.1 Kernel ............................................. 7 1.4.2 Networking .......................................... 11 1.4.3 Security ............................................ 12 1.4.4 User interface ......................................... 12 1.5 Real-time operating systems ...................................... 13 1.6 Operating system development as a hobby .............................. 14 1.7 Diversity of operating systems and portability ............................. 14 1.8 Market share .............................................. 14 1.9 See also ................................................ 14 1.10 References ............................................... 14 1.11 Further reading ............................................ 15 1.12 External links ............................................. 15 2 System software 16 2.1 See also ................................................ 16 2.2 References .............................................. 16 2.3 External links ............................................. 16 i ii CONTENTS 3 Firmware 17 3.1 Origin of the term ........................................... 17 3.2 Personal computers .......................................... 17 3.3 Consumer products .......................................... 18 3.4 Automobiles .............................................. 18 3.5 Examples ............................................... 18 3.6 Flashing ................................................ 19 3.7 Firmware hacking ........................................... 19 3.7.1 HDD firmware hacks ..................................... 19 3.8 Security risks ............................................. 19 3.9 See also ................................................ 20 3.10 References .............................................. 20 3.11 External links ............................................. 20 4 Computer multitasking 21 4.1 Multiprogramming .......................................... 21 4.2 Cooperative multitasking ....................................... 22 4.3 Preemptive multitasking ....................................... 22 4.4 Real time ............................................... 23 4.5 Multithreading ............................................ 23 4.6 Memory protection .......................................... 23 4.7 Memory swapping .......................................... 23 4.8 Programming ............................................. 23 4.9 See also ................................................ 24 4.10 References .............................................. 24 5 Time-sharing 25 5.1 History ................................................. 25 5.1.1 Batch processing ....................................... 25 5.1.2 Time-sharing ......................................... 25 5.1.3 Development ......................................... 26 5.1.4 Time-sharing business .................................... 26 5.1.5 The computer utility ..................................... 26 5.1.6 Security ............................................ 27 5.2 Notable time-sharing systems ..................................... 27 5.3 See also ................................................ 28 5.4 References ............................................... 28 5.5 Further reading ............................................ 28 5.6 External links ............................................. 28 6 Real-time computing 29 6.1 History ................................................ 29 CONTENTS iii 6.2 Criteria for real-time computing ................................... 29 6.2.1 Real-time in digital signal processing ............................. 30 6.3 Real-time and high-performance ................................... 30 6.4 Near real-time ............................................ 31 6.5 Design methods ............................................ 31 6.6 See also ................................................ 31 6.7 References ............................................... 31 6.8 Further reading ............................................ 32 6.9 External links ............................................. 32 6.9.1 Technical committees .................................... 32 6.9.2 Scientific conferences .................................... 32 6.9.3 Journals ............................................ 32 6.9.4 Research groups ....................................... 32 6.9.5 Technical papers ....................................... 33 7 Fault tolerance 34 7.1 Terminology .............................................. 34 7.2 Components .............................................. 35 7.3 Redundancy .............................................. 35 7.4 Criteria ................................................ 35 7.5 Requirements ............................................. 35 7.6 Replication .............................................. 36 7.7 Disadvantages ............................................. 36 7.8 Examples ............................................... 37 7.9 Related terms ............................................. 37 7.10 See also ................................................ 37 7.11 References ............................................... 37 7.12 Bibliography .............................................. 38 7.13 External links ............................................. 38 8 Mean time between failures 39 8.1 The Overview ............................................. 39 8.2 Formal definition of MTBF ...................................... 40 8.3 Variations of MTBF ......................................... 40 8.3.1 MTTF and MTTFd calculation ................................ 40 8.4 Notes ................................................. 40 8.5 See also ................................................ 40 8.6 References ............................................... 40 8.7 External links ............................................. 40 9 Flowchart 42 9.1 Overview ............................................... 42 iv CONTENTS 9.2 History ................................................ 43 9.3 Flowchart building blocks ....................................... 43 9.3.1 Symbols ........................................... 43 9.3.2 Data-flow extensions ..................................... 44 9.4 Types of flowchart .......................................... 44 9.5 Software ............................................... 45 9.5.1 Diagramming ......................................... 45 9.5.2 Programming ......................................... 45 9.6 See also ................................................ 45 9.7 References .............................................. 45 9.8 Further reading ............................................ 45 9.9 External links ............................................. 46 10 Programming language 47 10.1 Definitions ............................................... 47 10.2 History ................................................. 48 10.2.1 Early developments ...................................... 48 10.2.2 Refinement .......................................... 49 10.2.3 Consolidation and growth ................................... 49 10.3 Elements ................................................ 50 10.3.1 Syntax ............................................. 50 10.3.2 Semantics ........................................... 51 10.3.3 Standard library and run-time system ............................. 52 10.4 Design and implementation ...................................... 53 10.4.1 Specification ......................................... 53 10.4.2 Implementation ........................................ 53 10.5 Usage ................................................. 54 10.5.1 Measuring language usage .................................. 54 10.6 Taxonomies .............................................. 54 10.7 See also ................................................ 55 10.8 References ............................................... 55 10.9 Further reading ............................................ 57 10.10External links ............................................. 58 11 History of programming languages 59 11.1 Early history .............................................. 59 11.2 First programming languages ..................................... 59 11.3 Establishing fundamental paradigms ................................. 60 11.4 1980s: consolidation, modules, performance ............................. 61 11.5 1990s: the Internet age ........................................ 61 11.6 Current trends ............................................
Recommended publications
  • Xerox 4890 Highlight Color Laser Printing System Product Reference
    XEROX Xerox 4890 HighLight Color Laser Printing System Product Reference Version 5.0 November 1994 720P93720 Xerox Corporation 701 South Aviation Boulevard El Segundo, California 90245 ©1991, 1992, 1993, 1994 by Xerox Corporation. All rights reserved. Copyright protection claimed includes all forms and matters of copyrightable material and information now allowed by statutory or judicial law or hereinafter granted, including without limitation, material generated from the software programs which are displayed on the screen such as icons, screen displays, looks, etc. November 1994 Printed in the United States of America. Publication number: 721P82591 Xerox® and all Xerox products mentioned in this publication are trademarks of Xerox Corporation. Products and trademarks of other companies are also acknowledged. Changes are periodically made to this document. Changes, technical inaccuracies, and typographic errors will be corrected in subsequent editions. This book was produced using the Xerox 6085 Professional Computer System. The typefaces used are Optima, Terminal, and monospace. Table of contents 1. LPS fundamentals 1-1 Electronic printing 1-1 Advantages 1-1 Highlight color 1-2 Uses for highlight color in your documents 1-2 How highlight color is created 1-2 Specifying 4890 colors 1-3 Color-related software considerations 1-4 Adding color to line printer and LCDS data streams 1-4 Adding color to Interpress and PostScript data streams 1-5 Adding color to forms 1-6 Fonts 1-8 Acquiring and loading fonts 1-9 LPS production process overview 1-9 Ink referencing 1-10 Unformatted data 1-10 Formatted data 1-11 4890 HighLight Color LPS major features 1-11 4890 feature reference 1-12 LPS connection options 1-12 System controller 1-13 Optional peripheral cabinet 1-13 Printer 1-13 Paper handling 1-14 Forms 1-15 Fonts 1-15 Printed format 1-15 Highlight color 1-16 Types of output 1-16 DFA/Segment Management 1-16 SCSI System Disk/Floppy Disk 1-18 Color Enhancements 1-18 XEROX 4890 HIGHLIGHT COLOR LPS PRODUCT REFERENCE iii TABLE OF CONTENTS 2.
    [Show full text]
  • Dockerdocker
    X86 Exagear Emulation • Android Gaming • Meta Package Installation Year Two Issue #14 Feb 2015 ODROIDMagazine DockerDocker OS Spotlight: Deploying ready-to-use Ubuntu Studio containers for running complex system environments • Interfacing ODROID-C1 with 16 Channel Relay Play with the Weather Board • ODROID-C1 Minimal Install • Device Configuration for Android Development • Remote Desktop using Guacamole What we stand for. We strive to symbolize the edge of technology, future, youth, humanity, and engineering. Our philosophy is based on Developers. And our efforts to keep close relationships with developers around the world. For that, you can always count on having the quality and sophistication that is the hallmark of our products. Simple, modern and distinctive. So you can have the best to accomplish everything you can dream of. We are now shipping the ODROID U3 devices to EU countries! Come and visit our online store to shop! Address: Max-Pollin-Straße 1 85104 Pförring Germany Telephone & Fax phone : +49 (0) 8403 / 920-920 email : [email protected] Our ODROID products can be found at http://bit.ly/1tXPXwe EDITORIAL ow that ODROID Magazine is in its second year, we’ve ex- panded into several social networks in order to make it Neasier for you to ask questions, suggest topics, send article submissions, and be notified whenever the latest issue has been posted. Check out our Google+ page at http://bit.ly/1D7ds9u, our Reddit forum at http://bit. ly/1DyClsP, and our Hardkernel subforum at http://bit.ly/1E66Tm6. If you’ve been following the recent Docker trends, you’ll be excited to find out about some of the pre-built Docker images available for the ODROID, detailed in the second part of our Docker series that began last month.
    [Show full text]
  • Optional Package 1WIRE Paket OPT OW V. 1.0.0 Für Fli4l - 3.4.0
    Optional Package 1WIRE Paket OPT_OW V. 1.0.0 für Fli4L - 3.4.0 Karl M. Weckler [email protected] Rockenberg, Mai 2009 OPT_OW Inhaltsverzeichnis Paket OPT_OW.......................................................................................................... 1 Inhaltsverzeichnis ....................................................................................................... 2 Dokumentation des Paketes OPT_OW ...................................................................... 3 1. Einleitung................................................................................................................ 3 1.1. OPT_OW ......................................................................................................... 3 1.2. OW = OneWire = 1-Wire .................................................................................. 3 1.2.1. Der 1-Wire Standard.................................................................................. 3 1.2.2. 1-Wire-Bauteile.......................................................................................... 3 1.2.3. 1-Wire Bus................................................................................................. 3 1.3. OWFS .............................................................................................................. 4 1.4. Fuse................................................................................................................. 4 2. Lizenz ....................................................................................................................
    [Show full text]
  • Technical Details of the Elliott 152 and 153
    Appendix 1 Technical Details of the Elliott 152 and 153 Introduction The Elliott 152 computer was part of the Admiralty’s MRS5 (medium range system 5) naval gunnery project, described in Chap. 2. The Elliott 153 computer, also known as the D/F (direction-finding) computer, was built for GCHQ and the Admiralty as described in Chap. 3. The information in this appendix is intended to supplement the overall descriptions of the machines as given in Chaps. 2 and 3. A1.1 The Elliott 152 Work on the MRS5 contract at Borehamwood began in October 1946 and was essen- tially finished in 1950. Novel target-tracking radar was at the heart of the project, the radar being synchronized to the computer’s clock. In his enthusiasm for perfecting the radar technology, John Coales seems to have spent little time on what we would now call an overall systems design. When Harry Carpenter joined the staff of the Computing Division at Borehamwood on 1 January 1949, he recalls that nobody had yet defined the way in which the control program, running on the 152 computer, would interface with guns and radar. Furthermore, nobody yet appeared to be working on the computational algorithms necessary for three-dimensional trajectory predic- tion. As for the guns that the MRS5 system was intended to control, not even the basic ballistics parameters seemed to be known with any accuracy at Borehamwood [1, 2]. A1.1.1 Communication and Data-Rate The physical separation, between radar in the Borehamwood car park and digital computer in the laboratory, necessitated an interconnecting cable of about 150 m in length.
    [Show full text]
  • What Is an Operating System III 2.1 Compnents II an Operating System
    Page 1 of 6 What is an Operating System III 2.1 Compnents II An operating system (OS) is software that manages computer hardware and software resources and provides common services for computer programs. The operating system is an essential component of the system software in a computer system. Application programs usually require an operating system to function. Memory management Among other things, a multiprogramming operating system kernel must be responsible for managing all system memory which is currently in use by programs. This ensures that a program does not interfere with memory already in use by another program. Since programs time share, each program must have independent access to memory. Cooperative memory management, used by many early operating systems, assumes that all programs make voluntary use of the kernel's memory manager, and do not exceed their allocated memory. This system of memory management is almost never seen any more, since programs often contain bugs which can cause them to exceed their allocated memory. If a program fails, it may cause memory used by one or more other programs to be affected or overwritten. Malicious programs or viruses may purposefully alter another program's memory, or may affect the operation of the operating system itself. With cooperative memory management, it takes only one misbehaved program to crash the system. Memory protection enables the kernel to limit a process' access to the computer's memory. Various methods of memory protection exist, including memory segmentation and paging. All methods require some level of hardware support (such as the 80286 MMU), which doesn't exist in all computers.
    [Show full text]
  • Information Technology 3 and 4/1998. Emerging
    OCCASION This publication has been made available to the public on the occasion of the 50th anniversary of the United Nations Industrial Development Organisation. DISCLAIMER This document has been produced without formal United Nations editing. The designations employed and the presentation of the material in this document do not imply the expression of any opinion whatsoever on the part of the Secretariat of the United Nations Industrial Development Organization (UNIDO) concerning the legal status of any country, territory, city or area or of its authorities, or concerning the delimitation of its frontiers or boundaries, or its economic system or degree of development. Designations such as “developed”, “industrialized” and “developing” are intended for statistical convenience and do not necessarily express a judgment about the stage reached by a particular country or area in the development process. Mention of firm names or commercial products does not constitute an endorsement by UNIDO. FAIR USE POLICY Any part of this publication may be quoted and referenced for educational and research purposes without additional permission from UNIDO. However, those who make use of quoting and referencing this publication are requested to follow the Fair Use Policy of giving due credit to UNIDO. CONTACT Please contact [email protected] for further information concerning UNIDO publications. For more information about UNIDO, please visit us at www.unido.org UNITED NATIONS INDUSTRIAL DEVELOPMENT ORGANIZATION Vienna International Centre, P.O. Box 300, 1400 Vienna, Austria Tel: (+43-1) 26026-0 · www.unido.org · [email protected] EMERGING TECHNOLOGY SERIES 3 and 4/1998 Information Technology UNITED NATIONS INDUSTRIAL DEVELOPMENT ORGANIZATION Vienna, 2000 EMERGING TO OUR READERS TECHNOLOGY SERIES Of special interest in this issue of Emerging Technology Series: Information T~chn~~ogy is the focus on a meeting that took INFORMATION place from 2n to 4 November 1998, in Bangalore, India.
    [Show full text]
  • Powerview Command Reference
    PowerView Command Reference TRACE32 Online Help TRACE32 Directory TRACE32 Index TRACE32 Documents ...................................................................................................................... PowerView User Interface ............................................................................................................ PowerView Command Reference .............................................................................................1 History ...................................................................................................................................... 12 ABORT ...................................................................................................................................... 13 ABORT Abort driver program 13 AREA ........................................................................................................................................ 14 AREA Message windows 14 AREA.CLEAR Clear area 15 AREA.CLOSE Close output file 15 AREA.Create Create or modify message area 16 AREA.Delete Delete message area 17 AREA.List Display a detailed list off all message areas 18 AREA.OPEN Open output file 20 AREA.PIPE Redirect area to stdout 21 AREA.RESet Reset areas 21 AREA.SAVE Save AREA window contents to file 21 AREA.Select Select area 22 AREA.STDERR Redirect area to stderr 23 AREA.STDOUT Redirect area to stdout 23 AREA.view Display message area in AREA window 24 AutoSTOre ..............................................................................................................................
    [Show full text]
  • Linux. Sécuriser Un Réseau
    11960_Securiser_Linux_XP 31/10/06 9:40 Page 1 Cahiers Cahiers de de l’Admin Collection dirigée par Nat Makarévitch Delaunay Boutherin l’Admin B. B. Ingénieur de formation, Bernard Boutherin a éd. éd. e été administrateur système et e 3 édition réseau successivement dans e trois laboratoires du CNRS. Il 3 est actuellement responsable in- 3 Quelles règles d’or appliquer pour préserver la sûreté d’un réseau Linux ? formatique du LPSC à Grenoble Comment protéger les systèmes et les données ? et est chargé de mission pour la sécurité informatique auprès de la direction de l’IN2P3 (18 labo- Grâce à des principes simples et à la mise en œuvre d’outils libres réputés pour ratoires de recherche, près de leur efficacité, on apprendra dans ce cahier à améliorer l’architecture d’un réseau trois mille utilisateurs). d’entreprise et à le protéger contre les intrusions, dénis de service et autres Bernard Boutherin attaques. On verra notamment comment filtrer des flux (netfilter/IPtables…), De formation universitaire, sécuriser la messagerie (milter-greylist, ClamAV…), chiffrer avec SSL (stunnel…) Benoit Delaunay travaille Benoit Delaunay et (Open)SSH. On étudiera les techniques et outils de surveillance (métrologie avec actuellement au Centre de Cal- MRTG, empreintes Tripwire, détection d’intrusion avec des outils tel Snort, créa- cul de l’IN2P3 (Institut National tion de tableaux de bord) et l’authentification unique (SSO) avec LDAP, Kerberos, de Physique Nucléaire et de PAM, les certificats X509 et les PKI… Physique des Particules). Il y est Linux administrateur système et ré- Linux seau en charge de la sécurité informatique.
    [Show full text]
  • Mac OS X: an Introduction for Support Providers
    Mac OS X: An Introduction for Support Providers Course Information Purpose of Course Mac OS X is the next-generation Macintosh operating system, utilizing a highly robust UNIX core with a brand new simplified user experience. It is the first successful attempt to provide a fully-functional graphical user experience in such an implementation without requiring the user to know or understand UNIX. This course is designed to provide a theoretical foundation for support providers seeking to provide user support for Mac OS X. It assumes the student has performed this role for Mac OS 9, and seeks to ground the student in Mac OS X using Mac OS 9 terms and concepts. Author: Robert Dorsett, manager, AppleCare Product Training & Readiness. Module Length: 2 hours Audience: Phone support, Apple Solutions Experts, Service Providers. Prerequisites: Experience supporting Mac OS 9 Course map: Operating Systems 101 Mac OS 9 and Cooperative Multitasking Mac OS X: Pre-emptive Multitasking and Protected Memory. Mac OS X: Symmetric Multiprocessing Components of Mac OS X The Layered Approach Darwin Core Services Graphics Services Application Environments Aqua Useful Mac OS X Jargon Bundles Frameworks Umbrella Frameworks Mac OS X Installation Initialization Options Installation Options Version 1.0 Copyright © 2001 by Apple Computer, Inc. All Rights Reserved. 1 Startup Keys Mac OS X Setup Assistant Mac OS 9 and Classic Standard Directory Names Quick Answers: Where do my __________ go? More Directory Names A Word on Paths Security UNIX and security Multiple user implementation Root Old Stuff in New Terms INITs in Mac OS X Fonts FKEYs Printing from Mac OS X Disk First Aid and Drive Setup Startup Items Mac OS 9 Control Panels and Functionality mapped to Mac OS X New Stuff to Check Out Review Questions Review Answers Further Reading Change history: 3/19/01: Removed comment about UFS volumes not being selectable by Startup Disk.
    [Show full text]
  • Irmx® 286/Irmx® II Troubleshooting Guide
    iRMX® 286/iRMX® II Troubleshooting Guide Q1/1990 Order Number: 273472-001 inter iRMX® 286/iRMX® II Troubleshooting Guide Q1/1990 Order Number: 273472-001 Intel Corporation 2402 W. Beardsley Road Phoenix, Arizona Mailstop DV2-42 Intel Corporation (UK) Ltd. Pipers Way Swindon, Wiltshire SN3 1 RJ United Kingdom Intel Japan KK 5-6 Tokodai, Toyosato-machi Tsukuba-gun Ibaragi-Pref. 300-26 An Intel Technical Report from Technical Support Operations Copyright ©1990, Intel Corporation Copyright ©1990, Intel Corporation The information in this document is subject to change without notice. Intel Corporation makes no warranty of any kind with regard to this material, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. Intel Corporation assumes no responsibility for any errors that ~ay :!ppe3r in this d~ur:::ent. Intel Corpomtion make:; nc ccmmitmcut tv update nor to keep C"l..iiTeilt thc information contained in this document. Intel Corporation assUmes no responsibility for the use of any circuitry other than circuitry embodied in an Intel product. No other circuit patent licenses are implied. Intel software products are copyrighted by and shall remain the property of Intel Corporation. Use, duplication or disclosure is subject to restrictions stated in Intel's software license, or as defined in FAR 52.227-7013. No part of this document may be copied or reproduced in any form or by any means without the prior written consent of Intel Corporation. The following are trademarks of Intel Corporation
    [Show full text]
  • The Profession of IT Multitasking Without Thrashing Lessons from Operating Systems Teach How to Do Multitasking Without Thrashing
    viewpoints VDOI:10.1145/3126494 Peter J. Denning The Profession of IT Multitasking Without Thrashing Lessons from operating systems teach how to do multitasking without thrashing. UR INDIVIDUAL ABILITY to The first four destinations basi- mercial world with its OS 360 in 1965. be productive has been cally remove incoming tasks from your Operating systems implement mul- hard stressed by the sheer workspace, the fifth closes quick loops, titasking by cycling a CPU through a load of task requests we and the sixth holds your incomplete list of all incomplete tasks, giving each receive via the Internet. In loops. GTD helps you keep track of one a time slice on the CPU. If the task 2001, David Allen published Getting these unfinished loops. does not complete by the end of its O 1 Things Done, a best-selling book about The idea of tasks being closed loops time slice, the OS interrupts it and puts a system for managing all our tasks to of a conversation between a requester it on the end of the list. To switch the eliminate stress and increase produc- and a perform was first proposed in CPU context, the OS saves all the CPU tivity. Allen claims that a considerable 1979 by Fernando Flores.5 The “condi- registers of the current task and loads amount of stress comes our way when tions of satisfaction” that are produced the registers of the new task. The de- we have too many incomplete tasks. by the performer define loop comple- signers set the time slice length long He views tasks as loops connecting tion and allow tracking the movement enough to keep the total context switch someone making a request and you of the conversation toward completion.
    [Show full text]
  • Multiprocessing Contents
    Multiprocessing Contents 1 Multiprocessing 1 1.1 Pre-history .............................................. 1 1.2 Key topics ............................................... 1 1.2.1 Processor symmetry ...................................... 1 1.2.2 Instruction and data streams ................................. 1 1.2.3 Processor coupling ...................................... 2 1.2.4 Multiprocessor Communication Architecture ......................... 2 1.3 Flynn’s taxonomy ........................................... 2 1.3.1 SISD multiprocessing ..................................... 2 1.3.2 SIMD multiprocessing .................................... 2 1.3.3 MISD multiprocessing .................................... 3 1.3.4 MIMD multiprocessing .................................... 3 1.4 See also ................................................ 3 1.5 References ............................................... 3 2 Computer multitasking 5 2.1 Multiprogramming .......................................... 5 2.2 Cooperative multitasking ....................................... 6 2.3 Preemptive multitasking ....................................... 6 2.4 Real time ............................................... 7 2.5 Multithreading ............................................ 7 2.6 Memory protection .......................................... 7 2.7 Memory swapping .......................................... 7 2.8 Programming ............................................. 7 2.9 See also ................................................ 8 2.10 References .............................................
    [Show full text]