Conclusion
Conclusion If someone invents a new microchip or a new kind of display-screen technology, it can be a simple matter to build a manufacturing plant, create a marketing organization, and distribute the new technology worldwide in a matter of months. OK, not simple, maybe, but in fact our era is marked by the number of times just this has been done. If someone comes up with a good idea for the process by which technology is created, however, this can be distributed only one way: The innovator must teach someone the new method. That person must then teach someone else. Maybe that person can teach a class of 20. The innovator can write a book, although that means less control over what is learned from that book. Altogether, this is a much slower process. Moreover, it is prone to all the errors we experienced in playing "Telephone" when we were children. The method that is taught a year after it has been invented may be very different from what the originator had in mind. Creating system development methods has not been easy. For us to have come as far as we have in developing approaches to requirements analysis is truly remarkable . We all live in hope that the next method or the next technique will suddenly make it easy to build large complex systems. It is a foolish hope. Developing systems will never not be hard. But techniques are being developed all the time, and progress is being made. It hasn't necessarily gotten easier to build systems, but the systems we are building are vastly more sophisticated than those built just 20 or 30 years ago. And this is not just because the technology is better. It is because we are continually getting smarter in our ability to build systems that are actually useful to someone. This book is the first chapter of a story that is just beginning. This is an incredible time to be alive . We get to participate in an incredibly dynamic industry, and we get to be in on building its future.  |
| | |
Team-Fly  |
| Top |
EAN: 2147483647
Pages: 129