Увійти

Готові списки джерел за темами / Component software

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

Автор: Grafiati

Опубліковано: 4 червня 2021

Оновлено: 4 березня 2023

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

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

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

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

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

Зміст

Статті в журналах
Дисертації
Книги
Частини книг
Тези доповідей конференцій
Звіти організацій

Статті в журналах з теми "Component software":

1

S, R. Chinnaiyan, and Somasundaram . "Reliability of Component Based Software with Similar Software Components � a Review." i-manager's Journal on Software Engineering 5, no. 2 (December 15, 2010): 44–49. http://dx.doi.org/10.26634/jse.5.2.1335.

Повний текст джерела

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

2

Kwong, C. K., L. F. Mu, J. F. Tang, and X. G. Luo. "Optimization of software components selection for component-based software system development." Computers & Industrial Engineering 58, no. 4 (May 2010): 618–24. http://dx.doi.org/10.1016/j.cie.2010.01.003.

Повний текст джерела

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

3

Lau, Kung-Kiu, and Zheng Wang. "Software Component Models." IEEE Transactions on Software Engineering 33, no. 10 (October 2007): 709–24. http://dx.doi.org/10.1109/tse.2007.70726.

Повний текст джерела

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

4

Goguen, Joseph, Doan Nguyen, José Meseguer, Luqi, Du Zhang, and Valdis Berzins. "Software component search." Journal of Systems Integration 6, no. 1-2 (March 1996): 93–134. http://dx.doi.org/10.1007/bf02262753.

Повний текст джерела

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

5

Morris, J., G. Lee, K. Parker, G. A. Bundell, and Chiou Peng Lam. "Software component certification." Computer 34, no. 9 (2001): 30–36. http://dx.doi.org/10.1109/2.947086.

Повний текст джерела

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

6

Phanthanithilerd, Nattapon, and Nakornthip Prompoon. "Verifying Software Requirements Characteristics Based on Rules Defined from Software Component Relationships." Lecture Notes on Software Engineering 4, no. 1 (2016): 27–33. http://dx.doi.org/10.7763/lnse.2016.v4.219.

Повний текст джерела

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

7

Shah, Shubh. "Component Based Software Engineering." International Journal for Research in Applied Science and Engineering Technology 9, no. 8 (August 31, 2021): 1588–95. http://dx.doi.org/10.22214/ijraset.2021.37632.

Повний текст джерела

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

Анотація:

Abstract: The central idea of Component Based Engineering is to develop a system software by selecting the well defined software components not used often and assembling them with certain system architecture. Nowadays the software development pattern is far different from the earlier approach as many new concepts are being taken into consideration E.g. QA (QualityAssurance). This term paper includes a detailed description of all the current component based software techniques used as well as their advantages and disadvantages. We also address the quality assurance issue of component based software engineering.

8

Min, Byungho, and Vijay Varadharajan. "Rethinking Software Component Security: Software Component Level Integrity and Cross Verification." Computer Journal 59, no. 11 (August 10, 2016): 1735–48. http://dx.doi.org/10.1093/comjnl/bxw047.

Повний текст джерела

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

9

Geum, Yeong-Uk, and Byeong-Seop Park. "Component Retrieval using Extended Software Component Descriptor." KIPS Transactions:PartD 9D, no. 3 (June 1, 2002): 417–26. http://dx.doi.org/10.3745/kipstd.2002.9d.3.417.

Повний текст джерела

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

10

Kaur, Arvinder, and Kulvinder Singh Mann. "Component Selection for Component Based Software Engineering." International Journal of Computer Applications 2, no. 1 (May 10, 2010): 109–14. http://dx.doi.org/10.5120/604-854.

Повний текст джерела

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

Більше джерел

Дисертації з теми "Component software":

1

ALVARO, Alexandre. "A software component quality framework." Universidade Federal de Pernambuco, 2009. https://repositorio.ufpe.br/handle/123456789/1372.

Повний текст джерела

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

Анотація:

