Showing papers on "Rapid application development published in 1991"

Reusing designs for rapid application development

Abstract: Software design reuse can be an especially effective form of reuse when an organization builds many variations of a particular kind of system. Reusable designs can be used in conjunction with an application generator shell to facilitate the construction of domain-specific application generators, which have been shown to dramatically reduce the effort required to construct high-quality application software. Principles are presented for reusable designs and a description is given of the technology necessary for constructing a supporting application generator shell. >

Introducing Systems Design

Abstract: From the Publisher: In this new edition of Introducing Systems Design, (the companion text by the same author to Introducing Systems Analysis) the focus is on the design of computer systems. The author describes the skills necessary to be a successful systems designer and addresses the fundamental models that such a designer should follow (such as data flow diagrams and entity-relationship models). This edition retains the hypothetical case study of the first edition (a course bookings system) to explore crucial design issues. New coverage includes discussions of object oriented systems design and Rapid Application Development (RAD), including the impact of Computer Aided Software Engineering (CASE). Use of the integral case study and exercises at the end of each chapter provide the practical element essential to effective teaching of systems design.

A goal-driven cognitive model of the systems evaluation process

Abstract: Researchers have tried to build valid and reliable instruments for measuring users' assessments of IS. However, focusing on instruments is a somewhat ineffective way of dealing with problems associated with the evaluation process itself. This paper presents a model of the process by which individuals evaluate an IS. The model emphasizes the importance of raters' goals. To form an evaluation, raters seek information about an IS and compare it to their normative beliefs. The information they seek is influenced by their task support goals. Evaluations can be adjusted to serve raters' social adjustment, value expressive, and protective goals. Empirical evidence supporting the model is discussed, along with the model's implications for system developers. Some suggestions for future research are made. 1. INTRODUCI'ION information satisfaction (UIS) (e.g., Bailey and Pearson 1983; Doll and Torkzadeh 1988; Ives, Olson and Baroudi Users' evaluations of information systems (IS) are impor1983; Jenkins and Ricketts 1985). Some researchers have tant for two main reasons. First, user evaluations provide identified limitations of UIS instruments. For instance, information to help guide development. In prototyping Galletta and Lederer (1989) note problems with scale units (Naumann and Jenkins 1982), user evaluations are a and origins, item heterogeneity, and reliability. Ryan and central part of the project control mechanism. A developBock (1990) have suggested that the ambiguity of items in er gives a prototype to a user for evaluation and changes UIS instruments complicates the interpretation of rater's the prototype based on the user's suggestions for improveresponses. However, some of these problems are not ments. If the user's ideas about the system are incorrect, characteristics of the instruments per se, but of the way then development could proceed in the wrong direction. they are used. For instance, some users have little contact with IS developers and cannot evaluate them accurately, no More recent development methodologies also emphasize matter what the instrument. the importance of user evaluations. For example, Martin's (1991) Rapid Application Development methodology The current literature on users' evaluation resembles the involves four different user teams who evaluate everything literature on employee performance appraisal as it was a from requirements specifications to general design to the decade ago. Traditionally, researchers focused their efforts final system. Martin claims that users should actively on appraisal instruments, trying to reduce bias and increase participate in every phase of IS development. reliability (Landy and Farr 1980). However, Ilgen and Favero (1985) noted that focusing on scale construction is The second reason that user evaluations are important is a weak and indirect way of dealing with what are really that the evaluations guide the behavior of the users problems in human judgment. Landy and Farr (1980) themselves. For example, Davis, Bagozzi and Warshaw recommended a shift away from research on instruments (1989) found that individuals' intentions to use an IS are to research aimed at understanding how raters evaluate influenced by their evaluations of a system's usefulness and employees. In response, researchers have developed ease of use. If their evaluations are not accurate, users models of the evaluation process (e.g., DeNisi, Caferty and could act incorrectly. On the one hand, they might waste Meglino 1984). Later work has reflected a concern for resources on a system that initially seemed valuable but process issues. For instance, Pulakos (1986) developed turned out not to be effective. On the other hand, users successful rater training programs based on the implicacould miss an opportunity to improve performance by tions of process models. choosing not to use a system that has value. Given the importance of users' evaluations of IS, similar Researchers have designed instruments to quantify users' efforts by MIS researchers are warranted. This paper evaluations. Much of this work has focused on user introduces a model of the process by which an individual

Ada and the rapid development lifecycle

Abstract: JPL is under contract, through NASA, with the US Army to develop a state-of-the-art Command Center System for the US European Command (USEUCOM). The Command Center System will receive, process, and integrate force status information from various sources and provide this integrated information to staff officers and decision makers in a format designed to enhance user comprehension and utility. The system is based on distributed workstation class microcomputers, VAX- and SUN-based data servers, and interfaces to existing military mainframe systems and communication networks. JPL is developing the Command Center System utilizing an incremental delivery methodology called the Rapid Development Methodology with adherence to government and industry standards including the UNIX operating system, X Windows, OSF/Motif, and the Ada programming language. Through a combination of software engineering techniques specific to the Ada programming language and the Rapid Development Approach, JPL was able to deliver capability to the military user incrementally, with comparable quality and improved economies of projects developed under more traditional software intensive system implementation methodologies.