articles+ search results

1,510 articles+ results

1 - 50
View results as:
Number of results to display per page

1. Systems development: heuristic or prototyping? [1982]

  • Wetherbe, James C.
  • Computerworld. April 26, 1982, Vol. 16, pSR14, 2 p.
Subjects
Systems analysis -- Methods

2. Prototyping may alleviate DP crunch [1982]

  • Whitlock, Brad
  • Computerworld. June 14, 1982, Vol. 16, p71, 2 p.
Subjects
Information storage and retrieval systems -- Innovations and Electronic data processing -- Innovations

3. Prototyping Hailed as User-Tailored Approach [1983]

  • Paul, L.
  • Computerworld. Feb 14, 1983, Vol. 17 Issue 7, p15. photograph
Subjects
User Relations, System Development, User Need, Prototype, Systems, and System Design
Abstract
According to Merle Parks, product manager for Cincom, DP personnel need to recognize the following myths when developing applications: users' needs are static, users know what they want and users can communicate their needs to DP. When dealing with users, the system developer should illustrate several types of systems via menus. A photograph of Merle Parks is included.

4. Intel Enhances System 2000 [1983]

  • Computerworld. March 7, 1983, Vol. 17 Issue 10, p37
Subjects
Relational Data Base Management Systems, DBMS, Mainframe Computer, Interface, Enhancements, and System 2000 Release 11 (data base management system)
Abstract
Intel's Release 11 of its System 2000 data base management system (DBMS) features relational DBMS functions, data base modeling, prototyping, decision assist for what-if analysis, and access to multiple data bases. Designed for IBM-based OS and VM-CMS environments, the package also offers a new teleprocessing interface that combines the attributes of the existing batch and TP interfaces. It sells for $70,000.

5. A Propitious Marriage: CAD and Manufacturing [1983]

  • Rosenbaum, J.D.
  • IEEE Spectrum. May 1983, Vol. 20 Issue 5, p49. chart Other
Subjects
Automation, Computer-Aided Design, Manufacturing, Solids Modeling, Modeling, Three-Dimensional Graphics, Integrated Systems, CAD/CAM, and Ingersoll
Abstract
Computer-aided design (CAD) offers manufacturers increased design productivity, reduces prototyping by using three-dimensional modeling and easily transfers information from the designer to the manufacturer. Three-D modeling with solid and wire models has invaded mechanical engineering and can be linked to manufacturing operations. Ingersoll, a West German machine-tool company, uses a Cadam (Computer-augmented drafting and manufacturing) system for custom design of products. The increased productivity potential of CAD systems may not be fully realized but a case history illustrates a productivity increase using a CAD system. Screen displays of three-D graphics as well as a block diagram of the Northrup computer-aided design (NCAD) system are included.

6. An Electronic Form System-An Experience in Prototyping [1983]

  • Gehani, N.
  • Software - Practice & Experience. June 1983, Vol. 13 Issue 6, p479
Subjects
Prototype, Forms Design, System Development, and Forms
Abstract
Prototypes are often used to evaluate the feasibility of doing a full design of a new mechanism. A prototype of an electronic form system is presented with a discussion of prototypes. The mechanism being explored is a high level form definition mechanism based on abstract data types in programming languages. The prototype provided better understanding of implementation and facilities of a form definition language. Statements of prototype objectives assisted in developing a successful prototype.

7. A Prototyping Method for Applications Development by End Users and Information Systems Specialists [1983]

  • Kraushaar, J.M. and Shirland, L.E.
  • MIS Quarterly. Sept, 1983, Vol. 9 Issue 3, p189. chart
Subjects
Applications Programming, Backlog, Applications Backlog, Prototype, Methods, Information Systems, System Design, and Models
Abstract
A prototyping development method is presented here which has the potential to reduce the growing application development backlog. Prior research and our findings indicate that a prototyping process can assist in the efficient development of application systems by breaking a complex problem into several comprehensive parts. A state-transition model of the IS development process is presented and discussed. A two-prototype method is explained in the context of this model. Two projects are described which are typical of development efforts made by end users in a microcomputer environment and IS specialists in a mainframe environement. (Reprinted by Permission of Publisher.)

8. Giving Users a Working Model for Applications Development [1983]

  • Boar, B.H.
  • Computerworld. Sept 12, 1983, Vol. 17 Issue 37, pID 37