Made available in DSpace on 2014-06-12T15:49:28Z (GMT). No. of bitstreams: 1 license.txt: 1748 bytes, checksum: 8a4605be74aa9ea9d79846c1fba20a33 (MD5) Previous issue date: 2009
Coordenação de Aperfeiçoamento de Pessoal de Nível Superior
Um grande desafio da Engenharia de Software Baseada em Componentes (ESBC) é a qualidade dos componentes utilizados em um sistema. A confiabilidade de um sistema baseado em componentes depende da confiabilidade dos componentes dos quais ele é composto. Na ESBC, a busca, seleção e avaliação de componentes de software é considerado um ponto chave para o efetivo desenvolvimento de sistemas baseado em componentes. Até agora a indústria de software tem se concentrado nos aspectos funcionais dos componentes de software, deixando de lado uma das tarefas mais árduas, que é a avaliação de sua qualidade. Se a garantia de qualidade de componentes desenvolvidos in-house é uma tarefa custosa, a garantia da qualidade utilizando componentes desenvolvidos externamente os quais frequentemente não se tem acesso ao código fonte e documentação detalhada se torna um desafio ainda maior. Assim, esta Tese introduz um Framework de Qualidade de Componentes de Software, baseado em módulos bem definidos que se complementam a fim de garantir a qualidade dos componentes de software. Por fim, um estudo experimental foi desenvolvido e executado de modo que se possa analisar a viabilidade do framework proposto

2

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.

Повний текст джерела

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

Анотація:

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).

3

O'Fallon, Andrew Steven. "Component-based software engineering qualification of components during design /." Online access for everyone, 2004. http://www.dissertations.wsu.edu/Thesis/Summer2004/A%5FOFallon%5F073004.pdf.

Повний текст джерела

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

4

Eler, Marcelo Medeiros. ""Um método para o desenvolvimento de software baseado em componentes e aspectos"." Universidade de São Paulo, 2006. http://www.teses.usp.br/teses/disponiveis/55/55134/tde-04072006-114542/.

Повний текст джерела

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

Анотація:

Uma investigação sobre como a programação orientada a aspectos combinada com a tecnologia de componentes pode encapsular os interesses transversais de um sistema é apresentada. Como resultado desta investigação, um método para o desenvolvimento de software baseado em componentes e aspectos é proposto, cujas etapas, atividades e artefatos são mostrados por meio do exemplo de um Sistema de Reservas de Hotéis, juntamente com sua implementação nas linguagens JAsCO e AspectJ. O método é uma extensão do método UML Components e utiliza a UML com algumas adaptações. Além disso, uma estratégia de generalização e documentação de componentes transversais para que possam ser reusados em outras aplicações é proposta. Adicionalmente, o método proposto foi usado para o projeto de um Sistema de Locação de Carros e o resultado foi comparado com uma outra solução para o mesmo problema, baseada em UML Components e uma arquitetura geral para sistemas na Web. O resultado dessa comparação é apresentado e discutido.
An investigation about how aspect oriented programming combined with the components technology can encapsulate the crosscuting concerns of a system is presented. As result of this research, a method for the aspect and component based software development is proposed, whose phases, activities and designs elements are shown by means of an example of a Hotel Reservation System, with its implementation in the JAsCO and AspectJ languages. The method is an extension of the UML Components method and uses UML with some adaptations. Moreover, a strategy to the generalization and documentation of crosscutting (or aspectual) components to be reused in other applications is proposed. Additionally, the proposed method was used to design a Car Rental System and the result was compared with another solution for the same problem, based on UML Components and a general architecture for Web systems. The results of the comparation are presented and discussed.

5

ALVARO, Alexandre. "Software component certification: a component quality model." Universidade Federal de Pernambuco, 2005. https://repositorio.ufpe.br/handle/123456789/2796.

Повний текст джерела

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

Анотація:

