Atnaujinkite slapukų nuostatas

Year 2000 Software Crisis: The Continuing Challenge [Minkštas viršelis]

,
  • Formatas: Paperback / softback, 480 pages, aukštis x plotis x storis: 237x180x18 mm, weight: 687 g
  • Išleidimo metai: 26-May-1998
  • Leidėjas: Prentice Hall
  • ISBN-10: 0139601546
  • ISBN-13: 9780139601545
Kitos knygos pagal šią temą:
Year 2000 Software Crisis: The Continuing ChallengeDidesnis paveikslėlis
  • Formatas: Paperback / softback, 480 pages, aukštis x plotis x storis: 237x180x18 mm, weight: 687 g
  • Išleidimo metai: 26-May-1998
  • Leidėjas: Prentice Hall
  • ISBN-10: 0139601546
  • ISBN-13: 9780139601545
Kitos knygos pagal šią temą:
Pastovi nuoroda: https://www.kriso.lt/db/9780139601545.html
Raktažodžiai:
It's already 1998 -- and the Year 2000 crisis is proving to be even worse than expected. From now on, every Y2K move you make had better be right. That's why you need The Year 2000 Software Crisis: The Continuing Challenge. In this all-new book, the authors of the world's #1 Y2K guide assess all the newest solutions, and deliver more in-depth Y2K expertise than ever before. Leading Y2K experts Ian Hayes and William Ulrich evaluate your latest options for sourcing (and outsourcing) Y2K work; new techniques and how they're working in the field; how to test Y2K compliance in an increasingly constrained environment; and much more. Learn how to prepare contingency plans and make urgent triage decisions; understand your legal liabilities; and much more. Whatever your role -- IT management, senior business executive or software engineer -- you can't afford to be without this up-to-the-minute Y2K "report from the field."

Daugiau informacijos

