Bibliografías temáticas / Harware and software architecture

Índice

  1. Artículos de revistas
  2. Tesis
  3. Libros
  4. Capítulos de libros
  5. Actas de conferencias
  6. Informes

Literatura académica sobre el tema "Harware and software architecture"

Autor: Grafiati
Publicado: 8 de marzo de 2025

Crea una cita precisa en los estilos APA, MLA, Chicago, Harvard y otros

Elija tipo de fuente:

Consulte las listas temáticas de artículos, libros, tesis, actas de conferencias y otras fuentes académicas sobre el tema "Harware and software architecture".

Junto a cada fuente en la lista de referencias hay un botón "Agregar a la bibliografía". Pulsa este botón, y generaremos automáticamente la referencia bibliográfica para la obra elegida en el estilo de cita que necesites: APA, MLA, Harvard, Vancouver, Chicago, etc.

También puede descargar el texto completo de la publicación académica en formato pdf y leer en línea su resumen siempre que esté disponible en los metadatos.

Artículos de revistas sobre el tema "Harware and software architecture"

1

Setyanto, Barry Nur, Fanani Arief Ghozali, David Yoga Pradana y Hanafi Wahyu Ramndani. "PERANCANGAN SMART HELMET UNTUK KEAMANAN SEPEDA MOTOR DENGAN SISTEM BLUETOOTH DAN RADIO FREKUENSI". MEDIA ELEKTRIKA 15, n.º 2 (31 de diciembre de 2022): 64. http://dx.doi.org/10.26714/me.v15i2.8580.

Texto completo
Resumen
Peningkatan tindak pencurian sepeda motor sebesar enam persen dimasa pandemi covid-19 terjadi di tahun 2020, hal ini menjadi himbauan kepada masyarakat agar dapat menjaga kendaraan terkhusussepeda motor. Teknologi keamanan telah banyak diupayakan oleh pihak pabrik sepeda motor. Sistem keamanan ganda dan jenis nirkabel telah banyak diproduksi, akan tetapi teknologi yang canggih tersebut hanya tersemat pada kendaraan tipe baru, sehingga diperlukan pengembangan produk keamanan sepeda motor. Telah banyak produk diteliti menggunakan integrasi teknologi elektronika berupa hardware dan software. Hardware berupa arduino, bluetooth, relay, buzzer dan perangkat smartphone, sedangkan software berupa program arduino dan program aplikasi di android. Dalam hal tersebut belum ada perancangan yang mengabungkan antara bluetooth dan radio frekuensi yang meletakkan hardware pengirim sinyal pada helm. Perancangan dilakukan menggunakan metode penelitian modeling dengan pendekatan hard approaches untuk menghasilkan produk. Penelitian menghasilkan produk hardware receiver, hardware transmitter dan software berupa aplikasi android yang dapat mengendalikan kedua hardware. Hasil pengujian oleh expert judgement pada aspek functional suitabilitymenunjukkan kinerja sangat baik pada ujicoba harware maupun software.
Los estilos APA, Harvard, Vancouver, ISO, etc.
2

Lugo Espinosa, Oziel, Gregorio Arellano Ostoa y Diego Hernández Cote. "Automatización de un sistema de inmersión temporal con base en plataformas abiertas de hardware y software." REVISTA TERRA LATINOAMERICANA 35, n.º 3 (5 de julio de 2017): 269. http://dx.doi.org/10.28940/terra.v35i3.193.

Texto completo
Resumen
Un Sistema de Inmersión Temporal (SIT) permite la micropropagación de plantas en ambientes esterilizados y herméticos; sin embargo, es una tecnología complicada y costosa. En este trabajo, se presenta una alternativa de automatización con base en plataformas abiertas de harware y software, con los objetivos de reducir costos y aumentar las prestaciones frente a sistemas comerciales, mediante la reconf iguración por software de rutinas para la aplicación de nutrientes, monitoreo constante y control a distancia del sistema. Para el desarrollo del hadware se utilizó la metodología Bottom Up, y para el software, la metodología Kanban. El sistema propuesto tiene un costo promedio de un 10% en comparación con dispositivos electrónicos comerciales utilizados en la industria para resolver problemas de automatización de procesos. Sin embargo, es necesario una evaluación de crecimiento de los explantes para corroborar las ventajas competitivas del prototipo equiparadas a los sistemas tradicionales de inmersión temporal.
Los estilos APA, Harvard, Vancouver, ISO, etc.
3

McGregor, John D. "Software Architecture." Journal of Object Technology 3, n.º 5 (2004): 65. http://dx.doi.org/10.5381/jot.2004.3.5.c7.

Texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.
4

Anderson, Bruce, Mary Shaw, Larry Best y Kent Beck. "Software architecture". ACM SIGPLAN Notices 28, n.º 10 (octubre de 1993): 356–59. http://dx.doi.org/10.1145/167962.165922.

Texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.
5

ZHANG, Li. "Software Architecture Evaluation". Journal of Software 19, n.º 6 (21 de octubre de 2008): 1328–39. http://dx.doi.org/10.3724/sp.j.1001.2008.01328.

Texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.
6

Anderson, Bruce, Mary Shaw, Larry Best y Kent Beck. "Software architecture (panel)". ACM SIGPLAN OOPS Messenger 5, n.º 2 (abril de 1994): 63–66. http://dx.doi.org/10.1145/260304.260321.

Texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.
7

Garlan, David. "Software architecture (panel)". ACM SIGSOFT Software Engineering Notes 20, n.º 4 (octubre de 1995): 5. http://dx.doi.org/10.1145/222132.222134.

Texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.
8

Barber, K. S. y J. Holt. "Software architecture correctness". IEEE Software 18, n.º 6 (2001): 64–65. http://dx.doi.org/10.1109/52.965805.

Texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.
9

Del Ra, William. "Software systems architecture". ACM SIGSOFT Software Engineering Notes 37, n.º 2 (3 de abril de 2012): 36. http://dx.doi.org/10.1145/2108144.2108171.

Texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.
10

Miyachi, Christine. "Agile software architecture". ACM SIGSOFT Software Engineering Notes 36, n.º 2 (14 de marzo de 2011): 1–3. http://dx.doi.org/10.1145/1943371.1943388.

Texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.
Más fuentes

Tesis sobre el tema "Harware and software architecture"

1

Guerif, Benjamin. "Conception d’une sonde programmable, polyvalente et abordable pour l'imagerie médicale ultrasonore volumétrique en temps réel". Electronic Thesis or Diss., Université Paris sciences et lettres, 2024. http://www.theses.fr/2024UPSLS041.

