The Binomial Bookstore

AFTER the Y2K FIREWORKS
BUSINESS AND TECHNOLOGY STRATEGIES
by Bhuvan Unhelkar

“After the Y2K Fireworks focuses on the business and technical aspects of surviving the year
2000 programming dilemma - from an author conversant with both business (particularly
financial) and computer professionals.

“More companies than not will fail to prevent the problems arising from this potential
programming disaster. This book addresses this part of the market - putting the problem in
perspective and examining all the various organizational and technical issues required to
rebuild quickly and efficiently.
===================================

“FEATURES OF AFTER THE Y2K FIREWORKS:
Provides a prognosis of how an organizational structure will look after the Y2K predicament
Identifies essential elements of rebuilding an enterprise following the Y2K problem
Discusses new processes for the creation of a new enterprise
Balances business and technical aspects of the Y2K problem
Focuses on preparing for a potential disaster
Reflects the innovative use of object-oriented methodologies and designs
Serves a broad range of industrial firms, including manufacturing, finance, and banking.”

===================================
“Outlined in this book is a detailed approach of how you can rebuild quickly and effectively
from the ashes of a Y2K disaster. This has been called resurrection throughout the text -
which includes an understanding of what has happened in terms of the date disaster, and
how it can be converted into a situation of strategic value. Thus the book focuses not on a
quick date fix, but on survival through resurrection. It starts by identifying the various ways
you
are hit, the way your organizational structure will look like and how the organization will
behave after the disaster. After arguing about the strategic advantages of undertaking a
resurrection process, this discussion defines and describes a detailed process discipline for
resurrection. The actual resurrection process, which comprises the three essential
dimensions of rebuilding, follows this. These essential dimensions are technology,
methodology, and sociology. Once the process of creating the new business processes is
understood, it can be applied to various types of organizations that may have been hit by the
Y2K problem. Included in this discussion are simplified examples of business processes
relating to banking loan applications and resurrecting a Y2K-hit payroll application.
Distribution, which will be an essential architectural element of redesigning organizations in
the year 2000, is discussed in the context of these redesigns. Due to the extreme
importance
of testing in the year 2000, especially because it has to go way beyond the traditional Y2K
tests and ensure that the new system satisfies the functionality of the existing system as
well
as the added functionality, a separate chapter is dedicated to the topic of test planning, test
designing, and execution of test cases.

“Finally, this discussion accepts the fact that we are moving towards a global village.
Phenomenal advances in communication and transportation have shrunk the world.
Businesses will have to come to terms with these phenomena and will have to revisit their
priorities in the new millennium. The sociological aspect of managing a software
development, as well as managing the personality of the business in this global village, will
be
of utmost importance to the senior (and enlightened) management of the organization. No
longer can the organization consider itself separated from the rest of the society, and no
longer can it be said to be genuinely responsible towards its shareholders, if it does not
consider the context in which it is operating. This context is understood and accepted by an
adwait company. Adwait is a word derived from the Sanskrit literature, and literally means
nondual. The boundaries between organizations in the next millennium will be fuzzy and
undefined. Businesses will depend more on their relationships with customers, as well as
with their suppliers, in order to survive and prosper. In essence, it will be difficult to look at the
business as a separate entity - it will be a part of the global business - in other words it will
be
adwait. Creation of an adwait reengineered organization is the final goal of this exercise.
The
hope is that such an organization will be flexible and process-oriented enough to sustain
even
a Year 3000 hit - for the way IT is going today, I am sure there are a large number of
"unknown" bugs that we are busily inserting in our codes and embedded chips today, that will
somehow come out to bite us 1000 years from now.”

==========================================

CONTENTS

1 THE FIREWORKS
After the Fireworks
Party of the Millennium
The Party Goers
The Dawn of 2000
The Firecrackers
Doomsayer's Day
Silent Explosions
Personal Situations
Public Situations
Business Systems
Justifying the Gun Powder
Why We Programmed with 2-Digits
Underestimating Software Life Expectancy
Types of Firecrackers
The 2-Digit Cracker
The HIGH-LOW-Value Firecracker
Amateur Date Conversion
Y2K is a Leap Year
"Windowing" the Date in the Past
Compression Beyond Endurance
Other Firecrackers
Ripple Effect on Customers/Suppliers
Psychological Effect of 2000
The Centralized Architecture
The Euro Currency Concern in 1999
Year 2038: The Unix Concern
The Fallout
Variety of Fallout
Large Organizations
Small Business
Government
Family
Let the Hangover Begin
Possible Global Recession
Changing Nature of Business in Y2K
Social Hangover in Y2K
Family Hangover in Y2K
So What?
Key Points
Notes
References

