Modeling, Models, Notations:
  • modeling: the levels (introduction)
  • e.g. modeling reality: physics
  • e.g. modeling reality: what the system is about
  • system modeling: the paradigms
  • e.g. programs - descriptions of computation
  • e.g. models of computation
  • system properties: state
  • system properties: architecture
  • system models (dynamics graphs)
  • information models: spatial
  • associative networks
    		•  

      System Properties: Architecture

      Location http://www.cs.mun.ca/~ulf/mod/para.html.
    Written 291003 by Ulf Schünemann.
    Copyright (C) 2003 Ulf Schünemann.

    back to: scientific landscape (signs, relations) | prog. lang. design (paradigms, prog. lang. list)

    System Architecture
    The (recursive) analysis of a system into
    (a) [architectural] components (cf. reusable software components) and
    (b) connectors between them (which are a precondition for dynamic and/or static dependencies/couplings).
    Components as well as connectors can be elementary, or themselves subsystems composed of sub-components and/or sub-connectors.
     
    Classes of Architectures of Software System
    In software systems, the components and connectors are software objects [^]. For software systems there exists some work in classifying (them by) their architecture. The focus is not on developing a complete taxonomy, but on identifying and characterizing the most important classes of architectures, called "architectural styles".

    [REAL] David R Harris, Howard B Reubenstein, Alexander S Yeh: Reverse Engineering to the Architectural Level; 186-195; SE'95. (except for 'event-driven')

    navigation bar: Message Passing
  • message passing diagrams
  • client-server architecture
  • object systems (model of computation)
  • message filtering systems
  • message passing meta-programming
    • Interacting-components architecture (agents, objects) [REAL].
  • client-server architecture with directed "messages" (=> explicit transfer of control)
       (the foundational architecture of eg. object systems)
  • event-driven architecture with multicast "events" (=> implicit transfer of control)
       (the foundational architecture of eg. multiagent systems)
    • Repository architecture [REAL]
    Imperative models of computation with modules communicating
    via shared global variables have a repository architecture.
    Layered architecture [REAL], also called "stratified design":
  • opaque = access only adjacing layers, or
  • transparent = can access more than one layer away.
    • navigation bar: Dataflow
  • agent/thing relation
  • dataflow system models
  • dataflow models of computation
  • pipes & filters architecture
    • Pipes-and-filters architecture [REAL]
    Dataflow models of computation have a pipe-and-filters architecture
  • The "sequence paradigm": pipes and filters in sequence
    • Abstract-data-type architecture [REAL]
    API-users architecture [REAL]
    Optimizing-algorithm architecture [REAL]
    Task-spawning architecture [REAL]