Добірка наукової літератури з теми "System architecture"

Оформте джерело за APA, MLA, Chicago, Harvard та іншими стилями

Оберіть тип джерела:

Ознайомтеся зі списками актуальних статей, книг, дисертацій, тез та інших наукових джерел на тему "System architecture".

Біля кожної праці в переліку літератури доступна кнопка «Додати до бібліографії». Скористайтеся нею – і ми автоматично оформимо бібліографічне посилання на обрану працю в потрібному вам стилі цитування: APA, MLA, «Гарвард», «Чикаго», «Ванкувер» тощо.

Також ви можете завантажити повний текст наукової публікації у форматі «.pdf» та прочитати онлайн анотацію до роботи, якщо відповідні параметри наявні в метаданих.

Статті в журналах з теми "System architecture"

1

Sarma, A. D. N. "A Generic Functional Architecture for Operational BI System." International Journal of Business Intelligence Research 9, no. 1 (January 2018): 64–77. http://dx.doi.org/10.4018/ijbir.2018010105.

Повний текст джерела
Анотація:
In recent years, Operational Business Intelligence has emerged as an important trend in the Business Intelligence (BI) market. Majority of BI application architectures are bespoke in nature which have several architectural limitations like tightly coupled, static, historic, subjective, no performance measurement of business processes, limited user access, limited analytical processing, querying and reporting features. In this article, a generic functional architecture for Operational BI systems based on software architecture principles is presented. All functional modules of the system are derived from the key features of the system and by using top down approach of software design principles. The similar functional modules are grouped into sub-systems and a set of these sub-systems constitutes overall functional architecture. The proposed architecture overcomes the limitations of traditional BI architectures.
Стилі APA, Harvard, Vancouver, ISO та ін.
2

Carson, Ronald S. "Differentiating System Architectures: Applying Architecture Measures." INCOSE International Symposium 25, no. 1 (October 2015): 891–902. http://dx.doi.org/10.1002/j.2334-5837.2015.00103.x.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
3

Amelia Wulan Sari Sapitri. "Perancangan Enterprise Architecture HMI Sampit Menggunakan TOGAF." Kompak :Jurnal Ilmiah Komputerisasi Akuntansi 16, no. 1 (July 1, 2023): 154–61. http://dx.doi.org/10.51903/kompak.v16i1.1080.

Повний текст джерела
Анотація:
The Islamic Student Association (HMI) is an umbrella organization with a clear model of being Indonesian and Islamic, providing a platform to train and develop leaders with honesty and quality determination, faith and responsibility. The factors that provide direction within the organization to adopt an Enterprise Architecture (EA) system are aimed at enhancing what the organization needs. Enterprise architecture or what can be called Enterprise Architecture (EA) is a description of the task in question consisting of knowledge, actions, direction from the organization and architectural performance parameters in the description of the design or plan and development of an integrated system. TOGAF (The Open Group Architecture Framework) is a framework that is widely used in creating enterprise or organizational architectures. TOGAF offers methods and tools for creating, running, implementing, and maintaining enterprise architectures in existing systems. The results of this study are in the form of a blueprint that is expected to be useful for organizations as material to assist IT development in HMI.
Стилі APA, Harvard, Vancouver, ISO та ін.
4

Anyanhun, Awele, Clarissa Fleming, and Whit Matteson. "A Systematic and Traceable MOSA Evaluation Process for Systems Architectures: A Digital Engineering Tool." INCOSE International Symposium 33, no. 1 (July 2023): 1075–90. http://dx.doi.org/10.1002/iis2.13071.

Повний текст джерела
Анотація:
AbstractA process for evaluating the degree to which an architecture embraces Modular Open Systems Approaches (MOSA) is germane to ensuring that MOSA principles are actually used in the development of defense systems architectures. Furthermore, such a process provides artifacts that can be used by program offices to justify their key architectural decisions and prove they embrace MOSA as required. Therefore, an approach which facilitates the assessment of architecture requirements for MOSA compliance—rather than system designs or products—provides the added benefit of ensuring applicable MOSA quality attributes are incorporated into architectures during the requirements development phase. To this end, a systematic and traceable MOSA evaluation process which uses derived sets of evaluable criteria to evaluate architecture requirements is developed. The process utilizes a digital engineering approach to establish, within the authoritative source of truth (model), traceability relationships that can be queried, analyzed, and used to validate whether the architecture and resultant system will exhibit modularity and openness characteristics.
Стилі APA, Harvard, Vancouver, ISO та ін.
5

Su, Hong Zhi. "Systems Scientific Analysis of Architecture Adaptability Design." Applied Mechanics and Materials 744-746 (March 2015): 2165–70. http://dx.doi.org/10.4028/www.scientific.net/amm.744-746.2165.

Повний текст джерела
Анотація:
Architecture is the arena on which man's life unfolds, due to the constant changes taking place in life, deformability is demanded to increase the adaptability of modern Architecture. Thus, to achieve such deformability, research on the systematic hierarchy of architectures is carried out; indicating that the hierarchies are the intermediary of the inner transformation of the architecture and the formation process of architecture system is a process of gradual differentiation. With the development of the gradual differentiation process, the flexibility of architecture begins to fail while increasing its determinacy. The key point determining the adaptability of architectures lies in the inter-transformation between the various levels of sub-hierarchy systems. According to the complexity and hierarchy of the transformation, categorization and analysis with future study on the performance manifestation of architectural adaptability design are implemented.
Стилі APA, Harvard, Vancouver, ISO та ін.
6

