Relevant bibliographies by topics / Component architecture

Contents

  1. Journal articles
  2. Dissertations / Theses
  3. Books
  4. Book chapters
  5. Conference papers
  6. Reports

Academic literature on the topic 'Component architecture'

Author: Grafiati
Published: 4 June 2021
Last updated: 11 February 2022

Create a spot-on reference in APA, MLA, Chicago, Harvard, and other styles

Select a source type:

Consult the lists of relevant articles, books, theses, conference reports, and other scholarly sources on the topic 'Component architecture.'

Next to every source in the list of references, there is an 'Add to bibliography' button. Press on it, and we will generate automatically the bibliographic reference to the chosen work in the citation style you need: APA, MLA, Harvard, Chicago, Vancouver, etc.

You can also download the full text of the academic publication as pdf and read online its abstract whenever available in the metadata.

Journal articles on the topic "Component architecture"

1

Medvidovic, Nenad, Eric M. Dashofy, and Richard N. Taylor. "The Role of Middleware in Architecture-Based Software Development." International Journal of Software Engineering and Knowledge Engineering 13, no. 04 (August 2003): 367–93. http://dx.doi.org/10.1142/s0218194003001330.

Full text
Abstract:
Software architectures promote development focused on modular functional building blocks (components), their interconnections (configurations), and their interactions (connectors). Since architecture-level components often contain complex functionality, it is reasonable to expect that their interactions will be complex as well. Middleware technologies such as CORBA, COM, and RMI provide a set of predefined services for enabling component composition and interaction. However, the potential role of such services in the implementations of software architectures is not well understood. In practice, middleware can resolve various types of component heterogeneity — across platform and language boundaries, for instance — but also can induce unwanted architectural constraints on application development. We present an approach in which components communicate through architecture-level software connectors that are implemented using middleware. This approach preserves the properties of the architecture-level connectors while leveraging the beneficial capabilities of the underlying middleware. We have implemented this approach in the context of a component- and message-based architectural style called C2 and demonstrated its utility in the context of several diverse applications. We argue that our approach provides a systematic and reasonable way to bridge the gap between architecture-level connectors and implementation-level middleware packages.
APA, Harvard, Vancouver, ISO, and other styles
2

Mišovič, Milan, and Oldřich Faldík. "Applying of component system development in object methodology." Acta Universitatis Agriculturae et Silviculturae Mendelianae Brunensis 61, no. 7 (2013): 2515–22. http://dx.doi.org/10.11118/actaun201361072515.

