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
Journal ArticleDOI
TL;DR: This paper outlines the principles on which the U.S. Department of Defense packet internet architecture is based and characterizes some of the protocols which implement the architecture.

68 citations

Journal ArticleDOI
TL;DR: There is a large body of recent work in areas such as module interface languages, domain-specific architectures, architectural description languages, formal underpinnings for architectural design, and architectural design environments.
Abstract: A critical aspect of the design for any large software system is its high-level organization of computational elements and interactions between those elements. Broadly speaking, this is the software architectural level of design [ Garlan and Shaw 1993; Perry and Wolf 1992]. The structure of software has long been recognized as an important issue (e.g., [Dijkstra 1968; Parnas et al. 1985]) and recently software architecture has begun to emerge as an explicit field of study for software engineering practitioners and researchers. There is a large body of recent work in areas such as module interface languages, domain-specific architectures, architectural description languages, design patterns and handbooks, formal underpinnings for architectural design, and architectural design environments [Garlan 1995; Garlan and Perry 1995]. Although there is increasing agreement about the issues addressed by architectural design, there is currently no single, widely accepted definition of “software architecture.” Indeed, the term is used in quite different ways, including: (a) the architecture of a particular system, as in “the architecture of this system consists of the following components,” (b) an architectural style, as in “this system adopts a client-server architecture,” and (c) the general study of architecture, as in “the papers in this journal are about architecture.” Within software engineering, most uses of the term “software architecture” focus on the first of these interpretations. The following definition (developed in a software architecture discussion group at the SEI in 1994) is typical:

68 citations

Book ChapterDOI
TL;DR: The protocols implementing the functions of DNA are described, including the motivations for the specific designs, alternatives and tradeoffs, and lessons learned from the implementations.
Abstract: Recognizing the need to share resources and distribute computing among systems, computer manufacturers have been designing network components and communication subsystems as part of their hardware/software system offerings. A manufacturer's general purpose network structure must support a wide range of applications, topologies, and hardware configurations. The Digital Network Architecture (DNA), the architectural model for the DECnet family of network implementations, has been designed to meet these specific requirements and to create a communications environment among the heterogeneous computers comprising Digital's systems. This paper describes the Digital Network Architecture, including an overview of its goals and structure, and details on the interfaces and functions within that structure. The protocols implementing the functions of DNA are described, including the motivations for the specific designs, alternatives and tradeoffs, and lessons learned from the implementations. The protocol descriptions include discussions of addressing, error control, flow control, synchronization, flexibility, and performance. The paper concludes with examples of DECnet operation.

68 citations

Proceedings ArticleDOI
20 Apr 2009
TL;DR: This paper presents a general system developed to evaluate QoE on IP networks, designed to be capable of emulating multi agent networks and dynamically changing conditions.
Abstract: User's requirements have become a key factor for any Quality of Service (QoS) management model to succeed. The advent and rise of new broadband services and network architectures (Triple-Play-Services, NGN…) depends on the ability of providers to achieve user's expectations in these scenarios. For that reason, the overall end user's perception (Quality of Experience – QoE) must be audited, on a regular basis, to address changing user's needs. This paper presents a general system developed to evaluate QoE on IP networks. The system architecture is designed to be capable of emulating multi agent networks and dynamically changing conditions. In addition, the results of a Web browsing QoE experiment, laid out within this emulation system, are described. The experiment was conducted on the basis of ITU-T Recommendation G.1030, and aimed to update the perceptual model, provided in this Recommendation, to today’s user requirements and technical improvements.

68 citations

Dissertation
01 Jan 1996
TL;DR: The thesis of this research is that an approach based on summarization can overcome the limitations associated with existing approaches, enabling an engineer to assess, plan, and execute changes to a software system more effectively.
Abstract: To effectively perform a change to an existing software system, a software engineer needs to have some understanding of the structure of the system. All too often, though, an engineer must proceed to change a system without sufficient structural information because existing software understanding techniques are unable to help the engineer acquire the desired knowledge within the time and cost constraints specified for the task. The thesis of this research is that an approach based on summarization can overcome the limitations associated with existing approaches, enabling an engineer to assess, plan, and execute changes to a software system more effectively. Summarization involves the production of overviews of vast amounts of user-selected information in a timely manner. I describe two techniques developed to support the summarization approach. The first technique, the software reflexion model technique, enables an engineer to summarize selected structural information in the context of a task-specific high-level model. The second technique, the lexical source model extraction technique, supports the summarization process by facilitating the scanning and analysis of system artifacts for structural information that is difficult or impossible to extract at low cost using existing approaches. Each of these techniques is lightweight and iterative: the engineer is able to quickly and easily gain access to partial and approximate structural information, and may then balance the completeness and accuracy of the information needed with the cost of further applying the technique. I demonstrate the viability of the approach by describing its use on a variety of change tasks and systems, including the use of the reflexion model technique by an engineer at Microsoft Corporation to aid with an experimental reengineering of the million-line Excel spreadsheet product.

68 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