Texto completo
Resumen
Selon l’Organisation Mondiale de la Santé, les maladies cardiovasculaires sont la principale cause de décès dans le monde avec 17.9 millions de décès soit 32% des morts constatés en 2019. L’échocardiographie transthoracique (TTE), une technique d’imagerie ultrasonore non invasive et non irradiante, s’est alors imposée comme un outil de diagnostic efficace permettant d’identifier les dysfonctionnements du muscle cardiaque. Cette technique permet alors de procéder à une analyse morphologique et cinétique du cœur à l’aide de techniques d’imagerie dites conventionnelles.D’autres techniques alternatives telles que l’imagerie ultrarapide proposent des modalités complémentaires pouvant permettre d’améliorer le diagnostic des maladies cardiovasculaires. Si ces techniques ont pu faire leurs preuves en imagerie bidimensionnelle (2D), différentes barrières technologiques s’opposent à sa démocratisation en imagerie tridimensionnelle (3D). En effet, le passage de la 2D à la 3D nécessite d’adresser des réseaux de transducteurs de plusieurs milliers de voies. Les systèmes d’imagerie cliniques ayant un nombre de voies limité (le plus souvent à 256), l’utilisation de techniques dites de réduction de voie s’avère donc nécessaire. L’une d’entre elles, appelée micro-formation de faisceau, s’est ainsi démarquée en proposant des performances d’imagerie conventionnelles 3D similaires à une sonde d’imagerie 2D. Cette technologie est le plus souvent fermé et semble a priori difficilement compatible avec des techniques d’imagerie alternative. Ce faisant l’imagerie ultrarapide s’est rapidement orientée sur des techniques de réduction de voie alternatives telles que les réseaux ligne-colonne, les réseaux clairsemés ou l’utilisation de systèmes d’imagerie encombrants avec des sondes matricielles de plus petite surface acoustique et composée de milliers d’éléments.Dans cette thèse, un premier travail visant à améliorer les techniques d’imagerie ultrarapide existantes est proposé en nous appuyant sur l’utilisation d’une nouvelle sonde complètement peuplée composée de 3072 éléments associée à nouveau système d’imagerie de plusieurs milliers de voies. Par la suite, la définition et l’étude d’une sonde matricielle active dédiée à l’imagerie TTE reposant sur l’utilisation de la micro-formation de faisceau et composée de plusieurs milliers d’éléments pilotés par un unique système d’imagerie est proposée. Enfin, un prototype de sonde de micro-formation de faisceau est réalisé et évalué expérimentalement à l’aide d’un échographe de recherche ouvert afin de proposer une première sonde suffisamment polyvalente, programmable et abordable pour rendre accessible cette technologies aux laboratoires de recherche et ainsi offrir de nouveaux outils de diagnostic en échocardiographie transthoracique 3D
Selon l’Organisation Mondiale de la Santé, les maladies cardiovasculaires sont la principale cause de décès dans le monde avec 17.9 millions de décès soit 32% des morts constatés en 2019. L’échocardiographie transthoracique (TTE), une technique d’imagerie ultrasonore non invasive et non irradiante, s’est alors imposée comme un outil de diagnostic efficace permettant d’identifier les dysfonctionnements du muscle cardiaque. Cette technique permet alors de procéder à une analyse morphologique et cinétique du cœur à l’aide de techniques d’imagerie dites conventionnelles.D’autres techniques alternatives telles que l’imagerie ultrarapide proposent des modalités complémentaires pouvant permettre d’améliorer le diagnostic des maladies cardiovasculaires. Si ces techniques ont pu faire leurs preuves en imagerie bidimensionnelle (2D), différentes barrières technologiques s’opposent à sa démocratisation en imagerie tridimensionnelle (3D). En effet, le passage de la 2D à la 3D nécessite d’adresser des réseaux de transducteurs de plusieurs milliers de voies. Les systèmes d’imagerie cliniques ayant un nombre de voies limité (le plus souvent à 256), l’utilisation de techniques dites de réduction de voie s’avère donc nécessaire. L’une d’entre elles, appelée micro-formation de faisceau, s’est ainsi démarquée en proposant des performances d’imagerie conventionnelles 3D similaires à une sonde d’imagerie 2D. Cette technologie est le plus souvent fermé et semble a priori difficilement compatible avec des techniques d’imagerie alternative. Ce faisant l’imagerie ultrarapide s’est rapidement orientée sur des techniques de réduction de voie alternatives telles que les réseaux ligne-colonne, les réseaux clairsemés ou l’utilisation de systèmes d’imagerie encombrants avec des sondes matricielles de plus petite surface acoustique et composée de milliers d’éléments.Dans cette thèse, un premier travail visant à améliorer les techniques d’imagerie ultrarapide existantes est proposé en nous appuyant sur l’utilisation d’une nouvelle sonde complètement peuplée composée de 3072 éléments associée à nouveau système d’imagerie de plusieurs milliers de voies. Par la suite, la définition et l’étude d’une sonde matricielle active dédiée à l’imagerie TTE reposant sur l’utilisation de la micro-formation de faisceau et composée de plusieurs milliers d’éléments pilotés par un unique système d’imagerie est proposée. Enfin, un prototype de sonde de micro-formation de faisceau est réalisé et évalué expérimentalement à l’aide d’un échographe de recherche ouvert afin de proposer une première sonde suffisamment polyvalente, programmable et abordable pour rendre accessible cette technologies aux laboratoires de recherche et ainsi offrir de nouveaux outils de diagnostic en échocardiographie transthoracique 3D
Los estilos APA, Harvard, Vancouver, ISO, etc.
2

Jantz, Detlef. "Eine Prozessorerweiterung im Harware-Software-Interface zur Überwachung von Datenzugriffen". Clausthal-Zellerfeld Papierflieger, 2008. http://d-nb.info/992301386/04.

Texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.
3

Bahtiyar, Muhammed Yasin. "Software Architecture Checker". Thesis, Växjö University, School of Mathematics and Systems Engineering, 2008. http://urn.kb.se/resolve?urn=urn:nbn:se:vxu:diva-2294.

Texto completo
Resumen

By the increasing needs of software industry, software systems became more complex constructions than ever before. As a result of increasing complexity in software systems, functional decomposition of these systems gains the status of the most important aspect in the software development process. Dividing problems to sub-problems and producing specific solutions for divided parts makes it easier to solve the main problem.

Component Based Software Engineering is a way of developing software systems that consists of logically or functionally decomposed components which integrated to each other by the help of well-defined interfaces. CBSE relies on architectural design of a software system.

Planning phase and implementation of a software project may differ time to time. Because of the complexity of software systems, solving specific problems may affect the architecture of the whole system.

In spite of sophisticated software engineering processes and CASE tools there is still a large gap between the planned and implemented architecture of software systems. Finding deviations from architecture in source code is a non-trivial task requiring tool support.

Since, matching operation of designed software architecture and implemented software architecture needs to check design documents against implementation code. This manual checking operation is nearly impossible for major software systems. Software Architecture Checker provides a great approach to check the architecture of any software system.