Made available in DSpace on 2014-06-12T16:01:14Z (GMT). No. of bitstreams: 2 arquivo7273_1.pdf: 859722 bytes, checksum: 0a10aaaffe0f345515ef1d4559599ff4 (MD5) license.txt: 1748 bytes, checksum: 8a4605be74aa9ea9d79846c1fba20a33 (MD5) Previous issue date: 2005
Coordenação de Aperfeiçoamento de Pessoal de Nível Superior
Desenvolvimento de Software Baseado em Componentes tem sido amplamente adotado na academia e na prática, representando assim um mercado promissor para a indústria de software. A perspectiva de redução do custo e do ciclo de desenvolvimento do software tem sido a principal motivação para esta expansão. Entretanto, inúmeros problemas técnicos ainda permanecem sem solução antes mesmo que a indústria de componentes de software alcance a maturidade de outras indústrias de software. Problemas como a seleção de componentes, a carência de catálogos de componentes formalizados e a falta de informações sobre a qualidade dos componentes desenvolvidos trazem novos desafios para a comunidade de engenharia de software. Por outro lado, a área de certificação de componentes de software é relativamente imatura e necessita de consideráveis pesquisas para o estabelecimento de um padrão para certificação de componentes de software. Assim, esta dissertação apresenta um modelo de qualidade de componentes, baseada em características consistentes e bem definida, atributos de qualidade e métricas relacionadas para avaliação dos componentes. Um estudo experimental foi desenvolvimento visando analisar a viabilidade de utilização do modelo. Os resultados obtidos mostrar-se-iam que o modelo é um interessante candidato para avaliação da qualidade em componentes de software, e trabalhos futuros estão sendo planejamentos para que a evolução do modelo alcance o nível de maturação necessário e torne-o diretamente aplicável à indústria de software

6

Peres, Darley Rosa. "Modelo de qualidade para componentes de software." Universidade de São Paulo, 2006. http://www.teses.usp.br/teses/disponiveis/55/55134/tde-29012007-112338/.

Повний текст джерела

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

Анотація:

Dentre as tecnologias de desenvolvimento de software que promovem o reuso com o objetivo de construir sistemas com prazos e custos menores, sem sacrificar a qualidade dos produtos, está o Desenvolvimento Baseado em Componentes (DBC). O Desenvolvimento Baseado em Componentes consiste na construção de sistemas pela composição de componentes de software de acordo com um processo de desenvolvimento específico. Para garantir a qualidade desses sistemas, é importante garantir a qualidade de seus componentes. A falta da garantia da qualidade dos componentes de software destinados à reutilização é um dos fatores de inibição do DBC, e existe certa carência de pesquisas sobre a qualidade de componentes de software. Desta maneira, o principal objetivo deste trabalho foi a definição de um modelo de qualidade específico para componentes de software, fornecendo a base para a especificação de requisitos de qualidade e para a avaliação de qualidade dos mesmos. O Modelo está embasado nas normas ISO/IEC 9126 e ISO/IEC 12119, e também na literatura especializada. Uma ferramenta para apoiar avaliações de componentes (e de produtos de software de forma geral) também foi desenvolvida. Foram realizadas ainda quatro avaliações de componentes através de estudos de casos para verificar a aplicabilidade e utilidade do modelo de qualidade e da ferramenta desenvolvida. Dois questionários foram respondidos pelos avaliadores responsáveis pelas avaliações coletando assim, suas considerações sobre o modelo de qualidade e sobre a ferramenta
Among the software development technologies that promote the reuse aiming to build systems with periods and smaller costs, without sacrificing the quality of products, is the Component-Based Development (CBD). The Component-Based Development consists on the construction of systems by the composition of software components according to a specific development process. To guarantee the quality of those systems, it is important to guarantee the quality of their components. The lack of warranty of the quality of the software components destined to reuse is one of the inhibition factors of CBD, and there is certain lack of researches about quality of software components. This way, the main objective of this work was the formalization of a specific quality model for software components, supplying the base for the specification of quality requirements and for the quality evaluation of the same ones. The model is based on the norms ISO/IEC 9126 and ISO/IEC 12119, and also in the specialized literature. A tool to support components evaluations (and software products in a general way) was also developed. It was realized four components evaluations through case studies to verify the applicability and usefulness of the quality model and the developed tool. Two questionnaires were answered by the appraisers responsible for the evaluations collecting thereby, their considerations on the quality model and the tool

7

Abdullahi, Abdille. "Component-based Software development." Thesis, Växjö University, School of Mathematics and Systems Engineering, 2008. http://urn.kb.se/resolve?urn=urn:nbn:se:vxu:diva-2335.

Повний текст джерела

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

Анотація:

Component-based Software development is a promising way to improve quality, time to market and handle the increasing complexity of software management. However, The component-based development is still a process with many problems, it is not well de_ned either from theoretical or practical point of view. This thesis gives a brief overview of Component-Based Software development and starts with brief historical evolution followed by a general explanation of the method. A detailed discussion of the underlying principles like components, component framework and compent system architecture are then presented. Some real world component stadards such as .net framework, CORBA CCM and EJB are given in detail. Finally, simple fille-sharing-program based on Apache's Avalon framework and another one based on .net framework are developed as a case study.

