System Architecture

Topics: Database, Database management system, Relational model Pages: 41 (8711 words) Published: June 1, 2014
Information System Architectures: From Art to Science
Peter C. Lockemann
Fakultät für Informatik
Universität Karlsruhe
Postfach 6980
76128 Karlsruhe
lockeman@ipd.uka.de
Abstract: The presentation claims that architectural design plays a crucial role in system development as a first step in a process that turns a requirements specification into a working software and hardware system. As such, architectural design should follow a rigorous methodology – a science – rather than intuition – an art. Our basic premise is that requirements in information systems follow a service philosophy, where services are characterized by their functionality and quality-ofservice parameters. We develop a design hypothesis that takes the service characteristics into account in a stepwise fashion. We then validate the hypothesis for traditional database characteristics, demonstrate for novel requirements how these would affect architectures, and finally apply it to the current 4 -tier server

architectures.

1

Motivation

Information systems grow in the diversity of their application domains, number of users, and geographic distribution, but so does their complexity in terms of the number and functionality of components and the number of connections between these. An almost bewildering multitude of architectural patterns has appeared over the more recent past, that try to bring order into the evolving chaos. To name just a few of the buzzwords, take layered architectures, n-tier architectures, component architectures, middleware, vertical architectures, horizontal architectures, enterprise this-and-that. Nonetheless, it seems that these architectures have enough in common so that one suspects that they just look at similar phenomena from different perspectives, emphasize different aspects, or explore issues to different depths. The premise of this paper is that architectural design plays a crucial role in system development. Unfortunately though, architectural system design does not seem to have too many friends. Typical excuses are that “top-down designs never work anyway because they ignore the technical possibilities and opportunities”, that “even the cleanest architecture deteriorates over time due to the many additions and modifications on short notice”, or that “architectures emphasize order over performance”. We suspect that the real reason is the lack of a comprehensive, systematic and unifying approach to architectural design that makes the patterns in some sense comparable.

We claim that architectural design is the first step in a process that turns a requirements specification into a working software and hardware system and, hence,

could be seen as “programming-in-the-very-large”. Since it is an accepted doctrine that mistakes when caught in the early stages are much cheaper to correct than when discovered in the late stages, good architectural system design could be of enormous economical potential.

The purpose of this paper is to take a first step in the direction of a methodology for architectural design. Or in other words, we submit that architectural design should follow a methodology and not intuition, i.e., should be treated as a science and not as an art. In order not to become overly ambitious, and to stay within the confines of a conference paper, we will limit ourselves to information systems as the synthesis of data base and data communication systems, with more emphasis on the former.

2
2.1

Services
Services and resources

Since we claim that architectural design is the first step in a process that turns a requirements specification into a working software and hardware system, an essential ingredient of the design method is a uniform and rigorous requirements specification. Requirements is something imposed by an outside wo rld. For information systems the outside world are the business processes in some real-world organization such as industry, government, education, financial institutions,...

References: Integration von Datenübertragungstechnik und Datenbanktechnik. dpunkt.verlag. 2003 (in
German)
VLDB Conference. 2002
[As79]
Herzog, U.: Effiziente Konsistenzprüfung in Datenbanksystemen. Infix. 1996 (in German)
[HR99] Härder, T.; Rahm, E.: Datenbanksysteme: Konzepte und Techniken der Implementierung.
Springer, 1999 (in German)
[Lu02]
systems. Submitted for publication. 2002
[St02]
Continue Reading

Please join StudyMode to read the full document

You May Also Find These Documents Helpful

  • Architecture Essay
  • what is architecture? Essay
  • Management in Architecture Essay
  • Essay on architecture and psychology
  • Essay about GSM system
  • Networking
  • Vertical Architecture Essay
  • Client Server Architecture Essay

Become a StudyMode Member

Sign Up - It's Free