Full text
Abstract:
In the last three decades, the concept and implementation of component-based architectures have been promoted in software systems creation. Increasingly complex demands are placed on the software component systems, in particular relating to the dynamic properties. The emergence of such requirements has been gradually enforced by the practice of development and implementation of these systems, especially for information systems software.Just the information systems (robust IS) of different types require that target software meets their requirements. Among other things, we mean primarily the adaptive processes of different domains, high distributives due to the possibilities of the Internet 2.0, acceptance of high integrity of life domains (process, data and communications integrity), scalability, and flexible adaptation to process changes, a good context for external devices and transparent structure of the sub-process modules and architectural units.Of course, the target software of required qualities and the type robust cannot be a monolith. As commonly known, development of design toward information systems software has clearly come to the need for the software composition of completely autonomous, but cooperating architectural units that communicate with each other using messages of prescribed formats.Although for such units there were often used the so called subsystems and modules, see (Jac, Boo, Rumbo, 1998) and (Arlo, Neus, 2007), their abstraction being gradually enacted as the term component. In other words, the subsystems and modules are specific types of components.In (Král, Žeml, 2000) and (Král, Žeml, 2003) there are considered two types of target software of information systems. The first type – there are SWC (Software Components), composed of permanently available components, which are thought as services – Confederate software. The second type – SWA (Software Alliance), called semi Confederate, formed during the run-time of the software system and referred to as software alliance.In both of these mentioned publications there is delivered ​​deep philosophy of relevant issues relating to SWC / SWA as creating copies of components (cloning), the establishment and destruction of components at software run-time (dynamic reconfiguration), cooperation of autonomous components, programmable management of components interface in depending on internal components functionality and customer requirements (functionality, security, versioning).Nevertheless, even today we can meet numerous cases of SWC / SWA existence, with a highly developed architecture that is accepting vast majority of these requests. On the other hand, in the development practice of component-based systems with a dynamic architecture (i.e. architecture with dynamic reconfiguration), and finally with a mobile architecture (i.e. architecture with dynamic component mobility) confirms the inadequacy of the design methods contained in UML 2.0. It proves especially the dissertation thesis (Rych, Weis, 2008). Software Engineering currently has two different approaches to systems SWC / SWA. The first approach is known as component-oriented software development CBD (Component based Development). According to (Szyper, 2002) that is a collection of CBD methodologies that are heavily focused on the setting up and software components re-usability within the architecture. Although CBD does not show high theoretical approach, nevertheless, it is classified under the general evolution of SDP (Software Development Process), see (Sommer, 2010) as one of its two dominant directions.From a structural point of view, a software system consists of self-contained, interoperable architectural units – components based on well-defined interfaces. Classical procedural object-oriented methodologies significantly do not use the component meta-models, based on which the target component systems are formed, then. Component meta-models describe the syntax, semantics of components. They are a system of rules for components, connectors and configuration. Component meta-models for dynamic and mobile architectures also describe the concept of rules for configuration changes (rules for reconfiguration). As well-known meta-models are now considered: Wright for static architecture, SOFA and Darvin for dynamic architecture and SOFA 2.0 for mobile architecture, see (Rych, Weis, 2008).The CBD approach verbally defines the basic terms as component (primitive / composite), interface, component system, configuration, reconfiguration, logical (structural) view, process view (behavioral), static component architecture, dynamic architecture, mobile architecture (fully dynamic architecture), see (IEEE Report, 2000) and (Crnk, Chaud, 2006).The CBD approach also presents several ​​ADL languages (Architecture Description Languages) which are able to describe software architecture. The known languages ​​are integration ACME and UML (Unified Modeling Language), see (Garl, Mon, Wil, 2000) and (UNIFEM, 2005).The second approach to SWC / SWA systems is formed on SOA, but this article does not deal with it consistently.SOA is a philosophy of architecture. SOA is not a methodology for the comprehensive development of the target software. Nevertheless, SOA successfully filled the role of software design philosophy and on the other hand, also gave an important concept linking software components and their architectural units – business services. SOA understands any software as a Component System of a business service and solved life components in it. The physical implementation of components is given by a Web services platform. A certain lack of SOA is its weak link to the business processes that are a universally recognized platform for business activities and the source for the creation of enterprise services.This paper deals with a specific activity in the CBD, i.e. the integration of the concept of component-based system into an advanced procedural, object-oriented methodology (Arlo, Neust, 2007), (Kan, Müller, 2005), (​​Krutch, 2003) for problem domains with double-layer process logic. There is indicated an integration method, based on a certain meta-model (Applying of the Component system Development in object Methodology) and leading to the component system formation. The mentioned meta-model is divided into partial workflows that are located in different stages of a classic object process-based methodology. Into account there are taken the consistency of the input and output artifacts in working practices of the meta-model and mentioned object methodology. This paper focuses on static component systems that are starting to explore dynamic and mobile component systems.In addition, in the contribution the component system is understood as a specific system, for its system properties and basic terms notation being used a set and graph and system algebra.
APA, Harvard, Vancouver, ISO, and other styles
3

Hall, P. A. V. "Architecture-driven component reuse." Information and Software Technology 41, no. 14 (November 1999): 963–68. http://dx.doi.org/10.1016/s0950-5849(99)00071-3.

Full text
APA, Harvard, Vancouver, ISO, and other styles
4

Waguespack, Les, and William T. Schiano. "Component-Based is Architecture." Information Systems Management 21, no. 3 (June 2004): 53–60. http://dx.doi.org/10.1201/1078/44432.21.3.20040601/82477.8.

Full text
APA, Harvard, Vancouver, ISO, and other styles
5

Digre, T. "Business Object Component Architecture." IEEE Software 15, no. 5 (1998): 60–69. http://dx.doi.org/10.1109/52.714818.

Full text
APA, Harvard, Vancouver, ISO, and other styles
6

Imam Ya’u, Badamasi, and Muhammed Nura Yusuf. "Building Software Component Architecture Directly from User Requirements." International Journal Of Engineering And Computer Science 7, no. 02 (February 16, 2018): 23557–66. http://dx.doi.org/10.18535/ijecs/v7i2.07.

