This paper defines an information system design theory ISDT to be a prescriptive theory which integrates normative and descriptive theories into design paths intended to produce more effective information systems. The nature of ISDTs is articulated using Dubin's concept of theory building and Simon's idea of a science of the artificial. An example of an ISDT is presented in the context of Executive Information Systems EIS. Despite the increasing awareness of the potential of EIS for enhancing executive strategic decision-making effectiveness, there exists little theoretical work which directly guides EIS design. We contend that the underlying theoretical basis of EIS can be addressed through a design theory of vigilant information systems. Vigilance denotes the ability of an information system to help an executive remain alertly watchful for weak signals and discontinuities in the organizational environment relevant to emerging strategic threats and opportunities. Research on managerial information scanning and emerging issue tracking as well as theories of open loop control are synthesized to generate vigilant information system design theory propositions. Transformation of the propositions into testable empirical hypotheses is discussed.

Building an Information System Design Theory for Vigilant EIS

The paper describes the impact of critical success factors (CSFs) across the stages of enterprise resource planning (ERP) implementations using the responses from 86 organizations that completed or are in the process of completing an ERP implementation. Our results provide advice to management on how best to utilize their limited resources to choose those CSFs that are most likely to have an impact upon the implementation of the ERP system.

/pdf/the-impact-of-critical-success-factors-across-the-stages-of-x988cwivh8.pdf

The impact of critical success factors across the stages of enterprise resource planning implementations

An ontological model of an information system that provides precise definitions of fundamental concepts like system, subsystem, and coupling is proposed. This model is used to analyze some static and dynamic properties of an information system and to examine the question of what constitutes a good decomposition of an information system. Some of the major types of information system formalisms that bear on the authors' goals and their respective strengths and weaknesses relative to the model are briefly reviewed. Also articulated are some of the fundamental notions that underlie the model. Those basic notions are then used to examine the nature and some dynamics of system decomposition. The model's predictive power is discussed. >

An ontological model of an information system

The control relationship between project managers and team members is a central aspect of the working of any Information System I/S design team. This paper combines research on managerial control and team-member control in order to explore a range of control behaviors that can affect the performance of an I/S design team. Measures are developed and validated for managerial control and team-member control from both an outcome and a process perspective. Results from a study of 41 actual I/S design teams indicate that high-performing teams exhibit high process control by managers and high outcome control by team members. The results also support the proposition that both managerial and team-member control coexists and that increases in the total level of control behavior is positively correlated with performance.

Managing I/S Design Teams: A Control Theories Perspective

There is a design methodology calledrapid prototyping which has been used successfully in software engineering. Given the similarities between software design and instructional design, we argue that rapid prototyping is a viable model for instructional design, especially for computer-based instruction. Additionally, we argue that recent theories of design offer plausible explanations for the apparent success of rapid prototyping in software design. Such theories also support the notion that rapid prototyping is appropriate for instructional design. We offer guidelines for the use of rapid prototyping and list possible tradeoffs in its application.

/pdf/rapid-prototyping-an-alternative-instructional-design-1xsz2ikboe.pdf

Rapid Prototyping: An Alternative Instructional Design Strategy

From the Publisher:
This edition continues to react to changes and expected changes in the information technology domain including Year 2000 (Y2K) compatibility,client/server computing,the Internet,intranets,and extranets. Finally,there are exciting systems analysis and design challenges with Enterprise Resource Planning (ERP) applications (such as SAP),systems integration,and business process redesign. Today's students want to "practice" the application of concepts,not just study them. As with the previous editions of this book,the authors wrote it to: 1) Balance the coverage of concepts,tools,techniques,and their applications 2) Provide the most examples of system analysis and design deliverables available in any book 3) Balance the coverage of classical methods (such as structured analysis and information engineering) and emerging methods (e. g.,object-oriented analysis and rapid application development). Additionally,the textbook can serve the reader as a post-course,professional refer-ence for best current practices.

Systems Analysis and Design Methods

Systems Analysis and Design

Systems analysis & design methods , Systems analysis & design methods , کتابخانه مرکزی دانشگاه علوم پزشکی تهران

Systems analysis & design methods

A complete, but less complex approach to SA&D. Introduction to Systems Analysis & Design is organized like Whitten’s best-selling Systems Analysis & Design Methods, but without the information systems architecture framework theme that overwhelms some students. Each chapter covers the same topics, but stops short of advanced details that are unnecessary to the typical first course.
Table of contents
Part One: The Context of Systems Development Projects Chapter 1: The Context of Systems Analysis and Design Methods Chapter 2: Information Systems Development Chapter 3: Project Management Part Two: Systems Analysis Methods Chapter 4: Systems Analysis Chapter 5: Fact-Finding Techniques for Requirements Discovery Chapter 6: Modeling System Requirements with Use Cases Chapter 7: Data Modeling and Analysis Chapter 8: Process Modeling Chapter 9: Object-Oriented Analysis and Modeling Using the UML Chapter 10: Feasibility Analysis and the System Proposal Part Three: Systems Design Methods Chapter 11: Systems Design Chapter 12: Application Architecture and Modeling Chapter 13: Database Design Chapter 14: Output Design and Prototyping Chapter 15: Input Design and Prototyping Chapter 16: User Interface Design Chapter 17: Object-Oriented Design and Modeling Using the UML Part Four: Beyond Systems Analysis and Design Chapter 18: Systems Construction and Implementation

Jeffrey L. Whitten

Papers

Systems Analysis and Design Methods

Systems Analysis and Design

Systems analysis & design methods

Introduction to Systems Analysis & Design

Projects and cases for use with Systems analysis and design methods