• Journal of KIISE:Software and Applications
• /
• v.28 no.12
• /
• pp.896-909
• /
• 2001

Recently, above 50 percentages of software are being developed based on distributed application platforms. And recent technologies such as EJB(Enterprise Java Beans)[1]COM(Component Object Model)[2] CORBA(Common Object Request Broker Architecture)[3] have been advanced for distributed component-based software development . Therefore a systematic development process is necessary to develop component based applications using distributed application platforms. However, most of component-base software development processes do not define concrete flows between tasks and relationships among artifacts of each task Also, distribution issues are not considered explicitly in most of component-based software development In this paper, we present an approach to analyze and design software based on distributed components. In this approach, we propose systematic guidelines for developing a software based on Unified process and the relationships among artifacts which are produced, Also we explicitly consider the distribution issues such as performance, fault tolerance, security, distributed transaction of CORBA environments.

• Journal of Institute of Control, Robotics and Systems
• /
• v.21 no.2
• /
• pp.173-178
• /
• 2015

Cloud systems are efficient models that can utilize various infrastructures, platforms, and applications regardless of the type of clients. This paper proposes a cloud-based integrated development environment (IDE) for robot software development which would make software development easier. The proposed system provides robot simulation to test the robot HW modules or robot systems for development and testing of software operating in a robot system with two or more different operating systems (OS) such as Windows, Linux, and real-time OS. This paper implements and evaluates the proposed system using OPRoS [33].

• IEMEK Journal of Embedded Systems and Applications
• /
• v.8 no.4
• /
• pp.195-204
• /
• 2013

The embedded software has been developed in the forms of various versions that provides similar service based on product family. For increase usefulness of product family, software must has well-structured and reusable properties. Software architecture is important to improve adaptability in model-based development of embedded software mounted onto product family. In this paper, we proposed a technique of ADD(Attribute-Driven Design)-based software architecture design for low power software development. This technique provides a chance to consider the power consumption issue in design phase of software, and makes possible to develop low power embedded software.

• Journal of Information Technology Applications and Management
• /
• v.11 no.2
• /
• pp.15-27
• /
• 2004

Most software projects inevitably involve various types and degrees of uncertainty. Without proper risk assessment and coordination, software projects can easily run out of control and consume significant additional resource. Thus, risk management techniques are critical issues to information system researchers. Previous empirical studies of U.S. software firms support the adoption of development standardization and user requirement analysis techniques in risk-based software project management. Using data collected from software projects developed in Korea during 1999-2000, we conduct a comparative study to determine how risk management strategies impact software product and process performance in countries with dissimilar IT capabilities. In addition, we offer an alternative conceptualization of residual performance risk. We show that the use of residual performance risk as an intervening variable is inappropriate in IT developing countries like Korea where the role of late stage risk control remedies are critical. A revised model is proposed that generates more reliable empirical implications for Korean software projects.

• Journal of Korean Society for Quality Management
• /
• v.20 no.2
• /
• pp.94-108
• /
• 1992

This study involves an experiment for the cognitive experiment design and the human reliability in software engineering. Its overall objectives are to analyze common-cause human domain error and reliability in human-software interaction. A laboratory study was performed to analyze software engineers' task behavior in software production and to identify software design factors contributing to the effects in common cause failure redundancy. Common-cause model and its function were developed, then the main experiment using programming experts was conducted in order to define a new cognitive paradigm, in the aspects of identification, pattern recognition, and behavior domain for human reliability and quality control in software development. The results and analytical procedures developed in this research can be applied to reliability improvement and cost reduction in software development for many applications. Results are also expected to provide guidelines for software engineering quality control and for more effective design of human-software interface system.

• Journal of Information Processing Systems
• /
• v.6 no.2
• /
• pp.219-234
• /
• 2010

Gaming is an old humans' habit. Games help in logical development and encourage learning of theoretical and practical concepts. Besides they offer entertainment and challenge. The advent of the personal computer changed this tradition. Every year new challenges arise in a digital format, which lead the young and adults to spend hours in front of a computer or TV screen in an attempt to overcome hurdles and reach an objective. Quality, sophistication, and constant innovation are attained through complex computer software that almost has an obligation to improve as each new title is released, due to this game development becomes a challenge. Considering that a game title is software and thus faces the same restrictions of business applications, this article intends to analyze, under the optics of reuse, if game development resorts to reuse, and where and how this happens.

• ETRI Journal
• /
• v.32 no.5
• /
• pp.646-656
• /
• 2010

A component is a reusable and replaceable software module accessed through its interface. Component-based development is expected to shorten the development period, reduce maintenance costs, and improve program reusability and the interoperability of components. This paper proposes a new robot software component platform in order to support the entire process of robot software development. It consists of specifications of a component model, component authoring tool, component composer, and component execution engine. To show its feasibility, this paper presents the analysis results of the component's communication overhead, a comparison with other robotic software platforms, and applications in commercial robots.

• Journal of KIISE:Software and Applications
• /
• v.37 no.7
• /
• pp.518-535
• /
• 2010

Cloud Computing is emerged as an effective reuse paradigm, where service providers operate hardware and software and as a service, and service consumers invoke the service through Internet. Software-as-a-Service (SaaS) is a type of cloud services, where the whole software is designed as a service so that several consumers can reuse the SaaS. While tradition software applications are developed for a specific organization, SaaS is developed for multiple users in the various organizations. Hence, reusability is very essential characteristic of SaaS. Reusability is defined as a metric of how effective and efficient software functionalities can be used by various users. Reusability in SaaS is evaluated by considering three sub-characteristics; applicability, adaptability, and scalability. Since such a SaaS has considerable differences and characteristics from traditional software applications, conventional methods including object-oriented modeling, component-based development method, and service-oriented architecture (SOA) service development method would be limited in developing services which can fulfill these three sub-characteristics related to reusability as well as SaaS-intrinsic characteristics. Hence, there is a great demand for effective processes for developing SaaS cloud services. In this paper, we present a practical process for developing SaaS, which focuses on ensuring reusability. And by performing a case study with our proposed SaaS development process, we evaluate applicability of our proposed process and explain how the process is used in a real domain. Then, we compare our proposed process with others for verifying our study. Through the proposed process, cloud services with high quality can be more effectively developed.

• Convergence Security Journal
• /
• v.12 no.4
• /
• pp.115-122
• /
• 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.

• Proceedings of the Korea Society for Simulation Conference
• /
• 2001.10a
• /
• pp.354-358
• /
• 2001

Cosim (Hardware and Software Co-Simulator) is a JavaBeans-based simulation tool fur validating systems architecture and estimating performance of web applications. Cosim has four components: Modeler, Translator, Engine and Scenario. Users start from Modeler to describe systems architecture in UML(Unified Modeling Language) deployment diagram, and then specify hardware & software performance parameters such as execution delay, network topology, and frame size. All information specified on Modeler are sent to Translator, and then automatically converted to Java programs. Scenario is responsible to run the Java program and produce results in text reports and graphs. Developers can reduce development time and cost by validating systems architecture of web applications before the actual deployment.