Full text
Abstract:
Building software architectures from a set of requirements has been an area of research where programmers, architects and software engineers spend a lot of time using their expertise in resolving peculiar problems of mapping requirements to architectures. Some of these problems are directly associated with the ambiguity, incompleteness and inconsistency of requirements which draw a wide gap between the informal and formal specification of these requirements. The main objective here is to reconcile the mismatch in-between these domains by providing a systematic mapping technique. This paper presents a tool from which requirements are read from user in natural language or file and generated into words whereby the user makes some selections and maps the selected words directly to components architecture. Based on the design of this tool, human heuristic is used in the selection of the words. Unlike components, connectors are set as static. Partial architecture of requirements is drawn incrementally until complete system architecture is constructed
APA, Harvard, Vancouver, ISO, and other styles
7

Mohana Roopa, Y., M. Ramesh Babu, Jetti Kumar, and D. Kishore Babu. "Optimal component architecture using particle swarm optimization algorithm for self-adaptive software architecture." International Journal of Engineering & Technology 7, no. 1.6 (June 1, 2018): 23. http://dx.doi.org/10.14419/ijet.v7i1.6.11387.

Full text
Abstract:
The component-based software engineering (CBSE) ensue the procedure of reconfiguration and reusability of components to reap the higher productivity. The context-aware structures are portion of CBSE, which observes the functionality of the system and adopt automatically according to the execution context. In this paper, we are focusing on the aware context guidelines that automatically adapt to the given context given by the customers and remodel the software architecture based totally on the requirements. The component repository turned into added, in which it carries the wide variety of reusable components. The fuzzy logic becomes carried out to the component evaluation in the component repository. The Particle Swarm Optimization (PSO) algorithm applied, to optimize component architecture. The Hospital management system is used to test the adaptability of the system.
APA, Harvard, Vancouver, ISO, and other styles
8

ORLANDIC, RATKO, and JOHN L. PFALTZ. "PREVENTING MISMATCH OF HOMOGENEOUS COMPONENTS IN THE DESIGN OF SOFTWARE ARCHITECTURE." International Journal of Software Engineering and Knowledge Engineering 11, no. 06 (December 2001): 731–59. http://dx.doi.org/10.1142/s0218194001000761.

Full text
Abstract:
The objective of this work is to examine the feasibility of, as well as to learn about, a process of developing software architecture that prevents the possibility of mismatch between homogeneous components implemented according to the architectural specification. This paper shows how the architecture can be organized, which restrictions it can use and, provided that they are used, how elaborate it should be in order to ensure that independently-developed artifacts are structurally compatible. Two components are deemed structurally compatible as long as they have appropriate code to avoid mismatch. Since the focus of the paper is on the structural forms of mismatch, the results are derived under the assumption that no run-time environment can prevent a component from executing any path in its code. The paper develops a formal model of architecture that provides a minimal set of concepts in terms of which the designers can reason about incompatibility of components. The model is used to identify the causes of structural mismatch and examine alternative ways of eliminating these causes. Following that, the paper adopts a set of architectural restrictions and shows how these restrictions can be applied in the design of software architectures to prevent the possibility of structural mismatch.
APA, Harvard, Vancouver, ISO, and other styles
9

V. Kumaraguru, P., V. J. Chakravarthy, and M. Seenivasan. "Analysis of Component based Computing." International Journal of Engineering & Technology 7, no. 4.10 (October 2, 2018): 133. http://dx.doi.org/10.14419/ijet.v7i4.10.20823.

Full text
Abstract:
To achieve a precise goal of components on different platforms that are presented the some components in order to co-operate with one another over a communication network. The component should be able to access services provided through remote, location transparent service in vocations.The major role of component-based method is represent an ideal framework for component-driven in client/server computing. One of the good implementation examples of broker architecture is Common Object Request Broker Architecture (CORBA). The component based technologies discuss the proposal of distributed object of CORBA which is the Object Management Group’s (OMG).This paper proposes the broker architecture as CORBA has distributed system that can be demonstrated by client-server architecture which practices the base for multi-tier architecture.
APA, Harvard, Vancouver, ISO, and other styles
10

Ueda, Tetsuro, and Yasushi Kuno. "Nuts?white-box component architecture." Systems and Computers in Japan 32, no. 1 (2000): 20–28. http://dx.doi.org/10.1002/1520-684x(200101)32:1<20::aid-scj3>3.0.co;2-9.