Subjects
Prototype, Definitions, Models, System Development, Functional Capabilities, and End User
Abstract
The definition of a system can determine its success. Prototyping is a definition technique that minimizes life cycle cost, implementation time and project risk. This technique insures that a product will be accepted at conversion. It is based upon the assumption that people understand physical models and focuses upon the following factors when building a system: user needs, software that provides speed and flexibility, communication through familiar mediums and animated specifications. Prototyping works well in the early phases of system development.

9. Speaker Outlines Applications Building Concept [1983]

  • Gillin, P.
  • Computerworld. Oct 17, 1983, Vol. 17 Issue 42, p29
Subjects
Conferences and Meetings, Applications Programming, System Development, Consultants, Prototype, End User, User Need, Information Systems, and Architecture
Abstract
Speaking to a session at the 10th International Information Management Exposition and Conference, the vice-president of a computer consulting firm outlined a method of evolutionary information system development that draws heavily on prototyping to build systems that meet user needs at the end, rather than the beginning, of the development life cycle. There are three basic steps involved in this process: designing a standard system architecture, defining the application environment, and defining the application development methodology, that is, the 'how-to' of system design strategies.

10. The Use of Relational DBMS for Prototyping [1983]

  • Wiorkowski, G.
  • Computerworld. Oct 31, 1983, Vol. 17 Issue 44, pSR 20
Subjects
Relational Database, DBMS, Relational Data Base Management Systems, and Prototype
Abstract
Relational data base management systems (DBMS) are well suited for prototyping due to their ease of use and data independence. Updates can be entered directly at the terminals, placed in routines, or embedded in a host language. Relational DBMS have no separate data dictionaries. Changes to the logical design of data is also simple since logical design is implemented through views that do not physically exist.

11. The Building Blocks: Software Engineering [1983]

  • Yeh, R.
  • IEEE Spectrum. Nov 1983, Vol. 20 Issue 11, p91
Subjects
Future of Computing, Software Engineering, Software Design, Product Development, Programming, and Prototype
Abstract
Software tools are necessary for programming productivity and quality to match that of hardware improvements, but are not being used by engineers in the United States. One improvement in software design would be in rapid prototyping of systems. High- level languages could check the requirements of a program quickly by implementing a basic version of the final product. Reusable software would also cut down on the development process. Automated design tools would include a non-prodecural specifications language, an intelligent software-based management system for reusable software, and an intelligent editor.

12. On-Line Insurance [1983]

  • Lantz, K.E.
  • Computerworld. Nov 14, 1983, Vol. 17 Issue 46, p45
Subjects
Insurance Industry, Artificial Intelligence, Workstations, Networks, DBMS, Database, Online, Future Technologies, User Interface, Information Systems, and Information Resources Management
Abstract
By 1990 developments in data processing and communications technology will bring dramatic changes to the insurance industry and other businesses using stored information resources. Information will be kept in true data bases which will be accessed on-line for updating, inquiries, and transactions. Home terminals linked to a company's mainframe computer will provide for electronic purchases of insurance policies. Workstations will give users the ability to produce, store, retrieve, manipulate, and analyze information located in personal, corporate, and external data bases. All hardware will be seen as part of a communications network which the user will join when he sits at a workstation. In the 1980's methodologies such as prototyping, along with dedicated efforts by information system managers and end users, will be needed to bring about these advances.

13. Prototyping Slashes Insurance Firm's Backlog [1984]

  • Computerworld. Jan 1984, Vol. 18, p23SR-24
Subjects
Insurance Industry, Software Packages, Prototype, Software, Applications Backlog, Integrated Software, Applications, Equitable Life Assurance Society of the United States, and Umbrella
Abstract
Equitable Life Assurance has implemented Hogan Systems' Umbrella integrated applications system to help reduce its programming backlog. Umbrella is an on-line, transaction-driven process and data dictionary for batch as well as on-line processing. System development is a matter of choosing the proper components, supplying parameters tailored to the specifics of an application, then integrating into the system any programming that is unique to that application. It has three major components: the Processing Environment Manager (PEM), Production Support (PS), and Application Support (AS). PEM isolates the application so it is independent of the operating environment. PS controls the processing of exceptions, centralized applications, and cylical transactions. AS eliminates redundant programming, simplifies maintenance, creates application systems, and enables nontechnical personnel to create their own tables and their own error messages.

14. Architecture Prototyping in the Software Engineering Environment [1984]

  • Beregi, W.E.
  • IBM Systems Journal. Annual, 1984, Vol. 23 Issue 1, p4. chart
