Software Factories: Refactoring an Industry

Software Factories: Refactoring an Industry

Problems with the current concept of reuse
Software development has always been costly and time-consuming process. Specialized requirements and lack of skilled resources are just two of the difficulties facing companies today. Pressure to deliver software, on time and within budget, have pushed developers to look for a way to increase value delivered, while decreasing development time.

For many years now, efficient reuse of existing assets, either through object-oriented programming, component based development, patterns-based architecture, has been one of the core objectives for the IT industry as a whole. Reuse is seen as a means to combat many of the problems facing development teams. However, for many years and several different technology paradigms, this level of reuse has eluded the industry as a whole.

Software Factories: Assembling applications with Patterns, Models, Frameworks, and Tools aims to change this by modifying the definition of reuse as used by the IT industry and bring a more manufacturing approach to software reuse.

How To Save The Internet

Internet would shut down by 2006

Professor Hannu H. Kari of the Helsinki University of Technology is a smart guy, but most people thought he was just being provocative when he predicted, back in 2001, that the Internet would shut down by 2006. "The reason for this will be that proper users' dissatisfaction will have reached such heights by then that some other system will be needed," Kari said, "unless the Internet is improved and made reliable." Last fall, Kari bolstered his prophecy with statistics. Extrapolating from the growth rates of viruses, worms, spam, phishing and spyware, he concluded that these, combined with "bad people who want to create chaos," would cause the Internet to "collapse!"—and he stuck to 2006 as the likely time.

Disclaimer

These postings are provided "AS IS" with no warranties, and confers no rights. This site contains my personal opinions and does not necessarily reflect the viewpoint of my employer or anybody in general. The thoughts and opinions expressed herein are solely my own.