Software architecture, definition

Some of the early work on systematic description of software architecture was done by Shaw and Garlan [Shaw96b]. A good description of the breadth of issues involved in software architecture, which we have used and adapted, is in [Bass98], Our informal definition of architecture was coined in frustration by D Souza (we believe). 

System managers must maintain a System Definition SOP including a high-level description of the software architecture, general considerations, responsibilities, and a hst of current user manuals. [FDA 483, 1999]... 

The software architecture built with an EO approach is presented in Fig. 2.9. The input of the simulation problem can be formulated by means of a meta-language, or be supported by an intelligent GUI. In Aspen Dynamics, the problem definition starts at... 

To develop AUTOSAR-compliant systems, the model authoring tool Artop [2] provides basic functionality to create AUTOSAR system models, software architecture models, and ECU configurations. Furthermore, the ARText framework [3] supports the definition of textual languages for AUTOSAR. For example, ARText s software component language allows developers to describe software architectures at the VFB level. We use ARText s capabilities to define a textual language for software safety requirements. 

Referring to the above considerations, one arrives at the following definitions of the hardware and software architectures HARDWARE (see fig. 3)... 

Research users need full access to the functional elements of the spectrometer system and require the most efficient and flexible tools for MR sequence and application development. If the measurement methods delivered with the software do not adequately address the specific investigational requirements of a research team, modem NMR software is an open architecture for implementing new and more sophisticated functionality, with full direct access to all hardware controlling parameters. After evaluation, the new functionality can be developed with the help of toolbox functions that allow rapid prototyping and final builds, to enable the new sequence to be executed by non-experienced personnel and then used in routine applications. These toolboxes provide application oriented definitions and connect to standard mechanisms and routine interfaces, such as the geometry editor, configuration parameters or spectrometer adjustments. 

Sherwin-Williams has developed such a polymer process control system. The methodology used to accommodate the contrasting requirements has two key elements. First, the software is based on a simple architecture that places the definition of changing reactor hardware elements and characteristics in easily modified configuration files (5). Second, the language uses a small number of basic commands to describe formulations and reactor control. Complex operations are described by reference to commands tables (macros) built using several basic commands or other macros. 

Implementation of the software design commences once the design is finalized. Sandpit (prototyping of application functionality) and development facilities are required to support system definition and development. A validation environment to perform qualification testing and a live environment completes the system development and operational architecture. 

The creation of the concept of reuse definition scenarios during Apollo to save time in development and space in the software was a predecessor to the type of higher level language statements used within the systems language. This included horizontal and vertical reuse that led to a flexible open architecture within the DBTF environment. 

The book shows how intense has been in recent years the work for designing parallel and vector algorithms. Accurate electronic structure of reactive systems as well as exact and high level approximate three-dimensional calculations of the reactive dynamics, efficient directive and declaratory software for modeling complex systems. In turn, new and more complex problems have been posed by these advances. Some of them are concerned with the definition of the computer architecture better suited for chemical calculations. Others are concerned with balancing within the application vector and parallel structures. 

A thought experiment by [Green et al. 83] has led to the definition of the ideal architecture and functionalities of the software engineering environment of the future, namely the so-called KBS A Knowledge-Based Software Assistant). 

Hence a system employing software is almost by definition Type B, since its failure modes are hard to define, its behavior in fault conditions may also be hard to define, and there may be no dependable failure data. Because of this additional complexity and the non-deterministic calculation of failure probability, lEC 61508 has stronger architectural constraints for type B systems than for type A. Typically the pfd range claimable for type B systems is an order of magnitude less than for an otherwise architecturally similar Type A system. 

---