RELIABILITY VERIFICATION OF TRAIN CONTROL ALGORITHM FOR KOREAN HIGH-SPEED TRAIN

Computer-aided software engineering (CASE) Tools is a set of software that results in high-quality and maintainable software products. The Unified Modeling Language (UML) is one of the most commonly used CASE tools for analyzing and expressing software requirements. Considerably, UML overcomes ambiguity limitation which results from infamous shortcoming of national language. However, how to express requirements of E-Commerce System is still a very challenging problem. In this paper, requirement analysis is highlighted by IBM Rational Rose and Microsoft Visio, and typical E-Commerce system by UML is investigated as well. At the end, a guideline generated for Jewellery E-Commerce (JEC) is presented by UML use cases, activity diagrams, and data flow diagrams in details.

Computer-aided software engineering (CASE) tools have been advocated for improving maintainer productivity and the quality of maintained software. While there is evidence that such benefits can accrue to organizations adopting maintenance-oriented CASE tools, a key problem in achieving the desired benefits from CASE tools is low usage of these tools by programmers. The previously tested Maintenance Tool Utilization Model was a first step in investigating the factors that affect whether maintainers choose to use CASE tools during maintenance projects. We test the addition of experience with software maintenance tools and with the software maintenance task to the Maintenance Tool Utilization Model. The role of experience is important because managers can provide training to increase experience and they can ensure that project teams have some members experienced with the tools or with the task. Data for the test are collected from software maintainers working on their organization’s normal maintenance project backlog. Tool experience is significant as both a main and interaction effect, but task experience adds little to the explanatory power of the Maintenance Tool Utilization Model. These results support the value of improved CASE tool training programs.

Integrating software modelling and prototyping tools

Performing rigorous analysis of parallel and distributed systems (PDS) specifications is one of the important tasks during the early stages of development. The ambiguities and errors left unchecked during the analysis phase can creep into design and development phases, resulting in cost and schedule overruns and a less reliable end product. Commercial off the shelf CASE (Computer Aided Software Engineering) tools can play an important role in the analysis and design phases. However techniques must be developed to address the shortcomings of CASE tools. A set of such techniques is presented in this paper. CASE tools can be used to gather PDS specifications in the form of analysis models. The techniques presented in this paper deal with the problem of performing rigorous analysis of PDS specifications originally developed using a CASE tool. The approach is based on integrating a CASE tool with a verification tool based on coloured Petri nets (CPNs). CPNs can be used to model and analyze concurrency in specifications and design phases. Dynamic simulations of CPN models can be used to conduct performance/performability analysis as well as risk assessment studies.

Computer-Aided Software Engineering (CASE) tools have been advocated for improving maintainer productivity and the quality of maintained software. While there is evidence that such benefits can accrue to organizations adopting maintenance-oriented CASE tools, a key problem in achieving the desired benefits from CASE tools is low usage of these tools by programmers. The previously tested Maintenance Tool Utilization Model was a first step in investigating the factors that affect whether maintainers choose to use CASE tools during maintenance projects. We test the addition of experience with software maintenance tools and with the software maintenance task to the Maintenance Tool Utilization Model. The role of experience is important because managers can provide training to increase experience and they can ensure that project teams have some members experienced with the tools or with the task. Data for the test are collected from software maintainers working on their organization’s normal maintenance project backlog. Tool experience is significant as both a main and interaction effect, but task experience adds little to the explanatory power of the Maintenance Tool Utilization Model. These results support the value of improved CASE tool training programs.

