• IE interfaces
• /
• v.12 no.1
• /
• pp.49-55
• /
• 1999

There are many types of holes to be machined on dies manufactured in the car industry. In this paper we introduce a CAM software developed for hole machining of press dies. The CAM software automatically generates NC files for machining holes from CAD data modeled in the CATIA system. A procedure generating NC files consists of three steps. First, the geometric information such as types of holes, hole positions, hole diameters, and hole depths is extracted from CATIA models. And then tools to be used and operation orders are standardized to establish a data base. Finally, NC files are generated by considering the machining conditions such as feedrate and rpm. It is efficient that holes with the same type and the same size should be grouped and machined by a tool to reduce the tool change time. The optimal tool path for machining the holes in a group can be determined by applying an algorithm solving the traveling salesman problem.

• International Journal of Computer Science & Network Security
• /
• v.22 no.2
• /
• pp.81-90
• /
• 2022

There are several ways to improve software performance by using existing software. So, the developments of some programs are the most promising ways. However, traditional part programming studies usually assume that the components are recycled "as is". Existing models of component objects only provide limited support for partial adjustments, namely white box technologies ( copy-paste & inheritance) and the black-box methods (such as mixing and encapsulation). These technologies have problems related to recovery, efficiency, implementation of indirect costs, or their own problems. This paper suggests as JALTREE, The Black Box adaptation technology, which allows us for the implementation of previous components, but we need configurable the interface types, for measuring the adaptability. In this article we discussed the types of adjustments including component interfaces and component composition. An example of customizing JALTREE and component can be illustrated in several examples

• Advances in Computational Design
• /
• v.2 no.1
• /
• pp.43-56
• /
• 2017

The aim of this paper is to develop software for designing of steel reinforced elastomeric isolator (SREI) according to American Association for State Highway and Transportation Officials Load and Resistance Factor Design (AASHTO LRFD) Specifications. SREI is used for almost all bridge types and special structures. SREI-structures interface defines support boundary conditions and may affect the seismic performance of bridges. Seismic performance of the bridge is also affected by geometrical and materials properties of SREI. The selection of SREI is complicated process includes satisfying all the design constraints arising from code provisions and maximizing performance at the lowest possible cost. In this paper, design stage of SREI is described up to AASHTO LRFD 2012. Up to AASHTO LRFD 2012 analysis and design program of SREI performed different geometrical and material properties are created with C# object-oriented language. SREI-CAD, name of the created software, allows an accurate design for economical estimation of a SREI in a short time. To determine types of SREI effects, two different types of bearings, rectangular and circular with similar materials and dimension properties are selected as an application. Designs of these SREIs are completed with SREI-CAD. It is seen that ensuring the stability of circular elastomer bearing at the service limit state is generally complicated than rectangular bearing.

• Journal of Convergence for Information Technology
• /
• v.7 no.2
• /
• pp.67-76
• /
• 2017

Along with shortening the life cycle of software utilization and supporting various types of user functions, the importance of software architecture development has been emphasized recently. If a software architecture is developed flexibly and reliably for expansion to support new functionality, it can quickly cope with new market demands. This paper proposes an architecture design method based on design recovery of open source software to reuse the software in the development of sustainable software system. When using open source software to develop a software system based on software architecture, we can develop a software system rapidly and also can improve the reliability of the system because we use the already proven open source software in the development.

• Journal of Information Technology Applications and Management
• /
• v.26 no.2
• /
• pp.111-123
• /
• 2019

In this paper, software activity, software activity instance, and the quality of the activity instance are defined as the 'activity which is performed on the software product by a person or a group of persons,' the 'distinctive and individual performance of software activity,' and the 'performer's evaluation on how good or bad his/her own activity instance is,' respectively. The representative values of the instance quality population associated with a product and its sub-population are defined as the (software) activity quality and activity quality characteristic of the product, respectively. The activity quality model in this paper classifies activity quality characteristics according to the classification hierarchy of software activity by the goal. In the model, a quality characteristic can have two types of sub-characteristics : Special sub-characteristic and component sub-characteristic, where the former is its super-characteristic too simultaneously and the latter is not its super-characteristic but a part of its super-characteristic. The activity quality model is parsimonious, coherent, and easy to understand and use. The activity quality model can serve as a corner stone on which a software quality body of knowledge, which constituted with a set of models parsimonious, coherent, and easy to understand and use and the theories explaining the cause-and-relationships among the models, can be built. The body of knowledge can be called the (grand) activity-centric quality model of software.

