Organizational change is a reality of the modern world. If anything, organizations can expect to face the need for even more change in the future, at an ever-faster pace. Organizations have to deal with new technology, and with upgrades for existing technology. They have to cope with reorganizations, process improvement initiatives, and mergers and acquisitions. So, with all that change going on, how are organizations managing to cope? The reality is that relatively few of the organizations that institute change -- or are forced into it -- realize the benefits they had hoped for, and in fact end up worse off than they were before. The Microsoft Solution Framework is a system designed to help organizations effectively handle the constant changing parameters of their software and hardware requirements (Solutions framework, 1998, Online).
There are four main phases to the system development life cycle:
1. The Envisioning Phase -- This is where a Vision/Scope idea for a new software product gains interest and approval for further development. According to the Microsoft web site, at this point, it could be a program that "helps you plan an enterprise architecture that adapts to (or drives) industry change. Consistently build business-driven applications. And manage your computing environment" (Process model, 1998, Online).
2. The planning phase -- This phase leads to the Project Plan Approved milestone and contains all the steps needed to complete the vision and meet all required elements of customer satisfaction. (Solutions framework, 1998, Online).
3. The developing phase -- This phase includes a major event known as process management. This eliminates the well-known problems that plague some project developments, including: (a) The project turning into something it was not designed to be; (b) The project taking too long to develop and costing too much; (c) Someone
...