2 THE SCHIZOPHRENIC ENTERPRISE
Organization in a Y2K Society
Influence of Technology on the Business
Business: Not an Independent Entity
Influence of Business on the Society
Rate of the Rate of Change
The Unit that Exploded
Ignorant
Callous
Dependent
Rigid
Hierarchical
Coarse
Bulky
Unhedged
Level of Y2K Preparedness
Red: Aware of the Y2K Problem
Orange: Investigating Y2K Solutions
Yellow: Implementing Y2K Solutions
Green: Y2K Work Completed
Blue: Helping Business Partners
Gold: Open Consulting in Y2K
Sequence and Timings in a Y2K Explosion
Sequence and Probable Timing of Events
Skewing Factor
Describing the Steps in Y2K Hits
Basically a Technical Problem
Influences Ability to Serve
Starts Losing Business
Influences Suppliers
Starts Losing Productivity
Dwindling Stocks
Employee Morale
Dealing with Trade Unions
Litigation
Intensity of a Y2K Explosion
Mild
Medium
Severe
Still Breathing?
Scattered Ashes
Data with No Information
Schizophrenic Data
Organizational Identity Crises
Balance Sheets that Won't Balance
Vain Attempts at Redefinition
What is Attempted?
Who Attempts the Redefinition?
Abortive Redefinition
Matchstick Alliances
The Schizophrenic Enterprise
Merry-Go-Round Orders
Multiple Corporate Personalities
Donut and Sausage Sizzle Culture
False Projects
Continuous Catch-Up Game
Investigation
Notes
Key Points
References

3 STRATEGIC ADVANTAGE OF Y2K RESURRECTION
Strategic Benefits from Y2K Resurrection
Over the Y2K Hump
It's not all Maintenance
Discussing the Benefits
Recognition of Information Technology as a Strategic Tool
IT in a Supporting Role
IT in a Strategic Role
The Business Engineering Advantage
Existence of Processes
Redundancy of Processes
Reengineering Relevant Processes
Forward Engineering Processes
Inventory of Applications
Identification of all Applications
Third Party Products
End-User Applications
Inventory of Databases
Databases - by Usage
Databases - by Types
Identifying Existing Data
Documenting Data Models
Documenting Stored Procedures
Moving away from Legacy
The Legacy Importance
The Legacy Weight
Redundant and Inflexible Code
Opportunity to Sunset Systems
Introduction of Object Technology
Reduced Resistance to Change
New Approaches
Acceptance of Tools
New Languages
Opportunity for Training
Hardware Availability
Foundations for a Robust Architecture
New Building Blocks
Architectural Experience
User Literacy and Participation
Creating Quality
Climbing up the CMM Model
Easier in Resurrection
Importance of Documentation Accepted
Measurements and Metrics
Insourcing Business Engineering Projects
Recognition of Success
Providing Consulting Services
Providing Methodology and Tools
Reengineering Project Management
Concentrates on Essential Tasks
Opportunity for Creative Solutions
Using Project Management Tools
Flatter Structure
Heightened Employee Awareness
Awareness of Problems
Buy-In: The Solution
Measuring the Strategic Benefits
Strategic Advantage Factor
Strategic Benefits Accrue in Time
Key Points
Notes
References

