DOCSLIB.ORG

Application Notes for Telcomp Pickupip and Avaya IP Office - Issue 1.0

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Application Notes for Telcomp Pickupip and Avaya IP Office - Issue 1.0 Avaya Solution & Interoperability Test Lab Application Notes for Telcomp PickUpIp and Avaya IP Office - Issue 1.0 Abstract These Application Notes describe the configuration steps required for Telcomp PickUpIp to successfully interoperate with the Avaya IP Office. Telcomp PickUpIp provides CallerID number information via a single-line screen pop and/or a multi-line menu capability from the Avaya IP Office to a single computer, or to a network of computers. Information in these Application Notes has been obtained through compliance testing and additional technical discussions. Testing was conducted via the DeveloperConnection Program at the Avaya Solution and Interoperability Test Lab. SCR; Reviewed: Solution & Interoperability Test Lab Application Notes 1 of 14 SPOC 2/20/2006 ©2006 Avaya Inc. All Rights Reserved. telcomp-ipo.doc 1. Introduction These Application Notes describe the compliance-tested configuration of Avaya IP Office and Telcomp PickUpIp. PickUpIp is a client/server middleware application that provides CallerID number information via a single-line screen pop and/or a multi-line display capability from IP Office to a single computer, or a network of computers. Telcomp’s software solution for Avaya IP Office consists of the following application components: PickUpIp – CallerID IP Server for IP Office TcIpOff – IP Office / Partner Translator for IP Office Pickup – CallerID client The Telcomp TcIpOff application interfaces with the Avaya IP Office through the DevLink interface. TAPI 3rd party call control has not been implemented for this solution. TcIpOff translates the DevLink stream it receives into a format supported by Telcomp PickUpIp. The PickUpIp server receives CallerID number information for incoming calls from the DevLink stream translated by TcIpOff and then broadcasts the information over the network to its clients (called Pickup). The PickUpIp server and Pickup clients can display incoming CallerID number information on-screen using a single-line screen pop and/or a multi-line menu window. If CallerID number information is not available, Telcomp PickUpIp identifies the incoming call number as Unknown. The PickUpIp server and Pickup clients can also be configured to simulate keystrokes in order to deliver incoming CallerID number information to other applications running on the PC. The tested configuration is shown in Figure 1. SCR; Reviewed: Solution & Interoperability Test Lab Application Notes 2 of 14 SPOC 2/20/2006 ©2006 Avaya Inc. All Rights Reserved. telcomp-ipo.doc Figure 1: Telcomp PickUpIp and Avaya IP Office Configuration 2. Equipment and Software Validated The following equipment and software were used for the sample configuration provided: Product Version Avaya IP403 Office 3.0(59) Avaya IP Office Manager 5.0(59) Avaya IP Office User Suite 3.0(16) Avaya DevLink 1.0.0.4 Avaya Voicemail Pro 3.0(17) Avaya IP Office Feature Key Server 1.0 Avaya 4620 IP Telephones 2.3 Avaya 6408D Digital Telephones - Telcomp PickUpIp 8.0h Telcomp TcIpOff 8.0h Telcomp Pickup 8.0h PCs used for Avaya IP Office Manager, Avaya Windows 2000 Professional Voicemail Pro and Telcomp PickUpIp, TcIpOff, and Service Pack 4 Pickup Analog Telephone - SCR; Reviewed: Solution & Interoperability Test Lab Application Notes 3 of 14 SPOC 2/20/2006 ©2006 Avaya Inc. All Rights Reserved. telcomp-ipo.doc 3. Configure Avaya IP Office These Application Notes address provisioning of the Avaya IP Office as it relates to integration with the Telcomp software. For all other provisioning information such as provisioning of the trunks, call coverage, extensions; please refer to the Avaya IP Office product documentation. Step Description Login 1. Log into the IP Office Manager PC and go to Start → Programs → IP Office → Manager to launch the Manager application. Log into the Manager application using the appropriate credentials. 2. In the Manager window that appears, select File → Open to search for the IP Office system in the network. 3. Log into the IP Office system using the appropriate login credentials to receive its configuration. Configure Feature Key Server IP Address 4. In the Manager window, go to the Configuration Tree and double-click System. In the System tab of the System Configuration window that appears, verify that the License Server IP Address field is set properly. For example, if the Feature Key is connected to a PC, the License Server IP Address should be set to the IP address of the PC. Install licenses 5. In the Manager window, go to the Configuration Tree and double-click License to open the list of licenses installed in the IP Office system. SCR; Reviewed: Solution & Interoperability Test Lab Application Notes 4 of 14 SPOC 2/20/2006 ©2006 Avaya Inc. All Rights Reserved. telcomp-ipo.doc Step Description 6. Right click in the license list window and select New. In the License window that appears, enter the CTI Link Pro License Key (required for the DevLink interface) and click OK. The screen shows a fictitious license. 7. In the Manager window, select File → Save to save the licenses to the IP Office system and wait for the system to update. The system reload validates the new license. 4. Configure Telcomp software This section addresses provisioning of the Telcomp software as it relates to the Avaya IP Office. For all other provisioning and use information such as basic installation and configuration, license key registration, and product use, please refer to the Telcomp Help file provided with the Telcomp software or contact Telcomp support. 4.1. Install Avaya DevLink DLL on Telcomp server Step Description 1. Log into the Telcomp server with administrative privileges and launch the Avaya IP Office User Suite setup.exe in the CDROM drive. 2. Click Next in the InstallShield Wizard until the Select Components window appears. Check DEV Link to install the IP Office DevLink on the Telcomp server. 3. Click Next to complete the installation of the Avaya IP Office User Suite. At the InstallShield Wizard Complete window, click Finish. 4. To verify installation of the DEV Link DLL, initiate a search for the file devlink.dll on the Telcomp server. A copy of the file should have been created in a subfolder of the directory designated for the installation of the Avaya IP Office User Suite such as C:\Program Files\Avaya\IP Office\DEV Link. SCR; Reviewed: Solution & Interoperability Test Lab Application Notes 5 of 14 SPOC 2/20/2006 ©2006 Avaya Inc. All Rights Reserved. telcomp-ipo.doc 4.2. Configure Telcomp TcIpOff Step Description 1. Log into the Telcomp server with administrative privileges and go to Start → Programs → Telcomp → TcIpOff to launch the application. 2. In the TcIpOff window that appears, note Current State near the bottom of the window displays PBX: is Down which means TcIpOff has not established a connection to the Avaya IP Office and PickUpIp closed which means TcIpOff and PickUpIp have not yet established a connection. 3. In the TcIpOff window, set PBX IpAddress to the IP address of the Avaya IP Office such as 192.45.70.194, PBX Password to the password used to log into the Avaya IP Office and click OK. The TcIpOff window minimizes to the Windows system tray. 4. To verify TcIpOff established communication with the Avaya IP Office, click the TcIpOff icon on the Windows system tray. When the TcIpOff window appears, verify PBX: Up appears in Current state. Click OK to minimize the window. 5. This completes the configuration necessary to establish a DevLink connection between the Avaya IP Office and Telcomp TcIpOff. SCR; Reviewed: Solution & Interoperability Test Lab Application Notes 6 of 14 SPOC 2/20/2006 ©2006 Avaya Inc. All Rights Reserved. telcomp-ipo.doc 4.3. Configure Telcomp PickUpIp Step Description 1. Log into the Telcomp server with administrative privileges and go to Start → Programs → Telcomp → PickUpIp to launch the application. 2. Click PickUpIp on the Windows taskbar to open the Telcomp PickUpIp window. 3. Left-click the telephone icon ( ) on the top left corner of either the PickUpIp screen pop window or the PickUpIp Line Menu window and select Options… in the menu that appears. 4. In the PickUpIp Options window that appears, click TCP. 5. In the Tcp Settings window that appears, set My TCPIP Address to the IP address of the Telcomp PickUpIp server such as 192.45.70.46 and click Ok. Port is defaulted. SCR; Reviewed: Solution & Interoperability Test Lab Application Notes 7 of 14 SPOC 2/20/2006 ©2006 Avaya Inc. All Rights Reserved. telcomp-ipo.doc Step Description 6. In the PickUpIp Options window that appears, set OEM Ip Address to the IP address of the Telcomp PickUpIp server, e.g., 192.45.70.46 and click OK. By default, PickUpIp is configured to monitor the first four lines on the Avaya IP Office. Please refer to the Telcomp Help file for information on how to adjust the lines to be monitored. NOTE: Popup Timeout value was modified from 0 to 10 (screen pop generated by PickUpIp will pause 10 seconds before minimizing), Error Timeout was changed from 0 to 30 (PickUpIp will wait 30 seconds before timing out any error message popups) and Station was set to 4003 (PickUpIp will generate a screen pop for inbound trunk calls answered at extension 4003). These changes were done in the course of setting up the application for use during compliance testing and are not required for interoperability between the Telcomp software and Avaya IP Office. Please refer to the Telcomp Help file for a detailed description of these fields and their use. 7. This completes configuration of the PickUpIp server to establish a connection with TcIpOff. Verify installation 8. PickUpIp is configured to display all inbound calls to monitored lines in the PickUpIp Line Menu window along with the inbound CallerID number.
Load more

