• The KIPS Transactions:PartD
• /
• v.9D no.6
• /
• pp.1083-1090
• /
• 2002

The software development methodology has not caught up with the rapid change of information technology. Most of the software development projects use structural methodology or information engineering methodology. If established software development methodologies don't reflect technologies applied to the project, the project may be performed ineffectively. This paper describes a model in which we can apply a new information technology to an already existed structural methodology or information engineering methodology. This model uses the technique of the divide and conquer that software development life cycle is divided into phases, each phase is divided into viewpoint- areas and the software development processes of a new information technology are applied to each small area. By using the design phase this paper shows application example, in which I applied web-based development processes to CS@RoadMap Methodology of KCC Information & Communication, a system provider in Korea. The CS@RoadMap Methodology reflecting the Web technology, Web@RoadMap Methodology, has been applied to the public-domain projects.

• Archives of design research
• /
• v.12 no.1
• /
• pp.15-24
• /
• 1999

The deVelopment of technologies changes the thinking of people and the ways of IMngs. The software developers as well as users are now aware of the importance of graphic user interface design, and the usage of graphic elements is getting rrore and more easier due to the technological improvements based on the windows system(Microsoft). For these reasons, people who engaged in software developments do much more efforts to get user-oentered design solutions, in other words, the usability improvements. And the interdisciplinary projects teams which consist of experts of various fields are increasing in number. But, the lack of understanding on software developments and the proceeding of design work without the consideration of entire process of a project make interface design work difficult. For exampIe, some engineers often think designers as persons who decorate their products in the final stage. In this thesis, through the investigation of user interface design and software development process, the frarnework of effective team projects is proposed. The main purposes of this thesis are to define the work area and position of designers and to propose the interface design process for the cooperative software development projects within the interdiociplinary teams.

• The Mathematical Education
• /
• v.46 no.3
• /
• pp.331-349
• /
• 2007

This study aims to improve the teaching and learning method on the conic sections. To do that the researcher analyzed the impact of dynamic geometry software on students' problem solving of the conic sections. Students often say, "I have solved this kind of problem and remember hearing the problem solving process of it before." But they often are not able to resolve the question. Previous studies suggest that one of the reasons can be students' tendency to approach the conic sections only using algebra or analytic geometry without the geometric principle. So the researcher conducted instructions based on the geometric and historico-genetic principle on the conic sections using dynamic geometry software. The instructions were intended to find out if the experimental, intuitional, mathematic problem solving is necessary for the deductive process of solving geometric problems. To achieve the purpose of this study, the researcher video taped the instruction process and converted it to digital using the computer. What students' had said and discussed with the teacher during the classes was checked and their behavior was analyzed. That analysis was based on Branford's perspective, which included three different stage of proof; experimental, intuitive, and mathematical. The researcher got the following conclusions from this study. Firstly, students preferred their own manipulation or reconstruction to deductive mathematical explanation or proving of the problem. And they showed tendency to consider it as the mathematical truth when the problem is dealt with by their own manipulation. Secondly, the manipulation environment of dynamic geometry software help students correct their mathematical misconception, which result from their cognitive obstacles, and get correct ones. Thirdly, by using dynamic geometry software the teacher could help reduce the 'zone of proximal development' of Vigotsky.

• Journal of KIISE:Software and Applications
• /
• v.27 no.2
• /
• pp.134-147
• /
• 2000

Even though software industry has been activated, there lack in results of studies on evaluation effort and cost of software systems including Information Technology Security System (ITSS). In this paper, we present a process and a tool for evaluation effort and cost of ITSS, which are conformed to a ITSS evaluation criteria(i. e., Common Criteria or ISO/IEC 15408), by utilizing Evaluation Work Break-down Structure (EWBS) and conventional software development cost estimation methods. Even though we concentrate on ITSS, results of this paper can be applied to estimation of effort and cost of evaluation of software development process and software products.

• Industrial Engineering and Management Systems
• /
• v.10 no.1
• /
• pp.43-53
• /
• 2011

Currently, knowledge within the field of software development is largely implicit and is not formally disseminated and shared. This means that there is little improvement and regeneration of processes, and knowledge gained from previous projects is not necessarily applied to new ones. In order to turn this situation around it is necessary to take an organized approach to sharing job-related information. For this study, the authors constructed "Amalab-Project Planning Navigation System, or A-PPNS", a system for organizing accumulated knowledge related to the field of software development. More specifically, A-PPNS is a business process monitoring system and consists of the following four elements: (i) Optimized estimate support subsystem, (ii) Schedule monitoring system, (iii) QCD optimization diagnostic system, and (iv) Strategic technology accumulation system. The effectiveness of this system has been demonstrated and verified at Company A, a system integration company.