Full text
APA, Harvard, Vancouver, ISO, and other styles
More sources

Dissertations / Theses on the topic "Component architecture"

1

Banda, Ravi S. "Interoperable components across multiple component architectures." Morgantown, W. Va. : [West Virginia University Libraries], 1998. http://etd.wvu.edu/templates/showETD.cfm?recnum=232.

Full text
Abstract:
Thesis (M.S.)--West Virginia University, 1998.
Title from document title page. Document formatted into pages; contains vi, 53 p. : ill. Vita. Includes abstract. Includes bibliographical references (p. 50-51).
APA, Harvard, Vancouver, ISO, and other styles
2

Schmid, Stefan. "A component-based active router architecture." Thesis, Lancaster University, 2003. http://eprints.lancs.ac.uk/12227/.

Full text
APA, Harvard, Vancouver, ISO, and other styles
3

Leeb, Angelika. "A flexible object architecture for component software." Thesis, Massachusetts Institute of Technology, 1996. http://hdl.handle.net/1721.1/40229.

Full text
APA, Harvard, Vancouver, ISO, and other styles
4

Lewis, Joshua. "A COMMON COMPONENT-BASED SOFTWARE ARCHITECTURE FOR MILITARY AND COMMERCIAL PC-BASED VIRTUAL SIMULATION." Doctoral diss., University of Central Florida, 2006. http://digital.library.ucf.edu/cdm/ref/collection/ETD/id/2301.

Full text
Abstract:
Commercially available military-themed virtual simulations have been developed and sold for entertainment since the beginning of the personal computing era. There exists an intense interest by various branches of the military to leverage the technological advances of the personal computing and video game industries to provide low cost military training. By nature of the content of the commercial military-themed virtual simulations, a large overlap has grown between the interests, resources, standards, and technology of the computer entertainment industry and military training branches. This research attempts to identify these commonalities with the purpose of systematically designing and evaluating a common component-based software architecture that could be used to implement a framework for developing content for both commercial and military virtual simulation software applications.
Ph.D.
Other
Engineering and Computer Science
Modeling and Simulation
APA, Harvard, Vancouver, ISO, and other styles
5

Troup, Timothy J. "A component system architecture to enable user-directed component binding at run-time." Thesis, University of Glasgow, 2004. http://ethos.bl.uk/OrderDetails.do?uin=uk.bl.ethos.414045.

Full text
APA, Harvard, Vancouver, ISO, and other styles
6

Jung, Georg. "Structured interrelations of component architectures." Diss., Manhattan, Kan. : Kansas State University, 2007. http://hdl.handle.net/2097/485.

Full text
APA, Harvard, Vancouver, ISO, and other styles
7

Göbel, Steffen, Christoph Pohl, Ronald Aigner, Martin Pohlack, Simone Röttger, and Steffen Zschaler. "The COMQUAD Component Container Architecture and Contract Negotiation." Saechsische Landesbibliothek- Staats- und Universitaetsbibliothek Dresden, 2012. http://nbn-resolving.de/urn:nbn:de:bsz:14-qucosa-100181.

Full text
Abstract:
Component-based applications require runtime support to be able to guarantee non-functional properties. This report proposes an architecture for a real-time-capable, component-based runtime environment, which allows to separate non-functional and functional concerns in component-based software development. The architecture is presented with particular focus on three key issues: the conceptual architecture, an approach including implementation issues for splitting the runtime environment into a real-time-capable and a real-time-incapable part, and details of contract negotiation. The latter includes selecting component implementations for instantiantion based on their non-functional properties.
APA, Harvard, Vancouver, ISO, and other styles
8

Beckenkamp, Fábio Ghignatti. "A component architecture for artificial neural network systems." [S.l. : s.n.], 2002. http://deposit.ddb.de/cgi-bin/dokserv?idn=964923580.

Full text
APA, Harvard, Vancouver, ISO, and other styles
9

Eleyan, Amna. "Extending web service architecture with a quality component." Thesis, University of Manchester, 2007. http://ethos.bl.uk/OrderDetails.do?uin=uk.bl.ethos.511251.

Full text
APA, Harvard, Vancouver, ISO, and other styles
10