8

Fischer, Bernd. "Deduction-based software component retrieval." [S.l.] : [s.n.], 2002. http://deposit.ddb.de/cgi-bin/dokserv?idn=964334488.

Повний текст джерела

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

9

Wu, Zhengyu Leo. "Software component retrieval by composition." Thesis, National Library of Canada = Bibliothèque nationale du Canada, 1997. http://www.collectionscanada.ca/obj/s4/f2/dsk2/tape16/PQDD_0001/MQ31009.pdf.

Повний текст джерела

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

10

Kivijärvi, M. (Marko). "Cross-platform software component design." Master's thesis, University of Oulu, 2013. http://urn.fi/URN:NBN:fi:oulu-201306011427.

Повний текст джерела

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

Анотація:

The aim of this thesis is to analyze a project to design and implement a new FM Radio application for Symbian OS. The project process and relevant events are discussed when they have an impact on the design work. The goal of the project was to offer an improved user experience with features like favorite stations, song history, RT+ support, and automatic region selection. In order to complete the application within the project schedule, the existing radio modules were to be reused as much as possible. The application was required to be developed using the Qt application framework and to have no dependencies on the old UI framework from the Symbian OS. Platform-independence, testability, and simplicity were other key requirements for the new radio application. A final comprehensive goal was to stick to established design patterns and to follow the design principles and good practices defined earlier in the bachelor’s thesis by the same author. An added challenge was provided by the necessity to develop the application on top of a new UI framework that was still in development itself. Constant changes to the framework put a strain on the already tight project schedule. The discussion focuses on the design of the engine module that was required to house most of the application logic. The engine is disconnected from the Symbian OS by the use of a wrapper module, whose purpose is to hide the platform details. Due to its relevance to the engine, the design of the wrapper is discussed in detail. The application UI and the reused radio modules are discussed briefly and only to the extent that is relevant for the engine design. The resulting design fulfills its requirements and the implemented application performs as designed. All the required features are supported, and the existing radio modules are reused. The lack of dependency on the old UI framework is witnessed by running the application in a system that does not contain the framework. The possibility to run the application on a Windows workstation also affirms that the platform-independence requirement was achieved. The design and implementation adhere to the principles outlined in the bachelor’s thesis and provide a practical use for them. The principles are found to be valid and important for the successful completion of a complex software project. It is discovered that the goal of designing a simple system from complicated beginnings is difficult to achieve and requires many iterations. Gradual refinements to the architecture and implementation are necessary to finally arrive at the optimal design. Constant refactoring is found to be a key element in the successful completion of a software project
Tässä työssä analysoidaan projektia, jossa suunniteltiin ja toteutettiin uusi FM Radio -sovellus Symbian-käyttöjärjestelmälle. Projektin prosessi ja oleelliset tapahtumat kuvataan siltä osin kuin ne vaikuttavat suunnittelutyöhön. Projektin tavoite oli tarjota parempi käyttökokemus uusilla ominaisuuksilla kuten suosikkikanavilla, kappalehistorialla, RT+ -tuella, ja automaattisella aluevalinnalla. Olemassa olevia radiomoduuleita oli uudelleenkäytettävä niin paljon kuin mahdollista, jotta projekti saataisiin aikataulun puitteissa valmiiksi. Sovellus tuli suunnitella Qt-sovelluskehystä käyttäen, eikä sillä saanut olla riippuvuuksia vanhaan käyttöliittymäkirjastoon. Alustariippumattomuus, testattavuus ja yksinkertaisuus olivat myös tärkeitä vaatimuksia. Viimeinen kattava tavoite oli pitäytyä vakiintuneissa suunnittelumalleissa ja noudattaa suunnitteluperiaatteita ja hyviä toimintatapoja, jotka olivat saman tekijän kandidaatintyössä aiemmin määritelty. Tarve toteuttaa sovellus keskeneräisen käyttöliittymäkirjaston päälle asetti oman lisähaasteensa. Jatkuvat muutokset kirjastossa rasittivat jo valmiiksi tiukkaa projektiaikataulua. Tämän työn pääpaino on moottorimoduulissa, jonka tuli sisältää suurin osa sovelluksen logiikasta. Moottori on eriytetty Symbian-käyttöjärjestelmästä adapterimoduulilla, jonka tarkoitus on piilottaa ohjelmistoalustan yksityiskohdat. Adapterin suunnitelma kuvataan yksityiskohtaisesti. Sovelluksen käyttöliittymä ja uudelleenkäytetyt radiomoduulit kuvataan lyhyesti ja vain niiltä osin kuin ne ovat moottorin suunnitelmalle oleellisia. Tuloksena syntyvä suunnitelma täyttää vaatimukset, ja toteutettu sovellus toimii kuten oli suunniteltu. Kaikki vaaditut ominaisuudet ovat tuettuja ja olemassa olevat radiomoduulit käytettiin uudelleen. Riippumattomuus vanhasta käyttöliittymäkirjastosta havaitaan suorittamalla sovellusta järjestelmässä, jossa sitä ei ole. Mahdollisuus ajaa sovellusta Windows-työasemassa myös todistaa sen, että alustariippumattomuuden vaatimus täytettiin. Suunnitelma ja toteutus noudattavat kandidaatintyössä määriteltyjä periaatteita ja tarjoavat niille käytännön sovellutuksen. Periaatteet todetaan paikkansapitäviksi ja tärkeiksi monimutkaisen ohjelmistoprojektin onnistuneen valmistumisen kannalta. Työssä havaitaan, että tavoite suunnitella yksinkertainen järjestelmä monimutkaisista lähtökohdista on vaikea saavuttaa ja vaatii useita toistoja. Asteittaiset korjaukset arkkitehtuuriin ja toteutukseen ovat välttämättömiä optimaaliseen suunnitelman saavuttamiseksi. Jatkuvan uudelleenjärjestelyn havaitaan olevan avainasemassa ohjelmistosuunnitteluprosessissa

