articles+ search results

Applications Programming, Backlog, Applications Backlog, Prototype, Methods, Information Systems, System Design, and Models

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.)

Ink Jet Printer, Printers, Hybrid Circuits, Circuit Printing, Integrated Circuit Fabrication, Methods, Substrates, and Microelectronics

Rapid prototyping is possible in computer controlled ink jet printing of hybrid circuits. Other advantages of this kind of printing are also analyzed. Development of the ink jet printer is discussed. This printing is feasible for printing well defined conductor lines. Spray control parameters of the printer are analytically expressed. A block diagram of the ink jet printing system is included. Photographs show line formation. Graphs show the effect of substrate speed and frequency on line widths and thickness of silver films.

Circuit Design, Guidelines, Metallurgy, Substrates, Materials Analysis, Prototype, Technology, Resistor, Conductors, and Circuitry

Utilization of porcelain enameled metal substrate (PEMS) technology requires multiple rounds of prototyping. Materials capabilities are analyzed for PEMS. Design guidelines help in utilization of PEMS. Several guidelines are given. A table lists metal thicknesses. A diagram indicates dimensional adjustments required.

Software, Process Control, Real-Time System, Software Engineering, Application Development Software, Programming, Prototype, Requirements Analysis, and System Development

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.

Prototype, Specifications, Performance Specifications, Software Engineering, Program Development Techniques, and Comparative Study

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.

Software Engineering, Software Design, System Development, Requirements Analysis, Specifications, Methods, Software Maintenance, Software Metrics, and Software Quality

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.

Hospitals, United States, Computers standards, Information Systems standards, and Software standards

Programming, Programming Language, Software Engineering, Methods, and I/O Management

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.

Prototype, Design, Computer-Aided Design, and Boards/Cards

Building a prototype board is the last stage in the design process. The design for a board can be sent to an independent shop or it can be fabricated in-house. A tape is usually produced by CAD systems. Wire wrapping is the oldest approach to board prototyping. New approaches are represented by a liquid-chemistry process or a milling process.

Computer-Aided Software Engineering, Systems, Functional Capabilities, Applications, Outlook, Market, Hardware Vendors, Trends, Programming, Applications Backlog, Performance, Evaluation, and ADA

Software is 80 percent of new systems development cost, software maintenance costs are even greater, there is a 30 month software development backlog, and the annual need for programmers is over twice this year's 55,000 computer science graduates and getting worse. Consequently, there will be a $1 billion market for computer-aided software engineering (CASE) tools by 1990. CASE tools are either non-language-specific or language-specific, most commonly Ada because of federal demand, and provide modular development in analysis, design, prototyping, coding, testing, integration, and maintenance. Several CASE systems are described in detail.

Programming Language, Expert Systems, Software Design, Evaluation, System Design, Application Development Software, and Small-X (Program development software)

Small-X is a programming language designed for building expert systems that is not for the computer novice. A Small-X program consists of statements called rules. The language provides two key features that distinguish it from other languages: a set of pattern-matching and evaluation functions, and the automatic handling of control flow. Small-X also has good debug features that allow users to trace rules. The manual for Small-X is complete and well-written. The language serves as a tool for learning about expert systems and for prototyping trial applications, but it is not the most trustworthy of program development systems.

Object-Oriented Languages, programming languages (electronic computers), Evaluation, Performance, Functional Capabilities, and Dynamic Programming

Smalltalk is an object-oriented programming language in which objects represents data sets plus functions. The objects are composed of classes of reusable and redefinable building blocks, and messages are sent to objects for data or for action. Advantages include an open and interactive environment, incremental and dynamic program development providing easy applications prototyping, programming by refinement, and lack of distinguishing between data and code enabling creation of programs that can dynamically build other programs, all providing high programmer productivity. Major commercial applications include artificial intelligence, R&D, and business and technical analysis.

Programming Language, Programming, Scientific Research, and Mathematical Programming

We describe linear future semantics, an extension of linear history semantics as introduced by Francez, Lehmann, and Pnueli, and show how it can be used to add multiprocessing to languages given by standard continuation semantics. We then demonstrate how the resulting semantics can be implemented. The implementation uses functional abstractions and non-determinacy to represent the sets of answers in the semantics. We give an example, using a semantic prototyping system based on the language Scheme. (Reprinted by permission of the publisher.)

Programming Language, PROLOG, Compiler/decompiler, and Algorithm

The use of Prolog as a language offers advantages for describing succinctly most of the algorithms needed in prototyping and implementing compilers, or producing tools that facilitate the task of compiling. One approach in implementing compilers using Prolog consists of coupling actions to recursive descent parsers to produce syntax-trees, which are utilized in guiding the generation of assembly code. Prolog is not only used in parsing and compiling, but is a labor-saving device in prototyping and implementing many non-numerical algorithms which arise in compiling. Unification and nondeterminism as means to circumvent costly unnecessary features are also discussed. Other topics include: bottom-up and top-down parsers; syntax-directed translation; grammar properties; code generation; and newly proposed features for compiler construction.

Prototype, New Technique, Application Development Software, Object-Oriented Languages, Smalltalk (Computer program language), Software Design, and Software Engineering

