Thesis (MTech(Electrical Engineering)) -- Cape Peninsula University of Technology, 2014 / Today the building energy modeling industry is facing a number of challenges, the advanced programs or methods developed for building energy modeling, are very technical and complex to be used, especially for earlier designs, and the easy programs or methods are not accurate. Moreover, more than a hundred programs developed for energy modeling, have been used in the same building, but most of the time the results differed by about 30%. That is why this thesis has developed a new building energy model in System Modeling Language (SysML), in order to meet, at the same time, the accuracy and the simplicity to be used for future and existing buildings. In this thesis, SysML has been used to develop an energy model and to set up an automation system to the existing building. SysML can do more than simulations, but this thesis is limited to only the simulations steps by using easy applications of SysML and fewer diagrams which could develop in a complete building energy model. SysML is the extension of Unified modeling Language (UML), which uses fewer diagrams than UML. SysML is simple, open and more flexible to be used in any Engineering System. The previous chapter describes SysML and gives the overview and the platform of SysML. The simulations of SysML in this project have been developed through Enterprise Architect and Mat lab software. The inputs used to simulate the program are the parameters of the existing building chosen for modeling that is a student residential building complex located in Stellenbosch, Western Cape in South Africa. Automation system program used in this thesis was based on the norms and building standards of South Africa, renewable energy and the requirements of the buildings’ occupants, in order to meet energy efficiency and safety of the occupants.

Made available in DSpace on 2014-06-12T15:49:38Z (GMT). No. of bitstreams: 1 license.txt: 1748 bytes, checksum: 8a4605be74aa9ea9d79846c1fba20a33 (MD5) Previous issue date: 2011 / Antonius de Castro Tavares, Marcellus; Pierre Louis Robin, Jacques. Behavioral java code generation from imperative object constraint language expressions in plataformindependent UML models. 2011. Dissertação (Mestrado). Programa de Pós-Graduação em Ciência da Computação, Universidade Federal de Pernambuco, Recife, 2011.

Addressing Quality of Service and specification of quality attributes has been gaining a growing importance in the software engineering area. The research presented in this study investigates different approaches to specification of Quality of Service. UML profile for Quality of Service is one of the standards of the Quality of Service specification and is described in the QoS specification context. The research aim of this thesis is the evaluation of the UML profile for Quality of Service against the following criteria: expressiveness, reusability, understandability, applicability and tool support, as well as further comparison of the profile with other Quality of Service specification languages. To perform that, several tasks and activities were conducted, such as a survey on different QoS specification languages, an examination of the UML profile for Quality of Service, the formulation of the evaluation criteria, and the appliance of the criteria in the evaluation and comparison processes. This study is performed from the perspective of readers and users of the profile that are not UML experts but have sufficient knowledge of UML in terms of software systems analysis and design. The context of the UML profile and Quality of Service aspects include basic concepts of the UML 2.0 and Quality of Service which will be described along the thesis. The main contribution of the thesis is the evaluation of the UML profile for Quality of Service against a set of criteria, followed by explanations on the contents of the profile and how Quality of Service is specified within it. The presented comparison of the UML profile and other Quality of Service specification languages could be the basis for a user to decide what language to use in a particular situation. This study can be comprehended as a starting point for further evaluation of the UML profile and its comparison with other quality specification languages.

The earlier in the development process a fault is found, the cheaper it is to correct the fault. Therefore are verification and validation methods important tools. The problem with this is that there are many methods to choose between. This thesis sheds light on how to choose between four common verification and validation methods. The verification and validation methods presented in this thesis are reviews, inspections and Fault Tree Analysis. Review and inspection methods are evaluated in an empirical study. The result of the study shows that there are differences in terms of defect detection. Based on this study and literature study, guidelines on how to choose the best method in a given context are given. / Desto tidigare i utvecklingsprocessen som ett fel hittas, desto billigare är det att rätt till detta fel. Därför är verifierings- och valideringsmetoder viktiga verktyg. Problemet är att det finns många metoder. Den här rapporten sprider ljus över hur man ska välja mellan fyra vanliga verifierings- och valideringsmetoder. Verifierings- och valideringsmetoderna i den här rapporten är granskningar, inspektioner och "Fault Tree Analysis". Granskningar och inspektioner är utvärderade i en empiriskt studie. Resultatet av studien visar att det finns skillnader mellan metoderna när det gäller att hitta fel.