4 THE PROCESS DISCIPLINE FOR Y2K RESURRECTION
A Chat on Modeling
The Need for Modeling
Modeling as a Creative Cause
Advantages of a Model
Caveats and Limitations
Software Development Lifecycle Models
The Model We Need
A Look at White Clouds
A Process Model
A Hierarchical Viewpoint
A Reengineered Process-Based View
Reasoning for a Process Model for the Y2K Enterprise.
Formally Describing a Process
A Process Definition
A Simple Cooking Process
Picturing the Process
The Three Dimensions of a Process
Describing the Dimensions
The Orthogonal Process Relationship
"What" in a Process
"How" of a Process
"Who" in a Process
Process Elements
Notations for Process Elements
The "Actor" Element in a Process
The "Activity" Element in a Process
The "Task" Element in a Process
The "Deliverable" Element in a Process
Semantics of the Notation
Threads of a Process
Defining a Process-Thread
Identifying a Process-Thread
Need for a Process-Thread
Broken Process-Threads
Iterations in a Development Process
Need for Iterations
Initial
Major
Final
Measurement of Processes
Why Measure Processes?
Arriving at a Single Unit
Process Scope
Defining the Scope
Influencing the Process-Threads
Process Mappings
A Software Process
A Business Process
Software-Business Relationship
Mapping with the Process Discipline
Key Points
Notes
References

5 THE Y2K RESURRECTION PROCESS
The Y2K Resurrection Philosophy
Core Concept Behind Resurrection
The Driving Dimension of Resurrection
Applicability of the Resurrection Process
Steps in Y2K Resurrection
Sequence of Events in Resurrection
Probable Timing of Events in Resurrection
5.3 Advantage of Preparedness in Y2K Resurrection
Green
Yellow
Orange
Red
Describing the Y2K Resurrection Process
The Resurrection Process
Preliminary and Core Activities in Resurrection
Budgeting
Ensure Ability to Spend
Allocate Budgets
Assigning Budgetary Responsibility
Nomination of the "Resurrection Champion”
Identify Potential Candidates
Publicizing the Appointment
Decide Reporting Guidelines
Scoping the Resurrection
Small Scope
Medium Scope
Large Scope
Highlighting Strategic Advantages
Shortlist Strategic Advantages
Highlight Advantages to the Senior Managers
Highlight Advantages to the Technical Team
Regrouping the Peopleware
Setting up the Transition Atmosphere
Communicating the Resurrection
Identify Political Hotspots
Iron Out Issues
Balancing the Dimensions of the Y2K Resurrection Process
Following the White Cloud Role Model
Balancing Technology with Sociology
Iterating the Y2K Resurrection
Initial
Major
Final
An Iterative Y2K Project Plan
The Project Plan
Iterative Project Management Tools
Refining the Plan at the End of Each Iteration
Launching the Core Processes
Key Points
Notes
References

6 TECHNOLOGY IN YEAR 2000
Essence of Technological Challenge in Resurrection
"What" of Resurrection
Old was Gold
Sample from a Firecracker
Data
Data Model
Logic
Languages in Resurrection
COBOL
C++
SmallTalk
Java
Databases in Resurrection
Hierarchical
Relational
Object-Oriented
Object Relational
Thoughts on Database Conversion
Data Mining and Resurrection
Data Explosion after Y2K Resurrection
Understanding Data Mining
Relevance of Data Mining in Y2K
Middleware in Resurrection
CORBA
DCOM
Enterprise Business Solutions and Resurrection
Enterprise Resource Planning (ERP)
SAP(tm)
PeopleSoft(tm)
Oracle Applications(tm)
Networks and Communications in Resurrection
Communication Protocols
Access Mechanisms
Realtime Data
Hardware and Resurrection
Key Points
Notes
References

