Book contents
- Frontmatter
- Contents
- Preface
- Contributors
- Acknowledgments
- Introduction
- Notes for Educators: AMA Teaching Methods
- Chapter 1 Collaborative Engineering
- Chapter 2 Software Architecture and Integration Technologies
- Chapter 3 From a Specific Task to “Integration-Ready” Components
- Chapter 4 Integration with Voice
- Chapter 5 An Introduction to Knowledge Technologies
- Chapter 6 Write Once
- Chapter 7 The New Generation of Client–Server Software
- Chapter 8 Wireless Technologies
- Chapter 9 Programming Wireless Application Protocol Applications
- Chapter 10 A Single JavaCard Identity Key for All Doors and Services
- Chapter 11 The J2ME Family
- Chapter 12 Speech Technologies on the Way to a Natural User Interface
- Chapter 13 Integration with Knowledge
- Chapter 14 Distributed Life in the JXTA and Jini Communities
- Appendix 1 Java and C#: A Saga of Siblings
- Appendix 2 XML and Web Services
- Appendix 3 Source Examples
- Index
Introduction
Published online by Cambridge University Press: 17 August 2009
- Frontmatter
- Contents
- Preface
- Contributors
- Acknowledgments
- Introduction
- Notes for Educators: AMA Teaching Methods
- Chapter 1 Collaborative Engineering
- Chapter 2 Software Architecture and Integration Technologies
- Chapter 3 From a Specific Task to “Integration-Ready” Components
- Chapter 4 Integration with Voice
- Chapter 5 An Introduction to Knowledge Technologies
- Chapter 6 Write Once
- Chapter 7 The New Generation of Client–Server Software
- Chapter 8 Wireless Technologies
- Chapter 9 Programming Wireless Application Protocol Applications
- Chapter 10 A Single JavaCard Identity Key for All Doors and Services
- Chapter 11 The J2ME Family
- Chapter 12 Speech Technologies on the Way to a Natural User Interface
- Chapter 13 Integration with Knowledge
- Chapter 14 Distributed Life in the JXTA and Jini Communities
- Appendix 1 Java and C#: A Saga of Siblings
- Appendix 2 XML and Web Services
- Appendix 3 Source Examples
- Index
Summary
One might think that the software industry is performing very well because it is armed with object-oriented approaches, Web services, Java and NET technologies, and so forth. Unfortunately, this is not true.
There may be something wrong with the way we write programs. The process has not changed much during the past twenty years, except that applications and tools are getting bigger. Yet are they better and more scalable? Do they require any common sense? Can they be reused in different circumstances?
If these things were true, I do not think we would be rewriting the address book, schedule, order, and inventory applications over and over again instead of moving to new, untouched tasks. We would be able to accumulate the professional knowledge gained by millions of knowledge workers (everyone who manages information flow on a daily basis) instead of routinely losing it, as we do today. We would also not be facing the current IT crisis.
We could even have had more precise and direct access to the market's supply and demand, which would have reduced the glaring inefficiencies of the software marketplace of the 1990s. A big change is required to return investors' confidence to IT, and, hopefully, the change is coming.
Yes, technology can help economic stability if applied with precision. Sometimes I wonder why big companies are constantly growing bigger while small ones tend to disappear.
- Type
- Chapter
- Information
- Integration-Ready Architecture and DesignSoftware Engineering with XML, Java, .NET, Wireless, Speech, and Knowledge Technologies, pp. xviii - xxviiiPublisher: Cambridge University PressPrint publication year: 2004