This bachelor thesis examines the approach behind the Software Architecture Checker.

Los estilos APA, Harvard, Vancouver, ISO, etc.
4

Mårtensson, Frans y Per Jönsson. "Software Architecture Simulation". Thesis, Blekinge Tekniska Högskola, Institutionen för programvaruteknik och datavetenskap, 2002. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-4087.

Texto completo
Resumen
A software architecture is one of the first steps towards a software system. A software architecture can be designed in different ways. During the design phase, it is important to select the most suitable design of the architecture, in order to create a good foundation for the system. The selection process is performed by evaluating architecture alternatives against each other. We investigate the use of continuous simulation of a software architecture as a support tool for architecture evaluation. For this purpose, we study a software architecture of an existing software system in an experiment, where we create a model of it using a tool for continuous simulation, and simulate the model. Based on the results from the simulation, we conclude that the system is too complex to be modeled for continuous simulation. Problems we identify are that we need discrete functionality to be able to correctly simulate the system, and that it is very time-consuming to develop a model for evaluation purposes. Thus, we find that continuous simulation is not appropriate for evaluating a software architecture, but that the modeling process is a valuable tool for increasing knowledge and understanding about an architecture.
Los estilos APA, Harvard, Vancouver, ISO, etc.
5

Barnes, Jeffrey M. "Software Architecture Evolution". Research Showcase @ CMU, 2013. http://repository.cmu.edu/dissertations/291.

Texto completo
Resumen
Many software systems eventually undergo changes to their basic architectural structure. Such changes may be prompted by new feature requests, new quality attribute requirements, changing technology, or other reasons. Whatever the causes, architecture evolution is commonplace in real-world software projects. Today’s software architects, however, have few techniques to help them plan such evolution. In particular, they have little assistance in planning alternatives, making trade-offs among these different alternatives, or applying best practices for particular domains. To address this, we have developed an approach for assisting architects in planning and reasoning about software architecture evolution. Our approach is based on modeling and analyzing potential evolution paths that represent different ways of evolving the system. We represent an evolution path as a sequence of transitional architectural states leading from the initial architecture to the target architecture, along with evolution operators that characterize the transitions among these states. We support analysis of evolution paths through the definition and application of constraints that express rules governing the evolution of the systemand evaluation functions that assess path quality. Finally, a set of these modeling elements may be grouped together into an evolution style that encapsulates a body of knowledge relevant to a particular domain of architecture evolution. We evaluate this approach in three ways. First, we evaluate its applicability to real-world architecture evolution projects. This is accomplished through case studies of two very different software organizations. Second, we undertake a formal evaluation of the computational complexity of verifying evolution constraints. Finally, we evaluate the implementability of the approach based on our experiences developing prototype tools for software architecture evolution.
Los estilos APA, Harvard, Vancouver, ISO, etc.
6

Hatch, Andrew. "Software architecture visualisation". Thesis, Durham University, 2004. http://etheses.dur.ac.uk/3040/.

Texto completo
Resumen
Tracing the history of software engineering reveals a series of abstractions. In early days, software engineers would construct software using machine code. As time progressed, software engineers and computer scientists developed higher levels of abstraction in order to provide tools to assist in building larger software systems. This has resulted in high-level languages, modelling languages, design patterns, and software architecture. Software architecture has been recognised as an important tool for designing and building software. Some research takes the view that the success or failure of a software development project depends heavily on the quality of the software architecture. For any software system, there are a number of individuals who have some interest in the architecture. These stakeholders have differing requirements of the software architecture depending on the role that they take. Stakeholders include the architects, designers, developers and also the sales, services and support teams and even the customer for the software. Communication and understanding of the architecture is essential in ensuring that each stakeholder can play their role during the design, development and deployment of that software system. Software visualisation has traditionally been focused on aiding the understanding of software systems by those who perform development and maintenance tasks on that software. In supporting developers and maintainers, software visualisation has been largely concerned with representing static and dynamic aspects of software at the code level. Typically, a software visualisation will represent control flow, classes, objects, import relations and other such low level abstractions of the software. This research identifies the fundamental issues concerning software architecture visualisation. It does this by identifying the practical use of software architecture in the real world, and considers the application of software visualisation techniques to the visualisation of software architecture. The aim of this research is to explore the ways in which software architecture visualisation can assist in the tasks undertaken by the differing stakeholders in a software system and its architecture. A prototype tool, named ArchVis, has been developed to enable the exploration of some of the fundamental issues in software architecture visualisation. ArchVis is a new approach to software architecture visualisation that is capable of utilising multiple sources and representations of architecture in order to generate multiple views of software architecture. The mechanism by which views are generated means that they can be more relevant to a wider collection of stakeholders in that architecture. During evaluation ArchVis demonstrates the capability of utilising a number of data sources in order to produce architecture visualisations. Arch Vis' view model is capable of generating the necessary views for architecture stakeholders and those stakeholders can navigate through the views and data in order to obtain relevant information. The results of evaluating ArchVis using a framework and scenarios demonstrate that the majority of the objectives of this research have been achieved.
Los estilos APA, Harvard, Vancouver, ISO, etc.
7