7 A TECHNOLOGICAL PROCESS
Describing a Technological Process
The Process Figure
A High-Level Process Flow
Technological Actors
Actor: Programmer
Actor: Database Manager
Actor: Network Administrator
Technological Deliverables
Application
Database
Delivery Mechanism
Infrastructure
Technological Activities and Tasks - With Iterations
TA01: Dissection
TA01-1: Scope the Dissection
TT01-2: Dissect Data
TT01-3: Dissect Logic
TT01-4: Dissect Presentation
TT01-5: Shortlist Salvageable Options
TA02: Create Technical Environment
TT02-1: Setup Language
TT02-2: Deal with the Operating System
TT02-3: Install Database
TT02-4: Install Network
T702-5: Relate to Hardware
TA03: Rewrite-Modify-Customize
TT03-1: Environment Familiarization
TT03-2: Estimate Effort
TT03-3: Review Date Errors
TT03-4: Prototype
TT03-5: Code
TT03-6: Unit Test Code
T'1703-7: Incident Solving
TA04: Software Integration
TT04-1: Bring the Software Together
TT04-2: Ensure Consistency with Database
TT04-3: Verify Against Requirements
TT04-4: Verify Performance
T'T04-5: Incident Solving
TT04-6: Regression Testing
TA05: Data Creation
TT05-1: Review Date Errors
TT05-2: Scope the Data Creation
TT05-3: Automate Data Conversion
TT05-4: Manual Data Entry
TT05-5: Verification of Data
TT05-6: Backup and History of Data
TA06: DataBase
TT06-1: Evaluate Database
TT06-2: Distribution in Database
TT06-3: Create Data Model
TT06-4: Create Stored Procedures
TT06-5: Administration of Database
TA07: Hardware
TT07-1: Evaluate Current Hardware
TT07-2: Upgrade to New Hardware
T'F07-3: Maintenance of Hardware
TT07-4: Security of Hardware
TA08: Network
TT08-1: Evaluate Current Network
TT08-2: Upgrade Network
TT08-3: Network Maintenance
TA09: Delivery
TT09-1: Evaluate Existing Delivery Mechanisms
TT09-2: Upgrade Delivery Mechanism
TT09-3: Ensure Data Delivery
TT09-4: Ensure Software Delivery
TA 10: Quality Assurance
TT10-1: Test Plan
TT10-2: Test Designs
TT10-3: Test Cases
TT10-4: Code Walkthrough
TT10-5: Documentation
TA11: Project Management
TT11 - 1: Manage Build Environment
TT11-2: Take Charge of Working Version
TT11-3: Manage Configurations and Versions
TT11-4: Organize Database and Network
TT11-5: Update Project Plan
Size of the Technological Process
Caveats
Key Points
Notes
References.

8 METHODOLOGY IN YEAR 2000
8.1 Essence of the Y2K Methodological Challenge
8.1.1 "How" of Resurrection
8.1.2 What Comprises Methodology
Justifying Methodologies in a Process
Need for Methodologies
Relating Methodologies to Project Size
The Road Map Approach
Ups and Downs of Methodologies
Using Object-Orientation in the Resurrection
Advantage through Objects
Small Semantic Gap
Seamlessness
Choosing Top Down vs. Bottom Up
Object-Oriented Methodologies
Bringing Object-Oriented Methods Together
Unified Modeling Language (UML)
Object-Oriented Process, Environment, and Notation (OPEN)
Requirements Modeling for Y2K Resurrection
Use Cases and Scenarios
Class Diagrams in 00 Designs
Dynamicity in 00 Designs
Reusability in Y2K Resurrection
Reuse as Old as Software
With and For Reuse
Granularity in 00 Reuse
Locating Classes for Reuse
Patterns in Y2K Resurrection
Patterns and Y2K
Describing Patterns
Structure of a Pattern
A Y2K Resurrection Pattern
Quality in Y2K Resurrection
Repeatable Process
Quality from 00
Metrics and Measurements in Y2K
Purpose of Metrics
Metrics in Y2K Resurrection Process
The Object-Oriented Metrics
Resurrection Process Metric
Documentation and Support in Y2K
Technical Documentation
User Guides
Online Help
Wizards
Auto Demos
CASE Tools for 00 Methodologies
Rational Rose(tm)
Object Analyst(tm)TM
MetaEdit(tm)
Visio(tm)
Key Points
Notes
References