Subjects
Specifications, Program Development Techniques, Software Engineering, Prototype, System Development, Software Quality, and Software Architecture
Abstract
A perspective on the evolution and problems of the software development craft is presented. How software engineering techniques show promise to solve these problems is discussed. Using architecture prototyping as a program development technique for improving software quality is introduced. A disciplined approach to software development based on the use of formal specification techniques to express software requirements and system design is presented.

15. The Design of the REXX Language [1984]

  • Cowlishaw, M.F.
  • IBM Systems Journal. Annual, 1984, Vol. 23 Issue 4, p326. table
Subjects
Language, Programming Language, Applications, Machine Independence, User-Friendliness, Design, and Technology
Abstract
One way of classifying computer languages is by two classes: languages needing skilled programmers, and personal languages used by an expanding population of general users. REstructured eXtended eXecutor (REXX) is a flexible personal language designed with particular attention to feedback from its users. It has proved to be effective and easy to use, yet it is sufficiently general and powerful to fulfil the needs of many demanding professional applications. REXX is system and hardware independent, so that it has been possible to integrate it experimentally into several operating systems. Here REXX is used for such purposes as command and macro programming, prototyping, education, and personal programming. This paper introduces REXX and describes the basic design principles that were followed in developing it. (Reprinted by Permission of Publisher.)

16. Management of Industrial Software Production [1984]

  • Matsumoto, Y.
  • Computer. Feb 1984, Vol. 17 Issue 2, p59. chart
Subjects
Software, Process Control, Real-Time System, Software Engineering, Application Development Software, Programming, Prototype, Requirements Analysis, and System Development
Abstract
Large-scale software requires effective management for production. Such large-scale software consists of application software, a utility subsystem, and an operating system. Individual software factories require levels of abstraction in a design process which uses prototyping, reusing, and program generating systems. The first level is the requirements level which defines the external devices with which the software communicates. A capsulated form of a requirements description is shown. The data-function or design level is the transition, the definition of a user's needs and the establishment of the model. Program models are defined and implemented in the program level. Prototyping is done throughout the entire process for the first operational versions of software interfaces. Productivity and reliability are the most crucial factors in management of a software factory. In addition to the encapsulated format examples, numerous block diagrams illustrate software production and the rolling mill software production example.

17. New Roles for Programmers [1984]

  • Jones, R.
  • Data Processing. March 1984, Vol. 26 Issue 2, p60
Subjects
Trends, Future of Computing, User Relations, User Assistance, End User, User-Written Software, Management of EDP, Programmer, EDP Personnel, Program Development Techniques, and Prototype
Abstract
The processes of systems analysis and programming have changed little in the last ten to fifteen years. The arrival of mini- and micro-computers in user departments and the change in user information requirements will force a change in data processing. 'Fourth generation' software, or end user computing involves the user departments directly in the development of a system. Prototyping of a system by programmer and a user will be used to first develop screen layouts, then to map out processing using high-level languages. In order to survive, programmers will need to become involved with the applications they are coding and will need to acquire systems analysis skills.

18. Mantis Release Features Enhancements [1984]

  • Computerworld. March 5, 1984, Vol. 18 Issue 10, p54
Subjects
DBMS, Enhancements, Upgrading, Disk/File Management Software, and Mantis Release 3.7 (computer program)
Abstract
Cincom Systems Mantis application system has enhanced features for prototyping, file-access and documentation. Mantis runs in both IBM CICS and Cincom's TIS-DC environments. The list price ranges from $21,000 to $59,000.

19. Users Urged to Be Selective with Info Language [1984]

  • Gallant, J.
  • Computerworld. March 12, 1984, Vol. 18 Issue 11, p14
Subjects
Fourth Generation, Software Packages, Data Management, Programming Language, Applications Programming, Nonprocedural Languages, End User, and Info
Abstract
To get the most from Henco Software's Info fourth-generation programming language and data management system, users are urged to use the program package effectively. Info is best suited to developing single-user applications and prototyping general applications that can later be developed in another language for production environments. It should not be used in multiuser applications or applications involving over nine data relationships.

20. Bank Pleased with Teradata DBC-1012 [1984]

  • Gillin, P.
  • Computerworld. March 19, 1984, Vol. 18 Issue 12, p8
