Software Engineering-Re-Engineering

In a seminal article written for the Harvard Business Review, Michael Hammer  laid the foundation for a revolution in management thinking about business processes and computing:

It is time to stop paving the cow paths. Instead of embedding outdated processes in silicon and software, we should obliterate them and start over. We should “reengineer” our businesses: use the power of modern information technology to radically redesign our business processes in order to achieve dramatic improvements in their performance.

Every company operates according to a great many unarticulated rules . . . Reengineering strives to break away from the old rules about how we organize and conduct our business.

Like all revolutions, Hammer’s call to arms resulted in both positive and negative changes. During the 1990s, some companies made a legitimate effort to reengineer, and the results led to improved competitiveness. Others relied solely on downsizing and outsourcing (instead of reengineering) to improve their bottom line. “Mean” organizations with little potential for future growth often resulted .

During this first decade of the twenty-first century, the hype associated with reengineering has waned, but the process itself continues in companies large and small. The nexus between business reengineering and software engineering lies in a “system view.”

Software is often the realization of the business rules that Hammer discusses. As these rules change, software must also change. Today, major companies have tens of thousands of computer programs that support the “old business rules.” As managers work to modify the rules to achieve greater effectiveness and competitiveness, software must keep pace. In some cases, this means the creation of major new computer- based systems. But in many others, it means the modification or rebuilding of existing applications.
Software Engineering-Re-Engineering Reviewed by 1000sourcecodes on 05:26 Rating: 5
Powered by Blogger.