Ong, Elwin 1979. "Fault protection in a component-based spacecraft architecture." Thesis, Massachusetts Institute of Technology, 2003. http://hdl.handle.net/1721.1/82804.

Full text
APA, Harvard, Vancouver, ISO, and other styles
More sources

Books on the topic "Component architecture"

1

Michael, Rowley, ed. Understanding SCA (Service Component Architecture). Upper Saddle River, NJ: Addison-Wesley Professional, 2009.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
2

Michael, Rowley, ed. Understanding SCA (Service Component Architecture). Upper Saddle River, NJ: Addison-Wesley, 2010.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
3

Michael, Rowley, ed. Understanding SCA (Service Component Architecture). Upper Saddle River, NJ: Addison-Wesley, 2010.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
4

Akşit, Mehmet. Software Architectures and Component Technology. Boston, MA: Springer US, 2002.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
5

1949-, Anderson Paul, ed. Enterprise JavaBeans component architecture: Designing and coding enterprise applications. Upper Saddle River, N.J: Prentice Hall PTR, 2002.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
6

COM and .NET Component services. Beijing: O'Reilly, 2001.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
7

Strider, Eileen. Component-based development at Universal Underwriters. [Atlanta, Ga.]: Information Management Forum, 1997.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
8

Wentling, James W. Housing by lifestyle: The component method of residentialdesign. 2nd ed. New York: McGraw-Hill, 1995.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
9

Niemelä, Eila. A component framework of a distributed control systems family. Espoo [Finland]: Technical Research Centre of Finland, 1999.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
10

Wentling, James W. Housing by lifestyle: The component method of residential design. New York: McGraw Hill, 1989.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
More sources

Book chapters on the topic "Component architecture"

1

Rojas, Carlos. "Component Architecture." In Building Native Web Components, 61–88. Berkeley, CA: Apress, 2020. http://dx.doi.org/10.1007/978-1-4842-5905-4_6.

Full text
APA, Harvard, Vancouver, ISO, and other styles
2

Wolf, Pieter. "The Component Architecture." In Cad Frameworks, 121–83. Boston, MA: Springer US, 1994. http://dx.doi.org/10.1007/978-1-4615-2768-8_6.

Full text
APA, Harvard, Vancouver, ISO, and other styles
3

DePrince, Wayne, and Christine Hofmeister. "Analyzing Commercial Component Models." In Software Architecture, 205–19. Boston, MA: Springer US, 2002. http://dx.doi.org/10.1007/978-0-387-35607-5_13.

Full text
APA, Harvard, Vancouver, ISO, and other styles
4

Ford, Brian, Rosa Schiano-Phan, and Juan A. Vallejo. "Component Design." In The Architecture of Natural Cooling, 160–74. Second edition. | Abingdon, Oxon ; New York : Routledge, 2020. | First edition published by PHDC Press 2010.: Routledge, 2019. http://dx.doi.org/10.4324/9781315210551-7.

Full text
APA, Harvard, Vancouver, ISO, and other styles
5

Chan, Allen. "Service Component Architecture (SCA)." In Encyclopedia of Database Systems, 3479–80. New York, NY: Springer New York, 2018. http://dx.doi.org/10.1007/978-1-4614-8265-9_1193.

Full text
APA, Harvard, Vancouver, ISO, and other styles
6

Chan, Allen. "Service Component Architecture (SCA)." In Encyclopedia of Database Systems, 2632–33. Boston, MA: Springer US, 2009. http://dx.doi.org/10.1007/978-0-387-39940-9_1193.

Full text
APA, Harvard, Vancouver, ISO, and other styles
7

Paik, Hye-young, Angel Lagares Lemos, Moshe Chai Barukh, Boualem Benatallah, and Aarthi Natarajan. "Service Component Architecture (SCA)." In Web Service Implementation and Composition Techniques, 203–50. Cham: Springer International Publishing, 2017. http://dx.doi.org/10.1007/978-3-319-55542-3_8.

Full text
APA, Harvard, Vancouver, ISO, and other styles
8

Chan, Allen. "Service Component Architecture (SCA)." In Encyclopedia of Database Systems, 1–2. New York, NY: Springer New York, 2016. http://dx.doi.org/10.1007/978-1-4899-7993-3_1193-2.

Full text
APA, Harvard, Vancouver, ISO, and other styles
9