Більше джерел

Книги з теми "Component software":

1

Schmidt, Heinz W., Ivica Crnkovic, George T. Heineman, and Judith A. Stafford, eds. Component-Based Software Engineering. Berlin, Heidelberg: Springer Berlin Heidelberg, 2007. http://dx.doi.org/10.1007/978-3-540-73551-9.

Повний текст джерела

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

2

Gorton, Ian, George T. Heineman, Ivica Crnković, Heinz W. Schmidt, Judith A. Stafford, Clemens Szyperski, and Kurt Wallnau, eds. Component-Based Software Engineering. Berlin, Heidelberg: Springer Berlin Heidelberg, 2006. http://dx.doi.org/10.1007/11783565.

Повний текст джерела

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

3

Chaudron, Michel R. V., Clemens Szyperski, and Ralf Reussner, eds. Component-Based Software Engineering. Berlin, Heidelberg: Springer Berlin Heidelberg, 2008. http://dx.doi.org/10.1007/978-3-540-87891-9.

Повний текст джерела

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

4

Grunske, Lars, Ralf Reussner, and Frantisek Plasil, eds. Component-Based Software Engineering. Berlin, Heidelberg: Springer Berlin Heidelberg, 2010. http://dx.doi.org/10.1007/978-3-642-13238-4.

Повний текст джерела

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

5

Cechich, Alejandra, Mario Piattini, and Antonio Vallecillo, eds. Component-Based Software Quality. Berlin, Heidelberg: Springer Berlin Heidelberg, 2003. http://dx.doi.org/10.1007/b11721.

Повний текст джерела

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

6

Heineman, George T., Ivica Crnkovic, Heinz W. Schmidt, Judith A. Stafford, Clemens Szyperski, and Kurt Wallnau, eds. Component-Based Software Engineering. Berlin, Heidelberg: Springer Berlin Heidelberg, 2005. http://dx.doi.org/10.1007/b136248.

Повний текст джерела

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

7

Crnkovic, Ivica, Judith A. Stafford, Heinz W. Schmidt, and Kurt Wallnau, eds. Component-Based Software Engineering. Berlin, Heidelberg: Springer Berlin Heidelberg, 2004. http://dx.doi.org/10.1007/b97813.

Повний текст джерела

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

8

Lewis, Grace A., Iman Poernomo, and Christine Hofmeister, eds. Component-Based Software Engineering. Berlin, Heidelberg: Springer Berlin Heidelberg, 2009. http://dx.doi.org/10.1007/978-3-642-02414-6.

Повний текст джерела

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

9