The Smalltalk object-oriented programming language developed at the Xerox Palo Alto Research Center in the early 1970s offers a completely new environment for software development. Smalltalk is not easy to learn, even for programmers with experience in standard languages. Excellent references to Smalltalk are the Blue Book and the Orange Book: the Blue Book deals mainly with features of the language, while the Orange Book deals with the environment. Learning the language poses a short-term disadvantage, but the long-term gains in productivity may be worth the initial investment. Commercial versions of Smalltalk are available on workstations like the Tektronix 440X series, the Sun, and the IBM PC AT; implementations for the MicroVAX are under development.

Humans, Pedigree, Data Collection, Database Management Systems, Genetic Diseases, Inborn, and Software

This work examines some of the problems encountered in developing small and large database application systems involving human genetics data collection efforts that include data on individuals as well as family pedigree data. Rapid prototyping of a database application requires software tools to produce the application with little or no programming. Features of MEGADATS-4 that provide for rapid prototyping and for producing stand-alone applications are examined.

PROLOG, Program Logic, Data Structures, Language Analysis, programming languages (electronic computers), Language Complexity, Applications Programming, Enhancements, Productivity, Artificial Intelligence, Expert Systems, and System Design

The Prolog programming language manipulates complex data structures and flexibly presents real-world knowledge using the same inference methods that humans use in reasoning. Prolog is one of the two most commonly used languages in artificial intelligence, along with LISP; it can run on machines ranging from microcomputers to mainframes, has modest memory requirements, and can be used with a wide range of operating systems, including UNIX, VMS, and DOS. Other Prolog advantages include its speed, explanation facilities, natural-language processing capabilities, and pattern-matching mechanism. Prolog is easy to use, accurate, an excellent prototyping tool, and well suited to integration with other software and use in data processing. Current Prolog applications include, but are not limited to, CAD-CAM, process control, compiler implementation, and natural-language processing.

System Development, Comparative Study, System Design, Design, Methods, Project Management Software, Requirements Analysis, Research and Development, and Prototype

This article presents a retrospective comparative study of the use of the system development life cycle (SDLC) and prototyping methods to help select a development approach for a given information systems (IS) project. The respondents were asked (a) to decide independently whether one of their recent IS projects was developed using either the SDLC or prototyping approach and if so, (b) to evaluate the merit of that approach in terms of ease of project management, project requirements, project characteristics, impact on decision making, and user and designer satisfaction. The results indicate: (1.) Design methods cannot be considered apart from project, environment and decision characteristics. (2.) A clear cut preference of one method over the other could not be established. Each method performed better in some areas that in others. (3.) A framework that can be used by a project director for selecting a design method to develop a system could be postulated. (Reprinted with permission of the publisher.)

Application Development Software, Prototype, and Programming

Logic programming has great potential for reducing the cost of software development. We argue that, with an appropriate programming methodology, a logic programming system provides a powerful tool for rapid software prototyping. It is sufficiently formal and high-level to allow reasoning about specifications, and it provides an immediate operational validation of the programmer's intuitions. The methodology is introduced by means of an example larger than those usually used to illustrate the advantages of logic programming. We start with an informal specification of a structure-editor, show how it is formalized into a directly executable prototype, and introduce guidelines for validating logic programming code as implemented in Prolog. The developed prototype can be used for a number of applications: syntax-directed editor, semantic network browser, etc. The editor is compact but readable, and is quite efficient. (Reprinted by permission of the publisher.)

Database Management Systems, Medical Informatics Applications, Programming Languages, Software Design, Information Systems, and Software

AIDA consists of a set of software tools to allow for fast development and easy-to-maintain Medical Information Systems. AIDA supports all aspects of such a system both during development and operation. It contains tools to build and maintain forms for interactive data entry and on-line input validation, a database management system including a data dictionary and a set of run-time routines for database access, and routines for querying the database and output formatting. Unlike an application generator, the user of AIDA may select parts of the tools to fulfill his needs and program other subsystems not developed with AIDA. The AIDA software uses as host language the ANSI-standard programming language MUMPS, an interpreted language embedded in an integrated database and programming environment. This greatly facilitates the portability of AIDA applications. The database facilities supported by AIDA are based on a relational data model. This data model is built on top of the MUMPS database, the so-called global structure. This relational model overcomes the restrictions of the global structure regarding string length. The global structure is especially powerful for sorting purposes. Using MUMPS as a host language allows the user an easy interface between user-defined data validation checks or other user-defined code and the AIDA tools. AIDA has been designed primarily for prototyping and for the construction of Medical Information Systems in a research environment which requires a flexible approach. The prototyping facility of AIDA operates terminal independent and is even to a great extent multi-lingual. Most of these features are table-driven; this allows on-line changes in the use of terminal type and language, but also causes overhead. AIDA has a set of optimizing tools by which it is possible to build a faster, but (of course) less flexible code from these table definitions. By separating the AIDA software in a source and a run-time version, one is able to write implementation-specific code which can be selected and loaded by a special source loader, being part of the AIDA software. This feature is also accessible for maintaining software on different sites and on different installations.