Pérez, Jennifer, Nour Ali, Jose A. Carsí, and Isidro Ramos. "Designing Software Architectures with an Aspect-Oriented Architecture Description Language." In Component-Based Software Engineering, 123–38. Berlin, Heidelberg: Springer Berlin Heidelberg, 2006. http://dx.doi.org/10.1007/11783565_9.

Full text
APA, Harvard, Vancouver, ISO, and other styles
10

Ko, Byungsun, and Jainyun Park. "Component Architecture Redesigning Approach Using Component Metrics." In Lecture Notes in Computer Science, 449–59. Berlin, Heidelberg: Springer Berlin Heidelberg, 2005. http://dx.doi.org/10.1007/978-3-540-30583-5_48.

Full text
APA, Harvard, Vancouver, ISO, and other styles

Conference papers on the topic "Component architecture"

1

Keznikl, Jaroslav, Tomas Bures, Frantiek Plasil, and Michal Kit. "Towards Dependable Emergent Ensembles of Components: The DEECo Component Model." In 2012 Joint Working IEEE/IFIP Conference on Software Architecture (WICSA 2012) & European Conference on Software Architecture (ECSA 2012). IEEE, 2012. http://dx.doi.org/10.1109/wicsa-ecsa.212.39.

Full text
APA, Harvard, Vancouver, ISO, and other styles
2

Krka, Ivo, and Nenad Medvidovic. "Component-Aware Triggered Scenarios." In 2014 IEEE/IFIP Conference on Software Architecture (WICSA). IEEE, 2014. http://dx.doi.org/10.1109/wicsa.2014.23.

Full text
APA, Harvard, Vancouver, ISO, and other styles
3

Kanjilal, Ananya, Sabnam Sengupta, and Swapan Bhattacharya. "CAG: A Component Architecture Graph." In TENCON 2008 - 2008 IEEE Region 10 Conference. IEEE, 2008. http://dx.doi.org/10.1109/tencon.2008.4766419.

Full text
APA, Harvard, Vancouver, ISO, and other styles
4

Moullec, Marie-Lise, Marija Jankovic, Marc Bouissou, Jean-Claude Bocquet, and Olivier Maas. "Proposition of Combined Approach for Architecture Generation Integrating Component Placement Optimization." 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-12557.

Full text
Abstract:
Architecture generation and evaluation are critical points in complex systems design. System architecting starts with the exploration of a set of potential solutions that is progressively focused towards the most promising ones. In theory, these solutions are identified through their potential ability to reach system requirements. However, in early design stages, data supporting design choices are fuzzy and uncertain, making difficult the evaluation a priori of the future system architecture performance. In this paper, we propose a method using Bayesian Networks (BN) and Constraint Satisfaction Problem (CSP) to first generate potential system architectures, and then select the best ones regarding system requirements. The association of these two approaches allows to enhance architecture evaluation through integration of component placement optimization. This approach is demonstrated and implemented in radar antenna architecture generation. In the end, we also discuss some of the limits of the proposed approach as well as future research directions.
APA, Harvard, Vancouver, ISO, and other styles
5

Allier, Simon, Salah Sadou, Houari Sahraoui, and Regis Fleurquin. "From Object-Oriented Applications to Component-Oriented Applications via Component-Oriented Architecture." In 2011 9th Working IEEE/IFIP Conference on Software Architecture (WICSA). IEEE, 2011. http://dx.doi.org/10.1109/wicsa.2011.35.

Full text
APA, Harvard, Vancouver, ISO, and other styles
6

Anh, Phan Duy, and Truong Dinh Chau. "Component-oriented architecture for SCADA system." In 2009 7th IEEE International Conference on Industrial Informatics (INDIN). IEEE, 2009. http://dx.doi.org/10.1109/indin.2009.5195841.

Full text
APA, Harvard, Vancouver, ISO, and other styles
7

Mennenga, Bjorn, Jie Guo, and Gerhard Fettweis. "A Component based Reconfigurable Baseband Architecture." In 2007 16th IST Mobile and Wireless Communications Summit. IEEE, 2007. http://dx.doi.org/10.1109/istmwc.2007.4299211.

Full text
APA, Harvard, Vancouver, ISO, and other styles
8

Grinkrug, E. M., and A. R. Shakurov. "Component architecture with runtime type definition." In Test Symposium (EWDTS). IEEE, 2010. http://dx.doi.org/10.1109/ewdts.2010.5742123.