9 DESCRIBING THE METHODOLOGICAL PROCESS
Describing the Methodological Process
The Process Figure
A High-Level Process Flow
Methodological Actors
Actor: Project Manager
Actor: Architect
Actor: Quality Assurance Manager
Actor: User
Methodological Deliverables
Software with Development Process
Business Scenarios
System Architecture
System Designs
Iterative Project Plan
Quality Assurance Plan
Methodological Activities and Tasks with Iterations
MA01: Alternative Evaluation
MT01-1: Background Thinking
MT01-2: Prioritizing High-Level Requirements
MT01-3: Technological Feedback
MT01-4: Budgetary Feedback
MT01-5: Selecting Alternative
MT01-6: Methodology Decision
MA02: Project Planning
MT02-1: Formalize Process Elements
MT02-2: Create Iteration Plan
MT02-3: Assign Resources to Tasks
MT02-4: Assign Checkpoints
MA03: Project Management
MT03-1: Promote Methodology
MT03-2: Review Technical Demos
MT03-3: Conduct User Demos
MT03-4: Track Activities and Tasks
MT03-5: Update Project Plan
MT03-6: Watch Out for Road Factors
MT03-7: Contain Scope
MT03-8: Manage User Representatives
MA04: Requirements Modeling
MT04-1: Formalize Salvageable Requirements
MT04-2: Identify Date Specific Requirements
MT04-3: Specify New Requirements
MT04-4: Prototype User Interfaces
MT04-5: Describe Business Objects
MA05: Architecture
MT05-1: Identify Architectural Elements
MT05-2: Slice Large and Complex Elements
MT05-3: Relate the Architectural Elements
MT05-4: Consider Distributed Architecture
MT05-5: Produce System Architecture
MA06: Solution Design
MT06-1: Produce Component Designs
MT06-2: Design DATE Component
MT06-3: Reuse Designs
MT06-4: Design Database Tables
MT06-5: Consider Database Distribution
MT06-6: Design User Interface
MA07: Quality Planning
MT07-1: Identify Quality Elements
MT07-2: Estimate Quality Resources
MT07-3: Create Quality Plan
MT07-4: Review Quality Plan
MA08: Standards
MT08-1: Identify Needs for Standards
MT08-2: Map to Existing Standards
MT08-3: Create Local Standards
MT08-4: Publicize Standards
MT08-5: Upgrade Standards
MT08-6: Review Activities Based on Standards.
MA09: Testing
MT09-1: Create a Test Plan
MT09-2: Identify a Test Approach
MT09-3: Create a Test Environment
MT09-4: Create Test Designs
MT09-5: Conduct Testing
MT09-6: Review Test Results
MA10: Metrics
MT10-1: Identify Measurement Needs
MT10-2: Locate Historical Data
MT10-3: Make "Ballpark" Estimates
MT10-4: Measure Designs
MT10-5: Measure Code
MT10-6: Measure Quality
MT10-7: Measure Processes
MA11: Quality Management
MT11-1: Manage Quality Resources
MT 11-2: Manage Documentation
MT 11-3: Update Quality Plan
Size of the Methodological Process
Caveats and Assumptions
Key Points
Notes
References

10 SOCIOLOGY IN YEAR 2000
Essence of Sociological Challenge in Resurrection
Nature of Technical Development
Relevance of Sociological Factors in Development
External Sociological Factors
Personal Software Process
Processes within PSP
Measuring Productivity
Leadership in Y2K
Communication
Flattening the Pyramid
Morale and Motivation
Staffing in Y2K
Best Fit Approach
Cost of Turnover
Gaining from Exit
Team Formation
Constantine Team Models
Closed
Open
Random
Synchronous
Team Model within 00
Team for Y2K Resurrection
Ethics in Y2K
Productive time
Telecommuting
Directions Organizations Take
Individual Objectives
Corporate Objectives
Usability in Y2K
User Centered Development
Principles of Usability
The Environment
E-Factor
Utilizing the Technology
Pots and Plants
Games in a Resurrection Project
Use It or Lose It
Cowboy Programming
Flour Mix
Meetingitis
Deadline
Key Points
Notes
References