Recommended publications
  • Functional Thinking
    Functional Thinking director / software architect NEAL FORD meme wrangler ® ThoughtWorks [email protected] 2002 Summit Boulevard, Atlanta, GA 30319 nealford.com thoughtworks.com memeagora.blogspot.com @neal4d 1 a metaphor an essay a history lesson 2 3 4 new language: easy new paradigm: hard 5 “functional” is more a way of thinking than a tool set 6 Execution in the Kingdom of Nouns Steve Yegge http://steve-yegge.blogspot.com/ 2006/03/execution-in-kingdom-of-nouns.html 7 v e r b s ! 8 ! 9 http://oreilly.com/news/languageposter_0504.html 1954 1957 1960 1965 1970 1975 1980 1985 1990 1995 2000 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 PostScript level 3 PostScript level 3 PostScript PostScript level 2 PostScript level 3 v 3016 v 3017 1982 1992 september 11, 1996 OO Forth 2003 september 11, 2005 1987 Forth FIG-Forth Forth-83 ANS Forth ISO Forth 1968 1978 1983 1986 1997 Logo Object Logo Tcl Tcl/Tk Tcl/Tk 8.1 Tcl/Tk 8.2.3 Tcl/Tk 8.3 Tcl/Tk 8.4 Tcl/Tk 8.4.1 Tcl/Tk 8.4.2 Tcl/Tk 8.4.3 Tcl/Tk 8.4.4 Tcl/Tk 8.4.5 Tcl/Tk 8.4.6 Tcl/Tk 8.4.7 Tcl/Tk 8.4.8 Tcl/Tk 8.4.9 Tcl/Tk 8.4.11 Tcl/Tk 8.4.12 Tcl/Tk 8.4.13 Tcl/Tk 8.4.14 Tcl/Tk 8.4.15 Tcl/Tk 8.5 Tcl/Tk 8.5.5 Tcl/Tk 8.5.6 Tcl/Tk 8.5.7 Tcl/Tk 8.5.9 1968 1986 mid 1988 end 1988 april 1999 dec.
    [Show full text]
  • BBN and Computer Technology Timeline 1948 • Establishment Of
    BBN and Computer Technology Timeline 1948 • Establishment of Bolt Beranek and Newman Inc. (BBN) 1958 • Purchase of BBN's first computer, an LPG-30, manufactured by the Royal McBee Company 1959 • Purchase of PDP-1 from the Digital Equipment Corporation (DEC); Serial #0 [??] 1960 • Design of a priority-interrupt system for the PDP-1. • Development of Cyclops, an AI program for pattern recognition. 1962 • Public demonstration of computer time-sharing. 1963 • Demonstration of Data Dial, a modem to enable remote communication with computers by telephone. 1964 • Public demonstration of a computer-based communications system for the Massachusetts General Hospital. • Development of MENTOR and the SOCRATIC SYSTEM, systems for computer- based mixed-initiative tutoring. 1965 • Development of TELCOMP, an interactive computer language. • Development of the Grafacon, a tablet for scanning and digitizing graphic data. • Publication of Libraries of the Future, a consideration of the implications of computer technology for future libraries, based on a project for the Council of Library Resources. 1966 • Creation of LOGO, a computer programming language designed especially for use by children. 1967 • Formation of Time Share Ltd., a subsidiary offering computing services in the UK. 1968 • Development of packet-switching protocols for the ARPANET 1969 • Launching of the ARPANET; demonstration of four-node network. • Automation of odd-lot stock transactions for the Pacific Coast Stock Exchange. • Grammatical analysis of English text by augmented transition networks. 1970 • Development of TENEX, a virtual-memory operating system for DEC computers. • Demonstration of SCHOLAR, a computer-based system that modeled a Socratic tutor. • 1971 Transmission of person-to-person email message using the @ sign.
    [Show full text]
  • Learning to Code
    PART ILEARNING TO CODE How Important is Programming? “To understand computers is to know about programming. The world is divided… into people who have written a program and people who have not.” Ted Nelson, Computer Lib/Dream Machines (1974) How important is it for you to learn to program a computer? Since the introduction of the first digital electronic computers in the 1940s, people have answered this question in surprisingly different ways. During the first wave of commercial computing—in the 1950s and 1960s, when 1large and expensive mainframe computers filled entire rooms—the standard advice was that only a limited number of specialists would be needed to program com- puters using simple input devices like switches, punched cards, and paper tape. Even during the so-called “golden age” of corporate computing in America—the mid- to late 1960s—it was still unclear how many programming technicians would be needed to support the rapid computerization of the nation’s business, military, and commercial operations. For a while, some experts thought that well-designed computer systems might eventually program themselves, requiring only a handful of attentive managers to keep an eye on the machines. By the late 1970s and early 1980s, however, the rapid emergence of personal computers (PCs), and continuing shortages of computer professionals, shifted popular thinking on the issue. When consumers began to adopt low-priced PCs like the Apple II (1977), the IBM PC (1981), and the Commodore 64 (1982) by the millions, it seemed obvious that ground-breaking changes were afoot. The “PC Revolution” opened up new frontiers, employed tens of thousands of people, and (according to some enthusiasts) demanded new approaches to computer literacy.
    [Show full text]
  • Application Notes for Telcomp Software Applications and Avaya IP Office - Issue 1.0
    Avaya Solution & Interoperability Test Lab Application Notes for Telcomp Software Applications and Avaya IP Office - Issue 1.0 Abstract These Application Notes describe the configuration steps required for Telcomp software applications to successfully interoperate with the Avaya IP Office. The Telcomp PickUpIp application provides Caller ID capabilities to a single computer, or to a network of computers via the Telcomp PickUp application. The Telcomp PickUpEm application provides 911 emergency alert messages to be directed at a central console. All three of these applications work in conjunction with the Telcomp TcIpOff connection server application. Each of the Telcomp applications requires the functionality of run-time telephony event data streams provided by the Avaya IP Office DevLink PRO SDK interface. Information in these Application Notes has been obtained through DevConnect compliance testing and additional technical discussions. Testing was conducted via the DevConnect Program at the Avaya Solution and Interoperability Test Lab. SVS; Reviewed: Solution & Interoperability Test Lab Application Notes 1 of 18 SPOC 10/16/2007 ©2007 Avaya Inc. All Rights Reserved. IPO40-Telcomp 1. Introduction These Application Notes describe the compliance-tested configuration utilizing Telcomp software applications and Avaya IP Office. The Telcomp software application solution for Avaya IP Office consists of the following applications: PickUpIp – CallerID IP Server for IP Office TcIpOff – IP Office / Partner Translator for IP Office PickUp – CallerID client PickUpEm - 911 Alert Indicator Telcomp PickUpIp is a client/server middleware application that provides CallerID number information via a single-line screen pop and/or a multi-line menu capability from Avaya IP Office to a single computer, or a network of computers.
    [Show full text]
  • 1. with Examples of Different Programming Languages Show How Programming Languages Are Organized Along the Given Rubrics: I
    AGBOOLA ABIOLA CSC302 17/SCI01/007 COMPUTER SCIENCE ASSIGNMENT ​ 1. With examples of different programming languages show how programming languages are organized along the given rubrics: i. Unstructured, structured, modular, object oriented, aspect oriented, activity oriented and event oriented programming requirement. ii. Based on domain requirements. iii. Based on requirements i and ii above. 2. Give brief preview of the evolution of programming languages in a chronological order. 3. Vividly distinguish between modular programming paradigm and object oriented programming paradigm. Answer 1i). UNSTRUCTURED LANGUAGE DEVELOPER DATE Assembly Language 1949 FORTRAN John Backus 1957 COBOL CODASYL, ANSI, ISO 1959 JOSS Cliff Shaw, RAND 1963 BASIC John G. Kemeny, Thomas E. Kurtz 1964 TELCOMP BBN 1965 MUMPS Neil Pappalardo 1966 FOCAL Richard Merrill, DEC 1968 STRUCTURED LANGUAGE DEVELOPER DATE ALGOL 58 Friedrich L. Bauer, and co. 1958 ALGOL 60 Backus, Bauer and co. 1960 ABC CWI 1980 Ada United States Department of Defence 1980 Accent R NIS 1980 Action! Optimized Systems Software 1983 Alef Phil Winterbottom 1992 DASL Sun Micro-systems Laboratories 1999-2003 MODULAR LANGUAGE DEVELOPER DATE ALGOL W Niklaus Wirth, Tony Hoare 1966 APL Larry Breed, Dick Lathwell and co. 1966 ALGOL 68 A. Van Wijngaarden and co. 1968 AMOS BASIC FranÇois Lionet anConstantin Stiropoulos 1990 Alice ML Saarland University 2000 Agda Ulf Norell;Catarina coquand(1.0) 2007 Arc Paul Graham, Robert Morris and co. 2008 Bosque Mark Marron 2019 OBJECT-ORIENTED LANGUAGE DEVELOPER DATE C* Thinking Machine 1987 Actor Charles Duff 1988 Aldor Thomas J. Watson Research Center 1990 Amiga E Wouter van Oortmerssen 1993 Action Script Macromedia 1998 BeanShell JCP 1999 AngelScript Andreas Jönsson 2003 Boo Rodrigo B.
    [Show full text]
  • The Logo Lineage
    id302705 pdfMachine by Broadgun Software - a great PDF writer! - a great PDF creator! - http://www.pdfmachine.com http://www.broadgun.com THE LOGO LINEAGE by Wallace Feurzeig Wallace Feurzeig is a division scientist in information sciences for Bolt Beranek and Newman. His favorite implementation of Logo is still Logo-S for minicomputers. L ogo was created in 1966 at Bolt Beranek and Newman, a Cambridge research firm. Its intellectual roots are in artificial intelligence, mathematical logic and developmental psychology. The first four years of Logo research, development and teaching work was done at BBN. During the early 1960s, BBN had become a major center of computer science research and innovative applications. I joined the firm in 1962 to work with its newly available facilities in the Artificial Intelligence Department, one of the earliest AI organizations. My colleagues were actively engaged in some of the pioneering AI work in computer pattern recognition, natural language understanding, theorem proving, LISP language development and robot problem solving. Much of this work was done in collaboration with distinguished researchers at M.I.T. such as Marvin Minsky and John McCarthy, who were regular BBN consultants during the early 1960s. Other groups at BBN were doing original work in cognitive science, instructional research and man- computer communication. Some of the first work on knowledge representation (semantic networks), question-answering, interactive graphics and computer- aided instruction was actively underway. J. C. R. Licklider was the spiritual as well as the scientific leader of much of this work, championing the cause of on- line interaction during an era when almost all computation was being done via batch processing.
    [Show full text]
  • Computer Time-Sharing (T-S) "An Engineering Tool" for the Engineering Applications of the Small Company
    Scholars' Mine Masters Theses Student Theses and Dissertations 1970 Computer time-sharing (T-S) "an engineering tool" for the engineering applications of the small company James Binford Summers Follow this and additional works at: https://scholarsmine.mst.edu/masters_theses Part of the Civil Engineering Commons Department: Recommended Citation Summers, James Binford, "Computer time-sharing (T-S) "an engineering tool" for the engineering applications of the small company" (1970). Masters Theses. 5477. https://scholarsmine.mst.edu/masters_theses/5477 This thesis is brought to you by Scholars' Mine, a service of the Missouri S&T Library and Learning Resources. This work is protected by U. S. Copyright Law. Unauthorized use including reproduction for redistribution requires the permission of the copyright holder. For more information, please contact [email protected]. COMPUTER TIME-SHARING (T-S) "AN ENGINEERING TOOL" FOR THE ENGINEERING APPLICATIONS OF THE SMALL COMPANY BY JAMES BINFORD SUMMERS, 1938- A THESIS submitted to the faculty of the UNIVERSITY OF MISSOURI - ROLLA in partial fulfillment of the requirements for the Degree of MASTER OF SCIENCE IN CIVIL ENGINEERING Rolla., Missouri 1970 T2478 c.l 62 pages Approved by ~Jt£.~ ~.(advisor)~~ 187982 ~tiM/ ii ABSTRACT The objectives of this investigation were to illustrate the capabilities of the time-sharing (T-S) industry, identify the means by which the small sized company, with a need to solve engineering problems, can best be served through T-S, and to present T-S to these potential users. Investigation was made of distinctive T-S services to formulate a com­ posite of the T-S industry. Examples of three distinctive T-S services were used within this composite to exemplify the variations of services within the industry.
    [Show full text]
  • Writing Cybersecurity Job Descriptions for the Greatest Impact
    Writing Cybersecurity Job Descriptions for the Greatest Impact Keith T. Hall U.S. Department of Homeland Security Welcome Writing Cybersecurity Job Descriptions for the Greatest Impact Disclaimers and Caveats • Content Not Officially Adopted. The content of this briefing is mine personally and does not reflect any position or policy of the United States Government (USG) or of the Department of Homeland Security. • Note on Terminology. Will use USG terminology in this brief (but generally translatable towards Private Sector equivalents) • Job Description Usage. For the purposes of this presentation only, the Job Description for the Position Description (PD) is used synonymously with the Job Opportunity Announcement (JOA). Although there are potential differences, it is not material to the concepts presented today. 3 Key Definitions and Concepts (1 of 2) • What do you want the person to do? • Major Duties and Responsibilities. “A statement of the important, regular, and recurring duties and responsibilities assigned to the position” SOURCE: https://www.opm.gov/policy-data- oversight/classification-qualifications/classifying-general-schedule-positions/classifierhandbook.pdf • Major vs. Minor Duties. “Major duties are those that represent the primary reason for the position's existence, and which govern the qualification requirements. Typically, they occupy most of the employee's time. Minor duties generally occupy a small portion of time, are not the primary purpose for which the position was established, and do not determine qualification requirements” SOURCE: https://www.opm.gov/policy-data- oversight/classification-qualifications/classifying-general-schedule-positions/positionclassificationintro.pdf • Tasks. “Activities an employee performs on a regular basis in order to carry out the functions of the job.” SOURCE: https://www.opm.gov/policy-data-oversight/assessment-and-selection/job-analysis/job_analysis_presentation.pdf 4 Key Definitions and Concepts (2 of 2) • What do you want to see on resumes that qualifies them to do this work? • Competency.
    [Show full text]
  • Procedural Programming
    NASIR FIRDAUS OPEYEMI 17/SCI01/051 CSC302 1. (I) Examples of Structured Programming language are C, C+, C++, C#, Java, PERL, Ruby, PHP, ALGOL, Pascal, PL/I and Ada The structured programming language allows a programmer to code a program by dividing the whole program into smaller units or modules. Structured programming is not suitable for the development of large programs and does not allow reusability of any set of codes. (ii)A typical example of non-structured if BASIC. other unstructured include JOSS, FOCAL, TELCOMP, assembly languages, MS-DOS batch files, and early versions of BASIC, Fortran, COBOL, and MUMPS. Unstructured programming is a procedural program – the statements are executed in sequence as written(The statements execute in order you write) (iii)Example of procedural programming language are; FORTRAN, C, PASCAL, e.t.c Procedural programming is a programming paradigm, derived from structured programming, based on the concept of the procedure call. Procedures, also known as routines, subroutines, or functions, simply contain a series of computational steps to be carried out. (iv)Modular object oriented: Languages that formally support the module concept include Ada, Algol, BlitzMax, C#, Clojure, COBOL, D, Dart, Modular programming is a software design technique that emphasizes separating the functionality of a program into independent, interchangeable modules, such that each contains everything necessary to execute only one aspect of the desired functionality. (V)Example of Aspect oriented is Haskell Language. Aspect-Oriented Programming (AOP) is a programming paradigm which complements Object-Oriented Programming (OOP) by separating concerns of a software application to improve modularization. (Vi)Example of Activity Oriented: Activity-oriented knowledge representation methods.
    [Show full text]
  • Comparative Programming Languages CM20253
    We have briefly covered many aspects of language design And there are many more factors we could talk about in making choices of language The End There are many languages out there, both general purpose and specialist And there are many more factors we could talk about in making choices of language The End There are many languages out there, both general purpose and specialist We have briefly covered many aspects of language design The End There are many languages out there, both general purpose and specialist We have briefly covered many aspects of language design And there are many more factors we could talk about in making choices of language Often a single project can use several languages, each suited to its part of the project And then the interopability of languages becomes important For example, can you easily join together code written in Java and C? The End Or languages And then the interopability of languages becomes important For example, can you easily join together code written in Java and C? The End Or languages Often a single project can use several languages, each suited to its part of the project For example, can you easily join together code written in Java and C? The End Or languages Often a single project can use several languages, each suited to its part of the project And then the interopability of languages becomes important The End Or languages Often a single project can use several languages, each suited to its part of the project And then the interopability of languages becomes important For example, can you easily
    [Show full text]
  • 1^0 ^ Tkbocro' Project 16 A-Prll 1966 ;:Llrji:Ops
    1^0 ^ ]?Xl0 \U Jo Bro'i'jn ;:llrJi:OPs TKbOCrO’ Project 16 A-prll 1966 lU.f -fCvt? :1s th^ nano mod hero to do;^o?/;lbe a vropofsod syst^-m }::)attorncc:l after OSS-’-[I vjM.vh p^culd pz^ovlde :/?-n.pld and vo:^:^:atlle ccimutational :';c-:e to or.,g:.l;‘ieiO:es and salontiints via a tole-' !b;:^->;uiatc! am pex^sonaX latoraction of tho sairze \i a amarlonoad vilth a vnl^ate cisal?; calc^tl.ator comXad tro poT^Jor and fXenibility of a hiy^U apaad ccaapntsn is the 'note of this ayste^o i:t:e lann;i:>a^e used to coiimnnicate with tl'v:; aysteu Is easy to loanop sbeplo to use and natuvaX for itVinorioal problons^ Pnp?:i/iQnc0 vlth tho JOSS aysten? at rlAlW Coy-pnx^ntlorx has ar;.o'i^;n that systens of this sort ana oxtnamely usoful for a nide variety of en^;inooring and solentific cal- cnlationSo Our local e^iserienoe nita_a similar system-^ ■ Xi:.' lementod on the Hospital Cci;iputc;r (SOS-ld) shons tliat tlia /I ability to do useful ccmputaticus at the GOEa;and of in: Individual onyinaer or sclontist comornod uith a pmblGii:i V. indeed imomssme 1,1ut that res ability and doci^isentaticLi must rn-ovt very high standaisda in order to achieve eompleto aoo0j>tan,CGo n Vi out Version;●-> Vavyioi.-s im:plemen1'atioris of JOSS-lihe rysteins ?aave been^ rimm ins on the Hospital Cemputor (ifF-ld) since August i9t4« mono of thoBo has mar boon as coipplete a system as its parent (joss) and the documentatiGn has been quite inadequate= HemartmiesB.
    [Show full text]
  • Compatible Time-Sharing System (1961-1973) Fiftieth Anniversary
    Compatible Time-Sharing System (1961-1973) Fiftieth Anniversary Commemorative Overview The Compatible Time Sharing System (1961–1973) Fiftieth Anniversary Commemorative Overview The design of the cover, half-title page (reverse side of this page), and main title page mimics the design of the 1963 book The Compatible Time-Sharing System: A Programmer’s Guide from the MIT Press. The Compatible Time Sharing System (1961–1973) Fiftieth Anniversary Commemorative Overview Edited by David Walden and Tom Van Vleck With contributions by Fernando Corbató Marjorie Daggett Robert Daley Peter Denning David Alan Grier Richard Mills Roger Roach Allan Scherr Copyright © 2011 David Walden and Tom Van Vleck All rights reserved. Single copies may be printed for personal use. Write to us at [email protected] for a PDF suitable for two-sided printing of multiple copies for non-profit academic or scholarly use. IEEE Computer Society 2001 L Street N.W., Suite 700 Washington, DC 20036-4928 USA First print edition June 2011 (web revision 03) The web edition at http://www.computer.org/portal/web/volunteercenter/history is being updated from the print edition to correct mistakes and add new information. The change history is on page 50. To Fernando Corbató and his MIT collaborators in creating CTSS Contents Preface . ix Acknowledgments . ix MIT nomenclature and abbreviations . x 1 Early history of CTSS . 1 2 The IBM 7094 and CTSS at MIT . 5 3 Uses . 17 4 Memories and views of CTSS . 21 Fernando Corbató . 21 Marjorie Daggett . 22 Robert Daley . 24 Richard Mills . 26 Tom Van Vleck . 31 Roger Roach .
    [Show full text]