Relevant bibliographies by topics / Software architecture – Evaluation

Academic literature on the topic 'Software architecture – Evaluation'

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

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

Select a source type:

Contents

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

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

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

Journal articles on the topic "Software architecture – Evaluation"

1

Sobhy, Dalia, Rami Bahsoon, Leandro Minku, and Rick Kazman. "Evaluation of Software Architectures under Uncertainty." ACM Transactions on Software Engineering and Methodology 30, no. 4 (July 2021): 1–50. http://dx.doi.org/10.1145/3464305.

Full text
Abstract:
Context: Evaluating software architectures in uncertain environments raises new challenges, which require continuous approaches. We define continuous evaluation as multiple evaluations of the software architecture that begins at the early stages of the development and is periodically and repeatedly performed throughout the lifetime of the software system. Numerous approaches have been developed for continuous evaluation; to handle dynamics and uncertainties at run-time, over the past years, these approaches are still very few, limited, and lack maturity. Objective: This review surveys efforts on architecture evaluation and provides a unified terminology and perspective on the subject. Method: We conducted a systematic literature review to identify and analyse architecture evaluation approaches for uncertainty including continuous and non-continuous, covering work published between 1990–2020. We examined each approach and provided a classification framework for this field. We present an analysis of the results and provide insights regarding open challenges. Major results and conclusions: The survey reveals that most of the existing architecture evaluation approaches typically lack an explicit linkage between design-time and run-time. Additionally, there is a general lack of systematic approaches on how continuous architecture evaluation can be realised or conducted. To remedy this lack, we present a set of necessary requirements for continuous evaluation and describe some examples.
APA, Harvard, Vancouver, ISO, and other styles
2

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

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

LUNG, CHUNG-HORNG, and KALAI KALAICHELVAN. "AN APPROACH TO QUANTITATIVE SOFTWARE ARCHITECTURE SENSITIVITY ANALYSIS." International Journal of Software Engineering and Knowledge Engineering 10, no. 01 (February 2000): 97–114. http://dx.doi.org/10.1142/s0218194000000079.

Full text
Abstract:
Software architectures are often claimed to be robust. However, there is no explicit and concrete definition of software architecture robustness. This paper gives a definition of software architecture robustness and presents a set of architecture metrics that were applied to real-time telecommunications software for the evaluation of robustness. The purpose of this study is to provide a structured method to support software architecture evaluations and downstream software implementations. The study also expands the software architecture research to quantitative and measurable evaluations as opposed to qualitative assessments. In addition, this paper presents an empirical case study of applying the metrics. The approach and the metrics data provide insights into software architecture sensitivity analysis on system qualities and trade-off analysis among a set of design alternatives to support product evolution.
APA, Harvard, Vancouver, ISO, and other styles
4

Schmidt, Frederick, Stephen MacDonell, and Andy M. Connor. "Multi-Objective Reconstruction of Software Architecture." International Journal of Software Engineering and Knowledge Engineering 28, no. 06 (June 2018): 869–92. http://dx.doi.org/10.1142/s0218194018500262.

Full text
Abstract:
Design erosion is a persistent problem within the software engineering discipline. Software designs tend to deteriorate over time and there is a need for tools and techniques that support software architects when dealing with legacy systems. This paper presents an evaluation of a search-based software engineering (SBSE) approach intended to recover high-level architecture designs of software systems by structuring low-level artifacts into high-level architecture artifact configurations. In particular, this paper describes the performance evaluation of a number of metaheuristic search algorithms applied to architecture reconstruction problems with high dimensionality in terms of objectives. These problems have been selected as representative of the typical challenges faced by software architects dealing with legacy systems and the results inform the ongoing development of a software tool that supports the analysis of trade-offs between different reconstructed architectures.
APA, Harvard, Vancouver, ISO, and other styles
5

Tarvainen, Pentti. "Adaptability Evaluation at Software Architecture Level." Open Software Engineering Journal 2, no. 1 (September 25, 2008): 1–30. http://dx.doi.org/10.2174/1874107x00802010001.

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

Vishnyakov, Andrei, and Sergey Orlov. "Software Architecture and Detailed Design Evaluation." Procedia Computer Science 43 (2015): 41–52. http://dx.doi.org/10.1016/j.procs.2014.12.007.

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

