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.

Mobile commerce integrated with RFID technology in a container depot

Abstract: In this paper, we present the findings of a case study on the development of a radio frequency identification (RFID) prototype system that is integrated with mobile commerce (m-commerce) in a container depot. A system architecture capable of integrating mobile commerce and RFID applications is proposed. The system architecture is examined and explained in the context of the case study. The aims of the system are to (i) keep track of the locations of stackers and containers, (ii) provide greater visibility of the operations data, and (iii) improve the control processes. The case study illustrates the benefits and advantages of using an RFID system, particularly its support of m-commerce activities in the container depot, and describes some of the most important problems and issues. Finally, several research issues and directions of RFID applications in container depots are presented and discussed.

The Cydra 5 departmental supercomputer: design philosophies, decisions, and trade-offs

Abstract: The Cydra 5 is a heterogeneous multiprocessor system that targets small work groups or departments of scientists and engineers. The two types of processors are functionally specialized for the different components of the work load found in a departmental setting. The Cydra 5 numeric processor, based on a directed-data-flow architecture, provides consistently high performance on a broader class of numerical computations. The interactive processors offload all nonnumeric work from the numeric processor, leaving it free to spend all its time on the numeric application. The I/O processors permit high-bandwidth I/O transitions with minimal involvement from the interactive or numeric processors. The system architecture and data-flow architecture are described. The numeric processor decisions and tradeoffs are examined, and the main memory system is discussed. Some reflections on the design issues are offered. >

Designing object systems: object-oriented modelling with Syntropy

Abstract: Systems, models and views Part 1 Models of the world: describing structure - the basics describing structure - adding more detail describing behaviour - the basics describing behaviour - adding more detail Part 2 Models of software: software specification describing the implementation sub-types, inheritance and conformance concurrency Part 3 System architecture: relationships between models domains encapsulation and reuse Part 4 The development process

Method and apparatus including system architecture for multimedia communications

Abstract: A system architecture for multimedia communications comprises a bandwidth controller for continuously moderating the run-time status and/or condition changes of the telecommunications network and dynamically adjusting the corresponding bandwidth requirement for accommodating the change of status or condition prior to transmitting the video and/or audio information. The system further includes a reconfiguration memory for standardizing and re configuring the video and/or audio information according to a selective internal file format which is universally compatible with any coding algorithms received from, or supplied to the telecommunications network, the reconfiguration memory performing scalable internal data reformatting among incompatibly received or transmitted video and/or audio information.

Use case maps as architectural entities for complex systems

Abstract: The paper presents a novel, scenario based notation called Use Case Maps (UCMs) for describing, in a high level way, how the organizational structure of a complex system and the emergent behavior of the system are intertwined. The notation is not a behavior specification technique in the ordinary sense, but a notation for helping a person to visualize, think about, and explain the big picture. UCMs are presented as "architectural entities" that help a person stand back from the details during all phases of system development. The notation has been thoroughly exercised on systems of industrial scale and complexity and the distilled essence of what has been found to work in practice is summarized. Examples are presented that confront difficult complex system issues directly: decentralized control, concurrency, failure, diversity, elusiveness and fluidity of runtime views of software, self modification of system makeup, difficulty of seeing large scale units of emergent behavior cutting across systems as coherent entities (and of seeing how such entities arise from the collective efforts of components), and large scale.