Chen, Hualong, Yuanqiao Wen, Man Zhu, Yamin Huang, Changshi Xiao, Tao Wei, and Axel Hahn. "From Automation System to Autonomous System: An Architecture Perspective." Journal of Marine Science and Engineering 9, no. 6 (June 10, 2021): 645. http://dx.doi.org/10.3390/jmse9060645.

Повний текст джерела
Анотація:
Autonomy is the core capability of future systems, and architecture design is one of the critical issues in system development and implementation. To discuss the architecture of autonomous systems in the future, this paper reviews the developing progress of architectures from automation systems to autonomous systems. Firstly, the autonomy and autonomous systems in different fields are summarized. The article classifies and summarizes the architecture of typical automated systems and infer three suggestions for building an autonomous system architecture: extensibility, evolvability, and collaborability. Accordingly, this paper builds an autonomous waterborne transportation system, and the architecture is composed of the object layer, cyberspace layer, cognition layer, and application layer, the proposed suggestions made in the construction of the architecture are reflected in the inter-relationships at all layers. Through the cooperation of four layers, the autonomous waterborne transportation system can autonomously complete the system functions, such as system control and transportation service. In the end, the characteristics of autonomous systems are concluded, from which the future primary research directions and the challenges of autonomous systems are provided.
Стилі APA, Harvard, Vancouver, ISO та ін.
7

Rodríguez, Daniel A., and Joseph M. Sussman. "Framework for Developing a Regional System Architecture for Intelligent Transportation Systems." Transportation Research Record: Journal of the Transportation Research Board 1588, no. 1 (January 1997): 77–85. http://dx.doi.org/10.3141/1588-10.

Повний текст джерела
Анотація:
Defining an architecture for intelligent transportation systems (ITS) at the regional level, where most ITS deployment occurs, is constrained by jurisdictional, institutional, financial, political, and regulatory factors. These constraints provide opportunities for the architecture that go beyond its traditional role as a guiding tool for technology implementation to a newer role of reorienting institutional relationships. An architecture development approach is proposed that considers regional transportation needs and characteristics so as to increase the benefits from implementing ITS locally. It also provides a new way of thinking about the importance of the National ITS System Architecture in the context of regional ITS deployments. The development approach was tested by considering how regional architectures in New York, Boston, and Houston address regional needs. Findings and implications of the regional ITS architectures of the case study areas are presented.
Стилі APA, Harvard, Vancouver, ISO та ін.
8

Khumaidi, Ahmad, and Eka Ridhawati. "DEVELOPMENT OF INFORMATION SYSTEM STRATEGIES AND INFORMATION TECHNOLOGY AT PRIVATE UNIVERSITIES IN PRINGSEWU BY USING METHODOLOGY ENTERPRISE ARCHITECTURE PLANNING (EAP)." IJISCS (International Journal of Information System and Computer Science) 1, no. 2 (August 15, 2017): 38. http://dx.doi.org/10.56327/ijiscs.v1i2.503.

Повний текст джерела
Анотація:
The development of information systems and information technology requires planning to complement the direction of the college strategy. Planning is constructed by defining data, application and technology architectures in the use of information to support business processes and then architectural design to identify needs and create architectural schemes and make plans for their implementation. Enterprise Architecture Planning (EAP) is a method of data quality planning approach oriented to business needs and how the implementation of the architecture is done in such a way in an effort to support business turnover and achievement of Vision and Mission and the goal of strategic development of SI and IT at college private high. The result of this research is to get the blueprint resulting from Enterprise Architecture Planning (EAP) methodology which will be used as a guide for making blueprint in the form of data architecture, application architecture and technology architecture in strategy development Information system and information technology as a whole on High private sector especially in Pringsewu
Стилі APA, Harvard, Vancouver, ISO та ін.
9

Gradel, Simon, Benedikt Aigner, and Eike Stumpf. "Model-based safety assessment for conceptual aircraft systems design." CEAS Aeronautical Journal 13, no. 1 (November 23, 2021): 281–94. http://dx.doi.org/10.1007/s13272-021-00562-2.

Повний текст джерела
Анотація:
AbstractTraditional system technology modeling in conceptual aircraft design mainly relies on empirical knowledge and methods derived from conventional systems, for which valid system architecture designs are known. Since these systems have been proven valid especially from a safety perspective, detailed system safety analyses are usually not necessary. For unconventional systems and innovative technologies, on contrary, new architectures have to be designed and system safety has, therefore, to be taken into account. Therefore, the application of model-based safety assessment (MBSA) for designing system architectures in conceptual aircraft design studies is proposed. A MBSA approach based on a Simulink architecture model is presented which is tailored for use in conceptual design studies. It is applied to the cryocooling system of a hybrid-electric powertrain architecture from an already-published study. The original architecture as well as possible architecture alternatives are investigated. As a result, a safer architecture version with lower number of components can be proposed. The application example indicates that using MBSA in conceptual design benefits the latter by providing insights into safety properties of the system and by pointing out architecture safety weaknesses. This could result in safer, thus more realistic system architectures.
Стилі APA, Harvard, Vancouver, ISO та ін.
10