Subjects
Data Base Processors, New Product, Applications, Banking, Computer Systems, Data Base Languages, Query Languages, User Interface, Wells Fargo Bank N.A. -- Purchasing, and DBC-1012
Abstract
Wells Fargo Bank N.A. is the first user of Teradata Corp.'s DBC-1012 data base machine. While Wells Fargo has no plans for replacing its VSAM files with the data base machine, it does expect to develop many of its small and medium-scale applications on the DBC-1012, particularly those requiring a quick turnaround time. Teradata's TEQUEL fourth-generation language is about twice as fast as the FOCUS language, in terms of prototyping and development. The DBC-1012 has a reported capacity of up to one terabyte - one trillion bytes. One of the first applications on Wells Fargo's DBC-1012, which consists of four parallel access module processors, two communications controllers, and four Winchester disk packs, included a difference analysis program in which three million item processing balances were input and searched for discrepancies. The acid test for the system will come in April when Wells Fargo plans to install an accounts analysis system.

21. First User Planning Applications, End-User Computing [1984]

  • Computerworld. March 19, 1984, Vol. 18 Issue 12, p8
Subjects
Data Base Processors, New Product, Applications, Query Languages, Data Base Languages, User-Friendliness, Wells Fargo Bank N.A. -- Purchasing, and DBC-1012
Abstract
Although Teradata Corp. touts its new data base machine, the DBC-1012, as being capable of handling large production-scale processing, Wells Fargo, the first user of the system, plans to use it for fast-changing new applications and end-user computing. The DBC-1012 has proven useful for prototyping, due primarily to the TEQUEL query language and the machine's self- normalizing relational structure. Because TEQUEL is relatively easy to learn, it will be taught to executive-level users at Wells Fargo.

22. Test Robot Work Cells with Graphics Systems [1984]

  • Baumann, E.W.
  • Computerworld. March 26, 1984, Vol. 18 Issue 13, p12SR
Subjects
Robots, Simulation, Performance Prediction, Simulation of Computer Systems, and Testing -- Other
Abstract
There are three major advantages to using computer simulation for testing robot systems. First, the time and materials spent on physically prototyping alternative robot work cells is reduced or eliminated. Second, the need for on-site testing is eliminated. Third, the possibility of a programming error causing harm to personnel or equipment is reduced. The major disadvantage to using simulation is that computer simulations are never perfect representations of the real world. Users must be careful to understand how well real world applications are being reproduced. Three simulation screen displays are included.

23. Fourth-Generation Languages: Cure for DP Ills? [1984]

  • Computerworld. April 30, 1984, Vol. 18 Issue 18, p67
Subjects
Nonprocedural Languages, Study, User Relations, Evaluation, Programming, Programming Language, and Application Development Software
Abstract
According to Input Inc.'s report titled Opportunities of Fourth-Generation Languages, fourth-generation languages can solve several problems relating to information systems. These problems include isolation of information systems from the rest of the organization; the development of systems that are late, incomplete, or inflexible; the perception of the information systems department as unresponsive; and user ignorance of data processing functions. The report predicts fourth-generation languages will play an important role in the systems development process. In addition, micro versions will offer some attractive options, including micro-mainframe communication and prototyping.

24. Prototyping Versus Specifying: a Multiproject Experiment [1984]

  • Boehn, B.W., Gray, T.E., and Seewaldt, T.
  • IEEE Transactions on Software Engineering. May 1984, Vol. 10 Issue 3, p290
Subjects
Prototype, Specifications, Performance Specifications, Software Engineering, Program Development Techniques, and Comparative Study
Abstract
There has been much discussion on the relative merits of the specification-driven approach to software development versus the prototyping approach. An experiment has been conducted to give some basis for comparison of the two approaches. Seven software teams developed the same application software product. Three used the prototyping approach, four the specifying approach. Results indicate that prototyping required less effort and less code for equivalent performance. Prototyped products were easier to learn and use but rated lower on functionality and robustness. Specified products were easier to integrate.

25. Beta Test User of IDMS-R Lauds End-User Benefits [1984]

  • Gillin, P.
  • Computerworld. May 14, 1984, Vol. 18 Issue 20, p8
Subjects
Relational Data Base Management Systems, Software Packages, Database, Beta Testing, Integrated Software, Prototype, User-Written Software, Application Development Software, End User, User-Friendliness, Central & South West Services, IDMS-R, Integrated PC Software, and Information Database
Abstract
Although Central and South West Services, Inc. has yet to build a large-scale application, company officials are nonetheless pleased with Cullinet Software's IDMS-R relational data base management system (DBMS). The package has improved prototyping efficiency for both end-users and programmers. Central and South West also uses Cullinet's Integrated PC Software, which enables users to manipulate data without knowing where it is stored, and the Information Database package.

26. Alleviating Common Concerns of Application Prototyping - the Experience Difference [1984]

  • Boar, B.H.
  • Computerworld. May 28, 1984, Vol. 18 Issue 22, p66SR-67