• 한국경영정보학회:학술대회논문집
• /
• 2007.06a
• /
• pp.539-544
• /
• 2007

People tend to resist changing their software even alternatives are better then the current one. This study examines the resistance to change in the use of software from the switching costs perspective based on status quo bias theory. For this study, we select Web Browsers as software. Based on the classification of switching costs into three groups (psychological, procedural, and loss), this study identifies six types of switching costs (uncertainty, commitment, learning, setup, lost performance, and sunk costs). This study tests the effects of six switching costs on user resistance to change based on the survey of 204 web browser users. The results indicate that lost performance costs and emotional costs have significant effects on user resistance to change. This research contributes towards understanding of switching costs and the effects on user resistance to change. This study also offers suggestions to software vendors for retaining their users and to organizations for managing user resistance in switching and adopting software.

• KSII Transactions on Internet and Information Systems (TIIS)
• /
• v.8 no.6
• /
• pp.2118-2138
• /
• 2014

Risks are involved in all phases of the software life cycle, and due to these risks, software can face various problems that can cause different negative outcomes and sometimes, in extreme cases, the failure of the software. Most of these risks lie in the legacy software migration process. These risks can create many problems, and in the worst case they can lead to the failure of the migration project. This paper explores different types of risk analysis methods such as CRAMM, CORAS, OCTAVE and VECTOR. After comparing these methods, the two suitable methods were chosen, namely, OCTAVE and VECTOR. Based on the use of these two methods, the project suggests an enhanced EOV method for risk analysis in the migration of legacy software.

• Industrial Engineering and Management Systems
• /
• v.7 no.1
• /
• pp.51-56
• /
• 2008

With growing demand for zero defects, predicting reliability of software systems is gaining importance. Software reliability models are used to estimate the reliability or the number of latent defects in a software product. Most reliability models to estimate the reliability of software in the literature are based on the development lifecycle stages. However, in the maintenance phase, the software needs to be corrected for errors and to be enhanced for the requests from users. These decrease the reliability of software. Software Reliability Growth Models (SRGMs) have been applied successfully to model software reliability in development phase. The software reliability in maintenance phase exhibits many types of systematic or irregular behaviors. These may include cyclic behavior as well as long-term evolutionary trends. The cyclic behavior may involve multiple periodicities and may be asymmetric in nature. In this paper, SGRM has been adapted to develop a reliability prediction model for the software in maintenance phase. The model is established using maintenance data from a commercial shop floor control system. The model is accepted to be used for resource planning and assuring the quality of the maintenance work to the user.

• Journal of the Korean Institute of Illuminating and Electrical Installation Engineers
• /
• v.21 no.8
• /
• pp.10-19
• /
• 2007

Use of various lighting simulation software has been increased Lighting simulation software can be categorized into two types. One is for optical design while the other is for estimation and analysis of lighting design. Photopia 2.0 is typical software for optical design of a luminare and Lumen-micro 2000, Relux 2006, Lightscape 3.2 and AGI 32 are software for lighting design. Through using various lighting simulation software some different results can be found under the same conditions. Therefore, the purpose of this paper is to compare measured and simulated photometric data of different types of luminaires and to compare simulated values from Lumen-micro 2000, Relux 2006, Lightscape 3.2 and AGI 32 under the same conditions. In addition, the reasons for such differences are analyzed.

• Journal of KIISE:Software and Applications
• /
• v.34 no.8
• /
• pp.697-707
• /
• 2007

Since embedded software is very dependent for target hardware architecture, characteristics of the platform must be considered when designing the software. Furthermore, MPSoCs consists of heterogeneous hardware components that are specified in micro level. Thus mapping of embedded software for MPSoCs should be considered the characteristics. In this paper, we provide an approach to automatic mapping PIM (Platform Independent Model) of an embedded software to PSM(Platform Specific Model) for MPSoC(Multi Processor System On Chip) and verify its effectiveness with simulation. In the proposed approach, tasks are derived from an object oriented model based on the UML (Unified Modeling Language). And then the types of the derived tasks are identified. With the identified types and inter relationship between tasks, the tasks are assigned to appropriate heterogeneous hardware components. We expect that the approach improve accuracy of the assigning and concurrency of the deployed software.