11 A SOCIOLOGICAL PROCESS
Describing the Sociological Process
The Process Figure
A High-Level Process Flow
Sociological Actors
Actor: Director
Actor: Project Manager
Sociological Deliverables
Software with Aesthetics
The Resurrected Company
Sociological Activities and Tasks with Iterations
SA01: Staffing
ST01-1: Identify Staffing Need
ST01-2: Identify Sources
ST01-3: Evaluate Candidates
ST01-4: Negotiate Remuneration
ST01-5: Offer Written Letter
SA02: Team Formation
ST02-1: Understand Individual Objectives
ST02-2: Understand System Architecture
ST02-3: Assign Teams to Modules
ST02-4: Fine Tune Teams
SA03: Training
ST03-1: Identify Training Needs
ST03-2: Decide Training Types
ST03-3: Initiate Training Program
ST03-4: Obtain Feedback
ST03-5: Monitor Technology Trends
SA04: Environment (E) Factor
ST04-1: Monitor Environment
ST04-2: Initiate Survey
ST04-3: Introduce Controls
ST04-4: Manage Physical Layout
ST04-5: Beautification
SA05: Motivation
ST05-1: Shortlist Motivational Factors
ST05-2: Correlate with Company Objectives
ST05-3: Manage Remuneration
ST05-4: Undertake Teambuilding
ST05-5: Support Achievement
SA06: Process Refinement
ST06-1: Baseline Process
ST06-2: Organize Reviews
ST06-3: Set Priorities
ST06-4: Implement Process Change
ST06-5: Publicize Process Improvement
SA07: Usability
ST07- 1: Awareness of HCI Issues
ST07-2: Design User Centered Interfaces
ST07-3: Conduct Collaborative Usability Inspection (CUI)
ST07-4: Manage Usability Standards
SA08: Outsourcing
ST08-1: Identify Outsourcing Needs
ST08-2: Evaluate Outsourcing Partners
ST08-3: Outsource Projects
ST08-4: Manage and Review Projects
SA09: Advertising
ST09-1: Identify Areas for Advertisement
ST09-2: Advertise Resurrection Externally
ST09-3: Promote Resurrection Internally
ST09-4: Manage Advertising Contract
SA10: Corporate Relations
ST10-1: Manage Board Relationship
ST10-2: Nominate Y2K Experts on Board
ST10-3: Liaise with Business Partners
ST10-4: Liaise with Society
SA11: Litigation
ST11-1: Manage Documentary Evidence
ST11-2: Budget for Litigation
ST11-3: Claim on Insurance
ST11-4: Manage Settlement
SA12: Project Management
ST 12- 1: Track Activities and Tasks
ST12-2: Report to Board
ST12-3: Publish and Present
ST12-4: Manage HR Issues
ST12-5: Manage Games
ST12-6: Update Project Plan
SA13: Quality Assurance
ST13-1: Manage Internal/External Audits
ST13-2: Post Audit Review
ST13-3: Post Iteration Review
ST13-4: Independent Reporting
Measuring the Sociological Process
Caveats and Assumptions
Key Points
References

12 DISTRIBUTED ARCHITECTURE IN Y2K RESURRECTION
Distribution with Objects
Background of Distribution
Distributed Objects
Distributing Components
Advantages of Distribution
Caveats in Distribution
Role of Distribution in Y2K
Dissecting a Y2K Hit Using Distribution
Distributing DATE Components
Creating "Object Wrappers" Around Legacy Date Code
Distributing the Application
Further Distributing the Application
System Architecture in Y2K
Defining Architecture
Progress in Architecture
Architectural Approach
Logical vs. Physical Architecture
Architectural Issues in Y2K Resurrection
Relating the Architecture to the Requirements
Middleware in Distributed Architecture
Describing an Object Request Broker (ORB)
CORBA Advantages in Resurrection
DCOM and Its Use in Resurrection
Measuring Distribution
Key Points
Notes
References

13 PROCESSES FROM ASHES
Resurrecting from the Ashes
The Resurrection Repository
Process Repository
Product Repository
Payroll Process
Existing Process
Effect of Y2K Hit
The Resurrection Process
Payroll in the New Millennium
Bank Loan Process
Describing the Existing Loan System
Describing the Effect of Y2K Hit
Preliminary Activities
Initial Iteration
Major Iteration
Final Iteration
Bank Loan Process in the New Millennium
Key Points
Notes

14 TESTING STRATEGIES FOR Y2K PROCESSES
Testing in Y2K Resurrection
Testing Approaches for Y2K Resurrection
Black Box
White Box
Manual Testing
Automated Testing
Vertical Slicing
Horizontal Slicing
Equivalence Partitioning
Boundary Value
Testing Architecture for Y2K Resurrection
Unit Test
Component Test
System Test
Acceptance Test
Regression Test
Test Planning for Y2K Resurrection
A Good Test Plan
Analyzing Risks
Prioritizing Risks
Test Resources
Test Environment
Test Timeline
Test Cycles
Reusability in Testing
Test Design for Y2K Resurrection
Description of Test Designs
Sources for Test Designs
Format for Test Designs
Test Cases for Y2K Resurrection
Description of Test Cases
Designing the Test Cases
Format for Test Cases
Verifying Test Cases
Modifying the Test Cases
Test Execution in Y2K Resurrection
Getting Ready
Acceptance Criteria
Execute Test Suites
Record Incident Reports
Test Results in Y2K Resurrection
Software Incidents I
Recording Test Results
Analyzing Results
Reporting
Test Acceptance Criteria
Key Points
Notes
References