Pei, Breivold Hongyu. "Software Architecture Evolution and Software Evolvability". Licentiate thesis, Mälardalen University, School of Innovation, Design and Engineering, 2009. http://urn.kb.se/resolve?urn=urn:nbn:se:mdh:diva-4540.

Texto completo
Resumen

Software is characterized by inevitable changes and increasing complexity, which in turn may lead to huge costs unless rigorously taking into account change accommodations. This is in particular true for long-lived systems. For such systems, there is a need to address evolvability explicitly during the entire lifecycle, carry out software evolution efficiently and reliably, and prolong the productive lifetime of the software systems.

In this thesis, we study evolution of software architecture and investigate ways to support this evolution.           The central theme of the thesis is how to analyze software evolvability, i.e. a system’s ability to easily accommodate changes. We focus on several particular aspects: (i) what software characteristics are necessary to constitute an evolvable software system; (ii) how to assess evolvability in a systematic manner; (iii) what impacts need to be considered given a certain change stimulus that results in potential requirements the software architecture needs to adapt to, e.g. ever-changing business requirements and advances of technology.

To improve the capability in being able to on forehand understand and analyze systematically the impact of a change stimulus, we introduce a software evolvability model, in which subcharacteristics of software evolvability and corresponding measuring attributes are identified. In addition, a further study of one particular measuring attribute, i.e. modularity, is performed through a dependency analysis case study.

We introduce a method for analyzing software evolvability at the architecture level. This is to ensure that the implications of the potential improvement strategies and evolution path of the software architecture are analyzed with respect to the evolvability subcharacteristics. This method is proposed and piloted in an industrial setting.

The fact that change stimuli come from both technical and business perspectives spawns two aspects that we also look into in this research, i.e. to respectively investigate the impacts of technology-type and business-type of change stimuli.

Los estilos APA, Harvard, Vancouver, ISO, etc.
8

Svahnberg, Mikael. "Supporting Software Architecture Evolution". Doctoral thesis, Ronneby : Blekinge Institute of Technology, 2003. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-00232.

Texto completo
Resumen
Today it is more a rule than an exception that software systems have a lifecycle of more than several years. Hence, software evolution is inevitable. During the life span of a software system the domain in which the system is working evolves and changes. This causes changes to the software system, and the software system may also be evolved to satisfy new markets. The ability to evolve gracefully, and thus the long-term success of a software system, is to a large extent governed by its software architecture and the ability of the software architecture to fulfil requirements on quality attributes and to adapt to evolving requirements. In this thesis we study evolution of software architectures and what can be done to support this evolution. We focus on three particular aspects of evolution support: how to ensure that the correct blend of quality attributes is met (architecture selection), the technical means available for supporting changes in the software system (variability), and what types of changes that are likely to occur during evolution (categories of evolution). We introduce a method for architecture evaluation and selection that focus on ensuring that the selected software architecture is the architecture candidate with the most potential for fulfilling a particular blend of quality attributes. The method is based on quantification of expert opinions and focused discussions where these expert opinions differ. The architecture evaluation and selection method is studied in both an academic and in an industry setting. We also introduce a taxonomy of techniques for realising variability in a software system and study how the techniques in this taxonomy are applied in different evolution situations. The taxonomy is based on several industry case studies. Two industry cases are studied in further detail and the evolution of these systems are followed over a number of releases and generations. During this evolution it is shown how variability mechanisms are used to also support evolution, and that there are typical cases of evolution that a software system can be prepared to cope with. The contribution of this thesis is that it increases the understanding of how evolution occurs in a software system, how to create software that is flexible enough to support evolution and how to evaluate and select a software architecture that meets a particular blend of quality attributes. Together this ensures that a software system is based on a software architecture that fits the current quality requirements and that is flexible in the right places so that it is able to evolve gracefully.
Los estilos APA, Harvard, Vancouver, ISO, etc.
9

Tsamis, Alexandros 1976. "Software tectonics". Thesis, Massachusetts Institute of Technology, 2012. http://hdl.handle.net/1721.1/77777.