Conaghan, Peter. Component software and Javabeans. [s.l: The Author], 1998.

Знайти повний текст джерела

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

10

Hamlet, Dick. Composing software components: A software-testing perspective. New York: Springer, 2010.

Знайти повний текст джерела

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

Більше джерел

Частини книг з теми "Component software":

1

Coulange, Bernard. "Component Certification." In Software Reuse, 113–26. London: Springer London, 1998. http://dx.doi.org/10.1007/978-1-4471-1511-3_7.

Повний текст джерела

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

2

Coulange, Bernard. "Component Storage." In Software Reuse, 127–41. London: Springer London, 1998. http://dx.doi.org/10.1007/978-1-4471-1511-3_8.

Повний текст джерела

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

3

Hamlet, Dick. "Software Components and Component-based Development." In Composing Software Components, 29–40. Boston, MA: Springer US, 2010. http://dx.doi.org/10.1007/978-1-4419-7148-7_3.

Повний текст джерела

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

4

Eeles, Peter. "Business Component Development." In Software Architectures, 27–59. London: Springer London, 2000. http://dx.doi.org/10.1007/978-1-4471-0367-7_3.

Повний текст джерела

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

5

Attiogbé, Christian, Pascal André, and Gilles Ardourel. "Checking Component Composability." In Software Composition, 18–33. Berlin, Heidelberg: Springer Berlin Heidelberg, 2006. http://dx.doi.org/10.1007/11821946_2.

Повний текст джерела

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

6

Zimmermann, Wolf, and Michael Schaarschmidt. "Automatic Checking of Component Protocols in Component-Based Systems." In Software Composition, 1–17. Berlin, Heidelberg: Springer Berlin Heidelberg, 2006. http://dx.doi.org/10.1007/11821946_1.

Повний текст джерела

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

7

Seinturier, Lionel, Nicolas Pessemier, Laurence Duchien, and Thierry Coupaye. "A Component Model Engineered with Components and Aspects." In Component-Based Software Engineering, 139–53. Berlin, Heidelberg: Springer Berlin Heidelberg, 2006. http://dx.doi.org/10.1007/11783565_10.

Повний текст джерела

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

8

Hamlet, Dick. "Debugging Components, Component-based Systems, and Support Tools." In Composing Software Components, 219–32. Boston, MA: Springer US, 2010. http://dx.doi.org/10.1007/978-1-4419-7148-7_15.

Повний текст джерела

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

9

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.

Повний текст джерела

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

10

Heineman, George T. "Unit Testing of Software Components with Inter-component Dependencies." In Component-Based Software Engineering, 262–73. Berlin, Heidelberg: Springer Berlin Heidelberg, 2009. http://dx.doi.org/10.1007/978-3-642-02414-6_16.

Повний текст джерела

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

Тези доповідей конференцій з теми "Component software":

1

Reitz, Markus. "Software Evolvability by Component-Orientation." In Second International IEEE Workshop on Software Evolvability. IEEE, 2006. http://dx.doi.org/10.1109/software-evolvability.2006.13.

Повний текст джерела

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

2

Lau, Kung-Kiu. "Software component models." In the 17th international ACM Sigsoft symposium. New York, New York, USA: ACM Press, 2014. http://dx.doi.org/10.1145/2602458.2611456.

Повний текст джерела

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

3

Lau, Kung-Kiu. "Software component models." In Proceeding of the 28th international conference. New York, New York, USA: ACM Press, 2006. http://dx.doi.org/10.1145/1134285.1134516.

Повний текст джерела

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

4

Tiwari, Arti, and Partha Sarathi Chakraborty. "Software Component Quality Characteristics Model for Component Based Software Engineering." In 2015 IEEE International Conference on Computational Intelligence & Communication Technology (CICT). IEEE, 2015. http://dx.doi.org/10.1109/cict.2015.40.

Повний текст джерела

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

5

Alvaro, Alexandre, and Silvio Lemos Meira. "Software Component Certification: A Component Quality Model." In Simpósio Brasileiro de Qualidade de Software. Sociedade Brasileira de Computação - SBC, 2006. http://dx.doi.org/10.5753/sbqs.2006.15630.

Повний текст джерела

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

Анотація:

