"Reference models can be quite comprehensive, consisting of hundreds or thousands of model objects. This is why various levels of aggregation are used. Reference models provide enterprises with an initial process engineering solution, letting them determine the degree of detail of the model and the business content."

“Business information systems can be either designed as custom applications or purchased as off-the-shelf standard solutions. The development of custom applications is generally expensive and is often plagued by uncertainties, such as the selection of appropriate development tools, the duration of the development cycle, or the difficulties involved in assessing costs. Thus, empirical surveys have shown that between half to two-thirds of information systems projects fail. The current tendency to shift from individual development to standardized, prepackaged software solutions is therefore not surprising.”

“The creation and implementation of integrated information systems involves a variety of collaborators including people from specialist departments, informatics, external advisers and manufacturers. They need clear rules and limits within which they can process their individual sub-tasks, in order to ensure the logical consistency of the entire project. Therefore, an architecture needs to be established to determine the components that make up the information system and the methods to be used to describe it. The ARIS architecture developed in this book is described in concrete terms as an information model within the entity-relationship approach. This information model provides the basis for the systematic and rational application of methods in the development of information systems. It also serves as the basis for a repository in which the enterprise's application - specific data, organization and function models can be stored. The ARIS architecture constitutes a framework in which integrated applications systems can be developed, optimized and converted into EDP - technical implementations. At the same time, it demonstrates how business economics can examine and analyze information systems in order to translate their contents into EDP-suitable form.”

“Business process engineering aims to achieve the greatest efficiency possible in terms of business-organizational solutions. Organizational departments, reengineering project teams or even business process owners can be responsible for process engineering. While work schedule development for manufacturing processes might be institutionally allocated to a certain department for years as job preparation, other kinds of business processes are not quite as regimented.”

“At the heart of the book are the functional areas of an industrial firm. Although the data structures are thereby designed according to functional area the integration principle of supra-functional processing of tasks occupies the foreground. This book aims to achieve both a scientifically-based procedural method and a practically relevant, tried and tested approach. The author's experience of developing and introducing integrated information systems in several large industrial firms is incorporated in the treatment presented.”

“There are two fundamental ways of engineering information systems. The “formal driven” approach is based on the goal of developing and implementing a technical correct running system. The “content driven” approach is based on the goal of developing and implementing an organizational correct running system. By using reference models, content and technology can be combined in a new way”