Texto completo
Resumen
Thesis (Ph. D. in Design and Computation)--Massachusetts Institute of Technology, Dept. of Architecture, 2012.
Cataloged from PDF version of thesis.
Includes bibliographical references (p. 365-370).
The resent shift of attention in the architectural discourse towards issues of ecological design, coupled with the undeniable role of computation, has already cast a new operative role to the notion of environment. Instead of being the passive, conceptualized or historicized context of an architectural object, environment is quite literally becoming the object of design itself. We are moving away from the imposed-preconceived Cartesian object which negotiates through its boundaries its presence within its immediate context. The discipline is already considering an architecture in which architectural form is only an instance of a designed environment. In many respects, this new understanding of environment aspires to be actively designed as a closed system of constant transformation, an autonomous milieu of exchange at all scales and all levels between substances, properties or qualities. The object of investigation in Software Tectonics is how technologies of design and construction allow newly forming propositions about the role of environment in the discipline to become operational tactics in the design practice. SOFTWARE TECTONICS proposes 3 design research projects. VSpace is a computer drawing application for designers. Unlike traditional CAD systems that work primarily by representing boundaries (B-reps), VSpace derives form by the representation and direct manipulation of properties (P-reps) in space. Boundaries and Properties here are considered simultaneously in the same design environment. Castit is a multi axis, Computer Numerically Controlled device that prints 3D objects by dynamically mixing at least two distinct but chemically compatible materials. Dynamic mixing allows for gradient transitions between two or more materials, resulting in objects with anisotropic material properties. CHUNK aims to eliminate a joint as a third mediating member between two building elements with an area of gradient transition. Conceived as a "dynamic insulation" architectural skin, this building technology project challenges the multi-trade and multi-component tectonics of dominant late-industrial building manufacture.
by Alexandros Tsamis.
Ph.D.in Design and Computation
Los estilos APA, Harvard, Vancouver, ISO, etc.
10

Ström, David. "Purposes of Software Architecture Design". Thesis, Blekinge Tekniska Högskola, Avdelningen för programvarusystem, 2005. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-2830.

Texto completo
Resumen
Software architecture design as an engineering field has evolved greatly during the last 15 years, which is evident by the number of methods, styles, patterns, and guidelines available for its practitioners in industry. This paper takes a closer look at the purposes behind this field to reveal the level of discrepancy in pursued purposes between industrial practitioners and published methods for software architecture design. In our research surveys of architecture design methods and of purposes at a number of industrial practitioners resulted in two sets of purposes which were eventually compared and the level of discrepancy identified.
Mjukvarudesign är ett område inom mjukvaruindustrin som utvecklats omfattande under de senaste 15 åren, vilket synliggjorts av de nya metoder, designstilar, designmönster och paradigmer som gjorts tillgängliga för mjukvaruutvecklare idag. Den här uppsatsen gör en djupgranskning av syftena bakom detta arbetsområde för att upptäcka eventuella skillnader mellan de syften som framhålls av befintliga arkitekturmetoder och de syften som åtsträvas av utövare inom mjukvaruindustrin.
Los estilos APA, Harvard, Vancouver, ISO, etc.
Más fuentes

Libros sobre el tema "Harware and software architecture"

1

Biffl, Stefan, Elena Navarro, Welf Löwe, Marjan Sirjani, Raffaela Mirandola y Danny Weyns, eds. Software Architecture. Cham: Springer International Publishing, 2021. http://dx.doi.org/10.1007/978-3-030-86044-8.

Texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.
2

Scandurra, Patrizia, Matthias Galster, Raffaela Mirandola y Danny Weyns, eds. Software Architecture. Cham: Springer International Publishing, 2022. http://dx.doi.org/10.1007/978-3-031-15116-3.

Texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.
3

Gerostathopoulos, Ilias, Grace Lewis, Thais Batista y Tomáš Bureš, eds. Software Architecture. Cham: Springer International Publishing, 2022. http://dx.doi.org/10.1007/978-3-031-16697-6.

Texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.
4

Drira, Khalil, ed. Software Architecture. Berlin, Heidelberg: Springer Berlin Heidelberg, 2013. http://dx.doi.org/10.1007/978-3-642-39031-9.

Texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.
5

Cuesta, Carlos E., David Garlan y Jennifer Pérez, eds. Software Architecture. Cham: Springer International Publishing, 2018. http://dx.doi.org/10.1007/978-3-030-00761-4.

Texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.
6

Weyns, Danny, Raffaela Mirandola y Ivica Crnkovic, eds. Software Architecture. Cham: Springer International Publishing, 2015. http://dx.doi.org/10.1007/978-3-319-23727-5.

Texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.
7

Lopes, Antónia y Rogério de Lemos, eds. Software Architecture. Cham: Springer International Publishing, 2017. http://dx.doi.org/10.1007/978-3-319-65831-5.

Texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.
8

Crnkovic, Ivica, Volker Gruhn y Matthias Book, eds. Software Architecture. Berlin, Heidelberg: Springer Berlin Heidelberg, 2011. http://dx.doi.org/10.1007/978-3-642-23798-0.

Texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.
9

Tekinerdogan, Bedir, Uwe Zdun y Ali Babar, eds. Software Architecture. Cham: Springer International Publishing, 2016. http://dx.doi.org/10.1007/978-3-319-48992-6.

Texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.
10

Bures, Tomas, Laurence Duchien y Paola Inverardi, eds. Software Architecture. Cham: Springer International Publishing, 2019. http://dx.doi.org/10.1007/978-3-030-29983-5.

Texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.
Más fuentes

Capítulos de libros sobre el tema "Harware and software architecture"

1

Gebhardt, Friedrich, Angi Voß, Wolfgang Gräther y Barbara Schmidt-Belz. "Software Architecture". En Reasoning with Complex Cases, 195–211. Boston, MA: Springer US, 1997. http://dx.doi.org/10.1007/978-1-4615-6233-7_18.

Texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.
2

Doornbos, Richard y Sjir van Loo. "Software Architecture". En From scientific instrument to industrial machine, 43–50. Dordrecht: Springer Netherlands, 2012. http://dx.doi.org/10.1007/978-94-007-4147-8_4.

Texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.
3

Dooley, John F. "Software Architecture". En Software Development, Design and Coding, 53–63. Berkeley, CA: Apress, 2017. http://dx.doi.org/10.1007/978-1-4842-3153-1_5.

Texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.
4

Budgen, David. "Software Architecture". En Software Design, 77–92. Third edition. | Boca Raton : CRC Press, 2021. | Series: Chapman & Hall/CRC innovations in software engineering: Chapman and Hall/CRC, 2020. http://dx.doi.org/10.1201/b21883-9.

Texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.
5

Jalote, Pankaj. "Software Architecture". En A Concise Introduction to Software Engineering, 1–26. London: Springer London, 2008. http://dx.doi.org/10.1007/978-1-84800-302-6_5.

Texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.
6

Dooley, John F. y Vera A. Kazakova. "Software Architecture". En Software Development, Design, and Coding, 145–60. Berkeley, CA: Apress, 2024. http://dx.doi.org/10.1007/979-8-8688-0285-0_7.

Texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.
7

Streekmann, Niels. "Software Architecture". En Clustering-Based Support for Software Architecture Restructuring, 9–22. Wiesbaden: Vieweg+Teubner Verlag, 2012. http://dx.doi.org/10.1007/978-3-8348-8675-0_2.

Texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.
8

Dooley, John. "Software Architecture". En Software Development and Professional Practice, 47–58. Berkeley, CA: Apress, 2011. http://dx.doi.org/10.1007/978-1-4302-3802-7_5.

Texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.
9

Laplante, Phillip A. y Mohamad Kassab. "Software Architecture". En What Every Engineer Should Know about Software Engineering, 91–112. 2a ed. Boca Raton: CRC Press, 2022. http://dx.doi.org/10.1201/9781003218647-5.

Texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.
10

Taylor, John T. y Wayne T. Taylor. "Software Architecture". En Patterns in the Machine, 63–82. Berkeley, CA: Apress, 2021. http://dx.doi.org/10.1007/978-1-4842-6440-9_5.

Texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.

Actas de conferencias sobre el tema "Harware and software architecture"

1

Garlan, David y Mary Shaw. "Software architecture". En the 19th ACM SIGSOFT symposium and the 13th European conference. New York, New York, USA: ACM Press, 2011. http://dx.doi.org/10.1145/2025113.2025116.

Texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.
2

Taylor, Richard N. "Software architecture". En the 7th joint meeting of the European software engineering conference and the ACM SIGSOFT symposium on The foundations of software engineering. New York, New York, USA: ACM Press, 2009. http://dx.doi.org/10.1145/1595696.1595754.

Texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.
3

Garlan, David. "Software architecture". En the conference. New York, New York, USA: ACM Press, 2000. http://dx.doi.org/10.1145/336512.336537.

Texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.
4