• Convergence Security Journal
• /
• v.12 no.6
• /
• pp.93-99
• /
• 2012

As the most common application development of software development time, error-free quality, adaptability to frequent maintenance, such as the need for large and complex software challenges have been raised. When developing web applications to respond to software reusability, reliability, scalability, simplicity, these quality issues do not take into account such aspects traditionally. In this situation, the traditional development methodology to solve the same quality because it has limited development of new methodologies is needed. Quality of applications the application logic, data, and architecture in the entire area as a separate methodology can achieve your goals if you do not respond. In this study secure coding, the big issue, web application factors to deal with security vulnerabilities, web application architecture, design procedure is proposed. This proposal is based on a series of ISO/IEC9000, a web application architecture design process.

• The Transactions of the Korea Information Processing Society
• /
• v.7 no.5
• /
• pp.1388-1400
• /
• 2000

An important technical issue in recent software development is to make needed software by the composition of components that are assemblable, and configurable, and independently extracted. The main advantage of component-based software development is reducing development time and cost. It is more cost-effective in development time to use components that are already developed than developing from scratch. There are two ways of component-based software development: one is to compose self-developed components, and the other is to by the components developed by third-parties and compose them. In the second case, existing non component programs must can be used for reuse in the component development. In this paper, we approach two methods for increase of reusability of Java program. First, we suggest the technique of extracting the elements suitable for the Beans component model from Java program, and then we show a process and a guideline of converting the extract elements into the Beans component model. Second, we suggest a technique of automatically extracting component information from the Java Beans component, expressing them in XML, its is possible to reuse the efficient component environment.

• Journal of KIISE:Software and Applications
• /
• v.31 no.10
• /
• pp.1286-1303
• /
• 2004

Component-based Development is gaining a wide acceptance as an economical software development paradigm to develop applications by utilizing reusable software components. Well-defined interface manages coupling and cohesion between components, minimizes the effect on the user in case of component evolvement, and enhances reusability, extendibility and maintainability. Therefore, study on systematic development process and design guidelines for component interface has been required since the component has been introduced. In this paper, we propose three types of interfaces based on software architecture layers and functionality types； Provided Interface which provides functionality of a component, Required Interface which specifies required functionality that is provided by other components, and Customize Interface which tailors the component to customer's requirement. In addition, we suggest design criteria for well-designed interface, and systematic process and instructions for designing interface. We firstly cluster operations extracted from use case model and class model to identify Provided interfaces, and design Customize interfaces based on artifacts for variability. We also specify Required interfaces by identifying dependency among interfaces. Proposed interface design method provides traceability, throughout the component interface design. And furthermore, proposed guidelines support practical design for high quality component based on a case study.

• 제어로봇시스템학회:학술대회논문집
• /
• 2000.10a
• /
• pp.416-416
• /
• 2000

The Systems Engineering, as a methodology for engineering and management of today's ever-growing complex system, is a comprehensive and iterative problem-solving process. The process centers on the analysis and management of the stakeholders'needs throughout the entire Life-cycle of a system and searches for an optimized system architecture. There are many essential needs and requirements to be met when a system development task is carried out. Systems Engineering Management PLan(SEMP), as a specification for system development process, must be established to satisfy constraints and requirements of stakeholders successfully and to prevent cost overrun and schedule delay. The paper suggests a systematic SEMP development process and demonstrates a data model and schema for computer-aided systems engineering software, RDD-100, for use in the development and management of SEMP These are being applied to the systems engineering technology development task for the next-generation high-speed railway systems in progress.

• Journal of Information Processing Systems
• /
• v.2 no.3 s.4
• /
• pp.137-142
• /
• 2006

A large portion of the embedded system development process involves the integration of hardware and software. Unfortunately, communication across the hardware/software boundary is tedious and error-prone to create. This paper presents an automatic hardware/software interface generation system. As the front-end of hardware/software co-design frameworks, a system designer defines XML specifications for hardware functions. Our system generates hardware/software interfaces including Device Driver, Driver API, and Device Controller from these specifications. Embedded software designers can easily use hardware just like system libraries. Our system reduces the mistakes and errors that can be occurred when a software programmer directly connects software to hardware, and supports balancing labors between hardware developers and software programmers. Moreover, this system can be used as the back-end for a hardware/software co-design framework.