Subjects
Prototype, Applications Backlog, Applications Programming, Efficiency, and Program Development Techniques
Abstract
Although prototyping is not a perfect solution, it is one of the best ways to improve application development productivity. Unfortunately, it is also a misunderstood technique. Some fear that it serves merely to gloss over the real business problems. Others shy away from prototyping because they feel it departs from standard software engineering practices. Another concern is that it constrains the imagination of the system developers. Still another concern is that it conflicts with data resource administration and the creation of shared data bases. These are among the concerns that are addressed and refuted. In short, the difference between prototyping and traditional structured analysis is the difference bewteen experience and conjecture.

27. Apollo Adds Lisp Version on Domain [1984]

  • Gillin, P.
  • Computerworld. May 28, 1984, Vol. 18 Issue 22, p4
Subjects
Programming Language, LISP, Workstations, Enhancements, Software, and Domain LISP
Abstract
Apollo Computer Inc. has introduced a version of the LISP programming language for its Domain workstations. Domain LISP conforms to the standard LISP of 1979, and is compatible with the Portable Standard LISP developed at the University of Utah. It features save-restore environment commands, cross-call language capability, and a dynamically scoped binding environment. It also includes an interpreter for checkout and prototyping, and an optimizing compiler. The package runs on all Apollo systems and costs $1,850 per node and $15,500 per site.

28. Prototyping Gives Users More Enthusiasm [1984]

  • Messerich, P.
  • Computerworld. May 28, 1984, Vol. 18 Issue 22, p48SR
Subjects
Prototype, Applications Backlog, Programming, Efficiency, Productivity, Software, and Software Maintenance
Abstract
According to industry experts, eighty-two per cent of a program's bugs are introduced during the specification process, seventeen per cent are introduced during detail design, and only one per cent are introduced during coding. The way to improve programming efficiency is through prototyping. Prototyping enables the finished program to more precisely meet the user's requirements. This, in turn, lowers maintenance requirements and increases the useful life cycle of an application. Because seventy to eighty per cent of a programmer's time is spent on maintenance and enhancements, prototyping frees valuable resources that can be better applied to the applications backlog.

29. Application Generators Focus on Data Base [1984]

  • Pfrenzinger, S.
  • Computerworld. May 28, 1984, Vol. 18 Issue 22, p36SR
Subjects
Program Generators, Applications Programming, Programming, System Design, and Tutorial
Abstract
The design process for systems using application generators is different from traditionally designed systems, in that application generators are data base oriented, not process-oriented. It involves a recommended sequence of events. In order, they include defining the functional requirements, building a data model, understanding the application generator, creating the specifications, conducting design walkthroughs, prototyping, and designing the physical data base.

30. Program Generator an Ally in Battling Backlog [1984]

  • Pines, D.
  • Computerworld. May 28, 1984, Vol. 18 Issue 22, p62SR
Subjects
Program Generators, Applications Backlog, Application Development Software, Programming, and Applications Programming
Abstract
Applications backlog is the single biggest problem facing DP managers. One solution to the problem is program generators, not to be confused with applications generators. Program generators are designed to assist the programmer in the development of a program using procedural languages such as COBOL. Applications generators are strictly end user products. Program generators provide several benefits, including rapid prototyping, minimal debugging, easy code modification, well-organized code, and portability across many systems.

31. General Problem-Solving Methods Will Ease Your Move to Prototyping, If You Use Them [1984]

  • Scharer, L.L.
  • Computerworld. May 28, 1984, Vol. 18 Issue 22, p30SR-31
Subjects
Prototype, System Development, Tutorial, End User, and User Need
Abstract
Prototyping offers both increased development productivity and improved system quality. Prototyping can be broken down into four levels of activity: mock-ups of printed reports or screens; simulated interaction of on-line activity or batch reports; a working model of a system that can be gradually expanded, completed, and implemented; and a research project that uses the model to prove the feasibility of a system design. The best way to conceptualize prototyping is to think of it as anything that lessens the time between when a user describes a specification and then sees the results of the description. Remember, also, that it is a step-by-step proposition; prototyping does not happen overnight.

32. Watch for Prototyping Pitfalls, Speaker Warns Fellow Users [1984]

  • Gillin, P.
  • Computerworld. June 4, 1984, Vol. 18 Issue 23, p49
Subjects
System Development, Prototype, Programming, Applications Programming, Productivity, and Efficiency
Abstract
If used properly, prototyping can be a useful tool, but if used improperly can cause more problems than it solves. To be effective, prototyping should be used within a systems development methodology, though there are times when its use is inappropriate. It should be remembered that prototypes are full working representations of a complete system; poorly designed prototypes will result in poorly designed systems. It should also be realized that while prototyping may reduce coding time, it will not necessarily reduce total project time.

