Tesis sobre el tema "Software architecture evaluation and design"
Siga este enlace para ver otros tipos de publicaciones sobre el tema: Software architecture evaluation and design.
Crea una cita precisa en los estilos APA, MLA, Chicago, Harvard y otros
Consulte los 50 mejores tesis para su investigación sobre el tema "Software architecture evaluation and design".
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.
Explore tesis sobre una amplia variedad de disciplinas y organice su bibliografía correctamente.
1
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.
Texto completoResumen
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.
2
Wnukiewicz, Karol Kazimierz. "The role of quality requirements in software architecture design". Thesis, Blekinge Tekniska Högskola, Avdelningen för programvarusystem, 2006. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-2253.
Texto completoResumen
An important issue during architectural design is that besides functional requirements, software architecture is influenced greatly by quality requirements [9][2][7], which often are neglected. The earlier quality requirements are considered, the less effort is needed later in the software lifecycle to ensure a sufficient software quality levels. Errors due to lack of their fulfilment are the most expensive and difficult to correct. Therefore, attention to quality requirements is crucial during an architectural design. The problem is not only to gather the system’s quality requirements, but to establish a methodology that helps to deal with them during the software development. Literature has paid some attention to software architecture in the context of quality requirements, but there is still lack of effective solutions in this area. To alleviate the problem, this paper lays out important concepts and notions of quality requirements in a way they can be used to drive design decisions and evaluate the architecture to estimate whether these requirements are fulfilled. Important concepts of software architecture area are presented to indicate how important quality requirements are during the design and what are the consequences of their lack in a software system. Moreover, a quality requirement-oriented design method is proposed as an outcome of the literature survey. This method is a model taking quality requirements into account at first, before the core functionality is placed. Besides the conceptual solution to the identified problems, this paper also suggests a practical method of handling quality requirements during a design. A recommendation framework for choosing the most suitable architectural pattern from a set of quality attributes is also proposed. Since the literature provides insufficient qualitative information about quality requirement issues in terms of software architectures, an empirical research is conducted as means for gathering the required data. Therefore, a systematic approach to support and analyze architectural designs in terms of quality requirements is prepared. Finally, quality requirement-oriented and pattern-based design method is further proposed as a result of investigating patterns as a tool for addressing quality requirements at different abstraction levels of a design. The research is concerned with the analysis of software architectures against one or more desired software qualities that ought to be achieved at the architectural level.http://wnukiewicz.pl kareel@gmail.com
3
AL, Halbouni Hadi y Frank Hansen. "A Scenario-Based evaluation of Game Architecture". Thesis, Blekinge Tekniska Högskola, Institutionen för programvaruteknik, 2020. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-20241.
Texto completoResumen
When developers or organizations need to develop a game, simulation or a similar project, they phase the question of whether or not to use a game engine as well as the question on which one to use. Are all game engines the same or does the architecture change and how is the game design different between various game engines? The objective of this thesis is to research these questions as well as giving a concrete understanding of the impact of picking one engine over the other and how each engine influences the way games are developed and answer some more specific questions regarding architecture and usability. A project was designed with the goal of developing a game. This game was developed by two separate teams over a period of 6 weeks, using two different game engines. The development was split into separate iterations done simultaneously between the teams and questionnaires were filled in to gather data. The game engines used for projects had similarities but also things which were different. Each engine offered ways to speed up development by allowing the developer to reuse and distribute changes among objects to reduce work. The differences caused one engine’s code architecture to be more complex than the other while allowing a better code structure as well as adding more time to learn how the engine handles certain things such as collisions. In conclusion, there is an importance to properly evaluating different game engines depending on the project a developer or organization is creating, not evaluating this properly will impact development speed and project complexity. Even though each engine has their differences, there is no superior game engine as it all depends on the project being developed. The game developed for this project was only touching on certain areas related to 2D games.
4
Tyan, Hung-ying. "Design, realization and evaluation of a component-based compositional software architecture for network simulation /". The Ohio State University, 2002. http://rave.ohiolink.edu/etdc/view?acc_num=osu1486402544591791.
Texto completo
5
Roßbach, André Christian. "Evaluation of Software Architectures in the Automotive Domain for Multicore Targets in regard to Architectural Estimation Decisions at Design Time". Master's thesis, Universitätsbibliothek Chemnitz, 2015. http://nbn-resolving.de/urn:nbn:de:bsz:ch1-qucosa-163372.
Texto completoResumen
In this decade the emerging multicore technology will hit the automotive industry. The increasing complexity of the multicore-systems will make a manual verification of the safety and realtime constraints impossible. For this reason, dedicated methods and tools are utterly necessary, in order to deal with the upcoming multicore issues. A lot of researchprojects for new hardware platforms and software frameworks for the automotive industry are running nowadays, because the paradigms of the “High-Performance Computing” and “Server/Desktop Domain” cannot be easily adapted for the embedded systems. One of the difficulties is the early suitability estimation of a hardware platform for a software architecture design, but hardly a research-work is tackling that. This thesis represents a procedure to evaluate the plausibility of software architecture estimations and decisions at design stage. This includes an analysis technique of multicore systems, an underlying graph-model – to represent the multicore system – and a simulation tool evaluation. This can guide the software architect, to design a multicore system, in full consideration of all relevant parameters and issuesIn den nächsten Jahren wird die aufkommende Multicore-Technologie auf die Automobil-Branche zukommen. Die wachsende Komplexität der Multicore-Systeme lässt es nicht mehr zu, die Verifikation von Sicherheits- und Echtzeit-Anforderungen manuell auszuführen. Daher sind spezielle Methoden und Werkzeuge zwingend notwendig, um gerade mit den bevorstehenden Multicore-Problemfällen richtig umzugehen. Heutzutage laufen viele Forschungsprojekte für neue Hardware-Plattformen und Software-Frameworks für die Automobil-Industrie, weil die Paradigmen des “High-Performance Computings” und der “Server/Desktop-Domäne” nicht einfach so für die Eingebetteten Systeme angewendet werden können. Einer der Problemfälle ist das frühe Erkennen, ob die Hardware-Plattform für die Software-Architektur ausreicht, aber nur wenige Forschungs-Arbeiten berücksichtigen das. Diese Arbeit zeigt ein Vorgehens-Model auf, welches ermöglicht, dass Software-Architektur Abschätzungen und Entscheidungen bereits zur Entwurfszeit bewertet werden können. Das beinhaltet eine Analyse Technik für Multicore-Systeme, ein grundsätzliches Graphen-Model, um ein Multicore-System darzustellen, und eine Simulatoren Evaluierung. Dies kann den Software-Architekten helfen, ein Multicore System zu entwerfen, welches alle wichtigen Parameter und Problemfälle berücksichtigt
6
Al-Naeem, Tariq Abdullah Computer Science & Engineering Faculty of Engineering UNSW. "A quality-driven decision-support framework for architecting e-business applications". Awarded by:University of New South Wales. Computer Science and Engineering, 2006. http://handle.unsw.edu.au/1959.4/23419.
Texto completoResumen
Architecting e-business applications is a complex design activity. This is mainly due to the numerous architectural decisions to be made, including the selection of alternative technologies, software components, design strategies, patterns, standards, protocols, platforms, etc. Further complexities arise due to the fact that these alternatives often vary considerably in their support for different quality attributes. Moreover, there are often different groups of stakeholders involved, with each having their own quality goals and criteria. Furthermore, different architectural decisions often include interdependent alternatives, where the selection of one alternative for one particular decision impacts the selections to be made for alternatives from other different decisions. There have been several research efforts aiming at providing sufficient mechanisms and tools for facilitating the architectural evaluation and design process. These approaches, however, address architectural decisions in isolation, where they focus on evaluating a limited set of alternatives belonging to one architectural decision. This has been the primary motivation behind the development of the Architectural DEcision-Making Support (ADEMS) framework, which basically aims at supporting stakeholders and architects during the architectural decision-making process by helping them determining a suitable combination of architectural alternatives. ADEMS framework is an iterative process that leverages rigorous quantitative decision-making techniques available in the literature of Management Science, particularly Multiple Attribute Decision-Making (MADM) methods and Integer Programming (IP). Furthermore, due to the number of architectural decisions involved as well as the variety of available alternatives, the architecture design space is expected to be huge. For this purpose, a query language has been developed, known as the Architecture Query Language (AQL), to aid architects in exploring and analyzing the design space in further depth, and also in examining different ???what-if??? architectural scenarios. In addition, in order to support leveraging ADEMS framework, a support tool has been implemented for carrying out the sophisticated set of mathematical computations and comparisons of the large number of architectural combinations, which might otherwise be hard to conduct using manual techniques. The primary contribution of the tool is in its help to identify, evaluate, and rank all potential combinations of alternatives based on their satisfaction to quality preferences provided by the different stakeholders. Finally, to assess the feasibility of ADEMS, three different case studies have been conducted relating to the architectural evaluation of different e-business and enterprise applications. Results obtained for the three case studies were quite positive as they showed an acceptable accuracy level for the decisions recommended by ADEMS, and at a reasonable time and effort costs for the different system stakeholders.
7
Johansson, Gustav. "Investigating differences in response time and error rate between a monolithic and a microservice based architecture". Thesis, KTH, Skolan för elektroteknik och datavetenskap (EECS), 2019. http://urn.kb.se/resolve?urn=urn:nbn:se:kth:diva-264840.
Texto completoResumen
With great advancements in cloud computing, the microservice architecture has become a promising architectural style for enterprise software. It has been proposed to cope with problems of the traditional monolithic architecture which includes slow release cycles, limited scalability and low developer productivity. Therefore, this thesis aims to investigate the affordances and challenges of adopting microservices as well as the difference in performance compared to the monolithic approach at one of Sweden’s largest banks, SEB - the Scandinavian Individual Bank. The investigation consisted of a literature study of research papers and official documentation of microservices. Moreover, two applications were developed and deployed using two different system architectures - a monolithic architecture and a microservice architecture. Performance tests were executed on both systems to gather quantitative data for analysis. The two metrics investigated in this study were response time and error rate. The results indicate the microservice architecture has a significantly higher error rate but a slower response time than the monolithic approach, further strengthening the results of Ueda et. al. [47] and Villamizar et. al. [48]. The findings have then been discussed with regards to the challenges and complexity involved in implementing distributed systems. From this study, it becomes clear the complexity shifts from inside the application out towards infrastructure with a microservice architecture. Therefore, microservices should not be seen as a silver bullet. Rather, the type of architecture is highly dependent on the scope of the project and the size of the organization.Med stora framstegen inom molntjänster har microservice arkitekturen kommit att bli en lämplig kandidat för utveckling av företagsprogramvara. Denna typ av systemarkitektur har föreslagits att lösa de problem som den traditionella monolitiska arkitekturen medför; långsamma lanseringar, begränsad skalbarhet och låg produktivitet. Således fokuserar denna avhandling på att utforska de möjligheter samt utmaningar som följer vid adoptering av microservices samt skillnaden i prestanda jämfört med den monolitiska arkitekturen. Detta undersöktes på en av Sveriges största banker, SEB, den Skandinaviska Enskilda Banken. Utredningen bestod av en litteraturstudie av vetenskapliga artiklar samt officiell dokumentation för microservices. Dessutom utvecklades och lanserades två applikationer byggt med två olika typer av systemarkitektur - en som monolitisk arkitektur och den andra som en microservice arkitektur. Prestandatest utfördes sedan på båda systemen för att samla kvantitativ data för analys. De två nyckelvardena som undersöktes i denna studie var responstid och felfrekvens. Resultaten indikerar att microservice arkitekturen har en signifikant högre felfrekvens men en långsammare responstid än den monolitiska arkitekturen, vilket stärker resultaten av Ueda et. al. [47] och Villamizar et. al. [48]. Forskningsresultaten har diskuterats med hänsyn till den komplexitet och de utmaningar som följer vid implementering av distribuerade system. Från denna studie blir det tydligt att komplexiteten i en microservice arkitektur skiftar från inuti applikationen ut till infrastrukturen. Således borde microservices inte ses som en silverkula. Istället är valet av systemarkitektur strikt beroende på omfattningen av projektet samt storleken på organisationen i fråga.
8
Johansson, Per y Henric Holmberg. "On the Modularity of a System". Thesis, Malmö högskola, Teknik och samhälle, 2010. http://urn.kb.se/resolve?urn=urn:nbn:se:mau:diva-20183.
Texto completoResumen
Den här uppsatsen behandlar skapandet och designen av en arkitektur över ett system för behandling av depression och andra psykiska sjukdomar via internet, kallat Melencolia. Ett av kraven för detta projekt är att skapa ett system som kan utökas i framtiden. Vi har härlett detta krav till begreppet modularitet och för att skapa en modulär arkitektur för Melencolia har vi undersökt vad begreppet innebär och härlett det till att vara ett kvalitetsdrag hos flera kvalitetsattribut däribland ”maintainability” och ”reusability”. Med hjälp av ”Attribute Driven Design” kan en arkitektur skapas som fokuserar kring en viss typ av kvalitetsattribut. Eftersom modularitet inte är ett kvalitetsattribut utan en kvalitetsegenskap har vi varit tvungna att ändra indata till denna metod, från kvalitetsattribut till kvalitetsegenskap. Vidare har vi härlett och lagt fram en ny metod för att mäta kvalitetsegenskaper i en mjukvaruarkikektur.Slutligen har vi använt vår metod för att mäta graden av modularitet i Melencolias arkitektur.This thesis considers the problem of creating and designing an architecture for a software project that will result in a system for treatment of depression on the Internet. One of the requirements for this project, named by Melencolia, is to create a system which can be extended in the future. From this requirement we have derived the concept of modularity. In order to create a modular architecture we have concluded that modularity is a quality characteristic of multiple quality attributes such as "maintainability" and "reusability".We deploy Attribute-Driven Design (ADD) in this Melencolia project. By doing this, an architecture that is focused around modularity can be created. Since modularity is not a quality attribute, but rather a quality characteristic, we had to change the input to ADD from a quality attribute to a quality characteristic.Furthermore, we derive and propose a new method for quality characteristic evaluation of software architectures.Finally we apply our aforementioned method on the architecture of Melencolia and by doing this we get an indication on how well our proposed architecture satisfies modularity.
9
Toresson, Gabriel. "Documenting and Improving the Design of a Large-scale System". Thesis, Linköpings universitet, Programvara och system, 2019. http://urn.kb.se/resolve?urn=urn:nbn:se:liu:diva-157733.
Texto completoResumen
As software systems become increasingly larger and more complex, the need to make them easily maintained increases, as large systems are expected to last for many years. It has been estimated that system maintenance is a large part of many IT-departments’ software development costs. In order to design a complex system to be maintainable it is necessary to introduce structure, often as models in the form of a system architecture and a system design. As development of complex large-scale systems progresses over time, the models may need to be reconstructed. Perhaps because development may have diverted from the initial plan, or because changes had to be made during implementation. This thesis presents a reconstructed documentation of a complex large-scale system, as well as suggestions for how to improve the existing design based on identified needs and insufficiencies. The work was performed primarily using a qualitative manual code review approach of the source code, and the proposal was generated iteratively. The proposed design was evaluated and it was concluded that it does address the needs and insufficiencies, and that it can be realistically implemented.
10
Pereira, Carlos Eduardo da Silva. "Dynamic evaluation for reactive scenarios". Doctoral thesis, Universidade de Aveiro, 2016. http://hdl.handle.net/10773/18043.
Texto completoResumen
Doutoramento em InformáticaA natureza dinâmica de cenários como Ambient Assisting Living e ambientes pervasivos e ubíquos criam contextos de avaliação exigentes que não são completamente considerados pelos métodos existentes. Esta tese defende que são possíveis avaliações que tenham em consideração a natureza dinâmica e heterogénea de ambientes reactivos, integrando aspectos como percepção e dependência de contexto, adaptabilidade ao utilizador, gestão de eventos complexos e diversidade de ambientes. O principal objectivo deste trabalho foi desenvolver uma solução que forneça aos avaliadores a possibilidade de definir e aplicar avaliações a utilizadores suportadas por um modelo de avaliação flexível, permitindo a criação e reutilização de instrumentos e especificações de avaliação sem modificar a infraestrutura geral. Para atingir este objectivo foi seguida uma abordagem de engenharia envolvendo: a) definição de requisitos; b) conceptualização de uma solução geral contendo um paradigma, uma metodologia, um modelo e uma arquitectura; c) implementação dos componentes nucleares; d) desenvolvimento e teste de provas de conceito. Como resultado principal obteve-se uma solução de avaliação dinâmica para ambientes reactivos integrando três partes essenciais: um paradigma, uma metodologia e uma arquitectura de suporte. No seu conjunto, esta solução permite a criação de sistemas de avaliação escaláveis, flexíveis e modulares para concepção de avaliações e aplicação em ambientes reactivos.
The dynamic nature of scenarios such as Ambient Assisting Living and Ubiquitous and Pervasive environments turns them into challenging evaluation contexts not properly addressed by existing methods. We argue that it is possible to have evaluations that take into consideration the dynamic and heterogeneous nature of reactive environments by integrating aspects such as context-awareness, user adaptability, complex event handling, and environment diversity. In this context, the main objective of this work was to develop a solution providing evaluators with the ability to de ne and apply evaluation tests to end-users supported by a exible evaluation model allowing them to create or reuse evaluation instruments and speci cations without changing the infrastructure or the need for other logistical necessities. To pursue this goal, we adopted an engineering approach encompassing: a) requirements de nition; b) conceptualization of a general solution comprising paradigm, methodology, model, and architecture; c) implementation of its core components; and d) development and deployment of a proof of concept. The result was a dynamic evaluation solution for reactive environments based on three major parts: a paradigm, a methodology and its model, and a support architecture. Altogether, they enable the creation of scalable, exible and modular evaluation systems for evaluation design and application in reactive environments. Overall, we consider that the proposed approach, due to its exibility and scope, widely surpasses the goals considered on the onset of this work. With a broad range of features it establishes itself as a general purpose evaluation solution, potentially applicable to a wider range of scenarios, and fostering the creation of ubiquitous and continuous evaluation systems.
11
Hamada, Skander. "Design and evaluation of a visual rapid prototyping environment in an existing smart home platform". Thesis, Malmö högskola, Fakulteten för teknik och samhälle (TS), 2017. http://urn.kb.se/resolve?urn=urn:nbn:se:mau:diva-20267.
Texto completoResumen
Recent advances in the field of Internet of Things (IoT) are placing its own vision, as a platform of interconnected services and devices, at the heart of the smart home concept. This consolidation promises a new wave of innovative products designed in the open, and in which the user takes center stage starting from the very first steps. Therefore, researchers as well as product designers in these increasingly related fields are now tasked with a more complex mission when investigating user behavior. In this thesis we consider rapid prototyping as the upcoming standard process for investigating user interactions in the future smart home. Although past research contributed with several self-contained solutions (built from scratch) to allow such investigations, no accounts were found tackling the problem from our perspective, in which the focus is on how to enable rapid prototyping in an existing proprietary smart home platform by using open standards, software and hardware. To answer this question, we conducted our research with participation of academic researchers and professional designers in the context of an academic and industrial partnership, in an ongoing smart home research project. We used an approach based on the design science research process in combination with the user centered design (UCD) and agile software development methodologies. During this thesis we performed an end to end design process starting from ideation to implementation and evaluation; an architectural blueprint was proposed and a working prototype of our visual smart home rapid prototyping environment (SHRPE) was implemented and tested. The obtained results demonstrate the feasibility of enabling visual rapid prototyping capabilities in an existing smart home platform, by using the system integration process to introduce available open standards, software and hardware tools into the platform. In addition, evaluation results of user testing confirmed that using UCD to iteratively capture user needs in such complex context is a solid approach.
12
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 completoResumen
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.
13
Shepperd, Martin John. "System architecture metrics : an evaluation". n.p, 1990. http://ethos.bl.uk/.
Texto completo
14
Zhu, Liming Computer Science & 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.
Texto completoResumen
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.
15
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 completoResumen
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.
16
Shepperd, Martin John. "System architecture metrics : an evaluation". Thesis, Open University, 1991. http://oro.open.ac.uk/57340/.
Texto completoResumen
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.
17
Cronje, Johannes Jacobus. "Software architecture design of a software defined radio system". Thesis, Stellenbosch : Stellenbosch University, 2004. http://hdl.handle.net/10019.1/50095.
Texto completoResumen
Thesis (MScEng)--University of Stellenbosch, 2004.ENGLISH ABSTRACT: The high pace of technological advancement enables the realisation of ever more advanced mobile communications standards with more functionality than simple voice communications. The hardware that is used to implement the radio sections of these systems generally require long design cycles, much longer than the design cycles of the other components of a communications system. Another problem is that, once new communications standards are introduced, the current hardware platforms used in the terminal equipment becomes obsolete because they can generally not be used with the new standards. This has serious cost implications for both the service provider and the consumer, because both parties have to acquire new equipment to be able to use the new standards. An elegant solution to the above issues is to use software-defined radio sections to replace the hardware radio components. New communications standards can then be supported by simply loading new software onto the equipment, provided the maximum processing capacity of the processor(s) that the software runs on can accommodate the bandwidth requirements of that specific standard. This thesis investigates the ideas behind software defined radio and also describes the design and implementation of a software architecture that can be used to implement software defined radios on general-purpose platforms such as personal computers.
AFRIKAANSE OPSOMMING: Die hoë tempo van tegnologiese vordering maak dit moontlik om baie gevorderde mobiele kommunikasie standaarde te implementeer wat meer funksionaliteit bied as blote spraakkommunikasie. Die hardeware wat gebruik word om die radios van sulke stelsels te implementeer neem gewoonlik langer om te ontwikkel as die ander komponente van die stelsels. Die ander probleem is dat hierdie hardeware gewoonlik nie hergebruik kan word wanneer nuwe kommunikasie standaarde in gebruik geneem word nie omdat die standaarde nie versoenbaar is nie. Dit het tot gevolg dat beide die verbruiker en die diensverskaffer groot bedrae geld moet spandeer om die nuwe tegnologie te kan gebruik. 'n Elegante oplossing vir hierdie probleme is om gebruik te maak van radios waarvan die funksionaliteit in sagteware gedefiniëer word. Nuwe kommunikasie standaarde kan dan gebruik word deur slegs die nodige sagteware op die toerusting te laai, solank die verwerkingskapasiteit van die mikroverwerkers in die stelsel die benodigde bandwydte kan akkommodeer. Hierdie tesis ondersoek die konsepte van sagteware-gedefiniëerde radio en beskryf die ontwerp en implementering van 'n sagteware argitektuur vir die implementering van sagteware-gedefiniëerde radios op veeldoelige platforms soos persoonlike rekenaars.
18
Mourikas, George. "Reconfigurable software communication architecture : design implementation". Thesis, Lancaster University, 2011. http://ethos.bl.uk/OrderDetails.do?uin=uk.bl.ethos.531709.
Texto completo
19
Perovich, Gerosa Daniel. "Model-Based systematization of software architecture design". Tesis, Universidad de Chile, 2014. http://repositorio.uchile.cl/handle/2250/131098.
Texto completoResumen
Doctor en Ciencias, Mención ComputaciónLa Arquitectura de Software juega un rol crucial en la Ingeniería de Software, permitiendo el control intelectual, la integridad conceptual, la comunicación efectiva, la administración de un conjunto relacionado de variantes de sistemas, y la reutilización de conocimiento, experiencia, diseño e implementación. Aplicar el conocimiento arquitectónico promueve la calidad, reduce los riesgos, y es esencial para alcanzar las expectativas de los interesados con resultados predecibles. El conocimiento arquitectónico actual es vasto y está en constante aumento, pero a su vez, es heterogéneo y disperso, está expresado en diferentes niveles de abstracción y rigor, y requiere de herramientas que raramente están disponibles en los ambientes de desarrollo. En la práctica, el diseño arquitectónico está limitado por las habilidades y experiencia del arquitecto y por el conocimiento que domina, y requiere de gran esfuerzo para ajustarlo y adaptarlo al escenario de desarrollo. Así, el diseño arquitectónico rara vez alcanza el nivel de calidad que es posible dado el conocimiento arquitectónico disponible. Además, el esfuerzo del arquitecto no es repetible ya que resultan embebidos en las descripciones de las arquitecturas. Aunque las técnicas de modelado están siendo usadas en Arquitectura de Software, la mayoría de los enfoques carecen de generalidad y homogeneidad, dificultando su integración y aplicación. En este trabajo, usamos megamodelado para definir un mecanismo unificado y homogéneo para capturar conocimiento arquitectónico, haciéndolo compartible, reusable, manejable por herramientas, y directamente aplicable. Definimos una interpretación formal de los conceptos principales de la disciplina en términos de artefactos de modelado. Además, cambiamos el foco de construir la descripción de la arquitectura directamente, a capturar cómo dicha descripción es creada. Para ello, definimos un lenguaje para capturar las acciones de diseño, y lo interpretamos en términos de técnicas de modelado haciendo el diseño repetible. Validamos nuestro enfoque definiendo procedimientos para guiar a la comunidad en cómo capturar conocimiento arquitectónico usando nuestra interpretación formal, aplicando estos procedimientos para capturar las técnicas de descripción y diseño del SEI, y aplicando el conocimiento capturado al diseño de la línea de productos de mallas geométricas. Nuestro trabajo realiza dos contribuciones originales. Primero, definimos un mecanismo unificado y homogéneo para capturar conocimiento arquitectónico, usando técnicas de Ingeniería Dirigida por Modelos, particularmente el enfoque de megamodelado Global Model Management, y usando semántica denotacional para la formalización. Segundo, definimos una representación de decisiones y soluciones arquitectónicas en términos de un lenguaje específico, haciéndolas descriptivas y aplicables. Así, facilitamos el cambio de foco del arquitecto haciendo el diseño arquitectónico explícito, repetible y reusable, y obteniendo descripciones de arquitectura implícitas y generables en forma automática.
20
Kumar, Nadella Navin. "Evaluation of ISDS software". Master's thesis, This resource online, 1991. http://scholar.lib.vt.edu/theses/available/etd-01262010-020122/.
Texto completo
21
Colman, Alan Wesley. "Role oriented adaptive design". Australasian Digital Thesis Program, 2006. http://adt.lib.swin.edu.au/public/adt-VSWT20070320.110756/index.html.
Texto completoResumen
Thesis (Ph.D) - Swinburne University of Technology, Faculty of Information & Communication Technologies, 2006."October 2006". Submitted in fulfillment of the requirements of for the degree of Doctor of Philosophy, Faculty of Information and Communication Technologies, Swinburne University of Technology, 2006. Typescript. Includes bibliographical references (p. [229]-237) and index.
22
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.
Texto completoResumen
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.
23
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.
Texto completo
24
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.
Texto completoResumen
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.
25
Vickers, Andrew J. "Computational architecture : a step towards predictable software design". Thesis, University of York, 1994. http://ethos.bl.uk/OrderDetails.do?uin=uk.bl.ethos.239830.
Texto completo
26
Verminski, Matthew D. (Matthew David) 1974. "A distributed software architecture for semiconductors process design". Thesis, Massachusetts Institute of Technology, 1998. http://hdl.handle.net/1721.1/47433.
Texto completoResumen
Thesis (M.S.)--Massachusetts Institute of Technology, Dept. of Electrical Engineering and Computer Science, 1998.Includes bibliographical references (leaves 67-68).
by Matthew D. Verminski.
M.S.
27
Tang, Antony Shui Sum. "A rationale-based model for architecture design reasoning". Australasian Digital Thesis Program, 2007. http://adt.lib.swin.edu.au/public/adt-VSWT20070319.100952/index.html.
Texto completoResumen
Thesis (Ph.D) - Swinburne University of Technology, Faculty of Information & Communication Technologies, 2007.A thesis submitted in total fulfillment of the requirements of for the degree of Doctor of Philosophy, Faculty of ICT, Swinburne University of Technology, 2007. Typescript. Bibliography p. 214-226.
28
Lotz, Steven E. "Developing a comprehensive software environment for passive solar design". Thesis, Massachusetts Institute of Technology, 1985. http://hdl.handle.net/1721.1/75957.
Texto completoResumen
Thesis (M.S.)--Massachusetts Institute of Technology, Dept. of Architecture, 1985.MICROFICHE COPY AVAILABLE IN ARCHIVES AND ROTCH.
Includes bibliographical references.
This thesis is a journal which describes the thoughts and decisions leading up to the final design of a comprehensive software environment for passive solar design. The main purpose of this writing is to convey why a comprehensive software environment for this particular field is needed in order to help teach the principles of passive solar design, so that they can be adequately taken into consideration in the architectural design process, and how such a system could be implemented. A case study involving the use of previously available passive solar design tools is used to point out areas where these tools are deficient in their ability to focus a designer's attention on pertinent building performance simulation data, which could be more effectively used to influence design decisions at the various stages of the design process. This leads to a discussion of how these shortcomings could be overcome through a new and different software design strategy which utilizes a systems approach to build a more flexible and powerful passive solar design tool. Through further experiments, practical considerations and real-world constraints are brought to light, and how they affected the conceptual development of such a system which I undertook to develop here at MIT for Project Athena. Next, certain implementation details are given which seek to bridge the gap between conceptual goals and practical software design considerations. How the internal organization of software code affects the external interactions between the user and the system, and how it can promote the qualities needed for software survival in an educational setting is addressed . Finally, the outcome of an experimental prototype for this s y stem is discussed, as well as my concluding thoughts regarding what I have learned through this endeavor about writing architectural design tool software.
by Steven E. Lotz.
M.S.
29
Hawley, Jeffrey Allan. "Software architecture of the non-rigid image registration evaluation project". Thesis, University of Iowa, 2011. https://ir.uiowa.edu/etd/1229.
Texto completoResumen
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.
30
Ameller, David. "Non-functional requirements as drivers of software architecture design". Doctoral thesis, Universitat Politècnica de Catalunya, 2014. http://hdl.handle.net/10803/144942.
Texto completoResumen
In the last decades, software engineering has become an important area of research. As researchers, we try to identify a problem, a need, or a hole in some research topic, once identified we make an effort to produce new techniques, methods, and tools that hopefully will help to improve the detected issue. In the present thesis the identified issue was the need of supporting non-functional requirements in the software architecture design where these requirements are the drivers of the architectural decision-making.
This thesis started with the idea that a relatively new software engineering discipline, model-driven development, was a good place to propose a solution for the detected issue. We envisioned how non-functional requirements can be integrated in model-driven development and how this integration will impact in the architectural design activities.
When we started to produce our techniques, methods, and tools for model-driven development we found out that there was a bigger hole in the web of knowledge than what we had initially foreseen. Much of the evidence of how non-functional requirements affect the software architecture design is hidden. This situation caused a turn in this thesis: we needed to understand architects, how they think and how they make the architectural decisions, what is the role of non-functional requirements in the architectural decision-making process, and to what extent are the non-functional requirements important in this process. All these questions needed an answer, an answer that only architects could provide. In consequence we opted to drove several empirical studies to answer these questions.
In parallel, we started to work in a way of representing this knowledge, an ontology for software architecture that integrates non-functional requirements. Using this ontology as basis, we designed a method to assist architects in the architectural decision-making process and a tool that acted as a proof of concept of both, the ontology and the method.
In summary, this thesis explores how non-functional requirements are currently integrated in the software architecture design practices, and proposes ways to improve this integration and facilitate the work of architects by providing means to assist them in the architectural decision-making process.
31
Mogatala, Harshavardhan Reddy. "Secure software architecture design for multidatab[a]se system". Thesis, National Library of Canada = Bibliothèque nationale du Canada, 2001. http://www.collectionscanada.ca/obj/s4/f2/dsk3/ftp04/MQ56140.pdf.
Texto completo
32
Krishnamurthy, Likhita. "Comparative Assessment of Network-Centric Software Architectures". Thesis, Virginia Tech, 2006. http://hdl.handle.net/10919/32377.
Texto completoResumen
The purpose of this thesis is to characterize, compare and contrast four network-centric software architectures, namely Client-Server Architecture (CSA), Distributed Objects Architecture (DOA), Service-Oriented Architecture (SOA) and Peer-to-Peer Architecture (PPA) and seven associated frameworks consisting of .NET, Java EE, CORBA, DCOM, Web Services, Jini and JXTA with respect to a set of derived criteria. Network-centric systems are gaining in popularity as they have the potential to solve more complex problems than we have been able to in the past. However, with the rise of SOA, Web Services, a set of standards widely used for implementing service-oriented solutions, is being touted as the â silver bulletâ to all problems afflicting the software engineering domain with the danger of making other architectures seem obsolete. Thus, there is an urgent need to study the various architectures and frameworks in comparison to each other and understand their relative merits and demerits for building network-centric systems.
The architectures studied here were selected on the basis of their fundamentality and generality. The frameworks were chosen on the basis of their popularity and representativeness to build solutions in a particular architecture. The criteria used for comparative assessment are derived from a combination of two approaches â by a close examination of the unique characteristics and requirements of network-centric systems and then by an examination of the constraints and mechanisms present in the architectures and frameworks under consideration that may contribute towards realizing the requirements of network-centric systems. Not all of the criteria are equally relevant for the architectures and frameworks. Some, when relevant, are relevant in a different sense from one architecture (or framework) to another.
One of the conclusions that can be drawn from this study is that the different architectures are not completely different from each other. In fact, CSA, DOA and SOA are a natural evolution in that order and share several characteristics. At the same time, significant differences do exist, so it is clearly possible to judge/differentiate one from the other. All three architectures can coexist in a single system or system of systems. However, the advantages of each architecture become apparent only when they are used in their proper scope. At the same time, a sharp difference can be perceived between these three architectures and the peer-to-peer architecture. This is because PPA aims to solve a totally different class of problems than the other three architectures and hence has certain unique characteristics not observed in the others. Further, all of the frameworks have certain unique architectural features and mechanisms not found in the others that contribute towards achieving network-centric quality characteristics. The two broad frameworks, .NET and Java EE offer almost equivalent capabilities and features; what can be achieved in one can be achieved in the other.
This thesis deals with the study of all the four architectures and their related frameworks. The criteria used, while fairly comprehensive, are not exhaustive. Variants of the fundamental architectures are not considered. However, system/software architects seeking an understanding of the tradeoffs involved in using the various architectures and frameworks and their subtle nuances should benefit considerably from this work.Master of Science
33
Low, Kian Wai. "Software Communications Architecture (SCA) compliant software defined radio design for IEEE 802.16 wirelessman-OFDMtm transceiver". Thesis, Monterey, Calif. : Naval Postgraduate School, 2006. http://bosun.nps.edu/uhtbin/hyperion.exe/06Dec%5FLow.pdf.
Texto completoResumen
Thesis (M.S. in Electrical Engineering)--Naval Postgraduate School, December 2006.Thesis Advisor(s): Frank Kragh. "December 2006." Includes bibliographical references (p. 71-72). Also available in print.
34
Dellarocas, Chrysanthos 1967. "A coordinate perspective on software architecture : towards a design handbook for integrating software components". Thesis, Massachusetts Institute of Technology, 1996. http://hdl.handle.net/1721.1/11292.
Texto completoResumen
Thesis (Ph. D.)--Massachusetts Institute of Technology, Dept. of Electrical Engineering and Computer Science, 1996.Includes bibliographical references (p. 282-288).
by Chrysanthos Nicholas Dellarocas.
Ph.D.
35
Williams, Daniel Dee. "Design analysis techniques for software quality enhancement". Online access for everyone, 2007. http://www.dissertations.wsu.edu/Thesis/Summer2007/d_williams_072407.pdf.
Texto completo
36
Heintz, Matthias Martin. "Software-supported participatory design : design and evaluation of the tool PDot". Thesis, University of Leicester, 2017. http://hdl.handle.net/2381/40659.
Texto completoResumen
Participatory Design (PD) is a common software development approach that actively includes end-users in the design process. This ensures tailored results and can lead to a strong feeling of ownership and overall empowers end-users. Commonly applied paper-based PD approaches have several shortcomings. A prototype presented on paper is not interactive for the end-user to experience it. Preparing PD ideas captured as physical artefacts (e.g. sketches on acetates) for further data analysis can be unduly time consuming. Using software tools to conduct PD activities instead of relying on paper-based methods can address these shortcomings. The author has been motivated to design, develop, and evaluate two such tools - PDotCapturer and PDotAnalyser. PDotCapturer is used by end-users participating in PD activities to create new designs from scratch or express (re-)design ideas. PDotAnalyser is used by designers to work with and further analyse the ideas captured. PDotCapturer is compared with similar paper-based approaches to evaluate the relative effectiveness of tool-based and paper-based PD activities in terms of quantity and quality of design ideas elicited. To perform this comparison, the coding scheme CAt+ (Categories plus Attributes) to rate the quality of PD ideas is developed. CAt+ can also be used to filter and aggregate PD ideas to support designers in making sense of as well as addressing such ideas for re-design. Results of the comparisons of paper-based and tool-based approaches show that paper is advantageous in some regards (e.g. number of ideas gathered), but the tool is comparable or in some regards outperforms paper (e.g. user preference). Given the additional advantages tool-usage can bring (e.g. automated analysis support), the context where paper-based or tool-based PD approaches suit better is discussed. For future work the use of PDotCapturer and PDotAnalyser in diverse and distributed settings will be explored.
37
Colman, Alan Wesley y n/a. "Role oriented adaptive design". Swinburne University of Technology, 2006. http://adt.lib.swin.edu.au./public/adt-VSWT20070320.110756.
Texto completoResumen
Software systems are becoming inexorably more open, distributed, pervasive, mobile and
connected. This thesis addresses the problem of how to build adaptive software systems.
These systems need to reliably achieve system-level goals in volatile environments, where
the system itself may be built from components of uncertain behaviour, and where the
requirements for the software system may be changing. This thesis adopts the systemtheoretic
concept of ontogenic adaptation from biology, and applies it to software
architecture. Ontogenic adaptation is the ability of an individual system to maintain its
organisational integrity by reconfiguring and regulating itself. A number of approaches to
adaptive software architecture have been recently proposed that, to varying degrees, enable
limited adaptive behaviour and reconfiguration, but none possess all the properties needed
for ontogenic adaptation. We introduce a meta-model and framework called Role Oriented
Adaptive Design (ROAD) that is consistent with the concept of maintaining organisational
integrity through ontogenic adaptation.
The ROAD meta-model defines software applications as networks of functional roles
which are executed by players (objects, components, services, agents, people, or rolecomposites).
These flexible organisational structures are adaptive because the relationships
(contracts) between roles, and the bindings between roles and players, can be regulated and
reconfigured at run-time. Such flexible organisational role-structures are encapsulated into
composites each with its own organiser. Because self-managed composites are themselves
role-players, these composites can be distributed and recursively composed. The organisers
of the composites form a management system over which requirements and performance
data pass. Rather than being monolithic constructions, ROAD software applications are
dynamic, self-managed compositions of loosely-coupled, and potentially, distributed
entities.
The concepts in the ROAD meta-model have been implemented in a programming
framework which can be extended by the application programmer to create adaptive
applications. Central to this framework are dynamic contracts. These contracts define the
role structure, control interactions between the role instances, and measure the performance
of those interactions. Adaptivity is achieved by monitoring and manipulating these
contracts, along with the role-player bindings. Contracts have been implemented using the
mechanism of �association aspects�.
The applicability of the ROAD framework to the domain of Service-Oriented
Computing is demonstrated. The framework is further evaluated in terms of its ability to
express the concept of ontogenic adaptation and also in terms of the overhead its runtime
infrastructure imposes on interactions.
38
Turilli, Matteo. "Ethics and the practice of software design". Thesis, University of Oxford, 2012. http://ethos.bl.uk/OrderDetails.do?uin=uk.bl.ethos.711646.
Texto completo
39
Powale, Kalkin. "Automotive Powertrain Software Evaluation Tool". Master's thesis, Universitätsbibliothek Chemnitz, 2018. http://nbn-resolving.de/urn:nbn:de:bsz:ch1-qucosa-233186.
Texto completoResumen
The software is a key differentiator and driver of innovation in the automotive industry. The major challenges for software development are increasing in complexity, shorter time-to-market, increase in development cost and demand of quality assurance. The complexity is increasing due to emission legislations, variants of product and new communication technologies being interfaced with the vehicle. The shorter development time is due to competition in the market, which requires faster feedback loops of verification and validation of developed functionalities. The increase in development cost is contributed by two factors; the first is pre-launch cost, this involves the cost of error correction in development stages. Another is post-launch cost; this involves warranty and guarantees cost. As the development time passes the cost of error correction also increases. Hence it is important to detect the error as early as possible. All these factors affect the software quality; there are several cases where Original Equipment Manufacturer (OEM) have callbacks their product because of the quality defect. Hence, there is increased in the requirement of software quality assurance. The solution for these software challenges can be the early quality evaluation in continuous integration framework environment. The most prominent in today\'s automotive industry AUTomotive Open System ARchitecture (AUTOSAR) reference architecture is used to describe software component and interfaces. AUTOSAR provides the standardised software component architecture elements. It was created to address the issues of growing complexity; the existing AUTOSAR environment does have software quality measures, such as schema validations and protocols for acceptance tests. However, it lacks the quality specification for non-functional qualities such as maintainability, modularity, etc. The tool is required which will evaluate the AUTOSAR based software architecture and give the objective feedback regarding quality. This thesis aims to provide the quality measurement tool, which will be used for evaluation of AUTOSAR based software architecture. The tool reads the AUTOSAR architecture information from AUTOSAR Extensible Markup Language (ARXML) file. The tool provides configuration ability, continuous evaluation and objective feedback regarding software quality characteristics. The tool was utilised on transmission control project, and results are validated by industry experts.
40
Yan, Jie. "An Evaluation of Current Applications of 3D Visualization Software in Landscape Architecture". DigitalCommons@USU, 2014. https://digitalcommons.usu.edu/etd/3882.
Texto completoResumen
The design process is important to all landscape architects. It helps generate ideas to solve problems in an efficient amount of time and insure that all stages of a project are completed. Generally, a design process includes project acquisition, inventory and site analysis, conflicts identification, public involvement, draft products, and final presentation. Among these elements, public involvement has been recognized as one of the most important elements in the landscape design process. It not only helps professionals get projects done smoothly, but it also helps with long-term client retention. Traditional two-dimensional communication methods using renderings, design plans, and maps have not been fully successful in their ability to engage and sufficiently inform clients and stakeholders. While professional planners are able to rely on their experience to help them visualize proposed landscapes, the average client is often overwhelmed by the relatively complex and abstract information, and unable to translate this information into landscape visions. Developments in the field of 3D graphics have dramatically extended possibilities to overcome this barrier by providing a tool that produces designs that are easy to comprehend and helps clients better visualize the end product that the designer has put forth. Some people argue that the high investment cost of 3D software such as ArcGIS, 3Dmax, etc., and its time-consuming process to master, is too great an obstacle for most designers and firms to use the software in their work with the average client or stakeholder. However, little research has been done to investigate the extent to which landscape architects have adopted the 3D software. We know even less about their opinions on the suitability of existing 3D software packages to meet their professional needs.
A nationwide survey about current use and future demand for 3D simulation software within the landscape profession was conducted for this thesis. Comprehensive online surveys were sent to two groups: (1) landscape architecture firms and freelance landscape architects; and (2) institutions with landscape architecture programs. In total, 3,434 firms and freelance architects were identified based on data from the American Society of Landscape Architecture. Names and contact information of ninety-one faculty members from institutions with landscape architecture programs were found on the Council of Educators in Landscape Architecture website.
The opportunities and challenges of 3D visualization technology and its potential applications in landscape and environmental planning have been examined based on the findings from survey results. The results are relevant to the future improvement and innovation of 3D visualization software in the landscape architecture profession and can assist landscape architecture educators with future curriculum development.
41
Gentile, Antonio. "Portable multimedia supercomputers : system architecture design and evaluation". Diss., Georgia Institute of Technology, 2000. http://hdl.handle.net/1853/14726.
Texto completo
42
Pasini, Samuele <1979>. "Uniquitous internet middleware: architecture design and prototype evaluation". Doctoral thesis, Alma Mater Studiorum - Università di Bologna, 2009. http://amsdottorato.unibo.it/1760/.
Texto completoResumen
Technology advances in recent years have dramatically changed the way users exploit contents and services available on the Internet, by enforcing pervasive and mobile computing scenarios and enabling access to networked resources almost from everywhere, at anytime, and independently of the device in use. In addition, people increasingly require to customize their experience, by exploiting specific device capabilities and limitations, inherent features of the communication channel in use, and interaction paradigms that significantly differ from the traditional request/response one.
So-called Ubiquitous Internet scenario calls for solutions that address many different challenges, such as device mobility, session management, content adaptation, context-awareness and the provisioning of multimodal interfaces. Moreover, new service opportunities demand simple and effective ways to integrate existing resources into new and value added applications, that can also undergo run-time modifications, according to ever-changing execution conditions.
Despite service-oriented architectural models are gaining momentum to tame the increasing complexity of composing and orchestrating distributed and heterogeneous functionalities, existing solutions generally lack a unified approach and only provide support for specific Ubiquitous Internet aspects. Moreover, they usually target rather static scenarios and scarcely support the dynamic nature of pervasive access to Internet resources, that can make existing compositions soon become obsolete or inadequate, hence in need of reconfiguration.
This thesis proposes a novel middleware approach to comprehensively deal with Ubiquitous Internet facets and assist in establishing innovative application scenarios. We claim that a truly viable ubiquity support infrastructure must neatly decouple distributed resources to integrate and push any kind of content-related logic outside its core layers, by keeping only management and coordination responsibilities. Furthermore, we promote an innovative, open, and dynamic resource composition model that allows to easily describe and enforce complex scenario requirements, and to suitably react to changes in the execution conditions.
43
Scott, Mark W. (Mark Winfield) 1961. "System architecture evaluation by single metric". Thesis, Massachusetts Institute of Technology, 1998. http://hdl.handle.net/1721.1/9755.
Texto completoResumen
Thesis (S.M.)--Massachusetts Institute of Technology, System Design and Management Program, February 1999.Includes bibliographical references (leaf 62).
System architecture is driven by numerous upstream influences. Regulations, market forces, cultural biases, and a variety of other influences can significantly affect whether architecture is successful or not. To be successful the architect must include upstream influences in the design. Few if any architectural methods are available to systematically account for upstream influences. A new method, Evaluation by a Single Metric (ESM), is presented. It is based on fundamental design principles. It enhances the system architectural process by organizing upstream influences that drive architecture. The ESM method is concept independent and used before concept focused system architectural methods. Specifically, system boundaries, salient upstream elements. and functional connections thereof are systematically determined. The ESM process provides a concept neutral framework used to evaluate candidate architectural concepts. The ESM method is very general. It can be used for the design of nearly any kind of system or process. The thesis makes extensive use of a diverse set of examples which highlight ESM advantages and flexibility.
by Mark W. Scott.
S.M.
44
Molin, Oscar. "Design verification through software architecture recovery : Meeting ISO 26262 requirements on software using static analysis". Thesis, Uppsala universitet, Institutionen för informationsteknologi, 2013. http://urn.kb.se/resolve?urn=urn:nbn:se:uu:diva-202149.
Texto completoResumen
Emerging functional safety standards in the automotive industry will create new challenges for companies sitting on large deposits of legacy code. When refactoring existing code for compliance with standards such as ISO 26262, great savings could be made if work products required by the standard could be automatically generated from existing source code. In this thesis, we explore the possibilities to generate graphical software architectures, data-flow graphs and software architectural descriptions directly from existing C source code. By parsing the source code to find structures and the relations between them, we were able to create relational graphs that represents the software of an entire system or that of just one component, using different levels of abstraction where appropriate. We create a proof-of-concept tool chain that can generate two kinds of graphical architecture views and one data-flow view. Although these tools are by no means ready for production, they do show promise and are already useful as development tools for better software understanding. Finally we test the tool chain on current production ECU (Electric Control Unit) software used in heavy trucks and buses and evaluate the results against the requirements of the ISO 26262 standard. This thesis was done at Scania CV AB in Södertälje, Sweden.
45
Ramdat, Upendra. "Software Communications Architecture (SCA) compliant software radio design for Interim Standard 95B (IS-95B) transceiver". Thesis, Monterey, Calif. : Naval Postgraduate School, 2007. http://bosun.nps.edu/uhtbin/hyperion.exe/07Mar%5FRamdat.pdf.
Texto completoResumen
Thesis (M.S. in Electrical Engineering)--Naval Postgraduate School, March 2007.Thesis Advisor(s): Frank Kragh. "March 2007." Includes bibliographical references (p. 139-140). Also available in print.
46
Roets, Yzelle. "The design and evaluation of an integrated enterprise architecture metamodel". Thesis, University of Pretoria, 2015. http://hdl.handle.net/2263/43531.
Texto completoResumen
The research focuses on the relationship and interlinking between the different architectural domains within the enterprise architecture of an enterprise. The architectural domains are grouped together as business architecture, information architecture and technology architecture.
First, a literature review of the definitions, history, role, functions and qualities, existing frameworks, models and domains of enterprise architecture was conducted. The definitions; role and benefits; models, frameworks, ontologies and descriptive languages of the different architectural domains were then studied as background and basis. New definitions were deduced.
Second, the modelling methodology, process, elements and deliverables were investigated. An integration metamodel for enterprise architecture was developed, according to this modelling methodology. The metamodel is called the Relational Enterprise Architecture Metamodel or the REAM.
Third, the research methodology for the empirical research section was investigated and determined. The proposed conceptual metamodel has been assessed through a case study within three different industries each. The feedback from the case studies was used to modify/enhance the metamodel. The possibilities for application of the modified model were then assessed at the University of Pretoria.
The contribution of this research lies mainly in the development, empirical testing and refining of an integrated EA metamodel (REAM) as well as the development of new definitions for enterprise, business, information and technology architecture and relating them.Thesis (PhD)--University of Pretoria 2015.
Information Science
Unrestricted
47
White, Maurice Walter. "Verification and evaluation of structural analysis and design software". Thesis, Virginia Tech, 1991. http://hdl.handle.net/10919/41489.
Texto completo
48
Davis, Jesse H. Z. (Jesse Harper Zehring) 1980. "Hardware & software architecture for multi-level unmanned autonomous vehicle design". Thesis, Massachusetts Institute of Technology, 2002. http://hdl.handle.net/1721.1/16968.
Texto completoResumen
Thesis (M.Eng.)--Massachusetts Institute of Technology, Dept. of Electrical Engineering and Computer Science, 2002.Includes bibliographical references (p. 95-96).
This electronic version was submitted by the student author. The certified thesis is available in the Institute Archives and Special Collections.
The theory, simulation, design, and construction of a radically new type of unmanned aerial vehicle (UAV) are discussed. The vehicle architecture is based on a commercially available non-autonomous flyer called the Vectron Blackhawk Flying Saucer. Due to its full body rotation, the craft is more inherently gyroscopically stable than other more common types of UAVs. This morphology was chosen because it has never before been made autonomous, so the theory, simulation, design, and construction were all done from fundamental principles as an example of original multi-level autonomous development.
by Jesse H.Z. Davis.
M.Eng.
49
Dandekar, Ashok V. "A procedural approach to the evaluation of software development methodologies". Thesis, Virginia Polytechnic Institute and State University, 1987. http://hdl.handle.net/10919/94502.
Texto completoResumen
This thesis presents a procedural approach to evaluating software development methodologies. The evaluation procedure adopts a unique approach based on the fundamental assumption that the requirements govern the process by which software is constructed. To begin with, this research partitions desirable software characteristics into three categories, viz., objectives, principles and attributes. The thesis claims (claims are substantiated with literature references) that there exist definitive relationships (or linkages) among the software objectives, principles and attributes. These linkages form the foundation of the evaluation procedure. The procedure constitutes two processes, top-down process and bottom-up process. These processes are used to assess the software product and the employed software development methodology. The top-down process begins by identifying the objectives and travels down through principles and product attributes; thus, evaluating the adequacy of the methodology. The bottom-up process, on the other hand, starts at the attribute level and goes up through principles and objectives. The bottom-up process highlights the effectiveness of the methodology. Attributes are identified in the product via properties. This research establishes several properties (called factors in the report) for each attribute. A measurement approach is also presented to help assess the extent to which attributes are present. The feasibility and validity of the evaluation procedure are illustrated through the analysis of two real life methodologies.M.S.
50
Harel, Idit Ron. "Software design for learning : children's construction of meaning for fractions and LOGO programming". Thesis, Massachusetts Institute of Technology, 1988. http://hdl.handle.net/1721.1/75005.
Texto completo