• Journal of Information Technology Services
• /
• v.23 no.1
• /
• pp.37-53
• /
• 2024

Recently, the application of microservice architecture has been increasing as information systems have shifted to cloud environments. The purpose of this paper was to analyze the case of applying microservice architecture to MES in the manufacturing field, summarize the results of how it was applied in practice, and find out the effects of the application. Based on the improvement project by applying microservice architecture to the existing steel manufacturing MES, 11 principles of microservice application were derived through literature research, and the implementation process and results were summarized according to these principles. In addition, through a comparison of systems in the service industry and the manufacturing industry, we investigated why the application of microservices was more active in the service industry and whether the application in the manufacturing industry can be expected to have the same effect. We also evaluated the results and changes in the overall system after implementation. In particular, we analyzed the SR (Service Request) processing status of users' requests for system changes and operators' requests to see how much the lead time was reduced. The results showed that 8 out of 11 microservice application principles were properly implemented according to the principles, but the remaining 3 were not applicable due to practical difficulties and organizational circumstances. Despite not following all of the principles, the project was able to be implemented without any problems, and the most noticeable change as a result of the microservices architecture was that the lead time was reduced by 9 days compared to the previous system. This proves that it is possible to quickly adapt to customer requirements, and it also proves that the system is more flexible and scalable than the existing monolithic system.

• JSTS:Journal of Semiconductor Technology and Science
• /
• v.9 no.2
• /
• pp.75-79
• /
• 2009

A system-on-a-chip communication architecture has a significant impact on the performance and power consumption of modern multi-processors system-on-chips (MPSoCs). However, customization of such architecture for a specific application requires the exploration of a large design space. Thus, system designers need tools to rapidly explore and evaluate communication architectures. In this paper we present the method for application-specific low-power bus architecture synthesis at system-level. Our paper has two contributions. First, we build a bus power model of AMBA AXI bus communication architecture. Second, we incorporate this power model into a low-power architecture exploration algorithm that enables system designers to rapidly explore the target bus architecture. The proposed exploration algorithm reduces power consumption by 20.1% compared to a maximally connected reduced matrix, and the area is also reduced by 20.2% compared to the maximally connected reduced matrix.

• Journal of the Korea Society of Computer and Information
• /
• v.15 no.12
• /
• pp.217-225
• /
• 2010

Among web-based systems being widely used now, there are so many systems which are still using an user-level access control method. By successfully applying role-based access control(RBAC) to web-based application systems, we can expect to have an effective means with reinforced security for Internet-based systems. In order to apply RBAC to web-based application systems, we should come up with a system architecture for it. I proposed a system architecture which is needed to apply RBAC to web-based application systems. The proposed system architecture is largely composed of system composition and system functioning. For details, firstly, a certificate used by RBAC is specified. Secondly, a system architecture using a user-pull method is proposed and overall system components are mentioned with a role server being centered. Then, I showed how the system architecture can work to carry out RBAC on web-based application systems. Lastly, the analyses on the proposed system architecture are described for the purpose of proving its feasibility.

• 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.

• Journal of the Korean Institute of Landscape Architecture
• /
• v.35 no.4
• /
• pp.40-47
• /
• 2007

The objective of this study is to analyze the propriety of the Biotope Area Factor's(BAF) application and propose an improvement plan. The BAP system, initially started by Seoul metropolitan city, is being settled in Korea. The BAF originated from the Biotop $Fl{\ddot{a}}chen$ Faktor(BFF) system of Berlin Germany. It was established as part of the Landscape Plan for the ecological function recovery in the high density built-up area with a sense of environmentally friendly urban management. The study compared the BAF's present condition of Ganddong-Gu, Seoul with Seoul's BAF system. Some problems appeared from the system application. Firstly, it may cause ecological damage if the site ranges are more than current BAF system limits. Secondly, the application of the current BAF system has the possibility of general redevelopment, but the partial improvement considering current standards of the high density built-up area's paving section is impossible. Lastly, division of the application object and application type are not divided well. In addition, the Seoul BAF which is currently applied across the board is based on the destruction of the natural area and low density built-up area. Accordingly, to improve these problems requires a complementary system protecting the ecological function prior to the application of the BAF and with restricted application to high density of BAF system built-up area.

