Gotowa bibliografia na temat „Software architecture”
Utwórz poprawne odniesienie w stylach APA, MLA, Chicago, Harvard i wielu innych
Spis treści
Zobacz listy aktualnych artykułów, książek, rozpraw, streszczeń i innych źródeł naukowych na temat „Software architecture”.
Przycisk „Dodaj do bibliografii” jest dostępny obok każdej pracy w bibliografii. Użyj go – a my automatycznie utworzymy odniesienie bibliograficzne do wybranej pracy w stylu cytowania, którego potrzebujesz: APA, MLA, Harvard, Chicago, Vancouver itp.
Możesz również pobrać pełny tekst publikacji naukowej w formacie „.pdf” i przeczytać adnotację do pracy online, jeśli odpowiednie parametry są dostępne w metadanych.
Artykuły w czasopismach na temat "Software architecture"
Sahlabadi, Mahdi, Ravie Chandren Muniyandi, Zarina Shukur i Faizan Qamar. "Lightweight Software Architecture Evaluation for Industry: A Comprehensive Review". Sensors 22, nr 3 (7.02.2022): 1252. http://dx.doi.org/10.3390/s22031252.
Pełny tekst źródłaWOODSIDE, C. M. "SOFTWARE RESOURCE ARCHITECTURE". International Journal of Software Engineering and Knowledge Engineering 11, nr 04 (sierpień 2001): 407–29. http://dx.doi.org/10.1142/s0218194001000608.
Pełny tekst źródłaMedvidovic, Nenad, Eric M. Dashofy i Richard N. Taylor. "The Role of Middleware in Architecture-Based Software Development". International Journal of Software Engineering and Knowledge Engineering 13, nr 04 (sierpień 2003): 367–93. http://dx.doi.org/10.1142/s0218194003001330.
Pełny tekst źródłaPonnala Gangadhar Adepu, Ramesh. "Modeling Software Architecture with UML". International Journal of Science and Research (IJSR) 1, nr 3 (5.03.2012): 21–26. http://dx.doi.org/10.21275/ijsr12120316.
Pełny tekst źródłaMcGregor, John D. "Software Architecture." Journal of Object Technology 3, nr 5 (2004): 65. http://dx.doi.org/10.5381/jot.2004.3.5.c7.
Pełny tekst źródłaAnderson, Bruce, Mary Shaw, Larry Best i Kent Beck. "Software architecture". ACM SIGPLAN Notices 28, nr 10 (październik 1993): 356–59. http://dx.doi.org/10.1145/167962.165922.
Pełny tekst źródłaRoško, Zdravko. "Business Applications Architecture Model Based on Software Product Line Approach". Research Papers Faculty of Materials Science and Technology Slovak University of Technology 21, Special-Issue (1.06.2013): 90–97. http://dx.doi.org/10.2478/rput-2013-0015.
Pełny tekst źródłaSarma, U. V. R., Neelakantam Pavani Pavani i P. Premchand. "Building Software Architecture using Architectural Design Patterns". International Journal of Science and Engineering Applications 2, nr 4 (1.04.2013): 71–77. http://dx.doi.org/10.7753/ijsea0204.1004.
Pełny tekst źródłaDonins, Uldis, i Janis Osis. "Reconciling software requirements and architectures within MDA". Scientific Journal of Riga Technical University. Computer Sciences 38, nr 38 (1.01.2009): 84–95. http://dx.doi.org/10.2478/v10143-009-0007-9.
Pełny tekst źródłaSarma, A. D. N. "A Generic Functional Architecture for Operational BI System". International Journal of Business Intelligence Research 9, nr 1 (styczeń 2018): 64–77. http://dx.doi.org/10.4018/ijbir.2018010105.
Pełny tekst źródłaRozprawy doktorskie na temat "Software architecture"
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.
Pełny tekst źródłaBy 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.
Mårtensson, Frans, i 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.
Pełny tekst źródłaBarnes, Jeffrey M. "Software Architecture Evolution". Research Showcase @ CMU, 2013. http://repository.cmu.edu/dissertations/291.
Pełny tekst źródłaHatch, Andrew. "Software architecture visualisation". Thesis, Durham University, 2004. http://etheses.dur.ac.uk/3040/.
Pełny tekst źródłaPei, 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.
Pełny tekst źródłaSoftware 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.
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.
Pełny tekst źródłaStrö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.
Pełny tekst źródłaMjukvarudesign ä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.
Cunningham, Hamish. "Software architecture for language engineering". Thesis, University of Sheffield, 2000. http://ethos.bl.uk/OrderDetails.do?uin=uk.bl.ethos.324440.
Pełny tekst źródłaWermelinger, Miguel Alexandre. "Specification of software architecture reconfiguration". Doctoral thesis, FCT - UNL, 1999. http://hdl.handle.net/10362/1137.
Pełny tekst źródłaAssociation for Computing Machinery PRAXIS XXI 2/2.1/MAT/46/94 Fundação Calouste Gulbenkian PRAXIS XXI PCEX/P/MAT/46/96 PRAXIS XXI 2/2.1/ TIT/1662/95
Väisänen, T. (Toni). "Applied software architecture on Graphingwiki". Bachelor's thesis, University of Oulu, 2017. http://urn.fi/URN:NBN:fi:oulu-201710042937.
Pełny tekst źródłaGraphingwiki laajentaa MoinMoin-wikiohjelmistoa tarjoamalla työkalut wikisivuston yhteyksien visualisoimiseen. Sitä on käytetty riippuvuuksien kartoitukseen yhteistyömenetelmissä. Graphingwiki voidaan katsoa ”legacy”-järjestelmäksi, koska dokumentaatiota ei ole saatavilla. Tämän työn ensisijainen fokus on sovellettussa ohjelmistoarkeologiassa nykyisen implementaation ymmärtämiseksi tukemaan päätöksentekoa sen suhteen, kuinka jatkokehitystä tulisi lähestyä. Järjestelmän yleisnäkymä kartoitettiin käyttämällä lähdekoodin suorituksen jäljitystä ja lukien koodia manuaalisesti. Graphingwikin graafigeneroinnin suorituskyky ja MoinMoinin käyttäjän luomis- sekä autentikaatiomenetelmät analysoitiin. Tulokset osoittavat, että Graphingwikin suorituskykyä heikentävä tekijä on generoitujen graafikuvien tallentaminen välimuistiin, mutta MoinMoinin käyttäjän luomis- ja autentikaatiomenetelmät ovat sekä käyttökelpoisia ja laajennettavia. Kaikilta näiltä osa-alueilta löytyi parannettavaa. Näiden tuloksien perusteella tiedetään, että ohittamalla generoitujen kuvien tallentaminen välimuistiin serverin vasteaikaa voitaisiin parantaa jopa 90%. MoinMoinin salasanojen vaatimukset olisi hyvä päivittää vastaamaan OWASP:n suosituksia. Jatkotutkimus olisi suositeltavaa nykyisten käyttäjien tarpeiden selvittämiseksi ja visualisoinnin tehokkaammaksi toteuttamiseksi
Książki na temat "Software architecture"
Biffl, Stefan, Elena Navarro, Welf Löwe, Marjan Sirjani, Raffaela Mirandola i Danny Weyns, red. Software Architecture. Cham: Springer International Publishing, 2021. http://dx.doi.org/10.1007/978-3-030-86044-8.
Pełny tekst źródłaScandurra, Patrizia, Matthias Galster, Raffaela Mirandola i Danny Weyns, red. Software Architecture. Cham: Springer International Publishing, 2022. http://dx.doi.org/10.1007/978-3-031-15116-3.
Pełny tekst źródłaGerostathopoulos, Ilias, Grace Lewis, Thais Batista i Tomáš Bureš, red. Software Architecture. Cham: Springer International Publishing, 2022. http://dx.doi.org/10.1007/978-3-031-16697-6.
Pełny tekst źródłaDrira, Khalil, red. Software Architecture. Berlin, Heidelberg: Springer Berlin Heidelberg, 2013. http://dx.doi.org/10.1007/978-3-642-39031-9.
Pełny tekst źródłaCuesta, Carlos E., David Garlan i Jennifer Pérez, red. Software Architecture. Cham: Springer International Publishing, 2018. http://dx.doi.org/10.1007/978-3-030-00761-4.
Pełny tekst źródłaWeyns, Danny, Raffaela Mirandola i Ivica Crnkovic, red. Software Architecture. Cham: Springer International Publishing, 2015. http://dx.doi.org/10.1007/978-3-319-23727-5.
Pełny tekst źródłaLopes, Antónia, i Rogério de Lemos, red. Software Architecture. Cham: Springer International Publishing, 2017. http://dx.doi.org/10.1007/978-3-319-65831-5.
Pełny tekst źródłaCrnkovic, Ivica, Volker Gruhn i Matthias Book, red. Software Architecture. Berlin, Heidelberg: Springer Berlin Heidelberg, 2011. http://dx.doi.org/10.1007/978-3-642-23798-0.
Pełny tekst źródłaTekinerdogan, Bedir, Uwe Zdun i Ali Babar, red. Software Architecture. Cham: Springer International Publishing, 2016. http://dx.doi.org/10.1007/978-3-319-48992-6.
Pełny tekst źródłaBures, Tomas, Laurence Duchien i Paola Inverardi, red. Software Architecture. Cham: Springer International Publishing, 2019. http://dx.doi.org/10.1007/978-3-030-29983-5.
Pełny tekst źródłaCzęści książek na temat "Software architecture"
Vogel, Oliver, Ingo Arnold, Arif Chughtai i Timo Kehrer. "Architectures and Architecture Disciplines (WHAT)". W Software Architecture, 39–64. Berlin, Heidelberg: Springer Berlin Heidelberg, 2011. http://dx.doi.org/10.1007/978-3-642-19736-9_3.
Pełny tekst źródłaGebhardt, Friedrich, Angi Voß, Wolfgang Gräther i Barbara Schmidt-Belz. "Software Architecture". W Reasoning with Complex Cases, 195–211. Boston, MA: Springer US, 1997. http://dx.doi.org/10.1007/978-1-4615-6233-7_18.
Pełny tekst źródłaDoornbos, Richard, i Sjir van Loo. "Software Architecture". W From scientific instrument to industrial machine, 43–50. Dordrecht: Springer Netherlands, 2012. http://dx.doi.org/10.1007/978-94-007-4147-8_4.
Pełny tekst źródłaDooley, John F. "Software Architecture". W Software Development, Design and Coding, 53–63. Berkeley, CA: Apress, 2017. http://dx.doi.org/10.1007/978-1-4842-3153-1_5.
Pełny tekst źródłaBudgen, David. "Software Architecture". W 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.
Pełny tekst źródłaJalote, Pankaj. "Software Architecture". W A Concise Introduction to Software Engineering, 1–26. London: Springer London, 2008. http://dx.doi.org/10.1007/978-1-84800-302-6_5.
Pełny tekst źródłaStreekmann, Niels. "Software Architecture". W 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.
Pełny tekst źródłaDooley, John. "Software Architecture". W Software Development and Professional Practice, 47–58. Berkeley, CA: Apress, 2011. http://dx.doi.org/10.1007/978-1-4302-3802-7_5.
Pełny tekst źródłaLaplante, Phillip A., i Mohamad Kassab. "Software Architecture". W What Every Engineer Should Know about Software Engineering, 91–112. Wyd. 2. Boca Raton: CRC Press, 2022. http://dx.doi.org/10.1201/9781003218647-5.
Pełny tekst źródłaTaylor, John T., i Wayne T. Taylor. "Software Architecture". W Patterns in the Machine, 63–82. Berkeley, CA: Apress, 2021. http://dx.doi.org/10.1007/978-1-4842-6440-9_5.
Pełny tekst źródłaStreszczenia konferencji na temat "Software architecture"
Cavalcante, Everton, i Thais Batista. "Using Software Architecture Descriptions to Detect Architectural Smells at Design Time". W Congresso Ibero-Americano em Engenharia de Software. Sociedade Brasileira de Computação, 2023. http://dx.doi.org/10.5753/cibse.2023.24697.
Pełny tekst źródłaE. U. Silva, Douglas, Roberto A. Bittencourt i Rodrigo T. Calumby. "Clustering Similarity Measures for Architecture Recovery of Evolving Software". W VII Workshop on Software Visualization. Sociedade Brasileira de Computação - SBC, 2019. http://dx.doi.org/10.5753/vem.2019.7583.
Pełny tekst źródłaGarlan, David, i Mary Shaw. "Software architecture". W 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.
Pełny tekst źródłaTaylor, Richard N. "Software architecture". W 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.
Pełny tekst źródłaGarlan, David. "Software architecture". W the conference. New York, New York, USA: ACM Press, 2000. http://dx.doi.org/10.1145/336512.336537.
Pełny tekst źródłaAnderson, Bruce, Mary Shaw, Larry Best i Kent Beck. "Software architecture". W the eighth annual conference. New York, New York, USA: ACM Press, 1993. http://dx.doi.org/10.1145/165854.165922.
Pełny tekst źródłaMedvidovic, Nenad, i Richard N. Taylor. "Software architecture". W the 32nd ACM/IEEE International Conference. New York, New York, USA: ACM Press, 2010. http://dx.doi.org/10.1145/1810295.1810435.
Pełny tekst źródłaSosa, Manuel E., Tyson Browning i Ju¨rgen Mihm. "Studying the Dynamics of the Architecture of Software Products". W ASME 2007 International Design Engineering Technical Conferences and Computers and Information in Engineering Conference. ASMEDC, 2007. http://dx.doi.org/10.1115/detc2007-34761.
Pełny tekst źródłaMasuda, Satoshi, Jon Hagar, Yasuharu Nishi i Kazuhiro Suzuki. "Software Test Architecture Definition by Analogy with Software Architecture". W 2022 IEEE International Conference on Software Testing, Verification and Validation Workshops (ICSTW). IEEE, 2022. http://dx.doi.org/10.1109/icstw55395.2022.00050.
Pełny tekst źródłaBlas, Maria Julia, Horacio P. Leone i Silvio M. Gonnet. "Building DEVS Models from the Functional Design of Software Architecture Components to Estimate Quality". W Workshop em Modelagem e Simulação de Sistemas Intensivos em Software. Sociedade Brasileira de Computação - SBC, 2020. http://dx.doi.org/10.5753/mssis.2020.12493.
Pełny tekst źródłaRaporty organizacyjne na temat "Software architecture"
Khare, Rohit. Decentralized Software Architecture. Fort Belvoir, VA: Defense Technical Information Center, grudzień 2002. http://dx.doi.org/10.21236/ada441133.
Pełny tekst źródłaBachmann, Felix, Len Bass, Jeromy Carriere, Paul Clements, David Garlan, James Ivers, Robert Nord i Reed Little. Software Architecture Documentation in Practice: Documenting Architectural Layers. Fort Belvoir, VA: Defense Technical Information Center, marzec 2000. http://dx.doi.org/10.21236/ada377988.
Pełny tekst źródłaWood, William G., Mario Barbacci, Paul Clements, Steve Palmquist i Huei-Wan Ang. DoD Architecture Framework and Software Architecture Workshop Report. Fort Belvoir, VA: Defense Technical Information Center, marzec 2003. http://dx.doi.org/10.21236/ada416453.
Pełny tekst źródłaBachmann, Felix, Len Bass, Paul Clements, David Garlan i James Ivers. Documenting Software Architecture: Documenting Behavior. Fort Belvoir, VA: Defense Technical Information Center, styczeń 2002. http://dx.doi.org/10.21236/ada399792.
Pełny tekst źródłaBachmann, Felix, Len Bass, Paul Clements, David Garlan i James Ivers. Documenting Software Architecture: Documenting Interfaces. Fort Belvoir, VA: Defense Technical Information Center, czerwiec 2002. http://dx.doi.org/10.21236/ada403788.
Pełny tekst źródłaHamilton, Jr, Murtagh John A. i Jeanne L. Enabling Interoperability Via Software Architecture. Fort Belvoir, VA: Defense Technical Information Center, styczeń 2000. http://dx.doi.org/10.21236/ada458021.
Pełny tekst źródłaClements, Paul C., i Linda M. Northrop. Software Architecture: An Executive Overview. Fort Belvoir, VA: Defense Technical Information Center, luty 1996. http://dx.doi.org/10.21236/ada305470.
Pełny tekst źródłaClements, Paul C. Coming Attractions in Software Architecture. Fort Belvoir, VA: Defense Technical Information Center, styczeń 1996. http://dx.doi.org/10.21236/ada309156.
Pełny tekst źródłaBass, Len, Bonnie E. John i Jesse Kates. Achieving Usability Through Software Architecture. Fort Belvoir, VA: Defense Technical Information Center, marzec 2001. http://dx.doi.org/10.21236/ada387874.
Pełny tekst źródłaAuguston, Mikhail. Software Architecture Built from Behavior Models. Fort Belvoir, VA: Defense Technical Information Center, czerwiec 2009. http://dx.doi.org/10.21236/ada502640.
Pełny tekst źródła