Tsai, Jeffrey J. P., Bing Li, and Eric Y. T. Juan. "Parallel evaluation of software architecture specifications." Communications of the ACM 40, no. 1 (January 1997): 83–86. http://dx.doi.org/10.1145/242857.242881.

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

Shanmugapriya, P., and R. M. Suresh. "Software Architecture Evaluation Methods A Survey." International Journal of Computer Applications 49, no. 16 (July 28, 2012): 19–26. http://dx.doi.org/10.5120/7711-1107.

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

Wang, Alf Inge, and Bian Wu. "Using Game Development to Teach Software Architecture." International Journal of Computer Games Technology 2011 (2011): 1–12. http://dx.doi.org/10.1155/2011/920873.

Full text
Abstract:
This paper describes a case study of how a game project using the XNA Game Studio from Microsoft was implemented in a software architecture course. In this project, university students have to construct and design a type of software architecture, evaluate the architecture, implement an application based on the architecture, and test this implementation. In previous years, the domain of the software architecture project has been a robot controller for navigating a maze.Robot controllerwas chosen as the domain for the project, as there exist several papers and descriptions on reference architectures for managing mobile robots. This paper describes the changes we had to make to introduce an XNA game development project to the software architecture course, and our experiences from running a software architecture project focusing on game development and XNA. The experiences described in this paper are based on feedback from the course staff, the project reports of the students, and a mandatory course evaluation. The evaluation shows among other things that the majority of the students preferred the game project to the robot project, that XNA was considered to be suitable platform for a software architecture project, that the students found it useful to learn XNA and C#, and that some students were carried away when developing the game in the software architecture project.
APA, Harvard, Vancouver, ISO, and other styles
10

Venkitachalam, Hariharan, Christian Granrath, Balachandar Gopalakrishnan, and Johannes Richenhagen. "Metric-based Evaluation of Powertrain Software Architecture." SAE International Journal of Passenger Cars - Electronic and Electrical Systems 10, no. 1 (March 28, 2017): 194–208. http://dx.doi.org/10.4271/2017-01-1615.

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

Dissertations / Theses on the topic "Software architecture – Evaluation"

1

Mårtensson, Frans, and 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.

Full text
Abstract:
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.
APA, Harvard, Vancouver, ISO, and other styles
2

Shepperd, Martin John. "System architecture metrics : an evaluation." n.p, 1990. http://ethos.bl.uk/.

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

Zhu, Liming Computer Science &amp Engineering Faculty of Engineering UNSW. "Software architecture evaluation for framework-based systems." Awarded by:University of New South Wales. Computer Science and Engineering, 2007. http://handle.unsw.edu.au/1959.4/28250.

Full text
Abstract:
Complex modern software is often built using existing application frameworks and middleware frameworks. These frameworks provide useful common services, while simultaneously imposing architectural rules and constraints. Existing software architecture evaluation methods do not explicitly consider the implications of these frameworks for software architecture. This research extends scenario-based architecture evaluation methods by incorporating framework-related information into different evaluation activities. I propose four techniques which target four different activities within a scenario-based architecture evaluation method. 1) Scenario development: A new technique was designed aiming to extract general scenarios and tactics from framework-related architectural patterns. The technique is intended to complement the current scenario development process. The feasibility of the technique was validated through a case study. Significant improvements of scenario quality were observed in a controlled experiment conducted by another colleague. 2) Architecture representation: A new metrics-driven technique was created to reconstruct software architecture in a just-in-time fashion. This technique was validated in a case study. This approach has significantly improved the efficiency of architecture representation in a complex environment. 3) Attribute specific analysis (performance only): A model-driven approach to performance measurement was applied by decoupling framework-specific information from performance testing requirements. This technique was validated on two platforms (J2EE and Web Services) through a number of case studies. This technique leads to the benchmark producing more representative measures of the eventual application. It reduces the complexity behind the load testing suite and framework-specific performance data collecting utilities. 4) Trade-off and sensitivity analysis: A new technique was designed seeking to improve the Analytical Hierarchical Process (AHP) for trade-off and sensitivity analysis during a framework selection process. This approach was validated in a case study using data from a commercial project. The approach can identify 1) trade-offs implied by an architecture alternative, along with the magnitude of these trade-offs. 2) the most critical decisions in the overall decision process 3) the sensitivity of the final decision and its capability for handling quality attribute priority changes.
APA, Harvard, Vancouver, ISO, and other styles
4