• Information Systems Review
• /
• v.3 no.2
• /
• pp.277-288
• /
• 2001

Of critical importance to the success of any e-commerce site are the two factors: rapid application development and quick response time. A three-tier architecture composed of presentation layer, business layer, and data access layer emerges to allow rapid changes in user interface, business logic, and database structures. Too often, such a logical three-tier architecture is considered as requiring a three-tier physical architecture: Web server, application server, and database server running on separate computers. Contrary to the common belief, a Web stress test reveals that the three-tier logical architecture implemented on a two-tier physical platform guarantees a quicker response time due to the reduction in cross-machine communications. This would lead business firms to economize their spending on e-commerce: increasing the number of physical servers to expedite transaction is not necessarily the best solution. Before selecting a particular hardware configuration, a Web stress test needs to be conducted to compare the relative merits of alternative physical architectures. Together with capacity planning, Web stress test emerges as a powerful tool to build robust, yet economical e-commerce sites.

• Journal of Information Technology Applications and Management
• /
• v.20 no.3
• /
• pp.1-18
• /
• 2013

Software architecture is the blueprint for a software system and should provide consistent guidelines for design, implementation, and maintenance throughout the entire lifecycle of the system. Components, interactions between the components, well-formed structure, reasons, and various perspectives reflecting various stakeholders' concerns changing through the phases of software lifecycle are the key elements of software architecture. The architect identifies and engages the stakeholders, understands and captures stakeholder's concerns including those regarding life cycle, and lets the concerns reflected in the architecture. To do so, architect should take into consideration various contextual elements regarding the system too. We make an extended list of the elements, especially those of business application software architecture, that the architect should take into consideration and construct a model of the relationships between the elements.

• 한국경영정보학회:학술대회논문집
• /
• 2007.11a
• /
• pp.377-382
• /
• 2007

To transform the enterprise system into the 'Real Time Enterprise' with respect to IT, I suggest the conceptual application model which is composed of pieces(components) extracted from different packaged applications working in a heterogeneous environment based on the 'business activity' in other words, business services provided by internal (inter-enterprise) and external (extended enterprise) application to support a business activity within in an enterprise and the design mechanism focusing service tier which acts as intermediate tier within application architecture.

• IEIE Transactions on Smart Processing and Computing
• /
• v.5 no.1
• /
• pp.55-62
• /
• 2016

In this paper, we propose a hybrid multi.system-on-chip (H-MSoC) architecture that provides a high-flexibility system in a rapid development time. The H-MSoC approach provides a flexible system-on-chip (SoC) architecture that is easy to configure for physical- and application-layer development. The physical- and application-layer aspects are dynamically designed and modified; hence, it is important to consider a design methodology that supports rapid SoC development. Physical layer development refers to intellectual property cores or other modular hardware (HW) development, while application layer development refers to user interface or application software (SW) development. H-MSoC is built from multi-SoC architectures in which each SoC is localized and specified based on its development focus, either physical or application (hybrid). Physical HW development SoC is referred to as physical-SoC (Phy-SoC) and application SW development SoC is referred to as application-SoC (App-SoC). Phy-SoC and App-SoC are connected to each other via Ethernet. Ethernet was chosen because of its flexibility, high speed, and easy configuration. For prototyping, we used a LEON3 SoC as the Phy-SoC and a ZYNQ-7000 SoC as the App-SoC. The proposed design was proven in real-time tests and achieved good performance.

• Proceedings of the KIEE Conference
• /
• 2006.04a
• /
• pp.297-299
• /
• 2006

Many distributed applications is developed in various environment such as operating system, software platform. So, they exhibit different types of system behavior, status, during the course of their operation. Each such behavior may have different functional and non-functional requirements. Therefore, many distributed application need to fault-tolerance solution. Personal robot provide various service or application. Because personal robot has many application or service, it need to fault-tolerance architecture. A flexible architecture is required to provide dependability. In this paper, it is suggested a fault-tolerant architecture for module-based personal robot with module fault-tolerance, service fault-tolerance.