It's already 1998 -- and the Year 2000 crisis is proving to be even worse than expected. From now on, every Y2K move you make had better be right. That's why you need The Year 2000 Software Crisis: The Continuing Challenge. In this all-new book, the authors of the world's #1 Y2K guide assess all the newest solutions, and deliver more in-depth Y2K expertise than ever before. Leading Y2K experts Ian Hayes and William Ulrich evaluate your latest options for sourcing (and outsourcing) Y2K work; new techniques and how they're working in the field; how to test Y2K compliance in an increasingly constrained environment; and much more. Learn how to prepare contingency plans and make urgent triage decisions; understand your legal liabilities; and much more. Whatever your role -- IT management, senior business executive or software engineer -- you can't afford to be without this up-to-the-minute Y2K "report from the field."
Preface xxi(2)
Audience for this Book xxiii(1)
Summary of Contents xxiii
Chapter 1 Year 2000 Progress Update
1(42)
1.1 Year 2000 Update
2(7)
1.1.1 Studies Paint Disconcerting Picture
2(3)
1.1.2 The Real Story
5(2)
1.1.3 Where Is the Sense of Urgency?
7(1)
1.1.4 Coming to Grips with Reality: Look at the Details
8(1)
1.2 Media Update
9(3)
1.2.1 The Year 2000 Myth?
9(1)
1.2.2 Silver Bullets Abound
10(1)
1.2.3 Extremists Hurt the Cause
11(1)
1.3 Business Problem Requires Business Solution
12(1)
1.4 Industry by Industry Status
13(16)
1.4.1 Banking
14(2)
1.4.2 Securities Firms
16(1)
1.4.3 Manufacturing
17(2)
1.4.4 Retail
19(1)
1.4.5 Transportation
20(1)
1.4.6 Telecommunications
21(1)
1.4.7 Utilities and Energy
22(2)
1.4.8 Health Care, Insurance, and Pharmaceutical
24(2)
1.4.9 Service Industries
26(1)
1.4.10 Small to Mid-Size Companies
27(2)
1.5 Government Update
29(6)
1.5.1 U.S. Federal Government
29(3)
1.5.2 U.S. Department of Defense (DOD)
32(1)
1.5.3 U.S. State Governments
33(1)
1.5.4 U.S. Local Governments
34(1)
1.5.5 Schools and Universities
34(1)
1.6 International Update
35(3)
1.6.1 Canada
35(1)
1.6.2 Europe
36(1)
1.6.3 Pacific Rim/Japan
37(1)
1.6.4 Other Regions of the World
38(1)
1.7 Worldwide Economic Impacts
38(5)
Chapter 2 Strategy Update: Shift to Risk Mitigation
43(46)
2.1 It's Late in the Game, Now What?
44(6)
2.1.1 Achieving Full Scale Deployment
44(2)
2.1.2 The Declining Options Picture
46(2)
2.1.3 Running Out of Time: Alternative Strategies
48(1)
2.1.4 Launching Parallel Activities
49(1)
2.2 Year 2000 Business Risk Assessment
50(24)
2.2.1 Begin Fixing Five Most Critical Systems Now!
51(1)
2.2.2 Solidify Systems Inventory
52(1)
2.2.3 Identify Data Interchange Points
52(2)
2.2.4 Identify and Document External Entities
54(2)
2.2.5 Document Business Functions
56(1)
2.2.6 Relate Systems to Business Functions
57(2)
2.2.7 Relate External Data Interfaces to Business Functions
59(2)
2.2.8 Relate External Entities to Business Functions
61(2)
2.2.9 Identify Event Horizons
63(2)
2.2.10 Identify Revenue-or Customer-Related Risks
65(2)
2.2.11 Identify Legal and/or Regulatory Risk
67(2)
2.2.12 Prioritize Remediation and Testing Projects
69(2)
2.2.13 Prioritize Business End-User-Driven Projects
71(3)
2.3 Evolving Application Package Options
74(7)
2.3.1 Vendor Has Delivered Compliant System
74(2)
2.3.2 Vendor Fixed the System, But It Is Still Not Compliant
76(2)
2.3.3 Vendor Is Fixing System, But Delivery Times Misses the Compliance Deadline
78(1)
2.3.4 Vendor Refuses to Provide Compliance Status
79(1)
2.3.5 Vendor Is Not Going to Fix the System
80(1)
2.4 Strategies for the Far Behind
81(7)
2.4.1 Targeting to Reduce Risk
82(1)
2.4.2 "Safe" Corner Cutting
82(3)
2.4.3 Unacceptable Corner Cutting
85(2)
2.4.4 Launch Top Five Priority Remediation Projects
87(1)
2.5 Beating the Clock in 1998 and 1999
88(1)
Chapter 3 Legal Issues and Protections
89(34)
3.1 Why You Should Care About This Legal Stuff
91(2)
3.2 Minimizing Costs and Exposure
93(12)
3.2.1 Contract Issues
93(4)
3.2.2 Disclosure Obligations
97(4)
3.2.3 Company Statements
101(1)
3.2.4 Tax Law Issues
102(2)
3.2.5 Internal Risk Management
104(1)
3.3 Vendor Considerations
105(4)
3.3.1 Certification Letters
106(2)
3.3.2 Supply Chain/Partner Issues
108(1)
3.4 The Paper Trail
109(3)
3.5 Insurance
112(2)
3.6 Government Aspects
114(4)
3.6.1 Regulatory Agencies
114(2)
3.6.2 Congress
116(1)
3.6.3 State Government
117(1)
3.7 Other Legal Aspects
118(5)
3.7.1 Staffing
118(1)
3.7.2 Offshore Factories
119(1)
3.7.3 Copyright
119(4)
Chapter 4 Non-IT Issues and Answers
123(54)
4.1 Defining Non-It Year 2000 Requirements
124(4)
4.1.1 Business Partner Impacts
124(1)
4.1.2 Supply Chain Challenge
125(1)
4.1.3 Embedded and Other Non-It Technologies
125(2)
4.1.4 Non-It Problems: Consequences and Timing
127(1)
4.2 Industry-Specific Non-IT Challenges
128(7)
4.2.1 Telecommunications
129(1)
4.2.2 Energy and Power
129(1)
4.2.3 Health Care
130(1)
4.2.4 Manufacturing
131(1)
4.2.5 Wholesale, Retail, and Service Industries
132(1)
4.2.6 Transportation Sector
133(1)
4.2.7 Financial
134(1)
4.2.8 Government and Defense
135(1)
4.3 Supplier, Business Partner Challenges
135(15)
4.3.1 Supplier Categories
136(1)
4.3.2 Supply Chain and the Domino Principal
137(2)
4.3.3 Supplier Strategies: Methodological Approach
139(7)
4.3.4 Documenting Multitiered Supply Chains
146(2)
4.3.5 Supplier Responses
148(1)
4.3.6 Supplier Contingency Options: Hedging Against Failure
149(1)
4.4 Year 2000 Embedded Technology Challenge
150(27)
4.4.1 Embedded Systems Challenge
151(1)
4.4.2 Year 2000 Embedded Systems Impacts
152(2)
4.4.3 Embedded Systems: Types and Categories
154(14)
4.4.4 Embedded Systems Project Strategies
168(6)
4.4.5 Embedded Systems: The Bottom Line
174(3)
Chapter 5 Getting Help: Factories, Outsourcing, and Services
177(40)
5.1 Third-Party Services-Lessons Learned to Date
180(4)
5.1.1 The Roots of the Dilemma
181(1)
5.1.2 Identifying the Most Common Mistakes
182(2)
5.1.3 Ground Rules for Successful Vendor Relationships
184(1)
5.2 Selecting the Right Strategy
184(12)
5.2.1 Strategy Selection Parameters
185(3)
5.2.2 Using the Parameters to Select a Strategy
188(6)
5.2.3 Selecting the Right Partner
194(2)
5.3 Enabling Success
196(5)
5.4 Enabling Factories
201(8)
5.4.1 The Basic Factory Process
202(3)
5.4.2 Before Using a Factory
205(1)
5.4.3 The Factory Package
205(1)
5.4.4 The Factory QA Process
206(2)
5.4.5 Internal Factories
208(1)
5.5 Enabling Consultants
209(2)
5.6 Offshore Resources
211(2)
5.7 Market Update
213(4)
Chapter 6 Standards, Tools, and Techniques Update
217(30)
6.1 Standards Update
217(5)
6.1.1 Date Format Standards
218(1)
6.1.2 Certification Programs
218(2)
6.1.3 External Data Interchange
220(1)
6.1.4 Year 2000 Firewall Strategies
221(1)
6.2 Upgrade Unit Packaging Strategies
222(1)
6.3 Remediation Procedures Update
223(6)
6.3.1 High-Volume Productivity Targets
223(2)
6.3.2 Field Expansion Update
225(1)
6.3.3 Windowing Update
226(1)
6.3.4 Expansion Using Bridges
227(1)
6.3.5 Useful Notions and Worst Practices
227(2)
6.4 An Array of Implementation Choices
229(2)
6.4.1 "Do It Yourself" (DIY) Update
230(1)
6.5 Optimizing the DIY Approach
231(4)
6.5.1 Optimizing the Manual Fix Approach
231(1)
6.5.2 Optimizing the Tool-Assisted Approach
232(1)
6.5.3 Optimizing the Internal Factory Approach
233(2)
6.6 Rules Of Engagement-Start Now
235(1)
6.7 Year 2000 Tool Utilization Update
235(4)
6.7.1 Automated Remediation Tools
236(1)
6.7.2 Date Routines-Revisited
237(1)
6.7.3 Bridging Routines
237(1)
6.7.4 Testing Update
238(1)
6.7.5 PC and Distributed Systems Tools
238(1)
6.7.6 Risk Simulation Tools
238(1)
6.8 Tracking Risks and Progress: Repository Utilization
239(8)
6.8.1 Establishing Year 2000 Tracking Repository
239(2)
6.8.2 Information Requirements
241(1)
6.8.3 Enterprisewide Metamodel
242(1)
6.8.4 Physical Repository Requirements
243(1)
6.8.5 Information Capture and Loading Requirements
244(1)
6.8.6 Inquiry and Reporting Requirements
245(2)
Chapter 7 Year 2000 Testing Basics
247(42)
7.1 Year 2000 Testing Differences
250(8)
7.1.1 Scope of Year 2000 Testing
250(3)
7.1.2 Focus of Year 2000 Testing
253(2)
7.1.3 Infrastructure for Year 2000 Testing
255(3)
7.2 What Needs to Be Tested
258(8)
7.2.1 Compliance Requirement for Business Software
258(5)
7.2.2 End-User Systems
263(2)
7.2.3 Compliance Requirement for Embedded Technology
265(1)
7.3 Types and Levels of Testing
266(7)
7.3.1 Types of Tests
266(3)
7.3.2 Levels of Tests
269(4)
7.4 How Much Testing Is Enough?
273(3)
7.4.1 "Failsafe" Testing
274(1)
7.4.2 Typical Application Testing
275(1)
7.5 Risk-Based Targeting
276(9)
7.5.1 Elements of Risk-Based Analysis
277(2)
7.5.2 Components Affected by Risk-Based Testing Strategies
279(2)
7.5.3 Applying Risk-Based Testing Strategies
281(4)
7.6 Applying Testing
285(4)
Chapter 8 Implementing a Year 2000 Test Program
289(50)
8.1 Managing the Enterprise-Level Testing Effort
290(4)
8.1.1 The Testing Function of the Project Office
291(2)
8.1.2 Roles and Responsibilities
293(1)
8.2 Enterprise-Level Test Infrastructures
294(10)
8.2.1 Assessing Enterprise Test Infrastructures
295(2)
8.2.2 Determining Enterprise Infrastructure Improvements
297(6)
8.2.3 Implementing Enterprise Infrastructure Improvements
303(1)
8.3 Enterprise-Level Master Test Plan
304(6)
8.3.1 High-Level Summary
305(1)
8.3.2 Testing Strategy
306(2)
8.3.3 Application Consolidation
308(1)
8.3.4 Infrastructure Requirements
308(1)
8.3.5 Test Projects List
309(1)
8.3.6 Master Project Time Line
309(1)
8.4 Managing Application-Level Testing Efforts
310(13)
8.4.1 Roles and Responsibilities
312(1)
8.4.2 Application Test Assessment Activities
313(1)
8.4.3 Determining Application Infrastructure Improvements
314(2)
8.4.4 Create an Application Test Plan
316(1)
8.4.5 Test Data Creation
317(3)
8.4.6 Test Script Creation
320(1)
8.4.7 Test Execution
320(1)
8.4.8 Results Validation
321(2)
8.4.9 Acceptance and Sign-Off
323(1)
8.5 Creating Application Test Plans
323(7)
8.5.1 High-Level Summary
324(1)
8.5.2 Testing Strategy
324(3)
8.5.3 Test Environment
327(1)
8.5.4 Detailed Test Descriptions
328(1)
8.5.5 Application Project Time Line
329(1)
8.6 Creating an Application Test Plan for Packaged Software
330(4)
8.6.1 Factors Affecting Software Package Testing
331(1)
8.6.2 Approaches to Testing Packaged Software
332(1)
8.6.3 Developing a Test Plan for Packaged Software
333(1)
8.7 Creating an Application Test Plan for Factory Remediation
334(5)
8.7.1 Factors Affecting Testing of Factory-Remediated Software
334(1)
8.7.2 Approaches to Testing Factory-Remediated Software
335(2)
8.7.3 Developing a Test Plan for Factory-Remediated Software
337(2)
Chapter 9 Contingency Planning: When Time Runs Out
339(46)
9.1 What Is Contingency Planning
340(5)
9.1.1 Why Plan for Contingencies
340(2)
9.1.2 Technical versus Business-Driven Contingency Plans
342(1)
9.1.3 Internally versus Externally Driven Requirements
343(1)
9.1.4 Contingency Planning Participants
344(1)
9.2 Identifying Contingency Requirements
345(14)
9.2.1 Hardware and Infrastructure-Driven Requirements
345(4)
9.2.2 Software-Driven Requirements
349(5)
9.2.3 Development/Replacement Projects
354(1)
9.2.4 Business-Driven Contingency Requirements
355(4)
9.3 Building a Contingency Plan
359(11)
9.3.1 Planning Overview
360(5)
9.3.2 Business Model Redesign Options
365(1)
9.3.3 Business Unit Shutdown Options
366(1)
9.3.4 Business Function Consolidation Options
366(1)
9.3.5 Triage: The De Facto Contingency Plan
367(3)
9.4 Contingency Planning by Industry
370(9)
9.4.1 Financial Institutions
371(1)
9.4.2 Insurance Companies
372(1)
9.4.3 Health Care Providers
373(1)
9.4.4 Manufacturing and Retail Industries
374(1)
9.4.5 Service Industries
375(1)
9.4.6 Utilities and Telecommunications
376(1)
9.4.7 Government Strategies
377(1)
9.4.8 Small Company Contingency Planning
378(1)
9.5 Contingency Plan Invocation
379(3)
9.5.1 Time Criticality Defines Success
379(1)
9.5.2 Replacement Project Invocation
379(2)
9.5.3 Invocation Based on Package-Provider Problems
381(1)
9.5.4 Internal Failure Identification and Invocation
381(1)
9.5.5 External Problem Identification and Invocation
381(1)
9.5.6 Pre-2000 and Post-2000 Contingency Invocation
382(1)
9.5.7 Who Makes Contingency Decisions?
382(1)
9.6 Shift toward Contingency Management
382(1)
9.6.1 Contingency Management Is Continuous
383(1)
9.6.2 Contingency Options at an Industry Level
383(1)
9.6.3 Contingency Options at a National Level
383(1)
9.7 Personal Contingency Planning
383(2)
Chapter 10 Managing the Transition: Surviving the Inevitable
385(34)
10.1 Defining the "Transition Window"
386(10)
10.1.1 Problems to Date
387(2)
10.1.2 Predictions: 1998
389(1)
10.1.3 Predictions: 1999
390(1)
10.1.4 January 1, 2000
391(3)
10.1.5 Cleaning Up the Mess: 2001-2005
394(1)
10.1.6 Insurance Claims and Legal Action
395(1)
10.2 Looking Forward: Industry by Industry
396(3)
10.2.1 Financial Industry
396(1)
10.2.2 Health Care
397(1)
10.2.3 Manufacturing
397(1)
10.2.4 Utilities and Telecommunications
398(1)
10.2.5 Transportation
398(1)
10.2.6 International Implications
398(1)
10.3 Investment and Economic Impacts
399(2)
10.3.1 Investment Impacts
399(1)
10.3.2 Economic Impacts
400(1)
10.4 Building a Crisis Management Team
401(3)
10.5 Year 2000 Crisis Management
404(7)
10.5.1 Crisis Management Requirements
404(1)
10.5.2 Internal Planning Considerations
405(1)
10.5.3 External Impact Considerations
406(1)
10.5.4 The Crisis Management Plan
407(1)
10.5.5 Crisis Call-In Center
408(1)
10.5.6 Contingency Planning and Triage Center
409(1)
10.5.7 Shifting Business Strategies in Crisis Mode
410(1)
10.6 Cleanup Management Window
411(2)
10.7 Year 2000 Will Change IT Landscape
413(2)
10.7.1 Institutionalize the Project Office
413(1)
10.7.2 IT Must Move On
413(2)
10.7.3 IT Outsourcing: Be Careful
415(1)
10.8 Think Globally-Act Locally
415(4)
Authors' Note
416(3)
Vendor Lists 419(18)
Index 437
Ian Hayes is founder and principal of Clarity Consulting of Marblehead, MA. He specializes in strategic consulting on issues surrounding the management and support of corporate business systems.

William M. Ulrich is president of Tactical Strategy Group, Inc., a consulting firm that specializes in legacy architecture transition planning. A resident of Aptos, CA, he is co-founder and program chairman of the Year 2000: Blueprint for Success Conference.