Shepperd, Martin John. "System architecture metrics : an evaluation." Thesis, Open University, 1991. http://oro.open.ac.uk/57340/.

Full text
Abstract:
The research described in this dissertation is a study of the application of measurement, or metrics for software engineering. This is not in itself a new idea; the concept of measuring software was first mooted close on twenty years ago. However, examination of what is a considerable body of metrics work, reveals that incorporating measurement into software engineering is rather less straightforward than one might pre-suppose and despite the advancing years, there is still a lack of maturity. The thesis commences with a dissection of three of the most popular metrics, namely Haistead's software science, McCabe's cyclomatic complexity and Henry and Kafura's information flow - all of which might be regarded as having achieved classic status. Despite their popularity these metrics are all flawed in at least three respects. First and foremost, in each case it is unclear exactly what is being measured: instead there being a preponderance of such metaphysical terms as complexIty and qualIty. Second, each metric is theoretically doubtful in that it exhibits anomalous behaviour. Third, much of the claimed empirical support for each metric is spurious arising from poor experimental design, and inappropriate statistical analysis. It is argued that these problems are not misfortune but the inevitable consequence of the ad hoc and unstructured approach of much metrics research: in particular the scant regard paid to the role of underlying models. This research seeks to address these problems by proposing a systematic method for the development and evaluation of software metrics. The method is a goal directed, combination of formal modelling techniques, and empirical ealiat%or. The met\io s applied to the problem of developing metrics to evaluate software designs - from the perspective of a software engineer wishing to minimise implementation difficulties, faults and future maintenance problems. It highlights a number of weaknesses within the original model. These are tackled in a second, more sophisticated model which is multidimensional, that is it combines, in this case, two metrics. Both the theoretical and empirical analysis show this model to have utility in its ability to identify hardto- implement and unreliable aspects of software designs. It is concluded that this method goes some way towards the problem of introducing a little more rigour into the development, evaluation and evolution of metrics for the software engineer.
APA, Harvard, Vancouver, ISO, and other styles
5

Borowski, Jimmy. "Software Architecture Simulation : Performance evaluation during the design phase." Thesis, Blekinge Tekniska Högskola, Institutionen för programvaruteknik och datavetenskap, 2004. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-5882.

Full text
Abstract:
Due to the increasing size and complexity of software systems, software architectures have become a crucial part in development projects. A lot of effort has been put into defining formal ways for describing architecture specifications using Architecture Description Languages (ADLs). Since no common ADL today offers tools for evaluating the performance, an attempt to develop such a tool based on an event-based simulation engine has been made. Common ADLs were investigated and the work was based on the fundamentals within the field of software architectures. The tool was evaluated both in terms of correctness in predictions as well as usability to show that it actually is possible to evaluate the performance using high-level architectures as models.
APA, Harvard, Vancouver, ISO, and other styles
6

Mårtensson, Frans. "Software architecture quality evaluation : approaches in an industrial context /." Karlskrona : Blekinge Institute of Technology, 2006. http://www.bth.se/fou/Forskinfo.nsf/allfirst2/3e821fbd7a66542cc1257169002ad63c?OpenDocument.

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

Mårtensson, Frans. "Software Architecture Quality Evaluation : Approaches in an Industrial Context." Licentiate thesis, Karlskrona : Blekinge Institute of Technology, 2006. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-00313.

