12-11 Information Requirements Analysis The goal of the second stage of the model, the information requirement analysis, is to ensure that the various information systems, databases, and networks can be integrated to support decision making and operations.
12-12 Information Requirements Analysis Conducting a requirements analysis Using the requirements analysis for planning Resource allocation
12-13 Conducting a Requirements Analysis Define underlying organizational systems Develop subsystem matrix Define and evaluate information requirements for organizational subsystems Define major information categories and map interviews into them Develop information matrix
12-14 Using the Requirements Analysis for Planning Identify high payoff categories Provide an architecture
12-15 Resource Allocation Resource allocation consists of developing hardware, software, data communications, facilities, personnel, and financial plans needed to execute the master development plan as defined in the requirements analysis.
12-16 Planning Information Technology Architectures An IT architecture consists of the combination of hardware, software, data, personnel, and telecommunications elements within an organization, along with procedures to employ them.
12-17 Planning Information Technology Architectures Centralized architecture Noncentralized computing Client / server architecture IT infrastructure considerations Choosing among architecture options End-user computing architecture issues Reengineering legacy systems
12-19 Noncentralized Architecture Noncentralized computing architectures are either decentralized or distributed.
12-20 Decentralized Computing Decentralized computing breaks centralized computing into functionally equivalent parts, with each part essentially a smaller, centralized subsystem.
12-21 Distributed Computing Distributed computing breaks centralized computing into many computers that may not be (and usually are not) functionally equivalent.
12-22 Client / Server Architecture Client Server Specialization Client / server responsibilities
12-23 Client A client is generally agreed to be any system or process that can request and make use of data, services, or other systems provided by the server.
12-24 Server A server is generally agreed to be any system or process that provides data, services, or access to other systems for clients, most often for multiple clients simultaneously (as a shared resource).
12-25 IT Infrastructure Considerations Reach Range
12-27 Choosing Among Options Business goals Managerial / technological issue Centralized computing Distributed computing Blending centralized and distributed computing
12-28 End-User Computing Architecture Issues Key issue: to provide architecture support for a division of responsibilities agreed on by IS and user groups
12-29 Reengineering Legacy Systems Reverse engineering Upsizing BPR
12-30 Further Issues in IT Planning Guidelines for IT planning Strategic planning Requirements analysis Resource allocation Selecting methodologies
12-31 Managerial Issues Importance Organizing for planning Fitting the IT architecture to the organization IT architecture planning IT policy Ethical and legal issues
12-32 Copyright 1999 John Wiley & Sons, Incorporated. All rights reserved. Reproduction or translation of this work beyond that permitted in Section 117 of the 1976 United States Copyright Act without the express written permission of the copyright owner in unlawful. Request for further information should be addressed to the Permissions Department, John Wiley & Son, Inc. Adopters of the textbook are granted permission to make back-up copies for his/her own use only, to make copies for distribution to student of the course the textbook is used in, and to modify this material to best suit their instructional needs. Under no circumstances can copies be made for resale. The publisher assumes no responsibility for errors, omissions, or damages, caused by the use of these programs or from the use of the information contained herein.