Rasul, Hoshyar Qadir. "Architecture as system: A study of housing systems evolution." Kurdistan Journal of Applied Research 1, no. 1 (March 1, 2016): 21–34. http://dx.doi.org/10.24017/science.2016.1.1.1.

Повний текст джерела
Анотація:
Understanding architecture via the concept of system came after numerous, rapid and different developments upon all aspects of architecture, especially since the last third of past century till the present day.Some theories characterized architecture as the complex whole that based on the different relationships and interrelationships with different sciences, besides of the multiplicity and independency of internal components, it should be assigned into the world of integrated system.This study attempts to explain the phenomenon of architecture through the concept of (system), in order to include both its cognitive (the subject) - which is potential, and realistic presence (the object) -which is explicit. This study tries to explore both sides of the concept, in order to understand the architectural system -in one hand and determining its components -in the other hand.To find out how these systems which have been developed via some housing projects, as an integrated system; comprised by secondary sub-systems with clear limits, within the total system of the housing project. This study follows the inductive and descriptive approach as a methodology, depending on the related literatures and applied available theories in residential projects during different periods of time.The study aims to identify the systems and levels, set to reach a comprehensive understanding of the architectural system in general, and the evolutions of housing systems, in particular, benefiting from the rapid developments of this architectural style (Housing), which have been seen in many various levels too.
Стилі APA, Harvard, Vancouver, ISO та ін.

Дисертації з теми "System architecture"

1

Iacobucci, Joseph Vincent. "Rapid Architecture Alternative Modeling (RAAM): a framework for capability-based analysis of system of systems architectures." Diss., Georgia Institute of Technology, 2012. http://hdl.handle.net/1853/43697.