Component-based software development is becoming more generalized, representing a considerable market for the software industry. However, several technical issues remain unsolved before the software components industry reaches the maturity as other software industries. Problems such as component selection and the uncertain quality of third-party developed components bring new challenges to the software engineering community. In contrast, software component certification is still immature and much research is needed in order to create well-defined standards for certification. This paper introduces a component quality model, based upon consistent and well-defined quality characteristics, and describes a formal case study that was used in order to analyze the viability of the model usage.

6

Lednicki, Luka, Ana Petricic, and Mario agar. "A Component-Based Technology for Hardware and Software Components." In 2009 35th Euromicro Conference on Software Engineering and Advanced Applications. IEEE, 2009. http://dx.doi.org/10.1109/seaa.2009.26.

Повний текст джерела

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

7

Srinivas, Chintakindi, Vangipuram Radhakrishna, and C. V. Guru Rao. "Clustering Software Components for Component Reuse and Program Restructuring." In the Second International Conference. New York, New York, USA: ACM Press, 2013. http://dx.doi.org/10.1145/2556871.2556933.

Повний текст джерела

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

8

Biggs, Geoffrey. "Flexible, adaptable utility components for component-based robot software." In 2010 IEEE International Conference on Robotics and Automation (ICRA 2010). IEEE, 2010. http://dx.doi.org/10.1109/robot.2010.5509204.

Повний текст джерела

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

9

Capretz, L. F., M. A. M. Capretz, and Dahai Li. "Component-based software development." In IECON'01. 27th Annual Conference of the IEEE Industrial Electronics Society. IEEE, 2001. http://dx.doi.org/10.1109/iecon.2001.975569.

Повний текст джерела

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

10

Green, Robin. "Component-based software development." In the 17th annual international conference. New York, New York, USA: ACM Press, 1999. http://dx.doi.org/10.1145/318372.318582.

Повний текст джерела

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

Звіти організацій з теми "Component software":

1

Kohn, S., N. Dykman, G. Kumfert, and B. Smolinski. Scientific Software Component Technology. Office of Scientific and Technical Information (OSTI), February 2000. http://dx.doi.org/10.2172/792560.

Повний текст джерела

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

2

Wallnau, Kurt C. Software Component Certification: 10 Useful Distinctions. Fort Belvoir, VA: Defense Technical Information Center, September 2004. http://dx.doi.org/10.21236/ada430991.

Повний текст джерела

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

3

Chandrasekaran, B., and Bruce Weide. Functional Representation of Software Systems and Component-Based Software Technology. Fort Belvoir, VA: Defense Technical Information Center, February 1998. http://dx.doi.org/10.21236/ada341742.

Повний текст джерела

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

4

Malony, Allen D. Performance Engineering Technology for Scientific Component Software. Office of Scientific and Technical Information (OSTI), May 2007. http://dx.doi.org/10.2172/909872.

Повний текст джерела

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

5

Lindquist, Timothy E. PCIS-2: Distributed Component-based Software Engineering. Fort Belvoir, VA: Defense Technical Information Center, May 1999. http://dx.doi.org/10.21236/ada363579.

Повний текст джерела

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

6

Estep, James, and Kerri Haines. Command Center Component Supported Component Report. Central Archive for Reusable Defense Software (CARDS). Fort Belvoir, VA: Defense Technical Information Center, February 1994. http://dx.doi.org/10.21236/ada284575.

Повний текст джерела

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

7

Sottile, Matthew. Center for Technology for Advanced Scientific Component Software. Office of Scientific and Technical Information (OSTI), June 2010. http://dx.doi.org/10.2172/1122415.

Повний текст джерела

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

8

Ulery, Dana L., Brian R. Schallhorn, and Wade S. Jernigan. BuyIt Software Development Plan: A C-BASS Component. Fort Belvoir, VA: Defense Technical Information Center, May 1999. http://dx.doi.org/10.21236/ada363051.

Повний текст джерела

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

9

LKnight, J. C., J. W. Davidson, D. Evans, A. Nguyen-Tuong, and C. Wang. Genesis: A Framework for Achieving Software Component Diversity. Fort Belvoir, VA: Defense Technical Information Center, January 2007. http://dx.doi.org/10.21236/ada462289.

Повний текст джерела

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

10

Mateas, Michael. A Cognitively Motivated System for Software Component Reuse. Portland State University Library, January 2000. http://dx.doi.org/10.15760/etd.6583.

Повний текст джерела

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