Design extraction system for rapid development of object-oriented switching software

PurposeThe advent of web services and the semantic web have opened up opportunities for a new generation of interoperable systems on the web. The purpose of this paper is to show the importance of semantics in design and construction, and how this has long been recognised and addressed to varying extents by researchers.Design/methodology/approachThere is now the potential for designs to be developed through a system of collaborating design services and for input by the construction team members. The potential also extends to the construction phase where the designers can provide more timely responses to problems encountered in the field. Within this environment, there is the need for effective mechanisms for design and construction information management, in addition to an ontology that facilitates the sharing of design and construction information and the underlying semantics. This paper explores these trends in collaborative design and construction, and presents an ontology‐based approach to project information management in a semantic web environment.FindingsThe findings include a framework for semantic web‐based information management (SWIMS), which provides for effective collaborative information management. Examples, based on design and construction information, are presented to illustrate the key concepts.Originality/valueThis paper presents an innovative approach to overcoming the limitations of conventional information management approaches in construction. The proposed approach is expected to enhance collaboration, and avoid information loss, overload and misunderstanding,

In this paper, the authors explore the characteristics and requirementsof digitally supported ‘green’ building design. Well planned, integrated and interdisciplinary digital design practices play a vital role in the iterative processes of sustainable building design. Unlike traditional ways of working, the management of design information and process integration in green building design involves a wider range and a larger number of consultants utilizing sophisticated environmental modelling and analysis systems. To understand the complexities surrounding information management in this context, the authors focus on issues relating to: 1) information exchange and model management, and 2) multidisciplinary design process coordination. Different aspects of sustainable design modelling methodologies are explored in relation to technology requirements, information exchange, and multi-disciplinary collaboration. Finally, the literature is synthesised in a conceptual roadmap framing the key factors identified by the study.KeywordsBuilding information modelingenvironmental sustainable designinformation managementcollaboration

The early conceptual architectural design phases are characterized by a constant interplay of creating variants and assessment of those variants as well as their consistent detailing. Variant comparison plays a significant role in achieving the desired final building. Objectifiable criteria used for the evaluation and comparison of design variants can be used to legitimize decisions and selections as the design process proceeds. Moreover, using these criteria, such as the results of simulations and analysis performed by various domain experts, most likely leads to building designs with better performance. One major challenge in practice today is the management of design information and collaboration between several actors in a building project. A large portion of the Architecture, Engineering, and Construction (AEC) industry still deals with conventional methods to exchange design information. The growing use of building information models is promising, but even the most recent developments and practices still rely heavily on human-readable protocols and issue management systems (Beetz 2009; Borrmann et al. 2018). Considering the potential of schematized computer-readable communications to be analyzed and used for future references and case-based reasoning systems, this paper proposes a novel minimized communication protocol based on BIM, which aims to introduce a computer-readable, yet adaptive universal method/function which works on schematized information exchange requirements (templates) for different use cases. Furthermore, this concept will be explained and demonstrated using an example scenario.

Object-oriented software metrics are important in software engineering field for measurement of the software quality, size estimation, complexity and effort. Object oriented software development is the most popular and best practice in software development. Object oriented software metrics can be used for measuring extend of object orientedness of a program. These quantities are important information indicators, that can be helpful for a software developer in take decisions for designing good software. It is proven that the software metrics provide quantitative information about the structure of the code, which can be used to determine the reliability of software. The design of the software is highly recommended to be object oriented in the software development environment. Software metrics specific to programs that have object oriented design can be used to measure the quality of the software like inheritance, assessing the effects of coupling, the complexity of the code, size aspects, etc, of the software developed in such an environment. Software measurement is a way for assessing the quality of software. Many attributes can define quality of a software, internal (size, complexity) as well as external (reliability)[14]. Often internal attributes are contributing factors to external attributes. Reliability as a term means the degree to which a component, product or system executes specified functions for a specific period of time under specified conditions. Software reliability is the software being trustworthy of the specifications. The aim of the work is to model the relationship between reliability of object oriented software to the object oriented design metrics and predict reliability of software.

Time, effort and money required in maintaining software has always been considered greater than its development time. Also, its ambiguity in forecast at early stage of software development makes the process more complicated. The early estimation of maintainability will significantly help software designers to adjust the software product, if there is any fault, in early stages of designing. By doing this; time, effort and money required in maintaining software will be lessened. Although Object Oriented Software Development (OOSD) approach is equipped for enhancing software maintainability, a method for finding out if the required level of maintenance is being achieved amid the development process is required. This can be accomplished through measurement. This paper outlines the need and importance of maintainability at design phase and develops a Metrics-Based Maintainability Estimation Framework for Object-Oriented software(MEFOOS) that estimates the maintainability of object oriented software components in regard of their Understandability, Modifiability and Portability—which are the sub-attributes of maintainability. Keywords: Software maintenance, Software Maintainability, maintainability model, Software Metrics, Software Component DOI : 10.7176/JIEA/9-4-02 Publication date :June 30 th 2019