15 THE ADWAIT ENTERPRISE IN YEAR 2000
Understanding Adwait
The Traditional View of Business
Meaning of the Term Adwait
Adwait - After the Y2K Resurrection
Relationships with Business Partners in Y2K
Retaining Business Partners
Moving On
Relationship with Bureaucracy
The Martian Business
The Star Business
Growth of Martian Business
Key Points
Notes
References

APPENDIX A: SAMPLE Y2K ACCEPTANCE CRITERIA
Introduction
Standard Office Applications Reminders
Spreadsheets
Microsoft Excel for Windows (Office 97)
Microsoft Excel for Windows (Office 95)
Microsoft Excel Version 5
Databases
Microsoft SQL Server
Microsoft Access (Access 97)
Microsoft Access Version 2
Mail Packages
ccMail
Calendar
Microsoft Schedule .
Organizer Calendar
Organizer 2.x
Organizer I.x
Microsoft Project
Notes

APPENDIX B: WHITECLOUDS(TM)
Introduction
Target Environment
In Y2K Resurrection
Notes
References

APPENDIX C: MENTOR ASSISTANT TOOL (MAT)TM
Introduction
Y2K Resurrection Process in MAT
Entering the Process Elements
Tracking the Process Elements
Define the Dimensions
Define the Scope of Resurrection
Creating a Y2K Resurrection Project
Schedule the Project
Tracking Effort Against the Project Activities
Notes
References
Index

=====================================

ABOUT THE AUTHOR

“Bhuvan Unhelkar (MDBA, MSc, Ph.D., MACS) has over 17 years of professional
Information
Systems (IS) experience including consulting and senior roles in Product Development and
Quality Assurance. Currently, he is the Chief Operating Officer at CASE/digital Inc., a
Californian software company (with offices in India and Australia) involved in development,
consulting, and training in a wide area of software activities, including Year 2000,
object-oriented processes and methodologies, ERP solutions, and CAD/CAM development.

“Unhelkar's experience portfolio in software development includes initiating and
implementing methodological approaches to 00 development with a strong emphasis on
quality and reusability, as well as providing leadership and direction, staffing and budgeting,
internal and external training. For the development of a financial market application, he won
the Computerworld Object Developer's Awards (CODA '95) for "Best use of an
object-oriented approach across the organization." His ideas on the process of Y2K
resurrection derive from his experience in process-based software development, consulting
to various organizations and his own research and understanding.

“Unhelkar received his Doctorate from the University of Technology, Sydney. His thesis was
title "Effect of Granularity of 00 Design in Modeling an Enterprise and its Application to
Financial Risk Management." In addition to the discussion on object granularity in designs,
the thesis also discusses IT strategic planning, enterprise modeling and sociological issues
in IT project management, which form the basis of the sociological dimension of the Y2K
resurrection process. He has lectured in the subjects of "Object Oriented Information
Systems" at University of New South Wales, as well as at University of Technology, Sydney,
where he is also an Honorary Associate. He also has supervised many Master's projects at
the university.

“Unhelkar has participated in numerous conferences and training workshops in Australia,
New Zealand, the United States, Canada, Singapore, South Africa, and India. His work has
been published in Object Magazine, ROAD, and Computerworld journals, and as chapters in
Developing Business Objects (SIGS Publications, 1997), The OPEN Process Specification
(Addison-Wesley, 1997) and The Handbook of Object Technology (CRC Press, 1998).
Unhelkar is a member of the Australian Computer Society, the Software Quality Association,
and the Australian Software Metrics Association.”

===================================
1999, 421 pages. Order DR389.
===================================

The Binomial Bookstore

Management Issues

Rothstein Associates Inc.