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 published on a yearly basis
Papers
More filters
National and Kapodistrian University of Athens1, Oregon Health & Science University2, French Institute for Research in Computer Science and Automation3, University of Edinburgh4, University of Pennsylvania5, Virginia Tech6, University of Washington7, University of Southern California8, Istituto di Scienza e Tecnologie dell'Informazione9, ETH Zurich10, Max Planck Society11
TL;DR: This paper charts a research agenda on systems-oriented issues in digital libraries, including system architecture, user-level functionality, and the overall operational environment and recommends an explicit set of activities that would help achieve the research goals outlined.
Abstract: This paper charts a research agenda on systems-oriented issues in digital libraries. It focuses on the most central and generic system issues, including system architecture, user-level functionality, and the overall operational environment. With respect to user-level functionality, in particular, it abstracts the overall information lifecycle in digital libraries to five major stages and identifies key research problems that require solution in each stage. Finally, it recommends an explicit set of activities that would help achieve the research goals outlined and identifies several dimensions along which progress of the digital library field can be evaluated.
64 citations
01 Jan 2003
TL;DR: This work proposes the formalization of goals as the semantic basis for this mechanism, and sketches a system architecture that separates policy-rich goals-level planning code from a policy-neutral component assembly model.
Abstract: Contemporary pervasive computing environments demand mechanism for coherently addressing high-level user needs despite changing availability of resources. We propose the formalization of goals as the semantic basis for this mechanism, and sketch a system architecture that separates policy-rich goals-level planning code from a policy-neutral component assembly model.
64 citations
DOI•
01 Nov 2009TL;DR: The international consortium of aerospace companies with government participation has initiated the System Architecture Virtual Integration program, whose goal is to achieve an affordable solution through a paradigm shift of "integrate then build".
Abstract: The aerospace industry is experiencing exponential growth in the size and complexity of onboard software. It also seeing a significant increase in errors and rework of that software. All of those factors contribute to greater cost; the current development process is reaching the limit of affordability of building safe aircraft. An international consortium of aerospace companies with government participation has initiated the System Architecture Virtual Integration (SAVI) program, whose goal is to achieve an affordable solution through a paradigm shift of "integrate then build." Key concepts of this paradigm shift are an architecture-centric model repository as single source for analytical system models, accessed through a model bus, used as a single source for analytical models, and multi-level, multi-fidelity analysis of multiple operational quality attributes of the system and embedded software system architecture. The result is discovery of system-level faults earlier in the life cycle-reducing risk, cost, and development time. The first phase of this program demonstrated the feasibility of this new development process through a proof of concept which is the topic of this report.
64 citations
64 citations
Book•
01 Jan 1996
TL;DR: This chapter discusses Concurrency in a Real- time System,Object-Oriented Concurrency Models, and Transition from Design to Implementation, and the Design Criteria of OCTOPUS.
Abstract: 1. Introduction. Real-time Systems. Object-Oriented Methods. Concurrency in a Real- time System. Object-Oriented Concurrency Models. Levels of Concurrency. Design Criteria of OCTOPUS. Introduction to Case Studies. 2. Overvoew of the Octopus Method. Roadmap and Structuring the Development Process. System Requirements Phase. System Architecture Phase. Subsystem Analysis Phase. Subsystem Design Phase. Subsystem Implementation Phase. 3. Requirements Specification. Use Cases. Use Case Diagram. System Context Diagram. 4. System Architecture. Modular Structure. Early Division into Subsystems. Subsystems Diagram. Incremental Development. Interfaces. Example. 5. Analysis Phase. Object Model. Functional Model. Dynamic Model. Analysis of the Hardware Wrapper. Summary. 6. Design Phase. Design Objects. Interaction of Objects. Class Outlines. Design of Concurrency. Outlines of Processes and Messages. Design of the Hardware Wrapper. Summary. 7. Process Priorities and Timing. Basic Concepts. Deriving Process Priorities. Timing and Concurrency Behavior. 8. Transition from Design to Implementation. C++ and C Interpretability. Member Access Control. Visibility. Memory and Performance Optimization. Synchronization. Implementing Statecharts. Constructing Global Objects. Development Environment. 9. Case Study: Subscriber Line Tester. System Requirements Specification. SLT Application Subsystem Analysis. SLT Application Subsystem Design. Exercise: Hardware Wrapper. 10. Case Study: Cruise Control. Recapped System Requirements Specification. Application Subsystem Analysis. Analysis and Design of the Hardware Wrapper. Design of Application Subsystem. 11. Referemce Manual. Notation Summary. Case Tools. OCTOPUS Roadmap. References. Glossary. Index.
64 citations