Research aircraft have become increasingly dependent on advanced control systems to accomplish program goals. These aircraft are integrating multiple disciplines to improve performance and satisfy research objectives. This integration is being accomplished through electronic control systems. Because of the number of systems involved and the variety of engineering disciplines, systems design methods and information management have become essential to program success. The primary objective of the system design/information tool for aircraft flight control system is to help transfer flight control system design knowledge to the flight test community. By providing all of the design information and covering multiple disciplines in a structured, graphical manner, flight control systems can more easily be understood by the test engineers. This will provide the engineers with the information needed to thoroughly ground test the system and thereby reduce the likelihood of serious design errors surfacing in flight. The secondary objective is to apply structured design techniques to all of the design domains. By using the techniques in the top level system design down through the detailed hardware and software designs, it is hoped that fewer design anomalies will result. The flight test experiences of three highly complex, integrated aircraft programs are reviewed: the X-29 forward-swept wing, the advanced fighter technology integration (AFTI) F-16, and the highly maneuverable aircraft technology (HiMAT) program. Significant operating anomalies and the design errors which cause them, are examined to help identify what functions a system design/information tool should provide to assist designers in avoiding errors.

A business strategy based on customized products with a high level of variety requires systems for efficient generation of product variants. An area identified in near collaboration with five industrial partners that has not been subject for extensive research is how to support management of different application domains, projects, task knowledge and design information together with the possibility to perform detailed analyses on the data generated by a design automation system implementation. Initially, a number of success criteria were identified and the functionality of a database was perceived as a promising approach. Explorative work was conducted for the purpose to reveal the conceptual model and the principles that a system would reside upon. The work has resulted in an approach, consisting of an information model and underlying principles, presented in this paper to be used when developing a design automation system for quotation preparation. The functionality and usefulness has been demonstrated and validated by a system implementation developed in collaboration with an industry partner. It can be concluded that a system founded on the presented approach supports management and analysis of quotations and product variants.

Recently, reverse engineering has become widely recognized as a valuable process for extracting system abstractions and design information from existing software. This study focuses on ForUML, a reverse engineering tool developed to extract UML diagrams from modern object-oriented Fortran programs. Generally, Fortran is used to implement scientific and engineering software in various domains, such as weather forecasting, astrophysics, and engineering design. However, methods for visualizing the existing design of object-oriented Fortran software are lacking. UML diagrams of Fortran software would be beneficial to scientists and engineers in explaining the structure and behavior of their programs at a higher level of abstraction than the source code itself. UML diagrams can enhance discussions within development teams and with the broader scientific community. The first version of ForUML produces only UML class diagrams. Class diagrams provide a useful window into the static structure of a program, including the structure and components of each class and the relationships between classes. However, class diagrams lack the temporal information required to understand class behavior and interactions between classes. UML sequence diagrams provide this important algorithmic information. Therefore, herein, an extension for ForUML to extract UML sequence diagrams from the Fortran code is proposed, and this capability is provided using a widely used open-source platform. This study argues that the proposed extension will enable the visualization of object-oriented Fortran software behavior and algorithmic structure and thereby enhance the development, maintenance practices, decision processes, and communications in scientific and engineering software communities worldwide.

The need for reengineering of software systems has dramatically increased as legacy systems are migrated to new platforms and rewritten in modern object-oriented languages. Although the de facto standard for describing object-oriented systems is the Unified Modeling Language (UML), many legacy systems have been documented using non-object-oriented structured analysis and design methods. Problems arise in the migration because non-object-oriented documentation is inherently not conducive to the development of object-oriented systems. This chapter presents a set of rules to automate the conversion of systems which were originally modeled using structured techniques to UML. The newly created UML documentation can then be used in developing an object-oriented equivalent system. The UML model may also be used by computer aided software engineering tools to implement a new system. The reengineering rules are tested on an example structured system to demonstrate their viability.

As organizsations adopt the principles of total quality and become customer oriented new measures are needed to assess product performance within a variety of organizational settings. This study reports the relationships between usage of quality information, employee participation and quality management in product design and product performance. Using data collection with quality managers of a sample of industrial companies, rigorous factor analysis and regression analysis and regression analysis have been fostered and hypotheses regarding variables used for describing product performance of organizational settings have been described.

A framework of information and knowledge management for product design and development — A text mining approach

