On Time Technology Implementation How to Achieve Implementation Success with Limited Time and Resources Bennet P. Lientz.
Detalles de publicación: San Diego, CA Academic Press 2000.Descripción: xxi, 292 p. 23 cmISBN:- 0124499759
- T58.64 .L55 2000
| Imagen de cubierta | Tipo de ítem | Biblioteca actual | Biblioteca de origen | Colección | Ubicación en estantería | Signatura topográfica | Materiales especificados | Info Vol | URL | Copia número | Estado | Notas | Fecha de vencimiento | Código de barras | Reserva de ítems | Prioridad de la cola de reserva de ejemplar | Reservas para cursos | |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Libro | Biblioteca de Mayagüez Colección General mb | T58.64 .L55 2000 (Navegar estantería(Abre debajo)) | Disponible | 50000002174091 |
Total de reservas: 0
Descripciones mejoradas de Syndetics:
On Time Technology Implementation presents technology implementation guidelines and lessons learned from over 30 years of successful, hands-on project experience.
Includes index.
Tabla de contenidos provista por Syndetics
- Preface(p. xvii)
- Part I Set the Direction
- Chapter 1 Introduction
- Introduction(p. 3)
- Business Direction of Information Technology(p. 4)
- Business Processes and Technology(p. 5)
- Technology and Software Tool Trends(p. 6)
- Challenges Facing Information Technology and Management(p. 7)
- Critical Success Factors in Systems and Technology(p. 7)
- Trends in Software Development(p. 8)
- Trends in Software Packages(p. 9)
- Trends in Knowledge Management(p. 9)
- Techniques of the Past(p. 10)
- Where Are the Benefits?(p. 11)
- A Real World Approach(p. 12)
- Organization of the Book(p. 13)
- Transition to a New Approach(p. 16)
- Examples(p. 16)
- Lessons Learned(p. 16)
- Summary(p. 17)
- What to Do Next(p. 18)
- Chapter 2 Develop the Business Process Plan and Strategy
- Introduction(p. 19)
- Observations on Business Processes(p. 20)
- Common Problems with Processes(p. 21)
- Steps in Developing the Process Plan and Strategy(p. 22)
- How to Build Your First Process Plan(p. 28)
- What Can Go Wrong?(p. 28)
- Reduced Schedule and Low-Cost Approach(p. 29)
- Examples(p. 30)
- Lessons Learned(p. 32)
- Summary(p. 33)
- What to Do Next(p. 34)
- Chapter 3 Defining the New Process, Benefits, and Requirements
- Introduction(p. 35)
- Step 1 Define the New Business Process(p. 36)
- Step 2 Determine Requirements for the New Process(p. 38)
- Step 3 Identify Costs and Benefits(p. 40)
- Step 4 Present the Results to Management(p. 43)
- Step 5 Determine the Technology Approach and Refine Costs and Benefits(p. 46)
- Step 6 Make the Buy or Build Decision(p. 48)
- What Can Go Wrong?(p. 56)
- Reduced Schedule and Cost Approach(p. 57)
- Examples(p. 57)
- Lessons Learned(p. 57)
- Summary(p. 58)
- What to Do Next(p. 58)
- Chapter 4 Assess Outsourcing
- Introduction(p. 59)
- The Outsourcer's View of the World(p. 60)
- What Can Be Outsourced?(p. 61)
- Steps in Outsourcing(p. 68)
- What Can Go Wrong?(p. 76)
- Reduced Schedule and Cost Approach(p. 77)
- Examples(p. 77)
- Lessons Learned(p. 78)
- Summary(p. 79)
- What to Do Next(p. 79)
- Part II Software Development
- Chapter 5 Define Requirements and Do Prototyping
- Introduction(p. 83)
- Step 1 Identify the Development Team and Establish the Development Plan(p. 85)
- Step 2 Develop Detailed Requirements for Development(p. 86)
- Step 3 Determine the Methods and Tools To Be Applied Throughout Development(p. 91)
- Step 4 Perform Data Analysis(p. 93)
- Step 5 Develop the First Prototype(p. 93)
- Step 6 Conduct a Pilot of the Prototype and the New Process(p. 94)
- Step 7 Refine the Prototype and Conduct More Pilots(p. 96)
- What Can Go Wrong?(p. 97)
- Reduced Schedule and Cost Approach(p. 97)
- Examples(p. 98)
- Lessons Learned(p. 99)
- Summary(p. 99)
- What to Do Next(p. 100)
- Chapter 6 Perform System Development and Integration
- Introduction(p. 101)
- Computer-Aided Software Engineering(p. 102)
- System Design(p. 103)
- Programming and Unit Testing(p. 105)
- Testing Preparation and Test Categories(p. 107)
- Integration of Programs(p. 110)
- Integration Testing(p. 111)
- System Testing(p. 111)
- What Can Go Wrong?(p. 111)
- Reduced Schedule and Cost Approach(p. 112)
- Examples(p. 112)
- Lessons Learned(p. 113)
- Summary(p. 114)
- What to Do Next(p. 114)
- Chapter 7 Conversion, Procedures, and Training
- Introduction(p. 115)
- Steps in Data Conversion(p. 118)
- Steps in Documentation and Procedures(p. 121)
- Steps in Training and Using Training Materials(p. 123)
- What Can Go Wrong?(p. 125)
- Reduced Schedule and Cost Approach(p. 126)
- Examples(p. 126)
- Lessons Learned(p. 127)
- Summary(p. 127)
- What to Do Next(p. 128)
- Chapter 8 Perform Maintenance, Enhancement, and Production Support
- Introduction(p. 129)
- Issues in Maintenance(p. 130)
- Issues in Enhancements(p. 132)
- Issues in Production Support(p. 133)
- Maintenance and Enhancement Steps(p. 135)
- Implement a Maintenance and Enhancement Policy(p. 139)
- Routine Production Support(p. 140)
- Production Crises(p. 141)
- Implementing a Production Strategy(p. 142)
- What Can Go Wrong?(p. 142)
- Reduced Schedule and Cost Approach(p. 143)
- Examples(p. 143)
- Lessons Learned(p. 143)
- Summary(p. 144)
- What to Do Next(p. 144)
- Part III Software Packages
- Chapter 9 Carry Out Evaluation and Selection
- Introduction(p. 147)
- Selecting a Winning Combination(p. 148)
- Seven Steps in Evaluation and Selection(p. 149)
- What Can Go Wrong?(p. 165)
- Reduced Schedule and Cost Approach(p. 165)
- Examples(p. 166)
- Lessons Learned(p. 167)
- Summary(p. 167)
- What to Do Next(p. 167)
- Chapter 10 Conduct Negotiations and Define the Implementation Plan
- Introduction(p. 169)
- Contract Negotiations for the Software package(p. 169)
- Contract Negotiations for Consultants(p. 172)
- Implementation Planning Steps(p. 175)
- What Can Go Wrong?(p. 181)
- Reduced Schedule and Cost Approach(p. 182)
- Examples(p. 182)
- Lessons Learned(p. 182)
- Summary(p. 183)
- What to Do Next(p. 183)
- Chapter 11 Implement the Package
- Introduction(p. 185)
- Managing Consultants(p. 187)
- The Package or the Process--Who Wins?(p. 188)
- Steps in Package Implementation(p. 189)
- Implementing New Software Package Releases(p. 197)
- Implementing ERP Software(p. 198)
- What Can Go Wrong?(p. 199)
- Reduced Schedule and Cost Approach(p. 199)
- Examples(p. 200)
- Lessons Learned(p. 200)
- Summary(p. 201)
- What to Do Next(p. 201)
- Part IV Knowledge Management
- Chapter 12 Identify Opportunities and Develop Your Strategy
- Introduction(p. 205)
- Issues in Knowledge Management(p. 208)
- Steps in Establishing Knowledge Management(p. 209)
- Example: The Lessons Learned Knowledge Base(p. 215)
- What Can Go Wrong?(p. 218)
- Reduced Schedule and Cost Approach(p. 219)
- Examples(p. 219)
- Lessons Learned(p. 220)
- Summary(p. 220)
- What to Do Next(p. 220)
- Chapter 13 Analyze Knowledge Management Technologies and Services
- Introduction(p. 223)
- Data Preparation(p. 223)
- Metadata(p. 224)
- On-Line Analytical Processing(p. 225)
- Models(p. 227)
- Artificial Intelligence(p. 228)
- Data Mining(p. 229)
- Data Visualization(p. 230)
- Combining Methods(p. 231)
- Example: Enterprise Resource Planning(p. 232)
- Consultants in Knowledge Management(p. 232)
- Evaluation of Products(p. 234)
- What Can Go Wrong?(p. 235)
- Reduced Schedule and Cost Approach(p. 235)
- Examples(p. 235)
- Lessons Learned(p. 236)
- Summary(p. 236)
- What to Do Next(p. 236)
- Chapter 14 Implement Knowledge Management
- Introduction(p. 239)
- Steps in Implementing Knowledge Management(p. 240)
- Establish the Lessons Learned Knowledge Base(p. 251)
- Management and Support of Knowledge Management(p. 252)
- What Can Go Wrong?(p. 254)
- Reduced Schedule and Cost Approach(p. 255)
- Examples(p. 255)
- Lessons Learned(p. 256)
- Summary(p. 256)
- What to Do Next(p. 256)
- Part V Electronic Commerce and Implementation Issues
- Chapter 15 Implementing Electronic Commerce
- Introduction(p. 259)
- Steps in Implementing E-Commerce(p. 260)
- What Can Go Wrong?(p. 270)
- Reduced Schedule and Cost Approach(p. 271)
- Examples(p. 271)
- Lessons Learned(p. 272)
- Summary(p. 273)
- What to Do Next(p. 273)
- Chapter 16 Overcome Implementation Issues
- Introduction(p. 275)
- Lack of Top Management Commitment(p. 275)
- Failure to Gain User Commitment(p. 276)
- Misunderstanding Requirements(p. 277)
- Lack of User Involvement(p. 278)
- Failure to Manage End-User Expectations(p. 278)
- Changing Scope, Objectives, and Requirements(p. 279)
- Lack of Required Knowledge and Skills in the Team(p. 280)
- New Technology(p. 280)
- Insufficient or Inappropriate Staffing(p. 281)
- Conflicts among User Departments(p. 282)
- Management Directs the Implementation(p. 282)
- A System Is Implemented, but There Is No Benefit(p. 283)
- Many Problems Build Up during Implementation(p. 284)
- Wrong Technology Solution Chosen for Implementation(p. 284)
- New Process and System Are Operational, but Dysfunctional with the Organization(p. 285)
- Picking Up the Pieces When the Implementation Fails(p. 286)
- Summary(p. 287)
- Index(p. 289)