DOCSLIB.ORG

C4 Software Technology Reference Guide —A Prototype

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
C4 Software Technology Reference Guide —A Prototype Handbook CMU/SEI-97-HB-001 January 1997 C4 Software Technology Reference Guide —A Prototype Michael Bray, Lockheed Martin Maj David Luginbuhl, USAF, Air Force Office of Scientific Research Kimberly Brune, SEI William Mills, Lockheed Martin David A. Fisher, SEI Robert Rosenstein, SEI John Foreman, SEI Darleen Sadoski, GTE Capt Mark Gerken, USAF, Rome Laboratory James Shimp, E-System Jon Gross, SEI Edmond Van Doren, Kaman Sciences Capt Gary Haines, USAF, AFMC SSSG Cory Vondrak, TRW Elizabeth Kean, Rome Laboratory Unlimited distribution subject to the copyright. Software Engineering Institute Carnegie Mellon University Pittsburgh, Pennsylvania 15213 This report was prepared for the SEI Joint Program Office HQ ESC/AXS 5 Eglin Street Hanscom AFB, MA 01731-2116 The ideas and findings in this report should not be construed as an official DoD position. It is published in the interest of scientific and technical information exchange. FOR THE COMMANDER (signature on file) Thomas R. Miller, Lt Col, USAF SEI Joint Program Office This work is sponsored by the U.S. Department of Defense. Copyright © 1997 by Carnegie Mellon University. Permission to reproduce this document and to prepare derivative works from this document for internal use is granted, provided the copyright and “No Warranty” statements are included with all reproductions and derivative works. Requests for permission to reproduce this document or to prepare derivative works of this document for external and commercial use should be addressed to the SEI Licensing Agent. NO WARRANTY THIS CARNEGIE MELLON UNIVERSITY AND SOFTWARE ENGINEERING INSTITUTE MATERIAL IS FURNISHED ON AN “AS-IS” BASIS. CARNEGIE MELLON UNIVERSITY MAKES NO WARRAN- TIES OF ANY KIND, EITHER EXPRESSED OR IMPLIED, AS TO ANY MATTER INCLUDING, BUT NOT LIMITED TO, WARRANTY OF FITNESS FOR PURPOSE OR MERCHANTABILITY, EXCLUSIVITY, OR RESULTS OBTAINED FROM USE OF THE MATERIAL. CARNEGIE MELLON UNIVERSITY DOES NOT MAKE ANY WARRANTY OF ANY KIND WITH RESPECT TO FREEDOM FROM PATENT, TRADEMARK, OR COPYRIGHT INFRINGEMENT. This work was created in the performance of Federal Government Contract Number F19628-95-C-0003 with Carnegie Mellon University for the operation of the Software Engineering Institute, a federally funded research and development center. The Government of the United States has a royalty-free government-purpose license to use, duplicate, or disclose the work, in whole or in part and in any manner, and to have or permit others to do so, for government purposes pursuant to the copyright license under the clause at 52.227-7013. This document is available through Research Access, Inc., 800 Vinial Street, Pittsburgh, PA 15212. Phone: 1-800-685-6510. FAX: (412) 321-2994. RAI also maintains a World Wide Web home page. The URL is http://www.rai.com Copies of this document are available through the National Technical Information Service (NTIS). For informa- tion on ordering, please contact NTIS directly: National Technical Information Service, U.S. Department of Commerce, Springfield, VA 22161. Phone: (703) 487-4600. This document is also available through the Defense Technical Information Center (DTIC). DTIC provides ac- cess to and transfer of scientific and technical information for DoD personnel, DoD contractors and potential con- tractors, and other U.S. Government agency personnel and their contractors. To obtain a copy, please contact DTIC directly: Defense Technical Information Center, Attn: FDRA, Cameron Station, Alexandria, VA 22304- 6145. Phone: (703) 274-7633. Use of any trademarks in this report is not intended in any way to infringe on the rights of the trademark holder. Table of Contents Foreword to the First Edition iii 1 Introduction 1 1.1 Background 1 1.1.1 Scope 1 1.1.2 Vision 1 1.1.3 Goal 2 1.1.4 Limitations/Caveats 2 1.1.5 Target Audiences 4 1.2 Using the Document 5 2 Taxonomies 7 2.1 Overview and Purpose 7 2.1.1 General Taxonomy Structure 7 2.1.2 Using the Taxonomies 8 2.2 Application Taxonomy 9 2.2.1 Introduction 9 2.2.2 Graphical Representation 10 2.2.3 Textual Representation 16 2.2.4 Taxonomy-Based Directory to Technology Descriptions 19 2.3 Quality Measures Taxonomy 29 2.3.1 Introduction 29 2.3.2 Graphical Representation 30 2.3.3 Textual Representation 34 2.3.4 Taxonomy-Based Directory to Technology Descriptions 36 3 Technology Descriptions 43 3.1 Defining Software Technology 43 3.2 Technology Categories 44 3.3 Template for Technology Descriptions 45 3.4 The Technology Adoption Challenge 51 3.5 Alphabetical List of Technology Descriptions 59 References 391 Glossary 393 Appendix A Submitting Information for Subsequent Editions 407 Appendix B User Feedback 409 Appendix C Scenarios of Use 411 Keyword Index 417 CMU/SEI-97-HB-001 i ii CMU/SEI-97-HB-001 Foreword to the First Edition This inaugural edition of the C4 Software Technology Reference Guide1 marks the completion of an 11-month project undertaken by the Software Engineering Institute (SEI) and industry participants for the United States Air Force acquisition community. It includes the latest avail- able information on approximately 60 software technologies. Even though this initial version tends to have a narrow customer focus, our hope is that this guide, with future editions, will become a common knowledge base and a valuable reference for the software engineering community. To our knowledge, no other document exists that provides this type of software technology information in one place. Because software is a constantly-changing field, we are seeking sponsors, partners, and com- munity participation to expand this document and publish descriptions of software technology on at least an annual basis. The long-term goal is a continuously growing and evolving Web- based reference guide of software technologies. This goal can only be reached with active participation and direct support from the broad software community. Please refer to Appendi- ces A and B for details on how to contribute. The document was developed as a cooperative effort among the SEI, six defense contractors, and three Air Force organizations. Project members were physically co-located during various intervals of the project, and also worked from geographically dispersed locations. Defense contractors and Air Force personnel authored technology descriptions and main- tained/evolved the taxonomies and taxonomy-based directories. The SEI members estab- lished overall project direction, wrote various technology descriptions and sections, and integrated and edited the document extensively. We functioned as a cooperative team of in- dividual contributors with a goal of technical accuracy and credibility. Team members were: SEI Kimberly Brune David Fisher John Foreman Jon Gross Robert Rosenstein Defense Contractors Michael Bray, Lockheed Martin William Mills, Loral (Lockheed Martin) Darleen Sadoski, GTE James Shimp, E-Systems Edmond Van Doren, Kaman Sciences 1. We have used other names for the document during earlier phases of the project. These include the Software Technology Roadmap and the Structured Survey of Software Technology (SSST). CMU/SEI-97-HB-001 iii Cory Vondrak, TRW Air Force Capt Mark Gerken, Rome Laboratory Capt Gary Haines, AFMC SSSG Elizabeth Kean, Rome Laboratory Maj David Luginbuhl, Air Force Office of Scientific Research In addition, other individuals contributed to the document by writing and/or reviewing technol- ogy descriptions. These contributions are acknowledged in the specific technology descrip- tions. Development The project entailed an intense data collection and writing effort by the authors. Because of the tight project schedule, the project team initially took an “opportunistic” approach to soft- ware technology topic coverage: The authors focused on software technologies in their areas of expertise, in areas where technical experts were accessible, and in areas where abundant supporting material existed. Topics selected were of significant interest to our targeted user community and/or were emerging technologies getting a lot of attention in the software com- munity. Data collection approaches included the following: • literature search and the World Wide Web • previous studies, surveys, technical assessments, forecasts • program briefings from DARPA, NSF, ATP, NIST, and many others • interviews with researchers and technology developers in industry, government, and academia • broad-based solicitation of written input Each software technology description went through a rigorous review process which often in- cluded outside area experts. For the structure of the document, the Physician’s Desk Refer- ence (PDR), published by Medical Economics, provided us with a valuable model for overall organization. We referenced it often in the early days of the project. To ensure the develop- ment of a quality product, we also organized two formal outside reviews of the entire docu- ment. The first review team primarily focused on the technical validity and content of the document, while the second review team provided an executive management perspective on the utility of the document. Recommendations from these reviews were taken into consider- ation as we fine-tuned the document for this prototype publication. We greatly appreciate the time and valuable input of the following review team members. Their insightful critique and recommendations significantly improved the quality of this initial publi- cation. iv CMU/SEI-97-HB-001 Review Team #1 Participants Dr. William L. Scherlis, Review Team Chair, Carnegie Mellon University Ms. Christine Anderson, PL/VTQ Dr. David J. Carney, Software Engineering Institute Dr. John B. Goodenough, Software Engineering Institute Lt. Col. Mike Goyden, SSSG/SMW Col. Richard R. Gross, PhD, USAF, Defense Information Systems Agency Lt. Col. J. Greg Hanson, PhD, HQ USAF/SCTS Dr. Larry G. Jones, Software Engineering Institute Mr. Mark H. Klein, Software Engineering Institute Maj.George Newberry, SAF/AQRE Ms. Linda M. Northrop, Software Engineering Institute Lt. Col. Chris Ruminski, ESC/SRG Dr. Howard E. Shrobe, Defense Advanced Research Projects Agency (DARPA) Mr. John Willison, CECOM, Center for Software Engineering Review Team #2 Participants Dr. Harold W. Sorenson, Review Team Chair, The MITRE Corporation Mr.
Load more