Full text
Abstract:
Software architecture has been identified as an increasingly important part of software development. The software architecture helps the developer of a software system to define the internal structure of the system. Several methods for evaluating software architectures have been proposed in order to assist the developer in creating a software architecture that will have a potential to fulfil the requirements on the system. Many of the evaluation methods focus on evaluation of a single quality attribute. However, in an industrial system there are normally requirements on several quality aspects of the system. Therefore, an architecture evaluation method that addresses multiple quality attributes, e.g., performance, maintainability, testability, and portability, would be more beneficial. This thesis presents research towards a method for evaluation of multiple quality attributes using one software architecture evaluation method. A prototype-based evaluation method is proposed that enables evaluation of multiple quality attributes using components of a system and an approximation of its intended runtime environment. The method is applied in an industrial case study where communication components in a distributed realtime system are evaluated. The evaluation addresses performance, maintainability, and portability for three alternative components using a single set of software architecture models and a prototype framework. The prototype framework enables the evaluation of different components and component configurations in the software architecture while collecting data in an objective way. Finally, this thesis presents initial work towards incorporating evaluation of testability into the method. This is done through an investigation of how testability is interpreted by different organizational roles in a software developing organization and which measures of source code that they consider affecting testability.
APA, Harvard, Vancouver, ISO, and other styles
8

Graser, Thomas Jeffrey. "Reference architecture representation environment (RARE) : systematic derivation and evaluation of domain-specific, implementation-independent software architectures /." Access restricted to users with UT Austin EID Full text (PDF) from UMI/Dissertation Abstracts International, 2001. http://wwwlib.umi.com/cr/utexas/fullcit?p3023549.

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

Zapalowski, Vanius. "Evaluation of code-based information to architectural module identification." reponame:Biblioteca Digital de Teses e Dissertações da UFRGS, 2014. http://hdl.handle.net/10183/94691.

Full text
Abstract:
Arquitetura de software desempenha um importante papel no desenvolvimento de software, quando explicitamente documentada, ela melhora o entendimento sobre o sistema implementado e torna possível entender a forma com que requisitos não funcionais são tratados. Apesar da relevância da arquitetura de software, muitos sistemas não possuem uma arquitetura documentada, e nos casos em que a arquitetura existe, ela pode estar desatualizada por causa da evolução descontrolada do software. O processo de recuperação de arquitetura de um sistema depende principalmente do conhecimento que as pessoas envolvidas com o software tem. Isso acontece porque a recuperação de arquitetura é uma tarefa que demanda muita investigação manual do código fonte. Pesquisas sobre recuperação de arquitetura objetivam auxiliar esse processo. A maioria dos métodos de recuperação existentes são baseados em dependência entre elementos da arquitetura, padrões arquiteturais ou similaridade semântica do código fonte. Embora as abordagem atuais ajudem na identi cação de módulos arquiteturais, os resultados devem ser melhorados de forma signi cativa para serem considerados con áveis. Então, nesta dissertação, objetivamos melhorar o suporte a recuperação de arquitetura explorando diferentes fontes de informação e técnicas de aprendizado de máquina. Nosso trabalho consiste de uma análise, considerando cinco estudo de casos, da utilidade de usar um conjunto de características de código (features, no contexto de aprendizado de máquina) para agrupar elementos em módulos da arquitetura. Atualmente não são conhecidas as características que afetam a identificação de papéis na arquitetura de software. Por isso, nós avaliamos a relação entre diferentes conjuntos de características e a acurácia obtida por um algoritmo não supervisionado na identificação de módulos da arquitetura. Consequentemente, nós entendemos quais dessas características revelam informação sobre a organização de papéis do código fonte. Nossa abordagem usando características de elementos de software atingiu uma acurácia média significativa. Indicando a relevância das informações selecionadas para recuperar a arquitetura. Além disso, nós desenvolvemos uma ferramenta para auxílio ao processo de recuperação de arquitetura de software. Nossa ferramenta tem como principais funções a avaliação da recuperação de arquitetura e apresentação de diferentes visualizações arquiteturais. Para isso, apresentamos comparações entre a arquitetura concreta e a arquitetura sugerida.
Software architecture plays an important role in the software development, and when explicitly documented, it allows understanding an implemented system and reasoning about how non-functional requirements are addressed. In spite of that, many developed systems lack proper architecture documentation, and if it exists, it may be outdated due to software evolution. The process of recovering the architecture of a system depends mainly on developers' knowledge requiring a manual inspection of the source code. Research on architecture recovery provides support to this process. Most of the existing approaches are based on architectural elements dependency, architectural patterns or source code semantics, but even though they help identifying architectural modules, the obtained results must be signi cantly improved to be considered reliable. We thus aim to support this task by the exploitation of di erent code-oriented information and machine learning techniques. Our work consists of an analysis, involving ve case studies, of the usefulness of adopting a set of code-level characteristics (or features, in the machine learning terminology) to group elements into architectural modules. The characteristics mainly source code metrics that a ect the identi cation of what role software elements play in software architecture are unknown. Then, we evaluate the relationship between di erent sets of characteristics and the accuracy achieved by an unsupervised algorithm the Expectation Maximization in identifying architectural modules. Consequently, we are able to understand which of those characteristics reveal information about the source code structure. By the use of code-oriented information, our approach achieves a signi cant average accuracy, which indicates the importance of the selected information to recover software architecture. Additionally, we provide a tool to support research on architecture recovery providing software architecture measurements and visualizations. It presents comparisons between predicted architectures and concrete architectures.
APA, Harvard, Vancouver, ISO, and other styles
10

