Modeling software with object-oriented technique and Unified Modeling Language (UML) has become the new paradigm of modern information systems analysis and design. Selonen et al. (2003) proposed a framework for transformation within UML. However, they do not precisely define the operations and the rules they use. This research presents a systematic method which enhances Selonen et al.¡¦s work to transform the sequence diagram into the class diagram. The transformation process consists of three phases: (1) mapping the given sequence diagram to a notation-independent and semantically equivalent minimal model, (2) transforming the minimal model of the sequence diagram into the minimal model of a class diagram, and (3) mapping the minimal model to a class diagram. A real-world case is used to illustrate the concepts, application, and the advantages of using the proposed method. With this approach, the system developer can transform sequence diagram into class diagram automatically and thereby enhance the efficiency of system development.

Today, modeling the software with unified modeling language (UML) and computer-aided software engineering (CASE) tool becomes the main stream for the objected-oriented systems analysis and design. To enhance the degree of ransformation automation and reuse in the system development process, prior research suggested that most parts of the class diagram can be transformed from the sequence diagram directly. However, the explicit guideline for the transformation is lacking. This study presents a methodology, extended from Selonen et al (2003), to transform the sequence diagram into the class diagram. A real-world case using the integrated techniques is presented to illustrate the concepts, application, and the advantages of using the proposed approach. With this approach, the system developer can transform most parts of the sequence diagram into its associated class diagram automatically and thereby enhance the efficiency of system development.

After well-known structured technology, object-oriented technology has become another paradigm of system development and a hot topic in the field of software engineering. The Unified Modeling Language (UML) has become a standard means for the analysis and design of object-oriented after it passed the certification of the Object Management Group (OMG) in 1997, and it was widely used in many industries. Although it becomes a standard of object-oriented modeling language, UML hasn¡¦t provided principles or guidelines for mapping classes to tables. The purpose of this study is to investigate the guidelines for transforming UML class diagram to object-relational model. The transferring methods include both static structure transfer and dynamic behavior transfer. An example of automobile ordering system is used to illustrate the guideline and application. With these guidelines, analysts can easily use the UML class diagram to express database designing and thereby improve the efficiency and effectiveness of UML modeling.

Class normalization is a process that can be used to organize the structure of object schema to increase the cohesion of classes while minimizing the coupling between them. This research proposes a method to apply the rule of class normalization to class modeling during the object-oriented systems analysis and design process. A real-world case is presented to illustrate the concepts, application, and the advantages of using the proposed method. Utilizing this method in class modeling can help the system developer ensure the class diagram in third object normal form and thereby enhance the effectiveness of system development.

Object-Oriented analysis and design approach has become the mainstream of today¡¦s systems development technique. The Class Diagram in Unified Modeling Language (UML) is the major tool for modeling the class structure in the object-oriented system analysis and design process. Once the class diagram is constructed, class normalization needs to be performed to eliminate the anomalies for the designing a database. However, the detailed guideline for performing class normalization is lacking. Therefore, this study presents a class normalization methodology based on object normal forms proposed by Ambler (1996). Two real-world cases are presented to illustrate the concepts, application, and the advantages of using the proposed method. Using this methodology in class modeling will help system developers normalize the class design in advance, and thereby enhance the efficiency and effectiveness of system development.

No description available.

The main goal of testing is to find errors in the System Under Test (SUT). Prior research indicated that Model-Based Testing is indeed good at finding SUT errors, can lead to less time and effort spent on testing if the time needed to write and maintain the model plus the time spent on directing the test generation is less than the cost of manually designing and maintaining a test suite. This study proposed a methodology for Model-Based Testing. In this approach, Sequence Diagrams and Class Diagram are used to determine the testing path and test case and Object Constraint Language is used to specify the business logic constraint. Three real-world cases and a CASE tool are used to test the usability (including the concepts, application, and advantages) of the proposed methodology. With this approach, SUT errors can be found at the systems analysis and design stage and thereby reduce the cost of software testing and enhance the efficiency of system development.

Today, unified modeling language (UML) has become a standard modeling language in object-oriented systems analysis and design. Specifying the business logic constraint with object constraint language (OCL) and transforming the specification into code has become a main trend in this area. This research presents a classification of OCL expressions to specify the attribute, operation and relationship constraint on Class diagram. A sample case and a CASE tool are used to test the usability (including the concepts, application, and advantages) of the proposed method. With this approach, the system developer can specify the constraints easily and transform them into code automatically and thereby enhance the efficiency and reusability of system development.

<p>Abstract</p><p>The program analysis tool, VizzAnalyzer, works good for visualizing the program structure as graphs, but currently it does not allow for a UML conform visualization, which allows a effective communication among software engineers. In this thesis we describe the extension of the VizzAnalyzer to allow the visualization of software systems as UML class diagrams.</p><p>The Eclipse platform provides an open source platform for creating an extensible integrated development environment. We create a plug-in that can be seamlessly integrated in the Eclipse platform through the third party tools in Eclipse to visualize the graph in VizzAnalyzer as UML class diagrams. The third party tools that are used in this thesis are the Graphical Editing Framework (GEF) and Draw2D. They are mainly used to create the UML class diagram view.</p><p>In order to get a clear view on the diagram in the limited screen size, it is necessary to provide an appropriate layout for the diagram and drag and zoom actions on its figures. We provide the necessary means and document altogether in this thesis. We implement our solution as Eclipse plug-in and demonstrate feasibility.</p>

<p>Analyzing software contains two different tasks. First of all we are analyzing the software and try to calculate some metrics for software quality. Then those results have to be presented to the software engineers. VizzAnalyzer is a tool for analysis and visualization of software. It visualization allow not for a standardized diagram representation. Therefore it is difficult for others to understand, and we need to explain the meaning of our non-standard diagram elements. The solution is to use a standardized representation which can be understood by both sides. UML is such a collection of intuitively diagrams with standardized elements. Their meaning is clear to most software engineers.</p><p>We extended our analysis tool, the VizzAnalyzer, allowing it to view software systems as UML Class diagrams. We reused the existing plug-in architecture to connect our analysis tool with yEd, a graph visualization program. This plug-in is responsible for exchanging the data between the two applications.</p><p>We solve this conversion defining an UML Class Diagram Model and the mapping function between this model and the Common Meta-Model used by VizzAnalyzer and our Class Diagram Model. After that, we export this Class Diagram Model to a format suitable for yEd to display.</p><p>Now we can generate Class Diagrams with the VizzAnalyzer tool. This will allow a better communication of the results derived by different analysis with the software engineers.</p><p>This thesis describes the evolution of different alternatives and the design and implementation of our solution.</p>