This study investigates the job satisfaction of information technology (IT) professionals in an environment where computer aided software engineering (CASE) tools are used. Although the recent downturn in the economy might have temporarily eased the IT labor shortage, issues of recruitment and retention of qualified personnel are key to the success of IS development projects. This study presents a model of the combination of CASE tool usage and job satisfaction as related to internal career orientation. Two hypotheses based on this model were tested using empirical evidence collected through a survey method. The first examines whether the career orientation of IS personnel influences their job satisfaction. The second incorporates the impact of CASE tool usage on this relationship. The results indicate that in a CASE tool environment, personnel with a predominant technical career orientation have more job satisfaction than those with a predominant managerial tation. However, there is a significant and positive synergy between the sophistication of the CASE tool used and managerial competence orientation leading to higher job satisfaction. These findings indicate that combating the IT personnel shortage through task automation may also increase worker satisfaction, thereby decreasing turnover. Careful selection of the CASE tool for use may result in this win-win situation.

An integrated development and maintenance environment for the C programming language is discussed. The environment has been designed to take advantage of recent advances in platform and user-interface technology and provides unique capabilities not found in traditional computer-aided software engineering (CASE) tools. SMART system is an integrated, multiuser software development, maintenance, and reverse engineering environment which provides advanced capabilities for C programmers. The user's program source, modifications, and all derived data are stored in an object-oriented database. SMART system has a soft user interface that allows a high degree of user customization. Unlike existing CASE tools, which have been largely concerned with capturing specifications and designs for new products, the SMART system is concerned with the analysis, modification, and management of code. By providing tools that address programs as entities, as well as tools that operate at a finer granularity. SMART system allows the user to approach programming issues at the proper level of abstraction. >

This paper describes a course developed to teach software design with a focus on the use of computer-aided software engineering (CASE) environments. Commercial CASE tools were acquired and used in a classroom environment in response to the needs expressed by local industry. The paper assesses the benefits and problems associated with placing emphasis on CASE tools in a software engineering course. Using mature CASE environments brings one kind of realism to the students' project experience, but the complexity of learning a design methodology and complex tools places limits on the scope of design projects that can be assigned. Design recovery tools show promise for helping students learn design principles. In addition, assignments in which students carried out independent assessments of various CASE tools were found to be very valuable opportunities for students to practice written and oral expression, in addition to broadening their knowledge of CASE.

In this paper, a generic computer aided software engineering (CASE) tool builder MetaBuilder is proposed and described in detail. It is a graph-driven tool, not only for CASE application projects but for new methodology and new CASE tool design. MetaBuilder provides the following functionality: a rapid CASE tool developing environment for users to create new or modify old methodologies in graph manipulations; an integration platform for users to plug their own programs into MetaBuilder to realise their own special functionality; a central repository and a set of graphic user interface (GUI) classes for resource reuse that can greatly lighten users' developing work, shorten users' learning and developing time; and finally, a hierarchical design mechanism and a flexible type definition method based on nested graph structures for large and complex CASE methodology and application project design. All generated tools are integrated due to our unique data model. The implementation of MetaBuilder is also presented.

Model-to-model (M2M) transformations are among the key components of model-driven development, enabling a certain level of automation in the process of developing models. The developed solution of using drag-and-drop actions-based M2M transformations contributes to this purpose by providing a flexible, reusable, customizable, and relatively easy-to-use transformation method and tool support. The solution uses model-based transformation specifications triggered by user-initiated drag-and-drop actions within the model deployed in a computer-aided software engineering (CASE) tool environment. The transformations are called partial M2M transformations, meaning that a specific user-defined fragment of the source model is being transformed into a specific fragment of the target model and not running the whole model-level transformation. In this paper, in particular, we present the main aspects of the developed extension to that M2M transformation method, delivering a set of natural language processing (NLP) techniques on both the conceptual and implementation level. The paper addresses relevant developments and topics in the field of natural language processing and presents a set of operators that can be used to satisfy the needs of advanced textual preprocessing in the scope of M2M transformations. Also in this paper, we describe the extensions to the previous M2M transformation metamodel necessary for enabling the solution’s NLP-related capabilities. The usability and actual benefits of the proposed extension are introduced by presenting a set of specific partial M2M transformation use cases where natural language processing provides actual solutions to previously unsolvable situations when using the previous M2M transformation development.