Anderson, Bruce, Mary Shaw, Larry Best y Kent Beck. "Software architecture". En the eighth annual conference. New York, New York, USA: ACM Press, 1993. http://dx.doi.org/10.1145/165854.165922.

Texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.
5

Medvidovic, Nenad y Richard N. Taylor. "Software architecture". En the 32nd ACM/IEEE International Conference. New York, New York, USA: ACM Press, 2010. http://dx.doi.org/10.1145/1810295.1810435.

Texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.
6

Masuda, Satoshi, Jon Hagar, Yasuharu Nishi y Kazuhiro Suzuki. "Software Test Architecture Definition by Analogy with Software Architecture". En 2022 IEEE International Conference on Software Testing, Verification and Validation Workshops (ICSTW). IEEE, 2022. http://dx.doi.org/10.1109/icstw55395.2022.00050.

Texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.
7

Emer, Joel. "Accelerating architecture research". En Software (ISPASS). IEEE, 2009. http://dx.doi.org/10.1109/ispass.2009.4919629.

Texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.
8

Anderson, Bruce, Mary Shaw, Larry Best y Kent Beck. "Software architecture (panel)". En Addendum to the proceedings. New York, New York, USA: ACM Press, 1993. http://dx.doi.org/10.1145/260303.260321.

Texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.
9

Bass, Len. "Software Architecture Design". En 2009 22nd Conference on Software Engineering Education and Training. IEEE, 2009. http://dx.doi.org/10.1109/cseet.2009.50.

Texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.
10

Davis, Margaret J. y Roger B. Williams. "Software architecture characterization". En the 1997 symposium. New York, New York, USA: ACM Press, 1997. http://dx.doi.org/10.1145/258366.258380.

Texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.

Informes sobre el tema "Harware and software architecture"

1

Khare, Rohit. Decentralized Software Architecture. Fort Belvoir, VA: Defense Technical Information Center, diciembre de 2002. http://dx.doi.org/10.21236/ada441133.

Texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.
2

Wood, William G., Mario Barbacci, Paul Clements, Steve Palmquist y Huei-Wan Ang. DoD Architecture Framework and Software Architecture Workshop Report. Fort Belvoir, VA: Defense Technical Information Center, marzo de 2003. http://dx.doi.org/10.21236/ada416453.

Texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.
3

Bachmann, Felix, Len Bass, Paul Clements, David Garlan y James Ivers. Documenting Software Architecture: Documenting Behavior. Fort Belvoir, VA: Defense Technical Information Center, enero de 2002. http://dx.doi.org/10.21236/ada399792.

Texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.
4

Bachmann, Felix, Len Bass, Paul Clements, David Garlan y James Ivers. Documenting Software Architecture: Documenting Interfaces. Fort Belvoir, VA: Defense Technical Information Center, junio de 2002. http://dx.doi.org/10.21236/ada403788.

Texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.
5

Hamilton, Jr, Murtagh John A. y Jeanne L. Enabling Interoperability Via Software Architecture. Fort Belvoir, VA: Defense Technical Information Center, enero de 2000. http://dx.doi.org/10.21236/ada458021.

Texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.
6

Clements, Paul C. y Linda M. Northrop. Software Architecture: An Executive Overview. Fort Belvoir, VA: Defense Technical Information Center, febrero de 1996. http://dx.doi.org/10.21236/ada305470.

Texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.
7

Clements, Paul C. Coming Attractions in Software Architecture. Fort Belvoir, VA: Defense Technical Information Center, enero de 1996. http://dx.doi.org/10.21236/ada309156.

Texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.
8

Bass, Len, Bonnie E. John y Jesse Kates. Achieving Usability Through Software Architecture. Fort Belvoir, VA: Defense Technical Information Center, marzo de 2001. http://dx.doi.org/10.21236/ada387874.

Texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.
9

Auguston, Mikhail. Software Architecture Built from Behavior Models. Fort Belvoir, VA: Defense Technical Information Center, junio de 2009. http://dx.doi.org/10.21236/ada502640.

Texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.
10

Berkbigler, K. P., B. W. Bush y J. F. Davis. TRANSIMS software architecture for IOC-1. Office of Scientific and Technical Information (OSTI), abril de 1997. http://dx.doi.org/10.2172/572673.

Texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.
También puede estar interesado en las bibliografías ampliadas sobre el tema "Harware and software architecture" para tipos de fuentes particulares:
Artículos de revistas Tesis Libros
Ofrecemos descuentos en todos los planes premium para autores cuyas obras están incluidas en selecciones literarias temáticas. ¡Contáctenos para obtener un código promocional único!

Pasar a la bibliografía