33. Merrill Lynch Breaks Ground with Prototyping Effort [1984]

  • Gillin, P.
  • Computerworld. June 25, 1984, Vol. 18 Issue 26, p6
Subjects
Prototype, Application Development Software, Programming, Applications Programming, COBOL, Securities industry, Merrill Lynch & Company Inc., and Prototype-CICS
Abstract
Using Eureka Software's Prototype-CICS data dictionary- based prototyping tool, a development team at Merrill Lynch has developed a large COBOL applications system under IMS and CICS, despite the fact that none of the team members knew COBOL, only one knew IMS, and only three knew CICS. The project, called the Advanced Order Processing system, consists of fifty subprograms designed to process orders entered at over 1,000 terminals nationwide. Prototype CICS automates much of the design logic. Two features makes it especially useful. It uses a procedural language to create prototypes and it includes a data dictionary which stores all data, screen definitions, and procedural logic.

34. The New Engineers [1984]

  • Campbell, D.
  • Computerworld. June 27, 1984, Vol. 18 Issue 26, p23
Subjects
Application Development Software, Software Selection, Software Packages, Criteria, Productivity, and Efficiency
Abstract
Though viewed with skepticism when they first arrived on the scene in the late 1970s, the market for application development tools is now booming. In 1983, sales reached $215 million; that figure is expected to grow to one billion dollars by 1987. Productivity gains from the use of program development tools range anywhere from ten to 400 percent. It should be realized, however, that the quality, not the quantity, of code is the most important consideration. While using development tools enables programmers to write good code more quickly, they also enable programmers to write bad code more quickly. When considering the purchase of an application development tool, there are several factors to be evaluated, including efficiency, usability by nonprofessionals, prototyping techniques, procedural power, interpretive benefits, integration, file support flexibility and hardware independence.

35. A Trojan Horse for the 'Sos' [1984]

  • Inmon, W.H.
  • Computerworld. June 27, 1984, Vol. 18 Issue 26, p43
Subjects
Relational Database, Database, Evaluation, Appraisal, Database Design, Online, and Online Transaction Processing
Abstract
Relational data bases and relational-like fourth-generation software are useful for many applications, including electronic file cabinet systems, decision support systems, user-friendly systems that must be quickly constructed and changed, and prototyping. But they are not a panacea. Because they consume a lot of hardware resources, they are ineffective for on-line operational processing. After implementing a relational system, one company reported a fifty percent annual increase in the hardware budget over a five year period.

36. Softline - The Director's New MIS (A Fairy Tale) [1984]

  • Bryce, M.
  • Computerworld. July 2, 1984, Vol. 18 Issue 27, p47
Subjects
Application Development Software, Management of EDP, Applications Backlog, Productivity, Nonprocedural Languages, Microcomputer, Program Generators, DBMS, and Information Centers
Abstract
Fouth-generation languages, program generators, prototyping aids, data dictionaries, data base management systems (DBMS), information centers, and personal computers are all heralded as solutions to the problem of applications backlog. In fact, they lengthen backlog and do not improve productivity. In and of themselves, they should not be expected to solve problems of backlog and inefficiency. The key is proper management of program development tools, not chaotic implementation of available technology.

37. Computer-Aided Software Engineering: Automating DP [1984]

  • Gillin, P.
  • Computerworld. August 20, 1984, Vol. 18 Issue 34, p1
Subjects
Software Engineering, Trends, Growth, Application Development Software, System Development, Software Design, Information Systems, Automatic Programming, and Automation
Abstract
Computer-aided software engineering is now entering a period of rapid growth, according to many software productivity experts. Although there are a variety of approaches being taken by vendors of automated software engineering products, all are based on the process of designing an information system rather than toward the task of coding it. They emphasize the kind of structure and discipline that nonprocedural languages and prototyping aids purposely avoid. For many users, however, the focus of these tools on the total system life cycle may be their greatest weakness. The conversion to automated software engineering can be difficult for organizations without strictly defined software design procedures.

38. M&D Calls Millenium 'Cornerstone of Product Strategy' [1984]

  • Computerworld. August 27, 1984, Vol. 18 Issue 35, p15