Hawley, Jeffrey Allan. "Software architecture of the non-rigid image registration evaluation project." Thesis, University of Iowa, 2011. https://ir.uiowa.edu/etd/1229.

Full text
Abstract:
In medical image registration the goal is to find point by point correspondences between a source image and a target image such that the two images are aligned. There are rigid and non-rigid registration algorithms. Rigid registration uses rigid transformation methods which preserve distances between every pair of points. Non-rigid registration uses transformation methods that do not have to preserve the distances. Image registration has many medical applications -tracking tumors, anatomical changes over time, differences between characteristics like age and gender, etc. A gold standard transformation to compare and evaluate the registration algorithms would be ideal to use to verify if the two images are perfectly aligned. However, there is hardly if ever a gold standard transformation for non-rigid registration algorithms. The reason why there is no gold standard transformation for non-rigid registration algorithms is that pointwise correspondence between two registered points is not unique. In the absence of a gold standard various evaluation methods are used to gauge registration performance. However, each evaluation method only evalutes the error in the transformation from a limited perspective and therefore has its advantages and drawbacks. The Non-Rigid Image Registration Evaluation Project (NIREP) was was created to provide one central tool that has a collection of evaluation methods to perform the evaluations on non-rigid image registration algorithms and rank the registration algorithms based on the outputs of the evaluation methods in the absence of without having to use a gold standard.
APA, Harvard, Vancouver, ISO, and other styles
More sources

Books on the topic "Software architecture – Evaluation"

1

Semegn, Assefa D. Software architecture and design for reliability and predictability. Newcastle upon Tyne: Cambridge Scholars, 2012.

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

Knodel, Jens, and Matthias Naab. Pragmatic Evaluation of Software Architectures. Cham: Springer International Publishing, 2016. http://dx.doi.org/10.1007/978-3-319-34177-4.

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

Office, General Accounting. Weather forecasting: Systems architecture needed for national weather service modernization : report to Congressional requesters. Washington, D.C: The Office, 1994.

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

International Workshop on Development and Evolution of Software Architectures for Product Families (2nd 1998 Las Palmas (Canary Islands)). Development and evolution of software architectures for product families: Second international ESPRIT ARES workshop, Las Palmas de Gran Canaria, Spain, February 26-27, 1998 : proceedings. Berlin: Springer, 1998.

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

Jürgen, Kazmeier, Breu Ruth, Atkinson Colin, and SpringerLink (Online service), eds. Model Driven Engineering Languages and Systems: 15th International Conference, MODELS 2012, Innsbruck, Austria, September 30–October 5, 2012. Proceedings. Berlin, Heidelberg: Springer Berlin Heidelberg, 2012.

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

Misra, H. K. The role of software architectures in managing citizen-centric e-governance initiatives in India: An evaluation framework. Anand: Institute of Rural Management Anand, 2012.

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

Office, General Accounting. Information technology: Architecture needed to guide NASA's financial management modernization : report to congressional requesters. Washington, D.C. (P.O. Box 37050, Washington 20013): U.S. General Accounting Office, 2003.

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

Office, General Accounting. Information technology: Enterprise architecture use across the federal government can be improved : report to congressional committees. Washington, D.C: The Office, 2002.

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

