articles+ search results
58 articles+ results
1 - 20
Next
Number of results to display per page
-
Cacace, Filippo, Ceri, Stefano, Tanca, Letzia, and Crespi-Reghizzi, Stefano
- IEEE Transactions on Software Engineering. June 1992, Vol. 18 Issue 6, p534, 13 p. program
- Subjects
-
Software engineering, Scientific Research, Program Development Techniques, Database, Programming Language, Rule-Based System, Rapid Prototyping, Object-Oriented Programming, Relational Database, and Software engineering -- Methods
- Abstract
-
The design and rapid prototyping of data-intensive software applications can be accomplished via the use of Logres and Algres, two advanced database programming languages. Logres, a new-generation programming language, integrates rule-based programming with an object-oriented data model. Algres is a relational system that manages complex database relationships. Algres does not have the necessary programming constructs needed to implement imperative computations. Expressive power and openness to external libraries can be gained by embedding Algres into the C programming language, resulting in the Alice programming interface. THe Logres/Algres software platform allows data-intensive applications to be prototyped rapidly.
- Full text View on content provider's site
-
Berzins, Valdis, Yehudai, Amiram, and Luqi
- IEEE Transactions on Software Engineering. May 1993, Vol. 19 Issue 5, p436, 17 p. table
- Subjects
-
Software Design, Prototype, Specifications, Methods, Software engineering, and Software engineering -- Methods
- Abstract
-
Use of software transformations for software evolution is examined. The effects of software transformations on program synthesis and program optimization have been studied extensively, but it remains difficult to specify the desired behavior of a software system before the implementation is developed. The use of software transformations for developing requirements based on software prototyping is explored. Emphasis is placed on transformations that change a system's behavior. A new, general classification of transformations is presented. The transformations are based on their effects on system interfaces, externally observable behavior and the abstraction level of a system description. A process model for software evolution is described that utilizes prototyping techniques and utilizes the new class of transformations to support the process.
- Full text View on content provider's site
-
Davis, Alan M.
- IEEE Software. Sept, 1992, Vol. 9 Issue 5, p70, 9 p. table
- Subjects
-
Prototype, Methods, Computer Science, Software Engineering, Program Development Techniques, and Software Engineering -- Methods
- Abstract
-
Operational prototyping avoids the dangers of combining rapid prototypes with evolutionary prototypes by layering a rapid prototype atop a solid evolutionary base. Rapid, or throwaway, prototypes are often used in an attempt to discover the customer's true needs; evolutionary prototypes are built in a quality manner and implement only confirmed requirements. Both have their limitations, and a combination of the two often results in trying to extensively evolve a rapid prototype. With an operational prototype, an evolutionary prototype is made into a baseline using typical development methods, and only the requirements that are well understood are specified and implemented. Multiple customer sites and a trained prototyper receive copies of the baseline, and the prototyper watches the user at the system at each site. Additional operational prototyping concepts are discussed.
- Full text View on content provider's site
-
Eliot, Lance B.
- IEEE Expert. Summer, 1989, Vol. 4 Issue 2, p2, 4 p.
- Subjects
-
Prototype, Programming Language, Software Engineering, and Expert Systems
- Abstract
-
Rapid prototyping languages are being developed to reduce the cost of software development. A software prototype is an executable initial version of a proposed system. Prototypes are built to assess the usefulness and performance of a proposed system, and as such, they must be built economically and quickly. Th goals of a rapid prototyping language are: to rapidly construct and adapt software; to enable development of more powerful systems; to validate that proposed systems are acceptable to users; to check the internal consistency of proposed designs; to ensure the correctness of transformations; and to verify that implementations fully conform to specifications. The design of a rapid prototyping language discussed, with special attention paid to issues involving expert system prototyping.
- Full text View on content provider's site
-
Jordan, Pamela W., Keller, Karl S., Tucker, Richard W., and Vogel, David
- Computer. May 1989, Vol. 22 Issue 5, p39, 10 p. chart (Comparison of stages of software storming and expert-system development.)
- Subjects
-
Software Engineering, New Technique, Case Study, Methods, Utilization, System Design, Prototype, Resource Allocation, Artificial Intelligence, State-of-the-Art, and Mitre Corp. Artificial Intelligence Technical Center -- Research
- Abstract
-
The Artificial Intelligence Center of Mitre Corp (McLean, VA) developed software storming as an experimental method for prototyping software systems more rapidly and with greater functionality than with other prototyping methods. Software storming is an intense four-week initial prototype software design and implementation effort (plus follow-on phase) that utilizes domain experts and knowledge engineers plus state-of-the-art software development tools and hardware. The four weeks consist of problem definition, action plan development, brainstorming during knowledge engineering and analysis and review. The follow-on phase consists of revision and refinement of the software system. The major differences from other prototyping methods are use of experts to work with knowledge engineers to incorporate appropriate knowledge into a software system and evaluate it and the videotaping of the storming process to improve technique. Software storming was applied to the design of a software system for optimizing placement of equipment in the US Army Mobile Subscriber Equipment System.
- Full text View on content provider's site
-
Gupta, Rajiv, Cheng, Wesley H., Gupta, Rajesh, Hardonag, Ido, and Breuer, Melvin A.
- Computer. May 1989, Vol. 22 Issue 5, p28, 10 p. chart Layered organization of Cbase.
- Subjects
-
Very-Large-Scale Integration, Computer-Aided Design, Software Engineering, Methods, Object-Oriented Data Bases, Utilization, Iteration, Requirements Analysis, Specifications, Ontologic Inc. -- Product information, and Vbase (Data base management system) -- Usage
- Abstract
-
The development of the Cbase computer-aided design (CAD) framework for very-large-scale integration (VLSI) circuit design at the University of Southern California demonstrates the value of a rapid prototyping strategy based on an object-oriented data base management system (OODBMS). A major problem in the development of large software systems is specifying and analyzing the potential users' requirements. The software engineer needs tools that enable the evolution of the system design in a manner that can accommodate incomplete initial requirements specifications as well as changing requirements. Rapid prototyping tools enable interactive development, refinement and analysis of multiple software system prototypes. An OODBMS facilitates the process by providing reusable code modules, powerful modeling capabilities and generic programming. Ontologic's commercial Vbase OODBMS package and the Massachusetts Institute of Technology X11 toolkit were employed to develop Cbase.
- Full text View on content provider's site
-
Luqi, Berzins, Valdis, and Yeh, Raymond T.
- IEEE Transactions on Software Engineering. Oct 1988, Vol. 14 Issue 10, p1409, 15 p. table Consumer timing chart.
- Subjects
-
Real-Time System, Prototype, Programming Language, ADA, Embedded Systems, Large-Scale Systems, Software Quality, Software Engineering, and Technology
- Abstract
-
Present software development methods are not sufficient to handle the fast growing demand for larger systems and higher-quality software. Rapid prototyping may be the solution for improved programming productivity and software reliability. PSDL is a system description language for describing prototypes of real-time software systems. PSDL supports rapid prototyping based on abstractions and reusable software components. It is useful for very large real-time systems and for prototyping typical Ada applications. Information is provided on control constraints, computational models, timing constraints, hierarchical constraints, requirements for the hyperthermia system, prototyping methodology and the support environment.
- Full text View on content provider's site
-
Duke, Eugene L., Brumbaugh, Randal W., and Disbrow, James D.
- Computer. May 1989, Vol. 22 Issue 5, p61, 6 p. chart Remotely augmented vehicle concept.
- Subjects
-
Prototype, Methods, Aerospace Engineering, Research and Development, Flight Control Systems, System Development, Strategic Planning, Software Engineering, United States. Dryden Research Center, Simulation, Flight Simulator, and United States. Dryden Flight Research Center -- Research
- Abstract
-
The Dryden Flight Research Facility of the NASA Ames Research Center (Edwards, CA) has developed and is enhancing a rapid prototyping facility (RPF) for developing and testing advanced avionics systems. Specifically, the system is designed to perform flight research on avionics employing conventional techniques and/or knowledge-based systems (KBSs) for control. RPF is an extension of the agency's remotely augmented vehicle (RAV) facility, which tests a variety of control algorithms on research aircraft without the need for expensive ongoing avionics modifications. RAV consists of a research aircraft, ground-based auxiliary computational facility and simulator for flight systems development and validation. The enhanced RPF will enable flight-test planning and the real-time simulation of flight performance. Details of the system are discussed.
- Full text View on content provider's site
9. Software prototyping by relational techniques: experience with program construction systems [1988]
-
Ceri, Stefano, Crespi-Reghizzi, Stefano, Di Maio, Andrea, and Lavazza, Luigi A.
- IEEE Transactions on Software Engineering. Nov 1988, Vol. 14 Issue 11, p1597, 13 p. chart Subschemas of the PCDB.
- Subjects
-
New Technique, Relational Languages, Research and Development, Methods, Application Development Software, Cost Benefit Analysis, Applications, System Design, Strategic Planning, ADA, Prototype, and Software Engineering
- Abstract
-
A relational programming methodology is developed that enables the rapid design and prototyping of complex, evolutionary software applications, even by non-professionals with minimal supervision. Only relational data structures are used for system content and interface, and programming uses relational languages with an emphasis on relational algebra. The method is successfully applied to the development of two large projects: the Ada Relational Translator experimental compiler-interpreter for Ada and the Multi-Micro Line tool set for constructing multi-microprocessor applications. Cited advantages of the relational programming methodology include: avoiding early commitment to designing data structures and algorithms, extensive facilities for extracting data views when unanticipated functions must be added, and program structuring is decoupled from programming group structure.
- Full text View on content provider's site
10. Experimental prototyping in Smalltalk [1987]
-
Diederich, Jim and Milton, Jack
- IEEE Software. May 1987, Vol. 4 Issue 3, p50, 15 p. chart (Class definitions and variations.)
- Subjects
-
Prototype, New Technique, Application Development Software, Object-Oriented Languages, Smalltalk (Computer program language), Software Design, and Software Engineering
- Abstract
-
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.
- Full text View on content provider's site
-
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.
- Full text View on content provider's site
-
Smith, W.
- Computerworld. Sept 16, 1985, Vol. 19 Issue 37, p17
- Subjects
-
Prototype, Software Design, Software Engineering, and System Development
- Abstract
-
Some software development groups have little understanding about the prerequisites for successful prototyping. There are two approaches to prototyping: requirements prototyping and evolutionary development. In requirements prototyping, a prototype is used to define an initial solution to the prolem, while in evolutionary development, the prototype becomes the center of the developing system. Regardless of the prototyping approach, the result is a model used as a mechanism to define the final system solution.
- Full text View on content provider's site
13. Prototyping, ADS-Online join to triple productivity: AT&T Communications speeds development process [1986]
-
Babcock, Charles
- Computerworld. April 7, 1986, Vol. 20 Issue 14, p29
- Subjects
-
Telecommunications Industry, Performance, Prototype, Software Engineering, and System Development
- Abstract
-
AT&T Communications has made considerable productivity gains by utilizing application prototyping with Cullinet Software Inc.'s ADS-Online development language. On the average, the productivity rate was tripled for fifteen communications applications developed during the last eighteen months. An additional sixteen communications applications have been developed, besides the fifteen in production. AT&T Communications has confidence in prototyping and believes that prototyping works.
- Full text View on content provider's site
-
Hamilton, Rosemary
- Computerworld. April 7, 1986, Vol. 20 Issue 14, p33
- Subjects
-
Prototype, Simulation of Computer Systems, Software Engineering, Computer Software Industry, and Software Garden Inc. -- Product introduction
- Abstract
-
Dan Bricklin, one of the developers of Visicalc, has started Software Garden Inc., a one-man company. The Dan Bricklin Demo Program, a prototyping device for personal computer software, is an apparent success with early users. The Demo Program allows users to produce program simulations or tutorials for programs. Also, users have the ability to generate a product before it exists, and present it to OEMs and demonstrate it.
- Full text View on content provider's site
-
Kaniper, C.A.
- Computerworld. Sept 18, 1985, Vol. 19 Issue 37, p41
- Subjects
-
Applications Backlog, Backlog, Fourth Generation, Prototype, System Development, Software Engineering, and MIS
- Abstract
-
Because of the tremendous demand for specific computer applications in companies, management information systems (MIS) managers are years behind in completing applications for users. Fourth generation languages can be used to prototype applications so that development time is shortened and satisfaction with the final product is greater. By making a prototype of the application before actually creating it, MIS managers find that the end users are happier since they take a part in the development process, the program is better suited for its intended purpose, and there is less user training required. One company had a 60 percent increase in productivity in the data processing department after it switched to a fourth generation development system, and the inclusion of end users in the development process helped in almost all respects of application creation. A graph indicates increases in logic and functionality in a system through prototyping and interactive development.
- Full text View on content provider's site
-
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.
- Full text View on content provider's site
17. An optimizer using the software component paradigm for the optimization of engineering systems [2007]
-
Alessandro Formisano, B. Delinchant, D. Duret, L. Estrabaut, L. Gerbaud, H. Nguyen Huu, B. Du Peloux, H.L. Rakotoarison, F. Verdiere, and Raffaele Martone
- COMPEL -The international journal for computation and mathematics in electrical and electronic engineering, 2007, Vol. 26, Issue 2, pp. 368-379.
- Full text View on content provider's site
18. Rapid prototyping in software development [1989]
-
Tanik, Murat M. and Yeh, Raymond T.
- Computer. May 1989, Vol. 22 Issue 5, p9, 2 p. chart Process model for software/system evolution.
- Subjects
-
Prototype, Software Engineering, Methods, Integrated Approach, Software Design, Utilization, and Comparison
- Abstract
-
Computer-aided rapid software prototyping is a highly efficient method for the rapid development of low-maintenance software. The technology is based on a process model that focuses on requirements specification, design, validation, evaluation and tradeoffs between the related software and hardware systems. Rapid prototyping provides evolutionary development of software through the use of an integrated design environment. The output of the process is a working software system model that may be used as a functional or behavioral specification for the final product, a feasibility study for a more complex system or validation of the requirements of the target software system. Advantages of rapid prototyping include greater use of abstraction earlier in the software development process, lower cost of software maintenance and easier integration into the entire hardware/software system.
- Full text View on content provider's site
19. Giving prototyping free rein or just due [1987]
-
Barnes, John
- Computerworld. Sept 7, 1987, Vol. 21 Issue 36, p21, 2 p.
- Subjects
-
Prototype, Programming, Software Engineering, Applications Programming, User Need, and User Relations
- Abstract
-
Successful prototyping of software can fulfill needs of users who may not have originally known what their needs were. The variety of new prototyping tools, expert system shells, object-oriented languages, and other artificial intelligence products is likely to lead to the development of a completely original prototype, not just a new prototype technique. Products that were developed without full knowledge of what they would eventually be used for include the Visicalc spreadsheet, word processors, and computers themselves. Prototyping will encourage the human habit of probing for answers, rather than desperately seeking a way to fence answers out.
- Full text View on content provider's site
-
Huling, Jim
- Computerworld. April 20, 1987, Vol. 21 Issue 16, p74, 1 p.
- Subjects
-
Computer-Aided Software Engineering, Application Development Software, Software Engineering, Code Generator, Program Development Techniques, Project Life Cycle, Industrial project management, Prototype, Syntax Analyzers, and Program Verification
- Abstract
-
The common elements of tool kits for computer-aided software engineering (CASE) are described. A graphics tool is a crucial part of a CASE product used for creating program-structure charts, data-flow diagrams, and data-structure diagrams. CASE tool kits generally support a particularly methodology for structured analysis and design along with an appropriate method of syntax verification. Other elements of CASE tool kits include: central information repository; prototyping tools such as menu, screen and report generators; and code generators. Project management tools are an important part of the development life cycle but are not widely available in CASE products.
- Full text View on content provider's site
Catalog
Books, media, physical & digital resources
Guides
Course- and topic-based guides to collections, tools, and services.
1 - 20
Next