Subjects
Software, Software Packages, Integrated Software, New Product, Technology, and McCormack and Dodge Corp.
Abstract
McCormack & Dodge's Millenium technology is designed to integrate all the company's applications software into a real-time system. Under Millenium, users can switch from one program to another without leaving their work in progress. The system features a consistent user interface and a full-scale application development and prototyping language. Users are expressing concern about the amount of up-front money required to convert to the Millenium technology and the level of technical support the system will require.

39. Master Software Offers On-Line Programaster Version [1984]

  • Computerworld. Sept 24, 1984, Vol. 18 Issue 39, p72
Subjects
Software Packages, New Product, Online, Applications Programming, Application Development Software, Mainframe Computer, and Programaster-OL
Abstract
Master Software's Programaster-OL is an on-line applications development system that uses reusable code techniques. It features prototyping and screen and report-painting capabilities that can be used in batch and on-line modes. It is designed for IBM mainframes running under MVS with TSO. Annual licenses cost $5,000 plus $2,500-month. Perpetual licenses sell for $95,000.

40. Software Engineering: Problems and Perspectives [1984]

  • Ramamoorthy, C.V., Prakash, A., Tsai, W.T., and Usuda, Y.
  • Computer. Oct 1984, Vol. 17 Issue 10, p191. chart
Subjects
Software Engineering, Software Design, System Development, Requirements Analysis, Specifications, Methods, Software Maintenance, Software Metrics, and Software Quality
Abstract
Software engineering seeks to devise techniques for software development. Software systems go through two principal phases: development, and operations and maintenance. The conventional design-scheme requires that a large amount of time be spent developing specifications. Alternative schemes, include rapid prototyping, the very high level language approach, and the reusability approach. The design phase includes the decomposition of the requirement specification into certain basic elements and partitioning the set of decomposed elements into modules. Current design methodologies include functional decomposition, the data-flow design, and the data-structure design. Software maintenance can be divided into three categories: perfective, adaptive, and corrective maintenance. Software quality assurance aims to optimize reliability, reusability, and efficiency. Tables, graphs, and diagrams illustrate many of the features of software engineering.

41. Cost, Cancellations Impair Software Quality [1984]

  • Burton, K.
  • Computerworld. Nov 26, 1984, Vol. 18 Issue 48, p14
Subjects
Cost, Software, Software Quality, Hardware Error, Study, Increasing Costs, and Product Development
Abstract
According to a study by T. Casper Jones, general manager of the Nolan Norton Co., up to twenty-five percent of all software systems with over 64,000 lines of source code currently under development will be terminated before they are completed. In addition, up to sixty percent will suffer from cost and schedule overruns and approximately seventy-five percent will have serious operational difficulties. In very large programs, the combination of coding and documentation defects and inadequate maintenance results in an average of 300 serious errors per 1,000 lines of code. To correct the problem, longer design times, high speed prototyping and a shorter debugging phase are encouraged.

42. Fourth-Generation Tools Do Not Replace COBOL: IDC Study [1985]

  • McEnaney, M.
  • Computerworld. Jan 28, 1985, Vol. 19 Issue 4, p39
Subjects
Fourth Generation, Programming Language, Nonprocedural Languages, COBOL, Study, Applications Backlog, Response Time, Equipment Acquisition, and Comparative Study
Abstract
According to an International Data Corp. (IDC) study titled 'Fourth-Generation Languages: Information Generators to Meet Information Needs', fourth-generation languages used as a substitute for COBOL result in the loss of a competitive advantage, poor response times, and unnecessary hardware additions. Rather, they are most effective when used as a prototyping-only aid for COBOL-oriented applications. The IDC report praises fourth-generation languages as productivity tools, but warns of lack of standards, limited portability, poor documentation, data transportation problems, and the shortage of experienced fourth-generation personnel.

43. Softalk: Keeping Maintenance Minimal [1985]

  • Computerworld. Feb 4, 1985, Vol. 19 Issue 5, p37
Subjects
Software Maintenance, Programming, Productivity, Survey, Program Development Techniques, Structured Programming, and Programmer
Abstract
Software maintenance may be the major programming problem for the remainder of this century. According to a Computerworld survey, average programmers spend about fifty-five percent of their time on maintenance, up from forty-five percent in 1984. There are several ways to improve programmer productivity, including using structured programming techniques, computer-aided software engineering methods, reusable code, and prototyping aids.

44. Bernard H. Boar: Applications Prototyping: Trades Guesses for Experience [1985]

  • Desmond, J.
  • Computerworld. March 4, 1985, Vol. 19 Issue 9, p45