Office, General Accounting. Information technology: FBI needs an enterprise architecture to guide its modernization activities : report to congressional requesters. Washington, D.C: U.S. General Accounting Office, 2003.

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

Office, General Accounting. Information technology: Leadership remains key to agencies making progress on enterprise architecture efforts : report to Congressional Requesters. Washington, D.C: GAO, 2003.

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

Book chapters on the topic "Software architecture – Evaluation"

1

Li, Zhao, and Jiang Zheng. "Toward Industry Friendly Software Architecture Evaluation." In Software Architecture, 328–31. Berlin, Heidelberg: Springer Berlin Heidelberg, 2013. http://dx.doi.org/10.1007/978-3-642-39031-9_31.

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

Eloranta, Veli-Pekka, and Kai Koskimies. "Using Domain Knowledge to Boost Software Architecture Evaluation." In Software Architecture, 319–26. Berlin, Heidelberg: Springer Berlin Heidelberg, 2010. http://dx.doi.org/10.1007/978-3-642-15114-9_24.

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

Bode, Stephan, and Matthias Riebisch. "Impact Evaluation for Quality-Oriented Architectural Decisions regarding Evolvability." In Software Architecture, 182–97. Berlin, Heidelberg: Springer Berlin Heidelberg, 2010. http://dx.doi.org/10.1007/978-3-642-15114-9_15.

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

Knodel, Jens, and Matthias Naab. "Why Architecture Evaluation?" In Pragmatic Evaluation of Software Architectures, 3–10. Cham: Springer International Publishing, 2016. http://dx.doi.org/10.1007/978-3-319-34177-4_1.

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

Zhu, Liming, Muhammad Ali Babar, and Ross Jeffery. "Distilling Scenarios from Patterns for Software Architecture Evaluation – A Position Paper." In Software Architecture, 225–29. Berlin, Heidelberg: Springer Berlin Heidelberg, 2004. http://dx.doi.org/10.1007/978-3-540-24769-2_19.

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

Stol, Klaas-Jan, Paris Avgeriou, and Muhammad Ali Babar. "Design and Evaluation of a Process for Identifying Architecture Patterns in Open Source Software." In Software Architecture, 147–63. Berlin, Heidelberg: Springer Berlin Heidelberg, 2011. http://dx.doi.org/10.1007/978-3-642-23798-0_15.

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

Knodel, Jens, and Matthias Naab. "What Is Architecture Evaluation?" In Pragmatic Evaluation of Software Architectures, 21–34. Cham: Springer International Publishing, 2016. http://dx.doi.org/10.1007/978-3-319-34177-4_3.

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

Cruz, Pablo, Luis Salinas, and Hernán Astudillo. "Quick Evaluation of a Software Architecture Using the Decision-Centric Architecture Review Method: An Experience Report." In Software Architecture, 281–95. Cham: Springer International Publishing, 2020. http://dx.doi.org/10.1007/978-3-030-58923-3_19.

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

Züllighoven, Heinz, Carola Lilienthal, and Marcel Bennicke. "Software Architecture Analysis and Evaluation." In Quality of Software Architectures, 7–8. Berlin, Heidelberg: Springer Berlin Heidelberg, 2006. http://dx.doi.org/10.1007/11921998_5.

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

Dueñas, Juan C., William L. de Oliveira, and Juan A. de la Puente. "A Software Architecture Evaluation Model." In Lecture Notes in Computer Science, 148–57. Berlin, Heidelberg: Springer Berlin Heidelberg, 1998. http://dx.doi.org/10.1007/3-540-68383-6_22.

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

Conference papers on the topic "Software architecture – Evaluation"

1

Abrahão, Silvia, and Emilio Insfran. "Evaluating Software Architecture Evaluation Methods." In EASE'17: Evaluation and Assessment in Software Engineering. New York, NY, USA: ACM, 2017. http://dx.doi.org/10.1145/3084226.3084253.

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

"SOFTWARE ARCHITECTURE EVALUATION APPROACH." In 1st International Conference on Agents and Artificial Intelligence. SciTePress - Science and and Technology Publications, 2009. http://dx.doi.org/10.5220/0001665503530356.

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

