DOCSLIB.ORG

Basic Concepts of Operating Systems

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Basic Concepts of Operating Systems ✐ ✐ “26341˙CH01˙Garrido” — 2011/6/2 — 12:58 — page1—#3 ✐ ✐ © Jones & Bartlett Learning, LLC © Jones & Bartlett Learning, LLC NOT FOR SALE OR DISTRIBUTION NOT FOR SALE OR DISTRIBUTION Chapter© Jones & 1 Bartlett Learning, LLC © Jones & Bartlett Learning, LLC NOT FOR SALE OR DISTRIBUTION NOT FOR SALE OR DISTRIBUTION Basic Concepts of © JonesOperating & Bartlett Learning, Systems LLC © Jones & Bartlett Learning, LLC NOT FOR SALE OR DISTRIBUTION NOT FOR SALE OR DISTRIBUTION © Jones & Bartlett Learning, LLC © Jones & Bartlett Learning, LLC NOT FOR SALE OR DISTRIBUTION NOT FOR SALE OR DISTRIBUTION 1.1 ©Introduction Jones & Bartlett Learning, LLC © Jones & Bartlett Learning, LLC NOT FOR SALE OR DISTRIBUTION NOT FOR SALE OR DISTRIBUTION The operating system is an essential part of a computer system; it is an intermediary component between the application programsand the hardware. The ultimate purpose of an operating system is twofold: (1) to provide various services to users’ programs © Jones & Bartlettand (2) toLearning, control the LLC functioning of the computer© system Jones hardware & Bartlett in an Learning, efficient and LLC NOT FOR SALEeffective OR manner.DISTRIBUTION NOT FOR SALE OR DISTRIBUTION Thischapter presentsthe basicconceptsand the abstract views of operating sys- tems. This preliminary material is important in understanding more clearly the com- plexities of the structure of operating systems and how the various services are provided. General and brief referencesto Unix and Windowsare included throughout the chapter. © Jones & Bartlett Learning,Appendix LLC A presents a detailed explanation© Jones & of theBartlett Linux commands.Learning, LLC NOT FOR SALE OR DISTRIBUTION NOT FOR SALE OR DISTRIBUTION 1.1.1 Software Components A program is a sequence of instructions that enables a computer to execute a specific task. Before a program executes, it has to be translated from its original text form (source© Jones program) & Bartlett into a Learning, machine language LLC program. The program© thenJones needs & Bartlett to be Learning, LLC linkedNOT andFOR loaded SALE into OR memory. DISTRIBUTION NOT FOR SALE OR DISTRIBUTION The software components are the collection of programsthat execute in the com- puter. Theseprogramsperform computationsand control, manage, and carry out other important tasks. There are two general types of software components: © Jones & Bartlett• System Learning, software LLC © Jones & Bartlett Learning, LLC NOT FOR SALE OR DISTRIBUTION NOT FOR SALE OR DISTRIBUTION • Application software 1 © Jones & Bartlett Learning, LLC. NOT FOR SALE OR DISTRIBUTION. ©✐ Jones & Bartlett Learning, LLC © Jones & Bartlett Learning, LLC ✐ NOT FOR SALE OR DISTRIBUTION NOT FOR SALE OR DISTRIBUTION ✐ ✐ ✐ ✐ “26341˙CH01˙Garrido” — 2011/6/2 — 12:58 — page2—#4 ✐ ✐ © Jones & Bartlett Learning, LLC © Jones & Bartlett Learning, LLC NOT FOR SALE OR DISTRIBUTION NOT FOR SALE OR DISTRIBUTION 2 Chapter 1 Basic Concepts of Operating Systems System© Jones software & Bartlettisthe setof Learning, programsthat LLC control the activitiesand functionsof© Jones the & Bartlett Learning, LLC variousNOT hardware FOR components,SALE OR programmingDISTRIBUTION tools and abstractions, andNOT other FOR utilities SALE OR DISTRIBUTION to monitor the state of the computer system. This software forms an environment for the programmersto develop and execute their programs(collectively known asapplication software). There are actually two types of users: application programmers and end users. The most important part of system software is the operating system (OS) that © Jones directly& Bartlett controls Learning, and manages LLC the hardware resources© of Jones the computer. & Bartlett The OSLearning, also LLC NOT FORprovides SALE a OR set ofDISTRIBUTION services to the user programs. The mostNOT common FOR examples SALE of OR operating DISTRIBUTION systems are Linux, Unix, Windows, MacOS, and OS/2. Application software are the user programs and consists of those programs that solve specific problems for the users and execute under the control of the operating system. Application programsare developed by individualsand organizationsfor solvingspecific © Jones & Bartlett Learning,problems. LLC © Jones & Bartlett Learning, LLC NOT FOR SALE OR DISTRIBUTION NOT FOR SALE OR DISTRIBUTION 1.2 Operating Systems An operating© Jones system & Bartlett (OS) is aLearning, large and complex LLC set of system programs© Jones that control & Bartlett Learning, LLC the variousNOT operationsFOR SALE of a OR computer DISTRIBUTION system and provide a collection of servicesNOT FOR to other SALE OR DISTRIBUTION (user) programs. The purpose of an operating system involves two key goals: • Availability of a convenient, easy-to-use, and powerful set of services that are provided to the users and the application programs in the computer system © Jones & Bartlett• Management Learning, of the computerLLC resources in the most© Jones efficient & manner Bartlett Learning, LLC NOT FOR SALE OR DISTRIBUTION NOT FOR SALE OR DISTRIBUTION Application and system programmers directly or indirectly communicate with the op- erating system in order to request some of these services. The services provided by an operating system are implemented as a large set of system functions that include scheduling of programs, memory management, device © Jones & Bartlett Learning,management, LLC file management, network© management, Jones & Bartlett and other Learning, more advanced LLC services NOT FOR SALE OR DISTRIBUTIONrelated to protection and security. TheNOT operating FOR SALE system OR is also DISTRIBUTION considered a huge resource manager and performs a variety of services as efficiently as possible to ensure the desired performance of the system. Figure 1.1 shows an external view of a computer system. It illustrates the pro- grammers and end users communicating with the operating system and other system software.© Jones & Bartlett Learning, LLC © Jones & Bartlett Learning, LLC TheNOT most FOR important SALE activeOR DISTRIBUTION resource in the computer system is theNOT CPU. FOR Other SALE OR DISTRIBUTION important resources are memory and I/O devices. Allocation and deallocation of all resources in the system are handled by various resource managers of the operating system. General-purpose operating systems support two general modes of operation: (1) user © Jones &mode Bartlett and (2) Learning, kernel mode, LLC which is sometimes called the© supervisor,Jones & protected,Bartlett Learning, or priv- LLC NOT FORilege SALE mode. OR A userDISTRIBUTION process will normally execute in userNOT mode. FOR Some SALE instructions, OR DISTRIBUTION such aslow-level I/O functionsand memory accesstospecial areaswhere the OS maintains © Jones & Bartlett Learning, LLC. NOT FOR SALE OR DISTRIBUTION. ©✐ Jones & Bartlett Learning, LLC © Jones & Bartlett Learning, LLC ✐ NOT FOR SALE OR DISTRIBUTION NOT FOR SALE OR DISTRIBUTION ✐ ✐ ✐ ✐ “26341˙CH01˙Garrido” — 2011/6/2 — 12:58 — page3—#5 ✐ ✐ © Jones & Bartlett Learning, LLC © Jones & Bartlett Learning, LLC NOT FOR SALE OR DISTRIBUTION NOT FOR SALE OR DISTRIBUTION 1.2 Operating Systems 3 © Jones & Bartlett Learning, LLC © Jones & Bartlett Learning, LLC End Application NOT FOR SALEusers OR DISTRIBUTIONprograms NOT FOR SALE OR DISTRIBUTION Application Other system programmers programs © Jones & Bartlett Learning, LLC © Jones & Bartlett Learning, LLC NOT FOR SALE OR DISTRIBUTION NOT FOR SALE OR DISTRIBUTION Operating System system programmers © Jones & Bartlett Learning, LLC © JonesHardware & Bartlett Learning, LLC system NOT FOR SALE OR DISTRIBUTION NOT FOR SALE OR DISTRIBUTION Figure 1.1 An external view of a computer system. © Jones & Bartlett Learning, LLC © Jones & Bartlett Learning, LLC itsNOT data FOR structures, SALE can OR execute DISTRIBUTION only in kernel mode. As such, theNOT OS in FOR kernel SALE mode OR DISTRIBUTION has direct control of the computer system. © Jones1.2.1 & Bartlett Operating Learning, System LLC Interfaces © Jones & Bartlett Learning, LLC NOT FOR SALEUsers OR and DISTRIBUTION application programmers can communicateNOT with FOR an operating SALE OR system DISTRIBUTION through itsinterfaces.There are three general levelsof interfacesprovided by an operating system: • Graphical user interface (GUI) © Jones & Bartlett Learning, LLC © Jones & Bartlett Learning, LLC NOT FOR SALE OR DISTRIBUTION• Command line interpreter (alsoNOT called FOR the SALE shell) OR DISTRIBUTION • System-call interface Figure 1.2 illustrates the basic structure of an operating system and shows the three© Jones levels & of Bartlett interfaces, Learning, which are found LLC immediately above the© kernel. Jones The & highest Bartlett Learning, LLC levelNOT is FOR the graphical SALE OR user DISTRIBUTION interface (GUI), which allows I/O interactionNOT FOR with SALE a user OR DISTRIBUTION through intuitive icons, menus, and other graphical objects. With these objects, the user interacts with the operating system in a relatively easy and convenient manner— for example, using the click of a mouse to select an option or command. The most common GUI examplesare the Windowsdesktopand the X-Window in Unix. © Jones & BartlettThe Learning, user at this LLC level is completely separated© fromJones any & intrinsic Bartlett detail Learning, about the LLC NOT FOR SALEunderlying OR DISTRIBUTION system. This level of operating system interfaceNOT FOR is not SALE considered OR anDISTRIBUTION essential part of the operating system; it is rather an add-on system software component. © Jones & Bartlett
Load more