CASE tool for reusable software component storage and retrieval in rapid prototyping

Critical analysis of tools for computer-aided software engineering

This study aimed to evaluate 2 advanced methods for presurgical calculation of bilateral alveolar cleft defect volume using 3-dimensional (3D) printing and computer-aided engineering (CAE) software. Twelve patients with bilateral alveolar cleft (4 females, 8 males, age range 8-11 years) were enrolled in the study. All patients underwent preoperative helical computed tomography scans, and the digital imaging and communications in medicine (DICOM) data of the computed tomography images were analyzed using 3D printing and CAE software. The 3D-printed model used a simulated graft, and graft volume was measured by water displacement. The CAE software used a subtractive method to calculate volume. Simulated graft volumes and CAE-software-derived volumes were compared using Pearson's correlation test and paired Student's t-test. The average volume of the simulated bone grafts obtained using 3D-printed models was 1.45 mL, which was lower than the CAE-software-derived mean volume of 1.52 mL. The mean calculation time using the 3D-printed model was 51.5 minutes, which was 32.1 minutes longer than the average 19.4 minutes when using CAE software. Paired Student's t-test revealed no statistically significant difference between the volumes derived from these methods. The results of this study further validated the use of 3D printing and CAE technique in bilateral alveolar defect repair. The CAE software is more cost-effective in presurgical volumetric assessment. Moreover, 3D models overcome limitations of 3D visualizations by providing tactile feedback and superior appreciation of visuospatial relationships among anatomical structures.

This chapter focuses on two practical design approaches to bridging the gap: the User Interface War Room method and the Design Prism method. The walls of the “user interface war room” served as a metaphor used in redesigning the interface of a computer-aided software engineering (CASE) tool for telecommunications research. To begin, user requests (derived from task analysis interviews with software developers) were posted on the first wall of the war room. The English text describing these requests was grammatically parsed to yield user objects (and the functions which acted on them). These user objects were organized into hierarchical relationships and posted on the second wall. Design ideas were then generated in a creative process that drew ideas from team members, users, existing software, and scenario data. This led to the development of several mutually exclusive prototype systems, which could then be verified against the original user requests to make sure that concrete designs matched user requirements. In the Design Prism work, which involved redesigning the interface for a power plant, the user objects and functions of the war room were subdivided into four categories of user elements: Information, Objects, Goals, and Actions. Relationships between these user elements were captured in a “table of relations.” Prototype ideas were then sketched from the perspective of each category (e.g., from a user Goals perspective first). These idea sketches were fleshed out into actual screen designs, with the help of plant-specific design guides for coding information and for displaying graphical objects. Finally, the alternative designs from each of the four perspectives were consolidated to yield either a single “best-of’ prototype or several distinct alternatives that could then be evaluated with users.247

Additive manufacturing has opened the door to the creation of lightweight lattice structures. However, present Computer-Aided Design (CAD) and Computer-Aided Engineering (CAE) software are unsuitable for these types of structures. The objective of this research is to examine the performances of current CAD and CAE software to design lattice structures and to demonstrate their limitations and propose requirements for future developments. A performance evaluation of a case study for lattice structure designs was conducted. The criteria used for the evaluation were CAD human-machine-interface, RAM consumption, data exchange between CAD, CAE and CAM tools and finite element analysis (FEA) duration and file sizes. The CAD tool was incapable of executing a repetition function for octet-truss lattice structures of 150 x 150 x 150 mm dimensions or larger and the software stopped working. For 70 × 70 × 70 mm octet-truss lattice structure, the FEA computation file size reached 36.6 GB. The CAD file size of a 200 x 200 x 200 mm octet-truss lattice structure reached nearly 290 MB. In conclusion, this study exposes the performance inadequacy of current CAD and CAE tools and CAD file formats to design lattice structures for additive manufacturing parts.