Computers in Healthcare. Nov 1989, Vol. 10 Issue 11, p35, 3 p. chart (Flow chart for rapid prototyping)
Subjects
Automation, Hospital Information Systems, User Interface, Artificial Intelligence, and Prototype
Abstract
One way to implement an automated hospital information system is through the use of rapid prototyping of user interfaces. Such a system can overcome one of the main problems of automation, the difference between users needs and expectations and the limitations of designed systems. Prototyping allows the problems to be worked out in a scaled-down model of the system, thereby saving considerable time and money. Artificial intelligence can be of use in a prototype system because of its noted capabilities with user interface development. The non-algorithmic nature of artificial intelligence allows it to use declarative programming to enhance user interface capabilities.
Computerworld. August 8, 1988, Vol. 22 Issue 32, p53, 3 p. chart (Detect errors at their point of origin & not during testing.)
Subjects
Prototype, Project Management Software, Applications Programming, User Relations, and Computer programming -- Methods
Abstract
Prototyping is an effective project management tool when treated as a discrete discipline with a beginning and an end that is defined. Prototyping can be used as a valuable tool in the applications development cycle. Six productivity management principles can be applied to both individual development phases and to the overall development cycle: the job should be applied in detail, people should get involved, time and costs should be estimated, tasks can be based on the 80-hour rule, formal procedures should be created for changes, and system acceptance criteria must be established. A typical concern about prototyping is that it quickly becomes a reason to violate standards.
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.
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.
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.
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.
Applications, Information Systems, Management, System Development, MIS, Prototype, and Relational Data Base Management Systems
Abstract
Applications prototyping has gained acceptances a device for development since the coming of relational data base implementations and fourth-generation languages. Systems professionals can join forces with end users to develop new and enhanced information systems through prototyping. Management information systems managers can obtain the benefits of prototyping by setting up relevant project control, avoiding overkill, fitting the method to the environment, picking a balance team, avoiding overtraining, and involving everyone.
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.
Computerworld. August 26, 1985, Vol. 19 Issue 34, pSR8
Subjects
Implementation, System Development, Pilot Project, and Prototype
Abstract
Rapid prototyping, despite strong predictions, has failed to change software development. Although its strengths and weaknesses have not been evaluated, rapid prototyping is an excellent technique for delivering the correct system to users. Prototyping lets system developers generate parts of a system before the implementation phase. Prototyping saves time and allows the users to define their needs more quickly. Prototyping should include: planning, analysis, first-cut prototyping, prototype iteration, benchmarking, and training. A prototyping center's tools should consist of: text editor, teleprocessing monitor, screen generator, dictionary maintenance tools, report writer, interactive query language, and documentation reporter.
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.
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.
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.
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.
Computerworld. April 7, 1986, Vol. 20 Issue 14, p69
Subjects
Information Systems, Management, Prototype, and System Development
Abstract
Many organizations are failing to receive the full benefits of prototyping techniques, and some individuals utilizing the technique are taking shortcuts which eliminate important stages in the system development process. Many times information systems management is cautious about employing prototyping because of the quick-and-dirty approach used by some organizations. Prototyping is a collection of methods, accomplished in a systematic manner and based on constructing a model of the desired system. The initial model should contain necessary program modules, the data base, screens, reports, and inputs and outputs. Prototyping utilizes the initial model to design the system. Prototyping covers system development to end-user training and eliminates communication problems, satisfies end users, and assists in installing the right system the first time.
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.
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.
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.
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.
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.
Computerworld. August 26, 1985, Vol. 19 Issue 34, pSR 29. chart
Subjects
Applications Backlog, Backlog, COBOL, Data Processing, Insurance Industry, Prototype, and Rexcom
Abstract
The installation of Rexcom, a fourth-generation language and relational data base management system (DBMS), reduced Capitol Bankers Life Insurance Co.'s application development backlog. Capitol Bankers, prior to the installation of the software, was facing a backlog of six to eight months because of rapid growth and programmers' inability to maintain pace using a third-generation language, COBOL. Since installing Rexcom, the backlog has been reduced to three months. Capitol Bankers uses two 6M-byte Prime Computer, Inc. 9950s, linked to a ring network, to run the software. A chart showing the development process at Capitol is included.