Recommended publications
  • Software Tools: a Building Block Approach
    SOFTWARE TOOLS: A BUILDING BLOCK APPROACH NBS Special Publication 500-14 U.S. DEPARTMENT OF COMMERCE National Bureau of Standards ] NATIONAL BUREAU OF STANDARDS The National Bureau of Standards^ was established by an act of Congress March 3, 1901. The Bureau's overall goal is to strengthen and advance the Nation's science and technology and facilitate their effective application for public benefit. To this end, the Bureau conducts research and provides: (1) a basis for the Nation's physical measurement system, (2) scientific and technological services for industry and government, (3) a technical basis for equity in trade, and (4) technical services to pro- mote public safety. The Bureau consists of the Institute for Basic Standards, the Institute for Materials Research, the Institute for Applied Technology, the Institute for Computer Sciences and Technology, the Office for Information Programs, and the ! Office of Experimental Technology Incentives Program. THE INSTITUTE FOR BASIC STANDARDS provides the central basis within the United States of a complete and consist- ent system of physical measurement; coordinates that system with measurement systems of other nations; and furnishes essen- tial services leading to accurate and uniform physical measurements throughout the Nation's scientific community, industry, and commerce. The Institute consists of the Office of Measurement Services, and the following center and divisions: Applied Mathematics — Electricity — Mechanics — Heat — Optical Physics — Center for Radiation Research — Lab- oratory Astrophysics^ — Cryogenics^ — Electromagnetics^ — Time and Frequency*. THE INSTITUTE FOR MATERIALS RESEARCH conducts materials research leading to improved methods of measure- ment, standards, and data on the properties of well-characterized materials needed by industry, commerce, educational insti- tutions, and Government; provides advisory and research services to other Government agencies; and develops, produces, and distributes standard reference materials.
    [Show full text]
  • Employee Management System
    School of Mathematics and Systems Engineering Reports from MSI - Rapporter från MSI Employee Management System Kancho Dimitrov Kanchev Dec MSI Report 06170 2006 Växjö University ISSN 1650-2647 SE-351 95 VÄXJÖ ISRN VXU/MSI/DA/E/--06170/--SE Abstract This report includes a development presentation of an information system for managing the staff data within a small company or organization. The system as such as it has been developed is called Employee Management System. It consists of functionally related GUI (application program) and database. The choice of the programming tools is individual and particular. Keywords Information system, Database system, DBMS, parent table, child table, table fields, primary key, foreign key, relationship, sql queries, objects, classes, controls. - 2 - Contents 1. Introduction…………………………………………………………4 1.1 Background……………………………………………………....................4 1.2 Problem statement ...…………………………………………………….....5 1.3 Problem discussion………………………………………………………....5 1.4 Report Overview…………………………………………………………...5 2. Problem’s solution……………………………………………….....6 2.1 Method...…………………………………………………………………...6 2.2 Programming environments………………………………………………..7 2.3 Database analyzing, design and implementation…………………………10 2.4 Program’s structure analyzing and GUI constructing…………………….12 2.5 Database connections and code implementation………………………….14 2.5.1 Retrieving data from the database………………………………....19 2.5.2 Saving data into the database……………………………………...22 2.5.3 Updating records into the database………………………………..24 2.5.4 Deleting data from the database…………………………………...26 3. Conclusion………………………………………………………....27 4. References………………………………………………………...28 Appendix A: Programming environments and database content….29 Appendix B: Program’s structure and code Implementation……...35 Appendix C: Test Performance…………………………………....56 - 3 - 1. Introduction This chapter gives a brief theoretical preview upon the database information systems and goes through the essence of the problem that should be resolved.
    [Show full text]
  • Software Requirements Specification to Distribute Manufacturing Data
    NIST Advanced Manufacturing Series 300-2 Software Requirements Specification to Distribute Manufacturing Data Thomas Hedberg, Jr. Moneer Helu Marcus Newrock This publication is available free of charge from: https://doi.org/10.6028/NIST.AMS.300-2 NIST Advanced Manufacturing Series 300-2 Software Requirements Specification to Distribute Manufacturing Data Thomas Hedberg, Jr. Moneer Helu Systems Integration Division Engineering Laboratory Marcus Newrock Office of Data and Informatics Material Measurement Laboratory This publication is available free of charge from: https://doi.org/10.6028/NIST.AMS.300-2 December 2017 U.S. Department of Commerce Wilbur L. Ross, Jr., Secretary National Institute of Standards and Technology Walter Copan, NIST Director and Under Secretary of Commerce for Standards and Technology SRS to Distribute Manufacturing Data Hedberg, Helu, and Newrock ______________________________________________________________________________________________________ Contents 1 Introduction 1 1.1 Purpose ...................................... 1 1.2 Disclaimer ..................................... 1 This publication is available free of charge from: https://doi.org/10.6028/NIST.AMS.300-2 1.3 Scope ....................................... 1 1.4 Acronyms and abbreviations ........................... 1 1.5 Verbal Forms ................................... 3 1.5.1 Must .................................... 3 1.5.2 Should ................................... 3 1.5.3 May .................................... 3 1.6 References ....................................
    [Show full text]
  • How Era Develops Software
    How eRA Develops Software Executive Summary: In an organized, iterative, carefully documented manner, eRA has built a dense infrastructure of methodology, standards, and procedures to underpin the development of a reliable enterprise system for electronic research administration. For software development and quality assurance, NIH has relied thus far solely on contractors. Now the retirement of the legacy IMPAC system is freeing up NIH programmers to join the development team. eRA’s methodology combines the classical Waterfall method and the prototype-oriented Spiral method. It proceeds in three phases: 1. Definition Phase: systems analysis and software development analysis; 2. Development Phase: software design, code generation, and testing; and 3. Maintenance Phase: perfective maintenance and other kinds of maintenance, documentation, and training. To capture the needs of users at every step, eRA employs focus groups, user groups, and the group advocates. Key features of the process are the use of database and tools technology from Oracle and reliance on a strongly modular approach that permits systematic upgrading of modules on a regular basis. End Summary ***** For eRA, developing software is a mission-critical business. With some 576,000,000 transactions taking place annually in IMPAC II and Commons, the functioning of NIH’s extramural grant and contract system relies on a dependable and effective software development process. eRA has built a dense project infrastructure (see figure) to ensure the overall integrity of the system. Other features of the project also contribute: •= for database technology, we rely on Oracle, a leading vendor with robust products; •= our strongly modular approach has enabled us better to target the needs of particular user groups while reducing the complexity of each piece of the project; and •= we have moved ever farther toward empowering users and involving them at every step.
    [Show full text]
  • What Does the Software Requirement Specification for Local E- Government of Citizen Database Information System? an Analysis Using ISO/IEC/IEEE 29148 – 2011
    Journal of Physics: Conference Series PAPER • OPEN ACCESS What does the software requirement specification for local E- Government of citizen database information system? An analysis using ISO/IEC/IEEE 29148 – 2011 To cite this article: M Susilowati et al 2019 J. Phys.: Conf. Ser. 1402 022087 View the article online for updates and enhancements. This content was downloaded from IP address 113.190.230.192 on 07/01/2021 at 18:25 4th Annual Applied Science and Engineering Conference IOP Publishing Journal of Physics: Conference Series 1402 (2019) 022087 doi:10.1088/1742-6596/1402/2/022087 What does the software requirement specification for local E- Government of citizen database information system? An analysis using ISO/IEC/IEEE 29148 – 2011 M Susilowati1, *, M Ahsan2 and Y Kurniawan1 1 Program Studi Sistem Informasi, Fakultas Sains dan Teknologi, Universitas Ma Chung, Villa Puncak Tidar Blok N-1, Malang, Jawa Timur, Indonesia 2 Program Studi Teknik Informatika, Fakultas Sains dan Teknologi, Universitas Kanjuruan, Jl. S. Supriadi, No. 48 Malang, Jawa Timur, Indonesia *[email protected] Abstract. The management citizen database is Improper and not up-to-date will results decisions that are not strategic for the village development process. Inappropriate citizen data also results in long-term ineffective local government planning processes. Such as the problem of forecasting or predicting the level of growth of citizens as well as the need for development services which are part of the medium-term long-term plans of local governments. Therefore they need requires a citizen database information system. In connection with the needs of citizen database information systems, this study provides a solution of analysing documents, namely the requirement specification software for citizen database information systems using the ISO / IEC / IEEE 29148 edition of 2011.
    [Show full text]
  • Software Development a Practical Approach!
    Software Development A Practical Approach! Hans-Petter Halvorsen https://www.halvorsen.blog https://halvorsen.blog Software Development A Practical Approach! Hans-Petter Halvorsen Software Development A Practical Approach! Hans-Petter Halvorsen Copyright © 2020 ISBN: 978-82-691106-0-9 Publisher Identifier: 978-82-691106 https://halvorsen.blog ii Preface The main goal with this document: • To give you an overview of what software engineering is • To take you beyond programming to engineering software What is Software Development? It is a complex process to develop modern and professional software today. This document tries to give a brief overview of Software Development. This document tries to focus on a practical approach regarding Software Development. So why do we need System Engineering? Here are some key factors: • Understand Customer Requirements o What does the customer needs (because they may not know it!) o Transform Customer requirements into working software • Planning o How do we reach our goals? o Will we finish within deadline? o Resources o What can go wrong? • Implementation o What kind of platforms and architecture should be used? o Split your work into manageable pieces iii • Quality and Performance o Make sure the software fulfills the customers’ needs We will learn how to build good (i.e. high quality) software, which includes: • Requirements Specification • Technical Design • Good User Experience (UX) • Improved Code Quality and Implementation • Testing • System Documentation • User Documentation • etc. You will find additional resources on this web page: http://www.halvorsen.blog/documents/programming/software_engineering/ iv Information about the author: Hans-Petter Halvorsen The author currently works at the University of South-Eastern Norway.
    [Show full text]
  • A Coordination Perspective on Software System Design
    A Coordination Perspective on Software System Design Chrysanthos Dellarocas Sloan School of Management Massachusetts Institute of Technology Room E53-315, Cambridge, MA 02139, USA Tel: +1 617 258-8115 [email protected] ABSTRACT application. In the rest of the paper, we will use the term In large software systems the identification and proper dependencies to refer to interconnection relationships and management of interdependencies among the pieces of a constraints among components of a software system. system becomes a central concern. Nevertheless, most As design moves closer to implementation, current design traditional programming languages and tools focus on and programming tools increasingly focus on components, representing components, leaving the description and leaving the description of interdependencies among management of interdependencies among components components implicit, and the implementation of protocols implicit, or distributed among the components. This paper for managing them fragmented and distributed in various identifies a number of problems with this approach and parts of the system. At the implementation level, software proposes a new perspective for designing software, which systems are sets of source and executable modules in one or elevates the representation and management of component more programming languages. Although modules come interdependencies to a distinct design problem. A core under a variety of names (procedures, packages, objects, element of the perspective is the development of design clusters etc.), they are all essentially abstractions for handbooks, which catalogue the most common kinds of components. interconnection relationships encountered in software systems, as well as sets of alternative coordination Most programming languages directly support a small set of protocols for managing them.
    [Show full text]
  • Development of an Its Data Management System
    DEVELOPMENT OF AN ITS DATA MANAGEMENT SYSTEM by Robert E. Brydia Assistant Research Scientist E-mail: [email protected] Shawn M. Turner Assistant Research Engineer E-mail: [email protected] William L. Eisele Assistant Research Scientist E-mail: [email protected] of the Texas Transportation Institute The Texas A&M University System College Station, Texas 77843-3135 Phone (409) 845-6002 Fax (409) 845-6008 and Jyh C. Liu Assistant Professor Department of Computer Science Texas A&M University E-mail: [email protected] Paper Prepared for Presentation and Publication at the North American Travel Monitoring Exhibition and Conference NATMEC 98 Charlotte, North Carolina May 1998 Note: This paper was originally presented at the Transportation Research Board’s 77th Annual Meeting, January 1998, Washington, DC. The paper will also be published in a forthcoming Transportation Research Record. ABSTRACT The intelligent transportation system (ITS) components being deployed in U.S. urban areas are producing vast amounts of data. These ITS data are often used for real-time operations and then discarded. Few transportation management centers (TMCs) have any mechanism for sharing the data resources among other transportation groups or agencies within the same jurisdiction. Meanwhile, transportation analysts and researchers often struggle to obtain accurate, reliable data about existing transportation performance and patterns. This paper presents the development of an ITS data management system (referred to as ITS DataLink) that is used to store, access, analyze, and present data from the TransGuide center in San Antonio, Texas. Data outputs are both tabular and graphical in nature. There are no user costs associated with system except for an Internet connection.
    [Show full text]
  • Software Requirement Specification
    INRIA INNOVATION LAB CERTIVIBE V1.0 SOFTWARE REQUIREMENT SPECIFICATION Document Approval Name Function Date Originated by Reviewed by Reviewed by TABLE OF CONTENTS 1. Purpose .................................................................................................. 3 2. Scope ..................................................................................................... 3 3. References .............................................................................................. 3 4. Definitions ............................................................................................... 3 5. Abbreviations ........................................................................................... 4 6. Technical glossary ...................................................................................... 5 7. General Behavior ....................................................................................... 6 8. Functional requirement ............................................................................... 7 8.1 General Requirements ........................................................................... 7 8.2 Acquisition Requirements ...................................................................... 12 8.3 File I/O Requirements .......................................................................... 14 8.4 Data Generation Requirements ............................................................... 16 8.5 Data Aggregation Requirements .............................................................
    [Show full text]
  • Evaluating Database Management Systems
    EVALUATING DATABASE MANAGEMENT SYSTEMS: A FRAMEWORK AND APPLICATION TO THE VETERAN'S ADMINISTRATION HOSPITAL by MOHAMMAD DADASHZADEH S.B., Massachusetts Institute of Technology (1975) SUBMITTED IN PARTIAL FULFILLMENT OF THE REQUIREMENTS FOR THE DEGREE OF MASTER OF SCIENCE at the MASSACHUSETTS INSTITUTE OF TECHNOLOGY February, 1978 I J', Signature of Author: . .................. ... - v*......... Department of Electric Engineering and Computer Science, December 30, 1977 Certified by: ..... ...-------- ----....- Thesis Superviso - Accepted by: 0........... ................................ *.* Chairman, Departmental Committee on Graduate Students EVALUATING DATABASE MANAGEMENT SYSTEMS: A FRAMEWORK AND APPLICATION TO THE VETERAN'S ADMINISTRATION HOSPITAL by MOHAMMAD DADASHZADEH Submitted to the Department of Electrical Engineering and Computer Science on December 30, 1977, in partial fulfillment of the requirements for the degree of Master of Science. ABSTRACT The primary purpose of this thesis is to aid the database manage- ment system (DBMS) evaluation process by providing an example in a real-life setting - the design and implementation of a DBMS-based hospital information system. A guideline is presented in whose context the capabilities of a specific package, Generalized Information Management (GIM-II), are examined in detail. These capabilities are then evaluated in light of the requirements of a hospital information system. The design and implementation of a medical database and such hospital applications as patient scheduling and pharmacy are investigated. It is concluded that the GIM-II system can support a hospital information system. Thesis Supervisor: Stuart E. Madnick Title: Associate Professor of Management ACKNOWLEDGEMENTS I would like to express my gratitude to Professor Stuart Madnick for his guidance and extreme patience in supervising this thesis. I am indebted to my parents for their continued support, both financial and spiritual, throughout my academic years.
    [Show full text]
  • IEEE Recommended Practice for Software Requirements Speci~Cations
    IEEE Std 830-1998 (Revision of IEEE Std 830-1993) IEEE Recommended Practice for Software Requirements SpeciÞcations Sponsor Software Engineering Standards Committee of the IEEE Computer Society Approved 25 June 1998 IEEE-SA Standards Board Abstract: The content and qualities of a good software requirements specification (SRS) are de- scribed and several sample SRS outlines are presented. This recommended practice is aimed at specifying requirements of software to be developed but also can be applied to assist in the selec- tion of in-house and commercial software products. Guidelines for compliance with IEEE/EIA 12207.1-1997 are also provided. Keywords: contract, customer, prototyping, software requirements specification, supplier, system requirements specifications The Institute of Electrical and Electronics Engineers, Inc. 345 East 47th Street, New York, NY 10017-2394, USA Copyright © 1998 by the Institute of Electrical and Electronics Engineers, Inc. All rights reserved. Published 1998. Printed in the United States of America. ISBN 0-7381-0332-2 No part of this publication may be reproduced in any form, in an electronic retrieval system or otherwise, without the prior written permission of the publisher. IEEE Standards documents are developed within the IEEE Societies and the Standards Coordinat- ing Committees of the IEEE Standards Association (IEEE-SA) Standards Board. Members of the committees serve voluntarily and without compensation. They are not necessarily members of the Institute. The standards developed within IEEE represent a consensus of the broad expertise on the subject within the Institute as well as those activities outside of IEEE that have expressed an inter- est in participating in the development of the standard.
    [Show full text]
  • Systems Engineering for Software Engineers Ian Sommerville Computing Department, Lancaster University, Lancaster LA1 4YR, UK [email protected]
    Systems Engineering for Software Engineers Ian Sommerville Computing Department, Lancaster University, Lancaster LA1 4YR, UK [email protected] Abstract This paper describes how we have modified a software engineering stream within a computer science course to include broader concepts of systems engineering. We justify this inclusion by showing how many reported problems with large systems are not just software problems but relate to system issues such as hardware and operational processes. We describe what we mean by ‘systems engineering’ and go on to discuss the particular course structure which we have developed. We explain, in some detail, the contents of two specific systems engineering courses (Software Intensive Systems Engineering and Critical Systems Engineering) and discuss the problems and challenges we have faced in making these changes. In the Appendix, we provide details of the case studies which are used as linking themes in our courses. Introduction Software engineering gets a really bad press. All too often, we read horror stories of how software engineering projects have gone wrong with massive delays and cost overruns. The software ‘crisis’ which first emerged over 30 years ago is still claimed by some authors such as Pressman [1], who renames it as ‘software’s chronic affliction’, to be a reality of current software development. High-profile system failures such as the Denver Airport baggage handling system (in the USA) and the London Ambulance despatching system (in the UK) have been widely publicised. Software and the poor state of software engineering has been blamed for these failures. As an illustration of this, consider the reported problems with the Denver airport baggage handling system.
    [Show full text]