Recommended publications
  • Speakers' Bios
    Presenters' Biographies Keynote Presenters' Biographies Nicholas Negroponte Chairman, One Laptop per Child Chairman Emeritus, MIT Media Laboratory Nicholas is founder and Chairman of the One Laptop per Child non-profit Association. He is currently on leave from MIT, where he was co-founder and director of the MIT Media Laboratory, and the Hotel cut-off : Jerome B. Wiesner Professor of Media Technology. A graduate of October 27, 2006 MIT, Nicholas was a pioneer in the field of computer-aided design, and has been a member of the MIT faculty since 1966. Conceived in 1980, the Media Laboratory opened its doors in 1985. He is also author of the 1995 best seller, “Being Digital,” which has been Venue: translated into more than 40 languages. In the private sector, Nicholas serves on the board of directors for Motorola, Inc. and as general partner in a venture capital firm specializing in digital technologies for information and entertainment. He has provided Hilton Washington start-up funds for more than 40 companies, including Wired Dulles Airport magazine. Presenters' Biographies Dr. Deborah Anderson Researcher, University of California Berkeley Dr. Deborah Anderson is a researcher in the Dept. of Linguistics at UC Berkeley and runs the UC Berkeley Script Encoding Initiative (and its NEH- sponsored sibling, the Universal Scripts Project). She is the UC Berkeley representative to the Unicode Consortium, and serves as Liaison for the Linguistic Society of America. Having received her Ph.D. from UCLA in Indo- European Studies, she also edits the UCLA Indo-European Studies Bulletin, and promotes the use of Unicode generally.
    [Show full text]
  • Derivation of the Required Elements for a Definition of the Term Middleware
    Rochester Institute of Technology RIT Scholar Works Theses 2002 Derivation of the required elements for a definition of the term middleware Maya Mathew Follow this and additional works at: https://scholarworks.rit.edu/theses Recommended Citation Mathew, Maya, "Derivation of the required elements for a definition of the term middleware" (2002). Thesis. Rochester Institute of Technology. Accessed from This Thesis is brought to you for free and open access by RIT Scholar Works. It has been accepted for inclusion in Theses by an authorized administrator of RIT Scholar Works. For more information, please contact [email protected]. Derivation of the Required Elements for a Definition of the Term Middleware By Maya Mathew Thesis submitted in partial fulfillment ofthe requirements for the degree ofMaster ofScience in Information Technology Rochester Institute ofTechnology B. Thomas Golisano College Of Computing and Information Sciences May 2002 - 1 - Rochester Institute of Technology B. Thomas Golisano College Of Computing and Information Sciences Master of Science in Information Technology Thesis Approval Form Student Name: Maya Mathew Thesis Title: Derivation of the Required Elements for a Definition of the Term Middleware Thesis Committee Name Signature Date Prof. William Stratton Chair Prof. Andy Phelps ?-/ z /qL-.-- Committee Member I I :-.P.:...::ro~f.~J~e;.:..:.ff...::L:.:::a.=..:sk~y ~ 17, d-fIoJ--. Committee Member ~ Thesis Reproduction Permission Form Rochester Institute of Technology B. Thomas Golisano College Of Computing and Information Sciences Derivation of the Required Elements For a Definition of the Term Middleware I, Maya Mathew, hereby grant permission to the Wallace Library of the Rochester Institute of Technology to reproduce my thesis in whole or in part.
    [Show full text]
  • Distributed Communication Methods and Role-Based Access Control For
    Distributed Communication Methods and Role*Based Access Controi for Use in Heaith Care Applications Joseph Poole John Barkley Kevin Brady Anthony Cincotta Wayne Salamon U.S. DEPARTMENT OF COMMERCE Technology Administration National Institute of Standards and Technology Gaithersburg, MD 20899 QC 100 .U56 NIST NO. 5820 1996 if 1 •t r i I i j •? f Distributed Communication Methods and Roie-Based Access Controi for Use in Health Care Appiications Joseph Poole John Barkley Kevin Brady Anthony Cincotta Wayne Salamon U.S. DEPARTMENT OF COMMERCE Technology Administration National Institute of Standards and Technology Gaithersburg, MD 20899 April 1996 U.S. DEPARTMENT OF COMMERCE Michael Kantor, Secretary TECHNOLOGY ADMINISTRATION Mary L. Good, Under Secretary for Technology NATIONAL INSTITUTE OF STANDARDS AND TECHNOLOGY Arati Prabhakar, Director Abstract The use of software in the health care industry is becoming of increasing importance. One of the major roadblocks to efficient health care is the fact that important information is distributed across many sites. These sites can be located across a significant area. The problem is to provide a uniform mechanism to integrate this information. This paper documents the results of an investigation into the suitability of several different distributed access mechanisms. Five methods were examined: the Common Object Request Broker (CORBA), Object Linking and Embedding (OLE), remote procedure call (RPC), remote database access (SQL/RDA) and Protocol Independent Interfaces (PH, we specifically examined sockets). These mechanisms were compared with regard for use in health care applications. In particular, the following capabilities were compared: • Ease of use by the developer • Class of applications for which the technology is particularly effective in developing • Security capabilities • Protocols utilized • Performance of the transport mechanism.
    [Show full text]
  • Teradata Call-Level Interface Version 2 Reference for Channel-Attached Systems
    Teradata Call-Level Interface Version 2 Reference for Channel-Attached Systems Release 13.10 B035-2417-020A February 2010 The product or products described in this book are licensed products of Teradata Corporation or its affiliates. Teradata, BYNET, DBC/1012, DecisionCast, DecisionFlow, DecisionPoint, Eye logo design, InfoWise, Meta Warehouse, MyCommerce, SeeChain, SeeCommerce, SeeRisk, Teradata Decision Experts, Teradata Source Experts, WebAnalyst, and You’ve Never Seen Your Business Like This Before are trademarks or registered trademarks of Teradata Corporation or its affiliates. Adaptec and SCSISelect are trademarks or registered trademarks of Adaptec, Inc. AMD Opteron and Opteron are trademarks of Advanced Micro Devices, Inc. BakBone and NetVault are trademarks or registered trademarks of BakBone Software, Inc. EMC, PowerPath, SRDF, and Symmetrix are registered trademarks of EMC Corporation. GoldenGate is a trademark of GoldenGate Software, Inc. Hewlett-Packard and HP are registered trademarks of Hewlett-Packard Company. Intel, Pentium, and XEON are registered trademarks of Intel Corporation. IBM, CICS, RACF, Tivoli, and z/OS are registered trademarks of International Business Machines Corporation. Linux is a registered trademark of Linus Torvalds. LSI and Engenio are registered trademarks of LSI Corporation. Microsoft, Active Directory, Windows, Windows NT, and Windows Server are registered trademarks of Microsoft Corporation in the United States and other countries. Novell and SUSE are registered trademarks of Novell, Inc., in the United States and other countries. QLogic and SANbox are trademarks or registered trademarks of QLogic Corporation. SAS and SAS/C are trademarks or registered trademarks of SAS Institute Inc. SPARC is a registered trademark of SPARC International, Inc. Sun Microsystems, Solaris, Sun, and Sun Java are trademarks or registered trademarks of Sun Microsystems, Inc., in the United States and other countries.
    [Show full text]
  • Database Administration Guide for SAP on IBM Db2 for Linux, UNIX, and Windows Company
    Administration Guide | PUBLIC Document Version: 2.5 – 2021-09-23 Database Administration Guide for SAP on IBM Db2 for Linux, UNIX, and Windows company. All rights reserved. All rights company. affiliate THE BEST RUN 2021 SAP SE or an SAP SE or an SAP SAP 2021 © Content 1 Introduction................................................................7 1.1 Document History............................................................ 8 1.2 Naming Conventions..........................................................10 2 Administration Tools and Tasks.................................................12 2.1 Administration Tools..........................................................12 2.2 Administration Tasks..........................................................13 3 Architectural Overview.......................................................16 3.1 SAP Application Server for ABAP.................................................16 3.2 SAP Application Server for Java..................................................17 3.3 Db2 Components............................................................18 3.4 Db2 Client Connectivity........................................................19 4 User Management and Security................................................ 21 4.1 SAP System Users and Groups...................................................21 Access Authorizations for Db2 Directories and Database-Related Files....................25 4.2 Role-Based Security Concept for Database Users..................................... 27 Database Roles for
    [Show full text]
  • Welcome to Discussion on Ingres Code Architecture
    Welcome to discussion on Ingres Code Architecture. In this presentation we will discuss the • Various components of Ingres database, • Their interrelationship and • Their code architecture. 1 To an Ingres user, an Ingres database stores and retrieves data based on an SQL query. For example here is a screen shot of Ingres Terminal monitor session connected to database testdb. Here we wish to retrieve the details of all employees in a company. We enter our SQL query <Click To Animate > “Select * from emp” The database server processes the query <Click to Animate> 2 We obtain the results of our query. To understand the code architecture of Ingres. <Click Here> let us examine how Ingres processes this query <Click Here> 3 1. The Query is processed by Global Communications facility which communicates the data and results between the terminal monitor to the DBMS server. <Click Here to Animate> 2. The DBMS server and its associated processes process the query and send the results to the client through GCF. <Click Here to Animate> 3. Broadly categorizing we can summarize the code into • User interface facilities • Connectivity and Communications • DBMS server • And Utility libraries to interact with Operating system. 1. Ingres has several kinds of user interface for example 1. Embedded SQL precompiler for programmatic operations of database. 2. Ingres applications like, SQL Terminal Monitor, Query by forms (QBF), Report by Forms (RBF), VISION etc. 3. We have Ingres Internet Commerce (ICE) for web deployment. These user interfaces and others can be commonly grouped as Front End for Ingres. • Similarly in connectivity tools we have • Java Database connectivity (JDBC) driver • Open Database connectivity driver (ODBC) driver • Dot Net Data provider • Open API a C api to Ingres etc.
    [Show full text]
  • The US Government's Open System Environment Profile OSE/1 Version
    C NIST Special Publication 500-21 Computer Systems APPLICATION PORTABILITY PROFILE Technology (APP) The U.S. Government's U.S. DEPARTMENT OF COMMERCE Technology Administration Open System Environment Profile National Institute of Standards and Technology OSE/1 Version 2.0 Nisr NAT L !NST."OF STAND i TECH R.I.C. llllllllllllllllllll NIST PUBLICATIONS AlllDM QEETfll APPLICA TION PORTABILITYPROFILE j)JT)) The U S. Government's ^ k^Open System Environment IL Profile OSE/1 Version 2.0 -QG 100 .U57 #500-210 1993 7he National Institute of Standards and Technology was established in 1988 by Congress to "assist industry in the development of technology . needed to improve product quality, to modernize manufacturing processes, to ensure product reliability . and to facilitate rapid commercialization ... of products based on new scientific discoveries." NIST, originally founded as the National Bureau of Standards in 1901, works to strengthen U.S. industry's competitiveness; advance science and engineering; and improve public health, safety, and the environment. One of the agency's basic functions is to develop, maintain, and retain custody of the national standards of measurement, and provide the means and methods for comparing standards used in science, engineering, manufacturing, commerce, industry, and education with the standards adopted or recognized by the Federal Government. As an agency of the U.S. Commerce Department's Technology Administration, NIST conducts basic and applied research in the physical sciences and engineering and performs related services. The Institute does generic and precompetitive work on new and advanced technologies. NIST's research facilities are located at Gaithersburg, MD 20899, and at Boulder, CO 80303.
    [Show full text]
  • MLS DBMS Interoperability Study*
    MLS DBMS Interoperability Study* Rae K. Burns, AGCS, Inc. Yi-Fang Koh, Raytheon Electronic Systems ESC/AXS, Building 1704, Hanscom AFB, MA 01731 burns/[email protected] Interoperability among heterogeneous databases is a fundamental requirement of many emerging Department of Defense (DoD) systems. Often these systems also have requirements for Multilevel-Secure (MLS) operation, where data is labeled to reflect its sensitivity level (e.g., UNCLASSIFIED, SECRET, etc.). The Air Force Rome Laboratory MLS Database Management System (DBMS) Interoperability Study has surveyed the available Commercial- Off-The-Shelf (COTS) products supporting interoperability and tested several of them in a multilevel environment. We selected representative products and implemented test scenarios in the ESC/AXS Security Products Transition Analysis Facility (STAF). Our test environment included three commercial MLS DBMS products (Trusted ORACLE7, Informix Online/Secure, and Sybase Secure SQL Server) on several different MLS Operating System (OS) platforms. We also employed “system high” platforms running standard versions of the DBMS and OS products. We successfully moved data to and from the MLS databases using different COTS interoperability solutions. This paper describes our testing efforts and summarizes the lessons learned. 1. Introduction The Multilevel Secure Database Management System Interoperability Study was initiated by Air Force Rome Laboratory to expedite the transition of trusted database technology into operational Air Force C4I environments. The overall goal of the study is twofold: 1) To examine the theoretical basis for heterogeneous trusted database interoperability, identify issues, and transition findings to the communities involved in future development (vendors, DoD users, and applicable standards groups). 2) To develop demonstrable examples of database interoperability that illustrate the advantages of MLS DBMS products in support of Air Force operational requirements for multilevel security.
    [Show full text]
  • MIT Laboratory for Computer Science Progress Report, July 1984-June
    l II t OFPY Massachusetts Institute of Technology Laboratory for Computer Science July 1984- Progress Report June 1985 22 00 N N N N DTIC ELECTE SEP2 7 199011 DISTRIBUTION STATEMENT A Apprmo,?d 'or public release; Dist budon Unbrrits-d Unclassified SECURITY CLASSIFICATION OF THIS PAGE REPORT DOCUMENTATION PAGE Ia. REPORT SECURITY CLASSIFICATION lb. RESTRICTIVE MARKINGS Unclassified 2a. SECURITY CLASSIFICATION AUTHORITY 3. DISTRIBUTION /AVAILABILITY OF REPORT Approved for public release; distribution 2b. DECLASSIFICATIONIDOWNGRADING SCHEDULE is unlimited. 4. PERFORMING ORGANIZATION REPORT NUMBER(S) 5. MONITORING ORGANIZATION REPORT NUMBER(S) MIT/LCS/PR-22 6a. NAME OF PERFORMING ORGANIZATION 6b. OFFICE SYMBOL 7a. NAME OF MONITORING ORGANIZATION MIT Lab for Computer Science (ifapplicable) Office of Naval Research/Dept. of Navy 6c. ADDRESS (Cty, State, and ZIP Code) 7b. ADDRESS (City, State, and ZIP Code) 545 Technology Square Information Systems Program Cambridge, MA 02139 Arlington, VA 22217 Ba. NAME OF FUNDING I SPONSORING 8b. OFFICE SYMBOL 9. PROCUREMENT INSTRUMENT IDENTIFICATION NUMBER ORGANIZATION (If applicable) DARPA/DOD I Sc. ADDRESS (City, State, and ZIP Code) 10. SOURCE OF FUNDING NUMBERS PROGRAM PROJECT TASK WORK UNIT 1400 Wilson Blvd. ELEMENT NO. NO. NO. ACCESSION NO. Arlington, VA 22217 11. TITLE (Include Security Classfication) MIT Laboratory for Computer Science Progress Report - 22 12. PERSONAL AUTHOR(S) Dertouzos, M.L. 13a. TYPE OF REPORT 113b. TIME COVERED 14. DATE OF REPORT (Year, Month, Day) IS. PAGE COUNT Technical /Proqress FROM 7/84 TO 6/_8_5 June 1985 266 16. SUPPLEMENTARY NOTATION 17. COSATI CODES 18. SUBJECT TERMS (Continue on revere if necesary and identify by block number) FIELD GROUP SUB-GROUP Computer Architecture, Computer Science, Computer Systems, Electrical Engineering, Networks.Theory of Computers, Programming Languages 19.
    [Show full text]
  • Networks for Competitive Advantage: People, Partners & Processes
    2007 MIT CIO Symposium networks for competitive advantage: People, Partners & Processes mit Kresge Auditorium 05.17.07 The MIT Sloan Alumni Club of Boston thanks the following sponsors who helped make this event possible: gold level sponsors silver level sponsors Dear Colleagues, On behalf of the MIT Center for Digital Business, I would like to welcome you to the 2007 MIT CIO Symposium. The Center is pleased to once again be your co-host for this event, along with the MIT Sloan Alumni Club of Boston. Our theme for the 2007 CIO Symposium is “Networks for Competitive Advantage: People, Partners and Processes.” The Internet has provided a new communication medium, a reliable and robust stage for global commerce, and an increasingly trusted platform for doing business enabling reliable business models built on real value propositions. Online teams of individuals and groups bid, win and complete software projects without ever having met anyone in the contracting company. Never has the business environment been more complex. What better place on earth than MIT to not only make sense of this networked world, but also to provide methods of analysis and understanding to take best advantage of the opportunities within it. Four titans from the Center for Digital Business and MIT Sloan will lead sessions during the day today. Erik Brynjolfsson, whose forte is measuring the impact of IT on the productivity of companies and information workers; Tom Malone, who pushes us into the future with his thoughtful vision of the decentralized work force and the power of “collective intelligence”; Glen Urban, media sponsors who is helping companies realize that the Internet is the ultimate medium for building personal relationships with customers; Peter Weill has counseled countless companies around the globe on how to generate real and measurable value from IT.
    [Show full text]
  • Embedded SQL Precompiling Embedded SQL Call Level Interface
    Embedded SQL Call level interface (CLI) Extract from C program: An application programming interface (API), i.e.itprovides a set of EXEC SQL BEGIN DECLARE SECTION; function calls. short DEPT, DNO; In the SQL standards wor ld, ‘‘CLI’’means ‘‘not Embedded SQL’’ char NAME[26]; EXEC SQL END DECLARE SECTION; (which is also referred to as and API). main() •aclean separation between the application programand SQL. { GetInput(&DEPT); EXEC SQL DECLARE C1 CURSOR FOR •building a programissimpler ; no preprocessor (although calls to SELECT ENAME, DEPTNO FROM EMP WHERE DEPTNO = :DEPT; the DBMS runtime librar y are the same). EXEC SQL OPEN C1 while (SQLCODE == 0) { EXEC SQL FETCH C1 INTO :NAME, :DNO •debugging is simpler;you debug your own code rather than code } generated byaprecompiler. EXEC SQL CLOSE C1 } Precompilers from different vendors will produce different code. Graham Kemp,University of Aberdeen Graham Kemp,University of Aberdeen Precompiling Embedded SQL Programming models for relational systems The precompiler and DBMS interact in severalways: What if wewant to change the DBMS that our application uses? Embedded SQL •The DBMS parser checks the syntax of the SQL statements. Requires compiling application programusing newDBMS vendor’s precompiler.Wemight not have the source code (e.g. ‘‘shr ink- •The DMBS checks the semantics of the SQL statements (table wrapped’’applications). and column names are correct, data types of host language variables are correct, etc.) Vendor-specific API Requires changing the source code to use the newDBMS vendor’s •Ifthe SQL statements are OK, optimise them to produce an API, and recompiling with the newDBMS vendor’slibrar ies.Again, access plan, which is stored in the database.
    [Show full text]
  • SQL ENVIRONMENTS FEDERAL INFORMATIONPROCESSINGSTANDARDSPUBLICATION 1995 FEBRUARY3 FIPS PUB193 National Instituteofstandardsandtechnology U.S
    REFERENCE U.S. DEPARTMENT OF COMMERCE Technology Administration National Institute of Standards and Technology ItL'S FIPS PUB 193 FEDERAL INFORMATION PROCESSING STANDARDS PUBLICATION SQL ENVIRONMENTS Category: Software Standard Subcategory: Database 1995 FEBRUARY 3 193 PUB FIPS . A8A3 NO.193 1995 i - ( FIPS PUB 193 FEDERAL INFORMATION PROCESSING STANDARDS PUBLICATION SQL ENVIRONMENTS Category: Software Standard Subcategory: Database Computer Systems Laboratory National Institute of Standards and Technology Gaithersburg, MD 20899-0001 Issued February 3, 1995 U.S. Department of Commerce Ronald H. Brown, Secretary Technology Administration Mary L. Good, Under Secretary for Technology National Institute of Standards and Technology Arati Prabhakar, Director Foreword The Federal Information Processing Standards Publication Series of the National Institute of Standards and Technology (NIST) is the official publication relating to standards and guidelines adopted and promulgated under the provisions of Section 111 (d) of the Federal Property and Administrative Services Act of 1949 as amended by the Computer Security Act of 1987, Public Law 100-235. These mandates have given the Secretary of Commerce and NIST important responsibilities for improving the utilization and management of computer and related telecommunications systems in the Federal Government. The NIST, through its Computer Systems Laboratory, provides leadership, technical guidance, and coordination of Government efforts in the development of stan¬ dards and guidelines in these areas.
    [Show full text]