Full text
APA, Harvard, Vancouver, ISO, and other styles
9

Cheung-Foo-Wo, Daniel, Jean-Yves Tigli, and Michel Riveill. "Component-based architecture and implicit interactions." In the 1st French-speaking conference. New York, New York, USA: ACM Press, 2004. http://dx.doi.org/10.1145/1050873.1050887.

Full text
APA, Harvard, Vancouver, ISO, and other styles
10

Anh, Phan Duy, and Truong Dinh Chau. "Component-Oriented Architecture for SCADA System." In 2009 International Conference on Computing, Engineering and Information (ICC). IEEE, 2009. http://dx.doi.org/10.1109/icc.2009.22.

Full text
APA, Harvard, Vancouver, ISO, and other styles

Reports on the topic "Component architecture"

1

Barrand, Guy. Abstract Interfaces for Data Analysis - Component Architecture for Data Analysis Tools. Office of Scientific and Technical Information (OSTI), August 2002. http://dx.doi.org/10.2172/800027.

Full text
APA, Harvard, Vancouver, ISO, and other styles
2

Milind Deo, Chung-Kan Huang, and Huabing Wang. Parallel, Multigrid Finite Element Simulator for Fractured/Faulted and Other Complex Reservoirs based on Common Component Architecture (CCA). Office of Scientific and Technical Information (OSTI), August 2008. http://dx.doi.org/10.2172/949977.

Full text
APA, Harvard, Vancouver, ISO, and other styles
3

N. Lybeck, B. Pham, M. Tawfik, J. B. Coble, R. M. Meyer, P. Ramuhalli, and L. J. Bond. Lifecycle Prognostics Architecture for Selected High-Cost Active Components. Office of Scientific and Technical Information (OSTI), August 2011. http://dx.doi.org/10.2172/1027927.

Full text
APA, Harvard, Vancouver, ISO, and other styles
4

Wan, A. S., L. B. Da Silva, and J. C. Moreno. Development of x-ray laser architectural components. Office of Scientific and Technical Information (OSTI), June 1994. http://dx.doi.org/10.2172/10173003.

Full text
APA, Harvard, Vancouver, ISO, and other styles
5

Gannon, Dennis. A high performance software component architectures for SciTL. Final report. Office of Scientific and Technical Information (OSTI), February 2001. http://dx.doi.org/10.2172/805788.

Full text
APA, Harvard, Vancouver, ISO, and other styles
6

Froscher, J. N., and M. H. Kang. A Client-Server Architecture Supporting MLS Interoperability with COTS Components. Fort Belvoir, VA: Defense Technical Information Center, January 1997. http://dx.doi.org/10.21236/ada465304.

Full text
APA, Harvard, Vancouver, ISO, and other styles
7

Ali, Asma T. Re-Use of Integrated Dictionary Components for C4ISR Architectures. Fort Belvoir, VA: Defense Technical Information Center, June 2003. http://dx.doi.org/10.21236/ada466759.

Full text
APA, Harvard, Vancouver, ISO, and other styles
8

Woods, T. W. Program information architecture/document hierarchy. [Information Management Systems, it's components and rationale]. Office of Scientific and Technical Information (OSTI), September 1991. http://dx.doi.org/10.2172/5147121.

Full text
APA, Harvard, Vancouver, ISO, and other styles
9

Hatcliff, John, Torben Amtoft, and Anindya Banerjee. An Integrated Specification and Verification Environment for Component-Based Architectures of Large-Scale Distributed Systems. Fort Belvoir, VA: Defense Technical Information Center, May 2009. http://dx.doi.org/10.21236/ada501823.

Full text
APA, Harvard, Vancouver, ISO, and other styles
10

Royce, Walker. Reliable, Reusable Ada Components for Constructing Large, Distributed Multi-Task Networks: Network Architecture Series (NSA). Fort Belvoir, VA: Defense Technical Information Center, December 1989. http://dx.doi.org/10.21236/ada242966.

Full text
APA, Harvard, Vancouver, ISO, and other styles
You might also be interested in the extended bibliographies on the topic 'Component architecture' for particular source types:
Journal articles Dissertations / Theses Books
We offer discounts on all premium plans for authors whose works are included in thematic literature selections. Contact us to get a unique promo code!

To the bibliography