Modeling software with object-oriented technique and unified modeling language have become the new paradigm of modern information systems analysis and design. In addition, many approaches and CASE tools have been introduced to facilitate the transformation from class diagram to object-relational database and application template and thereby enhance the efficiency of system development. Model-driven architecture (MDA) and Rational Rose is such an approach and CASE tool, respectively. This research presents a systematic methodology which integrated the MDA concept to transform the class diagram into object-relational database and application template during the system development process. A real-world case using the integrated techniques is presented and the Rational Rose is used to illustrate the concepts, application, and the advantages of using the proposed methodology. With this approach, the system developer can transform class diagram into object-relational database and application template automatically and thereby enhance the efficiency of system development.

ITC/USA 2005 Conference Proceedings / The Forty-First Annual International Telemetering Conference and Technical Exhibition / October 24-27, 2005 / Riviera Hotel & Convention Center, Las Vegas, Nevada / This paper presents an approach to development of generic ground systems to be used for spacecraft testing and operations. This method makes use of a standard modeling method, which enables virtualization of spacecraft. By virtualizing spacecraft, development of generic systems that are applicable to different spacecraft becomes possible even if spacecraft themselves are not standardized. This is because systems can utilize (1) a standard database that can store information on any virtual spacecraft and (2) standard software tools that can be used for any virtual spacecraft. This paper explains the concept of virtualization of spacecraft, introduces the standard model used for virtualization of spacecraft, shows how to manipulate virtual spacecraft with software tools, and presents the core elements of generic ground systems.

Tese de Mestrado Integrado. Engenharia Informática e Computação. Faculdade de Engenharia. Universidade do Porto. 2013

Modeling software with unified modeling language (UML) and model driven architechutre (MDA) concept have become the new paradigm of modern systems analysis and design. Several CASE tools have been introduced to facilitate the transformation from platform independent model (i.e., class diagram) to platform specific model, and thereby enhance the efficiency of system development. This research presents a systematic methodology which integrated the UML and MDA concept with CASE tool to transform the class diagram into web-based user interface during the system development process. A real-world case using the integrated techniques is presented and the Rational Rose is used to illustrate the concepts, application, and the advantages of using the proposed methodology. With this approach, the system developer can transform class diagram into web-based user interface automatically and thereby enhance the efficiency of system development.

Modeling software with the model driven architecture (MDA) concept and unified modeling language (UML) has become a new trend for the objected-oriented systems analysis and design. Several CASE tools which embed MDA concept and UML have been introduced to facilitate the transformation from platform independent model (PIM, i.e., class diagram) to platform specific model (PSM) in order to enhance the efficiency of software development. In this work, we present a systematic methodology which integrates the concept of MDA and UML with CASE tool to refine the process of UML transformation. A personnel leave prototype system is implemented to illustrate the concepts, application, and advantages of the proposed methodology. With this approach, software developers can construct the PIM efficiently and thereby enhance the efficiency of system development.

Traditionally software testing is performed at the coding stage and is costly. Prior research indicated that if the errors can be found prior to the coding stage, the cost for fixing the errors can be reduced. Today, Unified Modeling Language (UML) has become a standard modeling language in object-oriented systems analysis and design. Over the past few years a considerable effort has been made in synthesizing UML, MDA (Model-Driven Architecture), and CASE tool to increase the productivity of the system development. Specifying the business logic constraints with Object Constraint Language (OCL) has become a main trend in this area. This study presents a methodology to specify the business logic constraint with OCL on the platform independent model during the systems analysis and design stage, then transform the OCL expressions into the code model and do the model testing simultaneously with a CASE tool. 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, software bugs related to business logic constraints 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.

This study presents a systematic methodology which integrated the model driven architecture with object-oriented technique to transform the platform independent model (PIM) into Web-based user interface (UI) platform specific model (PSM), and then into code model. A real-world case using the integrated techniques is presented and the Rational Rose is used to illustrate the concepts, application, and the advantages of using the proposed methodology. With this approach, the system developer can transform PIM into Web-based UI PSM and code automatically and thereby enhance the efficiency of system development.

No description available.

The Unified Modeling Language (UML) has quickly become the industry standard for object-oriented software development. It is being widely used in organizations and institutions around the world. However, UML is often found to be too complex for novice systems analysts. Although prior research has identified difficulties novice analysts encounter in learning UML, no viable solution has been proposed to address these difficulties. Sequence-diagram modeling, in particular, has largely been overlooked. The sequence diagram models the behavioral aspects of an object-oriented software system in terms of interactions among its building blocks, i.e. objects and classes. It is one of the most commonly-used UML diagrams in practice. However, there has been little research on sequence-diagram modeling. The current literature scarcely provides effective guidelines for developing a sequence diagram. Such guidelines will be greatly beneficial to novice analysts who, unlike experienced systems analysts, do not possess relevant prior experience to easily learn how to develop a sequence diagram. There is the need for an effective sequence-diagram modeling technique for novices. This dissertation reports a research study that identified novice difficulties in modeling a sequence diagram and proposed a technique called CHOP (CHunking, Ordering, Patterning), which was designed to reduce the cognitive load by addressing the cognitive complexity of sequence-diagram modeling. The CHOP technique was evaluated in a controlled experiment against a technique recommended in a well-known textbook, which was found to be representative of approaches provided in many textbooks as well as practitioner literatures. The results indicated that novice analysts were able to perform better using the CHOP technique. This outcome seems have been enabled by pattern-based heuristics provided by the technique. Meanwhile, novice analysts rated the CHOP technique more useful although not significantly easier to use than the control technique. The study established that the CHOP technique is an effective sequence-diagram modeling technique for novice analysts.

Maintaining large-scale legacy applications has been a major challenge for software producers. As the application evolves and gets more complicated, it becomes harder to understand, debug, or modify the code. Moreover, as new members are joining the development team, and others are leaving, the need for a well-documented code arises. Good documentation necessitates the visualization of the code in an easy to understand manner. The Unified Modeling Language (UML), an Object Management Group's (OMG) standard, is a graphical modeling language used for specifying, visualizing, constructing, and documenting software intensive artifacts. UML, which has been accepted as an industry standard in November 1997, has aided the design and maintenance of object-oriented legacy applications. While the software developers were building UML models for their existing applications as part of a reverse-engineering process, development of next generation software applications started from the models (forward-engineering process). In the forward engineering process, the system's code is specified and constructed from the UML models, which evolve as the system evolves in order to maintain consistent documentation and visualization of the system. Moreover, UML has the power of hiding unnecessary details of the system by the ability to model its different views. This enables visualizing the system at different levels of hierarchy. This thesis documents how to use UML to model a software-intensive simulation for the combat systems of a fully automated naval "digital ship". This process started with building the use case diagrams based on the system requirements given by the domain experts. Then activity diagrams were used to describe the exact performance of the use cases. The logical view of the system was built using class, interaction, and activity diagrams. Then, the physical view of the system was built using component diagrams. Finally, an example of the code generation process from the UML models was carried out for one of the system components. These models are to be maintained as the application evolves. Using UML has aided in building a well-structured object-oriented application, validating the use cases of the application with the domain experts, visualizing and validating the structure of the source code before writing it, communicating between different members of the development team, and providing an easily understandable documentation of the system. / Master of Science