or obvious reasons, we have not been able to expand on the task in depth, but the intention was to combine concepts and notions that we covered in numerous chapters into a meaningful stream of rea- soning that shows how design architects try to squeeze system choices into the constraints imposed upon them by specification and product requirements. SUMMARY In this chapter, we tried to fill the most important gaps of material that remained uncovered in the rest of the book. We discussed memory technologies and looked deeper into software development costs. We uncovered some very important software ownership issues and discussed the costs and modeling of productivity to develop this software. We concluded by skimming the surface of a large-scale real- life design challenge-namely, that of an MSR- order to show the magnitude and the complexity of the problem. We also put ideas and concepts into perspective, especially for newcomers in the field. SUGGESTED REFERENCES Memory manufacturer web sites have extensive literature, technical notes, and articles on the various memory technologies. These documents describe their functionality, principles of operation, systems design, and trade-offs. The following are a few good examples: www.micron.com www.fujitsu.com www.infineon.com www.rambus.com www.samsung.com www.toshiba.com www.idt.com A very good reference on numerous fundamental memory technologies is the following textbook: Betty Prince, High Performance Memories: New Architecture DRAMs and SRAMs Evolution and Function, revised updated edition (New York: John Wiley, 1999). Dr. Betty Prince's company Memory Strategies International is also a great source for more up- to-date memory-related advice, reference publications and material, and consulting. The company's web site is www.memorystrategies.com. She provides a glimpse into the near future of memory technologies in her most recent book Emerging Memories: Technologies and Trends (Dordrecht, The Netherlands: Kluwer Academic Publishers, 2002). RLDRAM is discussed in de