IDEF는 전통적인 구조적 소프트웨어 개발에 많이 사용된 방법론이다. 객체지향 소프트웨어가 널리 사용됨으로 이에 맞는 모델을 IDEF 개발 기관에서 제시한 것이 IDEF4다. UML은 객체지향 소프트웨어의 산업표준으로서 널리 이용되는 도구이다. IDEF는 CALS/EC 등에서 많이 사용하고 UML은 일반적인 객체지향 소프트웨어 개발할 때 많이 사용하기 때문에 소프트웨어 개발자들은 IDEF4모델의 표현법 보다는 UML의 표현법에 익숙하다. 또한 UML을 사용한 CASE 도구가 많이 개발되어 있어 IDEF4 모델을 UML 모델로 표현하면 이런 도구를 사용하여 소프트웨어 개발을 좀 더 효율적으로 할 수 있다. 본 논문은 IDEF4 모델을 UML 모델로의 변환하는 방법에 관하여 기술하였다. 변환 규칙을 제시하고 이를 사례에 적용하였다. IDEF is a widely used methodology for traditional structured software development. As object-oriented softwares are widely used, an object-oriented version of IDEF, IDEF4, is developed. UML is de facto standard for object-oriented software development methods. Whereas IDEF is widely used for CALS/EC, UML is used for general object-oriented software development. Most software developers are not familiar with IDEF4 but familiar with UML. Moreover, UML has many CASE tools. So we can develop software efficiently if we convert IDEF4 model to UML model. In this paper, we transform IDEF4 models to UML models. We explain the rules and methods to convert IDEF4 model to UML model and applied the transform methods and rules to a case study.

This paper deals with Design Supporting System that aims to support activities of welding design and joint design comprehensively. The following concepts are introduced into our system in order to deal with both the welding design and joint design explicitly:(1) Design information on both joint and welding is clearly and explicitly defined as product data.(2) The phase of joint design is different from the phase of welding design, and these two phases start from the division of the full structure into parts and end in determining values of detailed to execute welding operations.(3) Joint and welding is decomposed into some data, and appropriate design procedures depend on the decomposed data.(4) Determining optimal joint data is converted into selecting the optimal plan from a lot of feasible design plans. That is to say, a lot of feasible plans in every design stages are created semi-automatically and evaluations of each plan are calculated automatically by our system. As a result, optimal design plans are selected and the design stage moves to the next.(5) The design processes that are explicitly described are utilized in our system.In order to implement our system, two design process models of both welding and joint are discussed in this report: one model is Vertical Flow Model and the other is Horizontal Flow Model. The Vertical Flow Model indicates the design process among design stages, on the other hand, the Horizontal Flow Model indicates the value determination activities in each design stage.Some examples of both welding design and joint design by using our system are shown in this paper.

Object oriented software development different from traditional development products. In object oriented software polymorphism, inheritance, dynamic binding are the important features. An inheritance property is the main feature. The compilers usually detect the syntax oriented errors only. Some of the property errors may be located in the product. Data flow testing is an appropriate testing method for testing program futures. This test analysis structure of the software and gives the flow of property. This study is designed to detect the hidden errors with reference to the inheritance property. Inputs of the tool are set of classes and packages. Outputs of the tools are hierarchies of the classes, methods, attributes and a set of inheritance related bugs like naked access, spaghetti inheritance bugs are automatically detected by the tool. The tool is developed as three major modules. They are code analysis, knowledge base preparation and bugs analysis. The code analysis module is designed to parse extract details from the code. The knowledge base preparation module is designed to prepare the knowledge base about the program details. The bug's analysis module is designed to extract bugs related information from the database. It is a static testing. This study focused on Java programs.

This paper identifies key requirements for an advanced engineering design information management system. With the advent of information management technology and design automation, the definition of Computer Aided Design (CAD) systems has evolved beyond the realm of geometric data to include support for a very wide range of activities of an intelligent design agent — such as definition, manipulation and analyses of complex information models of a product. These information models represent not only conventional product data associated with typical CAD applications (FEM, NC, Geometric models, etc.), but also design information characterizing correlations between the requirements, function, behavior and form dimensions of the design. The new generation of CAD systems are expected to provide the designer with capabilities for defining, manipulating and reasoning with such models. These new functionalities are important to individual designers, as well as organizations as the need to manage information as a corporate asset is becoming a a critical facet of corporate strategies. This paper explores these needs using design scenarios that trace the conceptual phases of design as well as the organization relevance to the design process. The first scenario deals with the innovative design of drilling applications for lunar environments, while the second scenario deals with the routine design of computer peripherals in a collaborative, multidisciplinary environment. These scenarios are used to elicit high level requirements, and subsequently the development of prototype systems. Preliminary results from the prototypes are presented herein.