Повний текст джерела
Анотація:
The current national security environment and fiscal tightening make it necessary for the Department of Defense to transition away from a threat based acquisition mindset towards a capability based approach to acquire portfolios of systems. This requires that groups of interdependent systems must regularly interact and work together as systems of systems to deliver desired capabilities. Technological advances, especially in the areas of electronics, computing, and communications also means that these systems of systems are tightly integrated and more complex to acquire, operate, and manage. In response to this, the Department of Defense has turned to system architecting principles along with capability based analysis. However, because of the diversity of the systems, technologies, and organizations involved in creating a system of systems, the design space of architecture alternatives is discrete and highly non-linear. The design space is also very large due to the hundreds of systems that can be used, the numerous variations in the way systems can be employed and operated, and also the thousands of tasks that are often required to fulfill a capability. This makes it very difficult to fully explore the design space. As a result, capability based analysis of system of systems architectures often only considers a small number of alternatives. This places a severe limitation on the development of capabilities that are necessary to address the needs of the war fighter. The research objective for this manuscript is to develop a Rapid Architecture Alternative Modeling (RAAM) methodology to enable traceable Pre-Milestone A decision making during the conceptual phase of design of a system of systems. Rather than following current trends that place an emphasis on adding more analysis which tends to increase the complexity of the decision making problem, RAAM improves on current methods by reducing both runtime and model creation complexity. RAAM draws upon principles from computer science, system architecting, and domain specific languages to enable the automatic generation and evaluation of architecture alternatives. For example, both mission dependent and mission independent metrics are considered. Mission dependent metrics are determined by the performance of systems accomplishing a task, such as Probability of Success. In contrast, mission independent metrics, such as acquisition cost, are solely determined and influenced by the other systems in the portfolio. RAAM also leverages advances in parallel computing to significantly reduce runtime by defining executable models that are readily amendable to parallelization. This allows the use of cloud computing infrastructures such as Amazon's Elastic Compute Cloud and the PASTEC cluster operated by the Georgia Institute of Technology Research Institute (GTRI). Also, the amount of data that can be generated when fully exploring the design space can quickly exceed the typical capacity of computational resources at the analyst's disposal. To counter this, specific algorithms and techniques are employed. Streaming algorithms and recursive architecture alternative evaluation algorithms are used that reduce computer memory requirements. Lastly, a domain specific language is created to provide a reduction in the computational time of executing the system of systems models. A domain specific language is a small, usually declarative language that offers expressive power focused on a particular problem domain by establishing an effective means to communicate the semantics from the RAAM framework. These techniques make it possible to include diverse multi-metric models within the RAAM framework in addition to system and operational level trades. A canonical example was used to explore the uses of the methodology. The canonical example contains all of the features of a full system of systems architecture analysis study but uses fewer tasks and systems. Using RAAM with the canonical example it was possible to consider both system and operational level trades in the same analysis. Once the methodology had been tested with the canonical example, a Suppression of Enemy Air Defenses (SEAD) capability model was developed. Due to the sensitive nature of analyses on that subject, notional data was developed. The notional data has similar trends and properties to realistic Suppression of Enemy Air Defenses data. RAAM was shown to be traceable and provided a mechanism for a unified treatment of a variety of metrics. The SEAD capability model demonstrated lower computer runtimes and reduced model creation complexity as compared to methods currently in use. To determine the usefulness of the implementation of the methodology on current computing hardware, RAAM was tested with system of system architecture studies of different sizes. This was necessary since system of systems may be called upon to accomplish thousands of tasks. It has been clearly demonstrated that RAAM is able to enumerate and evaluate the types of large, complex design spaces usually encountered in capability based design, oftentimes providing the ability to efficiently search the entire decision space. The core algorithms for generation and evaluation of alternatives scale linearly with expected problem sizes. The SEAD capability model outputs prompted the discovery a new issue, the data storage and manipulation requirements for an analysis. Two strategies were developed to counter large data sizes, the use of portfolio views and top `n' analysis. This proved the usefulness of the RAAM framework and methodology during Pre-Milestone A capability based analysis.
Стилі APA, Harvard, Vancouver, ISO та ін.
2

Keller, James (James Thomas). "System architecture of offshore oil production systems." Thesis, Massachusetts Institute of Technology, 2008. http://hdl.handle.net/1721.1/45220.

Повний текст джерела
Анотація:
Thesis (S.M.)--Massachusetts Institute of Technology, Dept. of Aeronautics and Astronautics, 2008.
Includes bibliographical references (p. 117-118).
This thesis presents an approach to applying Systems Architecture methods to the development of large, complex, commercial systems, particularly offshore oil and gas productions systems. The aim of this research was to assist BP in the development of concepts for a multi-billion dollar oil production system, particularly in the unprecedented deep water arctic locations prone to seismic activity, as well as in existing fields that must be extended. The thesis demonstrates that these systems can be decomposed and analyzed using rigorous, methodical system architecture thinking that archives and represents tacit knowledge in several graphical frameworks. The thesis breaks the architecture of oil and gas production systems into two problems. The first problem is the architecture of one facility and one reservoir; a classic problem of assigning function to form. The second problem is the architecture of multiple facilities and multiple reservoirs; a classic problem of connection and routing. For the first problem, the production process is decomposed using Object Process Methodology (OPM). The decompositions provide a methodology to capture industry knowledge that is not always explicitly stated and provides a framework to explore the entire architectural design space. The thesis then describes how these decompositions of general and specific oil systems can be used to develop software models, using the meta-language tool OPN (Object Process Network), that successfully generate thousands of architecture concepts. This set of feasible architectures can be prioritized and better understood using metrics in an effort to down-select to a handful of preferred concepts to be carried forward for more detailed study and eventual development.
(cont.) The approach to the second problem demonstrates that even a modest set of facilities and reservoirs have a huge number of connection possibilities. This space of connection possibilities is large and daunting, and typically is not fully explored. To solve the second problem the thesis presents two models that generate all the possible connection schemes between elements in a system, in this case oil facilities and reservoirs. It is then demonstrated that these possibilities can be prioritized through the use of metrics. The thesis presents a method that can identify new concepts, highlight preferred sets of concepts, and underline patterns common to those concepts. This method increases the architects' overall knowledge and understanding of the entire space of possibilities, and ensures that all options are considered in the development of complex systems.
by James Keller.
S.M.
Стилі APA, Harvard, Vancouver, ISO та ін.
3

Siridhara, Siradol. "AHS Maglev System Architecture." Diss., Virginia Tech, 1999. http://hdl.handle.net/10919/29219.

Повний текст джерела
Анотація:
In the period between 1993-1998 a vision was presented of an Automated Highway System developed under a contract naming Virginia Tech one of the three ITS Research Centers of Excellence in the United States by the Federal Highway Administration. The AHS envisioned would consist of a guideway constructed in the rights-of-way of the Interstate Highway System which would utilized magnetic levitation ("maglev") to propel closely-space, individual vehicles at high speeds with full longitudinal and lateral control. In this dissertation the system architecture is described in detail. The system architecture is organized according to system structural, system operational, and vehicle subsystem technological elements. The structural aspects are concerned with the decision making capability allocated between a vehicle and the guideway, the characteristics of the control and sensing equipment contained within the guideway, the traveling unit configuration, and certain of the vehicle's structural and equipment considerations. The operational aspects are concerned with vehicle entrainment policy, system fleet mixture, network type and control functions, and guideway lane separation requirements. The vehicle subsystem and the vehicle longitudinal and lateral control subsystem. The operational architecture concentrates on developing and evaluating strategies for forming platoons of vehicles on the guideway since the average platoon sizes determine the practical capacity of the guideway as well as the safety of operation. It is instructive to review how platoons form naturally on conventional highways as a prelude to developing a strategy for forming platoon on the AHS Maglev Guideway. A novel, non-linear car-following model called "car maneuvering" is explored by defining the stimuli on the right-hand side of the model in terms of several vehicles ahead of the response vehicle. In order to add still more realism in developing a strategy for platoon formation in a guideway under automatic control, an additional spacing dependent term is introduced to achieve a "magnetic coupling headway" between platooned vehicles. Once vehicles are magnetically coupled, the desired intraplatoon headway is maintained through attraction and repulsion. In this dissertation the term "architecture" is interpreted in the broadest possible sense based on the assumption that any transportation system intended to serve society throughout the 21st Century and beyond must address a hierarchy of goals and issues ranging from the strategic (sustainable development) to the tactical (the concept of operations) and including the in-between (interfacing with the existing transportation system). In the past, transportation planning, policy, investment and operating decisions have been made in isolation from each other with incomplete information inputs from a broad base of disciplines and sectors, without a synthesizing instrumentality. A new approach is described to promote the best informed decisions governing planning and management. The approach features a realistic framework for allocating public sector-private sector effort, an instrumentality for generating the knowledge needed to conceive and implement the new transportation paradigm, and a strategic vision for rallying support. The new approach to the problem begins with a strategic vision for society's AHS infrastructure. We believe that the strategic vision must be based on the concept of "sustainable development." To affect this new strategic vision, higher budgets will be a necessary, but not a sufficient condition. A fundamental Decision Support System (DSS) with knowledge bases with contributions from the braid spectrum of science and engineering disciplines, and a methodology based on system dynamics capable of synthesizing these contributions is proposed. The AHS Maglev Alternative is compared to a "Do-Nothing" Alternative and a "Traditional Expansion" Alternative using user and nonuser benefit analyses. The advantages of AHS Maglev are seen to be overwhelming. Moreover, the ability of AHS Maglev to alleviate airport congestion by reducing short and medium range of flights, and to serve as a structuring device for rational population distribution is shown.
Ph. D.
Стилі APA, Harvard, Vancouver, ISO та ін.
4

Rixner, Scott. "Memory system architecture for real-time multitasking systems." Thesis, Massachusetts Institute of Technology, 1995. http://hdl.handle.net/1721.1/36599.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
5

Siddapureddy, Venu R. 1969. "Evolvable system architecture : design issues of learning systems." Thesis, Massachusetts Institute of Technology, 2002. http://hdl.handle.net/1721.1/92076.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
6

Ho, Teresa Tak-Sum. "System architecture for Internet-based teleoperation system." Thesis, National Library of Canada = Bibliothèque nationale du Canada, 1999. http://www.collectionscanada.ca/obj/s4/f2/dsk1/tape7/PQDD_0015/MQ47040.pdf.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
7

Hedfors, Sara. "Architecture for Diagnostic Platform." Thesis, Uppsala University, Department of Information Technology, 2010. http://urn.kb.se/resolve?urn=urn:nbn:se:uu:diva-126685.

Повний текст джерела
Анотація:

In order to maximize operating time of an industrial machine and minimize stand-by time, service time and operating costs, a diagnostic system can be a useful tool. Diagnostic systems employ information already available in a machine’s control system (such as control signals, system state, sensor readings and so forth) to perform intelligent fault detection and localisation, and predict future faults and service needs.

CC Systems develops advanced electronics and control systems for industrial machines and vehicles operating in rough environments. One of their products is a diagnostic platform called Diagnostic Runtime Engine (DRE), supplying the customer with a tool for building a diagnostic system. The platform offers supervision of the control system. Actions are performed when it detects a possible fault or indication of a potential future fault. An action could be for example the creation of an alarm.

The DRE, as designed today, only works together with a control system running in an environment called CoDeSys. In this master thesis a new architecture of the platform is presented, with the objective to make the platform compatible with an arbitrary control system. A prototype is implemented to prove the concept of the suggested architecture model. A number of different standard diagnostic blocks, used for building the diagnostic system, are also suggested with the objective to make it easier for the user to employ the DRE. A proposition of how development with the diagnostic platform can proceed beyond this thesis is also presented.


För att maximera drifttid hos en industriell maskin och minimera driftskostnader samt standby- och service-tid, kan ett diagnostiksystem användas. Ett sådant system använder sig av information som redan finns tillgänglig i maskinens styrsystem (så som styrsignaler, tillstånd, sensorvärden och så vidare) för att utföra feldetektering och fellokalisering samt analys av möjliga framtida feltillstånd och servicebehov.

CC Systems utvecklar avancerade elektronikkomponenter och styrsystem för industriella maskiner och fordon. En av deras produkter är en diagnostikplattform, Diagnostic Runtime Engine (DRE), som erbjuder ett verktyg för att bygga upp ett diagnostiksystem. Plattformen möjliggör övervakning av styrsystemet, och detektion av ett nuvarande feltillstånd eller möjligt framtida feltillstånd leder till att en handling utförs. En handling kan till exempel vara att ett alarm skapas.

Diagnostikplattformen, som den är gjord idag, fungerar bara tillsammans med ett styrsystem som är implementerat i utvecklingsmiljön CoDeSys. I detta examensarbete presenteras en ny arkitektur på plattformen som möjliggör användande tillsammans med ett godtyckligt styrsystem. En prototyp är implementerad för att visa att den föreslagna arkitekturmodellen fungerar i praktiken. Dessutom är ett antal standard-diagnostikblock, som används då ett diagnostiksystem byggs upp, föreslagna. Standardblocken har till syfte att underlätta användandet av diagnostikplattformen. Ett förslag för hur DRE kan byggas om och utvecklas i framtiden är också presenterat.

Стилі APA, Harvard, Vancouver, ISO та ін.
8

Shames, Peter, and Takahiro Yamada. "REFERENCE ARCHITECTURE FOR SPACE DATA SYSTEMS." International Foundation for Telemetering, 2003. http://hdl.handle.net/10150/605587.

Повний текст джерела
Анотація:
International Telemetering Conference Proceedings / October 20-23, 2003 / Riviera Hotel and Convention Center, Las Vegas, Nevada
This paper introduces the Reference Architecture for Space Data Systems (RASDS) that is being developed by CCSDS. RASDS uses five Views to describe architectures of space data systems. These Views are derived from the viewpoints of the Reference Model of Open Distributed Processing (RM-ODP), but they are slightly modified from the RM-ODP viewpoints so that they can better represent the concerns of space data systems.
Стилі APA, Harvard, Vancouver, ISO та ін.
9

Stottlemyer, Alan R., and Kevin M. Hassett. "Open Systems Architecture in a COTS environment." International Foundation for Telemetering, 1996. http://hdl.handle.net/10150/608368.

Повний текст джерела
Анотація:
International Telemetering Conference Proceedings / October 28-31, 1996 / Town and Country Hotel and Convention Center, San Diego, California
A distributed architecture framework has been developed for NASA at Goddard Space Flight Center (GSFC) as the basis for developing an extended series of space mission support data systems. The architecture is designed to include both mission development and operations. It specifically addresses the problems of standardizing a framework for which commercial off-the-shelf (COTS) applications and infrastructure are expected to provide most of the components of the systems. The resulting distributed architecture is developed based on a combination of a layered architecture, and carefully selected open standards. The layering provides the needed flexibility in mission design to support the wide variability of mission requirements. The standards are selected to address the most important interfaces, while not over constraining the implementation options.
Стилі APA, Harvard, Vancouver, ISO та ін.
10

Boosabaduge, Prasad Priyadarshana Fernando. "Hybrid Recommender System Architecture for Personalized Wellness Management." University of Akron / OhioLINK, 2016. http://rave.ohiolink.edu/etdc/view?acc_num=akron1457107427.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.

Книги з теми "System architecture"

1

Paul, Wolfgang J., Christoph Baumann, Petro Lutsyk, and Sabine Schmaltz. System Architecture. Cham: Springer International Publishing, 2016. http://dx.doi.org/10.1007/978-3-319-43065-2.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
2

Network system architecture. Reading, Mass: Addison-Wesley Pub. Co., 1990.

Знайти повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
3

System architecture and system design. New York, N.Y: McGraw-Hill, 1989.

Знайти повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
4

1953-, Anderson Don, Shanley Tom, and MindShare Inc, eds. ISA system architecture. Reading, Mass: Addison-Wesley Pub. Co., 1995.

Знайти повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
5

Shanley, Tom. EISA system architecture. 2nd ed. Richardson, TX: MindShare Press, 1993.

Знайти повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
6

Tom, Shanley, and MindShare Inc, eds. AGP system architecture. Reading, Mass: Addison Wesley, 1999.

Знайти повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
7

Muttoo, Sunil Kumar, ed. System and Architecture. Singapore: Springer Singapore, 2018. http://dx.doi.org/10.1007/978-981-10-8533-8.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
8

Shanley, Tom. PCI system architecture. 3rd ed. Reading, Mass: Addison-Wesley, 1995.

Знайти повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
9

Don, Anderson, ed. ISA system architecture. 2nd ed. Richardson, TX: MindShare Press, 1993.

Знайти повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
10

M, Rueger E., ed. Telemetry system architecture. 3rd ed. Research Triangle Park, N.C., USA: International Society of America, 1995.

Знайти повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.

Частини книг з теми "System architecture"

1

Efstathiou, Dimitrios, Mahboubeh Lohi, Dilshan Weerakoon, and A. H. Aghvami. "System Architecture." In Third Generation Mobile Telecommunication Systems, 317–85. Berlin, Heidelberg: Springer Berlin Heidelberg, 2001. http://dx.doi.org/10.1007/978-3-642-56919-7_6.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
2

Mahnke, Wolfgang, and Stefan-Helmut Leitner. "System Architecture." In OPC Unified Architecture, 265–82. Berlin, Heidelberg: Springer Berlin Heidelberg, 2009. http://dx.doi.org/10.1007/978-3-540-68899-0_9.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
3

Tinnefeld, Christian. "System Architecture." In Building a Columnar Database on RAMCloud, 45–51. Cham: Springer International Publishing, 2015. http://dx.doi.org/10.1007/978-3-319-20711-7_3.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
4

Hoppe, Jirka. "System Architecture." In Integrated Management of Technical Documentation, 74–83. Berlin, Heidelberg: Springer Berlin Heidelberg, 1992. http://dx.doi.org/10.1007/978-3-642-84840-7_6.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
5

Hey, Stefan, Panagiota Anastasopoulou, André Bideaux, Christos P. Antonopoulos, Nikolaos S. Voros, Alberto Fernandez, Vasilis Megalooikonomou, and Arthur Krukowski. "System Architecture." In Cyberphysical Systems for Epilepsy and Related Brain Disorders, 127–36. Cham: Springer International Publishing, 2015. http://dx.doi.org/10.1007/978-3-319-20049-1_7.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
6

Weik, Martin H. "system architecture." In Computer Science and Communications Dictionary, 1716. Boston, MA: Springer US, 2000. http://dx.doi.org/10.1007/1-4020-0613-6_18848.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
7

Meier, Andreas, and Michael Kaufmann. "System Architecture." In SQL & NoSQL Databases, 143–67. Wiesbaden: Springer Fachmedien Wiesbaden, 2019. http://dx.doi.org/10.1007/978-3-658-24549-8_5.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
8

Tawalbeh, Lo’ai. "System Architecture." In The NICE Cyber Security Framework, 195–206. Cham: Springer International Publishing, 2020. http://dx.doi.org/10.1007/978-3-030-41987-5_9.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
9

Silva, António Daniel, Rui Ferreira Neves, and Nuno Horta. "System Architecture." In SpringerBriefs in Applied Sciences and Technology, 39–56. Cham: Springer International Publishing, 2016. http://dx.doi.org/10.1007/978-3-319-29392-9_3.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
10

Smith, James E. "System Architecture." In Space-Time Computing with Temporal Neural Networks, 143–64. Cham: Springer International Publishing, 2017. http://dx.doi.org/10.1007/978-3-031-01754-4_7.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.

Тези доповідей конференцій з теми "System architecture"

1

Westermann, Thorsten, Harald Anacker, Roman Dumitrescu, Ursula Frank, and Axel Hessenkämper. "Interdisciplinary System Architecture for Intelligent Technical Systems." In ASME 2015 International Mechanical Engineering Congress and Exposition. American Society of Mechanical Engineers, 2015. http://dx.doi.org/10.1115/imece2015-50579.

Повний текст джерела
Анотація:
Nowadays, mechanical engineering products change from mechatronic products, characterized by the close interplay of mechanics, electronics, control and software engineering to Intelligent Technical Systems (ITS). Intelligent Technical Systems are mechatronic systems with inherent partial intelligence. Mechanical engineering products will be a symbiosis of information technology and mechanical parts. This will entail a rising complexity of technical systems and its development. Therefore we introduce an approach to improve system architectures of mechanical engineering products to realize Intelligent Technical Systems. Our approach meets the following challenges: creating a domain-spanning description of the system with Model-Based Systems Engineering (MBSE); designing an interdisciplinary and modular system architecture by using the technological concept of Intelligent Technical Systems; identifying and implementing solution elements as reusable modules. Validated by a separator, our results clarify the benefits of MBSE and the technological concept of ITS to improve system architectures of mechanical engineering products to realize Intelligent Technical Systems.
Стилі APA, Harvard, Vancouver, ISO та ін.
2

Richards, Matthew G., Daniel E. Hastings, Adam M. Ross, and Donna H. Rhodes. "Design Principles for Survivable System Architecture." In 2007 1st Annual IEEE Systems Conference. IEEE, 2007. http://dx.doi.org/10.1109/systems.2007.374645.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
3

Uchitel, Sebastian, Robert Chatley, Jeff Kramer, and Jeff Magee. "System architecture." In the 12th ACM SIGSOFT twelfth international symposium. New York, New York, USA: ACM Press, 2004. http://dx.doi.org/10.1145/1029894.1029903.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
4

White, Samantha, and Scott Ferguson. "Exploring Architecture Selection and System Evolvability." In ASME 2017 International Design Engineering Technical Conferences and Computers and Information in Engineering Conference. American Society of Mechanical Engineers, 2017. http://dx.doi.org/10.1115/detc2017-68290.

Повний текст джерела
Анотація:
For engineered systems, one of the first decisions a designer must make is the architecture that will solve the established high level function. In most cases, this can be accomplished in a multitude of ways, with each original architecture having strengths and weaknesses. This paper explores how the architecture choice for a system impacts the ability to evolve and meet future needs. The lessons learned from this paper are extracted from a case study where three systems that perform the same task via different architectural solutions are considered. These systems are them compared to understand how well they adhere to, or violate, the Empirically-Derived Principles for Designing Products with Flexibility for Future Evolution introduced by Tilstra et al.
Стилі APA, Harvard, Vancouver, ISO та ін.
5

Acheson, Paulette. "Methodology for object-oriented system architecture development." In 2010 4th Annual IEEE Systems Conference. IEEE, 2010. http://dx.doi.org/10.1109/systems.2010.5729856.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
6

Cavalcante, Everton, and Thais Batista. "Using Software Architecture Descriptions to Detect Architectural Smells at Design Time." In Congresso Ibero-Americano em Engenharia de Software. Sociedade Brasileira de Computação, 2023. http://dx.doi.org/10.5753/cibse.2023.24697.

Повний текст джерела
Анотація:
Architectural smells are decisions made at the software architecture level, whether intentional or not, that may negatively impact the quality of a software system. In the literature, architectural smells are identified mainly by relying on the source code or other implementation artifacts. However, architectural smells could be detected at design time, even before employing implementation efforts and preventing them from being reflected at the system implementation. This research investigates how software architecture descriptions realized through architecture description languages (ADLs) can be used to identify architectural smells at design time. This work focuses on how architectural smells manifest and can be detected in SysADL, an ADL that allows describing both structure and behavior of software architectures using standardized diagrams from the OMG’s SysML language.
Стилі APA, Harvard, Vancouver, ISO та ін.
7

Bone, Mary A., Robert Cloutier, Peter Korfiatis, and Anne Carrigy. "System architecture: Complexities role in architecture entropy." In 2010 5th International Conference on System of Systems Engineering (SoSE). IEEE, 2010. http://dx.doi.org/10.1109/sysose.2010.5544089.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
8

Bossom, R. "Developing architectures and systems from the European ITS framework architecture." In IEE Seminar ITS System Architecture. IEE, 2000. http://dx.doi.org/10.1049/ic:20000605.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
9

Boxer, Philip J., and Suzanne Garcia. "Enterprise architecture for complex system-of-systems contexts." In 2009 3rd Annual IEEE Systems Conference. IEEE, 2009. http://dx.doi.org/10.1109/systems.2009.4815807.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
10

Sinha, Kaushik, and Olivier L. de Weck. "Structural Complexity Quantification for Engineered Complex Systems and Implications on System Architecture and Design." In ASME 2013 International Design Engineering Technical Conferences and Computers and Information in Engineering Conference. American Society of Mechanical Engineers, 2013. http://dx.doi.org/10.1115/detc2013-12013.

Повний текст джерела
Анотація:
The complexity of today’s highly engineered products is rooted in the interwoven architecture defined by its components and their interactions. Such structures can be viewed as the adjacency matrix of the associated dependency network representing the product architecture. To evaluate a complex system or to compare it to other systems, numerical assessment of its structural complexity is essential. In this paper, we develop a quantitative measure for structural complexity and apply the same to real-world engineered systems like gas turbine engines. It is observed that low topological complexity implies centralized architectures and that higher levels of complexity generally indicate highly distributed architectures. We posit that the development cost varies non-linearly with structural complexity. Empirical evidence of such behavior is presented from the literature and preliminary results from simple experiments involving assembly of simple structures further strengthens our hypothesis. We demonstrate that structural complexity and modularity are not necessarily negatively correlated using a simple example. We further discuss distribution of complexity across the system architecture and its strategic implications for system development efforts.
Стилі APA, Harvard, Vancouver, ISO та ін.

Звіти організацій з теми "System architecture"

1

Kuchar, Olga, Swen Boehm, Thomas Naughton III, Suhas Somnath, Ben Mintz, Jack Lange, Scott {Leadership Computing} Atchley, Rohit Srivastava, and Patrick Widener. INTERSECT Architecture Specification: System-of-Systems Architecture (Version 0.9). Office of Scientific and Technical Information (OSTI), April 2024. http://dx.doi.org/10.2172/2333813.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
2

Boehm, Swen, Thomas Naughton III, Suhas Somnath, Ben Mintz, Jack Lange, Scott {Leadership Computing} Atchley, Rohit Srivastava, and Patrick Widener. INTERSECT Architecture Specification: System-of-systems Architecture (Version 0.5). Office of Scientific and Technical Information (OSTI), September 2022. http://dx.doi.org/10.2172/1968700.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
3

Harris, S. ChemTrack system architecture. Office of Scientific and Technical Information (OSTI), June 1997. http://dx.doi.org/10.2172/641116.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
4

Wood, David A., Susan J. Eggers, and Garth Gibson. SPUR Memory System Architecture. Fort Belvoir, VA: Defense Technical Information Center, January 1988. http://dx.doi.org/10.21236/ada619784.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
5

Schoonover II, Philip. LOTUS System Architecture Model. Office of Scientific and Technical Information (OSTI), September 2021. http://dx.doi.org/10.2172/1825518.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
6

Craft, Richard Layne, II. Telemedicine system interoperability architecture: concept description and architecture overview. Office of Scientific and Technical Information (OSTI), May 2004. http://dx.doi.org/10.2172/974884.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
7

Brown, Peter F., and Steven R. Ray. NBS AMRF process planning system- system architecture. Gaithersburg, MD: National Institute of Standards and Technology, 1989. http://dx.doi.org/10.6028/nist.ir.88-3828.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
8

Raychev, Nikolay. System architecture for maintenance of complex distributed systems. Web of Open Science, July 2020. http://dx.doi.org/10.37686/ser.v1i2.60.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
9

Chiarulli, Donald M., and Steven P. Levitan. Optoelectronic Cache Memory System Architecture. Fort Belvoir, VA: Defense Technical Information Center, December 1999. http://dx.doi.org/10.21236/ada371774.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
10

Viebeck, P. G. System design document U-AVLIS control system architecture. Office of Scientific and Technical Information (OSTI), February 1994. http://dx.doi.org/10.2172/10176047.

Повний текст джерела
Стилі APA, Harvard, Vancouver, ISO та ін.
Ми пропонуємо знижки на всі преміум-плани для авторів, чиї праці увійшли до тематичних добірок літератури. Зв'яжіться з нами, щоб отримати унікальний промокод!

До бібліографії