The year 2000 software crisis : the continuing challenge


    • Hayes, Ian S.
    • Ulrich, William M.


The year 2000 software crisis : the continuing challenge

Ian S. Hayes and William M. Ulrich

(Yourdon Press computing series)

Prentice Hall PTR, c1998

大学図書館所蔵 件 / 2



Includes bibliographical references and index



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."


1. Year 2000 Progress Update. Year 2000 Update. Studies Paint Disconcerting Picture. The Real Story. Where Is the Sense of Urgency? Coming to Grips with Reality: Look at the Details. Media Update. The Year 2000 Myth? Silver Bullets Abound. Extremists Hurt the Cause. Business Problem Requires Business Solution. Industry by Industry Status. Banking. Securities Firms. Manufacturing. Retail. Transportation. Telecommunications. Utilities and Energy. Health Care, Insurance, and Pharmaceutical. Service Industries. Small to Mid-Size Companies. Government Update. U.S. Federal Government. U.S. Department of Defense (DOD). U.S. State Governments. U.S. Local Governments. Schools and Universities. International Update. Canada. Europe. Pacific Rim/Japan. Other Regions of the World. Worldwide Economic Impacts. 2. Strategy Update: Shift to Risk Mitigation. It's Late in the Game, Now What? Achieving Full Scale Deployment. The Declining Options Picture. Running Out of Time: Alternative Strategies. Launching Parallel Activities. Year 2000 Business Risk Assessment. Begin Fixing Five Most Critical Systems Now! Solidify Systems Inventory. Identify Data Interchange Points. Identify and Document External Entities. Document Business Functions. Relate Systems to Business Functions. Relate External Data Interfaces to Business Functions. Relate External Entities to Business Functions. Identify Event Horizons. Identify Revenue- or Customer-Related Risks. Identify Legal and/or Regulatory Risk. Prioritize Remediation and Testing Projects. Prioritize Business End-User-Driven Projects. Evolving Application Package Options. Vendor Has Delivered Compliant System. Vendor Fixed the System, But It Is Still Not Compliant. Vendor Is Fixing System, But Delivery Times Misses the Compliance Deadline. Vendor Refuses to Provide Compliance Status. Vendor Is Not Going to Fix the System. Strategies for the Far Behind. Targeting to Reduce Risk. "Safe" Corner Cutting. Unacceptable Corner Cutting. Launch Top Five Priority Remediation Projects. Beating the Clock in 1998 and 1999. 3. Legal Issues and Protections. Why You Should Care About This Legal Stuff. Minimizing Costs and Exposure. Contract Issues. Disclosure Obligations. Company Statements. Tax Law Issues. Internal Risk Management. Vendor Considerations. Certification Letters. Supply Chain/Partner Issues. The Paper Trail. Insurance. Government Aspects. Regulatory Agencies. Congress. State Government. Other Legal Aspects. Staffing. Offshore Factories. Copyright. 4. Non-IT Issues and Answers. Defining Non-IT Year 2000 Requirements. Business Partner Impacts. Supply Chain Challenge. Embedded and Other Non-IT Technologies. Non-IT Problems: Consequences and Timing. Industry-Specific Non-IT Challenges. Telecommunications. Energy and Power. Health Care. Manufacturing. Wholesale, Retail, and Service Industries. Transportation Sector. Financial. Government and Defense. Supplier, Business Partner Challenges. Supplier Categories. Supply Chain and the Domino Principal. Supplier Strategies: Methodological Approach. Documenting Multitiered Supply Chains. Supplier Responses. Supplier Contingency Options: Hedging Against Failure. Year 2000 Embedded Technology Challenge. Embedded Systems Challenge. Year 2000 Embedded Systems Impacts. Embedded Systems: Types and Categories. Embedded Systems Project Strategies. Embedded Systems: The Bottom Line. 5. Getting Help: Factories, Outsourcing, and Services. Third-Party ServicesYLessons Learned to Date. The Roots of the Dilemma. Identifying the Most Common Mistakes. Ground Rules for Successful Vendor Relationships. Selecting the Right Strategy. Strategy Selection Parameters. Using the Parameters to Select a Strategy. Selecting the Right Partner. Enabling Success. Enabling Factories. The Basic Factory Process. Before Using a Factory. The Factory Package. The Factory QA Process. Internal Factories. Enabling Consultants. Offshore Resources. Market Update. 6. Standards, Tools, and Techniques Update. Standards Update. Date Format Standards. Certification Programs. External Data Interchange. Year 2000 Firewall Strategies. Upgrade Unit Packaging Strategies. Remediation Procedures Update. High-Volume Productivity Targets. Field Expansion Update. Windowing Update. Expansion Using Bridges. Useful Notions and Worst Practices. An Array of Implementation Choices. "Do It Yourself" (DIY) Update. Optimizing the DIY Approach. Optimizing the Manual Fix Approach. Optimizing the Tool-Assisted Approach. Optimizing the Internal Factory Approach. Rules Of Engagement-Start Now. Year 2000 Tool Utilization Update. Automated Remediation Tools. Date Routines-Revisited. Bridging Routines. Testing Update. PC and Distributed Systems Tools. Risk Simulation Tools. Tracking Risks and Progress: Repository Utilization. Establishing Year 2000 Tracking Repository. Information Requirements. Enterprisewide Metamodel. Physical Repository Requirements. Information Capture and Loading Requirements. Inquiry and Reporting Requirements. 7. Year 2000 Testing Basics. Year 2000 Testing Differences. Scope of Year 2000 Testing. Focus of Year 2000 Testing. Infrastructure for Year 2000 Testing. What Needs to Be Tested. Compliance Requirement for Business Software. End-User Systems. Compliance Requirement for Embedded Technology. Types and Levels of Testing. Types of Tests. Levels of Tests. How Much Testing is Enough? "Failsafe" Testing. Typical Application Testing. Risk-Based Targeting. Elements of Risk-Based Analysis. Components Affected by Risk-Based Testing Strategies. Applying Risk-Based Testing Strategies. Applying Testing. 8. Implementing a Year 2000 Test Program. Managing the Enterprise-Level Testing Effort. The Testing Function of the Project Office. Roles and Responsibilities. Enterprise-Level Test Infrastructures. Assessing Enterprise Test Infrastructures. Determining Enterprise Infrastructure Improvements. Implementing Enterprise Infrastructure Improvements. Enterprise-Level Master Test Plan. High-Level Summary. Testing Strategy. Application Consolidation. Infrastructure Requirements. Test Projects List. Master Project Time Line. Managing Application-Level Testing Efforts. Roles and Responsibilities. Application Test Assessment Activities. Determining Application Infrastructure Improvements. Create an Application Test Plan. Test Data Creation. Test Script Creation. Test Execution. Results Validation. Acceptance and Sign-Off. Creating Application Test Plans. High-Level Summary. Testing Strategy. Test Environment. Detailed Test Descriptions. Application Project Time Line. Creating an Application Test Plan for Packaged Software. Factors Affecting Software Package Testing. Approaches to Testing Packaged Software. Developing a Test Plan for Packaged Software. Creating an Application Test Plan for Factory Remediation. Factors Affecting Testing of Factory-Remediated Software. Approaches to Testing Factory-Remediated Software. Developing a Test Plan for Factory-Remediated Software. 9. Contingency Planning: When Time Runs Out. What Is Contingency Planning. Why Plan for Contingencies. Technical versus Business-Driven Contingency Plans. Internally versus Externally Driven Requirements. Contingency Planning Participants. Identifying Contingency Requirements. Hardware and Infrastructure-Driven Requirements. Software-Driven Requirements. Development/Replacement Projects. Business-Driven Contingency Requirements. Building a Contingency Plan. Planning Overview. Business Model Redesign Options. Business Unit Shutdown Options. Business Function Consolidation Options. Triage: The De Facto Contingency Plan. Contingency Planning by Industry. Financial Institutions. Insurance Companies. Health Care Providers. Manufacturing and Retail Industries. Service Industries. Utilities and Telecommunications. Government Strategies. Small Company Contingency Planning. Contingency Plan Invocation. Time Critically Defines Success. Replacement Project Invocation. Invocation Based on Package-Provider Problems. Internal Failure Identification and Invocation. External Problem Identification and Invocation. Pre-2000 and Post-2000 Contingency Invocation. Who Makes Contingency Decisions? Shift toward Contingency Management. Contingency Management Is Continuous. Contingency Options at an Industry Level. Contingency Options at a National Level. Personal Contingency Planning. 10. Managing the Transition: Surviving the Inevitable. Defining the "Transition Window." Problems to Date. Predictions: 1998. Predictions: 1999. January 1, 2000. Cleaning Up the Mess: 2001-2005. Insurance Claims and Legal Action. Looking Forward: Industry by Industry. Financial Industry. Health Care. Manufacturing. Utilities and Telecommunications. Transportation. International Implications. Investment and Economic Impacts. Investment Impacts. Economic Impacts. Building a Crisis Management Team. Year 2000 Crisis Management. Crisis Management Requirements. Internal Planning Considerations. External Impact Considerations. The Crisis Management Plan. Crisis Call-In Center. Contingency Planning and Triage Center. Shifting Business Strategies in Crisis Mode. Cleanup Management Window. Year 2000 Will Change IT Landscape. Institutionalize the Project Office. IT Must Move On. IT Outsourcing: Be Careful. Think Globally-Act Locally. Authors' Note. Vendor Lists. Index.

「Nielsen BookData」 より

関連文献: 1件中  1-1を表示