ion (compared to the standards libraries of today). Furthermore, whether AMLn is used in producing standards or only in implementors' devel- opment processes, AMLn gives strong support for validation through simulation (provided that model creators describe the behavior of interfaces and elements, e.g., using AMLs). The purpose with using AMLn as an analyzing tool may be to produce a model that can explain a network standard or an implementor's system documentation. AMLn is therefore also an excellent tool for re-engineering. Furthermore, an implementor who supports and documents the evolution of his system in an AMLn model will experience a considerable increase in system quality and length of life. The model can also be a basis for code generation as well as for network configuration, which can result in a considerably shorter time-to-mar- ket for new system functions and services. The author has developed and applied AMLn for almost a decade. A few co- workers have been exposed to AMLn ideas over the years. AMLn is, however, completely unknown to a broader audience. The purpose with the case studies in this chapter is therefore to demonstrate AMLn as a modeling language by analyz- ing some well known network standards. In doing so, two effects have become very obvious. 1. The problem of describing a model on a serial media, such as a book. Using AMLn the way it is intended means that an information model is created in a database. Such a model is a more or less hierarchical structure of a large number of information elements. The intended way of getting to know the system is by browsing the model, i.e., accessing different information elements through the model itself in a user-selected fashion. There is very little need for adding eluci- 6 Applying AMLn dating text to an AMLn model. We cannot however store a model on the pages of a book, we can only describe a model. This implies that (a) a particular order of description had to be chosen and (b) a lot of text had to be produced that is not part of the model i