The graphical user interface (GUI) could have a major impact on the successof an application. Like any other software component, the GUI is designedbefore being developed. The software design process usually starts with anabstract design that is illustrated via a modeling language and narrows downto more specific details during the process. However, there are not anymodeling languages that are explicitly focusing on designing the blueprint ofthe GUI. Developing a modeling language that is specialized in designing theskeleton of the graphical user interface could offer the software designers,architectures and clients the means of obtaining a better communication andunderstanding. Thus, developing a better product. In this report, thedevelopment of such a modeling language was made. The modeling languagecan illustrate the blueprint of the GUI. The development process was madeafter researching and finding the most suitable development procedures forour modeling language.

Cascading failures involve a failure in one system component that triggers failures in successive system components, potentially leading to system wide failures. While frequently used fault tolerant techniques can reduce the severity and the frequency of such failures, they continue to occur in practice. To better understand how failures cascade, we have conducted a qualitative analysis of 55 cascading failures, described in 26 publicly available incident reports. Through this analysis we have identified 16 types of cascading mechanisms (organized into eight categories) that capture the nature of the system interactions that contribute to cascading failures. We also discuss three themes based on the observation that the cascading failures we have analyzed occurred in one of three ways: a component being unable to tolerate a failure in another component, through the actions of support or automation systems as they respond to an initial failure, or during system recovery. We believe that the 16 cascading mechanisms we present and the three themes we discuss, provide important insights into some of the challenges associated with engineering a truly resilient and well-supported system.

This document is the masters thesis called refactoring of object oriented application. Goal of this document was to introduce the problem of refactoring and apply gained knowledge on real software project. Document is divided into six chapters. The first chapter is introduction, the term refactoring is defined there with a brief history. Next chapter explains basic principles of refactoring, advantages and disadvantages of using refactoring. The third chapter is called catalog of refactorings and describes common patterns of refactoring. Next two chapters describe .NET platform and tools, which support refactoring on this platform. Sixth chapter is about real application of refactoring. Final chapter is conclusion and summary.

The environmental and economic implications of the increase in Information and Communication Technology energy consumption have become a topic of research in energy efficiency. Most studies focus on the energy estimation and optimization of lower tiers of the hardware and software infrastructures. However, the software itself is an indirect driver of energy consumption, therefore, its energy implications can be to some extent controlled by the software design. Software design patterns belong to high-level software abstractions that represent solutions to common design problems. Since patterns define the structure and behavior of software components, their application may come at energy efficiency costs that are not obvious to the software developers. The existing body of knowledge on energy consumption of software design patterns contains a number of gaps, some of which are addressed within the scope of this thesis project. More specifically, we conducted a series of experiments on the estimation of energy consumption of Visitor and Observer/Listener patterns within the context of non-trivial data parsing in Python. Furthermore, we considered a Patternless alternative for the same task. Additionally, our measurements include runtime duration and memory consumption. The results show that the Visitor pattern led to the largest energy consumption, followed by Observer/Listener and finally the Patternless version. We found a strong relationship between runtime duration and energy consumption, thus coming to the conclusion that the longest-running pattern is the most energy-consuming one. The findings of the current study can be beneficial for Python software developers interested in the energy implications of software design patterns.

No description available.

Context: A software project’s success; involvinga larger group of individuals, relies on efficient teamcommunication. Part of efficient communication is avoidingmiscommunication, misunderstandings, and losingknowledge. These consequences of poor communication canlead to negative repercussions such as loss of time, money,and customer approval. Much effort has been put intocreating tools and systems to aid software engineers inretaining knowledge and decisions made during meetings,but many existing solutions require additional manualintervention on the part of software meeting participants.The objective of this thesis is to explore and develop a toolcalled Design Extractor (DE) which creates concisesummaries of design meetings from recorded voiceconversations. These summaries include both the designdecisions made during a meeting as well as the rationalebehind them. This thesis used readily available Pythonframeworks for machine learning to train two transformermodels based on DistilBert and Google’s BERT. Fine-tuningthese models with data sourcedfrom six different softwaredesign meetings found that the best base model wasDistilBert, which resulted in a fine-tuned model reporting anF1 score of 82.63%. This study created a simple Python tool,built upon many publicly available Python frameworks andthe fine-tuned transformer model, that takes in voicerecordings and outputs labeled sentence-label pairs that canbe used to quickly notate a design meeting. Short summariesare also provided by the tool through the use of pre-existingtext summarisation machine learning models such as BART.Design extractor therefore provides a simple quick way toreview longer meeting recordings in the context of softwareengineering decisions.

No description available.

No description available.

No description available.

No / This paper introduces multimedia design guidelines for browsing large volumes of e-mail data. These software design guidelines derived from two sets of experiments under a prototype version of a multimedia e-mail tool. The experiments tested various forms of audio-visual communication metaphors. For example, the auditory stimuli consisted of musical sounds (earcons), compositional sounds, environmental sounds (auditory icons), stereophony, pitch, synthesised and recorded speech as well as other sound effects. The first set of experiments involved the multimedia browsing of simple and complex sets of e-mail data. The second set of the experiments involved the communication of e-mail categories and other related e-mail information such as the presence or absence of an attachment, priority status and subject of an e-mail. The results of these two sets of experiments are described and linked with other experiments in the literature. The paper integrates and discusses all these experimental results, the incorporation of auditory stimuli and the suitability of different types of multimedia metaphors for the design of audio-visual browsing techniques of large volumes of e-mail data. The totality of the multimedia design appeared to offer a meaningful, easily understood and recognised interaction mechanism and therefore demonstrated a potential way to maximise the volume of information that could be communicated to users. The application of synthesised and recorded speech, earcons and auditory icons as well as sound effects are also discussed in the light of the experimental results with emphasis upon issues of synergy, synchronisation, consistency, structure, classification and presentation of different types of communication metaphors as an integral part of the software design process. Furthermore, the suitability and use of compositional sounds are also discussed. The paper concludes with a set of practical guidelines for software and multimedia designers and a design approach for this type of data browsing.