scispace - formally typeset
Search or ask a question
Topic

Systems architecture

About: Systems architecture is a research topic. Over the lifetime, 17612 publications have been published within this topic receiving 283719 citations. The topic is also known as: system architecture.


Papers
More filters
Proceedings ArticleDOI
27 Jul 2014
TL;DR: In this article, an adaptive protection and microgrid control system has been developed and currently being installed at Hailuoto island in Finland based on a centralized controller running the real-time analysis of the data received from the field Intelligent Electronic Devices and communicating with them by means of IEC 61850 communications.
Abstract: Microgrids can provide various economic and environmental benefits but their implementation poses great technical challenges in control, protection and energy management. One of the most important technical aspects in microgrids is distribution system protection. This paper first demonstrates a need for and then focuses on the design aspects of the adaptive protection system addressing issues such as: selection of alternative setting groups, components and system architecture; system configuration and programmed logic. The system is based on a centralized controller running the real-time analysis of the data received from the field Intelligent Electronic Devices and communicating with them by means of IEC 61850 communications. The adaptive protection and microgrid control system has been developed and currently being installed at Hailuoto island in Finland.

64 citations

Proceedings Article
01 Jan 2003
TL;DR: An overview of issues involved in the specification of non- functional properties in a component-based development is given and a system architecture for supporting and a methodology for developing components with guaranteed non-functional properties is developed.
Abstract: In the last few years component-based software development has achieved a great improvement in software engineering. Component models can be found mainly for graphical user interfaces (JavaBeans [12], ActiveX [2]) and server components (EJB [7], COM [10]). Using the component paradigm is well understood for independent application development. In contrast, the reuse of existing components is still difficult. For reusing components they need an exact specification of their functional and non-functional properties. The existing component models do not support this in a sufficient manner. E.g., in EJB the deployment descriptor mainly supports functional specification. There exist no concepts for handling all aspects of the component paradigm, in particular non-functional aspects. The COMQUAD-project has the goal to investigate such concepts. COMQUAD develops a system architecture for supporting and a methodology for developing components with guaranteed non-functional properties. This paper gives an overview of issues involved in the specification of non-functional properties in a component-based development. It can be separated into the specification at development time and the representation of non-functional properties at runtime. First, we have to identify all non-functional requirements on the system and all non-functional offers of the system. As part of the development process these requirements have to be separated into offers and demands

64 citations

Book ChapterDOI
TL;DR: The experimental application of the i* agent-based system approach to model a system architecture in terms of dependencies between components to achieve goals, satisfy soft goals, complete tasks and provide and consume resources is reported.
Abstract: Selecting multiple, interdependent software components to meet complex system requirements is difficult. This paper reports the experimental application of the i* agent-based system approach to model a system architecture in terms of dependencies between components to achieve goals, satisfy soft goals, complete tasks and provide and consume resources. It describes two treatments, at the architecture and component levels, that can be applied to these architecture models to determine important system properties that inform multiple component selection. The modelling approach and treatments are demonstrated throughout using the example of a meeting scheduler system.

64 citations

Proceedings ArticleDOI
08 Jun 2003
TL;DR: In this paper, the implications for waveform design and the consequent limitation on system architecture, including antenna design and receiver architecture, are discussed, and practical considerations such as available semiconductor technology with low-cost plastic packaging are reviewed.
Abstract: The recent approval granted by the FCC for the use of Ultra Wide Band (UWB) signals for vehicular radar applications has provided a gateway for production of these sensors as early as in 2004. However, the rules governing the allowable spectral occupancy create significant constraints on the operation of the sensors. The implications for waveform design and the consequent limitation on system architecture, including antenna design and receiver architecture are discussed. Other practical considerations such as available semiconductor technology with low-cost plastic packaging are reviewed. This is developed into a methodology for developing a single board sensor with integrated antenna. Results are presented for a specification compliant antenna, and a low-cost plastic package for 24GHz ICs. Finally, the required IC architecture for a Transceiver is presented, along with measured results of a single-chip homodyne I/Q down-conversion receiver fabricated in SiGe.

64 citations

Book ChapterDOI
Dewayne E. Perry1
TL;DR: Having a product line implies having a generic architecture from which the individual product architectures can be derived in some manner.
Abstract: Two of the fundamental needs in defining an architecture for a product line are to be able to generalize or abstract from the individual products to capture the important aspects of the product line and to be able to instantiate an individual product architecture from the product line architecture In other words, having a product line implies having a generic architecture from which the individual product architectures can be derived in some manner.

64 citations


Network Information
Related Topics (5)
Software
130.5K papers, 2M citations
90% related
Wireless sensor network
142K papers, 2.4M citations
86% related
Information system
107.5K papers, 1.8M citations
85% related
Wireless
133.4K papers, 1.9M citations
85% related
Network packet
159.7K papers, 2.2M citations
85% related
Performance
Metrics
No. of papers in the topic in previous years
YearPapers
202311
202227
2021405
2020555
2019638
2018572