Shahmohammadi, Gholamreza. "Reliability Evaluation of Software Architecture Styles." In Sixth International conference on Computer Science and Information Technology. Academy & Industry Research Collaboration Center (AIRCC), 2016. http://dx.doi.org/10.5121/csit.2016.60111.

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

Windhorst, Robert, Larry Meyn, Vikram Manikonda, Patrick Carlos, and Brian Capozzi. "The Airspace Concept Evaluation Software Architecture." In AIAA Guidance, Navigation, and Control Conference and Exhibit. Reston, Virigina: American Institute of Aeronautics and Astronautics, 2006. http://dx.doi.org/10.2514/6.2006-6231.

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

Lamouchi, Olfa, Amar Ramdan-Cherif, and Nicole Levy. "Adaptable evaluation approach for software architecture." In the 9th International Conference. New York, New York, USA: ACM Press, 2008. http://dx.doi.org/10.1145/1500879.1500898.

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

Duszynski, Slawomir, Jens Knodel, and Mikael Lindvall. "SAVE: Software Architecture Visualization and Evaluation." In 2009 13th European Conference on Software Maintenance and Reengineering. IEEE, 2009. http://dx.doi.org/10.1109/csmr.2009.52.

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

E. U. Silva, Douglas, Roberto A. Bittencourt, and Rodrigo T. Calumby. "Clustering Similarity Measures for Architecture Recovery of Evolving Software." In VII Workshop on Software Visualization. Sociedade Brasileira de Computação - SBC, 2019. http://dx.doi.org/10.5753/vem.2019.7583.

Full text
Abstract:
Automated software architecture recovery of module views from source code is a challenging research issue. Different similarity measures are used to evaluate clustering algorithms in the software architecture recovery of module views. However, few studies seek to evaluate whether such measures accurately capture the similarities between two clusterings. This work presents an evaluation of six clustering similarity measures through the use of intrinsic quality and stability measures and the use of ground truth architectures proposed by developers. The results suggest that the MeCl metric is the most adequate to measure similarity in the context of comparison with ground truth models provided by developers. However, when the architectural models do not exist, the Purity metric shows the best results, as measured by the correlation with the intrinsic Silhouette coefficient.
APA, Harvard, Vancouver, ISO, and other styles
8

Pérez-Castillo, Ricardo, Benedikt Mas, and Markus Pizka. "Understanding Legacy Architecture Patterns." In 10th International Conference on Evaluation of Novel Software Approaches to Software Engineering. SCITEPRESS - Science and and Technology Publications, 2015. http://dx.doi.org/10.5220/0005467302820288.

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

Knodel, Jens, and Matthias Naab. "Software Architecture Evaluation in Practice: Retrospective on More Than 50 Architecture Evaluations in Industry." In 2014 IEEE/IFIP Conference on Software Architecture (WICSA). IEEE, 2014. http://dx.doi.org/10.1109/wicsa.2014.37.

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

Bass, Len, and Robert L. Nord. "Understanding the Context of Architecture Evaluation Methods." In 2012 Joint Working IEEE/IFIP Conference on Software Architecture (WICSA) & European Conference on Software Architecture (ECSA). IEEE, 2012. http://dx.doi.org/10.1109/wicsa-ecsa.212.45.

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

Reports on the topic "Software architecture – Evaluation"

1

Mao, Song, and Tapas Kanungo. Software Architecture of PSET: A Page Segmentation Evaluation Toolkit. Fort Belvoir, VA: Defense Technical Information Center, September 2000. http://dx.doi.org/10.21236/ada453815.

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

Bergey, John K., Matthew J. Fisher, Lawrence G. Jones, and Rick Kazman. Software Architecture Evaluation with ATAM in the DoD System Acquisition Context. Fort Belvoir, VA: Defense Technical Information Center, September 1999. http://dx.doi.org/10.21236/ada377450.

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

Barbacci, Mario R., Mark H. Klein, and Charles B. Weinstock. Principles for Evaluating the Quality Attributes of a Software Architecture. Fort Belvoir, VA: Defense Technical Information Center, March 1997. http://dx.doi.org/10.21236/ada324233.

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

To the bibliography