管理信息系统Session Four.ppt

Management Information System Limitations of the Lifecycle Approach The system lifecycle approach is costly, time-consuming, and inflexible. Volumes of new documents must be generated and steps repeated if requirements and specifications need to be revised. Formal specification of requirements may inhibit system-builders from exploring and discovering the problem structure (Fraser et al., 1994). the lifecycle approach is not suitable for many small desktop systems, which tend to be less structured and more individualized. Management Information System Prototyping Prototyping The process of building an experimental system quickly and inexpensively for demonstration and evaluation so that users can better determine information requirements. Prototype The preliminary working version of an information system for demonstration and evaluation purposes. Management Information System Prototyping The prototype is a working version of an information system or part of the system, but it is meant to be only a preliminary model. Once operational, the prototype will be further fined until it conforms precisely to users’ requirements. Once the design has been finalized, the prototype can be converted t a polished production system. Steps in Prototyping Step 1: identify the user’s basic requirements. The system designer (usually an information systems specialist) works with the user only long enough to capture his or her basic information needs. Management Information System Step 2: develop an initial prototype. The system designer creates a working prototype quickly, most likely using the fourth-generation software tools that speed application development. Some features of computer-aided software engineering (CASE) tools can be used for prototyping as can multimedia software tools that present users with interactive storyboards that sketch out the tasks of the proposed system for evaluation and modification (Madsen and Aiken, 1993). (See Fig-2 The prototyping process). Step