Subjects
Prototype, Applications Backlog, System Development, and Program Development Techniques
Abstract
While some argue that prototyping decreases the applications backlog and allows for more responsiveness to end-user requirements, others suggest it unnecessarily lengthens the program development life cycle. Bernard H. Boar, the national director of Software Resources Inc., is interviewed. Software Resources is a consulting firm specializing in prototyping. Boar discusses the differences between the prototype life cycle from the typical applications development life cycle, whether prototyping does lengthen the development cycle, how prototyping can reduce an applications backlog, and how a development center determines which applications are suitable for prototyping.

45. Prototyping Seen as Tool for Applications Refinement [1985]

  • Gallant, J.
  • Computerworld. March 4, 1985, Vol. 19 Issue 9, p18
Subjects
Prototype, System Development, Program Development Techniques, and Conferences and Meetings
Abstract
Prototyping is an important factor in the applications development process. While it should not be mistaken for a panacea, it can make it easier for developers to modify a program before the system reaches end users. Prototyping is most effective when used for applications designed to be interactive and predictive.

46. Ethernet Prototyping Equipment [1985]

  • Computer Communications. April 1985, Vol. 8 Issue 1, p103
Subjects
Test Equipment, New Product, System Development, Protocol, RAM, Prototype, Ethernet, LAN, Controllers, EtherServer 1, and EtherServer 2
Abstract
Logic Replacement Technology's EtherServer 1 and EtherServer 2 equipment test and prototyping tools are designed to help accelerate Ethernet system development and installation times. The EtherServer 1 unit is designed to monitor traffic on an Ethernet network. The EtherServer 2 is an echo server that can be used for production testing controllers and for checking cable installations and controller performance.

47. Prototyping [1985]

  • Adamski, L.
  • Computerworld. May 6, 1985, Vol. 19 Issue 18, p23ID-26
Subjects
Prototype, System Development, Program Development Techniques, Systems, Models, Analysis, Methods, and Guidelines
Abstract
The purpose of prototyping is to refine the functions and I-O of a system during the design phase. There are three types of prototyping methods. In its simplest form, a prototype is simply a mock-up of system outputs. A more elaborate prototype is a throwaway functional model of the proposed system. An evolutionary prototype includes all the attributes of a throwaway system; in addition, it is capable of being transformed into the final system. There are six steps involved in the prototyping process: initial user confrontation; first-cut outputs; user review; prototype modification; data structure evolution; and coding program shells.

48. Nicholas Zvegintzov [1985]

  • Desmond, J.
  • Computerworld. June 10, 1985, Vol. 19 Issue 23, p47
Subjects
Software Maintenance, Software Modification, Prototype, Software, Fourth Generation, and State-of-the-Art
Abstract
Nicholas Zvegintzov, editor of Software Maintenance News, a monthly newsletter published by the Software Maintenance Association, is interviewed. He discusses the keys to improving software maintenance, whether it is easier to maintain code written in a fourth generation language, the maintenance implications of prototyping, the lack of adequate maintenance training, and the state-of-the-art in maintenance tools.

49. I-O Statements in Higher Programming Languages [1985]

  • Botting, R.J.
  • Computer. August 1985, Vol. 18 Issue 8, p95
Subjects
Programming, Programming Language, Software Engineering, Methods, and I/O Management
Abstract
Responding to a letter from Robert Baber (Computer, June 1985, p. 112), a reader disagrees with the conclusion that I-O is a conceptual block which hampers software development and argues instead that it is the central concept of intelligible programs. Current programming languages are certainly inadequate, in that they confuse design with implementation. These separate concerns should be dealt with in separate languages, and separate prototyping notions for designer and user should be added. Thus interprocess communication is a vital concept, of which I-O is the simplest expression.

50. The Future of Prototyping as a User-Friendly DP Strategy [1985]

  • Boar, B.H.
  • Computerworld. August 26, 1985, Vol. 19 Issue 34, pSR 28. chart
Subjects
Data Processing, Future Technologies, Prototype, and System Development
Abstract
Prototyping is growing as a requirements definition strategy. Data processing professionals are interested in learning prototyping and its implementation. The future of prototyping will consist of controversies, consultants becoming prototyping experts, prototyping products, and prototyping displacing prespecification. Prototyping will build a path for a fourth-generation development life cycle, which will provide the following benefits:; reduce application development risk, performance modeling to assure operational feasibility, rapid and responsive application, tactical software, and confirmation. A chart of a fourth-generation development life cycle is included.

Catalog

Books, media, physical & digital resources
See catalog results

Guides

Course- and topic-based guides to collections, tools, and services.
Search ""Prototyping"" in all guide pages