The benefits of prototyping as a basis for system design include better specifications, earlier discovery of omissions and extensions, and the likelihood of salvaging much of the effort expended on the prototype. Risks and methods of prototyping during rapid systems development are also noted. (Author/MLW)

Pepperdine University's decision support system provides: (1) user access to data through terminals; (2) the availability of retrieval modules and languages that allow the managers to structure ad hoc reports; (3) access to models through a national network; and (4) training, encouragement and consultation through coordinators. (Author/MLW)

The creation of the Claremont Computing Center as a separate organization to serve only administrative information systems represented a significant change from past combined academic and administrative computing operations. File integration and custom reports are handled by individual users; database design and file maintenance are controlled by…

The development of a new automated alumni and donor support system at UCLA is discussed. Elements of project dynamics that are critical to a large systems development project are described. (Author/MLW)

The entity-relationship (ER) approach to database design is defined, and a specific example of an ER model (personnel-payroll) is examined. The requirements for converting ER models into specific database management systems are discussed. (Author/MSE)

The development of information systems using an engineering approach that uses both traditional programing techniques and fourth generation software tools is described. Fourth generation applications tools are used to quickly develop a prototype system that is revised as the user clarifies requirements. (MLW)

At Clemson University, requests from individual departments for specialized data processing services are increasing. Avenues taken by the division of administrative programing services to respond to department requests include: expanding availability of existing data retrieval and restricting new development to areas of general use by all…

In a 1981 national survey, nearly 80 percent of the surveyed institutions reported they were either already using or were planning to use computer-based administrative information systems. This survey is discussed and institutional predictors of the impact of information systems are analyzed. (MLW)

Clemson University has developed techniques and procedures to assist in the construction and maintenance of administrative systems. Procedures as well as the tools and techniques used by all systems are discussed: online report request software, online user table maintenance software, report supervisor and report writer software, etc. (Author/MLW)

A project management system for organizing requests from multiple departments and controlling the workload of the development/maintenance computer staff is described. Practical solutions to deciding project priorities, determining time estimates, creating positive peer pressure among programing staff, and formalizing information requests are…

The development and implementation of an institutional framework to guide the management and use of information technologies (computing, office automation, and telecommunications) at Mount Royal College in Calgary, Alberta, are described. (Author/MLW)

In 1981 a project to determine the current information needs of the institution was outlined and strategies for meeting those needs were identified. Each administrative office has full responsibility for data and production scheduling, while the computing center ensures that the software and hardware are operational. (MLW)

The design of a database interface, the different types of decisions supported, the nature and applications of the system outputs, and continuing work on extending the system are described. The system was designed to forecast the enrollment for Guilford College. (Author/MLW)

The development of a faculty information system from the perspectives of need, objectives, file structures, and the interaction between the faculty and administration during data collection is discussed. The file includes biographical data of the faculty, staffing assignments, and projections for tenure, promotion, and retirement. (Author/MLW)

The development of a faculty information system from the perspectives of need, objectives, file structures, and the interaction between the faculty and administration during data collection is discussed. The file includes biographical data of the faculty, staffing assignments, and projections for tenure, promotion, and retirement. (Author/MLW)