On Class Diagrams, Crossings and Metrics

As a standardized software engineering diagram, the UML class diagram provides various information on the static structure of views on software while design, implementation and maintenance phase. This talk gives an overview on drawing UML class diagrams in hierarchical fashion. Therefore, common elements of class diagrams are introduced and aesthetic rules for drawing UML class diagrams are given. These rules are based on four disciplines involved in the reading process of diagrams. After a brief introduction to our drawing algorithm, an extensive extension of the well-known Sugiyama algorithm, two details are highlighted: A new crossing reduction algorithm is presented and compared to existing ones and issues on measuring the quality of a layout are discussed

Auto-Generation of Use Case Controllers

The thesis is based on the concept of generating machine executable code from UML diagrams. There has been some research done on the same topic but it is mainly focused on class diagrams. My main focus will be on the use case diagrams, and sequence diagrams. Sequence diagrams give us the details of any process in a step-by-step fashion which makes it easier to extract the required information regarding the use cases and the controllers which help us generate the code. The process follows three steps, first being generation of UML diagrams. Secondly, these are converted into XMI (XML Metadata Interchange) which is a XML format. In the end this XMI file is converted into machine executable Java code with the help of a tool that I will be generating. We will be using StarUML as the UML editor for the thesis which also provides the functionality of converting UML diagrams into XMI format. The advantages of this process include the reduction of time complexity of the process and ease of coding for the software developers. In future, this project can be extended to map the requirements provided by the customer to the software developed so that the customer can understand the system very easily. This project could be further expanded so that it can generate code even considering the state chart diagrams for any system. The report includes the details of the implementation and the work I have done. I have named the software are ProtoGen and will be referring to it as ProtoGen throughout the report

A graph-based aspect interference detection approach for UML-based aspect-oriented models

Aspect Oriented Modeling (AOM) techniques facilitate separate modeling of concerns and allow for a more flexible composition of these than traditional modeling technique. While this improves the understandability of each submodel, in order to reason about the behavior of the composed system and to detect conflicts among submodels, automated tool support is required. Current techniques for conflict detection among aspects generally have at least one of the following weaknesses. They require to manually model the abstract semantics for each system; or they derive the system semantics from code assuming one specific aspect-oriented language. Defining an extra semantics model for verification bears the risk of inconsistencies between the actual and the verified design; verifying only at implementation level hinders fixng errors in earlier phases. We propose a technique for fully automatic detection of conflicts between aspects at the model level; more specifically, our approach works on UML models with an extension for modeling pointcuts and advice. As back-end we use a graph-based model checker, for which we have defined an operational semantics of UML diagrams, pointcuts and advice. In order to simulate the system, we automatically derive a graph model from the diagrams. The result is another graph, which represents all possible program executions, and which can be verified against a declarative specification of invariants.\ud To demonstrate our approach, we discuss a UML-based AOM model of the "Crisis Management System" and a possible design and evolution scenario. The complexity of the system makes con°icts among composed aspects hard to detect: already in the case of two simulated aspects, the state space contains 623 di®erent states and 9 different execution paths. Nevertheless, in case the right pruning methods are used, the state-space only grows linearly with the number of aspects; therefore, the automatic analysis scales

A systematic approach for component-based software development

Component-based software development enables the construction of software artefacts by assembling prefabricated, configurable and independently evolving building blocks, called software components. This paper presents an approach for the development of component-based software artefacts. This approach consists of splitting the software development process according to four abstraction levels, viz., enterprise, system, component and object, and three different views, viz., structural, behavioural and interactional. The use of different abstraction levels and views allows a better control of the development process

UML-F: A Modeling Language for Object-Oriented Frameworks

The paper presents the essential features of a new member of the UML language family that supports working with object-oriented frameworks. This UML extension, called UML-F, allows the explicit representation of framework variation points. The paper discusses some of the relevant aspects of UML-F, which is based on standard UML extension mechanisms. A case study shows how it can be used to assist framework development. A discussion of additional tools for automating framework implementation and instantiation rounds out the paper.Comment: 22 pages, 10 figure

Development of a Secured Information System to Manage Malaria Related Cases in South Western region of Nigeria

Effective community based management of malaria incidences in most community health care centers are hampered by failure in the prompt diagnosis and treatment of malaria. This challenge is exacerbated by the emergence of multidrug resistant plasmodium parasites which makes ineffective most of the effective therapeutic drugs used in the treatment of malaria. Furthermore, even at abrupt changes in the therapeutic recommendations does not always translate to an immediate change in the effective management and control of malaria. Thus, the quest for effective diagnosis and appropriate treatment becomes a daunting and necessary task. . In this article, a secured Information system to manage malaria related cases was developed by 2-tier architecture by using the VB.NET programming language within the Microsoft Visual studio 2008 edition. The database employed for storing relevant data was the SQL server 2005 edition and fingerprint device integrated into the information system was the Microsoft fingerprint reader. From the results in this study, we modeled a feasible medical history system for prompt diagnosis, effective drug recommendations and promulgation of policies that would serve as palliatives for community health care centers that suffers shortages in material and human resources handling malaria and its related diseases