Academia.eduAcademia.edu

Figure 8 – uploaded by chaitanya k

See full PDFdownloadDownload figure
Fig. 8. High level Software Architecture The software architecture of the system is derived by systematic organization and representation of the architecture styles of the constituent subsystems. At the topmost level the subsystems identified during the first level of functional decomposition along with data and control interfaces are represented. This forms the high-level software architecture. (Figure 8) Each of these components are exploded subsequently and the internal architecture confirming to its style is represented. This is continued to the required level of abstraction. Hierarchical organization of these representations forms the software architecture of the system.

Figure 8 High level Software Architecture The software architecture of the system is derived by systematic organization and representation of the architecture styles of the constituent subsystems. At the topmost level the subsystems identified during the first level of functional decomposition along with data and control interfaces are represented. This forms the high-level software architecture. (Figure 8) Each of these components are exploded subsequently and the internal architecture confirming to its style is represented. This is continued to the required level of abstraction. Hierarchical organization of these representations forms the software architecture of the system.

Related Figures (7)

Fig. 1. Block diagram of distributed embedded system.
Fig. 1. Block diagram of distributed embedded system.
Fig. 2. Sensor — Data Acquisition The component types are Sensor (Producer), Filter and the Sink (Consumer). The sensor component produces the data and pushes it into an output port connected to the input end of a pipe. The Filter component receives data from an input port connected to the output end of a pipe, transforms the data and puts the data onto an output port that is connected to the inpu end of a different pipe. The destination or the sink component gets the data from the input port that is connected to the outpu end of a pipe and consumes the data. A filter component is a combination of a sink and a Producer. The components in this subsystem are usually realized in hardware with dedicated communication links between the components.
Fig. 2. Sensor — Data Acquisition The component types are Sensor (Producer), Filter and the Sink (Consumer). The sensor component produces the data and pushes it into an output port connected to the input end of a pipe. The Filter component receives data from an input port connected to the output end of a pipe, transforms the data and puts the data onto an output port that is connected to the inpu end of a different pipe. The destination or the sink component gets the data from the input port that is connected to the outpu end of a pipe and consumes the data. A filter component is a combination of a sink and a Producer. The components in this subsystem are usually realized in hardware with dedicated communication links between the components.
The components of this architecture are the distinct processing steps. They are independent software modules having a definite responsibility.
The components of this architecture are the distinct processing steps. They are independent software modules having a definite responsibility.
Fig. 4. Data Analysis
Fig. 4. Data Analysis
The data flow architecture style — Pipe and filter - is proposed. The data source here is the Human Machine Interface subsystem and the data sink is the Supervisory Control subsystem. When the operator changes the system mode the data sink pulls the corresponding configuration from the source . Therefore the architectural style of the subsystem is refined as “Pull variant” of Pipe and Filter style. The Supervisory control system informs the transformed configuration control words to the subsystem responsible for effecting the configuration change. The Supervisory control scenario while following _ this architecture style is shown in Figure 6.
The data flow architecture style — Pipe and filter - is proposed. The data source here is the Human Machine Interface subsystem and the data sink is the Supervisory Control subsystem. When the operator changes the system mode the data sink pulls the corresponding configuration from the source . Therefore the architectural style of the subsystem is refined as “Pull variant” of Pipe and Filter style. The Supervisory control system informs the transformed configuration control words to the subsystem responsible for effecting the configuration change. The Supervisory control scenario while following _ this architecture style is shown in Figure 6.
Fig. 7 Human Machine Interface The Model View Controller architecture style is proposed for this subsystem [2]. The Human Machine interface scenario while following this architecture style is shown in Figure 7.
Fig. 7 Human Machine Interface The Model View Controller architecture style is proposed for this subsystem [2]. The Human Machine interface scenario while following this architecture style is shown in Figure 7.
580 California St., Suite 400
San Francisco, CA, 94104
© 2025 Academia. All rights reserved