This thesis investigates a novel approach to reverse engineering, in which modeling information such as UML associations, state machines and attributes is incrementally added to code written in Java or C++, while maintaining the system in a textual format. Umple is a textual representation that blends modeling in UML with programming language code. The approach, called umplification, produces a program with behavior identical to the original one, but written in Umple and enhanced with model-level abstractions. As the resulting program is Umple code, our approach eliminates the distinction between code and model. We implemented automated umplification in a tool called the Umplificator. The tool is rule-driven: code, including Umple code, is parsed and processed into an internal representation, which is then operated on by rules; transformed textual code and model, in Umple, is then generated. The rules used to transform code to model have been iteratively refined by using the tool on a variety of open-source software systems. The thesis consists of three main parts. The first part (Chapters 1 and 2) present the research questions and research methodology, as well as introducing Umple and the background necessary to understand the rest of the thesis. The umplification method is presented at increasing levels of detail through Chapters 3 and 4. Chapters 5 and 6 present the tool and evaluation of our approach, respectively. An analysis of related work, and comparison to our own, appears in Chapter 7. Finally, conclusions and future work directions are presented in Chapter 8.

No description available.

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.

In the digital age that we live in today, we are dependent on numerous web applications or services, from dealing with banking, booking air flights, and handling our taxes. We expect these applications and services to support high availability, data loss prevention, and fast response time. Microservices is a design pattern to support faster software change, and it also supports other non-functional attributes such as scalability and high availability. One way to deploy your software as microservices is to use containers and deploy them on a container cluster such as Kubernetes. The public opinion about writing Kubernetes deployment files is that it is complex and repetitive writing. This project aims to see how model-driven development can assist with the creation of the Kubernetes deployment files. To see how model-driven development can assist in the creation of Kubernetes files. The project will implement a domain-specific modeling language for Kubernetes, and the language should be able to model the application's desired states. And by using model transformation, the tool can generate Kubernetes deployable files.

Type checking is widely used in mainstream programming languages to detect programming errors at compile time. Model checking is gaining popularity as an automated technique for systematically analyzing behaviors of systems. My research focuses on combining these two software verification techniques synergically into one platform for the creation of correct models for software designs. This thesis describes two modeling languages ATS/PML and ATS/Veri that inherit the advanced type system from an existing programming language ATS, in which both dependent types of Dependent ML style and linear types are supported. A detailed discussion is given for the usage of advanced types to detect modeling errors at the stage of model construction. Going further, various modeling primitives with well-designed types are introduced into my modeling languages to facilitate a synergic combination of type checking with model checking. The semantics of ATS/PML is designed to be directly rooted in a well-known modeling language PROMELA. Rules for translation from ATS/PML to PROMELA are designed and a compiler is developed accordingly so that the SPIN model checker can be readily employed to perform checking on models constructed in ATS/PML. ATS/Veri is designed to be a modeling language, which allows a programmer to construct models for real-world multi-threaded software applications in the same way as writing a functional program with support for synchronization, communication, and scheduling among threads. Semantics of ATS/Veri is formally defined for the development of corresponding model checkers and a compiler is built to translate ATS/Veri into CSP# and exploit the state-of-the-art verification platform PAT for model checking ATS/Veri models. The correctness of such a transformational approach is illustrated based on the semantics of ATS/Veri and CSP#. In summary, the primary contribution of this thesis lies in the creation of a family of modeling languages with highly expressive types for modeling concurrent software systems as well as the related platform supporting verification via model checking. As such, we can combine type checking and model checking synergically to ensure software correctness with high confidence.

No description available.